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

RESTORE OF A SNAPSHOT BACKUP IMAGE FROM A DOWNLEVEL RELEASE FAILS IN A
PARTITIONED DATABASE ENVIRONMENT WITH SQL1031N

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
In v11.1 and partitioned database environment, when attempting
to restore
a snapshot backup image which was acquired from a downlevel
release
(v10.5 or earlier releases), an SQL1031N error will occur.

"SQL1031N  The database directory cannot be found on the
indicated file system."
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* DPF users                                                    *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Update to the fixpack inclusive of this APAR fix and then    *
* perform the restore operation.                               *
* Alternatively, restore the snapshot backup image into a      *
* database instance of the same release from which the backup  *
* image was acquired, and follow regular upgrade procedure.    *
****************************************************************
Local Fix:
Update to the fixpack inclusive of this APAR fix and then
perform the restore operation.
Alternatively, restore the snapshot backup image into a database
instance of the same release from which the backup image was
acquired, and follow regular upgrade procedure.
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
24.10.2017
24.10.2017
24.10.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)