Oracle Cloud Infrastructure Documentation

Using EM Express and Database Control on Exadata Cloud at Customer

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

Accessing Enterprise Manager Database Express

Enterprise Manager Database Express is available on Exadata Cloud at Customer databases 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 is created, Exadata Cloud at Customer automatically sets a port for EM Express access to the CDB. You do not need to perform any manual configuration steps. Each database is allocated a unique port number. The allocations use ports in a range starting with 5500, 5501, 5502, and so on.
  • To manage a PDB. With Oracle Database 12c Release 2 or later, EM Express can be configured to access the CDB and all PDBs on a single port, which is known as the global port. 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. You do not need to perform any manual configuration steps. Each database is allocated a unique port number. The allocations use ports in a range starting with 5500, 5501, 5502, and so on.

    For a version 12.1 database, you must manually set a port for each PDB you want to manage using EM Express.

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

You can access EM Express by directing your browser to the URL:

https://node-ip-address:port/em

where node-ip-address is the client network IP address of the compute node hosting EM Express, and port is the EM Express port used by the database.

If your browser displays a warning that your connection is not secure or not private, use the browser’s advanced option to ignore the warning and continue. You get this warning because Exadata Cloud at Customer uses a self-signed certificate to provide HTTPS (secure HTTP) connectivity, and such certificates are considered suspicious by many web browsers.

Accessing Enterprise Manager 11g Database Control

Enterprise Manager 11g Database Control is available on Exadata Cloud at Customer databases created using Oracle Database 11g Release 2. Each database is allocated a unique port number in a range starting with 1158, 1159, 1160, 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. In the preceding file name, host is the host name of the compute node hosting Database Control, and sid is the Oracle Database system identifier (SID).

You can access Database Control by directing your browser to the URL:

https://node-ip-address:port/em

where node-ip-address is the client network IP address of the compute node hosting Database Control, and port is the Database Control port used by the database.

If your browser displays a warning that your connection is not secure or not private, use the browser’s advanced option to ignore the warning and continue. You get this warning because Exadata Cloud at Customer uses a self-signed certificate to provide HTTPS (secure HTTP) connectivity, and such certificates are considered suspicious by many web browsers.