Integrated Replicat Troubleshooting MOS Doc ID 2819503.1.pdf

Tiny666

28页

0次

2025-01-10

5墨值下载

Integrated Replicat Troubleshooting

MOS Doc ID 2819503.1

Disclaimer: The information presented in this article is for educational

purposes only, applies to Oracle GoldenGate versions 19c and above, and

does not constitute any contractual agreement; either implied or explicit. Any

scripts or database query examples are presented where-is, as-is, and are

unsupported by Oracle Support and Development. Always refer to the official

Oracle documentation when planning changes to your Oracle GoldenGate

installations.

Integrated Replicat was first introduced in Oracle GoldenGate version 12.1.2, and at the time

was the preferred method for applying replicated data into Oracle Database targets.

Integrated Replicat is well suited for OLTP use cases as it provides the ability to automatically

calculate transactional data dependencies and auto tune parallelism based on the workload.

However, the drawback of Integrated Replicat is its inability to split-up and apply large

transactions in parallel. Therefore, as of Oracle GoldenGate version 19c, the best practice for

data apply into Oracle databases; especially for mixed workloads consisting of OLTP and batch

transactions, is to use Parallel Replicat (For Oracle GoldenGate 19c best practices refer to:

https://www.oracle.com/a/tech/docs/maa-goldengate-hub.pdf).

Even though the preferred, and best practice, apply mechanism for Oracle GoldenGate 19c and

above is Parallel Replicat, many organizations have yet to migrate from Integrated Replicat. In

this article we shall present troubleshooting information for when Integrated Replicat presents

performance issues.

Note

Parallel Replicat features two modes of operation; Parallel Non-integrated and Parallel

Integrated. Parallel Integrated Replicat should be considered for use cases requiring

Procedural Replication and Auto CDR. All other use cases should use Parallel Non-integrated

Replicat.

For more information on Parallel Replicat features, refer to the Oracle GoldenGate

documentation (https://docs.oracle.com/en/middleware/goldengate/core/index.html).

Integrated Replicat and Parallel Integrated Replicat are not supported for data apply to

Oracle Autonomous Data Warehouse

(https://docs.oracle.com/en/middleware/goldengate/core/19.1/oracle-db/using-ogg-

autonomous-databases.html#GUID-808668AB-68B0-4D4A-96C4-A18FC06D1299).

Integrated Replicat Architecture

The image below provides a simplified view of Integrated Replicat architecture.

In this view, Integrated Replicat consists of several distinct processes:

Replicat

The Replicat process:

 Reads the Oracle GoldenGate trail.

 Performs data filtering, mapping, and conversion.

 Constructs logical change records (LCR) that represent source database DML

transactions (in committed order).

 Attaches to a background process in the target database known as the database

inbound server by means of a lightweight streaming interface.

 Transmits the LCRs to the inbound server, which applies the data to the target

database.

Important Facts

DDL is applied directly, or in “direct mode”, by the Inbound Server Apply Network Receiver.

For direct mode apply, the operations are queued by the Apply Network Receiver until the

Inbound Server Appliers complete the current transactions in their queue. Then the Apply

Network Receiver applies the transaction to the database in direct apply mode through

Oracle Call Interface (OCI). While the direct apply is in progress, Inbound Server Appliers

cannot perform any data apply until the direct apply operation commits.

Direct mode apply degrades the performance of Integrated Replicat.

Inbound Server

The Inbound Server is a set of processes that run as part of the Oracle Database.

of 28

5墨值下载

ogg goldengate

关注

评论