|
Problem IC81710
|
Status: Closed |
THE INDIVIDUAL DB2 DIAGNOSTIC ROTATING LOG ( DB2DIAG.#.LOG, OR <INSTANCE>.#.NFY ) IS LIMITED WITHIN 4G IN SIZE. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
If DIAGSZIE is set to a value so that the size of individual db2
diagnostic rotating log ( db2diag.#.log, or <instance>.#.nfy )
is more than 4G, then, when the individual db2 diagnostic
rotating log reached 4G in size, following ADM14000E will be
dumped into <instance>.nfy, and current db2diag.#.log will be
stopped logging.
2012-01-21-02.58.42.413049 Instance:ndm Node:021
PID:2688288(db2linit 21) TID:8001
Appid:10.154.145.104.42631.120120185744
RAS/PD component pdLogInternal Probe:18 Database:NDB
ADM14000E DB2 is unable to open diagnostic log file "". Run
the
command
"db2diag -rc "0x870f014c"" to find out more. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users of version 9.7 on Linux, Unix and Windows *
* platforms. *
****************************************************************
* PROBLEM DESCRIPTION: *
* If DIAGSZIE is set to a value so that the size of individual *
* db2 *
* diagnostic rotating log ( db2diag.#.log, or <instance>.#.nfy *
* ) *
* is more than 4G, then, when the individual db2 diagnostic *
* rotating log reached 4G in size, following ADM14000E will be *
* dumped into <instance>.nfy, and current db2diag.#.log will *
* be *
* stopped logging. *
* *
* 2012-01-21-02.58.42.413049 Instance:ndm Node:021 *
* *
* PID:2688288(db2linit 21) TID:8001 *
* *
* Appid:10.154.145.104.42631.120120185744 *
* *
* RAS/PD component pdLogInternal Probe:18 Database:NDB *
* *
* *
* *
* ADM14000E DB2 is unable to open diagnostic log file "". *
* Run *
* the *
* command *
* *
* "db2diag -rc "0x870f014c"" to find out more. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 6. *
**************************************************************** |
| Local Fix: |
Reset DIAGSIZE to a value so that the size of individual db2
diagnostic rotating log ( db2diag.#.log, or <instance>.#.nfy )
is less then 4G, then restart instance.
Or
Archive ( or delete ) the current db2 diagnostic rotating log (
db2diag.#.log, or <instance>.#.nfy ) |
| available fix packs: |
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
|
| Solution |
Problem was first fixed in Version 9.7 Fix Pack 6 |
| Workaround |
Reset DIAGSIZE to a value so that the size of individual db2
diagnostic rotating log ( db2diag.#.log, or <instance>.#.nfy )
is less then 4G, then restart instance.
Or
Archive ( or delete ) the current db2 diagnostic rotating log (
db2diag.#.log, or <instance>.#.nfy ) |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC84498
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.02.2012
05.06.2012
05.06.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
