|
Problem IT19926
|
Status: Closed |
THE DB2CHECKSD OPERATION MAY HANG WHEN RESTORING A 11.1.0.0 ESE BACKUP IMAGE TO 11.1.1.1 PURESCALE ENVIRONMENT |
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
The documented procedure to restore an ESE backup image into a
pureScale instance (as described in the Knowledge Center page
titled "Restore from DB2 Enterprise Server Edition to DB2
pureScale instance") describes performing a db2checkSD operation
after the restore operation.
When restoring a v11.1.0.0 (GA) ESE backup image into a
v11.1.1.1 pureScale instance, the db2checkSD operation may hang.
The db2diag.log will contain the following error message:
2017-03-27-10.33.45.204689-240 I146748A817 LEVEL:
Warning
PID : 55705820 TID : 50406 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
SAMPLE
APPHDL : 0-58 APPID: *N0.DB2.170327143345
AUTHID : DB2INST1 HOSTNAME: hotelaix14
EDUID : 50406 EDUNAME: db2agnti (SAMPLE) 0
FUNCTION: DB2 UDB, base sys utilities,
sqeLocalDatabase::SubsequentConnect, probe:12292
RETCODE : ZRC=0xFFFFFBF5=-1035
SQL1035N The operation failed because the specified
database cannot
be connected to in the mode requested.
A stack dump of the hanging agent will show the following
functions:
<Stack dump>
WaitForCompletion
DispatchIndependentDBAgent
StartRqstHandler
sqlraInvokeAutonomousRebind
sqlra_find_pkg |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 11.1 Mod 2 Fix Pack 2 or higher *
**************************************************************** |
| Local Fix: |
As a workaround, the v11.1.0.0 (GA) ESE backup image can instead
be restored into a v11.1.0.0 (GA) pureScale instance followed by
the upgrade of this pureScale instance to v11.1.1.1.
Alternately, v11.1.0.0 (GA) ESE instance can be upgraded to
v11.1.1.1 before the backup image is obtained, followed by
restoring this backup image in the v11.1.1.1 pureScale instance. |
| available fix packs: |
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 11.1 Mod 2 Fix Pack 2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.03.2017
23.06.2017
23.06.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
