Configure Existing HSM Wallet Migrated from Manual Software Wallet
Perform the following steps to migrate your existing HSM wallet to CAKM for Oracle TDE that was once migrated from Software wallet using VKM.
Start the database. Check the status of existing wallet in the Oracle database. Execute the following commands.
Output:
WRL_TYPE WRL_PARAMETER WALLET_TYPE STATUS FILE UNKNOWN CLOSED HSM HSM CLOSED Open the hardware keystore.
Note
In the command above,
<domain::cm_user:cm_user_password>
represents the domain, NAE user name, and its password. The domain, NAE user name, and password are case-sensitive. They must appear in double-quotes (" ") separated by a colon (:).The NAE user specified here is the owner of the encryption key created and stored on the CipherTrust Manager.
You can view the generated master encryption key on the CipherTrust Manager GUI.
Check the wallet status by executing the following query. It should be in open state.
Output:
WRL_TYPE WRL_PARAMETER WALLET_TYPE STATUS FILE UNKNOWN CLOSED HSM HSM OPEN [Optional] Generate a new MEK with CAKM for Oracle TDE.
View the MEK by executing the following command.
After the MEK is rotated using CAKM for Oracle TDE, you can access the data from column-encrypted tables or tablespace-encrypted tables.
(This step is applicable for Oracle RAC.) After running the above steps on the source node, run the following steps on all the destination node(s) to open the wallet.
Rename the existing
ewallet.p12
file.Copy the
ewallet.p12
file from the source node to the destination node in the cluster at the<software_wallet_location>/tde
location.Restart the database on the destination node.
Open the wallet using the below command.
This completes the migration of your keystore from VKM to CAKM for Oracle TDE.