Cheers John, worked perfectly on the imported database. There was no 
connection to the original machine so no problems there. Just waiting 
until i can try it out on the partially uninstalled machine.

Thanks again,
James


John Sidney-Woollett wrote:
> Just a thought...
>
> I would probably as a precaution remove node entries for 
> _{clustername}.SL_NODE for nodes other than the once you are 
> connecting to BEFORE running the slonik uninstall command.
>
> John
>
> John Sidney-Woollett wrote:
>> James, these are from some notes I made about building test databases 
>> from a dump of a live (master) database with slony installed:
>>
>> Clear the replication information: Be VERY careful in trying to clear 
>> the replication information from the newly imported database. The 
>> replication information is cleared in two stages:
>>
>>   1. delete all records from _{clustername}.SL_TABLE and 
>> _{clustername}.SL_SEQUENCE
>>   2. then use a slonik script to remove the remainder of the 
>> replication information
>>
>> #!/bin/bash
>>
>> /usr/local/pgsql/bin/slonik ? _END_
>>
>> # define the cluster namespace
>> cluster name = {clustername};
>>
>> # define two nodes connection information
>> node 1 admin conninfo = ?dbname={yournewdatabase} 
>> host={newdatabasehost} user=postgres?;
>>
>> # uninstall the first node and cluster
>> uninstall node (id=1);
>>
>> _END_
>>
>> IMPORTANT: Make sure the the connection string is to the postgres 
>> instance/cluster holding the new database you just imported, and not 
>> to the one the dump file came from!
>>
>> Replace {clustername}, {yournewdatabase} and {newdatabasehost} by 
>> your appropriate values for your new database.
>>
>> Can't guarantee that the above will work for you, but it has always 
>> done so for me in the past.
>>
>> John
>>
>> James Brookes wrote:
>>> Hi All,
>>> Im hoping someone can point me in the right direction regarding some 
>>> problems im having. I've got two scenarios but the aim is generally 
>>> the same, to remove Slony changes from the database when the scripts 
>>> can not be used...
>>>
>>> 1) I've taken a database dump of a system that is running Slony and 
>>> restored it on a system that does not run Slony. How do i remove the 
>>> Slony elements from the database?
>>> 2) I ran the uninstall master script, which usually works fine, but 
>>> for some reason it failed about 3/4 of the way through. Now Slony 
>>> wont start because of conflicts with the previous instance and wont 
>>> stop because most of the instance has been removed. How do i remove 
>>> the Slony elements from the database?
>>>
>>> Im relatively new to Slony so something like this would take me a 
>>> while to solve. Im sure someone out there must have had a similar 
>>> requirement. Any help would be appreciated!
>>>
>>> Regards,
>>> James
>>> *
>>> *
>>>
>>>
>>>
>>> _______________________________________________
>>> Slony1-general mailing list
>>> Slony1-general at gborg.postgresql.org
>>> http://gborg.postgresql.org/mailman/listinfo/slony1-general
>> _______________________________________________
>> Slony1-general mailing list
>> Slony1-general at gborg.postgresql.org
>> http://gborg.postgresql.org/mailman/listinfo/slony1-general
>