File xxx in use or locked by another process. LOCK_MAX_TIME_SEC: Return code = 603

[Arjen Visser]

I am continuously getting the following error message from my standby database every 15 mins but every time the log number is different. can you please help me resolve this

Dbvisit Standby Database Technology message from JACKSERP02
Message received from process: dbvisit.exe liveorcl
(Dbvisit Standby: 6.0.28.8679 Process id: 4968)
201207210845 - File E:\oracle\product\10.2.0\flash_recovery_area\LIVEO RCL\O1_MF_1_22682_80M4P8X5_.ARC.gz is in use or locked by another process. LOCK_MAX_TIME_SEC and LOCK_RETRY_TIMEOUT_MILLISEC can be set in Dbvisit Database configuration (DDC) file dbv_liveorcl.env to set parameters for retry.
Dbvisit Standby terminated.
Return code = 603

(Tracefile required if contacting Dbvisit Standby support: C:\temp\4968_dbvisit_liveorcl_201207210845.trc (server:JACKSERP02))
201207210845 - Log seq 22675 thread 1 applied to standby database liveorcl.
201207210845 - Log seq 22676 thread 1 applied to standby database liveorcl.
201207210845 - Log seq 22677 thread 1 applied to standby database liveorcl.
201207210845 - Log seq 22678 thread 1 applied to standby database liveorcl.
201207210845 - Log seq 22679 thread 1 applied to standby database liveorcl.
201207210845 - Log seq 22680 thread 1 applied to standby database liveorcl.
201207210845 - Log seq 22681 thread 1 applied to standby database liveorcl

Solution
The error message means that the archive is still being transferred from the primary server to the standby server. Dbvisit Standby tries to apply it to the standby server but because there is still a lock on the file (because it is being transferred) it cannot be applied. The next time Dbvisit Standby runs, the lock has been released so Dbvisit Standby can apply the archive log. That is why it is a different log every time.

There are 2 solutions:

1. Delay the time by 1 or 2 minutes that Dbvisit Standby on the standby database is being scheduled. So if Dbvisit Standby is being scheduled at 00,15,30,45, then set this to 03,18,33,48.
2. Increase the settings for LOCK_MAX_TIME_SEC in the DDC file dbv_liveorcl.env. It is currently set to 30. Suggested setting is 60. You can increase this further if you are still getting the error.