home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC95286 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to 10.5.0.3                                           * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
Problem Fixed In 10.5.0.3
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
27.08.2013
24.03.2014
24.03.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.3 FixList
10.5.0.3 FixList