oracle - can a timesten replication agent hold deadlock to itself? -
i experiencing strange issue, timesten subdaemon core dumped, , in analysing tterrors log, find stream of lock errors, replication agent trying obtain lock held itself(see pids in below log message), cause ? can see logs @ least repeated next 7 minutes , lead core dump, has been problem timesten/oracle ? cannot find known bugs , , not able reproduce problem well
under circumstances ,can replication agent lock self out ? , wouldnt release lock in case
15:59:23.89 warn: rep: 14037: collectordb:receiver.c(9880): tt6003: tt6003: lock request denied because of time-out details: tran 28.27845 (pid 14037) wants x lock on rowid bmufvuaaaaaachfk+g, table dbuser.customers. tran 7.327400504 (pid 14037) has in x (request x). holder sql () -- file "tindex.c", lineno 4429, procedure "sbtixnext()"
Comments
Post a Comment