TrivadisContent

Oracle 12.2 – New Features I like – Part 1: Multitenant “Hot Clones”

I like the Oracle Multitenant architecture which was introduced in 12.1. But the concept to clone a source database to multiple copies in a small step had one big problem.  In Oracle 12.1, to clone a pluggable database the source database had to be in state read-only.

In 12.2 is it not longer necessary to set the source pluggable database in state read-only, the source database has not to be modified to create a clone. Oracle calls it in the documentation “Hot Clone”.

Link to the official Oracle documentation: https://docs.oracle.com/database/122/ADMIN/creating-and-removing-pdbs-with-sql-plus.htm#ADMIN13584

Here is a clone of the pluggable database PDB1 into PDB2 in the Oracle Database Cloud Service.

Verify existing Pluggable Databases and States – PDB1 is in state READ-WRITE

Verify if Oracle Managed Files are in use

Using Oracle Managed Files makes the file name convert much easier. You don’t have to care about files and directories. Like the feature says, Oracle is managing that for you.

Create TEMP directory

Is it a bug or is it a feature? The directory for the temporary datafile will not be created, we have to do it manually.

Error message when the directory is not created in advanced when a clone is started:

Clone PDB1 into PDB2

Attention: Databases in the Oracle Database Cloud Service are created “Secure by Default”, that means that Transparent Data Encryption (TDE) is enabled. This is why I need the KEYSTORE INDENTIFIED BY command in line 6.

Verify PDB2 state

The cloned PDB2 is in state MOUNTED after the clone procedure.

Open PDB2

Now the pluggable database PDB2 is ready to use, just open it. For more information how TDE works in a multitenant environment (export key etc.) take a look here: http://docs.oracle.com/database/122/ASOAG/using-transparent-data-encryption-with-other-oracle-features.htm#ASOAG10353

 

 

 

Enterprise Manager 13cR2 – How to apply Patch 23094292: WLS PATCH SET UPDATE 12.1.3.0.160719

My fresh EM13cR2 installation showed me that there is a patch for the Weblogic environment available. This patch was released in July 2016: Patch Patch 23094292: WLS PATCH SET UPDATE 12.1.3.0.160719. This patchset has included 157 fixes and is a generic one. The patch is marked in My Oracle Support as recommended. OPatch has no to be updated. This patch is not an online patch, you have to shut down your running EM13cR2 server.

This blog post describes the apply of the Weblogic patch set update in an Enterprise Manager 13cR2 environment running on a Oracle Linux server.

patch_01

Prepare Patch Set Update on EM13c Server

The patch file has to be extracted. I have copied to file to my EM13cR2 server stage directory /u00/app/oracle/stage.

Set ORACLE_HOME

Set the ORACLE_HOME variable to the directory where the Oracle Enterprise Manager 13cR2 is located. In my example the EM13cR2 is installed in directory /u00/app/oracle/product/em13cr2.

Stop running Oracle Enterprise Manager 13c

Apply Patch 23094292: WLS PATCH SET UPDATE 12.1.3.0.160719

Go to the extracted patch set directory:

Apply the patch:

You can ignore the warning message, it’s because OPatch has to rollback a previous installed patch.

Start Oracle Enterprise Manager 13c

Summary

Like the patches which were released for Weblogic / Enterprise Manager before, the installation was very smooth. There were no problems and the EM13cR2 started well after the patch apply.

Connect your Enterprise Manager 13cR2 with the Oracle Database Backup Service

In EM13cR1, it was the first time when the Oracle Database Backup Service was integrated . In Release 2 the configuration menu was extended, a storage container can be defined now e.g. for a better organization and overview of the backups. This blog post shows you how to configure the Oracle Database Backup Service in Enterprise Manager 13cR2 and how to prepare a database for a cloud backup. All you need is the Oracle Database Backup Service, a trial works too.

Configure Service Settingsbackup_service_step_00

 

 

 

 

 

Enter your domain and login information. Optional: Set a backup container. A backup container is an organiziation unit like a subdirectory on a server.

backup_service_step_01

Configure the Database

Select the database which you want to backup to the Oracle cloud from the database target page. Configure Oracle Cloud Backup Service.

backup_service_step_02

The first time when you run the configuration, you need to enter your host credentials for the host where the database is running which you want to configure. Use the username which has installed the database software, or you can use a named credential. Be sure that the server where the backup has to be configured has access to the internet.

After submit, a deployment procedure configures the Oracle Database Backup Service on the server. The Oracle Database Backup Service module will be installed on server.

backup_service_step_03

backup_service_step_04

The deployment procedure copies the tape library for the Oracle Database Backup Service into the $ORACLE_HOME/lib and creates a wallet in $ORACLE_HOME/dbs/opc with the cloud certficates. Bot components are required to use the service.

The EM13c view after the successful deployment. To verify the configuration, press the Test Oracle Cloud Backup Button.

backup_service_step_05

All backups into the Oracle Cloud have to be encrypted, the test run too.

backup_service_step_06

Backup test succeeded.

backup_service_step_07

Execute  RMAN Backup

Now you are able to backup an Oracle database with RMAN into the Oracle Cloud. Schedule a backup.

backup_service_step_08

Schedule a customized backup

backup_service_step_09

On the backup settings page, scroll down to set the encryption mode. You can choose between the wallet and the password method. For more information how to configure a wallet for a backup, take a look at my blog post here: Encrypt RMAN Backups for the Oracle Cloud with a Keystore.

As reminder, database backups with target Oracle Cloud have to be encrypted locally. Otherwise the backup job fails. Activate the checkbox for the password method and set/confirm the password. Next.

backup_service_step_10

Select the Oracle Cloud as destination. Below you can see the used RMAN parameter. Oracle uses the file libopc.so like a tape driver. Next.

backup_service_step_11

Schedule the execution. Next.

backup_service_step_12

Now you can submit the job or use the syntax in the RMAN script box.

backup_service_step_13

The Backup Management Page shows the Oracle Cloud as Media

backup_service_step_14

Summary

The Oracle Database Backup Service is fully integrated in the Oracle Enterprise Manager 13c and it works fine. The EM deploys you  the Oracle backup module on the target servers, once deployed, the configuration can be used for every other database which runs on the same target host as configured.

For more information about the Oracle Database Backup Service, take a look in the documentation here: https://docs.oracle.com/cloud/latest/dbbackup_gs/