What do I need to track down deadlocks that are appearing in the app-niku or bg-niku logs for Oracle?

Article Id: 52918
Status: Published
Updated On: 14-02-2018 06:43
Legacy Id: TEC510757
Products:
CA Identity Manager , CA Identity Governance , CA Identity Portal , STARTER PACK-CLARITY PPM
Issue/Introduction:

Description:

Under periods of heavy load or heavily intensive querying, database servers can experience deadlocking. Tracking such errors is time consuming and require a number of log files.

Solution:

To track down deadlocks, you can locate the following. These files are also useful if you provide those to CA Tech Support if you decide to create a support case.

  1. Any recent .trc files from the oracle\udump directory.

  2. The app-niku and bg-niku logs (make sure to include the logs spanning the time in which the problem occurred.).

  3. The app-access logs can be useful, but only if the enhanced logging is enabled. Please refer to the knowledgebase article, titled, "Clarity: How do I activate enhanced logging for app-access logs using Apache Tomcat?" for more information.

Keywords: deadlock, Oracle, udump, trc.

Environment:

Release: NCSVCS05900-8.1-Clarity-Service Connect-for MS-SQL
Component: