Skip to Content
0
Former Member
Sep 25, 2009 at 08:52 AM

DB2 history file was damaged and recreated

162 Views

Hello

Today the db2rhist.ask and db2rhist.bak files was damaged and

automatically recreated by DB2

Our environment : AIX 5300-05-06, DB2 9.1.7, TSM 5.4

Acording to IBM technote #1392085 (http://www-01.ibm.com/support/docview.wss?rs=0&q1=ETXTBSY%2826%29%22Textfilebusy%22&uid=swg21392085&loc=en_US&cs=utf-8&cc=us&lang=en)

this issue can to be related for some reasons.

I check our environment for this reasons.

So, no file system full conditions, no limits for file size on AIX

(unlimited)

This problem occur at 2009-09-25-02.22.34.781958

I beleave what in this time there were no other processes (e.g. backup of DB2 or AIX filesystems) that would

impose a lock on the files db2rhist.ask(bak)

Also, this is the second time of this issue. The first time it happened

about a month ago on another system

Next part of db2diag.log related to this issue :

2009-09-25-02.22.34.781958240 E298693973A534 LEVEL: Warning (OS)+

PID : 323662 TID : 1 PROC : db2loggw (NEP) 0

INSTANCE: db2nep NODE : 000

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) "Text file busy"

DATA #1 : File name, 46 bytes

/db2/NEP/db2nep/NODE0000/SQL00001/db2rhist.asc

2009-09-25-02.22.34.808105240 E298694508A534 LEVEL: Warning (OS)+

PID : 323662 TID : 1 PROC : db2loggw (NEP) 0

INSTANCE: db2nep NODE : 000

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) "Text file busy"

DATA #1 : File name, 46 bytes

/db2/NEP/db2nep/NODE0000/SQL00001/db2rhist.bak

Sorry, but cant' understand how to past all db2diag.log entries ralated to error

More than 2 entries result of unreadable message.

What tags should be used for correct posting logs ?

Thank's

With best regards,

Dmitry Krivov