Skip to main content

How to Unplug and Plug a PDB Having TDE from One Container to Another


<<Back to DB Administration Main Page

How to Unplug and Plug a PDB Having Encryption (TDE) from One Container to Another

Setup Overview Source Container: CDB01
No of PDB's in Source Container 2 (PDB01 and PDB02)
PDB01 using TDE
PDB02 using TDE
Target Container: CDB02
Note: Even if the PDB you are unplugging and re-plugging to another container, don't have any encrypted object but Wallet keys, are treated exactly same as PDB having encrypted objects.
Task: In this post I will unplug the PDB02 from CDB01 and Plug it in CDB002 on the same host without copying the datafile (using NOCOPY Method).
Precheck
1) Perform Full PDB backup of PDB02 database.
2) Create PDB description XML file for PDB(PDB02)
SQL> exec dbms_pdb.describe (PDB_DESCR_FILE=>'/u01/app/oracle/PDB02.xml', PDB_NAME=>'PDB02');
3) Verify the status of the PDB.
SQL> select pdb_name, status from cdb_pdbs where pdb_name in ('PDB02');
4)  Checking the Compatibility of the PDB with the Target CDB
SQL> BEGIN
IF dbms_pdb.check_plug_compatibility('/u01/app/oracle/PDB02.xml') THEN
dbms_output.put_line('no violations found');
ELSE
dbms_output.put_line('violations found');
END IF;
END;
/
SQL> SELECT type, message, action FROM pdb_plug_in_violations WHERE name = 'PDB02';
At this point resolve if there is any violation found. If not proceed with unplug

How to Unplug a PDB Having Encrypted Objects from CDB to Plug into Another CDB

Step1> Check if wallet keys are available in Source PDB
SQL>col creator for a5
SQL>col key_use for a10
SQL>col keystore_type for a25
SQL>col origin for a10
SQL>col creator_pdbname for a15
SQL>col activating_pdbname for a15
select con_id,substr(key_id,1,6)||'...' "KEY_ID...",creator,key_use,keystore_type,origin,creator_pdbname,activating_pdbname from v$encryption_keys;
    CON_ID KEY_ID...     CREAT KEY_USE    KEYSTORE_TYPE             ORIGIN     CREATOR_PDBNAME ACTIVATING_PDBN
---------- ------------- ----- ---------- ------------------------- ---------- --------------- ---------------
         0 AdiYqO...     SYS   TDE IN PDB SOFTWARE KEYSTORE         LOCAL      PDB02           PDB02
1 row selected.
As you can see PDB02 is very well having the wallet keys. Once the PDB is having the wallet keys, you must export/import the wallet as well to be able to unplug and re-plug the PDB in another container, even if the PDB don't have any encrypted object.
Step2> Export the Wallet Key from Source PDB
CDB011> alter session set container=PDB02;
Session altered.
CDB011> administer key management export encryption keys with secret "xxxxxxx" TO '/u01/app/oracle/pdb02key.exp' identified by xxxxxxx;
keystore altered.
Step3> Close the Source PDB on all Instances 
CDB011> alter pluggable database PDB02 close immediate instances=('CDB011','CDB012');
Pluggable database altered.
Step4> Unplug PDB database
CDB011> alter pluggable database PDB02 unplug into '/u01/app/oracle/TMP_PDB02.xml';
Pluggable database altered.
Step5> Drop Source PDB database (Keep the datafiles)
CDB011> drop pluggable database PDB02 keep datafiles;
Pluggable database dropped.
Step6> Check Source PDB database Status
CDB011> select pdb_name, status from cdb_pdbs where pdb_name in ('PDB02');
no rows selected

How to Plug an Unplugged PDB (Having Encrypted Objects TDE Enabled )in Same or Different Container

Step1> Prepare the Target Container
The step can be done much in advance to minimize the downtime 
a) Target container should have same options installed as source
b) Important database parameter (eg NLS_CHARACTERSET, DB_BLOCK_SIZE etc) should be same as source
c) Wallet must be created should be open in root container ReadHere: How to Configure Wallet
Step2> Verify the Wallet/Keystore Status in Target Root Container
SQL> show con_name
CON_NAME
------------------------------
CDB$ROOT
SQL> set linesize 200
SQL>col WALLET_DIR for a32
SQL>col status for a21
SQL>select STATUS,WRL_PARAMETER WALLET_DIR,WALLET_TYPE from V$ENCRYPTION_WALLET;
STATUS                WALLET_DIR                       WALLET_TYPE
--------------------- -------------------------------- ------------------------------------------------------------
OPEN                  +DATAC4/CDB02/wallet/            PASSWORD
1 row selected.
Note:- Wallet must be open in root container
Step3> Plug the PDB database
SQL> show pdbs;
    CON_ID CON_NAME                       OPEN MODE  RESTRICTED
---------- ------------------------------ ---------- ----------
         2 PDB$SEED                       READ ONLY  NO
SQL> create pluggable database PDB02 using '/u01/app/oracle/TMP_PDB02.xml' NOCOPY TEMPFILE REUSE;
Pluggable database created.
Step4>Check PDB Status
SQL> select pdb_name, status from cdb_pdbs where pdb_name='PDB02';
PDB_NAME   STATUS
---------- --------------------
PDB02      NEW
1 row selected.
SQL> select open_mode,con_id from v$pdbs where name='PDB02';
OPEN_MODE                          CON_ID
------------------------------ ----------
MOUNTED                                 3
1 row selected.
Step5>Open PDB
SQL> alter pluggable database PDB02 open;
Warning: PDB altered with errors.
Step6> Check PDB Status again
SQL> show pdbs
    CON_ID CON_NAME                       OPEN MODE  RESTRICTED
---------- ------------------------------ ---------- ----------
         2 PDB$SEED                       READ ONLY  NO
         3 PDB02                          READ WRITE   YES
Step7>Check Violations
SQL> col MESSAGE for a50
SQL> col ACTION for a50
SQL> set line 200
SQL> SELECT type, message, action FROM pdb_plug_in_violations WHERE name = 'PDB02';
TYPE            MESSAGE                                            ACTION
--------------- -------------------------------------------------- --------------------------------------------------
ERROR           PDB needs to import keys from source.              Import keys from source.
1 row selected.
Step8> Import Keys
The Keys must be imported from the export taken in Step2 while unplugging the PDB
SQL> alter session set container=PDB02
Session altered.
SQL> ADMINISTER KEY MANAGEMENT IMPORT ENCRYPTION KEYS WITH SECRET "xxxxxxxx" FROM '/u01/app/oracle/pdb02key.exp' IDENTIFIED BY xxxxxxx;
ADMINISTER KEY MANAGEMENT IMPORT ENCRYPTION KEYS WITH SECRET "xxxxxx" FROM '/u01/app/oracle/pdb02key.exp' IDENTIFIED BY xxxxxxx
*
ERROR at line 1:

ORA-46658: keystore not open in the container

Let's open the KeyStore and Retry
SQL> alter session set container=PDB02;
Session altered.
CDB021> show con_name
CON_NAME
------------------------------
PDB02
SLQ> ADMINISTER KEY MANAGEMENT SET KEYSTORE OPEN IDENTIFIED BY "xxxxx";
keystore altered.
SQL> set linesize 200
SQL> col WALLET_DIR for a32
SQL> col status for a21
SQL> select STATUS,WRL_PARAMETER WALLET_DIR,WALLET_TYPE from V$ENCRYPTION_WALLET;
STATUS                WALLET_DIR                       WALLET_TYPE
--------------------- -------------------------------- ------------------------------------------------------------
OPEN_NO_MASTER_KEY    +DATAC4/CDB02/wallet/            PASSWORD
1 row selected.
SQL> show con_name
CON_NAME
------------------------------
PDB02
SQL> ADMINISTER KEY MANAGEMENT IMPORT ENCRYPTION KEYS WITH SECRET "xxxxxxx" FROM '/u01/app/oracle/pdb02key.exp' IDENTIFIED BY xxxxxxx;
ADMINISTER KEY MANAGEMENT IMPORT ENCRYPTION KEYS WITH SECRET "xxxxxxx" FROM '/u01/app/oracle/pdb02key.exp' IDENTIFIED BY xxxxxxxx
*
ERROR at line 1:

