Hi,

I am getting below error in the diag log.
DB2 version is 8.1.2 FP 7 on Windows.

Please help me with possible solutions...

2011-03-09-06.03.52.633000+240 I37487120H491 LEVEL: Error
PID : 2476 TID : 772 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : TIDTPRD
APPHDL : 0-125 APPID: C0A80289.L40F.155449020205
FUNCTION: DB2 UDB, buffer pool services, sqlbSMSOpenContainer, probe:820
RETCODE : ZRC=0x870F0016=-2029060074=SQLO_SHAR "File sharing violation."
DIA8519C A file sharing violation has occurred, filename was "".

2011-03-09-06.03.52.695000+240 I37487613H464 LEVEL: Error
PID : 2476 TID : 772 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : TIDTPRD
APPHDL : 0-125 APPID: C0A80289.L40F.155449020205
FUNCTION: DB2 UDB, buffer pool services, sqlbSMSOpenContainer, probe:820
DATA #1 : String, 93 bytes
Obj={pool:2;obj:107;type:1} State=x5 Cont=0
D:\DB2\NODE0000\SQL00002\SQLT0002.0\SQL00107.INX

2011-03-09-06.03.52.711000+240 I37488079H682 LEVEL: Error
PID : 2476 TID : 772 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : TIDTPRD
APPHDL : 0-125 APPID: C0A80289.L40F.155449020205
MESSAGE : SQLB_OBJECT_DESC
DATA #1 : Hexdump, 68 bytes
0x0614D428 : 0200 6B00 0200 6B00 0100 0000 0000 0000 ..k...k.........
0x0614D438 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x0614D448 : 0000 0000 0100 0000 0500 0000 0000 0000 ................
0x0614D458 : 0010 0000 2000 0000 0200 0000 0200 6B01 .... .........k.
0x0614D468 : B0C9 7D02 ..}.

2011-03-09-06.03.52.820000+240 I37488763H489 LEVEL: Error
PID : 2476 TID : 772 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : TIDTPRD
APPHDL : 0-125 APPID: C0A80289.L40F.155449020205
FUNCTION: DB2 UDB, buffer pool services, sqlbSMSGetOpenInfo, probe:810
RETCODE : ZRC=0x870F0016=-2029060074=SQLO_SHAR "File sharing violation."
DIA8519C A file sharing violation has occurred, filename was "".

2011-03-09-06.03.52.820000+240 I37489254H395 LEVEL: Error
PID : 2476 TID : 772 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : TIDTPRD
APPHDL : 0-125 APPID: C0A80289.L40F.155449020205
FUNCTION: DB2 UDB, buffer pool services, sqlbSMSGetOpenInfo, probe:810
MESSAGE : Obj={pool:2;obj:107;type:1} State=x5 Cont=0

2011-03-09-06.03.52.820000+240 I37490335H484 LEVEL: Error
PID : 2476 TID : 772 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : TIDTPRD
APPHDL : 0-125 APPID: C0A80289.L40F.155449020205
FUNCTION: DB2 UDB, buffer pool services, sqlbReadPage, probe:1130
RETCODE : ZRC=0x870F0016=-2029060074=SQLO_SHAR "File sharing violation."
DIA8519C A file sharing violation has occurred, filename was "".

2011-03-09-06.03.52.820000+240 I37490821H479 LEVEL: Severe
PID : 2476 TID : 772 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : TIDTPRD
APPHDL : 0-125 APPID: C0A80289.L40F.155449020205
FUNCTION: DB2 UDB, data management, loadSMSDesc, probe:1171
RETCODE : ZRC=0x870F0016=-2029060074=SQLO_SHAR "File sharing violation."
DIA8519C A file sharing violation has occurred, filename was "".

2011-03-09-06.03.52.852000+240 I37491302H479 LEVEL: Severe
PID : 2476 TID : 772 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : TIDTPRD
APPHDL : 0-125 APPID: C0A80289.L40F.155449020205
FUNCTION: DB2 UDB, data management, loadSMSDesc, probe:1268
RETCODE : ZRC=0x870F0016=-2029060074=SQLO_SHAR "File sharing violation."
DIA8519C A file sharing violation has occurred, filename was "".

2011-03-09-06.03.52.852000+240 I37491783H479 LEVEL: Severe
PID : 2476 TID : 772 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : TIDTPRD
APPHDL : 0-125 APPID: C0A80289.L40F.155449020205
FUNCTION: DB2 UDB, data management, sqldLoadTCB, probe:4768
RETCODE : ZRC=0x870F0016=-2029060074=SQLO_SHAR "File sharing violation."
DIA8519C A file sharing violation has occurred, filename was "".

2011-03-09-06.03.52.852000+240 I37492264H462 LEVEL: Severe
PID : 2476 TID : 772 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : TIDTPRD
APPHDL : 0-125 APPID: C0A80289.L40F.155449020205
FUNCTION: DB2 UDB, data management, sqldLoadTCB, probe:4768
MESSAGE : Error loading TCB. tcbFlags =
DATA #1 : Hexdump, 4 bytes
0x05502C8C : 1400 0000 ....

