Oracle Goldengate: Tune TCPBUFSIZE and TCPFLUSHBYTES parameters.

Tune TCPBUFSIZE and TCPFLUSHBYTES parameters:

The two RMTHOST parameters, TCPBUFSIZE and TCPFLUSHBYTES, are very useful for increasing the buffer sizes and network packets sent by Data Pump over the network from the source to the target system. This is especially beneficial for high latency networks.
It is recommended that you set these parameters to an initial value of 1MB (1,048,576 bytes) or the calculated value, whichever is larger.

Use the ping command to obtain the average round trip time (RTT).
For example: % ping ggtarget.doyensys.com Pinging ggtarget.doyensys.com [192.168.1.171] with 32 bytes of data: Reply from 192.168.1.171: bytes=32 time=31ms TTL=56 Reply from 192.168.1.117: bytes=32 time=61ms TTL=56 Reply from 192.168.1.117: bytes=32 time=32ms TTL=56 Reply from 192.168.1.117: bytes=32 time=34ms TTL=56 Ping statistics for 192.168.1.117: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 31ms, Maximum = 61ms, Average = 45ms

Calculate the bandwidth-delay product (BDP):
For example, if the network between the source and target databases is 125 megabits per second (Mbits) and the latency is 45ms the calculation would be as follows: BDP = (125,000,000 / 8) * 0.045 = 703125bytes

Multiply the result by 4 to determine 4xBDP:
For example: 4xBDP = 703125 x 4 = 2812500
In this example, because the result is more than 1MB, set the values of TCPBUFSIZE and TCPFLUSHBYTES to 2812500
The parameters are set in the Data Pump parameter file. For example: RMTHOST ggtarget, MGRPORT 7810, TCPBUFSIZE 2812500, TCPFLUSHBYTES 2812500 

Note: The maximum socket buffer size for non-Windows systems is usually limited by default.

Catch Me On:- Hariprasath Rajaram

Telegram:https://t.me/joinchat/I_f4DhGF_Zifr9YZvvMkRg
LinkedIn:https://www.linkedin.com/in/hari-prasath-aa65bb19/
Facebook:https://www.facebook.com/HariPrasathdba
FB Group:https://www.facebook.com/groups/894402327369506/
FB Page: https://www.facebook.com/dbahariprasath/?
Twitter: https://twitter.com/hariprasathdba

Oracle Goldengate: Configure the Streams pool for integrated Replicat

Configure the Streams pool for integrated Replicat:

When using integrated Replicat the Streams pool must be configured.
If we are using non-integrated Replicat means the Streams pool is not necessary.

The shared memory that is used by the servers comes from the Streams pool portion of the System Global Area (SGA) in the database. Therefore, you must set the database initialization parameter STREAMS_POOL_SIZE high enough to keep enough memory available for the number of Extract and Replicat processes that you expect to run in integrated mode. Note that Streams pool is also used by other components of the database (like Oracle Streams, Advanced Queuing, and Datapump export/import), so make certain to take them into account while sizing the Streams pool for Oracle GoldenGate.

The size requirement of the Streams pool for integrated Replicat is based on a single parameter, MAX_SGA_SIZE. The MAX_SGA_SIZE parameter defaults to INFINITE which allows the Replicat process to use as much of the Streams pool as possible. Oracle does not recommend setting the MAX_SGA_SIZE parameter.

Set the STREAMS_POOL_SIZE initialization parameter for the database to the following value:
(1GB * # of integrated Replicats) + 25% head room
For example, on a system with tw0 integrated Replicat process the calculation would be as follows:
(1GB * 2) * 1.25 = 2.5GB STREAMS_POOL_SIZE = 2500M

For example, on a system with three integrated Replicat process the calculation would be as follows:
(1GB * 3) * 1.25 = 3.75GB STREAMS_POOL_SIZE = 3750M

 

Catch Me On:- Hariprasath Rajaram

Telegram:https://t.me/joinchat/I_f4DhGF_Zifr9YZvvMkRg
LinkedIn:https://www.linkedin.com/in/hari-prasath-aa65bb19/
Facebook:https://www.facebook.com/HariPrasathdba
FB Group:https://www.facebook.com/groups/894402327369506/
FB Page: https://www.facebook.com/dbahariprasath/?
Twitter: https://twitter.com/hariprasathdba