|
Problem IC67522
|
Status: Closed |
-901 OCCURS WHEN AN APPLICATION COMPILING PL/SQL PROCEDURE IS FORCED OFF, CAUSING DATABASE TO BE MARKED BAD |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
For a database running with the PL/SQL compilation compatability
feature (DB2_COMPATABILITY_VECTOR=0x800), if the application is
forced off when it is compiling a PL/SQL create procedure
statement, the DB2 LUW server may report a -901 sqlcode with the
following text:
"got_lock FALSE before hold processing"
A db2diag.log probe like the following would result in such a
case:
2010-03-17-02.31.02.037819-240 I4132847A861 LEVEL: Severe
PID : 901312 TID : 12700 PROC : db2sysc
0
INSTANCE: svtdbm5 NODE : 000 DB : PROTEUS
APPHDL : 0-1976 APPID: *N0.svtdbm5.100317063035
AUTHID : SVTDBM5
EDUID : 12700 EDUNAME: db2agent (PROTEUS) 0
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc,
probe:300
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -901 sqlerrml: 37
sqlerrmc: got_lock FALSE before hold processing
sqlerrp : SQLRA133
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3)
0x00000000
(4) 0x00000000 (5) 0xFFFFFF38 (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
and the database will be marked bad requiring the database to be
restarted |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2_COMPATABILITY_VECTOR must include 0x800 (or be equal to *
* ORA) to be impacted *
****************************************************************
* PROBLEM DESCRIPTION: *
* -901 and database marked bad during a forced application *
* while executing a create of a PL/SQL procedure *
****************************************************************
* RECOMMENDATION: *
* move to DB2 for LUW, Version 9.7, fixpack 2 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows
|
| Solution |
Fixed in DB2 for LUW, Version 9.7 fixpack 2 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC67524
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 29.03.2010
26.04.2010
26.04.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
