Skip Headers

Oracle Enterprise Manager Administrator's Guide
Release 9.0.2

Part Number A95407-01
Go To Documentation Library
Home
Go To Product List
Solution Area
Go To Table Of Contents
Contents
Go To Index
Index

Go to previous page Go to next page

D
Repository Views

The Enterprise Manger Configuration Assistant creates repository views whenever a new repository is created. These views are created on top of the repository tables. They enable users to view information from the repository without the danger of manipulating data the wrong way.

Administrator Views

SMP_VIEW_ADMINISTRATORS

This view shows a list of all administrators which have been defined on the machines. Information will be useful to system administrators.

The boolean values are represented as a numerical value so that you can change these values into a string appropriate for the Globalization Support settings which are currently active. These values can then be decoded into proper localized values when the report is run

Columns Descriptions

ADMINISTRATOR_NAME

Name of defined database administrator that is used throughout the repository

SUPERUSER

Shows whether the database administrator is a superuser.

Possible values: 1 (YES) and 0 (NO)

JOB_SYSTEM

Shows whether the database administrator can access the JOB system.

Possible values: 1 (YES) and 0 (NO)

EVENT_SYSTEM

Shows whether the database administrator can access the EVENT system.

Possible values: 1 (YES) and 0 (NO)

SMP_VIEW_ADMIN_CREDENTIALS

List of all the preferred credentials defined per administrator. Every target known in the navigator will have an entry in this view for each administrator who has setup preferred credentials for this target. This view is of interest for system administration.

Columns Descriptions

ADMINISTRATOR_NAME

Name of defined database administrator used throughout the repository

TARGET_NAME

Name of the target. The target name uniquely identifies the target. Several targets can exist with the same name, each with a different type.The column TARGET_NAME links with TARGET_NAME in the SMP_VIEW_NODE_SERVICES view.

TARGET_TYPE

Type of the target

TARGET_NLS_TYPE

Type string used for globalization support of the reports.

SMP_VIEW_ADMIN_SETUP

This view shows the notification setup per administrator. This information is important to system administrators.

Columns Descriptions

ADMINISTRATOR_NAME

Name of defined database administrator that is used throughout the repository. The ADMINISTRATOR_NAME column links with ADMINISTRATOR_NAME from the SMP_VIEW_ADMINISTRATORS view

EMAIL_ADDRESS

Email address defined for this administrator

EMAIL_TITLE

Title of the email message

PAGING_SERVICE

Name of the paging service to use for this administrator

PAGING_PIN

Paging pin code to use for this administrator

Service Views

SMP_VIEW_AGENTS

Shows topology information/details of all discovered Intelligent Agents on nodes in the Navigator. Manually added nodes are not included in this view.

Columns Descriptions

NODE_NAME

Name of the node. The NODE_NAME column links with NODE_NAME in the SMP_VIEW_NODES view.

AGENT_ALIAS

Name of the machine as recognized by the Agent

LAST_CHECKED

The last time and date this node was checked by the Management Server to see if it is reachable.

AGENT_TIMEZONE

Offset in hours

This value can be subtracted from the all times reported by this Intelligent Agent.

AGENT_STATUS

Current status of the Intelligent Agent.

Possible values: 1 (UP) and 0 (DOWN)

AGENT_STATE

Current condition of the Intelligent Agent.

Possible values: 1 (GOOD) and 0 (BAD)

OMS_MACHINE

Name of the Management Server machine servicing this node

This field is NULL if this is a manually added node.

This name is the canonical name of the Management Server machine. The OMS_MACHINE column links with OMS_MACHINE from the SMP_VIEW_OMS_MACHINES view.

SEVERITY

Aggregated alert severity of this target:

0 - No events registered against this target

15 - All events are clear

20 - One or more events are in Warning state

25 - One or more events are in Alert state

115 - Agent down, previous state was Clear

120 - Agent down, previous state was Warning

125 - Agent down, previous state was Alert

SMP_VIEW_TARGETS

Shows topology information, a list of all targets managed by Intelligent Agents, which potential targets are present in the repository for jobs and events. This view is a subset of the V$SMP_NODE_SERVICES view and contains only these targets which have an Intelligent Agent running on the node. Manually added targets will not show up in this view.

Columns Descriptions

TARGET_NAME

Name of the target. The TARGET_NAME combination uniquely identifies the target. Several targets can exist with the same name, each with a different type. The TARGET_NAME column links with TARGET_NAME in the SMP_VIEW_NODE_SERVICES view.

TARGET_TYPE

Type identifier of this target.

The type is the type returned by the Intelligent Agent.

Only two manually added target types are possible:

  • Nodes (oracle_sysman_node)

  • Databases (oracle_sysman_database)

TARGET_NLS_TYPE

Type string used for globalization support of the reports.

NODE_NAME

Name of node on which this target runs. The NODE_NAME column links with NODE_NAME in the SMP_VIEW_NODES view.

USERDATA

Parameters on how to contact this target

SEVERITY

Aggregated alert severity of this target.

0 - No events registered against this target

15 - All events are clear

20 - One or more events are in Warning state

25 - One or more events are in Alert state

115 - Agent down

SMP_VIEW_TARGET_PROPERTIES

Shows topology information, listing all the properties the Intelligent Agent has reported for this target. Only 8.1.7 or higher Agents will transmit target properties during discovery. Manually added nodes will never appear in this list, since they cannot have properties send over by the Intelligent Agent.

Columns Descriptions

TARGET_NAME

Name of the target. The TARGET_NAME combination uniquely identifies the target.Several targets can exist with the same name, each with a different type. The TARGET_NAME column links with TARGET_NAME in the SMP_VIEW_TARGETS view.

TARGET_TYPE

Type identifier of this target.

The type is the type returned by the Intelligent Agent.

TARGET_NLS_TYPE

Type string used for globalization support of the reports.

NAME

Name of the property

VALUE

Value of the property

SMP_VIEW_NODES

Shows Topology Information, list of all known nodes in the repository. Both manually added nodes as well as nodes managed by an Agent (nodes defined in the navigator) will be represented in this view. For each node, the current state of the Intelligent Agent running on the node will be reported.

The boolean values are represented as a numerical value so that these values can change into a string appropriate for the Globalization Support settings which are currently active.

These values can then be decoded into proper localized values when the report is run

Columns Descriptions

NODE_NAME

Name of the node. The NODE_NAME field is the name of the node defined in the navigator. The same name will also appear in the target list as target type, oracle_sysman_node.

DISCOVERY

Shows whether the node is discovered or manually added.

Possible values: 1 (AUTOMATIC) and 0 (MANUAL)

For all nodes with an operational Intelligent Agent, the DISCOVERY will be set to 1, the OMS_MACHINE and LAST_CHECKED fields will contain a value.

For all manually added nodes, the fields DISCOVERY and AGENT_STATUS will be set to 0, and the fields OMS_MACHINE and LAST_CHECKED will be set to NULL.

LAST_CHECKED

The last time and date this node was checked by the Management Server to see if it is reachable.

AGENT_STATUS

Current status of the Intelligent Agent.

Possible values: 1 (UP) and 0 (DOWN)

OMS_MACHINE

Name of the Management Server machine servicing this node.

This field is NULL if this is a manually added node.

This name is the canonical name of the Management Server machine.

The OMS_MACHINE column links with OMS_MACHINE from the SMP_VIEW_OMS_MACHINES view.

SMP_VIEW_NODE_SERVICES

Shows topology information which lists all targets present in the repository. Both manually added as well as targets managed by an Intelligent Agent will be represented in this view.

Columns Descriptions

TARGET_NAME

Name of the target. The TARGET_NAME combination uniquely identifies the target. Several targets can exist with the same name, each with a different type.

TARGET_TYPE

Type identifier of this target.

The type is the type returned by the Intelligent Agent.

TARGET_NLS_TYPE

Type string used for globalization support of the reports.

NODE_NAME

Name of node on which this target runs. The NODE_NAME column links with NODE_NAME in the SMP_VIEW_NODES view.

USERDATA

Parameters on how to contact this target

Group Views

SMP_VIEW_GROUPS

A System Administration view which lists all groups defined in the repository (Which groups are defined in the navigator).

The boolean values are represented as a numerical value so that these values can change into a string appropriate for the Globalization Support settings which are currently active.

These values can then be decoded into proper localized values when the report is run

Columns Descriptions

GROUP_NAME

Name of the group

DESCRIPTION

User description of this group

BACKGROUND_IMAGE

Image to use as a background for this group.

This is a physical path location to a file on the disc.

ICON_SIZE

Size of the icons.

Boolean field: 0 (SMALL) or 1 (LARGE)

SMP_VIEW_GROUP_SERVICES

A System Administration view which lists all targets in a group, showing which targets are placed into which group. This view contains only the targets defined in the group at that level

Columns Descriptions

GROUP_NAME

Name of the group. The GROUP_NAME column links with GROUP_NAME of the SMP_VIEW_GROUPS view.

TARGET_NAME

Name of the targets put in this group and if the target is nested in another group (Nested groups)

The TARGET_NAME column links with TARGET_NAME of the SMP_VIEW_NODE_SERVICES view.

TARGET_TYPE

Type of target

The type can be any of the registered types within the navigator. Since a group can be a target in another group

TARGET_NLS_TYPE

Type string used for globalization support of the reports.

SMP_VIEW_ALL_GROUP_ALL_SERVICES

A System Administration view which lists all targets in a group, recursively. If a group has a group as its member, all targets of the member group will be shown as well. The member groups themselves will not show up in the view as targets of the group.

Columns Descriptions

GROUP_NAME

Name of the group. The GROUP_NAME column links with GROUP_NAME of the SMP_VIEW_GROUPS view.

MEMBER_NAME

Name of the member group.

A group is also considered to be a member of itself

The MEMBER_NAME column links with GROUP_NAME of the SMP_VIEW_GROUPS view.

TARGET_NAME

Name of the targets put in this group. The TARGET_NAME column links with TARGET_NAME of the SMP_VIEW_NODE_SERVICES view.

TARGET_TYPE

Type of target

