Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
We have a job that fails intermittantly; we're unable to find any specific cause. In the output logs for the job we see something similiar to:
Exception in component tPostgresqlOutput_11
java.sql.BatchUpdateException: Batch entry 4,351 INSERT INTO "mytable" ("column1","column2") VALUES ('value1','value2') was aborted.
Call getNextException to see the cause.
at org.postgresql.jdbc2.AbstractJdbc2Statement$BatchResultHandler.handleError(AbstractJdbc2Statement.java:2762)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:428)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(AbstractJdbc2Statement.java:2929)
at imports.importtopostgres_0_1.ImportToPostgres.tFileList_2Process(ImportToPostgres.java:12538)
at imports.importtopostgres_0_1.ImportToPostgres.tFixedFlowInput_1Process(ImportToPostgres.java:1901)
at imports.importtopostgres_0_1.ImportToPostgres.tMSSqlInput_1Process(ImportToPostgres.java:1497)
at imports.importtopostgres_0_1.ImportToPostgres.runJobInTOS(ImportToPostgres.java:15458)
at imports.importtopostgres_0_1.ImportToPostgres.runJob(ImportToPostgres.java:15258)
Normally in situations like this I would reproduce the error in TOS and disable the batch mode to see the error. Unfortunately this error seems to only happen when it's live and we can't disable batch mode because it takes far too long to run then. Is there a way to log out the nested exception/call getNextException on errors like this so we can dump it into the log output?
Thanks,
Rob