|
Problem IC88612
|
Status: Geschlossen |
IN A DB2 MULTI-PARTITION (DPF) ENVIRONMENT, SQL0960C AND TDA FIL E ACCUMULATION CAN RESULT WHEN CREATING GLOBAL TEMPORARY TABLES. |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problembeschreibung: |
In a DB2 MULTI-PARTITION (DPF) configuration (where the
applications are connected at non-catalog partitions), an
interrupt detected during connection termination can result in
the following probes to the db2diag.log:
2012-06-25-07.35.23.965277+540 I7405212A1209 LEVEL: Warning
PID : 127116 TID : 26243 PROC : db2sysc
3
INSTANCE: db2inst1 NODE : 003 DB : SAMPLE
APPHDL : 3-613 APPID:
12.30.47.77.56095.120624223508
AUTHID : DB2INST1
EDUID : 26243 EDUNAME: db2agent (SAMPLE) 3
FUNCTION: DB2 UDB, base sys utilities,
sqeAgent::AgentBreathingPoint, probe:16
CALLSTCK:
[0] 0x0900000006E5B7F8 pdLog + 0xF0
[1] 0x0900000004B0476C pdLog@glue40E + 0x94
[2] 0x0900000003B47F90 AgentBreathingPoint__8sqeAgentFi + 0x2C
[3] 0x09000000070775E8
AgentBreathingPoint__8sqeAgentFi@glue198 + 0x78
[4] 0x0900000003EA37EC
sqlrkrpc_nl__FP8sqlrr_cbiN22PsP15SQLR_RPCMESSAGEP13SQLO_MEM_POOL
P18SQLR_RPC_REPLY_HDRPbPl + 0x178
[5] 0x0900000003F9C8AC
sqlrl_userTempReleaseFIDTID__FP8sqlrr_cbiT2P21sqlrl_userTempDrop
pedT2P16sqlr_usertemp_cb + 0x774
[6] 0x09000000049E2DE8
sqlrl_userTempCleanup__FP8sqlrr_cbiP16sqlr_usertemp_cb + 0x64C
[7] 0x09000000035E755C sqlrr_appl_term__FP8sqeAgentiP5sqlca +
0x79C
[8] 0x0900000006DE4350
AppStopUsing__14sqeApplicationFP8sqeAgentUcP5sqlca + 0x650
[9] 0x0900000006DFCF5C sqlesrspWrp__FP14db2UCinterface + 0xEC
2012-06-25-07.35.23.969501+540 I7406422A569 LEVEL: Error
PID : 127116 TID : 26243 PROC : db2sysc
3
INSTANCE: db2inst1 NODE : 003 DB : SAMPLE
APPHDL : 3-613 APPID:
12.30.47.77.56095.120624223508
AUTHID : DB2INST1
EDUID : 26243 EDUNAME: db2agent (SAMPLE) 3
FUNCTION: DB2 UDB, catalog services,
sqlrl_userTempReleaseFIDTID, probe:20
RETCODE : ZRC=0x80120003=-2146303997=SQLR_INTRP
"Statement interrupt, detected at RDS"
DIA8003C The interrupt has been received.
2012-06-25-07.35.23.978135+540 I7406992A563 LEVEL: Error
PID : 127116 TID : 26243 PROC : db2sysc
3
INSTANCE: db2inst1 NODE : 003 DB : SAMPLE
APPHDL : 3-613 APPID:
12.30.47.77.56095.120624223508
AUTHID : DB2INST1
EDUID : 26243 EDUNAME: db2agent (SAMPLE) 3
FUNCTION: DB2 UDB, catalog services, sqlrl_userTempCleanup,
probe:90
RETCODE : ZRC=0x80120003=-2146303997=SQLR_INTRP
"Statement interrupt, detected at RDS"
DIA8003C The interrupt has been received.
2012-06-25-07.35.23.978289+540 I7407556A560 LEVEL: Error
PID : 127116 TID : 26243 PROC : db2sysc
3
INSTANCE: db2inst1 NODE : 003 DB : SAMPLE
APPHDL : 3-613 APPID:
12.30.47.77.56095.120624223508
AUTHID : DB2INST1
EDUID : 26243 EDUNAME: db2agent (SAMPLE) 3
FUNCTION: DB2 UDB, relation data serv, sqlrr_appl_term,
probe:850
RETCODE : ZRC=0x80120003=-2146303997=SQLR_INTRP
"Statement interrupt, detected at RDS"
DIA8003C The interrupt has been received.
This would indicate that loss of the file token(s) that were in
the process of being released during application termination
processing. This loss of file tokens (if the problem recurs
enough) can lead to a subsequent exhaustion of file tokens for a
user temporary tablespace resulting in SQL0960N errors
2012-06-24-23.59.05.787521+540 I1838A537 LEVEL: Error
PID : 439676 TID : 17308 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 3-55406 APPID:
12.30.47.77.44519.120826022356
AUTHID : DB2INST1
EDUID : 17308 EDUNAME: db2agntp (SAMPLE) 0
FUNCTION: DB2 UDB, catalog services, sqlrl_userTempGetInfo,
probe:320
RETCODE : ZRC=0x85020007=-2063466489=SQLB_NTOK "no file token
available"
DIA8307C Maximum file tokens were used.
In addition the user temporary tablespace may see an
accumulation of TDA files due to the loss of the FID (resulting
in a lack of re-use of the files). |
| Problem-Zusammenfassung: |
In a DB2 MULTI-PARTITION (DPF) configuration (where the
applications are connected at non-catalog partitions), an
interrupt detected during connection termination can result in
the following probes to the db2diag.log:
2012-06-25-07.35.23.965277+540 I7405212A1209 LEVEL: Warning
PID : 127116 TID : 26243 PROC : db2sysc
3
INSTANCE: db2inst1 NODE : 003 DB : SAMPLE
APPHDL : 3-613 APPID:
12.30.47.77.56095.120624223508
AUTHID : DB2INST1
EDUID : 26243 EDUNAME: db2agent (SAMPLE) 3
FUNCTION: DB2 UDB, base sys utilities,
sqeAgent::AgentBreathingPoint, probe:16
CALLSTCK:
[0] 0x0900000006E5B7F8 pdLog + 0xF0
[1] 0x0900000004B0476C pdLog@glue40E + 0x94
[2] 0x0900000003B47F90 AgentBreathingPoint__8sqeAgentFi + 0x2C
[3] 0x09000000070775E8
AgentBreathingPoint__8sqeAgentFi@glue198 + 0x78
[4] 0x0900000003EA37EC
sqlrkrpc_nl__FP8sqlrr_cbiN22PsP15SQLR_RPCMESSAGEP13SQLO_MEM_POOL
P18SQLR_RPC_REPLY_HDRPbPl + 0x178
[5] 0x0900000003F9C8AC
sqlrl_userTempReleaseFIDTID__FP8sqlrr_cbiT2P21sqlrl_userTempDrop
pedT2P16sqlr_usertemp_cb + 0x774
[6] 0x09000000049E2DE8
sqlrl_userTempCleanup__FP8sqlrr_cbiP16sqlr_usertemp_cb + 0x64C
[7] 0x09000000035E755C sqlrr_appl_term__FP8sqeAgentiP5sqlca +
0x79C
[8] 0x0900000006DE4350
AppStopUsing__14sqeApplicationFP8sqeAgentUcP5sqlca + 0x650
[9] 0x0900000006DFCF5C sqlesrspWrp__FP14db2UCinterface + 0xEC
2012-06-25-07.35.23.969501+540 I7406422A569 LEVEL: Error
PID : 127116 TID : 26243 PROC : db2sysc
3
INSTANCE: db2inst1 NODE : 003 DB : SAMPLE
APPHDL : 3-613 APPID:
12.30.47.77.56095.120624223508
AUTHID : DB2INST1
EDUID : 26243 EDUNAME: db2agent (SAMPLE) 3
FUNCTION: DB2 UDB, catalog services,
sqlrl_userTempReleaseFIDTID, probe:20
RETCODE : ZRC=0x80120003=-2146303997=SQLR_INTRP
"Statement interrupt, detected at RDS"
DIA8003C The interrupt has been received.
2012-06-25-07.35.23.978135+540 I7406992A563 LEVEL: Error
PID : 127116 TID : 26243 PROC : db2sysc
3
INSTANCE: db2inst1 NODE : 003 DB : SAMPLE
APPHDL : 3-613 APPID:
12.30.47.77.56095.120624223508
AUTHID : DB2INST1
EDUID : 26243 EDUNAME: db2agent (SAMPLE) 3
FUNCTION: DB2 UDB, catalog services, sqlrl_userTempCleanup,
probe:90
RETCODE : ZRC=0x80120003=-2146303997=SQLR_INTRP
"Statement interrupt, detected at RDS"
DIA8003C The interrupt has been received.
2012-06-25-07.35.23.978289+540 I7407556A560 LEVEL: Error
PID : 127116 TID : 26243 PROC : db2sysc
3
INSTANCE: db2inst1 NODE : 003 DB : SAMPLE
APPHDL : 3-613 APPID:
12.30.47.77.56095.120624223508
AUTHID : DB2INST1
EDUID : 26243 EDUNAME: db2agent (SAMPLE) 3
FUNCTION: DB2 UDB, relation data serv, sqlrr_appl_term,
probe:850
RETCODE : ZRC=0x80120003=-2146303997=SQLR_INTRP
"Statement interrupt, detected at RDS"
DIA8003C The interrupt has been received.
This would indicate that loss of the file token(s) that were in
the process of being released during application termination
processing. This loss of file tokens (if the problem recurs
enough) can lead to a subsequent exhaustion of file tokens for a
user temporary tablespace resulting in SQL0960N errors
2012-06-24-23.59.05.787521+540 I1838A537 LEVEL: Error
PID : 439676 TID : 17308 PROC : db2sysc
0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
APPHDL : 3-55406 APPID:
12.30.47.77.44519.120826022356
AUTHID : DB2INST1
EDUID : 17308 EDUNAME: db2agntp (SAMPLE) 0
FUNCTION: DB2 UDB, catalog services, sqlrl_userTempGetInfo,
probe:320
RETCODE : ZRC=0x85020007=-2063466489=SQLB_NTOK "no file token
available"
DIA8307C Maximum file tokens were used.
In addition the user temporary tablespace may see an
accumulation of TDA files due to the loss of the FID (resulting
in a lack of re-use of the files).
First fixed in DB2 Version 10.1 Fix Pack 2. |
| Local-Fix: |
Ensure connections are terminated with proper disconnect/connect
resets or are forced off to avoid this interrupt detection.
Restarting the database reclaims the lost file tokens as well -
so a periodic db restart can keep this from causing application
errors. |
| verfügbare FixPacks: |
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
|
| Lösung |
|
| Workaround |
Ensure connections are terminated with proper disconnect/connect
resets or are forced off to avoid this interrupt detection.
Restarting the database reclaims the lost file tokens as well -
so a periodic db restart can keep this from causing application
errors. |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 27.11.2012
19.04.2013
19.04.2013 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.1.0.2
|
 |
| 10.5.0.2
|
|
