Thu Oct 1 19:27:03 PDT 2009
- Previous message: [Slony1-general] Options for altering tables in one replication set with other replication sets live
- Next message: [Slony1-general] How does it work if has different sets on different nodes?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I am running Slony-I on 2 Windows 2003 Servers. How would I start an extra= slon process on Windows? Is this related to adding an engine for the serv= ice? = The log file for slony doesn't say anything about db2. But when I run slon= ik.exe <scriptName>. It produces the error '48: ERROR: syntax error at or n= ear cluster'. That is the line that says "cluster name =3D slony_dbTwo;". = To experiment, I commented out this line and then ran the slonik script an= d it gave me the same error but for the next line "node 3 admin conninfo=3D= 'host=3D192.168.112.4 dbname=3DdbTwo user=3Dpostgres password=3Dpostgres';"= . I guess this was expected. I then deleted everything from my script aft= er "cluster name =3D slony_dbTwo" and it ran ok. I will try running the se= cond half as a separate script. But it would be really beneficial to run t= hem in the same one. = LW . . . Lawrence > Date: Wed, 30 Sep 2009 08:29:16 -0400 > From: wmoran at potentialtech.com > To: lawrencew00 at hotmail.com > CC: slony1-general at lists.slony.info > Subject: Re: [Slony1-general] Multiple Databases > = > In response to Lawrence Wong <lawrencew00 at hotmail.com>: > = > > = > > Hi, > > I am trying to replicate two databases in a simple 1 master, 1 slave co= nfiguration. I was successful with one database but unsuccessful with 2. = I was wondering if anyone could point out my mistake in my slonik script tr= ying to replicate 2 databases. I have read that a simple way to go around = is to have the tables in the same schema but I would like to keep the datab= ases separate. Here is my slonik script: > = > Wow. Hotmail really mangled your email. Just ran everything together. > = > Looking at the config, I don't see anything obviously wrong. Here are > some guesses as to what might be causing you trouble and/or how to > debug further > 1) Did you start 2 slon processes on each server? You'll need a separate > slon for each cluster. > 2) Perhaps try splitting that config in two and submitting separately. I > don't know that submitting it all at once _won't_ work, but I've never > tried it. > 3) What's in slony's log files? > = > If I were a betting man, I'd put money that #1 is the problem. > = > I assume this is what the config is supposed to look like: > = > cluster name =3D slony_dbOne; > node 1 admin conninfo=3D'host=3D192.168.112.4 dbname=3Ddb user=3Dpostgres= password=3Dpostgres'; > node 2 admin conninfo=3D'host=3D192.168.112.5 dbname=3Ddb user=3Dpostgres= password=3Dpostgres'; > init cluster (id=3D1,comment=3D'node 1 dbOne'); > #CREATE SET > create set (id =3D 1, origin =3D 1, comment =3D 'tables'); > #SET ADD TABLE > set add table (set id=3D1, origin=3D1, id=3D1, fully qualified name =3D '= schema1.table2',comment=3D''); > set add table (set id=3D1, origin=3D1, id=3D2, fully qualified name =3D '= schema1.table2',comment=3D''); > #STORE NODE > store node ( id =3D 2, comment =3D 'node 2 dbOne' ); > #STORE PATH > store path ( server =3D 1, client =3D 2, conninfo =3D 'dbname=3Ddb host= =3D192.168.112.4 user=3Dpostgres password=3Dpostgres'); > store path ( server =3D 2, client =3D 1, conninfo =3D 'dbname=3Ddb host= =3D192.168.112.5 user=3Dpostgres password=3Dpostgres'); > #STORE LISTEN > store listen ( origin =3D 1, provider =3D 1, receiver =3D 2 ); > store listen ( origin =3D 2, provider =3D 2, receiver =3D 1 ); > = > cluster name =3D slony_dbTwo; > node 3 admin conninfo=3D'host=3D192.168.112.4 dbname=3DdbTwo user=3Dpostg= res password=3Dpostgres'; > node 4 admin conninfo=3D'host=3D192.168.112.5 dbname=3DdbTwo user=3Dpostg= res password=3Dpostgres'; > init cluster (id=3D3,comment=3D'node 1 dbTwo'); > #CREATE SET > create set (id =3D 2, origin =3D 3, comment =3D 'tables'); > #SET ADD TABLE > set add sequence (set id=3D2, origin=3D3, id=3D1, fully qualified name = =3D 'schema1.table1', comment=3D''); > #STORE NODE > store node ( id =3D 4, comment =3D 'node 2 dbTwo' ); > #STORE PATH > store path ( server =3D 3, client =3D 4, conninfo =3D 'dbname=3DdbTwo hos= t=3D192.168.112.4 user=3Dpostgres password=3Dpostgres'); > store path ( server =3D 4, client =3D 3, conninfo =3D 'dbname=3DdbTwo hos= t=3D192.168.112.5 user=3Dpostgres password=3Dpostgres'); > #STORE LISTEN > store listen ( origin =3D 3, provider =3D 3, receiver =3D 4 ); > store listen ( origin =3D 4, provider =3D 4, receiver =3D 3 ); > = > -- = > Bill Moran > http://www.potentialtech.com > http://people.collaborativefusion.com/~wmoran/ = _________________________________________________________________ We are your photos. Share us now with Windows Live Photos. http://go.microsoft.com/?linkid=3D9666047 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20091002/= 15d57242/attachment.htm
- Previous message: [Slony1-general] Options for altering tables in one replication set with other replication sets live
- Next message: [Slony1-general] How does it work if has different sets on different nodes?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list