Accessing Enterprise Manager 11g Database Control
Enterprise Manager 11g Database Control (Database Control), a web-based tool for managing Oracle Database 11g, is available on Oracle Database Exadata Cloud Service database deployments created using Oracle Database 11g Release 2.
You can access Database Control in the following ways:
Note:
On Exadata Cloud Service, the Database Control network port is blocked by default. To access Database Control by using the Open EM Console menu item or by using a direct URL, you must first gain access to the network port. See Finding the Database Control Network Port and Enabling Network Access to a Compute Node.
Using the Open EM Console Menu Item to Access Database Control
-
Open the Instances page of the Oracle Database Cloud Service console.
For detailed instructions, see Accessing the My Services Dashboard and the Oracle Database Cloud Service Console.
-
From the action menu (
) for the deployment, select Open EM Console.
-
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 Service database deployments use a self-signed certificate to provide HTTPS (secure HTTP) connectivity, and such certificates are considered suspicious by many web browsers.
-
When prompted for a user name and password, enter the name of a user with the
DBA
privilege (such asSYS
orSYSTEM
) and the password.If you want to connect with
SYSDBA
privileges, select as SYSDBA.After entering or selecting the required values, click Login.
The Open EM Console menu item is also available from the action menu () on the Oracle Database Cloud Service Instance Overview page.
Using a Direct URL to Access Database Control
-
In your web browser, go to the following URL:
https://node-ip-address:DB-Control-port/em
where
node-ip-address
is the public IP address of the compute node hosting Database Control, andDB-Control-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 Service database deployments use a self-signed certificate to provide HTTPS (secure HTTP) connectivity, and such certificates are considered suspicious by many web browsers.
-
When prompted for a user name and password, enter the name of a user with the
DBA
privilege (such asSYS
orSYSTEM
) and the password.If you want to connect with
SYSDBA
privileges, select as SYSDBA.After entering or selecting the required values, click Login.
Using an SSH Tunnel to Access Database Control
-
Create an SSH tunnel to the Database Control port on the compute node hosting Database Control. For information about creating an SSH tunnel, see Creating an SSH Tunnel to a Compute Node Port.
-
After creating the SSH tunnel, go to the following URL:
https://localhost:DB-Control-port/em
where
DB-Control-port
is the Database Control port used by the database. -
When prompted for a user name and password, enter the name of a user with the
DBA
privilege (such asSYS
orSYSTEM
) and the password.If you want to connect with
SYSDBA
privileges, select as SYSDBA.After entering or selecting the required values, click Login.
Finding the Database Control Network Port
When a database deployment is created, Exadata Cloud Service automatically sets a port for Database Control. You do not need to perform any manual configuration steps. Each database deployment is allocated a unique port number in a range starting with 1158, 1159, 1160, and so on.
To find the port that is in use for a specific database, investigate the REPOSITORY_URL
entry in the $ORACLE_HOME/Hostname_SID/sysman/config/emd.properties
file. In the preceding file name, Hostname
is the host name of the compute node hosting Database Control, and SID
is the Oracle Database system identifier (SID).