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 IT01784 Status: Geschlossen

Database recovery using a history file in a partitioned environm ent where
the database has been dropped will fail with SQL1092

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
Database recovery using a history file in a partitioned 
environment where the database has been dropped 
will fail with SQL1092 insufficient authority error. 
 
 
Reproduction: 
1. Create a database in the partitioned environment. (in this 
example, a 3 node system logically collocated will be used) 
    > db2 create database sample 
 
2. Backup the database on all partitions 
    > db2 backup db sample on all dbpartitionnums 
 
3. Backup the database history file on all partitions 
    > cp $DBDIR/NODE0000/SQL00001/db2rhist.asc 
$HOME/histfile/NODE0000/ 
    > cp $DBDIR/NODE0001/SQL00001/db2rhist.asc 
$HOME/histfile/NODE0001/ 
    > cp $DBDIR/NODE0002/SQL00001/db2rhist.asc 
$HOME/histfile/NODE0002/ 
 
4. Drop the database 
    > db2 drop db sample 
 
5. Recover the database with the history files 
backup. 
     > db2 recover db SAMPLE to 2014-03-21-11.05.39 using local 
time 
using history file "($HOME/histfile/NODE0000/, 
$HOME/histfile/NODE0001/ on dbpartitionnum 1, 
$HOME/histfile/NODE0002/ on dbpartitionnum 2)" 
 
The above command will fail with the following error: 
SQL1092N  The requested command or operation failed because the 
user ID does 
not have the authority to perform the requested command or 
operation.  User 
ID: "TESTER". 
 
 
Error messages in db2diag.log: 
2014-04-11-13.02.30.870416-240 E302280E600           LEVEL: 
Severe 
PID     : 20033                TID : 46912916941120  PROC : 
db2sysc 2 
INSTANCE: tester             NODE : 002            DB   : 
SAMPLE 
APPHDL  : 0-89                 APPID: *N0.tester.140411170155 
AUTHID  : TESTER             HOSTNAME: HOST0 
EDUID   : 274                  EDUNAME: db2agntp (SAMPLE) 2 
FUNCTION: DB2 UDB, database utilities, sqludInitCheck, probe:766 
DATA #1 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes 
-1092 
DATA #2 : Hexdump, 13 bytes 
0x00002AAADB58D170 : BCFB FFFF 4745 4F46 4652 4559 00 
....TESTER. 
 
2014-04-11-13.02.30.953448-240 E302881E468           LEVEL: 
Severe 
PID     : 20033                TID : 46912916941120  PROC : 
db2sysc 2 
INSTANCE: tester             NODE : 002            DB   : 
SAMPLE 
APPHDL  : 0-89                 APPID: *N0.tester.140411170155 
AUTHID  : TESTER             HOSTNAME: HOST0 
EDUID   : 274                  EDUNAME: db2agntp (SAMPLE) 2 
FUNCTION: DB2 UDB, database utilities, sqludrsa, probe:860 
MESSAGE : Restore Terminated.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DPF mode                                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* See Local Fix:                                               * 
* The customer can restore the database first, then use        * 
* rollforward or recover command.                              * 
****************************************************************
Local-Fix:
The customer can restore the database first, then use 
rollforward or recover command.
verfügbare FixPacks:
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
The Recover command will complete successfully. The fix is in 
DB2V105FP4 (CANCUN).
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
13.05.2014
15.09.2014
15.09.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList