How to work around with Synchronisation issue caused by frequent deadlock error ORA-04020

Follow

Read our docs This issue is encountered in ASM instance when there is an exclusive lock on the dba directory which dbvisit uses for copying files from ASM to the filesystem to transfer it. 


Problem Details

Problem Statement

How to work around with Synchronisation issue caused by frequent deadlock error ORA-04020

Applicable Error Code

ORA-04021: timeout occurred while waiting to lock object (DBD ERROR: OCIStmtExecute)

Affected Versions

v8 and v9

Affected Platforms

NA

 

Workaround

Step 1.  Stop dbvisit daemon on the primary server

Step 2. Use different DDC name 

cd /dbvisit/standby/conf

cp dbv_DEV.env dbv_DEVNEW.env

Step 3: Change dbvhost.sh file to a new name 

cp /dbvisit/standby/dbvhost_dev.sh /dbvisit/standby/dbvhost_devnew.sh 
Step 4. Send a log 
./dbvctl -d DEVNEW
After changing the DDC name the Directory name (DBVS_DEV_DEV to DBVS_DEVNEW_DEVNEW) is changed internally and we don't see the error
Have more questions? Submit a request

Comments