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 Classic Cloud Service database deployments created using Oracle Database 11g Release 2.

You can access Database Control in the following ways:

Using the Open EM Console Menu Item to Access Database Control

Note:

For database deployments built on Oracle Cloud Infrastructure Classic, the network port to access Database Control is blocked by default. To use the Open EM Console menu item, you must unblock port 1158, either by enabling the deployment’s ora_p2_dbconsole predefined access rule or by creating your own access rule that opens port 1158. For instructions, see Enabling Access to a Compute Node Port.

Open the Instances page of the Oracle Database Classic Cloud Service console.

For detailed instructions, see Accessing the Oracle Database Classic 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 Database Classic 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 theDBA privilege (such as SYS or SYSTEM) and the password.

If you want to connect with SYSDBA privileges, select as SYSDBA.

After entering or selecting the required values, click Login.

Note: if the database deployment was created using a QuickStart template, the password is available in the zip file downloaded when the deployment was created.

The Open EM Console menu item is also available from the action menu () on the Oracle Database Classic Cloud Service Instance Overview page.

Note:

On database deployments hosting an Oracle RAC database, the Open EM Console menu item opens Database Control on node 1. To open Database Control on node 2, you must use a direct URL.

Using a Direct URL to Access Database Control

Note:

For database deployments built on Oracle Cloud Infrastructure Classic, the network port to access Database Control is blocked by default. To use a direct URL, you must unblock port 1158, either by enabling the deployment’s ora_p2_dbconsole predefined access rule or by creating your own access rule that opens port 1158. For instructions, see Enabling Access to a Compute Node Port.

In your web browser, go to the following URL:
```
https://node-ip-address:1158/em
```
where node-ip-address is the IP address of the compute node as listed on the deployment’s Overview page.
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 Database Classic 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 theDBA privilege (such as SYS or SYSTEM) and the password.

If you want to connect with SYSDBA privileges, select as SYSDBA.

After entering or selecting the required values, click Login.

Note: if the database deployment was created using a QuickStart template, the password is available in the zip file downloaded when the deployment was created.

Using an SSH Tunnel to Access Database Control

Create an SSH tunnel to port 1158 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, direct your browser to the URL https://localhost:1158/em.
When prompted for a user name and password, enter the name of a user with theDBA privilege (such as SYS or SYSTEM) and the password.

If you want to connect with SYSDBA privileges, select as SYSDBA.

After entering or selecting the required values, click Login.

Note: if the database deployment was created using a QuickStart template, the password is available in the zip file downloaded when the deployment was created.