ER Problem
Marco set up Enterprise Replication between two Linux servers; one failed with 'fatal server error (100)', error -310 on a syscdrs/syscdr:servdef query and 'Catalog Initialization Failed'. Madison Pruet asked for the start of the SQL statement in the online log, suspecting the view on sysmaster created during ER init, and said rebuilding the smi database could work around it; contact tech support. Unresolved.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Hi, Have an ER problem. I am seetting up replication between two linux servers. I have one setup and have defined the server for replication (no problems). The other does not want to play as nicely. It tells me: command failed -- fatal sever error (100) Log shows: from syscdrs a, outer syscdr:servdef b where a.servid = b.servid error: -310 'syscdr' database built successfully. CDR Initilization failed (Catalog Initialization Failed). CDR GC: operation updateCDRState failed (error 62). CDR Initilization failed (CDRStaeSub). CDR GC: operation updateCDRState failed (error 62). Any ideas? Thanks. Marco Sent via Deja.com http://www.deja.com/ Before you buy.
I'd really like to see the first part of the sql statement in the online message log file. There is a view that is created against sysmaster as part of the ER initialization. I'm betting that this is where the problem is occuring. If that is the case, then you should be able to rebuild the smi database to get arround the problem. Contact tech support to get more information on the procedure necessary to do that. mdelerme@my-deja.com wrote: > Hi, > > Have an ER problem. I am seetting up replication between two linux > servers. I have one setup and have defined the server for replication > (no problems). The other does not want to play as nicely. It tells me: > > command failed -- fatal sever error (100) > > Log shows: > > from syscdrs a, outer syscdr:servdef b > where a.servid = b.servid error: -310 > 'syscdr' database built successfully. > CDR Initilization failed (Catalog Initialization Failed). > CDR GC: operation updateCDRState failed (error 62). > CDR Initilization failed (CDRStaeSub). > CDR GC: operation updateCDRState failed (error 62). > > Any ideas? > > Thanks. > > Marco > > Sent via Deja.com http://www.deja.com/ > Before you buy. -- Madison Pruet =========================================== Enterprise Replication Product Developement Dallas, Texas Informix Software ===========================================
I'd really like to see the first part of the sql statement in the online message log file. There is a view that is created against sysmaster as part of the ER initialization. I'm betting that this is where the problem is occuring. If that is the case, then you should be able to rebuild the smi database to get arround the problem. Contact tech support to get more information on the procedure necessary to do that. mdelerme@my-deja.com wrote: > Hi, > > Have an ER problem. I am seetting up replication between two linux > servers. I have one setup and have defined the server for replication > (no problems). The other does not want to play as nicely. It tells me: > > command failed -- fatal sever error (100) > > Log shows: > > from syscdrs a, outer syscdr:servdef b > where a.servid = b.servid error: -310 > 'syscdr' database built successfully. > CDR Initilization failed (Catalog Initialization Failed). > CDR GC: operation updateCDRState failed (error 62). > CDR Initilization failed (CDRStaeSub). > CDR GC: operation updateCDRState failed (error 62). > > Any ideas? > > Thanks. > > Marco > > Sent via Deja.com http://www.deja.com/ > Before you buy. -- Madison Pruet =========================================== Enterprise Replication Product Developement Dallas, Texas Informix Software ===========================================
I'd really like to see the first part of the sql statement in the online message log file. There is a view that is created against sysmaster as part of the ER initialization. I'm betting that this is where the problem is occuring. If that is the case, then you should be able to rebuild the smi database to get arround the problem. Contact tech support to get more information on the procedure necessary to do that. mdelerme@my-deja.com wrote: > Hi, > > Have an ER problem. I am seetting up replication between two linux > servers. I have one setup and have defined the server for replication > (no problems). The other does not want to play as nicely. It tells me: > > command failed -- fatal sever error (100) > > Log shows: > > from syscdrs a, outer syscdr:servdef b > where a.servid = b.servid error: -310 > 'syscdr' database built successfully. > CDR Initilization failed (Catalog Initialization Failed). > CDR GC: operation updateCDRState failed (error 62). > CDR Initilization failed (CDRStaeSub). > CDR GC: operation updateCDRState failed (error 62). > > Any ideas? > > Thanks. > > Marco > > Sent via Deja.com http://www.deja.com/ > Before you buy. -- Madison Pruet =========================================== Enterprise Replication Product Developement Dallas, Texas Informix Software ===========================================
I'd really like to see the first part of the sql statement in the online message log file. There is a view that is created against sysmaster as part of the ER initialization. I'm betting that this is where the problem is occuring. If that is the case, then you should be able to rebuild the smi database to get arround the problem. Contact tech support to get more information on the procedure necessary to do that. mdelerme@my-deja.com wrote: > Hi, > > Have an ER problem. I am seetting up replication between two linux > servers. I have one setup and have defined the server for replication > (no problems). The other does not want to play as nicely. It tells me: > > command failed -- fatal sever error (100) > > Log shows: > > from syscdrs a, outer syscdr:servdef b > where a.servid = b.servid error: -310 > 'syscdr' database built successfully. > CDR Initilization failed (Catalog Initialization Failed). > CDR GC: operation updateCDRState failed (error 62). > CDR Initilization failed (CDRStaeSub). > CDR GC: operation updateCDRState failed (error 62). > > Any ideas? > > Thanks. > > Marco > > Sent via Deja.com http://www.deja.com/ > Before you buy. -- Madison Pruet =========================================== Enterprise Replication Product Developement Dallas, Texas Informix Software ===========================================
I'd really like to see the first part of the sql statement in the online message log file. There is a view that is created against sysmaster as part of the ER initialization. I'm betting that this is where the problem is occuring. If that is the case, then you should be able to rebuild the smi database to get arround the problem. Contact tech support to get more information on the procedure necessary to do that. mdelerme@my-deja.com wrote: > Hi, > > Have an ER problem. I am seetting up replication between two linux > servers. I have one setup and have defined the server for replication > (no problems). The other does not want to play as nicely. It tells me: > > command failed -- fatal sever error (100) > > Log shows: > > from syscdrs a, outer syscdr:servdef b > where a.servid = b.servid error: -310 > 'syscdr' database built successfully. > CDR Initilization failed (Catalog Initialization Failed). > CDR GC: operation updateCDRState failed (error 62). > CDR Initilization failed (CDRStaeSub). > CDR GC: operation updateCDRState failed (error 62). > > Any ideas? > > Thanks. > > Marco > > Sent via Deja.com http://www.deja.com/ > Before you buy. -- Madison Pruet =========================================== Enterprise Replication Product Developement Dallas, Texas Informix Software ===========================================