ORA-46658: keystore not open in the container

You may face this error when database needs to access the keystore and keystore is not open. For example, while changing keystore password, or while creating/rotating master encryption key. In the following example, I faced this error while creating master encryption key.

ORA-28417: password-based keystore is not open

You may face this error while creating a master encryption key while having/using auto-login (or local auto-login) keyswtore, but your password-based keystore is still closed which is required to be open before you can create master encryption key.

SQL> ADMINISTER KEY MANAGEMENT SET KEY IDENTIFIED BY salman12 WITH BACKUP USING 'initial_backup' CONTAINER = ALL ;

ORA-28354: Encryption wallet, auto login wallet, or HSM is already open

This error comes when you try to open a password-based keystore, and the keystore is already open.

SQL> SELECT WRL_PARAMETER, STATUS, WALLET_TYPE FROM V$ENCRYPTION_WALLET; WRL_PARAMETER                                                        STATUS                                            WALLET_TYPE ---------------------------------------- ------------------------------ -------------------- ----------------------------------------- C:\APP\ORACLE\ADMIN\SALMAN12C\WALLET     OPEN_NO_MASTER_KEY             PASSWORD

ORA-46661: keystore not open in root container

In a multi tenant environment, this error comes when you try to open a password-based keystore in a pluggable database and the keystore in root container is no already open. Please note that to open keystore in any pluggable database, the keystore in root container (CDB$ROOT) must be opened first, or alternatively you can use CONTAINER=ALL option while opening keystore in the root container so that keystore for all the pluggable databases is also opened.

Transparent Data Encryption in 11g

In this article I would discuss how to implement Transparent Data Encryption (TDE) in 11g. TDE is used to encrypt data at table/column level or tablespace level. This ensures that encrypted data is accessible only by using encryption key that is stored in either Wallet or Hardware Security Module.

For RAC setups, encryption key needs to be stored/copies on all the RAC nodes. In dataguard setup, encryption key should also be copied on dataguard sites.

ORA-28365: wallet is not open

This error means that you are trying to perform some operation in the database which requires encryption wallet to be open, but wallet is not open. In 11g, use following command to open the wallet. Provide password after “identified by” clause. In the following scenario, password is “welcome”.

alter system set encryption wallet open identified by "welcome1";

OEM Cloud Control Job Suspended - Target is not ready

In my OEM 12c, my RMAN backup job for one target database started failing, and next execution status was marked as "Suspended".

DUPLICATE Database using Backup of a Database

If you want to create a duplicate database from a live/active database, you can follow this article. But if you want to DUPLICATE a database using backup of another database, you can use following steps. I am creating new database with a different name using DUPLICATE command, or you may want to retain same name for the database while duplicating.

Configuring OEM Express Control

Starting 12c, OEM Database Control has been replaced by OEM Database Express. OEM Express configuration is very simple as compared to previous OEM Database Control. Following is the method to configure OEM Express. OEM Express Database is configured separately for container database and each pluggable database. Method is same; you just need to set current container to pluggable database for which you want to configure the OEM, and execute the steps as explained bellow.

Calculating ASM diskgroup Usable Size

Sometimes sizing information of an ASM diskgroup returned by “lsdg” command from “asmcmd” prompt (similar information is also available under v$asm_diskgroup view) leaves DBAs perplexed. Sizing information and usable space for diskgroups with EXTERNAL REDUNDANCY is quite easy to understand, but when it comes to NORMAL or HIGH redundancy diskgroups, it is not very straightforward. Here I would explain ASM diskgroup space calculation in detail to make it easier to understand. Before I explain how to calculate usable space in an ASM diskgroup, some useful information to note is as follows