1. Verifying that your environment meets certification requirements:

   Make sure that you install your product on a supported hardware and software configuration. See the certification matrix for more details: GoldenGate Certifications.

   Oracle has tested and verified the performance of your product on all certified systems and environments. Whenever new certifications are released, they are added to the certification document right away. New certifications can be released at any time. Therefore, the certification documents are kept outside the documentation libraries and are available on Oracle Technology Network.

2. Using the system requirements document to verify certification:

   Oracle recommends that you use the Oracle Fusion Middleware Supported System Configuration document to verify that the certification requirements are met. For example, if the certification document indicates that your product is certified for installation on 64-Bit Oracle Linux 6.5, use this document to verify that your system meets the required minimum specifications. These include disk space, available memory, specific platform packages and patches, and other operating system-specific requirements. System requirements can change in the future. Therefore, the system requirement documents are kept outside of the documentation libraries and are available on Oracle Technology Network.

3. Verifying interoperability among multiple products:

   To learn how to install and run multiple Fusion Middleware products from the same release or mixed releases with each other, see Oracle Fusion Middleware Supported System Configuration in Oracle Fusion Middleware Understanding Interoperability and Compatibility.

The compatibility of the GG for DAA handlers with the various data collections, including distributions, database releases, and drivers is included in the certification document.

For more information, see the Certification Matrix.

This section describes additional Oracle GoldenGate for Distributed Applications and Analytics (GG for DAA) additional support considerations.

Pluggable Formatters—Support

The handlers support the Pluggable Formatters as follows:

• The File Writer Handler supports all of the pluggable formatters.
• The HDFS Handler supports all of the pluggable formatters.

• Pluggable formatters are not applicable to the HBase Handler. Data is streamed to HBase using the proprietary HBase client interface.

• The Kafka Handler supports all of the pluggable formatters.

• The Kafka Connect Handler does not support pluggable formatters. You can convert data to JSON or Avro using Kafka Connect data converters.

• The Kinesis Streams Handler supports all of the pluggable formatters described in the Using the Pluggable Formatters.

• The Cassandra, MongoDB, and JDBC Handlers do not use a pluggable formatter.

Java Delivery Using Extract

Java Delivery using Extract is not supported. Support for Java Delivery is only supported using the Replicat process. Replicat provides better performance, better support for checkpointing, and better control of transaction grouping.

MongoDB Handler—Support

• The handler can only replicate unique rows from source table. If a source table has no primary key defined and has duplicate rows, replicating the duplicate rows to the MongoDB target results in a duplicate key error and the Replicat process abends.

• Missed updates and deletes are undetected so are ignored.

• Untested with sharded collections.

• Only supports date and time data types with millisecond precision. These values from a trail with microseconds or nanoseconds precision are truncated to millisecond precision.

• The datetime data type with timezone in the trail is not supported.

• A maximum BSON document size of 16 MB. If the trail record size exceeds this limit, the handler cannot replicate the record.

• No DDL propagation.

• No truncate operation.

JDBC Handler—Support

• The JDBC handler uses the generic JDBC API, which means any target database with a JDBC driver implementation should be able to use this handler. There are a myriad of different databases that support the JDBC API and Oracle cannot certify the JDBC Handler for all targets.

• The handler supports Replicat using the REPERROR and HANDLECOLLISIONS parameters.

• DDL operations are ignored by default and are logged with a WARN level.

• Coordinated Replicat is a multithreaded process that applies transactions in parallel instead of serially. Each thread handles all of the filtering, mapping, conversion, SQL construction, and error handling for its assigned workload. A coordinator thread coordinates transactions across threads to account for dependencies. It ensures that DML is applied in a synchronized manner preventing certain DMLs from occurring on the same object at the same time due to row locking, block locking, or table locking issues based on database specific rules.  If there are database locking issue, then Coordinated Replicat performance can be extremely slow or pauses.

DDL Event Handling

Only the TRUNCATE TABLE DDL statement is supported. All other DDL statements, suh as CREATE TABLE, CREATE INDEX, and DROP TABLE are ignored.

You can use the TRUNCATE statements one of these ways:

• In a DDL statement, TRUNCATE TABLE, ALTER TABLE TRUNCATE PARTITION, and other DDL TRUNCATE statements. This uses the DDL parameter.

• Standalone TRUNCATE support, which just has TRUNCATE TABLE. This uses the GETTRUNCATES parameter.