The type can be any of the registered types within the navigator.

TARGET_NLS_TYPE

Type string used for globalization support of the reports.

SMP_VIEW_TOP_GROUPS

Lists all views which are not part of other groups and have targets in them.

Columns Descriptions

GROUP_NAME

Logical name of the group

GROUP_OWNER

Administrator who created this group

DESCRIPTION

Description of the group

BACKGROUND_IMAGE

Background image used in the console

ICON_SIZE

Size of icons. Boolean field: 0 (SMALL) or 1 (LARGE)

Operational System Metrics

SMP_VIEW_OMS_MACHINES

An operational data view which lists all Management Servers currently connected to and working with the repository.

Columns Descriptions

OMS_MACHINE

Name of the machine

LAST_CHECKED

Timestamp of the last heartbeat of this Management Server, using the timezone of the Management Server machine.

SMP_VIEW_SESSIONS

An operational data view which lists all administrators logged on to this repository.

Columns Descriptions

ADMINISTRATOR_NAME

Name of database administrator currently connected. The ADMINISTRATOR_NAME column links with ADMINISTRATOR_NAME from the SMP_VIEW_ADMINISTRATORS view.

OMS_MACHINE

Name of Management Server machine the database administrator requested to login to.

This name is the canonical name of the Management Server machine.

The OMS_MACHINE column links with OMS_MACHINE from the SMP_VIEW_OMS_MACHINES view.

LOGIN_TIME

Time the administrator logged in on the Management Server machine

SMP_VIEW_NOTIFICATION_QUEUE

A view for diagnostics and debugging. It lists all the pending notifications still in the queue. The contents of this view will constantly change. If there are records in this view, the Management Server(s) do not have sufficient time to complete the work

Columns Descriptions

SEQUENCE_NUM

Internal number to process the notifications. Since the Management Server processes the notifications sorted on SEQUENCE_NUM, this may give an estimate of what is to be processed and when.

SUBSYSTEM

The subsystem who has generated this operation.

Can be:

VdeEvent - Events

VdjJob - Jobs

VdmNotificationManager - Notifications

NOTIFICATION_TYPE

The type of notification for the subsystem

NODE_NAME

Name of the node responsible for this operation. The NODE_NAME column links with NODE_NAME in the SMP_VIEW_NODES view.

TARGET_NAME

Name of the target responsible for this operation. The TARGET_NAME column links with TARGET_NAME in the SMP_VIEW_TARGETS view.

TARGET_TYPE

Type of target

TARGET_NLS_TYPE

Type string used for globalization support of the reports.

ADMINISTRATOR_NAME

Name of the administrator involved. The ADMINISTRATOR_NAME column links with ADMINISTRATOR_NAME from the SMP_VIEW_ADMINISTRATORS view.

TIMESTAMP

Time the notification was received

SMP_VIEW_NOTIFICATION_HISTORY

A diagnostics and debugging view which lists all the processed notifications. The notification history can be cleaned. The information in this view is only a snapshot of what is still in the repository.

The boolean values are represented as a numerical value so that these values can change into a string appropriate for the Globalization Support settings which are currently active.

These values can then be decoded into proper localized values when the report is run

Columns Descriptions

OBJECT_TYPE

The subsystem type who generated this notification

Currently the notification types are:

EVENT - Event subsystem

JOB - Job subsystem

OBJECT_ID

The ID of the object within the sub-system.

Events - EVENT_ID

Jobs - JOB_ID

The OBJECT_ID column links with either JOB_ID in the SMP_VIEW_JOBS view, or EVENT_ID in the SMP_VIEW_EVENTS view, depending on the value of OBJECT_TYPE.

TARGET_NAME

Name of the target responsible for this notification. The TARGET_NAME column links with TARGET_NAME in the SMP_VIEW_TARGETS view.

ADMINISTRATOR_NAME

Name of the administrator involved. The ADMINISTRATOR_NAME column links with ADMINISTRATOR_NAME from the SMP_VIEW_ADMINISTRATORS view.

METHOD

Notification method. Currently these methods are defined:

Email - SMTP

Paging - Paging Server

TIMESTAMP

Time the notification was send

STATUS

Shows whether the notification was sent successfully

Boolean field: 0 (NO) or 1 (YES)

OBJECT_STATUS

Status of the object

SMP_VIEW_OPERATION_QUEUE

A diagnostics and debugging view which lists all the pending operations still in the queue. The content of this view will constantly change. If there are records in this view, the Management Servers do not have sufficient time to complete the work

Columns Descriptions

OBJECT_ID

The ID of either a job or event

SUBSYSTEM

The subsystem who has generated this operation.

Can be:

VdeEvent - Events

VdjJob - Jobs

VdmNotificationManager - Notifications

OPERATION_TYPE

The type of operation for the subsystem

NODE_NAME

Name of the node responsible for this operation. The NODE_NAME column links with NODE_NAME in the SMP_VIEW_NODES view.

TARGET_NAME

Name of the target responsible for this operation. The TARGET_NAME column links with TARGET_NAME in the SMP_VIEW_NODE_SERVICES view.

TARGET_TYPE

Type of target

TARGET_NLS_TYPE

Type string used for globalization support of the reports.

ADMINISTRATOR_NAME

Name of the administrator involved. The ADMINISTRATOR_NAME column links with ADMINISTRATOR_NAME from the SMP_VIEW_ADMINISTRATORS view.

OMS_MACHINE

Management Server currently working on this operation.

Value will be NULL if not yet allocated

The OMS_MACHINE column links with OMS_MACHINE from the SMP_VIEW_OMS_MACHINES view.

Job Definition Views

SMP_VIEW_JOBS

A view of the Job Subsystem which lists all jobs present in the repository:

The boolean values are represented as a numerical value so that these values can change into a string appropriate for the Globalization Support settings which are currently active.

These values can then be decoded into proper localized values when the report is run

Columns Descriptions

JOB_ID

ID of this job.

The JOB_ID is an unique identifier for this job.

Since a job can be submitted at different times, and because the same job can be created more than once, the JOB_NAME is not enough to uniquely identify a job in the repository.

Therefore, all queries used to obtain job information must use the JOB_ID identifier.

JOB_NAME

Name of the group. JOB_NAME contains the name of the job as entered by the administrator.This name is not unique and can appear several times for different jobs.

ADMINISTRATOR_NAME

Name of the administrator owning this job. The ADMINISTRATOR_NAME column links with ADMINISTRATOR_NAME from the SMP_VIEW_ADMINISTRATORS view.

DESCRIPTION

Description of the job

TARGET_TYPE

Type of the targeted service. A job is always designed to run against a specific set of target targets.

This job type is represented by the TARGET_TYPE field which basically determines which different job tasks are possible for this job.

TARGET_NLS_TYPE

Type string used for globalization support of the reports.

FIXIT_JOB

Shows whether it is a fixit job

Boolean field: 0 (NO) or 1 (YES)

LIBRARY_JOB

Shows whether it is a job defined only in the library

Boolean field: 0 (NO) or 1 (YES)

INTERVAL_JOB

Shows whether it is a job to be executed in an interval

Boolean field: 0 (NO) or 1 (YES)

MODIFIED_BY

Name of the administrator who last modified this job. The MODIFIED_BY column links with ADMINISTRATOR_NAME from the SMP_VIEW_ADMINISTRATORS view.

MODIFIED_DATE

Time and date this job was last modified. The value of the MODIFIED_DATE field is specified in the time zone of the administrator who has modified it.

When the job is created, the first set of modification information is always the owner of the job and the creation date.

SMP_VIEW_JOB_EXECUTIONS

A view of the Job Subsystem which shows the status of each execution of a job. Only the end result of each execution is given in each view.

Columns Descriptions

JOB_ID

ID of this job.

The JOB_ID is an unique identifier for this job.

Since a job can be submitted at different times, and because the same job can be created more than once, the job_name is not enough to uniquely identify an job in the repository.

Therefore, all queries used to obtain job information must use the JOB_ID identifier.

The JOB_ID column links with JOB_ID of the SMP_VIEW_JOBS view.

JOB_NAME

Name of the job. JOB_NAME contains the name of the job as entered by the administrator.

This name is not unique and can appear several times for different jobs.

NODE_NAME

Name of the node on which this job is running. The NODE_NAME column links with NODE_NAME in the SMP_VIEW_NODES view.

TARGET_NAME

Target this job is scheduled/submitted for. The TARGET_NAME combination uniquely identifies the target this job was meant for. Several targets can be present for any particular job.

The TARGET_NAME column links with TARGET_NAME of the SMP_VIEW_NODE_SERVICES view.

TARGET_TYPE

Type of the targeted service

TARGET_NLS_TYPE

Type string used for globalization support of the reports.

ADMINISTRATOR_NAME

Name of the administrator who owns this job. The ADMINISTRATOR_NAME column links with ADMINISTRATOR_NAME from the SMP_VIEW_ADMINISTRATORS view.

EXEC_NUM

The execution number. The EXEC_NUM field represents the number of times the job was actually scheduled against a particular target. For each time the job gets to status SCHEDULED, this number is increased by 1.

For the SUBMITTED state, the EXEC_NUM value will always be 0, as the Intelligent Agent has not responded for this job yet.

TIMESTAMP

Time the action was recorded. The timestamp is the time of the job occurrence on the Intelligent Agent side.

STATUS

Status of the job notification

  • 1 - Submitted - The Management Server has submitted the request to the Intelligent Agent and is waiting for a confirmation

  • 2 - Scheduled - The Intelligent Agent has responded to the submit request and is now waiting till the actual execution time for the job to get executed

  • 4 - Running - The job has been started

  • 9 - Completed - The job terminated successfully (with an exit code of zero 0)

  • 11 - Failed - The job failed. The exit code was non-zero

  • 13 - Pending delete - An administrator requested a delete of a scheduled job. Waiting on Intelligent Agent confirmation

  • 14 - Deleted - The Intelligent Agent has confirmed the delete of the job

The status 0 can never appear in this view as library jobs have no active status and do not interact with the Intelligent Agent.

