|
Problem IC93405
|
Status: Closed |
DB2PD -LOGS AND MON_GET_TRANSACTION_LOG() DO NOT RETURN RIGHT LOG CHAIN ID |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
Starting with 10.1 db2pd -log and mon_get_transaction_log()
always return 0 for log chain id instead of returning the right
log chain number.
Example:
$ db2 "select log_chain_id from
table(mon_get_transaction_log(-1))"
LOG_CHAIN_ID
--------------------
0
1 record(s) selected.
$ db2pd -db <dbname> -logs
Database Member 0 -- Database DBNAME -- Active -- Up 0 days
00:05:45 -- Date 2013-06-12-12.09.52.672927
Logs:
Current Log Number 8
Pages Written 60
Cur Commit Disk Log Reads 0
Cur Commit Total Log Reads 0
Method 1 Archive Status n/a
Method 1 Next Log to Archive 8
Method 1 First Failure n/a
Method 2 Archive Status n/a
Method 2 Next Log to Archive n/a
Method 2 First Failure n/a
Log Chain ID 0 <-------
Current LSO 74396511
Current LSN 0x000000000003C5C2 |
| 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: IC93406 IC95449
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.06.2013
18.10.2013
18.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
|
 |
| 10.1.0.3
|
|
