home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC89312 Status: Geschlossen

"DB2CKLOG CHECK -M" FAILS WITH DBT7045E IN V10.1, WHEN THE
CHECKED DATABASE IS ACTIVE

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
"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.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 3.                      * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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 DB2 Version 10.1 Fix Pack 3.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
28.12.2012
02.10.2013
02.10.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.3 FixList
10.1.0.3 FixList