Also, status 15 cannot appear in this view as this is also not an active status of a job.

SMP_VIEW_JOB_HISTORY

A Job Subsystem view which shows the history of all the job executions. It is only a snapshot of the available information since the job history can be cleanup up and jobs can get manually deleted. It presents information about when and how the job was executed and an overview of the job at this time.

Columns Descriptions

JOB_ID

ID of this job. The JOB_ID is an unique identifier for this job.

Since a job can be submitted at different times, and because the same job can be created more than once, the job_name is not enough to uniquely identify an job in the repository.

Therefore, all queries used to obtain job information must use the JOB_ID identifier.

The JOB_ID column links with JOB_ID of the SMP_VIEW_JOBS view.

JOB_NAME

Name of the job. JOB_NAME contains the name of the job as entered by the administrator.

This name is not unique and can appear several times for different jobs.

TARGET_NAME

Target this job is scheduled/submitted for. The TARGET_NAME combination uniquely identifies the target this job was meant for. Several targets can be present for any particular job.

The TARGET_NAME column links with TARGET_NAME of the SMP_VIEW_NODE_SERVICES view.

TARGET_TYPE

Type of the targeted service

TARGET_NLS_TYPE

Type string used for globalization support of the reports.

EXEC_NUM

The execution number. The EXEC_NUM field represents the number of times the job was actually scheduled against a particular target. For each time the job gets to status SCHEDULED, this number is increased by 1.

For the SUBMITTED state, the EXEC_NUM value will always be 0 as the Intelligent Agent has not responded for this job yet.

TIMESTAMP

Time the action was recorded. The timestamp is the time of the job occurrence on the Intelligent Agent side.

STATUS

Status of the job notification

  • 1 - Submitted - The Management Server has submitted the request to the Intelligent Agent, and is waiting for a confirmation

  • 2 - Scheduled - The Intelligent Agent has responded to the submit request, and is now waiting till the actual execution time for the job to get executed

  • 4 - Running - The job has been started

  • 9 - Completed - The job terminated successfully (with an exit code of zero 0)

  • 11 - Failed - The job failed. The exit code was non-zero

  • 13 - Pending delete - An administrator requested a delete of a scheduled job. Waiting on Intelligent Agent confirmation

  • 14 - Deleted - The Intelligent Agent has confirmed the delete of the job

SMP_VIEW_JOB_STATUS

A job subsystem view which shows the current status of all active jobs. One line will appear in this view for each target this job is submitted against. For library jobs, the NODE_NAME field is NULL, and the STATUS and EXEC_NUM fields are forced to 0 since no actual executions have taken place. Only active jobs are represented in this view.

Columns Descriptions

JOB_ID

ID of this job.

The JOB_ID is an unique identifier for this job. Since a job can be submitted at different times, and because the same job can be created more than once, the job_name is not enough to uniquely identify an job in the repository.Therefore, all queries used to obtain job information must use the JOB_ID identifier.

The JOB_ID column links with JOB_ID in the SMP_VIEW_JOBS view.

JOB_NAME

Name of the job. JOB_NAME contains the name of the job as entered by the administrator.This name is not unique and can appear several times for different jobs.

NODE_NAME

Name of the node on which this job is running

The name of the node will be NULL for library jobs

The NODE_NAME column links with NODE_NAME in the SMP_VIEW_NODES view.

TARGET_NAME

The target this job is scheduled/submitted for. The TARGET_NAME, TARGET_TYPE combination uniquely identifies the target this job was meant for.Several targets can be present for any particular job.

The TARGET_NAME column links with TARGET_NAME in the SMP_VIEW_TARGETS view.

TARGET_TYPE

Type of the targeted service

TARGET_NLS_TYPE

Type string used for globalization support of the reports.

ADMINISTRATOR_NAME

Name of the administrator who owns this job. The ADMINISTRATOR_NAME column links with ADMINISTRATOR_NAME from the SMP_VIEW_ADMINISTRATORS view.

EXEC_NUM

The execution number. The EXEC_NUM field represents the number of times the job was actually scheduled against a particular target. For each time the job gets to status SCHEDULED, this number is increased by 1. For the SUBMITTED state, as well as library jobs, the EXEC_NUM value will always be 0, as the Intelligent Agent has not responded for this job yet.

TIMESTAMP

Time the job notification was recorded

STATUS

Status of the job:

  • 1 - Submitted - The Management Server has submitted the request to the Intelligent Agent and is waiting for a confirmation

  • 2 - Scheduled - The Intelligent Agent has responded to the submit request, and is now waiting till the actual execution time for the job to get executed

  • 4 - Running - The job has been started

  • 9 - Completed - The job terminated successfully (with an exit code of zero 0)

  • 11 - Failed - The job failed. The exit code was non-zero

  • 13 - Pending delete - An administrator requested a delete of a scheduled job. Waiting on Intelligent Agent confirmation

  • 14 - Deleted - The Intelligent Agent has confirmed the delete of the job

  • 15 - Expired - The finish time for an internal job has passed

SMP_VIEW_AGENT_JOBS

View of job subsystem with overview of all active jobs with the Intelligent Agent specific information.

