Tue Aug 4 02:56:54 PDT 2009
- Previous message: [Slony1-general] Windows Event Log Error
- Next message: [Slony1-general] Error - table id 1 has already been assigned
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi, I have cross checked the table ids in my replication set. Each of the 8 tables in my replication set has unique ids. But still I am getting the same error when I start the cluster. 2009-08-04 10:45:53 GMT Daylight Time DEBUG1 copy_set 1 2009-08-04 10:45:53 GMT Daylight Time DEBUG4 version for "host=vali port=5432 dbname=nlp user=postgres password= " is 80307 2009-08-04 10:45:53 GMT Daylight Time DEBUG1 remoteWorkerThread_1: connected to provider DB 2009-08-04 10:45:53 GMT Daylight Time DEBUG2 remoteWorkerThread_1: prepare to copy table "nlp_schema"."authority" 2009-08-04 10:45:53 GMT Daylight Time DEBUG3 remoteWorkerThread_1: table "nlp_schema"."authority" does not require Slony-I serial key 2009-08-04 10:45:53 GMT Daylight Time DEBUG2 remoteWorkerThread_1: prepare to copy table "nlp_schema"."blpu" 2009-08-04 10:45:53 GMT Daylight Time DEBUG3 remoteWorkerThread_1: table "nlp_schema"."blpu" does not require Slony-I serial key 2009-08-04 10:45:53 GMT Daylight Time DEBUG2 remoteWorkerThread_1: prepare to copy table "nlp_schema"."change_log" 2009-08-04 10:45:53 GMT Daylight Time DEBUG3 remoteWorkerThread_1: table "nlp_schema"."change_log" does not require Slony-I serial key 2009-08-04 10:45:53 GMT Daylight Time DEBUG2 remoteWorkerThread_1: prepare to copy table "nlp_schema"."lpi" 2009-08-04 10:45:53 GMT Daylight Time DEBUG3 remoteWorkerThread_1: table "nlp_schema"."lpi" does not require Slony-I serial key 2009-08-04 10:45:53 GMT Daylight Time DEBUG2 remoteWorkerThread_1: prepare to copy table "nlp_schema"."street" 2009-08-04 10:45:53 GMT Daylight Time DEBUG3 remoteWorkerThread_1: table "nlp_schema"."street" does not require Slony-I serial key 2009-08-04 10:45:53 GMT Daylight Time DEBUG2 remoteWorkerThread_1: prepare to copy table "nlp_schema"."xml_property" 2009-08-04 10:45:53 GMT Daylight Time DEBUG3 remoteWorkerThread_1: table "nlp_schema"."xml_property" does not require Slony-I serial key 2009-08-04 10:45:53 GMT Daylight Time DEBUG2 remoteWorkerThread_1: prepare to copy table "nlp_schema"."xml_street" 2009-08-04 10:45:53 GMT Daylight Time DEBUG3 remoteWorkerThread_1: table "nlp_schema"."xml_street" does not require Slony-I serial key 2009-08-04 10:45:53 GMT Daylight Time DEBUG2 remoteWorkerThread_1: prepare to copy table "nlp_schema"."xref" 2009-08-04 10:45:53 GMT Daylight Time DEBUG3 remoteWorkerThread_1: table "nlp_schema"."xref" does not require Slony-I serial key 2009-08-04 10:45:53 GMT Daylight Time DEBUG2 remoteWorkerThread_1: all tables for set 1 found on subscriber 2009-08-04 10:45:53 GMT Daylight Time DEBUG2 remoteWorkerThread_1: copy table "nlp_schema"."authority" 2009-08-04 10:45:53 GMT Daylight Time DEBUG3 remoteWorkerThread_1: table "nlp_schema"."authority" does not require Slony-I serial key 2009-08-04 10:45:53 GMT Daylight Time ERROR remoteWorkerThread_1: "select "_M_Cluster".setAddTable_int(1, 1, '"nlp_schema"."authority"', 'authority_pkey', ''); " PGRES_FATAL_ERROR ERROR: Slony-I: setAddTable_int: table id 1 has already been assigned! The procedure I followed is -- [Postgres 8.3.7 , Slony - 1.2.16, pgAdminIII, Windows VISTA.] 1) Created master and slave db with the same schema and same tables in each. Only the master tables were loaded with data. 2) Created the master.conf and slave.conf. Registered Slony-I service and added the 2 engines to it. 3) Created M_Cluster in master db and joined it in the slave. 4) Set the path in master and slave clusters. 5) Created one replication set in master db and added 8 tables to it with 8 unique ids for each table. 6) Started the Slony-I service or Started the slon cluster with the command slon M_Cluster "host=XXX port=5432 dbname=nlp_slave1 user=postgres password=xxx" Regards, Don -----Original Message----- From: Peter Geoghegan [mailto:peter.geoghegan86 at gmail.com] Sent: 04 August 2009 09:52 To: Don Sasikumar; slony1-general at lists.slony.info Subject: Re: [Slony1-general] Windows Event Log Error You've already assigned a table as table 1 of your set. Each set's table must have a unique id. If you would actually include relevant details like the events leading up to you getting this error message ( are you using PgAdminIII or writing a slonik script? What does your slonik script consist of?) we might be able to help you. Regards, Peter Geoghegan Intelligent Addressing Ltd. Registered Office: 1 Adam Street, London WC2N 6DD Reg. in England No.3863861 VAT No.GB 802258946 This message has been scanned for viruses by BlackSpider MailControl - www.blackspider.com
- Previous message: [Slony1-general] Windows Event Log Error
- Next message: [Slony1-general] Error - table id 1 has already been assigned
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list