My Oracle Support Banner

Unable to Complete Target Datastore Refresh (Doc ID 2782211.1)

Last updated on JUNE 10, 2021

Applies to:

Oracle Financial Services Data Integration Hub - Version 8.0.0.1 and later
Information in this document applies to any platform.

Symptoms


On : 8.0.7.4 version, TDR_OFSS

When attempting to perform Target Datastore Refresh, the following error occurs.

ERROR
-----------

TDR log:

[07-05-21 15:26:33.898][INFO ] [ODIPublishUtils][refreshTrgtDataStore]Target DataStore Refresh Successful
[07-05-21 15:26:33.898][INFO ] [ODIPublishUtils][refreshTrgtDataStore]--Target DataStore Refresh has been completed at: 2021/05/07 22:26:33 . Total Time taken - [13725] seconds
[07-05-21 15:26:34.061][INFO ] [ODIPublishUtils][refreshTrgtDataStore]entered to insert the row
[07-05-21 15:26:34.062][ERROR] [ODIPublishUtils][refreshTrgtDataStore]IO Error: Connection reset by peer
java.sql.SQLRecoverableException: IO Error: Connection reset by peer
at oracle.jdbc.driver.T4CConnection.createTemporaryBlob(T4CConnection.java:3188) ~[ojdbc8.jar:12.2.0.1.0]
at oracle.sql.BLOB.createTemporary(BLOB.java:661) ~[ojdbc8.jar:12.2.0.1.0]
at oracle.jdbc.driver.OraclePreparedStatement.setBinaryStreamContentsForBlobCritical(OraclePreparedStatement.java:6850) ~[ojdbc8.jar:12.2.0.1.0]
at oracle.jdbc.driver.OraclePreparedStatement.setBlobInternal(OraclePreparedStatement.java:11234) ~[ojdbc8.jar:12.2.0.1.0]
at oracle.jdbc.driver.OraclePreparedStatement.setBlobInternal(OraclePreparedStatement.java:11241) ~[ojdbc8.jar:12.2.0.1.0]
at oracle.jdbc.driver.OraclePreparedStatement.setBlob(OraclePreparedStatement.java:10983) ~[ojdbc8.jar:12.2.0.1.0]
at oracle.jdbc.driver.OraclePreparedStatementWrapper.setBlob(OraclePreparedStatementWrapper.java:459) ~[ojdbc8.jar:12.2.0.1.0]
at weblogic.jdbc.wrapper.PreparedStatement.setBlob(PreparedStatement.java:803) ~[com.bea.core.datasource6.jar:12.2.1.3]
at com.ofs.reveleus.DIH.model.ODIPublishUtils.refreshTrgtDataStore(ODIPublishUtils.java:423) [dih.jar:8.0.7.2.0_10177188939600]
at com.ofs.reveleus.DIH.model.ODIPublishUtils.refreshTrgtDataStore(ODIPublishUtils.java:76) [dih.jar:8.0.7.2.0_10177188939600]
at com.ofs.reveleus.DIH.rest.service.Refresh.invokeTDS(Refresh.java:177) [dih.jar:8.0.7.2.0_10177188939600]
at com.ofs.reveleus.DIH.rest.service.Refresh.access$000(Refresh.java:33) [dih.jar:8.0.7.2.0_10177188939600]
at com.ofs.reveleus.DIH.rest.service.Refresh$4.run(Refresh.java:153) [dih.jar:8.0.7.2.0_10177188939600]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_171]
Caused by: java.io.IOException: Connection reset by peer
at sun.nio.ch.FileDispatcherImpl.write0(Native Method) ~[?:1.8.0_171]
at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47) ~[?:1.8.0_171]
at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93) ~[?:1.8.0_171]
at sun.nio.ch.IOUtil.write(IOUtil.java:65) ~[?:1.8.0_171]
at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:471) ~[?:1.8.0_171]
at oracle.net.nt.TimeoutSocketChannel.write(TimeoutSocketChannel.java:215) ~[ojdbc8.jar:12.2.0.1.0]
at oracle.net.ns.NIOPacket.writeToSocketChannel(NIOPacket.java:211) ~[ojdbc8.jar:12.2.0.1.0]
at oracle.net.ns.NIONSDataChannel.writeDataToSocketChannel(NIONSDataChannel.java:181) ~[ojdbc8.jar:12.2.0.1.0]
at oracle.net.ns.NIONSDataChannel.writeDataToSocketChannel(NIONSDataChannel.java:132) ~[ojdbc8.jar:12.2.0.1.0]
at oracle.jdbc.driver.T4CMAREngineNIO.prepareForReading(T4CMAREngineNIO.java:96) ~[ojdbc8.jar:12.2.0.1.0]
at oracle.jdbc.driver.T4CMAREngineNIO.unmarshalUB1(T4CMAREngineNIO.java:534) ~[ojdbc8.jar:12.2.0.1.0]
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:485) ~[ojdbc8.jar:12.2.0.1.0]
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:252) ~[ojdbc8.jar:12.2.0.1.0]
at oracle.jdbc.driver.T4C8TTIBlob.createTemporaryLob(T4C8TTIBlob.java:182) ~[ojdbc8.jar:12.2.0.1.0]
at oracle.jdbc.driver.T4CConnection.createTemporaryBlob(T4CConnection.java:3183) ~[ojdbc8.jar:12.2.0.1.0]
... 13 more
STEPS
-----------
The issue can be reproduced at will with the following steps:
1. Try to perform Target Datastore Refresh after upgrading DB to 19c

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot perform Target Datastore Refresh successfully

Changes

 DB was upgraded from 12c to 19c

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.