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 IC67771 Status: Closed

REDIRECT RESTORE OF DATABASE FAILS WITH SQL5153N

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Redirect restore of a database fails with the following error 
 
SQL5153N  The update cannot be completed because the following 
relationship 
would be violated: "". 
 
Following errors can be seen in the db2diag.log 
 
2010-03-19-03.21.14.686996-240 E18178A946         LEVEL: Severe 
PID     : 143450               TID  : 2058        PROC : db2sysc 
INSTANCE: rohiraut             NODE : 000         DB   : CRCTST3 
APPHDL  : 0-8                  APPID: 
*LOCAL.rohiraut.100319072115 
AUTHID  : ROHIRAUT 
EDUID   : 2058                 EDUNAME: db2agent (CRCTST3) 
FUNCTION: DB2 UDB, database utilities, sqludProcessDBCfg, 
probe:474 
MESSAGE : SQL5153N  The update cannot be completed because the 
following 
          relationship would be violated: "". 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -5153   sqlerrml: 0 
 sqlerrmc: 
 sqlerrp : sqludPro 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0x00000000      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
 
2010-03-19-03.21.15.189518-240 E19125A1051        LEVEL: Error 
(OS) 
PID     : 143450               TID  : 2058        PROC : db2sysc 
INSTANCE: rohiraut             NODE : 000         DB   : CRCTST3 
APPHDL  : 0-8                  APPID: 
*LOCAL.rohiraut.100319072115 
AUTHID  : ROHIRAUT 
EDUID   : 2058                 EDUNAME: db2agent (CRCTST3) 
FUNCTION: DB2 UDB, oper system services, sqloopenp, probe:80 
MESSAGE : ZRC=0x870F0016=-2029060074=SQLO_SHAR "File sharing 
violation." 
          DIA8519C A file sharing violation has occurred, 
filename was "". 
CALLED  : OS, -, open 
OSERR   : ETXTBSY (26) "Text file busy" 
DATA #1 : Codepath, 8 bytes 
4:14:15:16:23:36:37 
DATA #2 : File name, 71 bytes 
/home/rohiraut/databases/CRCTST3/rohiraut/NODE0000/SQL00001///SQ 
LDBCONF 
DATA #3 : Bitmask, 4 bytes 
0x0000004C 
 
fuser for the file SQLDBCONF shows db2sysc as the holder 
 
Note that this error only occurs on V9.5 FP5. Will be fixed in 
V9,5 FP6 onwards. On all FixPaks's below Fp5 it works fine. 
 
This error only occurs during a redirect restore and when 
LOGSECOND is set to 254
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users prior to V9.7 FP2                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Redirect restore of a database fails with the                * 
* followingerrorSQL5153N  The update cannot be completed       * 
* because thefollowingrelationshipwould be violated:           * 
* "".Following errors can be seen in the                       * 
* db2diag.log2010-03-19-03.21.14.686996-240 E18178A946         * 
* LEVEL:SeverePID    : 143450              TID  : 2058         * 
* PROC :db2syscINSTANCE: rohiraut            NODE : 000        * 
* DB  :CRCTST3APPHDL  : 0-8                                    * 
* APPID:*LOCAL.rohiraut.100319072115AUTHID  : ROHIRAUTEDUID  : * 
* 2058                EDUNAME: db2agent (CRCTST3)FUNCTION: DB2 * 
* UDB, database utilities, sqludProcessDBCfg,probe:474MESSAGE  * 
* : SQL5153N  The update cannot be completed                   * 
* becausethefollowingrelationship would be violated: "".DATA   * 
* #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytessqlcaid : SQLCA      * 
* sqlcabc: 136  sqlcode: -5153  sqlerrml: 0sqlerrmc:sqlerrp :  * 
* sqludProsqlerrd : (1) 0x00000000      (2) 0x00000000         * 
* (3)0x00000000(4) 0x00000000      (5) 0x00000000              * 
* (6)0x00000000sqlwarn : (1)      (2)      (3)      (4)        * 
* (5)      (6)(7)      (8)      (9)      (10)                  * 
* (11)sqlstate:2010-03-19-03.21.15.189518-240 E19125A1051      * 
*   LEVEL:Error(OS)PID    : 143450              TID  : 2058    * 
*     PROC :db2syscINSTANCE: rohiraut            NODE : 000    * 
*     DB  :CRCTST3APPHDL  : 0-8                                * 
* APPID:*LOCAL.rohiraut.100319072115AUTHID  : ROHIRAUTEDUID  : * 
* 2058                EDUNAME: db2agent (CRCTST3)FUNCTION: DB2 * 
* UDB, oper system services, sqloopenp, probe:80MESSAGE :      * 
* ZRC=0x870F0016=-2029060074=SQLO_SHAR "File                   * 
* sharingviolation."DIA8519C A file sharing violation has      * 
* occurred,filename was "".CALLED  : OS, -, openOSERR  :       * 
* ETXTBSY (26) "Text file busy"DATA #1 : Codepath, 8           * 
* bytes4:14:15:16:23:36:37DATA #2 : File name, 71              * 
* bytes/home/rohiraut/databases/CRCTST3/rohiraut/NODE0000/SQL000 
* #3 : Bitmask, 4 bytes0x0000004Cfuser for the file SQLDBCONF  * 
* shows db2sysc as the holderNote that this error only occurs  * 
* on V9.5 FP5. Will be fixedinV9,5 FP6 onwards. On all         * 
* FixPaks's below Fp5 it works fine.This error only occurs     * 
* during a redirect restore and whenLOGSECOND is set to 254    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.7 FP2                                          * 
****************************************************************
Local Fix:
1. Move the instance to V9.5 FP4 and then do the redirect 
restore. 
 
2. Update db cfg parameter LOGSECOND to less that 254. Take a 
new backup and then do the redirect restore
available fix packs:
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a 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
First fixed in V9.7 FP2
Workaround
1. Move the instance to V9.5 FP4 and then do the redirect 
restore. 
 
2. Update db cfg parameter LOGSECOND to less that 254. Take a 
new backup and then do the redirect restore
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.04.2010
22.06.2010
22.06.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 FixList