Summary of GLOBALS Parameters

Here's a list of GLOBALS parameters.

Table 2-1 GLOBALS Parameters list and description

Parameter	Description
`ALLOWINVISIBLEINDEXKEYS`	Allows Extract and Replicat to use columns that are part of an Oracle invisible index as a unique row identifier
`ALLOWNULLABLEKEYS \| NOALLOWNULLABLEKEYS`	Changes the key selection logic so that it does not consider a nullable unique key as a viable candidate for uniquely identifying a row.
`ALLOWNONVALIDATEDKEYS`	Allows Extract, Replicat, and other Oracle GoldenGate commands to use a non-validated primary key or an invalid key as a unique identifier. This parameter overrides the key selection criteria that is used by Oracle GoldenGate
`CHECKPOINTTABLE`	Specifies the name of a default checkpoint table that can be used by all Replicat groups in one or more Oracle GoldenGate instances.
`CRYPTOENGINE`	Use this parameter to select which cryptographic library the Oracle GoldenGate processes use to provide implementation of security primitives.
`DDLTABLE`	Specifies the name of the DDL history table, if other than the default of `GGS_DDL_HIST`.
`ENABLEMONITORING`	Enables the monitoring of Oracle GoldenGate instances from Oracle GoldenGate Monitor and collects trend data for Performance Metrics Service.
`ENABLE_HEARTBEAT_TABLE \| DISABLE_HEARTBEAT_TABLE`	Specifies whether the Oracle GoldenGate process will be handling records from `GG_HEARTBEAT` table or not.
`EXCLUDEWILDCARDOBJECTSONLY`	Forces the inclusion of non-wildcarded source objects specified in `TABLE` or `MAP` parameters when an exclusion parameter contains a wildcard that otherwise would exclude that object.
`GGSCHEMA`	Specifies the name of the schema that contains Oracle GoldenGate database objects.
`HEARTBEATTABLE`	Specifies a non-default name of the heartbeat table. The table name `GG_HEARTBEAT` is the default. This name used to denote the heartbeat table is used to create a seed and history table, `GG_HEARTBEAT_SEED` and `GG_HEARTBEAT_HISTORY` respectively.
`LOGOUT_RECV_TIMEOUT`	Specifies the amount of time OCI client waits for a response from database server when releasing the connection.
`MASTERKEYNAME`	Controls the name of the masterkey that Oracle GoldenGate processes in a deployment will use to retrieve the key from the wallet. I
`MAXGROUPS`	Specifies the maximum number of process groups that can run in an instance of Oracle GoldenGate.
`NAMECCSID`	Specifies the CCSID (coded character set identifier) of the database object names stored in the SQL catalog tables.
`NAMEMATCH parameters`	Controls the behavior of fallback name mapping. Fallback name mapping is enabled by default when the source database is casesensitive and the target database support both case-sensitive and case-insensitive object names, such as Oracle and Db2 LUW.
`NODUPMSGSUPPRESSION`	Prevents the automatic suppression of duplicate informational and warning messages in the report file, the error log, and the system log files.
`OUTPUTFILEUMASK`	Specifies an octal umask for Oracle GoldenGate processes to use when creating all files.
`SESSIONCHARSET`	Sets the database session character set for all database connections that are initiated by Oracle GoldenGate processes in the local Oracle GoldenGate instance.
`TRAILBYTEORDER`	This is automatically handled by OracleGoldenGate.
`USEIPV4 \| USEIPV6`	Forces the use of Internet Protocol version 4 (IPv4) by Oracle GoldenGate for TCP/IP connections.