Db2 Error Acquiring Partition Resources
sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Results 1 to 14 of 14 Thread: Failed to lock table and fix TCB Tweet Thread Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 09-11-13,04:32 #1 itsonlyme44 View Profile View Forum Posts Registered User Join Date Dec 2007 Posts 288 Unanswered: Failed to lock table and fix TCB Getting these errors every 15 minutes like clockwork (even with no activity against the database) can anyone shed any light? This is DB2 LUW on Windows V 9.7 Code: 2013-07-09-20.15.14.356000-240 I67462266H479 LEVEL: Warning PID : 4292 TID : 1804 PROC : db2syscs.exe INSTANCE: DB2 NODE : 000 DB : MYDB APPHDL : 0-5846 APPID: *LOCAL.DB2.130710001721 AUTHID : DB2 EDUID : 1804 EDUNAME: db2agent (MYDB) 0 FUNCTION: DB2 UDB, database utilities, sqluvtld_route_in, probe:839 DATA #1 :
LOADI NG CONCURRENTLY TO THE SAME TABLE WITHOUT PARTITIONING_DBPARTNUM z/os Fixes are available DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows DB2 Version 9.7 Fix Pack 9a for http://www.dbforums.com/showthread.php?1696318-Failed-to-lock-table-and-fix-TCB Linux, UNIX, and Windows DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows Subscribe You can track all active APARs for this component. APAR status Closed as program error. Error description When multiple load operations load data concurrently into the same table, some load might fail with the -2038 error on http://www.ibm.com/support/docview.wss?uid=swg1IC80823 a partitioning subagent if the database partitions are not specified by the PARTITIONING_DBPARTNUMS option. If the database partitions are specified by the PARTITIONING_DBPARTNUMS option and do not overlap, the issue can be avoided. The following is the failure that you may see. $ db2 "load from TAB01.del.001 of del insert into TAB01 ( ID, DATA ) indexing mode AUTOSELECT partitioned db config OUTPUT_DBPARTNUMS ( 1,2 )" $ db2 "load from TAB01.del.003 of del insert into TAB01 ( ID, DATA ) indexing mode AUTOSELECT partitioned db config OUTPUT_DBPARTNUMS ( 3,4 )" The former LOAD command completes as follows. Agent Type Node SQL Code Result ________________________________________________________________ ______________ LOAD 001 +00000000 Success. ________________________________________________________________ ______________ LOAD 002 +00000000 Success. ________________________________________________________________ ______________ PARTITION 002 +00000000 Success. ________________________________________________________________ ______________ PRE_PARTITION 001 +00000000 Success. ________________________________________________________________ ______________ RESULTS: 2 of 2 LOADs completed successfully. On the other hand, later one may fail as follows. Agent Type Node SQL Code Result ________________________________________________________________ ______________ PARTITION
TABLES WITH LOBS z/os Fixes are available DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows DB2 Version 9.7 Fix Pack 8 for Linux, http://www.ibm.com/support/docview.wss?uid=swg1IC78050 UNIX, and Windows DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows Subscribe You can track all active APARs for this component. APAR status Closed as program error. Error description This APAR is being used to improve problem diagnostics for a db2 error potential DB2 issue that is still at problem determination stage. AFTER LOAD LOB/LF DATA FAILURE, FOLLOWED BY LOAD TERMINATE, SUBSEQUENT LOAD MAY FAIL WITH SQLDXE_BADPAGE 1) Pre-requisites: - Recoverable database - Table with LOB/LF column - Failed LOAD command (INSERT/REPLACE) - Successful LOAD TERMINATE After LOAD FAILURE, followed by LOAD TERMINATE is done, some LOB pages may not have been completely cleaned up. Please note db2 error acquiring that table is fully accessible after TERMINATE. However, a subsequent LOAD against this table may fail with a bad LOB page error. You can identify that LOAD TERMINATE was run in the scenario with below example: (Failed LOAD): 2011-07-12-12.03.47.037585+540 I64449596A539 LEVEL: Error PID : 29032720 TID : 118291 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-31282 APPID: *LOCAL.db2inst1.110803015837 AUTHID : DB2INST1 EDUID : 118291 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0 DATA #1 : String, 113 bytes LOADID: 118291.2011-07-12-11.40.31.681591.0 (10;100) sqluv_rollback , 0, 93, Detected in file:sqluvutl.C, Line:937 2011-07-12-12.03.47.037731+540 I64450136A462 LEVEL: Severe PID : 29032720 TID : 118291 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-31282 APPID: *LOCAL.db2inst1.110803015837 AUTHID : DB2INST1 EDUID : 118291 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, database utilities, sqlu_register_table_load, probe:1132 MESSAGE : Load Error: Error loading partition. (LOAD TERMINATE): 2011-07-12-13.27.26.417998+540 I64672391A619 LEVEL: Warning PID : 29032720 TID : 113667 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-5149 APPID: *LOCAL.db2inst1.110803123533 AUTHID : DB2INST1 EDUID : 113667 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB,