Monitor a Database with Enterprise Manager Database Control

This article explains how to set up an Enterprise Manager Database Control console to monitor the database.

By default, the Enterprise Manager Database Control console is not enabled on version 11.2.0.4 databases. You can enable the console:

when you create a container database by using the Database Commands with the -co parameter.
for an existing container database as described in Configuring Database Control Using EMCA.

Port 1158 is the default port used for the first console enabled on the DB system, but each additional console enabled on the DB system will have a different port.

Note:

For a version 11.2.0.4 database on a 2-node RAC DB system, see Enable the Console For a Version 11.2.0.4 Database On a Multi-node DB System.

Required IAM Policy

Some of the procedures below require permission to create or update security lists. For more information about security list policies, see Security Lists.

Related Topics

Monitor a Database with Enterprise Manager Express

Determine the Port For the Enterprise Manager Database Control Console

SSH to the DB system, log in as opc, and sudo to the oracle user.

sudo su - oracle
. oraenv
 <provide the database SID at the prompt>

Use the following command to get the port number.

emctl status dbconsole

The port is in the URL, as shown in the following output:

Oracle Enterprise Manager 11g Database Control Release 11.2.0.4.0
Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.
https://dbprod:1158/em/console/aboutApplication
Oracle Enterprise Manager 11g is running.
------------------------------------------------------------------
Logs are generated in directory /u01/app/oracle/product/11.2.0.4/dbhome_2/dbprod_db11/sysman/log

Open the console's port as described in Open Ports on the DB System.
Update the security list for the console's port as described in Update the Security List for the DB System.

Connect to the Enterprise Manager Database Control Console

After you've enabled the console and opened its port in the security list and iptables, you can connect as follows:

From a web browser, connect to the console using the following URL format:
```
https://<ip_address>:<port>/em
```
For example, https://129.145.0.164:1158/em

Use the DB system's private or public IP address depending on your network configuration.

Use the private IP address to connect to the system from your on-premises network, or from within the Virtual Cloud Network (VCN). This includes connecting from a host located on-premises connecting through a VPN or FastConnect to your VCN, or from another host in the same VCN. Use the public IP address to connect to the system from outside the cloud (with no VPN). You can find the IP addresses in the Console as follows:
- On the DB System Details page, under Resources, click Nodes.
- The Public IP address and Private IP address & DNS name are displayed in the table columns.
A login page will be displayed and you can log in with any valid database credentials.

To learn more about Enterprise Manager Database Control, see Introduction to Oracle Enterprise Manager Database Control.

Enable the Console For a Version 11.2.0.4 Database On a Multi-node DB System

A few extra steps are required to enable the console for a version 11.2.0.4 database on a multi-node DB system.

Configure SSH Equivalency Between the Two Nodes

You'll create SSH keys on each node and copy the key to the other node, so that each node has the keys for both nodes. The following procedure uses the sample names node1 and node2.

SSH to node1, log in as opc, and sudo to the oracle user.
```
sudo su - oracle
```
Create a directory called .ssh, set its permissions, create an RSA key, and add the public key to the authorized_keys file.
```
mkdir .ssh
chmod 755 .ssh
ssh-keygen -t rsa
cat id_rsa.pub > authorized_keys 
```
Repeat the previous steps on the other node in the cluster.
On each node, add the id_rsa.pub key for the other node to the authorized_keys file.
When you're done, you should see both keys in authorized_keys on each node.
On node1, create the known_hosts file by doing the following:
- SSH to node1 and reply yes to the authentication prompt.
- SSH to node2 and reply yes to the authentication prompt.
On node2, create the known_hosts file by doing the following:
- SSH to node2 and reply yes to the authentication prompt.
- SSH to node1 and reply yes to the authentication prompt.
On node1, verify that SSH equivalency is now configured by using the following Cluster Verification Utility (CVU) command.
```
cluvfy stage -pre crsinst -n all -verbose
```

Configure the Console

On node1, create a file called emca.rsp with the following entries.

DB_UNIQUE_NAME=<pdb_unique_name>
SERVICE_NAME=<db_unique_name>.<db_domain>
PORT=<scan listener port>
LISTENER_OH=$GI_HOME
SYS_PWD=<admin password>
DBSNMP_PWD=<admin password>
SYSMAN_PWD=<admin password>
CLUSTER_NAME=<cluster name>     <=== to get the cluster name, run: $GI_HOME/bin/cemutlo -n 
ASM_OH=$GI_HOME
ASM_SID=+ASM1
ASM_PORT=<asm listener port>
ASM_USER_NAME=ASMSNMP
ASM_USER_PWD=<admin password>

On node1, run Enterprise Manager Configuration Assistant (EMCA) using the emca.rsp file as input.

$ORACLE_HOME/bin/emca 
    -config dbcontrol db 
    -repos create 
    -cluster 
    -silent 
    -respFile <location of response file above>

On node2, configure the console so the agent in node1 reports to the console in node1, and the agent in node2 reports to the console in node2.

$ORACLE_HOME/bin/emca 
    -reconfig dbcontrol 
    -silent 
    -cluster 
    -EM_NODE <node2 host> 
    -EM_NODE_LIST <node2 host> 
    -DB_UNIQUE_NAME <db_unique_name> 
    -SERVICE_NAME <db_unique_name>.<db_domain>

On each node, verify that console is working properly.

export ORACLE_UNQNAME=<db_unique_name>

emctl status agent

Output:

Oracle Enterprise Manager 11g Database Control Release 11.2.0.4.0
Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.
---------------------------------------------------------------
Agent Version     : 10.2.0.4.5
OMS Version       : 10.2.0.4.5
Protocol Version  : 10.2.0.4.5
Agent Home        : /u01/app/oracle/product/11.2.0.4/dbhome_x/<host>_<db_unique_name>
Agent binaries    : /u01/app/oracle/product/11.2.0.4/dbhome_x
Agent Process ID  : 26194
Parent Process ID : 25835
Agent URL         : https://<node host>:1831/emd/main
Repository URL    : https://<node host>:5501/em/upload/
Started at        : 2017-03-15 20:20:34
Started by user   : oracle
Last Reload       : 2017-03-15 20:27:00
Last successful upload                       : 2017-03-15 21:06:36
Total Megabytes of XML files uploaded so far :    22.25
Number of XML files pending upload           :        0                       <=== should be zero
Size of XML files pending upload(MB)         :     0.00
Available disk space on upload filesystem    :    42.75%
Data channel upload directory                : /u01/app/oracle/product/11.2.0.4/dbhome_x/<host>_<db_unique_name>/sysman/recv
Last successful heartbeat to OMS             : 2017-03-15 21:08:45
---------------------------------------------------------------

Update iptables and Security List

On each node, edit iptables to open the console's port as described in Open Ports on the DB System.
Update the security list for the console's port as described in Update the Security List for the DB System.

Title and Copyright Information

Oracle and/or its affiliates.