DB2 FOR LUW / DB2FORLUW / 970 - DB2

If AIC is interrupted with user user interrupt(-952 in SQLCA), 
its status is set to ABP_TASK_PRO_ERROR state.  You will see the 
following entries in the db2diag.log: 
 
************************************************************ 
 
FUNCTION: DB2 UDB, catalog services, 
sqlrlAlterDetachCatalogChange, 
probe:100 
RETCODE : ZRC=0x8012006D=-2146303891=SQLR_CA_BUILT 
          "SQLCA has already been built" 
 
 
    <SNIP> 
 
 
FUNCTION: DB2 UDB, AIC, aicDelDPartID, probe:150 
 
MESSAGE : ZRC=0x8012006D=-2146303891=SQLR_CA_BUILT 
          "SQLCA has already been built" 
CALLED  : DB2 UDB, catalog services, sqlrlCleanDPartID 
RETCODE : ZRC=0x82A90067=-2102853529=ABP_TASK_PRO_ERROR 
          "Task processor encountered an error" 
 
 
    <SNIP> 
 
FUNCTION: DB2 UDB, ABP, 
ABPDispatcher::updateAssignedTaskProCont, 
probe:100 
MESSAGE : 
ADM13500E  An agent executing an asynchronous background task 
processor encountered an unrecoverable error. The task processor 
has been suspended and diagnostic information was written to the 
db2diag.log. Contact IBM Support for assistance. The task 
processor context is "0x07800002493DA4A0". The task processor 
description is "Remove Partition ID from Catalog". 
 
************************************************************ 
 
DB2 should rather put AIC in suspended state ( 
ABP_SUSPEND_TASK_PRO).  When AIC is put in suspended state, it 
will retry the task every 5 minutes until it succeed.

If AIC is interrupted with user user interrupt(-952 in SQLCA), 
 
its status is set to ABP_TASK_PRO_ERROR state.  You will see the 
following entries in the db2diag.log: 
 
************************************************************ 
 
FUNCTION: DB2 UDB, catalog services, 
sqlrlAlterDetachCatalogChange, 
probe:100 
RETCODE : ZRC=0x8012006D=-2146303891=SQLR_CA_BUILT 
          "SQLCA has already been built" 
 
 
    <SNIP> 
 
 
FUNCTION: DB2 UDB, AIC, aicDelDPartID, probe:150 
 
MESSAGE : ZRC=0x8012006D=-2146303891=SQLR_CA_BUILT 
          "SQLCA has already been built" 
CALLED  : DB2 UDB, catalog services, sqlrlCleanDPartID 
RETCODE : ZRC=0x82A90067=-2102853529=ABP_TASK_PRO_ERROR 
          "Task processor encountered an error" 
 
 
    <SNIP> 
 
FUNCTION: DB2 UDB, ABP, 
ABPDispatcher::updateAssignedTaskProCont, 
probe:100 
MESSAGE : 
ADM13500E  An agent executing an asynchronous background task 
processor encountered an unrecoverable error. The task processor 
has been suspended and diagnostic information was written to the 
db2diag.log. Contact IBM Support for assistance. The task 
processor context is "0x07800002493DA4A0". The task processor 
description is "Remove Partition ID from Catalog". 
 
************************************************************ 
 
DB2 should rather put AIC in suspended state ( 
ABP_SUSPEND_TASK_PRO).  When AIC is put in suspended state, it 
will retry the task every 5 minutes until it succeed.

You can manually resume the AIC process left in such error 
state as following: 
 
 
db2pd -db <DB_NAME> -abp resume <CONTEXT_ADDRESS> 
 
Where, 
 
<DB_NAME>         = name of the database 
<CONTEXT_ADDRESS> = This context address can be found in the 
                    db2diag.log entry as I have shown in the 
                    error description. 
 
For example, 
 
db2pd -db SAMPLE -abp resume 0x07800002493DA4A0

DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 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 Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Defect   => wsdbu00624192 
Fixed in => v9.7 + FP3 
Module   => engn_ABP

You can manually resume the AIC process left in such error 
state as following: 
 
 
db2pd -db <DB_NAME> -abp resume <CONTEXT_ADDRESS> 
 
Where, 
 
<DB_NAME>         = name of the database 
<CONTEXT_ADDRESS> = This context address can be found in the 
                    db2diag.log entry as I have shown in the 
                    error description. 
 
For example, 
 
db2pd -db SAMPLE -abp resume 0x07800002493DA4A0

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

11.02.2010
24.09.2010
24.09.2010

9.7.