DECRYPTTRAIL

Valid For

Replicat

Description

Use the DECRYPTTRAIL parameter to decrypt data in a trail or Extract file. This parameter is required in the following cases:

Data encryption is controlled by the ENCRYPTTRAIL \| NOENCRYPTTRAIL parameters.

For Oracle, if you are using wallet based encryption DECRYPTTRAIL does not require a cipher because it is recorded in the trail file header.

Default

None

Syntax

DECRYPTTRAIL ({AES128 | AES192 | AES256}, KEYNAME name)

DECRYPTTRAIL

Valid without any other options only if the trail or file was encrypted with ENCRYPTTRAIL without options to use 256-key byte substitution.

**{AES128 AES192 AES256}**

Valid for Encryption Profile and ENCKEYS methods.

When using the Encryption Profile method, then you need to create an encryption profile in advance and associate it with the Replicat.

When using the ENCKEYS method, an ENCKEYS file that has the master key must exist in the deployment_home/etc/conf/ogg directory.

KEYNAME name

The KEYNAME option is only required when the trail files from HP NonStop systems are encrypted using the ENCKEY option.

Example

Example 1

The following is an example of the encryption profile method.

DECRYPTTRAIL AES192

Example 2

The following decrypts using the ENCKEYS method.

DECRYPTTRAIL AES192, KEYNAME mykey1