home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC90772 Status: Closed

SQL2036N WHEN USING RECOVER WITH RESTORED RECOVERY HISTORY FILE FROM A
BACKUP THAT HAS MORE THAN 1 SEQUENCES

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Consider the following scenario: 
Your backup has 2 sequences, eg: 
DBNAME.0.db2v1012.DBPART000.20130308155932.001 
DBNAME.0.db2v1012.DBPART000.20130308155932.002 
Now you restore the recovery history file from this backup: 
$ db2 restore db dbname history file from /backup-path taken at 
20130308155932 
As next step you use the restored recovery history file to 
recover the database: 
$ db2 "recover db dbname to end of logs using history file 
(/path/)" 
SQL2036N  The path for the file, named pipe, or device " " is 
not valid. 
The problem does not occur, when the backup only has 1 sequence. 
The error occurs because the restored recovery history file does 
not contain the path to the backup image. 
The history file on disk is ok. Only the restored one has this 
issue.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 3.                      * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 10.1 Fix Pack 3.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC90815 IC90816 IC95286 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.03.2013
02.10.2013
02.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList