StarETL Process Fails With Error: "class com.primavera.er.util.UpdateEtlParameters :: Io exception: Connection reset" on Linux or Unix (Doc ID 1539559.1)

Last updated on JUNE 08, 2017

Applies to:

Primavera Analytics - Version R2 and later
Primavera Data Warehouse - Version R3.0 and later
Generic UNIX
Generic Linux

Symptoms

When attempting to run star etl process on a Linux 64 bit RedHat, the following error occurs.

SYMPTOM #1

ERROR
-----------------------
staretl [ERROR] (Message) - class com.primavera.er.util.UpdateEtlParameters :: Io exception: Connection reset
java.sql.SQLRecoverableException: Io exception: Connection reset
    at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:101)
    at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:199)
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:263)
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:521)
    at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:418)
    at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:508)
    at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:203)
    at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:33)
    at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:510)
    at java.sql.DriverManager.getConnection(DriverManager.java:582)
    at java.sql.DriverManager.getConnection(DriverManager.java:154)
    at com.primavera.er.util.GeneralUtil.getConnection(Unknown Source)
    at com.primavera.er.util.UpdateEtlParameters.b(Unknown Source)
    at com.primavera.er.util.UpdateEtlParameters.start(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.primavera.er.util.JavaClassInvokerAction.doAction(Unknown Source)
    at com.primavera.er.util.CommandInvoker.a(Unknown Source)
    at com.primavera.er.util.CommandInvoker.invoke(Unknown Source)
    at com.primavera.er.util.CommandInvoker.main(Unknown Source)
Caused by: java.net.SocketException: Connection reset
    at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:96)
    at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
    at oracle.net.ns.DataPacket.send(DataPacket.java:150)
    at oracle.net.ns.NetOutputStream.flush(NetOutputStream.java:180)
    at oracle.net.ns.NetInputStream.getNextPacket(NetInputStream.java:169)
    at oracle.net.ns.NetInputStream.read(NetInputStream.java:117)
    at oracle.net.ns.NetInputStream.read(NetInputStream.java:92)
    at oracle.net.ns.NetInputStream.read(NetInputStream.java:77)
    at oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1034)
    at oracle.jdbc.driver.T4CMAREngine.unmarshalSB1(T4CMAREngine.java:1010)
    at oracle.jdbc.driver.T4CTTIoauthenticate.receiveOauth(T4CTTIoauthenticate.java:760)
    at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:368)
    ... 17 more
staretl [ERROR] (Message) - The main class (com.primavera.er.util.UpdateEtlParameters) failed
java.lang.Exception: UpdateEtlParameters failed
    at com.primavera.er.util.UpdateEtlParameters.start(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.primavera.er.util.JavaClassInvokerAction.doAction(Unknown Source)
    at com.primavera.er.util.CommandInvoker.a(Unknown Source)
    at com.primavera.er.util.CommandInvoker.invoke(Unknown Source)
    at com.primavera.er.util.CommandInvoker.main(Unknown Source)
staretl [INFO] (Progress) - Step 7/28 Part 1/1 - FAILED (1) (0 hours, 2 minutes, 28 seconds, 699 milliseconds)

Symptom 2:

An error may not actually occur, but the jdbc database connections take a long time to connect.  For example, in a 100% successful ETL log, EACH jdbc connection took approximately 30 seconds where it was previously taking 1-2 seconds to connect..
Log example:
<05.09.2014 13:16:40> staretl [DEBUG] (Progress) - DBConnection Manager got connection in 0 hours, 0 minutes, 30 seconds, 544 milliseconds

Symptom 3:

Staretlprocess.log may contain this error:
ORA-12516: TNS:listener could not find available handler with matching protocol stack

Symptom 4:

Completed steps take a long time to run to process 0 rows.

For example:
<07.10.2014 08:36:26> staretl [INFO] (Message) - Load2SCD Insert Time for 0 rows on table W_CODES_ACTIVITY_HD is 103.686 mins  (6221.14s) at rate 0/s

Symptom 5:

The jdbc connection issue can actually occur with ANY .sh file which is performing jdbc connections.  For example, a connection timeout can occur when running the configstar.sh and trying to connect to a database.

For any .sh file, it may be necessary to add the -Djava.security.egd=file:/dev/./urandom to the script.

 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms