Hi

We use db2 8.2.6 on windows 2000.

We got following error in our production DB
-------------------------------------------------
2008-02-14-23.40.16.168000+600 E1934574H468 LEVEL: Error
PID : 4016 TID : 4476 PROC : db2syscs.exe
INSTANCE: AXISPROD NODE : 000 DB : AXISRTDL
FUNCTION: DB2 UDB, data protection, sqlpgOrphanLogFile, probe:900
MESSAGE : ADM1510W A file sharing violation has occurred while accessing log
file "S0004103.LOG". Another process may be using this file. DB2
will try to delete it later.

2008-02-14-23.40.16.168000+600 I1935044H444 LEVEL: Error
PID : 4016 TID : 4476 PROC : db2syscs.exe
INSTANCE: AXISPROD NODE : 000 DB : AXISRTDL
FUNCTION: DB2 UDB, data protection, sqlpgRenameLogFile, probe:1120
RETCODE : ZRC=0x870F0016=-2029060074=SQLO_SHAR "File sharing violation."
DIA8519C A file sharing violation has occurred, filename was
"S0004103.LOG".
-------------------------------------------

The DB is working OK and the error has not happened again so far.


Any explanation as to why this has happened? Any thing can be done proactively to prevent this from happening?

Thanks

Harikumar

are you archiving the log ? to disk - tsm ?

No we do not use tsm.

Any suggestions as to the reasons for this error and how to avoid this. Bit wrorried as it is our productio database.


Regards

Harikumar

Hi Hari...

is ur problem resolved?? am also facing the same problem..

i will let you know my scenario...

last week my db2diag.log file was showing the below message.

MESSAGE : ADM1510W A file sharing violation has occurred while accessing log file "S0073564.LOG". Another process may be using this file. DB2
will try to delete it later.

Eventhough log file was archived and moved to archive log location, the file was existing in active log location.

We had a downtime last week and after instance restart we got the below message in db2diag.log file

MESSAGE : Deleting old log file S0073564.LOG

After restart the log file was deleted from the active log path

Again today morning i got file sharing violation message on another log file.

Let me know if you have any input on this?

Thanks,
Dharma.G

Hi Dharma,

No updates on this. We have not got this error for last few months. If you happen to get a solution let me know.


Hari Kumar

We had a similar problem sometime back and figured that some other process is locking the files needed by DB2. Some of the typical causes are virus scans and OS file system backups. If you have any of these running, they should not be accessing DB2 files. You need to exclude all DB2 related files when running such utilities. You might want to find out if this happens during a certain timeframe and see what all OS utilities are being run during that time. Hope this helps.