Qlik Replicate: Failed to read from ASM file using PLSQL with thread id '1' from block number

[narendersarva]

The following error is logged:

03058203: 2022-07-16T18:39:32:324014 [SOURCE_CAPTURE ]T: Failed to read from ASM file using PLSQL with thread id '1' from block number '3719644', size '32256' OCI Thread Id '6' [20014] (oradcdc_io.c:1347)
END OF TRACE ON DEMAND
03058203: 2022-07-16T18:39:32:323993 [SOURCE_CAPTURE ]E: OCI error 'ORA-03113: end-of-file on communication channel
Process ID: 272958
Session ID: 39 Serial number: 31803' [1022307] (oradcdc_io.c:1343)
03058202: 2022-07-16T18:39:32:334587 [SOURCE_CAPTURE ]T: OCI error 'ORA-03113: end-of-file on communication channel
Process ID: 272939
Session ID: 833 Serial number: 65186' [1022307] (oradcdc_io.c:1343)
03058203: 2022-07-16T18:39:32:324014 [SOURCE_CAPTURE ]E: Failed to read from ASM file using PLSQL with thread id '1' from block number '3719644', size '32256' OCI Thread Id '6' [20014] (oradcdc_io.c:1347)
03058199: 2022-07-16T18:39:32:337700 [SOURCE_CAPTURE ]T: OCI error 'ORA-03113: end-of-file on communication channel
Process ID: 272883
Session ID: 828 Serial number: 16912' [1022307] (oradcdc_io.c:1343)

Resolution

Frequent database disconnects build up the latency as we need to reprocess the redo log.

To address the ORA-03113 error:

1. Open the sqlnet.ora file on the Replicate Server in the Oracle client
2. Set the following:
   • BREAK_POLL_SKIP=10000
   • DISABLE_OOB=on
3. If the connection issue is not resolved with the above, we recommend the following settings on your database server (carried out by your database admin):
   
   • Set INBOUND_CONNECT_TIMEOUT_<listener_name>=180 in listener.ora
   • Set SQLNET.INBOUND_CONNECT_TIMEOUT=180 in sqlnet.ora
   • BREAK_POLL_SKIP=10000 in sqlnet.ora
   • DISABLE_OOB=on in sqlnet.ora
   • SQLNET.SEND_TIMEOUT = 6000 in sqlnet.ora
   • SQLNET.EXPIRE_TIME=10

Please work with your DBAs to check the alert logs during that time period. There will be an *.trc file that corresponds with the Session ID and the DBAs should be able to determine why the session is being terminated.

 

Environment:

Qlik Replicate