Operation & Support

Q: CDB restart - when and how?

A: In general, there is no resource action available to restart the CDB on-demand. The CDB will automatically restart in two cases:

  1. When changing the number of vCPUs. This is a modify action. It requires a re-start of the CDB, because not only more (or less) vCPUs are allocated, but also the RAM allocation needs to be adapted.

  2. When enabling or disabling database backup. This is a modify action. It requires a restart of the CDB, because the archive mode of the database needs to be enabled/disabled.


Q: How can I access the alert log file

A: Alert log information can be retrieved from V$DIAG_ALERT_EXT. User pdbadmin has read access to V$DIAG_ALERT_EXT. Example query:

SELECT originating_timestamp,message_text 
  FROM v$diag_alert_ext  
 WHERE originating_timestamp > (SYSDATE- 1/12) 
 ORDER BY originating_timestamp DESC;

Q: How are the CDBs and PDBs monitored?

A: The databases are monitored by Oracle Enterprise Manager Cloud Control. The OpsTeam takes care about the required measures. The monitoring metrics are documented in the chapter Monitoring Metrics.


Q: Can I manage my Databases with Oracle Enterprise Manager?

A: Yes.

With OEMaC (OEM at Customer) MODS Regular provides an option to install an OEM Agent on the container VM in order to manage, operate and monitor the PDBs. For that, the OEM agent binaries need to be provided by the customer.

OEMaC is not a MODS Regular service option. And therefore the installation and configuration of OEMaC is not a self-service task. To enable OEMaC on a MODS Regular container, a service request is needed. The MODS team will then request the OEM Agent binaries, and the connectivity information, and will initiate the needful activities.


Q: Can you monitor the VM utilization of your CDB?

A: Yes.

The utilization of the VM can be visualized within the vRA console (available only on swisscom ESC tenants).


Q: Is it possible to create database links between PDBs and on-prem databases?

A: Yes.

It is possible to create DB links between different DBs as long as it use the customer network. There is no limitation configured e.g. lockdown profile. As shown in the below drawing, different types of DB links are possible.

  1. Local database link between two PDBs in the same container database.
  2. ESC cloud based database link between two PDBs in different ESC container databases.
  3. Database link between ESC PDB and a customer on-premises database.

Database Links between misc databases

In any case the database link has to be created with a full connect string including the customer network information i.e. IP address of the customer network.

CREATE DATABASE LINK pdbcrm01.appsrv.ch CONNECT TO user01 IDENTIFIED BY "<PASSWORD>" USING
'(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<IP>)(PORT=1521))
(CONNECT_DATA=(SERVICE_NAME=pdbcrm01.appsrv.ch)))';
Last Updated: