Re: ER error

Another option is cdr delete server.... to rebuild the ER. It might cleanup the leftover Frank On Wed, May 15, 2013 at 10:59 AM, Laurie Gustin <lgustin@utah.gov> wrote: > IDS 11.70 FC7 > > yes - output for cdr list server is the same.. and shows all servers > connected > > > On Wed, May 15, 2013 at 8:46 AM, FRANK <yunyaoqu@gmail.com> wrote: > >> Laurie, >> >> What is your IDS version? >> >> Are outputs of cdr list server all the same in all replication >> nodes? >> >> Thanks, >> Frank >> >> >> >> On Tue, May 14, 2013 at 6:03 PM, Laurie Gustin <lgustin@utah.gov> wrote: >> >>> Im wondering if anyone has seen this error? >>> >>> 15:37:07 CDR CDRD_217: transaction aborted (One or more rows in a>>> transaction defined with tx scope were rejected) with sql error 908 isam >>> error 0. >>> >>> The 908 would indicate that the servers were not able to connect... but >>> then why would I get the error on the receiving server? some data is still >>> going back and forth but I am unable to completely sync up the data. >>> >>> When I do cdr list server (or cdr view servers) it shows all servers >>> connected >>> >>> I did cdr stop and cdr start to try to 'jumpstart' things... and get >>> this error on start >>> >>> 15:54:57 CDR GC: operation database syscdr exclusive failed (error >>> -154).>>> it tries 5 times... then doesnt say anything more >>> >>> >>> I am trying to sync again now - after the cdr stop/start. My next course >>> of action is to bounce the whole engine. But I dont really want to do that. >>> >>> Any help is appreciated. >>> >>> Laurie :) >>> >>> _______________________________________________ >>> Informix-list mailing list >>> Informix-list@iiug.org >>> http://www.iiug.org/mailman/listinfo/informix-list >>> >>> >> >