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

DB2INIDB SAMPLE AS SNAPSHOT WAS RETURNED DBT1011N UNABLE TO RES TART
DATABASE "DATABASE-NAME" WITH THE WRITE RESUME OPTION. SQL

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
db2inidb sample as snapshot was returned DBT1011N  Unable to 
restart database "database-name" with the WRITE RESUME option. 
SQLCODE = "-1768". 
 
$ db2start 
04/14/2014 10:59:42     0   0   SQL1063N  DB2START processing 
was successful. 
SQL1063N  DB2START processing was successful. 
$ db2 catalog db sample 
DB20000I  The CATALOG DATABASE command completed successfully. 
DB21056W  Directory changes may not be effective until the 
directory cache is 
refreshed. 
$ db2inidb sample as snapshot 
DBT1011N  Unable to restart database "SAMPLE" with the WRITE 
RESUME option.  SQLCODE = "-1768". 
 
This behavior will be occurred, if use the image from a HADR 
primary database.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* HADR                                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 10.1 fix pack 5.                  * 
****************************************************************
Local Fix:
Stop hadr, then connect or activate database.
Solution
Problem was first fixed in DB2 UDB Version 10.1 fix pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.04.2014
17.07.2015
17.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList