java.sql.SQLException: Closed Connection

[Anonymous]

Hello Folks,

I am getting following error for only one job. As remedy I tried following options but issue persists. I am able to ping the ip address of Db. I am able to connect the DB using sql developer.

Remedy:

1. Used tDBConnection, used existing option in every tDBInput component.

2. Ojdbc14.jar was used for Oracle 10.

3. Kept the "-Djava.security.egd=file:/dev/../dev/urandom" in Use specific JVM argument at advanced settings of run tab.

4. Updated the java.security file with "-Djava.security.egd=file:/dev/../dev/urandom" and rebooted the server.

Exception in component tOracleInput_1
java.sql.SQLException: Closed Connection
at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
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:271)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:445)

thanks in advance

Crteja

[Anonymous]

Hi,

    Could you please specify which Talend product you are using and also the version? 

    If you could share the job screen shot and the screen shot of the Oracle connection component (after masking the sensitive data), it would help in more analysis of the issue.

Warm Regards,

Nikhil Thampi

[Anonymous]

Hi 

Am using Talend Data Integration 7.0.1 version. Required screen shots are attached.

DB Connection.GIF
JOb.GIF

[Anonymous]

Hi,

      Since you have specified that that you are using the SQL developer from same desktop, the connection should work fine for Talend also since both are using Java based engines. Remove all the other parameters and connect exactly like you are connecting in SQL Developer.

Could you please also check whether you are using tOracleCommit somewhere with close connection option as selected? 

     Another topic I would recommend is not to connect 20+ tables to one tmap. This is against Talend coding and best practices. Please use 2-3 lookups in each stage and pass the result set to next tmap (use multiple tmap if required). This will ensure easy debugging if an issue is coming and also better code readability within tmap.

Warm Regards,

Nikhil Thampi

[Anonymous]

Thanks Nikhil,

But I am still facing the same issue though I changed the design as you suggested. Can you think is there any way I can get rid out of the issue.

Attached the new job design screenshot.

Regards

Crteja

job.GIF

[Anonymous]

Hi,

     Apologies for the delay in reply as I was on vacation. Could you please verify whether you are able to connect when you are giving the DB details directly to tOracleInput and tOracleOutput components (instead of going through a tOracleConnect)? 

     If its urgent, I would suggest you to raise a Talend support ticket so that they can check the issue remotely and can resolve it quickly.

Warm Regards,

Nikhil Thampi