|
Problem IC84509
|
Status: Closed |
AIC IS NOT PUT INTO SUSPENDED STATE AFTER RECEIVING -954 ERROR. IF AIC IS NOT IN SUSPENDED STATE, IT IS NOT INVOKED FOR RETRY. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
If AIC is receives SQL0954N (-954 in SQLCA), its status is set
to ABP_TASK_PRO_ERROR state. You will see the following entries
in the db2diag.log:
2011-12-10-10.54.47.750364+000 I12180602E498 LEVEL: Error
PID : 853 TID : 46919887874368PROC :
db2sysc 1
INSTANCE: bculinux NODE : 001 DB :
BDWLP01
APPHDL : 1-8926 APPID: *N1.DB2.111210105449
AUTHID : BCULINUX
EDUID : 106822 EDUNAME: db2taskp (BCUDB) 1
FUNCTION: DB2 UDB, catalog services, sqlrlCatalogScan::open,
probe:70
RETCODE : ZRC=0x8012006D=-2146303891=SQLR_CA_BUILT
"SQLCA has already been built"
...
2011-12-10-10.54.48.089042+000 I12220522E5553 LEVEL: Error
PID : 853 TID : 46918797355328PROC :
db2sysc 1
INSTANCE: bculinux NODE : 001 DB :
BDWLP01
APPHDL : 1-8967 APPID: *N1.DB2.111210105530
AUTHID : BCULINUX
EDUID : 113385 EDUNAME: db2taskp (BCUDB) 1
FUNCTION: DB2 UDB, AIC, aicTaskProcessor, probe:2332
MESSAGE : ZRC=0x8012006D=-2146303891=SQLR_CA_BUILT
"SQLCA has already been built"
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -954 sqlerrml: 0
sqlerrmc:
sqlerrp : SQLESBCN
sqlerrd : (1) 0x8B0F0001 (2) 0x00000001 (3)
0x00000000
(4) 0x00000000 (5) 0x00000000 (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
DATA #2 : AIC_CB, PD_AIC_TYPE_CB, 976 bytes
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. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All Platforms *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to v10.1 Fixpack 1 or Higher *
**************************************************************** |
| Local Fix: |
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. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First Fixed in v10.1 Fixpack 1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.06.2012
05.11.2012
05.11.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
