Latest versionsfixlist
11.1.0.6 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26
Question in the chat LiveZilla Live Help

DB2 - Problem description

Problem IC76028 Status: Closed

Online backup may fail due to Log file reader recomputing the log file size
wrong when the log file was truncated

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
Under certain workload conditions the rename array will get full 
in a HADR environment. When perform online backup, as the rename 
array is full, the log file may be truncated by other EDUs. The 
log file reader may recompute the log file size when the log 
file was truncated by other EDUs. However, under some condition 
when backup manager tries to include log file into backup image, 
log file reader may recompute the log file wrong which in turn 
causes online backup failed. 
 
Similar entries may be wriiten to db2diag.log: 
 
2011-02-08-00.06.23.647720+480 I50644589A374      LEVEL: Warning 
 
PID    : 344124              TID  : 1          PROC : db2lfr 
(FB) 0 
INSTANCE: inst              NODE : 000 
FUNCTION: DB2 UDB, data protection services, sqlpRenameStartUse, 
probe:1230 
MESSAGE : Log file 11948 is not added by DB2 because renameArray 
is full.File could be renamed while in use. 
 
 
2011-02-08-00.06.26.339653+480 I50646413A369      LEVEL: Error 
 
PID    : 344124              TID  : 1          PROC : db2lfr 
(FB) 0 
INSTANCE: inst1              NODE : 000 
 
FUNCTION: DB2 UDB, recovery manager, sqlplfrFMReadLog, 
probe:5300 
RETCODE : ZRC=0x870F0009=-2029060087=SQLO_EOF "the data does not 
exist" DIA8506C Unexpected end of file was reached. 
 
2011-02-08-00.06.31.103059+480 I50650497A487      LEVEL: Error 
PID    : 803028              TID  : 1          PROC : 
db2bm.2392210.0 0 
INSTANCE: inst1              NODE : 000 
APPHDL  : 0-1988              APPID: *LOCAL.fbinst.110207132939 
AUTHID  : INST 
FUNCTION: DB2 UDB, database utilities, sqlubProcessLogExtent, 
probe:1870 
MESSAGE : Backup error while copying log file extent: 
DATA #1 : Hexdump, 4 bytes 
0x0FFFFFFFFFFFD178 : 0000 2EAC 
 
2011-02-08-00.06.31.134124+480 E50652317A492      LEVEL: Error 
PID    : 803028              TID  : 1          PROC : 
db2bm.2392210.0 0 
INSTANCE: inst1              NODE : 000 
APPHDL  : 0-1988              APPID: *LOCAL.fbinst.110207132939 
AUTHID  : INST 
FUNCTION: DB2 UDB, database utilities, sqlubProcessLogExtent, 
probe:1876 
MESSAGE : ADM8010E  Backup was unable to copy requested log file 
"S0011948.LOG" for inclusion in the backup image. The backup has 
been 
aborted.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Under certain workload conditions the rename array will get  * 
* full                                                         * 
* in a HADR environment. When perform online backup, as the    * 
* rename                                                       * 
* array is full, the log file may be truncated by other EDUs.  * 
* The                                                          * 
* log file reader may recompute the log file size when the log * 
* file was truncated by other EDUs. However, under some        * 
* condition                                                    * 
* when backup manager tries to include log file into backup    * 
* image,                                                       * 
* log file reader may recompute the log file wrong which in    * 
* turn                                                         * 
* causes online backup failed.                                 * 
*                                                              * 
* Similar entries may be wriiten to db2diag.log:               * 
*                                                              * 
* 2011-02-08-00.06.23.647720+480 I50644589A374      LEVEL:     * 
* Warning                                                      * 
*                                                              * 
* PID    : 344124              TID  : 1          PROC : db2lfr * 
* (FB) 0                                                       * 
* INSTANCE: inst              NODE : 000                       * 
* FUNCTION: DB2 UDB, data protection services,                 * 
* sqlpRenameStartUse,                                          * 
* probe:1230                                                   * 
* MESSAGE : Log file 11948 is not added by DB2 because         * 
* renameArray                                                  * 
* is full.File could be renamed while in use.                  * 
*                                                              * 
*                                                              * 
* 2011-02-08-00.06.26.339653+480 I50646413A369      LEVEL:     * 
* Error                                                        * 
*                                                              * 
* PID    : 344124              TID  : 1          PROC : db2lfr * 
* (FB) 0                                                       * 
* INSTANCE: inst1              NODE : 000                      * 
*                                                              * 
* FUNCTION: DB2 UDB, recovery manager, sqlplfrFMReadLog,       * 
* probe:5300                                                   * 
* RETCODE : ZRC=0x870F0009=-2029060087=SQLO_EOF "the data does * 
* not                                                          * 
* exist" DIA8506C Unexpected end of file was reached.          * 
*                                                              * 
* 2011-02-08-00.06.31.103059+480 I50650497A487      LEVEL:     * 
* Error                                                        * 
* PID    : 803028              TID  : 1          PROC :        * 
* db2bm.2392210.0 0                                            * 
* INSTANCE: inst1              NODE : 000                      * 
* APPHDL  : 0-1988              APPID:                         * 
* *LOCAL.fbinst.110207132939                                   * 
* AUTHID  : INST                                               * 
* FUNCTION: DB2 UDB, database utilities,                       * 
* sqlubProcessLogExtent,                                       * 
* probe:1870                                                   * 
* MESSAGE : Backup error while copying log file extent:        * 
* DATA #1 : Hexdump, 4 bytes                                   * 
* 0x0FFFFFFFFFFFD178 : 0000 2EAC                               * 
*                                                              * 
* 2011-02-08-00.06.31.134124+480 E50652317A492      LEVEL:     * 
* Error                                                        * 
* PID    : 803028              TID  : 1          PROC :        * 
* db2bm.2392210.0 0                                            * 
* INSTANCE: inst1              NODE : 000                      * 
* APPHDL  : 0-1988              APPID:                         * 
* *LOCAL.fbinst.110207132939                                   * 
* AUTHID  : INST                                               * 
* FUNCTION: DB2 UDB, database utilities,                       * 
* sqlubProcessLogExtent,                                       * 
* probe:1876                                                   * 
* MESSAGE : ADM8010E  Backup was unable to copy requested log  * 
* file                                                         * 
* "S0011948.LOG" for inclusion in the backup image. The backup * 
* has                                                          * 
* been aborted.                                                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V95 FP9.                                      * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
The fix will be included in DB2 V95 FP9
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.04.2011
08.03.2012
08.03.2012
Problem solved at the following versions (IBM BugInfos)
9.5.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.9 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.