Connection to Exasol DB is broken frequently resulting in job failure

[KSD]

Hello,

I have developed a job that loads data from a CSV file into Exasol DB table(

which is based on ExaCloud)

using tDBOutput

.

The file contains around 1120099 records and is approximately 1.3GB.

While loading this data, the job frequently fails with the following error:

tDBOutput_1 Successfully reconnected after internal server error, transaction was rolled back.SessionID: 1689514193564183496

java.sql.SQLWarning: Successfully reconnected after internal server error, transaction was rolled back.

A ticket was created with Exasol to get some solution, but all they say is it could be

because of network issues, client issues and they cannot do anything here.

I am using the TMC and find the logs there. Is there some way to get more details from the log, like what was the cause of the connection failure?

Is there some way to resolve this issue from the code?

Has anyone come across such errors and have some idea how to resolve it?

Thanks in advance.

KSD

[Anonymous]

Hello,

Is there any more error message in TMC log? Execution logs? Could you please show us your current TMC Logs?

Best regards

Sabrina

[KSD]

Hello,

Here is the error message from the TMC log for the failure. Other than the reconnect message, i do not see anything else. The reason for the disconnect is not mentioned in the TMC log.

Do you need the log for the whole job? one that worked fine and one instance of failed one? Please let me know if you need anything more.

tDBOutput_1 Successfully reconnected after internal server error, transaction was rolled back.SessionID: 1689272480183465327

java.sql.SQLWarning: Successfully reconnected after internal server error, transaction was rolled back.SessionID: 1689272480183465327

    at com.exasol.jdbc.AbstractEXAConnection.addWarning(AbstractEXAConnection.java:1220)

    at com.exasol.jdbc.AbstractEXAConnection.setupConnection(AbstractEXAConnection.java:1190)

    at com.exasol.jdbc.AbstractEXAConnection.reconnect(AbstractEXAConnection.java:3025)

    at com.exasol.jdbc.ServerCommunication.handle(ServerCommunication.java:78)

    at com.exasol.jdbc.AbstractEXAConnection.communication(AbstractEXAConnection.java:2082)

    at com.exasol.jdbc.AbstractEXAConnection.communication_resultset(AbstractEXAConnection.java:1793)

    at com.exasol.jdbc.AbstractEXAPreparedStatement._execute(AbstractEXAPreparedStatement.java:293)

    at com.exasol.jdbc.AbstractEXAPreparedStatement.execute(AbstractEXAPreparedStatement.java:168)

    at com.exasol.jdbc.AbstractEXAPreparedStatement.executeUpdate(AbstractEXAPreparedStatement.java:326)

    at com.exasol.jdbc.AbstractEXAPreparedStatement.executeBatch(AbstractEXAPreparedStatement.java:142)

    at ors_prd.ors_shbl_prepare_0_1.ORS_SHBL_PREPARE.tFileInputDelimited_1Process(ORS_SHBL_PREPARE.java:16178)

    at ors_prd.ors_shbl_prepare_0_1.ORS_SHBL_PREPARE.tJava_1Process(ORS_SHBL_PREPARE.java:1596)

    at ors_prd.ors_shbl_prepare_0_1.ORS_SHBL_PREPARE.tPrejob_1Process(ORS_SHBL_PREPARE.java:1241)

    at ors_prd.ors_shbl_prepare_0_1.ORS_SHBL_PREPARE.runJobInTOS(ORS_SHBL_PREPARE.java:20936)

    at ors_prd.ors_shbl_prepare_0_1.ORS_SHBL_PREPARE.runJob(ORS_SHBL_PREPARE.java:20424)

    at ors_prd.ors_shbl_job_0_1.ORS_SHBL_JOB.tRunJob_3Process(ORS_SHBL_JOB.java:14723)

    at ors_prd.ors_shbl_job_0_1.ORS_SHBL_JOB.tJava_5Process(ORS_SHBL_JOB.java:14265)

    at ors_prd.ors_shbl_job_0_1.ORS_SHBL_JOB.tJava_3Process(ORS_SHBL_JOB.java:13282)

    at ors_prd.ors_shbl_job_0_1.ORS_SHBL_JOB.tJava_4Process(ORS_SHBL_JOB.java:12635)

    at ors_prd.ors_shbl_job_0_1.ORS_SHBL_JOB.tDBConnection_1Process(ORS_SHBL_JOB.java:11482)

    at ors_prd.ors_shbl_job_0_1.ORS_SHBL_JOB.tFileInputJSON_2Process(ORS_SHBL_JOB.java:10242)

    at ors_prd.ors_shbl_job_0_1.ORS_SHBL_JOB.tFileExist_1Process(ORS_SHBL_JOB.java:2231)

    at ors_prd.ors_shbl_job_0_1.ORS_SHBL_JOB.tJava_1Process(ORS_SHBL_JOB.java:1978)

    at ors_prd.ors_shbl_job_0_1.ORS_SHBL_JOB.tPrejob_1Process(ORS_SHBL_JOB.java:1704)

    at ors_prd.ors_shbl_job_0_1.ORS_SHBL_JOB.runJobInTOS(ORS_SHBL_JOB.java:25148)

    at ors_prd.ors_shbl_job_0_1.ORS_SHBL_JOB.main(ORS_SHBL_JOB.java:24655)

Thanks,

Deepti

[KSD]

Hello,

Is there any way to increase the log level to find out more details of the failure?

The TMC logs do not give enough information to resolve the connection problem.

I have checked the tStatCatcher Statistics under the Advanced settings of the tDBOutput too. But i do not see any difference in the logs.

Thanks,

KSD

[Anonymous]

Hello,

Please have a look at this article to see if it is what you are looking for.

https://community.talend.com/s/article/Log-management-and-monitoring-in-Talend-Cloud-D6MD7

Best regards

Sabrina