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

THE SPLIT SNAPSHOT FLAG IS NOT CLEARED DURING A SNAPSHOT BACKUP

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
If a database is a clone database using DB2 split mirroring, i.e 
db2inidb as snapshot, a flag was set to indicate this is a split 
snapshot with a new log chain. However if an ACS snapshot backup 
is taken subsequently from this clone database, i.e. db2 backup 
db use snapshot, the flag is not cleared, therefore a subsequent 
command running on this snapshot backup copy such as db2inidb as 
acs standby would fail with DBT1010N error: 
 
DBT1010N  The split mirror image database <the db name> has been 
previously initialized as a snapshot. 
 
This issue has been seen when using Tivoli Flashcopy Manager to 
offload a DB2 snapshot backup to TSM tape.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 4 or newer              * 
****************************************************************
Local Fix:
N/A
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem was first fixed in Version 10.1 Fix Pack 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.11.2013
10.06.2014
10.06.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList