|
Problem IC84290
|
Status: Geschlossen |
IMPROVE DB2CKLOG TOOL TO PROVIDE MORE DIAGNOSTIC INFORMATION |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problembeschreibung: |
To improve the db2cklog tool to provide further diagnostic
information, ie: it will display the last log file that was
written to - this is important for servicability. It's also an
important piece of info that customers would like to see, but
currently they need to start the database and get this info via
db2pd.
Change directory to location of Database Control files and then
look to run:
$ db2cklog check -m
________________________________________________________________
____
_____ D B 2 C K L O G _____
DB2 Check Log File tool
I B M
The db2cklog tool is a utility can be used to test the
integrity
of an archive log file and to determine whether or not
the log file
can be used in the rollforward database
command.
________________________________________________________________
____
________________________________________________________________
________________
Last Write Extent Number = 2
"db2cklog": Finished processing log file "S0000000.LOG". Return
code: "0".
======================================================== |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* All Platforms *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to v10.1 Fixpack 1 or Higher *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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
|
| Lösung |
First Fixed in v10.1 Fixpack 1 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 13.06.2012
13.11.2012
13.11.2012 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
