Discover Autonomous Database in Enterprise Manager (EM)


In Enterprise Manager (EM) release 13.4 and 13.5, the Autonomous Database can be discovered as a target along with your other target databases on-premise deployments.

In this post I will share with you on how easily you can discover your Autonomous Database.

Topology

The following topology depicts how a remote EM agent can be used to monitor the autonomous database.

Option 1 – An EM Agent on OMS (Oracle Management Service ) or OMR (Oracle Management Repository) can be used to remotely monitor the Autonomous Database (ADB).

Option 2 – Alternatively an EM agent on another compute or VM can be used to remotely monitor the Autonomous Database (ADB).

Prerequisites

1. In this example an Autonomous Transaction Processing Instance will be discovered and monitored by the Enterprise Manager deployed on OCI.

2. Connect to the Autonomous Database (via Database Actions or SQL Developer) and unlock ADBSNMP user account.

SQL> alter user adbsnmp identified by "<set_your_password>" account unlock;

3. Grant additional privileges required for ADB monitoring to the ADB_MONITOR role and then grant to ADBSNMP user.

SQL> grant create session,select_catalog_role,select any dictionary to ADB_MONITOR;
SQL> grant ADB_MONITOR to adbsnmp;

4. Download Client Credential (Wallet) for Autonomous Database.

5. Configure Network Rules for communication between EM and ADB. 

Network RequirementSourceDestinationPortProtocol
ADBSNMP MonitoringRemote Agent HostAutonomous Database Target1522TCP
Upload to EMRemote Agent HostOracle Management Service (OMS) Host4903TCP
Comm with AgentOracle Management Service (OMS) HostRemote Agent host3872TCP

a) Verify from Remote Agent Host that you can access the DB service and EM Upload port:

[oracle@agent_host ~]$ nc -zv adb.ap-sydney-1.oraclecloud.com 1522
Ncat: Version 7.50 ( https://nmap.org/ncat )
Ncat: Connected to 192.29.xxx.xxx:1522.
Ncat: 0 bytes sent, 0 bytes received in 0.01 seconds.
[oracle@agent_host ~]$

[oracle@agent_host ~]$ nc -zv emcc.xxx.com 4903
Ncat: Version 7.50 ( https://nmap.org/ncat )
Ncat: Connected to 10.0.x.x:4903.
Ncat: 0 bytes sent, 0 bytes received in 0.01 seconds.
[oracle@agent_host ~]$

b) Verify from OMS Host that you can communicated with Remote Agent Host:

[oracle@oms_host ~]$ nc -zv agent_host.xxx.com 3872
Ncat: Version 7.50 ( https://nmap.org/ncat )
Ncat: Connected to 10.0.x.x:3872.
Ncat: 0 bytes sent, 0 bytes received in 0.01 seconds.
[oracle@oms_host ~]$

6. Check for additional requirements for Service Gateway and IAM policies that are required for monitoring Autonomous Database in EM.

https://docs.oracle.com/en/enterprise-manager/cloud-control/enterprise-manager-cloud-control/13.5/emadb/prerequisite-tasks-autonomous-databases-shared.html

7. In OCI Console, create IAM Group eg. EMGroup

Allow group EMGroup to manage autonomous-database in compartment <compartment_for_Autonomous_Database>
Allow group EMGroup to read resource-availability in compartment <compartment_for_Autonomous_Database>
Allow group EMGroup to read limits in compartment <compartment_for_Autonomous_Database>

Allow group EMGroup to manage orm-stacks in compartment <compartment_for_EM_stack>
Allow group EMGroup to manage instance-family in compartment <compartment_for_EM_stack>
Allow group EMGroup to manage volume-family in compartment <compartment_for_EM_stack>
Allow group EMGroup to manage load-balancers in compartment <compartment_for_EM_stack>
Allow group EMGroup to manage virtual-network-family in compartment <compartment_for_EM_stack>
Allow group EMGroup to manage file-family in compartment <compartment_for_EM_stack>
Allow group EMGroup to manage autonomous-database-family in compartment <compartment_for_EM_stack>
Allow group EMGroup to manage orm-jobs in compartment <compartment_for_EM_stack>
Allow group EMGroup to read resource-availability in compartment <compartment_for_EM_stack>
Allow group EMGroup to read limits in compartment <compartment_for_EM_stack>

8. Deploy new or use existing EM Agent that will remotely monitor the target Autonomous Database.

Discover Autonomous Database Target

1. Login to EM Console.

2. Navigate to Setup > Add Target > Add Targets Manually

3. Click on Add Target Manually

4. Specify the Agent host that will be remotely monitoring the Autonomous Database.

(In my example, I will be using the EM Agent Host running on my OMS host: emcc.xxx.com, this EM agent can be on any host)

Choose Target Type (eg. Autonomous Transaction Processing)

Click Add

5. Complete the details for the Autonomous Database and then click on Test Connection

  • Target Name
  • Upload the Credential Wallet for the Autonomous Database
  • Wallet Password
  • Service Name
  • Monitoring Username (eg. adbsnmp) and password


Verify Connection is Successful

6. Click on Next

7. Review Details and then click on Submit

8. The target should now be discovered successfully.

9. From EM menu, navigate to TARGETS > DATABASES

10. You should now see the Autonomous Database discovered in the Database Target Page

This completes the discovery of the Autonomous Database in Enterprise Manager.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s