Skip to main content

Unplug PDB command fails ORA-46680 Master Keys Of The Container Database Must Be Exported

Unplug PDB command fails ORA-46680 Master Keys Of The Container Database Must Be Exported


Facing the issue while unplugging PDB after the clone.

SQL> alter pluggable database PDB1 unplug into '/u01/app/oracle/19.0.0/dbs/PDB1.xml'
*
ERROR at line 1:
ORA-46680: master keys of the container database must be exported

SQL> alter pluggable database pdb1 close;

Pluggable database altered.

SQL> conn / as sysdba

Connected.

SQL> alter pluggable database pdb1 unplug into '/u01/app/oracle/19.0.0/dbs/PDB1.xml';

alter pluggable database pdb1 unplug into '/u01/app/oracle/19.0.0/dbs/PDB1.xml'

*

ERROR at line 1:

ORA-46680: master keys of the container database must be exported 



This PDB have TDE configured and so the TDE mkeyid have to be exported into .exp file before the PDB unplug. So later during this PDB plug, the mkeyid can be imported from this .exp file into the new container wallet file.


Solution:

Export the TDE encryption keys of this PDB, before PDB unplug using ADMINISTER KEY MANAGEMENT EXPORT ENCRYPTION KEYS command.

SQL> alter session set container=PDB1;

Session altered.

SQL> select * from v$encryption_wallet; -- make sure the wallet is in open status.

 

SQL> ADMINISTER KEY MANAGEMENT EXPORT ENCRYPTION KEYS WITH SECRET "my_secret" TO '/u01/app/oracle/19.0.0/dbs/exportpdb1.exp' IDENTIFIED BY "<wallet password>";

keystore altered.

SQL> conn / as sysdba
Connected.

SQL> alter pluggable database pdb1 close;

Pluggable database altered.

SQL> alter pluggable database pdb1 unplug into '/u01/app/oracle/19.0.0/dbs/PDB1.xml';

Pluggable database altered.






Please do like and subscribe to my youtube channel: https://www.youtube.com/@foalabs If you like this post please follow,share and comment

Comments

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...

How to make flash work on IE or Edge with IE Compatibility

How to make flash work on IE or Edge with IE Compatibility With flash been ended from 1-Jan-2021, many applications using flash have stopped working the way they were built (like OEM, OBIEE, etc). The option you have to upgrade.  This method will give a workaround in IE or Edge in IE compatibility mode without upgrading. 1. Verify you have installed flash.ocx on your desktop. Typically, flash.ocx file is located in C:\Windows\System32\Macromed\Flash or C:\Windows\SysWOW64\Macromed\Flash according to your laptop OS system. 2. Edit mms.cfg from the location as a System Administrator In the case of the 64bit system, it might have mms.cfg under C:\Windows\SysWOW64\Macromed\Flash 3. Add below options into mms.cfg file. Note: AllowListUrlPattern list is an example. The URLs need to be replaced to your hosts those have Flash pages. SilentAutoUpdateEnable=0 AutoUpdateDisable=1 EOLUninstallDisable=1 EnableAllowList=1 AllowListUrlPattern=http://www.google.com/ AllowListUrlPattern=http://goo...