Summary of GLOBALS Parameters
Here's a list of GLOBALS parameters available in Microservices and Classic architectures.
Table 1-1 GLOBALS Parameters for Microservices and Classic architectures
| Parameter | Description |
|---|---|
|
Allows Extract and Replicat to use columns that are part of an Oracle invisible index as a unique row identifier |
|
|
Changes the key selection logic so that it does not consider a nullable unique key as a viable candidate for uniquely identifying a row. |
|
|
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 |
|
|
Specifies the name of a default checkpoint table that can be used by all Replicat groups in one or more Oracle GoldenGate instances. |
|
|
Use this parameter to change the location of the Oracle GoldenGate credential store from the default location. |
|
|
Use this parameter to select which cryptographic library the Oracle GoldenGate processes use to provide implementation of security primitives. |
|
|
|
Adds a RULE hint to the DDL trigger |
|
Specifies the name of the DDL history table, if other than the
default of |
|
|
Enables support for three-part names for SQL/MX databases. |
|
|
Enables the monitoring of Oracle GoldenGate instances from Oracle GoldenGate Monitor and collects trend data for Performance Metrics Service. |
|
|
Specifies whether the Oracle GoldenGate process will be handling
records from |
|
|
Forces the inclusion of non-wildcarded source objects specified in
|
|
|
Specifies the name of the schema that contains Oracle GoldenGate database objects. |
|
|
Specifies a non-default name of the heartbeat table. The table name
|
|
|
Specifies the amount of time OCI client waits for a response from database server when releasing the connection. |
|
|
Controls the name of the masterkey that Oracle GoldenGate processes in a deployment will use to retrieve the key from the wallet. I |
|
|
Specifies the maximum number of process groups that can run in an instance of Oracle GoldenGate. |
|
|
Specifies the name of the Manager process when it is installed as a Windows service. |
|
|
Specifies the CCSID (coded character set identifier) of the database object names stored in the SQL catalog tables. |
|
|
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. |
|
|
Prevents the automatic suppression of duplicate informational and warning messages in the report file, the error log, and the system log files. |
|
|
Specifies an octal umask for Oracle GoldenGate processes to use when creating all files. |
|
|
Sends metrics data to the Performance Metrics Service to monitor Oracle GoldenGate processes of a Classic Architecture implementation. |
|
|
Sets the database session character set for all database connections that are initiated by Oracle GoldenGate processes in the local Oracle GoldenGate instance. |
|
|
This is automatically handled by OracleGoldenGate. |
|
|
Controls the number of digits of trail file sequence numbers that are written by an Extract or a data pump Extract. |
|
|
Forces the use of Internet Protocol version 4 (IPv4) by Oracle GoldenGate for TCP/IP connections. |
|
|
Specifies the location of the Oracle GoldenGate master-key wallet. |
|
|
Enables the Oracle GoldenGate Transparent Integration with Clusterware feature that allows you to continue using GGSCI to start and stop manager when GoldenGate instance is under the management of Oracle Grid Infrastructure Bundled Agents (XAG). |