Hi folks!

I have problems with offline backups. Just after midnight the
application disconnects from the DB and starts with backup. After backup
is done it waits for few minutes and then connects to the db again. For
few minutes everything is OK, but then DB2 disconnects all aplications:

[SQLSTATE=40003 - [IBM][CLI Driver][DB2/NT] SQL1224N A database agent
could not be started to service a request, or was terminated as a result
of a database system shutdown or a force command. SQLSTATE=55032 [Native
Error=-1224]]

[SQLSTATE=08003 - [IBM][CLI Driver] CLI0106E Connection is closed.
SQLSTATE=08003 [Native Error=-99999]]

In db2diag.log I have this:

2003-02-18-03.44.02.312000 InstanceB2 Node:000
PID:1240(db2syscs.exe) TID:1968 Appid:*LOCAL.DB2.030703094551
buffer_pool_services sqlbWritePageToContainer Probe:30
Database:PRO_DB

Obj={pool:2;obj:5;type:1} State=x27 Cont=0 Offset=64017 BlkSize=12

Data Title:SQLB_OBJECT_DESC PID:1240 TID:1968 Node:000
0200 0500 0200 0500 0100 0000 0073 7347 .............ssG
ca36 0000 0000 0000 0000 0000 0000 0000 Ê6..............
0000 0000 0100 0000 2700 0000 0000 0000 ........'.......
0010 0000 2000 0000 0100 0000 0200 0501 .... ...........
48b7 7501 3080 c101 H·u.0€Á.

2003-02-18-03.44.02.593000 InstanceB2 Node:000
PID:1240(db2syscs.exe) TID:1968 Appid:*LOCAL.DB2.030703094551
buffer_pool_services sqlbwrpg Probe:1120 Database:PRO_DB
DIA3811C A locked file was encountered.
...
... (full of erorrs)
...
2003-02-18-03.44.03.515000 InstanceB2 Node:000
PID:1172(db2syscs.exe) TID:1968 Appid:*LOCAL.DB2.030218024403
base_sys_utilities sqledint Probe:0 Database:PRO_DB

Crash Recovery is needed.

2003-02-18-03.44.03.625000 InstanceB2 Node:000
PID:1172(db2syscs.exe) TID:1968 Appid:*LOCAL.DB2.030218024403
recovery_manager sqlpresr Probe:1 Database:PRO_DB
DIA3908W Crash recovery has been initiated. Lowtran LSN is
"00329E7F000C",
Minbuff LSN is "00329E7F000C".

2003-02-18-03.44.03.703000 InstanceB2 Node:000
PID:1172(db2syscs.exe) TID:1968 Appid:*LOCAL.DB2.030218024403
recovery_manager sqlprecm Probe:125 Database:PRO_DB

Using parallel recovery with 3 agents 3 QSets 21 queues and 125 chunks


2003-02-18-03.44.03.890000 InstanceB2 Node:000
PID:1172(db2syscs.exe) TID:1968 Appid:*LOCAL.DB2.030218024403
recovery_manager sqlprecm Probe:400 Database:PRO_DB
DIA3916W Forward phase of crash recovery has completed. Next LSN is
"00329E7F070B".

2003-02-18-03.44.04.078000 InstanceB2 Node:000
PID:1172(db2syscs.exe) TID:1968 Appid:*LOCAL.DB2.030218024403
recovery_manager sqlpresr Probe:170 Database:PRO_DB
DIA3909W Crash recovery completed. Next LSN is "00329E7F08D6".

On the machine we have: DB2 V7.2.3, WIN2k.

Thank's in advance

--
Posted via http://dbforums.com

In article <3085564.1057669656 (AT) dbforums (DOT) com>, member32772 (AT) dbforums (DOT) com
says...

Maybe some other backup tool is locking the database files?
If so you need to exclude the database directories from that backup.

Could there have been a virus scan program running that locked the file?

--
Garfield A. Lewis
DB2 UDB Development,
IBM Canada Laboratory


"mariborcan" <member32772 (AT) dbforums (DOT) com> wrote

There is no virus scan program or other backup tool!
Strange, isn't it?

--
Posted via http://dbforums.com

mariborcan <member32772 (AT) dbforums (DOT) com> wrote

We had a similar situation a while back. Our Network Administrators
swore they weren't running any automated backup software. That turned
out to be incorrect.

To finally catch the offender we used a free program to help determine
the
cause of this type of problem.

You can download filemon from,
"http://www.sysinternals.com/ntw2k/utilities.shtml"

Since your problem seems to occur at a known time it will be fairly
easy to start up filemon and show which programs are accessing the
file.

Good luck,
klh