Versions Compared

Old Version 4

changes.mady.by.user Vijayganesh Sivaprakasam

Saved on

compared with

New Version 5

changes.mady.by.user Vijayganesh Sivaprakasam

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

After completing the initial steps like running setup wizard, completing the ALL.sh script and before starting the MINE and APPLY, you can start the console and run the below command from the console to set the parameters for the TDE. After setting the below parameters you can start MINE/APPLY.

...

Changing Keystore password

Below are the steps that must be followed , when changing the keystore password.

  1. Shutdown the MINE process.

  2. Change the Keystore password ,when the keystore is set to AUTOLOGIN.


    Code Block
    SQL> ADMINISTER KEY MANAGEMENT ALTER KEYSTORE PASSWORD FORCE KEYSTORE IDENTIFIED BY kiwi123 SET dbvisit123 WITH BACKUP ;
 
keystore altered.


  3.  Now change the TDE password in the MINE to the new password in the console.


    Code Block
    dbvrep> set _MINE_TDE_PASSWORD = dbvisit123


  4. Start the MINE process.


Limitation when using TDE


  1. Keystore in ASM is not supported in Dbvisit Replicate 2.9.02
  2. Set Oracle Environment when starting MINE/APPLY when using TDE , since MINE searches for mkstore.
  3. Modifying a column in the source to encrypt/decrypt is not supported.
  4. Replicating to NON TDE target, adding a encrypted column does not work and creates a conflict , so as a workaround ignore the conflict and then add the column as non-encrypted column in the target and proceed further.