Oracle Monitoring Configuration

Configuring Oracle DB Monitoring

1. In the IT-Conductor main menu, navigate to Dashboards > Administrator.

Figure 1: IT-Conductor Dashboards Menu

2. In the Administrator dashboard, locate the Oracle Instances panel and click to start adding a system for monitoring.

Figure 2: Add a New Oracle Instance

3. In the Create New Oracle Instance, fill out all the necessary information. Click to add the system.

Figure 3: Create a New Oracle Instance

4. A pop-up message will confirm that the Oracle DBMS has been added successfully. Click OK to dismiss and proceed to configure the Oracle account to be used for monitoring.

Figure 4: Oracle DBMS Created Successfully

5. Provide the account information in the wizard and click to complete the configuration.

Note Please take note of the Oracle Monitoring configuration requirements.

Figure 5: Oracle Instance Account Information

6. A pop-up message will confirm that the JDBC Oracle account has been created successfully. Click OK to complete the process.

Figure 6: Oracle Account Confirmation

7. The newly added system will appear in the Oracle Instances panel.

Figure 8: Oracle Instances

Note It may take a few minutes to change the status to "In Progress," refresh the panel if needed. If there are issues with the configuration, such as wrong connection parameters or an invalid account etc. the status will stay "Ready", troubleshoot by displaying the log. Click for the new record or click object icon and select Log from the menu popup.

8. The Oracle Server will show up in the service grid within 5-15 minutes.

Figure 9: IT-Conductor Service Grid View

IT-Conductor Oracle Monitoring Configuration Requirements

When selecting an Oracle User, please ensure the user is granted CREATE SESSION and OEM_MONITOR role, and "SELECT ON V$DIAG_ALERT_EXT".

The latter two are only relevant when creating a new user used for monitoring.

Automation users may have different requirements depending on the nature of the automation activities.

Last updated

#660:

Change request updated