|
Problem IT21171
|
Status: Closed |
CRASH RECOVERY FAILED DUE TO MISSING OF ROR FILE
|
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
Crash Recovery may fail due to missing of ROR file, DB2 may get
panic due to this issue.
db2diag.log:
2017-06-12-11.47.50.713722+480 I66790A1239 LEVEL:
Severe
PID : 3932642 TID : 29043 PROC :
db2sysc 4
INSTANCE: qhbiinst NODE : 004 DB :
QHBIDB
APPHDL : 0-55 APPID:
135.191.27.160.59354.170612034541
AUTHID : IPD HOSTNAME: bdwy2
EDUID : 29043 EDUNAME: db2redow (QHBIDB) 4
FUNCTION: DB2 UDB, Common Trace API, sqlbfix, probe:143
DATA #1 : String, 63 bytes
Error: sqlbSetupObjDesc, unable to get the SQLB_POOL_CB for obj
DATA #2 : Hexdump, 4 bytes
Object not dumped: Address: 0x0000000000000088 Size: 4 Reason:
Possible offset from NULL pointer
DATA #3 : Hexdump, 104 bytes
0x0A000203248874B8 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x0A000203248874C8 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x0A000203248874D8 : 0000 0000 0000 0043 0000 0000 0000 0000
.......C........
0x0A000203248874E8 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x0A000203248874F8 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x0A00020324887508 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x0A00020324887518 : 0000 0000 0000 0000
........ |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* N/A *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* This problem is planed to be fixed in next release. *
**************************************************************** |
| Local Fix: |
Use filtered recovery to bypass the problematic table(s). |
| Solution |
|
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner :
follow-up : IT21468 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.06.2017
16.07.2017
16.07.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