The boolean values are represented as a numerical value so that these values can change into a string appropriate for the Globalization Support settings which are currently active.

These values can then be decoded into proper localized values when the report is run

Columns Descriptions

JOB_ID

ID of this job.

The JOB_ID is an unique identifier for this job.

Since a job can be submitted at different times, and because the same job can be created more than once, the job_name is not enough to uniquely identify an job in the repository.

Therefore, all queries used to obtain job information must use the JOB_ID identifier.

AGENT_ID

ID attributed by the Intelligent Agent for this job.

The AGENT_ID is the unique Intelligent Agent ID for this job. This ID is unique for this Intelligent Agent, although others Intelligent Agents can attribute the same ID to a job or event.

JOB_NAME

Name of the group. JOB_NAME contains the name of the job as entered by the administrator.

This name is not unique, and can appear several times for different jobs.

ADMINISTRATOR_NAME

Name of the administrator owning this job. The ADMINISTRATOR_NAME column links with ADMINISTRATOR_NAME from the SMP_VIEW_ADMINISTRATORS view.

DESCRIPTION

Description of the job

NODE_NAME

Node on which this job is running. The NODE_NAME column links with NODE_NAME in the SMP_VIEW_NODES view.

TARGET_NAME

Name of the targeted service. The TARGET_NAME column links with TARGET_NAME in the SMP_VIEW_TARGETS view.

TARGET_TYPE

Type of the targeted service. A job is always designed to run against a specific set of target targets.

This job type is represented by the TARGET_TYPE field, which basically determines which different job tasks are possible for this job.

TARGET_NLS_TYPE

Type string used for globalization support of the reports.

FIXIT_JOB

Shows whether it is a fixit job

Boolean field: 0 (NO) or 1 (YES)

INTERVAL_JOB

Shows whether the job is to be executed in an interval

Boolean field: 0 (NO) or 1 (YES)

EXEC_NUM

The execution number. The EXEC_NUM field represents the number of times the job was actually scheduled against a particular target. For each time the job gets to status SCHEDULED, this number is increased by 1.

For the SUBMITTED state, the EXEC_NUM value will always be 0, as the Intelligent Agent has not responded for this job yet.

MODIFIED_BY

Name of the administrator who last modified this job. The MODIFIED_BY column links with ADMINISTRATOR_NAME from the SMP_VIEW_ADMINISTRATORS view.

MODIFIED_DATE

Time and date this job was last modified. The value of the MODIFIED_DATE field is specified in the timezone of the administrator who has modified it.

When the jobs is created, the first set of modification information is always the owner of the job and the creation date.

STATUS

Status of the job condition

1 - Submitted

2 - Scheduled

4 - Running

9 - Completed successfully

11 - Job failed

13 - Pending delete

14 - Job deleted

15 - Job expired

STARTED

Time and date the job started

FINISHED

Time and date the job finished

NEXT_EXEC

Time and date for the next execution.

Only valuable for interval jobs

AGENT_STATUS

Shows whether an Intelligent Agent is currently running

Boolean field: 0 (DOWN) or 1 (UP)

Event Definition Views

SMP_VIEW_EVENTS

A view of the Event Subsystem which lists all events defined in the repository, only 1 line for each event defined in the repository.

The boolean values are represented as a numerical value so that these values can change into a string appropriate for the Globalization Support settings which are currently active.

These values can then be decoded into proper localized values when the report is run

Columns Descriptions

EVENT_ID

Uniquely distinguishes events from each other. The EVENT_ID is an unique identifier for this job.

Since a event can be registered and de-registered at different times, and because the same event can be registered against more than one target, the EVENT_NAME is not enough to uniquely identify an event in the repository.

Therefore, all queries used to obtain event information must use the EVENT_ID identifier.

The EVENT_ID column links with EVENT_ID from the SMP_VIEW_EVENTS view.

EVENT_NAME

Name of this event

ADMINISTRATOR_NAME

Name of the administrator who created this event. The ADMINISTRATOR_NAME column links with ADMINISTRATOR_NAME from the SMP_VIEW_ADMINISTRATORS view.

DESCRIPTION

Description of the event

NODE_NAME

Node on which this event is running. The NODE_NAME column links with NODE_NAME from the SMP_VIEW_NODES view.

TARGET_TYPE

Type of target this event is meant for

TARGET_NLS_TYPE

Type string used for globalization support of the reports.

LIBRARY_EVENT

Shows whether an event is saved in the event library

Boolean field: 0 (NO) or 1 (YES)

FIXIT_JOB_ID

ID of the fixit job to execute when this event triggers

Value is ZERO (0) if no fixit associated with this event.

UNSOLICITED

Shows whether it is a 3rd party event

Boolean field: 0 (NO) or 1 (YES)

SNMP_TRAP

Shows whether an SNMP trap is sent when event triggers

Boolean field: 0 (NO) or 1 (YES)

SMP_VIEW_EVENT_HISTORY

View of event subsystem with historical overview of all event occurrences currently in the repository.

The boolean values are represented as a numerical value so that these values can change into a string appropriate for the Globalization Support settings which are currently active.

These values can then be decoded into proper localized values when the report is run

Columns Descriptions

EVENT_ID

Needed to uniquely distinguish events from each other. The EVENT_ID is an unique identifier for this job.

Since a event can be registered and de-registered at different times, and because the same event can be registered against more than one target, the EVENT_NAME is not enough to uniquely identify an event in the repository.

Therefore, all queries used to obtain event information must use the EVENT_ID identifier.

The EVENT_ID column links with EVENT_ID from the SMP_VIEW_EVENTS view.

EVENT_NAME

Name of this event.

OCCURRENCE_ID

Sequence number of event occurrences. These numbers are not necessarily consecutive

NODE_NAME

Name of the node on which this event is running. The NODE_NAME column links with NODE_NAME from the SMP_VIEW_NODES view.

TARGET_NAME

Name of the target that caused the event to trigger. An event is always registered against a specific set of target services.

This event type is represented by the TARGET_TYPE field, which basically determines which different event tests are possible for this event.

The TARGET_NAME column links with TARGET_NAME from the SMP_VIEW_NODE_SERVICES view.

TARGET_TYPE

Type of target this event is meant for

TARGET_NLS_TYPE

Type string used for globalization support of the reports.

OWNER

Administrator who is currently assigned to check this occurrence.

The OWNER column links with ADMINISTRATOR_NAME from the SMP_VIEW_ADMINISTRATORS view.

TIMESTAMP

Date/Time this occurrence happened

MESSAGE

Specific occurrence text

AGENT_STATUS

Current status of the Intelligent Agent

Boolean field: 0 (DOWN) or 1 (UP)

SEVERITY

Current severity level of this occurrence

ACTIVE

Shows whether this event occurrence is still outstanding in the console

Boolean field: 0 (NO) or 1 (YES)

SMP_VIEW_EVENT_TEST_HISTORY

View of event subsystem with historic overview of the notifications of all tests per events present in the repository.

The boolean values are represented as a numerical value so that these values can change into a string appropriate for the Globalization Support settings which are currently active.

These values can then be decoded into proper localized values when the report is run

Columns Descriptions

EVENT_ID

Needed to uniquely distinguish events from each other. The EVENT_ID is an unique identifier for this job.

Since a event can be registered and de-registered at different times, and because the same event can be registered against more than one target, the EVENT_NAME is not enough to uniquely identify an event in the repository.

Therefore, all queries used to obtain event information must use the EVENT_ID identifier.

The EVENT_ID column links with EVENT_ID from the SMP_VIEW_EVENTS view.

EVENT_NAME

Name of this event

TEST_ID

Needed to uniquely distinguish this test from other tests within the event

EVENT_TEST

Name of the test within the event

OCCURRENCE_ID

Sequence number of event occurrences. These numbers are not necessarily consecutive

NODE_NAME

Name of the node on which this event is running. The NODE_NAME column links with NODE_NAME from the SMP_VIEW_NODES view.

TARGET_NAME

Name of the target that caused the event to trigger. The TARGET_NAME column links with TARGET_NAME from the SMP_VIEW_NODE_SERVICES view.

TARGET_TYPE

Type of target this event is meant for. An event is always registered against a specific set of target targets.

This event type is represented by the TARGET_TYPE field, which basically determines which different event tests are possible for this event.

TARGET_NLS_TYPE

Type string used for globalization support of the reports.

OWNER

Administrator who is currently assigned to check this occurrence. The OWNER column links with ADMINISTRATOR_NAME from the SMP_VIEW_ADMINISTRATORS view.

TIMESTAMP

Date/Time this occurrence happened

MESSAGE

Specific occurrence text

EVENT_SEVERITY

Overall severity level of the event

TEST_SEVERITY

Severity level of the test within the event

ACTIVE

Shows whether this event occurrence is still outstanding in the console.

Boolean field: 0 (NO) or 1 (YES)

SMP_VIEW_EVENT_STATUS

View of Event Subsystem showing current status of all events present in the repository.

The boolean values are represented as a numerical value so that these values can change into a string appropriate for the Globalization Support settings which are currently active.

These values can then be decoded into proper localized values when the report is run

Columns Descriptions

EVENT_ID

Needed to uniquely distinguish events from each other. The EVENT_ID is an unique identifier for this job.

Since a event can be registered and de-registered at different times, and because the same event can be registered against more than one target, the EVENT_NAME is not enough to uniquely identify an event in the repository.

Therefore, all queries used to obtain event information must use the EVENT_ID identifier.

The EVENT_ID column links with EVENT_ID from the SMP_VIEW_EVENTS view.

EVENT_NAME

Name of this event

NODE_NAME

Name of the node on which this event is running. The NODE_NAME column links with NODE_NAME from the SMP_VIEW_NODES view.

TARGET_NAME

Name of the target that caused the event to trigger. The TARGET_NAME column links with TARGET_NAME from the SMP_VIEW_NODE_SERVICES view.

TARGET_TYPE

Type of target this event is meant for

An event is always registered against a specific set of target targets.

This event type is represented by the TARGET_TYPE field, which basically determines which different event tests are possible for this event.

TARGET_NLS_TYPE

Type string used for globalization support of the reports.

ADMINISTRATOR_NAME

Name of the administrator who owns this event. The ADMINISTRATOR_NAME column links with ADMINISTRATOR_NAME from the SMP_VIEW_ADMINISTRATORS view.

TIMESTAMP

Date/Time this occurrence happened

EVENT_STATUS

Current status of this event

204: Pending registration

205: Registered

206: Registration failed

207: Pending deregistration

208: Deregistered

AGENT_STATUS

Current status of the Intelligent Agent

Boolean field: 0 (DOWN) or 1 (UP)

If the Intelligent Agent is DOWN or BAD, this boolean field will be marked as DOWN

SEVERITY

Current severity level of this event

15 - clear

20 - warning

25 - alert

SMP_VIEW_EVENT_TESTS

View of event subsystem with list of all tests defined per event.

Columns Descriptions

EVENT_ID

Needed to uniquely distinguish events from each other. The EVENT_ID is an unique identifier for this job.

Since a event can be registered and de-registered at different times, and because the same event can be registered against more than one target, the EVENT_NAME is not enough to uniquely identify an event in the repository.

Therefore, all queries used to obtain event information must use the EVENT_ID identifier.

The EVENT_ID column links with EVENT_ID from the SMP_VIEW_EVENTS view.

EVENT_NAME

Name of this event

EVENT_TEST

Internal name of the event test

SMP_VIEW_AGENT_EVENTS

View of Event Subsystem showing Intelligent Agent specific information about all registered events.

The boolean values are represented as a numerical value so that these values can change into a string appropriate for the Globalization Support settings which are currently active.

These values can then be decoded into proper localized values when the report is run

Columns Descriptions

EVENT_ID

Needed to uniquely distinguish events from each other. The EVENT_ID is an unique identifier for this job.

Since a event can be registered and de-registered at different times, and because the same event can be registered against more than one target, the EVENT_NAME is not enough to uniquely identify an event in the repository.

Therefore, all queries used to obtain event information must use the EVENT_ID identifier.

The EVENT_ID column links with EVENT_ID from the SMP_VIEW_EVENTS view.

AGENT_ID

ID attributed by the Intelligent Agent for this event.

EVENT_NAME

Name of this event

EVENT_TEST

Specific test the Intelligent Agent has to evaluate

ADMINISTRATOR_NAME

Name of the administrator who created this event. The ADMINISTRATOR_NAME column links with ADMINISTRATOR_NAME from the SMP_VIEW_ADMINISTRATORS view.

DESCRIPTION

Description of the event

NODE_NAME

Node on which this event is running. The NODE_NAME column links with NODE_NAME from the SMP_VIEW_NODES view.

TARGET_NAME

Name of the target this event is meant for. The TARGET_NAME column links with TARGET_NAME in the SMP_VIEW_TARGETS view.

TARGET_TYPE

Type of target this event is meant for

TARGET_NLS_TYPE

Type string used for globalization support of the reports.

FIXIT_JOB_ID

ID of the fixit job to execute when this event triggers Value is ZERO (0) if no fixit associated with this event.

UNSOLICITED

Shows whether this is a 3rd party event

Boolean field: 0 (NO) or 1 (YES)

SNMP_TRAP

Shows whether to send an SNMP trap when event triggers

Boolean field: 0 (NO) or 1 (YES)

SEVERITY

Current severity level of this event

15 - clear

20 - warning

25 - alert

AGENT_STATUS

Shows whether the Intelligent Agent is currently running

Boolean field: 0 (DOWN) or 1 (UP)

Capacity Planner and Data Gatherer Collections

SMP_VIEW_COLLECTIONS

Capacity Planner view showing list of defined Capacity Planner collections in the repository.

The boolean values are represented as a numerical value so that these values can change into a string appropriate for the Globalization Support settings which are currently active.

These values can then be decoded into proper localized values when the report is run

Columns Descriptions

DG_NAME

Name of node on which the Data Gatherer is running which is collecting the information.

NODE_NAME

Name of node on which this collection runs. The NODE_NAME column links with NODE_NAME from the SMP_VIEW_NODES view.

TARGET_NAME

Name of the target for which this collection is defined. The TARGET_NAME column links with TARGET_NAME from the SMP_VIEW_NODE_SERVICES view.

TARGET_TYPE

Type identifier of this target.

TARGET_NLS_TYPE

Type string used for globalization support of the reports.

ADMINISTRATOR_NAME

Name of the administrator owning this collection. The ADMINISTRATOR_NAME column links with ADMINISTRATOR_NAME from the SMP_VIEW_ADMINISTRATORS view.

ACTIVE

Shows whether the collection is still active

Boolean field: 0 (NO) or 1 (YES)

LOCAL

Shows whether the collection is stored locally in the repository

Boolean field: 0 (NO) or 1 (YES)


Go to previous page Go to next page
Oracle
Copyright © 2002 Oracle Corporation.

All Rights Reserved.
Go To Documentation Library
Home
Go To Product List
Solution Area
Go To Table Of Contents
Contents
Go To Index
Index