Specifying New Target Monitoring Credentials in Enterprise Manager

To monitor the status and performance of your database targets, Enterprise Manager connects to your database using a database user name and password. The user is referred to as the database monitoring user; the user name and password combination is referred to as the database monitoring credentials.

When you first add, provision or clone an Oracle database target, by default Enterprise Manager uses the DBSNMP database user account and the password for the DBSNMP account as the monitoring credentials.

Alternatively, you may choose to use a different user as the database monitoring user. This new user must have the same roles and privileges as DBSNMP. To create this database monitoring user, refer to MOS note EM 13c: Creating the Oracle Database Monitoring Credentials for Oracle Enterprise Manager 13.5 RU4 (and later) DocID 2847191.1

non-DBSNMP Monitoring User Availability:

• Adding a an Oracle database: Enterprise Manager 13c Release 5 Update 4

• Database-as-a-Service: Enterprise Manager 13c Release 5 Update 8

• Oracle database provisioning (outside Exadata) and cloning: Enterprise Manager 13c Release 5 Update 8

• Oracle database provisioning for Exadata: Enterprise Manager 13c Release 5 Update 9

  (13.5.0.9)

Notes:

While discovery and monitoring of Oracle database targets works with non-DBSNMP users, there are management features that still assume DBSNMP as the database monitoring user.

These features include the following:

• Oracle Database Benchmarks such as CIS Oracle Database 19c Benchmark include assessments for the DBSNMP user. These assessments will continue to support only the DBSNMP user, and not other database users used as monitoring credentials
• For monitoring AVDF (Oracle Audit Vault and Database Firewall) targets, the use of non-DBSNMP users as monitoring credentials is not supported.