IBM Support

LI73497: ABNORMAL TERMINATION OF A RESTORE IN PROGRESS CAN RESULT IN A DIA8415C ERROR AFTER COMPLETION OF A SUBSEQUENT RESTORE

Fixes are available

DB2 Version 9.5 Fix Pack 3b for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 4  for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 4a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a restore is abnormally terminated (db2agent or client
process killed, db2_kill or some other abnormal termination due
to an error), a subsequent restore into the same database
directory may result in a dbseed mismatch error upon
rollforward.  The abnormal termination of the restore causes a
subsequent restore to use a default database configuration file
instead of the backup image database configuration file,
resulting in the dbseed mismatch errors.

Example db2diag.log messages:

2008-03-27-08.22.26.526022-300 I240218E516         LEVEL:
Severe
PID     : 30324                TID  : 47559930276160PROC :
db2sysc
INSTANCE: db2inst1             NODE : 000          DB   :
SAMPLE
APPHDL  : 0-670                APPID:
*LOCAL.db2inst1.080327132226
AUTHID  :
DB2INST1

EDUID   : 113                  EDUNAME: db2agent
(SAMPLE)
FUNCTION: DB2 UDB, base sys utilities,
sqeLocalDatabase::FirstConnect,
probe:100

DATA #1 : Hexdump, 4
bytes
0x00000002010E8D5C : A3FB FFFF
....

Another behavior has been observed for databases without
automatic storage enabled  The default database configuration
file is created with the automatic storage flag enabled and
under the same abnormal termination conditions the use of this
default configuration file with a database image that does NOT
have automatic storage results in the following error in the
db2diag.log at rollforward:

2008-05-10-18.01.45.374895-240 I3967A657          LEVEL: Severe
PID     : 27629                TID  : 1           PROC :
db2agent            (SAMPLE) 0
INSTANCE: db2inst1             NODE : 000
APPHDL  : 0-34                 APPID:
*LOCAL.db2idea1.080510220145
AUTHID  : DB2IDEA1
FUNCTION: DB2 UDB, buffer pool services,
sqlbInitStorageGroupTable,  probe:25
MESSAGE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic
error detected"
          DIA8501C A buffer pool logic error has occurred.
DATA #1 : String, 49 bytes
/opt/db2inst1/db2inst1/NODE0000/SQL00006/SQLSGF.1
DATA #2 : Boolean, 1 bytes
false
DATA #3 : Boolean, 1 bytes
true
DATA #4 : Boolean, 1 bytes
false

The underlying issue is the same as the use of the default
configuration file instead of the backup image configuration
file in this instance is at the root of the problem.

Local fix

  • Manual cleanup of the database files located in the database
path after abnormal termination of restore will allow subsequent
restore and rollforward to complete successfully.

Problem summary

  • User Affected: Any doing a restore.
Problem Description: Abnormal termination of a restore can
result in the subsequent restore failing with DIA8415C error.
Problem summary: See above.

Problem conclusion

  • First fixed in DB2 UDB Version 9.5, FixPak 3

Temporary fix

  • Manual cleanup of the database files located in the database
path after abnormal termination of restore will allow subsequent
restore and rollforward to complete successfully.

Comments

  • 



APAR Information




    

  • APAR number
    LI73497
    • 

  • Reported component name
    DB2 UDB WSE LIN
    • 

  • Reported component ID
    5765F3504
    • 

  • Reported release
    950
    • 

  • Status
    CLOSED  PER
    • 

  • PE
    NoPE
    • 

  • HIPER
    NoHIPER
    • 

  • Special Attention
    NoSpecatt
    • 

  • Submitted date
    2008-06-07
    • 

  • Closed date
    2009-03-28
    • 

  • Last modified date
    2009-03-28
    • 





    

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

    • 

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

    
LI73498
    

    • 



Fix information


    

  • Fixed component name
    DB2 UDB WSE LIN
    • 

  • Fixed component ID
    5765F3504
    • 



Applicable component levels


    

  • R950  PSN
       UP
    • 








      
              
                            

              

              [{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"950","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
              

                          

          
 
        

      

    

      

        

          

            
Document Information


            

            


                        

            Modified date:
            

            15 October 2021
            

            
                      

        


        

        


      

    

  



    

  

  
    
            

          
Page Feedback