Release Notes › Known Issues › Tracking ID 644-72: Installation time-outs on Oracle CMSs

Tracking ID 644-72: Installation time-outs on Oracle CMSs

Under certain conditions, an installation process times out when you install CA DataMinder components into an existing Oracle database on the CMS or a gateway server. When a time-out occurs, you see this error message:

ORA-04021: timeout occurred while waiting to lock object 

This message indicates that a database object is locked by a separate database process. Consequently, the installation process cannot update or remove the object. The following list contains examples of database processes which, if running, can lock objects required by the installation process:

• iConsole searches or reports, including BusinessObjects reports for CA DataMinder
• Data warehousing jobs
• Database statistics collection, especially processes that call the CA DataMinder wgn_stats package
• Data ingestion processes. For example, CA DataMinder email agents, archive agents, and Event Import jobs, can conflict with the installation process when they write events into the CMS database
• DBAs running SQL Statements in SQL*Plus or SQL Developer, or in third-party tools such as SQL Navigator or TOAD
• Database purges, including infrastructure-based purges and partition-based purges

Where possible, we recommend that you allow these processes to complete before you retry the installation.

Alternatively, if there is no risk of data loss, you can terminate the locking process. For example, if you terminate a process that only queries the database (such as reports and searches), there is a low risk of data loss. Conversely, if you terminate a process that updates the database (such as data ingestion), the risk of data loss is considerably higher.

When the locking process has completed or been terminated, you can retry the installation.