If a Db2 Change Selector repeatedly stops because of a timeout, you may see a message like the following:
Error Code -913
Message {DB2 FOR OS/390}{ODBC DRIVER}{DSN07011}
DSNT408I SQLCODE = -913, ERROR: UNSUCCESSFUL EXECUTION CAUSED BY DEADLOCK OR
TIMEOUT. REASON CODE 00C9008E, TYPE OF RESOURCE 00000302, AND RESOURCE
NAME DRPPREP1.RPRCRQ .X'000671'
DSNT418I SQLSTATE = 57033 SQLSTATE RETURN CODE
DSNT415I SQLERRP = DSNXRRC SQL PROCEDURE DETECTING ERROR
DSNT416I SQLERRD = 101 13172746 13172878 13817319 -470675453 536870912
SQL DIAGNOSTIC INFORMATION
DSNT416I SQLERRD = X'00000065' X'00C9000A' X'00C9008E' X'00D2D5E7'
X'E3F21003' X'20000000' SQL DIAGNOSTIC INFORMATION
ERRLOC=1:13:2 Change the lock level the lock level to explicit row level locking by issuing the following ALTER statement:
alter tablespace <rp_database>.RPRCRQ locksize row lockmax 0;
commit work;