Qlik Replicate: Task using Oracle as Source or Target is getting stuck

[David_Fergen]

A Task using Oracle Endpoint as a Source or Target is getting stuck at several occasions. Setting DEBUG or monitoring the Oracle server shows that the Client is stuck waiting for response.

Oracle provides a setting called ENABLE=BROKEN, that can enable keepalive functionality on the TCP/IP connection with the Oracle DB Server. This will allow the client to detect the dead connections.

Note that the timeout depends on the operating system's TCP/IP settings. You would usually want to set it to a lower value than default, which in many cases maybe 2hrs.

Solution:

The ENABLE=BROKEN can be enabled in the TNS entry or directly in the connection string as follows:

Example 1 -- Adding the property to the TNS definition on the client

<addressname> =
 (DESCRIPTION =
   (ENABLE=BROKEN) 
   (ADDRESS_LIST =
     (ADDRESS = (PROTOCOL = TCP)(Host = <hostname>)(Port = <port>))
   )
 (CONNECT_DATA =
   (SERVICE_NAME = <service_name>)
 )
)

Example 2 -- Adding the property as part of Replicate's connection string

You can provide Replicate with a full TNS entry maintained as a single line, for example:

(DESCRIPTION=(ENABLE=BROKEN)(ADDRESS=(PROTOCOL=TCP)(HOST=<hostname>)(PORT=<port>))(CONNECT_DATA=(SERVICE_NAME=<service_name>)))

[wali]

Most of our tasks are setup with following options for Oracle Source-endpoint.

asmUsePLSQLArray 

bulkArraySize: 5000

ReadaheadBlocks: 500000

and number of concurrent ASM Rad Threads: 4

Are any of these parameters impacting the Network packet sizes we are using Azure Express Route to pull data from Oracle OCI?

[Sonja_Bauernfeind]

Hello @wali 

I recommend posting your requirement in the Qlik Replicate forum, where our active product experts and your knowledgeable Qlik peers are better able to assist you.

All the best, 
Sonja