Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

ER error

21 views
Skip to first unread message

Laurie Gustin

unread,
May 14, 2013, 6:03:11 PM5/14/13
to inform...@iiug.org
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  :)

FRANK

unread,
May 15, 2013, 10:46:43 AM5/15/13
to Laurie Gustin, inform...@iiug.org
Laurie,
 
What is your IDS version?
 
Are  outputs of cdr list server   all the same   in all replication  nodes?
 
Thanks,
Frank
 


_______________________________________________
Informix-list mailing list
Inform...@iiug.org
http://www.iiug.org/mailman/listinfo/informix-list


Laurie Gustin

unread,
May 15, 2013, 10:59:25 AM5/15/13
to FRANK, inform...@iiug.org
IDS 11.70 FC7

yes - output for cdr list server is the same.. and shows all servers connected

FRANK

unread,
May 15, 2013, 1:37:23 PM5/15/13
to Laurie Gustin, inform...@iiug.org
Another option is cdr delete server.... to rebuild   the ER. It might cleanup the leftover
Frank

Laurie Gustin

unread,
May 15, 2013, 1:48:49 PM5/15/13
to FRANK, inform...@iiug.org
I found the problem... there was a trigger that accessed data on a third server - that's where the connection problem was.  :(

Thanks!
0 new messages