Configuring a Target Database for Secure Monitoring

You can enable secure monitoring either while discovering a target database, or by changing the secure monitoring settings for a selected target database after discovery.

Note:

DB monitoring setup accepts case-sensitive user names. .Every Oracle database object has a name. In a SQL statement, you represent the name of an object with a quoted identifier or a non-quoted identifier.

A quoted identifier begins and ends with double quotation marks (").

  • If you name a schema object using a quoted identifier, then you must use the double quotation marks whenever you refer to that object.
  • This is a case-sensitive identifier.

A nonquoted identifier is not surrounded by any punctuation.

  • This is not a case sensitive name.

When you set up the monitoring credentials you can provide either quoted (case-sensitive) or unquoted account names.

Follow these steps to change the settings of a discovered database target:
  1. From the Enterprise Manager page, choose Databases from the Targets menu.

    Enterprise Manager displays the Databases page.

  2. Choose the database for which you want to configure monitoring.

    The Database Home page for that database appears.

  3. From the Oracle Database menu, select Monitoring Configuration from the Target Setup menu.

    Enterprise Manager displays the Configure Database Instance: Properties page.

  4. On the Configure Database Instance: Properties page, scroll down to the Connection Protocol field and select from one of the following drop-down menu choices:

    • TCP -- Enterprise Manager connects to the target database for target monitoring using the TCP protocol. The data communication between the target database and the Enterprise Manager OMS happens in clear text form over the network.

    • TCPS -- Enterprise Manager connects to the target database TCP over a secure socket layer (SSL) for target monitoring. In this case, the client authenticates the database server using a trusted certificate of the server. The data communicates over the network between Enterprise Manager and the target database in encrypted form.

    • TCPS with Server Authentication using Kerberos -- Enterprise Manager connects to the target database TCP over a secure socket layer (SSL) for target monitoring. In this case, the client authenticates the database server using the Kerberos authentication protocol. The data communicates over the network between Enterprise Manager and the target database in encrypted form.

  5. Optionally you can test the connection by clicking Test Connection to determine whether the change in Connection Protocol has impacted the connection to the database.
  6. Click Next to move to the Configure Database Instance: Review Page.
  7. Click Submit to apply your changes.

    The database target now connects using the protocol you selected.