ORA-46631: keystore needs to be backed up

Solution: Import the Keys with backup option
SQL> show con_name
CON_NAME
------------------------------
PDB02
SQL> ADMINISTER KEY MANAGEMENT IMPORT ENCRYPTION KEYS WITH SECRET "xxxxxxx" FROM '/u01/app/oracle/pdb02key.exp' IDENTIFIED BY xxxxxx with backup;
keystore altered.
SQL> set linesize 200
SQL> col WALLET_DIR for a32
SQL> col status for a21
SQL> select STATUS,WRL_PARAMETER WALLET_DIR,WALLET_TYPE from V$ENCRYPTION_WALLET;
STATUS                WALLET_DIR                       WALLET_TYPE
--------------------- -------------------------------- ------------------------------------------------------------
OPEN                  +DATAC4/CDB02/wallet/            PASSWORD
1 row selected.
Step9> Restart the PDB and Check the Status
SQL> alter pluggable database PDB02 close immediate  instances=('CDB021','CDB022');
Pluggable database altered.
SQL> alter pluggable database PDB02 open instances=('CDB021','CDB022');
Pluggable database altered.
SQL> show pdbs;
    CON_ID        CON_NAME        OPEN MODE         RESTRICTED
---------- ------------------------------ ---------- ----------
         3                  PDB02                READ WRITE          NO

Step10> Check PDB Violations
SLQ> SELECT type, message, action FROM pdb_plug_in_violations WHERE name = 'PDB02';
no rows selected




Related Posts
How to Unplug and Plug a PDB from One Container to Another
How to configure TDE Using Wallet in pluggable database in 12c

Comments

Post a Comment

Popular posts from this blog

DataPump Import Of Object Types Fails With Errors ORA-39083 ORA-2304 Or ORA-39117 ORA-39779