2011-03-09-06.03.52.883000+240 I37492728H361 LEVEL: Severe
PID : 2476 TID : 772 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : TIDTPRD
APPHDL : 0-125 APPID: C0A80289.L40F.155449020205
MESSAGE : SQLD_TCB:
DATA #1 : String, 41 bytes
Perm Table(2:107)=TBSPACEID=2.TABLEID=107

2011-03-09-06.03.52.992000+240 I37496388H501 LEVEL: Warning
PID : 2476 TID : 772 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : TIDTPRD
APPHDL : 0-125 APPID: C0A80289.L40F.155449020205
FUNCTION: DB2 UDB, catcache support, sqlrlc_systables_fetch_from_disk, probe:320
RETCODE : ZRC=0x870F0016=-2029060074=SQLO_SHAR "File sharing violation."
DIA8519C A file sharing violation has occurred, filename was "".

2011-03-09-06.03.53.070000+240 I37497796H697 LEVEL: Severe
PID : 2476 TID : 772 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : TIDTPRD
APPHDL : 0-125 APPID: C0A80289.L40F.155449020205
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -902 sqlerrml: 2
sqlerrmc: 22
sqlerrp : SQLRC05F
sqlerrd : (1) 0x870F0016 (2) 0x00000016 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:

2011-03-09-06.03.53.602000+240 I37501571H3943 LEVEL: Severe
PID : 2476 TID : 772 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : TIDTPRD
APPHDL : 0-125 APPID: C0A80289.L40F.155449020205
MESSAGE : section stmt
DATA #1 : Hexdump, 779 bytes
0x0542ACE0 : 7365 6C65 6374 2022 5245 434E 5F52 4546 select "RECN_REF
0x0542ACF0 : 222C 2250 524F 4A45 4354 494F 4E22 2C22 ","PROJECTION","
0x0542AD00 : 4143 4354 5F4E 554D 222C 2254 5241 4E5F ACCT_NUM","TRAN_
0x0542AFD0 : 2220 6672 6F6D 2022 5452 4144 4549 4E31 " from "TRADEIN1
0x0542AFE0 : 222E 2250 4F53 5449 4E47 22 "."POSTING"

2011-03-09-06.03.53.805000+240 I37515609H369 LEVEL: Severe
PID : 2476 TID : 772 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : TIDTPRD
APPHDL : 0-125 APPID: C0A80289.L40F.155449020205
MESSAGE : SQLD_CCB:
DATA #1 : String, 50 bytes
pool(TID)=1, obj(FID)=2, indexid(IID)=0, class=128

2011-03-09-06.03.54.102000+240 I37558130H430 LEVEL: Severe
PID : 2476 TID : 772 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : TIDTPRD
APPHDL : 0-125 APPID: C0A80289.L40F.155449020205
FUNCTION: DB2 UDB, relation data serv, sqlrr_rds_common_post, probe:12
DATA #1 : Hexdump, 4 bytes
0x0550A3B0 : 1600 0F87 ....

2011-03-09-06.03.54.117000+240 I37558562H379 LEVEL: Severe
PID : 2476 TID : 772 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : TIDTPRD
APPHDL : 0-125 APPID: C0A80289.L40F.155449020205
MESSAGE : UCstate:
DATA #1 : Hexdump, 4 bytes
0x32A56990 : 4000 0004 @...

2011-03-09-06.03.54.117000+240 I37559757H697 LEVEL: Severe
PID : 2476 TID : 772 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : TIDTPRD
APPHDL : 0-125 APPID: C0A80289.L40F.155449020205
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -902 sqlerrml: 2
sqlerrmc: 22
sqlerrp : SQLRC05F
sqlerrd : (1) 0x870F0016 (2) 0x00000016 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:

2011-03-09-06.03.54.117000+240 E37560456H375 LEVEL: Severe
PID : 2476 TID : 772 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : TIDTPRD
APPHDL : 0-125 APPID: C0A80289.L40F.155449020205
FUNCTION: DB2 UDB, base sys utilities, sqleMarkDBad, probe:10
MESSAGE : ADM7518C "TIDTPRD " marked bad.

as indicated - file sharing violation
any other application accessing the db files (should not be done ..)
maybe the virus-scanner active ...

will anitvirus mark the database bad?
please check the complete logs which i have posted and post a solution.

No,
DB2 detected a file sharing violation and marked the database bad.

If you have a virus-scanner, then check your excludes on the Directory/Files for DB2.

Database bad? Is it down? What does db2dart report? Who has access to the file-systems assigned to the table-spaces. Make sure no-one but the instance-owner can access them. Even better: harden your server and get rid of any virus-scanners, you do not want that on your databaseserver!

If you have a backup of your database before the problem, you
may restore all data from the backup copy..
If you don't have backup then check with system restore(in case of windows..) you can take backup and restore it !!!

The db is not really bad/damaged so there is no need to execute db2dart or restore it. As previously mentioned, exclude all db2 related files from anti-virus scan. Also, make sure to exclude them from any OS backup or stop the instance prior to running it.