ENCRYPTTRAIL | NOENCRYPTTRAIL

Valid for

Extract

Description

Specifies encryption explicity for each output trail.

Use ENCRYPTTRAIL to encrypt data records in subsequent Oracle GoldenGate trails until a NOENCRYPTTRAIL is encountered. This applies to EXTFILE, EXTTRAIL, RMTFILE and RMTTRAIL entries. ENCRYPTTRAIL is not recommended for RMTBATCH.

If you plan to use AES encryption or multiple flavors of encryption, then it's recommended to not use this parameter, but instead specific each encryption method as an option to EXTTRAIL, RMTTRAIL, EXTFILE, RMTFILE.

AES trail encryption on HP NonStop currently uses the ENCKEYS file to store the trail master key. There is no provision in the trail file header to store a keyname, so you must specify that keyname in downstream readers with DECRYPTTRAIL and the key must match the key at the source.

AES trail encryption on HP NonStop cannot currently use the WALLET file used in theOpen System Oracle GoldenGate products. Do not use AES encryption to or from OpenSys using the Oracle Wallet. To use AES encryption to and from OpenSys, you must use the ENCKEYS file implementation.

Oracle GoldenGate trail files that contain any flavor of AES encryption can only be interrogated with the AES enabled version of LOGDUMP, which is LOGDUMPA.

LOGDUMPA can not be used to interrogate TMF.

Default

NOENCRYPTTRAIL

Syntax

ENCRYPTTRAIL ← (Deprecated)
ENCRYPTTRAIL (GGS) ← (Deprecated)
ENCRYPTTRAIL (<AES>, KEYNAME <name>)

AES can be AES, AES128, AES192, or AES256.

The default is AES256.