Procedure
1. If you still have high CPU usage issues even after ensuring proper connectivity
across firewalls, open a problem report with IBM Software Support or refer to
the IBM Support Portal (http://www.ibm.com/support/entry/portal/
software).
2. For more information, see the “Firewalls” topics in the IBM Tivoli Monitoring
Installation and Setup Guide.
Resolving Oracle DB Agent problems - diagnostic actions
Oracle DB Agent problems, such as a cursor performance problem can be resolved
by setting an environment variable to disable problematic cursors.
Procedure
Diagnostic actions
1. Collect the detail traces of collector and RAS1 log. See the problem
determination topics for enabling detailed tracing in the collector trace log and
setting RAS trace parameters in the IBM Tivoli Monitoring for Databases: Oracle
Agent User's Guide.
2. Identify the SQL query that caused the high CPU usage issues from the
collector logs.
3. You can identify the SQL query that caused the high CPU usage issue from
ITM Oracle Agent logs or the Oracle tools. Use the following procedure to
identify the problematic cursors from ITM Oracle Agent logs:
a. Open the collector logs and find CFE1645 messages. The messages show the
return time of each cursors. For example: CFE1645T (165929) Time =
2008/06/06 16:59:29, collected records in 6 seconds.
b. The default timeout value of ITM Oracle Agent is 45 seconds. If it takes
more than 45 seconds, it might cause a timeout problem and Open Probe
pipe error will be reported in the collector log. CFE1645T (170246) Time =
2008/06/06 17:02:46, collected records in 203 seconds
c. When a timeout happens, review the previous cursor that executed before
this message. For example:
PDR3000T (170002) Deleting (1) rows for cursor DB6
RPF0300T (170002) Doing prep_l_fet for cursor DB6
ORU0085I (170002) --------------------------------------------------
ORU0090I (170002) Starting new SQL query.
ORU0095I (170002) <SELECT /*+RULE*/ COUNT(*) EXTENTS FROM SYS.DBA_EXTENTS >
ORU0085I (170002) --------------------------------------------------
CAT1610I (170213) Dump of row 1
UPX0100T 000: 20202020 20202020 20202032 34313135 * 24115*
4. The previous cursor (DB6) took about 2 minutes and 11 seconds to return data
causing the performance problem.
5. Were you able to identify an SQL query?
v Yes: Continue to the corrective actions task.
Resolving Oracle DB Agent problems - corrective actions
Oracle DB agent problems, such as problematic cursors can be resolved by setting
environment variables and overriding variable settings.
32 IBM Tivoli Monitoring: Troubleshooting Guide
To Next Page
Loading...
Need help?
General
