|
Problem IC65412
|
Status: Geschlossen |
In DB2 LUW, DB2ADUTL VERIFY HEADONLY command and DB2ADUTL QUERY command may show incorrect result for multi-session BACKUP. |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
1. The filename returned by the db2adutl verify headeronly
command does not match the header information when a backup is
taken
using more then one session.
Example
db2 backup database sample use tsm open 8 sessions
db2adutl verify headeronly db sample taken at 20091119140501
From below you can see it states:
Verifying file:
./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.001
But in per the header the file name should be
SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.007
Retrieving FULL DATABASE BACKUP information. Please wait.
FULL DATABASE BACKUP image:
./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.001,
DB Partition Number: 0
./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.002,
DB Partition Number: 0
./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.003,
DB Partition Number: 0
./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.004,
DB Partition Number: 0
./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.005,
DB Partition Number: 0
./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.006,
DB Partition Number: 0
./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.007,
DB Partition Number: 0
./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.008,
DB Partition Number: 0
Do you wish to verify this image (Y/N)?
Verifying file:
./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.001
=====================
MEDIA HEADER REACHED:
=====================
Server Database Name -- SAMPLE
Server Database Alias -- SAMPLE
Client Database Alias -- SAMPLE
Timestamp -- 20091119140501
Database Partition Number -- 0
Instance -- db2inst1
Sequence Number -- 7
Release ID -- B00
Database Seed -- DBFF1C1A
DB Comment's Codepage (Volume) -- 0
DB Comment (Volume) -- A sample database
DB Comment's Codepage (System) -- 0
DB Comment (System) -- A sample database
Authentication Value -- -1
Backup Mode -- 0
Includes Logs -- 0
Compression -- 0
Backup Type -- 0
Backup Gran. -- 0
Status Flags -- 1
System Cats inc -- 1
Catalog Partition Number -- 0
DB Codeset -- UTF-8
DB Territory --
LogID -- 1254882872
LogPath --
/home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/
Backup Buffer Size -- 1052672
Number of Sessions -- 8
Platform -- 1E
The proper image file name would be:
SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.007
2. The db2adutl query command may return several entries for the
same backup image to TSM.
db2adutl query full db SAMPLE
Query for database SAMPLE
Retrieving FULL DATABASE BACKUP information.
1 Time: 20091218011337 Oldest log: S1846095.LOG DB
Partition Number: 0 Sessions: 2
2 Time: 20091218011337 Oldest log: S1846095.LOG DB
Partition Number: 0 Sessions: 1
3 Time: 20091217011235 Oldest log: S1845626.LOG DB
Partition Number: 0 Sessions: 3
4 Time: 20091216011338 Oldest log: S1845409.LOG DB
Partition Number: 0 Sessions: 1
5 Time: 20091216011338 Oldest log: S1845409.LOG DB
Partition Number: 0 Sessions: 1
6 Time: 20091216011338 Oldest log: S1845409.LOG DB
Partition Number: 0 Sessions: 1
Retrieving INCREMENTAL DATABASE BACKUP information.
No INCREMENTAL DATABASE BACKUP images found for SAMPLE
Retrieving DELTA DATABASE BACKUP information.
No DELTA DATABASE BACKUP images found for SAMPLE
This problem happens whenever you have more than one session
that is required for a database.
This can occur even if the second session is due to an online
include logs and the backup only was defined as single session
(it automatically gets the second session for the logs phase).
3. The db2adutl keep <N> functionality may not work when the
images are not aggregated correctly.
Sample scenario is like this.
1) Check the backup images.
$ db2adutl query full db SAMPLE
Query for database SAMPLE
Retrieving FULL DATABASE BACKUP information.
1 Time: 20091218155633 Oldest log: S0004309.LOG DB
Partition Number: 0 Sessions: 2 (Online backup)
2 Time: 20091218131854 Oldest log: S0004300.LOG DB
Partition Number: 0 Sessions: 2 (Online backup)
3 Time: 20091218104953 Oldest log: S0004293.LOG DB
Partition Number: 0 Sessions: 1 (Offline backup)
Retrieving INCREMENTAL DATABASE BACKUP information.
No INCREMENTAL DATABASE BACKUP images found for SAMPLE
Retrieving DELTA DATABASE BACKUP information.
No DELTA DATABASE BACKUP images found for SAMPLE
The output is correct, one entry for one image.
2) Take a fourth online backup, and db2adutl delete with
"keep 6" option.
# su - maint1 -c db2 backup db SAMPLE online use tsm buffer
2049 include logs
Backup successful. The timestamp for this backup image is :
20091218163950
# su - maint1 -c db2adutl delete full NONINCREMENTAL keep 6
db SAMPLE without prompting
Query for database SAMPLE
Retrieving FULL DATABASE BACKUP information.
Taken at: 20091218104953 DB Partition Number: 0
Sessions: 1
The backup image which should not be deleted was deleted.
3) Check the backup images again.
$ db2adutl query full db SAMPLE
Query for database SAMPLE
Retrieving FULL DATABASE BACKUP information.
1 Time: 20091218163950 Oldest log: S0004315.LOG DB
Partition Number: 0 Sessions: 1
2 Time: 20091218163950 Oldest log: S0004315.LOG DB
Partition Number: 0 Sessions: 1
3 Time: 20091218155633 Oldest log: S0004309.LOG DB
Partition Number: 0 Sessions: 1
4 Time: 20091218155633 Oldest log: S0004309.LOG DB
Partition Number: 0 Sessions: 1
5 Time: 20091218131854 Oldest log: S0004300.LOG DB
Partition Number: 0 Sessions: 1
6 Time: 20091218131854 Oldest log: S0004300.LOG DB
Partition Number: 0 Sessions: 1
Retrieving INCREMENTAL DATABASE BACKUP information.
No INCREMENTAL DATABASE BACKUP images found for SAMPLE
Retrieving DELTA DATABASE BACKUP information.
No DELTA DATABASE BACKUP images found for SAMPLE
Two entries are listed for each backup image.
This problem does not occur in V8 and V9.1. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* The filename returned by the db2adutl verify *
* headeronlycommand does not match theheader information when *
* backup taken using more then onesessionExampledb2 backup *
* database sample use tsm open 8 sessionsdb2adutl verify *
* headeronly db sample taken at 20091119140501From below you *
* can see it statesVerifying *
* file:./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.001B
* in per the header the file name should *
* beSAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.007Retrie
* FULL DATABASE BACKUP information. Please wait.FULL DATABASE *
* BACKUP *
* image:./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.001
* DBPartition Number: *
* 0./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.002, *
* DBPartition Number: *
* 0./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.003, *
* DBPartition Number: *
* 0./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.004, *
* DBPartition Number: *
* 0./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.005, *
* DBPartition Number: *
* 0./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.006, *
* DBPartition Number: *
* 0./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.007, *
* DBPartition Number: *
* 0./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.008, *
* DBPartition Number: 0Do you wish to verify this image *
* (Y/N)?Verifying *
* file:./SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.001=
* HEADER REACHED:=====================Server Database Name *
* -- SAMPLEServer Database Alias -- SAMPLEClient *
* Database Alias -- SAMPLETimestamp *
* -- 20091119140501Database Partition Number -- *
* 0Instance -- db2inst1Sequence Number *
* -- 7Release ID -- B00Database *
* Seed -- DBFF1C1ADB Comment's Codepage *
* (Volume) -- 0DB Comment (Volume) -- A sample *
* databaseDB Comment's Codepage (System) -- 0DB Comment *
* (System) -- A sample databaseAuthentication Value *
* -- -1Backup Mode -- 0Includes *
* Logs -- 0Compression -- *
* 0Backup Type -- 0Backup Gran. *
* -- 0Status Flags -- 1System Cats inc *
* -- 1Catalog Partition Number -- 0DB *
* Codeset -- UTF-8DB Territory *
* --LogID -- 1254882872LogPath *
* *
* --/home/db2inst1/db2inst1/NODE0000/SQL00001/SQLOGDIR/Backup *
* Buffer Size -- 1052672Number of Sessions *
* -- 8Platform -- 1EThe proper image *
* file name would *
* be:SAMPLE.0.db2inst1.NODE0000.CATN0000.20091119140501.007 *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V9.7 Fixpack 2 *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Lösung |
V9.7 Fixpack 2 contains fix |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 05.01.2010
22.06.2010
22.06.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.FP2
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.2
|
 |
