A Optional Parameters for Integrated Modes

This appendix contains optional parameters that may be required when operating Extract in integrated capture mode or Replicat in integrated Replicat mode.

This appendix includes the following sections:

A.1 Additional Parameter Options for Integrated Capture

This section contains additional parameters that may be required for your Extract configuration.

Integrated capture uses a database logmining server in the mining database to mine the redo stream of the source database. You can set parameters that are specific to the logmining server by using the TRANLOGOPTIONS parameter with the INTEGRATEDPARAMS option in the Extract parameter file.

Note:

For detailed information and usage guidance for these parameters, see the "DBMS_CAPTURE_ADM" section in Oracle Database PL/SQL Packages and Types Reference.

The following parameters can be set with INTEGRATEDPARAMS:

  • ANNOTATEDDLSIZE: Controls the maximum length of the DDL text in bytes up to which the DDL could be annotated if applicable for the DDL. Any DDL text whose size is greater than this would not be annotated. The default value is zero. Oracle GoldenGate DDL filtering can take advantage of this annotation, if this parameter is set to a non-zero value.

  • CAPTURE_IDKEY_OBJECTS: Controls the capture of objects that can be supported by FETCH. The default for Oracle GoldenGate is Y (capture ID key logical change records).

  • DOWNSTREAM_REAL_TIME_MINE: Controls whether the logmining server operates as a real-time downstream capture process or as an archived-log downstream capture process. The default is N (archived-log mode). Specify this parameter to use real-time capture in a downstream logmining server configuration. For more information on establishing a downstream mining configuration, see Appendix B, "Configuring a Downstream Mining Database."

  • GETCTASDML: Enables CTAS functionality. When GETCTASDML is enabled, CTAS DMLs are sent from LogMiner and replicated on the target.

  • INLINE_LOB_OPTIMIZATION: Controls whether LOBs that can be processed inline (such as small LOBs) are included in the LCR directly, rather than sending LOB chunk LCRs. The default for Oracle GoldenGate is Y (Yes).

  • MAX_SGA_SIZE: Controls the amount of shared memory used by the logmining server. The default is 1 GB.

  • PARALLELISM: Controls the number of processes used by the logmining server. The default is 2. For Oracle Standard Edition, this must be set to 1.

  • TRACE_LEVEL: Controls the level of tracing for the Extract logmining server. For use only with guidance from Oracle Support. The default for Oracle GoldenGate is 0 (no tracing).

  • WRITE_ALERT_LOG: Controls whether the Extract logmining server writes messages to the Oracle alert log. The default for Oracle GoldenGate is Y (Yes).

See Section 3.5, "Managing Server Resources."

A.2 Additional Parameter Options for Integrated Replicat

The default Replicat configuration as directed in Chapter 9, "Configuring Oracle GoldenGate Apply" should be sufficient. However, if needed, you can set the following inbound server parameters to support specific requirements. You can set these parameters by using the DBOPTIONS parameter with the INTEGRATEDPARAMS option or dynamically by issuing the SEND REPLICAT command with the INTEGRATEDPARAMS option in GGSCI.

Note:

For detailed information and usage guidance for these parameters, see the "DBMS_APPLY_ADM" section in Oracle Database PL/SQL Packages and Types Reference.

