HOWTO : Understand TimesTen Replication And Bulk Delete Transaction Limitations
Last updated on SEPTEMBER 23, 2016
Applies to:TimesTen Data Server - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Bulk delete transaction.
***Checked for relevance on 26-Sep-2013***
Running a bulk delete transaction along replication may incur numerous lock time out messages
and could severely impact a system.
The large single transaction deleting many hundreds of thousands of rows will see these symptoms
in the log files :
17:18:24.23 Warn: REP: 25569: RMS_SSR_PRIMARY:rephold.c(96): TT16041: Failed to compute a new replication hold LSN in rephold()
17:18:24.24 Err : REP: 25569: RMS_SSR_PRIMARY:meta.c(4874): TT6003: TT6003: Lock request denied because of time-out
Details: Tran 4.269768 (pid 25569) wants X lock on rowid 0x00000000001d6d30, table TTREP.REPPEERS. But tran 2.880 (pid 25569) has it in U (request was U). Holder SQL () -- file "hindex.c", lineno 2009, procedure "sbHixGetCursorFirstFetchLocks()"
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms