Writer instructions | |
|---|---|
Page title | For most spaces, this page must be titled Space announcements. For spaces with localized content, this page must be titled Space announcements l10n. |
Purpose | Provide an announcement banner on every page of your space. |
Location | Move this page outside of your home branch. |
Guidelines | |
Oracle Database Instance
This topic provides information about configuring the Oracle Database Instance by using Central Monitoring Administration.
Click to view a short video on how to configure an Oracle Database instance for monitoring in a TrueSight environment.
On the Add Monitor Types dialog, with the Monitoring Profile set to Oracle Database, and the Monitor Type set to Oracle Database Instance, provide the following details:
Field | Description |
|---|---|
Oracle Database Monitoring Configuration | |
Oracle Instance Information | |
Oracle Instance Name | Specify the Oracle instance name. |
Oracle Instance Home | Specify the Oracle home directory. |
Default Tablespace | Specify the default tablespace for database monitoring user. |
Temporary Tablespace | Specify the temporary tablespace for database monitoring user. |
Profile | Specify the user created profile. |
Remote Host Name | Specify the host name for remote monitoring. |
TNS Service String | Specify the TNS service string for remote monitoring. |
Privileged Database Account Credentials | |
User Name | Specify the database privileged user name. |
Password | Specify the database privileged password. |
Confirm Password | Re-type the database privileged password. |
Database Monitoring Account Credentials | |
User Name | Specify the database monitoring user name. |
Password | Specify the database monitoring password. |
Confirm Password | Re-type the database monitoring password. |
Filename cache frequency | Number of cycles for the next update of Oracle files location. Zero (0) means each cycle. |
Categories to be monitored | |
Categories to be monitored | Specify the category to be monitored. The available categories are Availability, Full, Custom. |
Oracle Failed Jobs Configurations Options | |
Generate detailed events (requires MRL) | Select this check box to generate a detailed event per job. |
Exclude disabled jobs | Select this check box to exclude the disabled jobs from the list of failed jobs. |
Exclude failed jobs | Specify the list of job names that you want to exclude from the list of failed jobs. Use comma (,) only to separate the names of the job. |
Exclude failed job IDs | Specify the list of job IDs that you want to exclude from the list of failed jobs. Use comma (,) only to separate the IDs of the job. |
Oracle Custom SQL Queries | |
Custom SQL Query | |
Query name | Specify the name of the query to identify. |
SQL query | Specify the query that you want to execute. |
Collection time (min) | Specify the time within which the query has to be executed. The time must be specified in minutes. |
Add to List | To add the queries to the list of Oracle instances, click the button. |
Modify Selection | To modify a query, from the list of Oracle instances, click the button. |
Remove from List | To remove a query, from the list of Oracle instances, click the button. |
Oracle User Configuration | |
User monitoring regular expression | To add users for monitoring, the KM uses this regex. Any existing and future users which answer this regex is monitored. |
Oracle Alert Log Filters Configurations Options | |
Exclude error log strings | Specify the list of strings that you want to exclude from the alert log monitoring. Use comma (,) only to separate the error log strings. |
Include error log strings | Specify the list of strings that you want to include in the alert log monitoring. Use comma (,) only to separate the error log strings. |
Oracle Debug Information | |
Oracle instance debug | Select this check box to turn on the debug. |
Configuring an MRL script for a detailed event per job
If you selected the option to generate detailed events for failed Oracle jobs, you must configure an MRL script so that the TrueSight console only displays events which are still open with an alarm status.
The KM will send an individual event for jobs in which the last execution status is:
FAILED | A job that has a failed status on the last run. |
BROKEN | A job that has a broken status on the last run. |
OVERDUE | The last attempt to start the job exceeded the set period of time (default: 2 minutes). |
LONG RUNNING | The last run of the job exceeded the set period of time (default: 60 minutes). |
To configure and deploy the MRL script:
- Write an MRL rule for closed events based on the following sample:
new ORACLE_KM_Jobs_Event_Close : PATROL_EV($NEW) where [ $NEW.status != CLOSED
AND $NEW.p_catalog == "ORACLE_JOBS"]
updates ALL PATROL_EV($OLD) where [$OLD.p_origin == $NEW.p_origin AND $OLD.mc_origin_key == listgetelt($NEW.p_args, 1)
{
$OLD.status = CLOSED ;
drop_new ;
}
END - Go to the \server\etc\<cellname>\kb\rules folder and open the .load file.
- Copy the MRL rule to the .load file and save the file.
- Compile the CELL, i.e. mccomp -n <cellname>.
- Restart the CELL.
Where to go from here
To configure the Remote host registration, see Remote Host Configuration.