See Reference for Oracle GoldenGate for Windows and UNIX for more information about the DBOPTIONS parameter.

  • COMMIT_SERIALIZATION: Controls the order in which applied transactions are committed and has 2 modes, DEPENDENT_TRANSACTIONS and FULL. The default mode for Oracle GoldenGate is DEPENDENT_TRANSACTIONS where dependent transactions are applied in the correct order though may not necessarily be applied in source commit order. In FULL mode, the source commit order is enforced when applying transactions.

  • BATCHSQL_MODE: Controls the batch execution scheduling mode including pending dependencies. A pending dependency is a dependency on another transaction that has already been scheduled, but not completely executed. The default is DEPENDENT. You can use following three modes:

    DEPENDENT

    Dependency aware scheduling without an early start. Batched transactions are scheduled when there are no pending dependencies.

    DEPENDENT_EAGER

    Dependency aware batching with early start. Batched transactions are scheduled irrespective of pending dependencies.

    SEQUENTIAL

    Sequential batching. Transactions are batched by grouping the transactions sequentially based on the original commit order.

  • DISABLE_ON_ERROR: Determines whether the apply server is disabled or continues on an unresolved error. The default for Oracle GoldenGate is N (continue on errors). The default setting enables Replicat to perform error handling based on the REPERROR parameter or the Conflict Detection and Resolution (CDR) parameters, if used.

  • EAGER_SIZE: Sets a threshold for the size of a transaction (in number of LCRs) after which Oracle GoldenGate starts applying data before the commit record is received. The default for Oracle GoldenGate is 9500.

  • ENABLE_XSTREAM_TABLE_STATS: Controls whether statistics on applied transactions are recorded in the V$GOLDENGATE_TABLE_STATS view or not collected at all. The default for Oracle GoldenGate is Y (collect statistics).

  • GROUPTRANSOPS: Controls the minimum number of operations that can be grouped into a single transaction. The default for Oracle GoldenGate is 250. It is recommended that this parameter be set with the Replicat parameter GROUPTRANSOPS in the Replicat parameter file, rather than with INTEGRATEDPARAMS. GROUPTRANSOPS is only effective when PARALLELISM is set to 1.

  • MAX_PARALLELISM: Limits the number of apply servers that can be used when the load is heavy. This number is reduced again when the workload subsides. The automatic tuning of the number of apply servers is effective only if PARALLELISM is greater than 1 and MAX_PARALLELISM is greater than PARALLELISM. If PARALLELISM is equal to MAX_PARALLELISM, the number of apply servers remains constant during the workload. The default for Oracle GoldenGate is 50.

  • MAX_SGA_SIZE: Controls the amount of shared memory used by the inbound server. The default for Oracle GoldenGate is INFINITE.

  • MESSAGE_TRACKING_FREQUENCY: Controls how often LCRs are marked for high-level LCR tracing through the apply processing. The default value is 2000000, meaning that every 2 millionth LCR is traced. A value of zero (0) disables LCR tracing.

  • PARALLELISM: Sets a minimum number of apply servers that can be used under normal conditions. Setting PARALLELISM to 1 disables apply parallelism, and transactions are applied with a single apply server process. The default for Oracle GoldenGate is 4. For Oracle Standard Edition, this must be set to 1.

  • PARALLELISM_INTERVAL: Sets the interval in seconds at which the current workload activity is computed. Replicat calculates the mean throughput every 5 X PARALLELISM_INTERVAL seconds. After each calculation, the apply component can increase or decrease the number of apply servers to try to improve throughput. If throughput is improved, the apply component keeps the new number of apply servers. The parallelism interval is used only if PARALLELISM is set to a value greater than one and the MAX_PARALLELISM value is greater than the PARALLELISM value. The default is 5 seconds.

  • PRESERVE_ENCRYPTION: Controls whether to preserve encryption for columns encrypted using Transparent Data Encryption. The default for Oracle GoldenGate is N (do not apply the data in encrypted form).

  • OPTIMIZE_PROGRESS_TABLE: Integrated Delivery uses this table to track the transactions that have been applied. It is used for duplicate avoidance in the event of failure or restart. If it is set to N (the default), then the progress table is updated synchronously with the apply of each replicated transaction. When set to Y, rather than populating the progress table synchronously, markers are dropped into the redo stream so when the apply process starts up, it mines the redo logs for these markers, and then updates the progress table for the previously applied transactions.

  • TRACE_LEVEL: Controls the level of tracing for the Replicat inbound server. For use only with guidance from Oracle Support. The default for Oracle GoldenGate is 0 (no tracing).

  • WRITE_ALERT_LOG: Controls whether the Replicat inbound server writes messages to the Oracle alert log. The default for Oracle GoldenGate is Y (yes).