My Oracle Support Banner

How to Enable Tracing for PL/SQL Routines in the Enterprise Manager Grid Control Repository (Doc ID 435055.1)

Last updated on NOVEMBER 16, 2019

Applies to:

Enterprise Manager Base Platform - Version 10.2.0.1 to 11.1.0.1 [Release 10.2 to 11.1]
Information in this document applies to any platform.

Purpose

The Enterprise Manager Grid Control Repository consists of many PL/SQL routines which are executed by the OMS components for their operations. For example, the EMD_LOADER package which is used by the Loader for uploading files sent by the Target Agents into the Repository tables.

The PL/SQL code flow can be traced starting from Grid Control 10gR2 (Release 10.2.0.1 onwards). This feature can be very useful when debugging some SQL exception, or trying to narrow-down a problem with one of the internal OMS server sub-systems.

An example of use would be to find out which SQL statement in a repository DBMS_JOB EMD_MAINTENANCE procedure hits the ORA-01000 error (Max Open Cursors Limit Reached).

Scope

Enterprise Manager Grid Control users / Administrators who are trying to debug / troubleshoot a problem with any of the OMS components, having an associated pl/sql routine in the Repository.

Details

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Scope
Details
 Tracing Levels
 Contexts Types that can be Traced
 Steps for Enabling and Disabling the Tracing 
 Viewing the Trace Data
 Purging the Trace Data
 Best Practices

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.