"db2cklog CHECK -m" reports the following error, when run
against an active database in DB2 V10.1:
________________________________________________________________
____
_____ 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.
________________________________________________________________
____
________________________________________________________________
________________
DBT7045E The db2cklog command failed because the db2cklog
utility cannot open the current log file. Log file name:
"SQLOGMIR.LFH".
The following information is reported in the db2diag.log file:
2012-12-27-15.42.29.986340+060 E68399A1006 LEVEL: Error
(OS)
PID : 9175208 TID : 1 PROC :
db2cklog
INSTANCE: xxxxxx NODE : 000
HOSTNAME: yyyyyy
EDUID: 1
FUNCTION: DB2 UDB, oper system services, sqloopenp, probe:80
MESSAGE : ZRC=0x870F0016=-2029060074=SQLO_SHAR "File sharing
violation."
DIA8519C A file sharing violation has occurred,
filename was "".
CALLED : OS, -, open
OSERR : ETXTBSY (26) "Cannot open or remove a file containing
a running progra
m."
DATA #1 : Codepath, 8 bytes
4:11:15:16:24:38:39:40
DATA #2 : File name, 12 bytes
SQLOGMIR.LFH
DATA #3 : SQO Open File Options, PD_TYPE_SQO_FILE_OPEN_OPTIONS,
4 bytes
SQLO_REVISE, SQLO_READWRITE, SQLO_SHAREREAD, SQLO_WRITETHRU
DATA #4 : Hex integer, 4 bytes
0x00000180
DATA #5 : signed integer, 4 bytes
100
DATA #6 : Hex integer, 4 bytes
0x00000000
DATA #7 : String, 105 bytes
Search for ossError*Analysis probe point after this log entry
for further
self-diagnosis of this problem.
When the database is not active, db2cklog works as expected. |
