IBM Support

IC67771: REDIRECT RESTORE OF DATABASE FAILS WITH SQL5153N

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error 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
    

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
    

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                                          *
    ****************************************************************
    

Problem conclusion

  • First fixed in V9.7 FP2
    

Temporary 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
    

Comments

APAR Information

  • APAR number

    IC67771

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-04-09

  • Closed date

    2010-06-22

  • Last modified date

    2010-06-22

  • APAR is sysrouted FROM one or more of the following:

    IC67584

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.7","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
22 June 2010