Data protection operation fails if operational lock file is not deleted


While performing an operation on the database, an operational lock file (sm_lock_dbsid) is created in $ORACLE_HOME/dbs to avoid multiple operations being executed on the database. This operational lock file is automatically deleted soon after the operation is completed. However, sometimes the operational lock file might not get deleted and the next operation fails.

The cataloging operation fails if the database name is missing form the \etc\oratab file. The operational lock file that was created is not deleted because SID of the database cannot be retrieved.

Error message

Operation failed. The database SID sid_value might be in use by another SnapCenter Plug-in for Oracle Database operation.

Failed to find entry for SID sid_value or database name database_name in /etc/oratab file on host.

Corrective action

You must manually delete the operational lock file by performing the following steps:

  1. From the command prompt, navigate to $ORACLE_HOME/dbs.
  2. Enter the following command:rm -rf .sm_lock_dbsid.