|
Problem IT23310
|
Status: Closed |
WHEN USING SCRIPTED INTERFACE TIMESTAMP IN PROTOCOL FILE NAME AND IN CONTENTS OF PROTOCOL FILE MAY NOT BE EQUAL
|
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
When using the Scripted Interface for DB2 ACS, protocol files
are written. Their filename look like the following:
db2acs.JKL.0.db2c29.1459329788.cfg
The number in the file is the handle that is used by DB2
throughout the session, in the background a timestamp when the
snapshot was started.
In these protocol files additional timestamps are stored, e.g.
OBJ_DB2ID_LEVEL=5
OBJ_DB2ID_RELEASE=5
OBJ_DB2ID_VERSION=10
APP_OPTIONS=2100
TIMESTAMP=20160330112307
START_TIME=1459329787
It may happen that the timestamps are not equal.
In particular the timestamp in the protocol file reflects the
timestamp in the history file of the database. If this differs
with the timestamp in the filename a one to one mapping between
history file entry is not easily possible. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 Version 10.5 Fix Pack 10. *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.11.2017
12.07.2018
12.07.2018 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