<<Back to Oracle DATAPUMP Main Page ORA-39083: Object type TYPE:"TEST_QA01"."LOG_RECORD" failed to create with error: ORA-02304: invalid object identifier literal Import: Release 12.1.0.2.0 - Production on Tue May 29 07:59:12 2018 Copyright (c) 1982, 2014, Oracle and/or its affiliates.  All rights reserved. Connected to: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production With the Partitioning, Real Application Clusters, Automatic Storage Management, Oracle Label Security, OLAP, Advanced Analytics and Real Application Testing options Master table "SYSTEM"."SYS_IMPORT_FULL_01" successfully loaded/unloaded Starting "SYSTEM"."SYS_IMPORT_FULL_01":  system/********@TEST_QA parfile=import_TEST.par Processing object type SCHEMA_EXPORT/USER Processing object type SCHEMA_EXPORT/SYSTEM_GRANT Processing object type SCHEMA_EXPORT/ROLE_GRANT Processing object type SCHEMA_EXPORT/DEFAULT_ROLE Pr
Post a Comment
Read more

ORA-28374: typed master key not found in wallet

<<Back to Oracle DB Security Main Page ORA-46665: master keys not activated for all PDBs during REKEY SQL> ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL ; ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL * ERROR at line 1: ORA-46665: master keys not activated for all PDBs during REKEY I found following in the trace file REKEY: Create Key in PDB 3 resulted in error 46658 *** 2019-02-06T15:27:04.667485+01:00 (CDB$ROOT(1)) REKEY: Activation of Key AdnU5OzNP08Qv1mIyXhP/64AAAAAAAAAAAAAAAAAAAAAAAAAAAAA in PDB 3 resulted in error 28374 REKEY: Keystore needs to be restored from the REKEY backup.Aborting REKEY! Cause: All this hassle started because I accidently deleted the wallet and all wallet backup files too and also forgot the keystore password. There was no way to restore the wallet back. Fortunately in my case the PDB which had encrypted data was supposed to be deco
7 comments
Read more

How to Find VIP of an Oracle RAC Cluster

<<Back to Oracle RAC Main Page How to Find Out VIP of an Oracle RAC Cluster Login clusterware owner (oracle) and execute the below command to find out the VIP hostname used in Oracle RAC $ olsnodes -i node1     node1-vip node2     node2-vip OR $ srvctl config nodeapps -viponly Network 1 exists Subnet IPv4: 10.0.0.0/255.255.0.0/bondeth0, static Subnet IPv6: Ping Targets: Network is enabled Network is individually enabled on nodes: Network is individually disabled on nodes: VIP exists: network number 1, hosting node node1 VIP Name: node1-vip VIP IPv4 Address: 10.0.0.1 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes: VIP exists: network number 1, hosting node node2 VIP Name: node2-vip VIP IPv4 Address: 10.0.0.2 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes:
1 comment
Read more

How to Power On/off Oracle Exadata Machine

<<Back to Exadata Main Page How to Power On/off Oracle Exadata Machine Oracle Exadata machines can be powered on/off either by pressing the power button on front of the server or by logging in to the ILOM interface. Powering on servers using  button on front of the server The power on sequence is as follows. 1. Start Rack, including switches  Note:- Ensure the switches have had power applied for a few minutes to complete power on  configuration before starting Exadata Storage Servers 2.Start Exadata Storage Servers  Note:- Ensure all Exadata Storage Servers complete the boot process before starting the   database servers 3. Start Database Servers Powering On Servers Remotely using ILOM The ILOM can be accessed using the Web console, the command-line interface (CLI), IPMI, or SNMP. For example, to apply power to server dm01cel01 using IPMI, where dm01cel01-ilom is the host name of the ILOM for the server to be powered on, run the
Post a Comment
Read more

How to Attach to a Datapump Job and Check Status of Export or Import

<<Back to Oracle DATAPUMP Main Page How to check the progress of  export or import Jobs You can attach to the export/import  job using ATTACH parameter of oracle datapump utility. Once you are attached to the job you check its status by typing STATUS command. Let us see how Step1>  Find the Export/Import Job Name You can find the datapump job information from  DBA_DATAPUMP_JOBS or  USER_DATAPUMP_JOBS view. SQL> SELECT OWNER_NAME,JOB_NAME,OPERATION,JOB_MODE,STATE from DBA_DATAPUMP_JOBS; OWNER_NAME JOB_NAME                       OPERATION            JOB_MODE   STATE ---------- ------------------------------ -------------------- ---------- ---------- SYSTEM     SYS_EXPORT_FULL_02             EXPORT               FULL       EXECUTING OR You can also find the job name for export/import in logfile in beginning itself. Step2>Attach to the Job and check status One you get the Export/Import Job Name attach the job and check its status. You can attach or det
7 comments
Read more

How to Create Pfile from Spfile and Vice Versa

<<Back to DB Administration Main Page There are instances when a DBA need to start the database using pfile, for example to trouble an instance startup error or to validate init file post parameter changes etc. In such situations you can create a pfile from spfile and once you are done with your changes you can create spfile from updated/modified pfile to start the database. How to Create Pfile from Spfile As sysdba execute following command  SQL> create pfile='/tmp/initOrcl.ora' from spfile; How to Create SPfile from Pfile As sysdba execute following command  SQL> create spfile from  pfile='/tmp/initOrcl.ora'; You can also create the pfile directly from memory How to Create Pfile from Memory As sysdba execute following command  SQL> create  pfile='/tmp/initOrcl.ora' from memory;
3 comments
Read more

How to export only data or only metadata using expdp

<<Back to Oracle DATAPUMP Main Page CONTENT parameter of expdp let you select whether you want to export only data or only metadata or both Default : ALL Syntax and Description CONTENT=[ALL | DATA_ONLY | METADATA_ONLY] DATA_ONLY exports only table row data; no database object definitions are exported. METADATA_ONLY exports only database object definitions; no table row data is exported. Exporting metadata only  $ cat exp_full_pdb01.par directory=dump dumpfile=EXP_PDB01_FULL%U.dmp logfile=EXP_PDB01_FULL.log full=y CONTENT=METADATA_ONLY $ expdp system@PDB01 parfile=exp_full_pdb01.par Exporting data only directory=dump dumpfile=EXP_PDB01_FULL%U.dmp logfile=EXP_PDB01_FULL.log full=y CONTENT=DATA_ONLY $ expdp system@PDB01 parfile=exp_full_pdb01.par
Post a Comment
Read more

ORA-15040: diskgroup is incomplete

<<Back to Oracle ASM Main Page ORA-15040: diskgroup is incomplete SQL> startup ORA-00099: warning: no parameter file specified for ASM instance ASM instance started Total System Global Area 1140850688 bytes Fixed Size                  8629704 bytes Variable Size            1107055160 bytes ASM Cache                  25165824 bytes ORA-15110: no diskgroups mounted Reason: The reason of this error is simply the ASM is not able to find the some or all the disks. Solution: Investigate and make all the disks available to ASM to mount the disk group. Make sure the disks has proper permissions. If you are using AFD check following services are online oracleacfs oracleadvm oracleoks  oracleafd   Source of Problem : Issue started after restart of the server After restarting the server when I tried to start the ASM instance its started throwing error.  ORA-15110: no diskgroups mounted Investigation in my Case Step1> ASM Logfile Scanning  Looked i
2 comments
Read more

Step by Step How to Configure Software Keystore/ Oracle Wallet

<<Back to Oracle DB Security Main Page How to Configure a Software Keystore A software keystore is a container that stores the Transparent Data Encryption master encryption key. To configure a software Keystore follow the steps below. Step 1: Set the Keystore Location in the sqlnet.ora File You can store the software keystore (also known as wallet) in file system or in ASM Diskgroup. Does not matter where you want to store the keystore you have modify the sqlnet.ora and make an entry accordingly Make an entry as shown below in $ORACLE_HOME/network/admin/sqlnet.ora file Example1: If Storing the Wallet in ASM ENCRYPTION_WALLET_LOCATION=  (SOURCE=(METHOD=FILE)    (METHOD_DATA=     (DIRECTORY= +DG_TST_DATA/$ORACLE_SID/wallet )    )  )   Example2: If Storing the Wallet in File System ENCRYPTION_WALLET_LOCATION=  (SOURCE=(METHOD=FILE)    (METHOD_DATA=     (DIRECTORY= /u01/dbatst1/admin/wallet/$ORACLE_SID)    )  ) NOTE: Ensure that the path you entered in  DIREC
7 comments
Read more

ORA-28365: wallet is not open while starting the database

<<Back to DB Administration Main Page ORA-28365: wallet is not open Encountered while Starting the Database $ srvctl start instance -d CDB001 -i CDB0011 PRCR-1013 : Failed to start resource ora.cdb001.db PRCR-1064 : Failed to start resource ora.cdb001.db on node node1.oracle.com CRS-5017: The resource action "ora.cdb001.db start" encountered the following error: ORA-28365: wallet is not open . For details refer to "(:CLSN00107:)" in "/u01/app/oracle/diag/crs/node1.oracle.com/crs/trace/crsd_oraagent_oracle.trc". CRS-2674: Start of 'ora.cdb001.db' on 'node1.oracle.com' failed Solution : Start the instance in mount mode SQL> startup mount; ORACLE instance started. Total System Global Area 2147483648 bytes Fixed Size                  2926472 bytes Variable Size            1392511096 bytes Database Buffers          738197504 bytes Redo Buffers               13848576 bytes Database mounted. Check Wallet status set linesiz
3 comments
Read more