Oracle PL/SQL for DBAs

Window Logs

Like jobs, windows produce logging entries , which you can examine via the two data dictionary views described in the following sections.

Tip

You do not have the same ability to fine-tune the level and the retention period of the logs for window operations as you do for job operations.

DBA_SCHEDULER_WINDOW_LOG

When windows are created, altered, and dropped, the results are loaded into a summary table that is visible through the DBA_SCHEDULER_WINDOW_LOG view . Its columns are listed in the following table.

Column name	Description
LOG_ID	Unique identifier for the record.
LOG_DATE	Timestamp of the log entry.
WINDOW_NAME	Name of the window.
OPERATION	What happened to the window during the log entry (e.g., CLOSE, DISABLE, ENABLE, OPEN, UPDATE).
STATUS	What happened after the operation was performed by the job (e.g., SUCCEEDED, FAILED).
USER_NAME	Name of the user who invoked the job.
CLIENT_ID	The client identifier, if set using DBMS_SESSION.SET_IDENTIFIER, is recorded here. If this command was issued from Oracle’s Enterprise Manager or Grid Control, this column is populated as follows: SYSMAN@192.168.1.1@Mozilla/4.0 (compatible; MSIE 6.0; Windows N This example shows that the Grid Control user was SYSMAN, logged in from the IP address 192.168.1.1, and so on.
GLOBAL_UID	If the user is a global user, the global UID is recorded here.
ADDITIONAL_INFO	Any additional information is stored as a CLOB in this column. For example, if the program is disabled forcibly, ...