Replication: remove merge subscription without existing publisher?

Hi all,
I'm a rather newbie, not only to this forum but also to sql server having a question to the following issue:
Is it possible to drop/remove/delete the "orphan" of a merge subscription on one instance of sql server without having the (former) distributor/publisher (on other instance) available?
The background is: I had a small replication infrastructure with two instances (on two machines), one the publisher and distributor, the other the subscriber. Now it happened that the publisher/distributor machine was completely set up new without having the replication dropped in advance, what remained on the subscriber is now a database with all the merge/replication tables and the guid columns in the user tables.
Moreover this, an entry remained in the subscription saying that a subscription with the former publisher exists...

Can I remove these "orphans" without having to setup the instance again?

Thank you,
AndyDid you recreate the Publisher again?|||Originally posted by smasanam
Did you recreate the Publisher again?

No, I didn't recreate the publisher, but I plan to do so, however, with slightly different properties (e.g. publisher db name has changed)...|||Originally posted by AndreasJaehn
No, I didn't recreate the publisher, but I plan to do so, however, with slightly different properties (e.g. publisher db name has changed)...
Sorry to ask again. Can you please give more details about your question.

Looks like you want to drop the subscription. If that is so you can drop the subscription or subscriber database.

Once you dropped the subscription and remove the subscription databases you can go head and change the schema of the database at the subscriber|||Originally posted by smasanam
Once you dropped the subscription and remove the subscription databases you can go head and change the schema of the database at the subscriber

The thing is that I cannot drop the subscription as this implies having a valid publisher, but I don't have the publisher anymore. The system Stored Procedure requires the publishing/distributing instance alive, even if I set the ignore_distributor flag...

I found something in the archive which comes quite close to my problem: http://dbforums.com/arch/69/2002/4/348973

I'll try it that way (see Ramakrishna Koni's comment)...

Thank you.