Accessing Oracle DBaaS Monitor

Database deployments of single-instance databases on Oracle Database Classic Cloud Service include Oracle DBaaS Monitor, a built-in monitor that provides a wide spectrum of information about Oracle Database and operating system status and resource usage.

You can access Oracle DBaaS Monitor in the following ways:

Using the “Open DBaaS Monitor Console” Menu Item to Access Oracle DBaaS Monitor

Note:

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

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

For detailed instructions, see Accessing the Oracle Database Classic Cloud Service Console.
From the menu for the deployment, select Open DBaaS Monitor Console.
If your browser displays a warning that your connection is not secure or not private, use the browser’s advanced option to 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 dbaas_monitor as the user name and the password specified during the database deployment creation process, and then click OK.

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 DBaaS Monitor Console menu item is also available on the Overview page in the menu next to the deployment’s name.

Using a Direct URL to Access Oracle DBaaS Monitor

Note:

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

In your web browser, go to the following URL:
```
https://node-ip-address/dbaas_monitor
```
where node-ip-address is the IP address of the deployment’s 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 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 dbaas_monitor as the user name and the password specified during the database deployment creation process, and then click OK.

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 Oracle DBaaS Monitor

Create an SSH tunnel to port 443 on the compute node hosting Oracle DBaaS Monitor. 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/dbaas_monitor.
When prompted for a user name and password, enter dbaas_monitor as the user name and the password specified during the database deployment creation process, and then click OK.

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.