Oracle Cloud Infrastructure Documentation

Monitoring a Database on an Exadata DB System

This topic explains how to access Enterprise Manager Database Express and Enterprise Manager Database Control, which are web-based tools for managing Oracle Database.

Accessing Enterprise Manager Database Express 12c

Enterprise Manager Database Express 12c (EM Express) is available on Exadata DB system database deployments created using Oracle Database 12c Release 1 (12.1) or later.

How you access EM Express depends on whether you want to manage a CDB or PDB.

  • To manage the CDB. When a database deployment is created, Database automatically sets port 5500 on the deployment’s compute nodes for EM Express access to the CDB.
  • To manage a PDB. For an Oracle Database 12.2 or later deployment, a single port (known as the global port) is automatically set on the deployment's compute nodes. The global port lets you use EM Express to connect to all of the PDBs in the CDB using the HTTPS port for the CDB.

    For an Oracle Database 12.1 deployment, you must manually set a port on the deployment's compute nodes for each PDB you want to manage using EM Express.

For both CDBs and PDBs, you must add the port to a security list as described in Updating the Security List.

To confirm the port that is in use for a specific database, connect to the database as a database administrator and execute the query shown in the following example:

SQL> select dbms_xdb_config.getHttpsPort() from dual;


DBMS_XDB_CONFIG.GETHTTPSPORT()
------------------------------
                          5502

Setting the Port for EM Express to Manage a PDB (Oracle Database 12.1 Only)

In Oracle Database 12c Release 1, a unique HTTPS port must be configured for the root container (CDB) and each PDB that you manage using EM Express.

To configure a HTTPS port so that you can manage a PDB with EM Express:

  1. Invoke SQL*Plus and log in to the PDB as the SYS user with SYSDBA privileges.
  2. Execute the DBMS_XDB_CONFIG.SETHTTPSPORT procedure.

    SQL> exec dbms_xdb_config.sethttpsport(port-number)

Accessing EM Express

Before you access EM Express, add the port to the security list. See Updating the Security List.

After you update the security list, you can access EM Express by directing your browser to the URL https://<node-ip-address>:<port>/em, where node-ip-address is the public IP address of the compute node hosting EM Express, and port is the EM Express port used by the database.

Accessing Enterprise Manager 11g Database Control

Enterprise Manager 11g Database Control (Database Control) is available on Exadata DB system database deployments created using Oracle Database 11g Release 2. Database Control is allocated a unique port number for each database deployment. By default, access to Database Control is provided using port 1158 for the first deployment. Subsequent deployments are allocated ports in a range starting with 5500, 5501, 5502, and so on.

You can confirm the Database Control port for a database by searching for REPOSITORY_URL in the $ORACLE_HOME/host_sid/sysman/config/emd.properties file.

Before you access Database Control, add the port for the database to the security list associated with the Exadata DB system's client subnet. For more information, see Updating the Security List.

After you update the security list, you can access Database Control by directing your browser to the URL https://<node-ip-address>:<port>/em, where node-ip-address is the public IP address of the compute node hosting Database Control, and port is the Database Control port used by the database.

Updating the Security List

Before you can access EM Express or Database Control, you must add the port for the database to the security list associated with the Exadata DB system's data (client) subnet. To update an existing security list, complete the following steps using the Console:

  1. Open the navigation menu. Under Database, click Bare Metal, VM, and Exadata.
  2. Choose your Compartment.

    A list of DB systems is displayed.

  3. Locate the DB system in the list.
  4. Note the DB system's Client Subnet name and click its Virtual Cloud Network.
  5. Locate the subnet in the list, and then click its security list under Security Lists.
  6. Click Edit All Rules and add an ingress rule with source type=CIDR, source CIDR=<source CIDR>, protocol=TCP, and port=<port number or port range>.

    The source CIDR should be the CIDR block that includes the ports you open for the client connection.

For detailed information about creating or updating a security list, see Security Lists.