IBM Support

IT26452: RESTORE OF A NON-ENCRYPTED DATABASE INTO AN ENCRYPTED ONE (TO IMPLEMENT ENCRYPTION) WILL NOT ALLOW ACTIVATION OF THE DATABASE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Reproduction of the issue with an online backup:
    
    - Create unencrypted database, set to archiving, create table, 5
    inserts
    - Online backup with no transaction during backup
    - Copy out all of the logs in active log path
    - Update dbm to encrypted
    - Drop database
    - Restore using overflow, encrypted
    - Rollforward to EoL and stop
    - Activate database
    - An error is hit on first log write:
    
    2018-08-18-22.12.26.880402-420 I8775A1847          LEVEL: Error
    PID    : 16057330            TID : 24625         PROC : db2sysc
    0
    INSTANCE: db2inst1             NODE : 000          DB  : SAMPLE
    HOSTNAME: server1
    EDUID  : 24625               EDUNAME: db2loggw (SAMPLE) 0
    FUNCTION: DB2 Common, Cryptography, cryptP12KSGetSecretKey,
    probe:492
    MESSAGE :
    ECF=0x90000645=-1879046587=ECF_CRYPT_KEYSTORE_EXPECTED_LABEL_NOT
    _FOUND
    
    NOTE:  This problem can also be reproduced with an offline
    backup.  Online vs. offline doesn't matter.
    

Local fix

  • A) Restore the online/offline backup to a non-encrypted
    database.
    
    or
    
    B) Only copy logs that are needed from active to overflow:
    
    - deactivate database
    - db2 get db cfg (note down "First active log file")
    - copy out all active logs (just in case)
    - follow regular procedure to restore encrypt
    - Only copy the active log files prior to "First active log
    file" to overflow
    - rollforward
    
    or
    
    C) If offline backup can be done, don't copy any active logs.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * all                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1.4.6 or higher                            *
    ****************************************************************
    

Problem conclusion

  • Upgrade to Db2 11.1.4.6 or higher
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT26452

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-09-27

  • Closed date

    2021-03-31

  • Last modified date

    2021-03-31

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

    IT26045

  • 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

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1"}]

Document Information

Modified date:
01 April 2021