home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 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

DB2 - Problem description

Problem IC95431 Status: Closed

ONLINE BACKUP CAN FAIL WITH SQL0100W AND INCORRECTLY REPORT BACK UP
COMPLETE AS WELL AS OVERWRITING THE BACKUP TRACKING STRUCTURE

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
During an online backup, if the locklist is low, the backup may 
get an SQL0100W warning while building the list of tablespaces 
after a lock escalation.  This will cause the backup to error 
out, but it will write a Backup Complete message in the 
db2diag.log even thought the backup did not actually complete. 
This will also incorrectly update the backup tracking structure 
which could effect incremental backups 
 
Example db2daig.log messages: 
 
2013-01-27-01.08.05.330717-300 E4225668A790       LEVEL: Warning 
 
PID     : 188530               TID  : 23549       PROC : db2sysc 
23 
INSTANCE: db2inst1             NODE : 023         DB   : SAMPLE 
APPHDL  : 0-13776              APPID: *N0.db2inst1.140902031401 
AUTHID  : db2inst1 
EDUID   : 23549                EDUNAME: db2agntp (SAMPLE) 23 
FUNCTION: DB2 UDB, data management, sqldEscalateLocks, probe:2 
MESSAGE : ADM5500W  DB2 is performing lock escalation. The 
affected application 
          is named "db2bp", and is associated with the workload 
name 
          "SYSDEFAULTUSERWORKLOAD" and application ID 
          "*N0.db2inst1.140902031401"  at member "23". The total 
number of 
          locks currently held is "127", and the target number 
of locks to hold 
          is "63". 
 
(...) 
 
 
2013-01-27-01.08.05.357824-300 E4226981A562       LEVEL: Warning 
 
PID     : 188530               TID  : 23549       PROC : db2sysc 
23 
INSTANCE: db2inst1             NODE : 023         DB   : SAMPLE 
APPHDL  : 0-13776              APPID: *N0.db2inst1.140902031401 
AUTHID  : db2inst1 
EDUID   : 23549                EDUNAME: db2agntp (SAMPLE) 23 
FUNCTION: DB2 UDB, database utilities, sqlubBuildAppTbsp, 
probe:1799 
DATA #1 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes 
100 
DATA #2 : Hexdump, 8 bytes 
0x07000000DCC64770 : 0000 0001 0000 0001 
........ 
 
2013-01-27-01.08.05.364628-300 E4227544A953       LEVEL: Warning 
 
PID     : 188530               TID  : 23549       PROC : db2sysc 
23 
INSTANCE: db2inst1             NODE : 023         DB   : SAMPLE 
APPHDL  : 0-13776              APPID: *N0.db2inst1.140902031401 
AUTHID  : db2inst1 
EDUID   : 23549                EDUNAME: db2agntp (SAMPLE) 23 
FUNCTION: DB2 UDB, database utilities, sqlubBuildAppTbsp, 
probe:1799 
MESSAGE : SQL0100W  No row was found for FETCH, UPDATE or 
DELETE; or the result 
          of a query is an empty table. 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: 100   sqlerrml: 1 
 sqlerrmc: 1 
 sqlerrp : sqlubBui 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0x00000000      (6) 
0x00000017 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
 
(...) 
 
2013-01-27-01.08.13.916118-300 E4274426A428       LEVEL: Info 
PID     : 188530               TID  : 23549       PROC : db2sysc 
23 
INSTANCE: db2inst1             NODE : 023         DB   : SAMPLE 
APPHDL  : 0-13776              APPID: *N0.db2inst1.140902031401 
AUTHID  : db2inst1 
EDUID   : 23549                EDUNAME: db2agntp (SAMPLE) 23 
FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:906 
MESSAGE : Backup complete.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Any doing a database backup when the locklist is almost      * 
* exhausted                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to 10.5.Fixpack 3                                     * 
****************************************************************
Local Fix:
Take a fresh backup of the database or partition where the error 
occurred.
available fix packs:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
Problem Fixed In 10.5.Fixpack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.08.2013
27.02.2014
27.02.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.3 FixList
10.5.0.3 FixList