Why does SharePlex need TDE wallet and password on source database when TDE encryption is enabled?
On source SharePlex needs to be able to read the changes in the redo logs that are to be replicated.
When TDE encryption is enabled on the source database, SharePlex uses the TDE Master Encryption Key to decrypt TDE-protected data that must be replicated. SharePlex uses the Oracle wallet password to access the TDE Master Encryption Key.
If the wallet opens successfully, Capture connects to the decryption module and processes the data. If the wallet does not open, Capture remains in the initialization state until either the wallet is opened or the process is stopped. This is only applicable for the source database. For target we do not care about encryption as the Post process simply submits the changes to the target database and SharePlex does not need to read the redo logs.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center