Skip to main content
Announcements
A fresh, new look for the Data Integration & Quality forums and navigation! Read more about what's changed.
cancel
Showing results for 
Search instead for 
Did you mean: 
MattE
Creator II

Invalid operation: zero-length delimited identifier at or near """"

I'm trying to debug the standard logging joblet we use and I'm getting a weird error. I've got a simple job which just raises a warning via tWarn. I have a simple jobjet which catches that via a tLogCatcher then maps the value to a redshift database via a tMap and tDBOutput. 

 

When i run this locally it works with no errors and the rows appear in the Redshift database.

 

When i publish this to cloud and run manually i get the errors below and nothing is logged in the database. 

 

I've even hardcoded all the Redshift credentials so there are no context variables - just to elimiate that as a possibilty.

 

Any ideas?

 

Talend Enterprise 7.2.1

 

 

 

Failed 2020-01-02 15:38:28

tWarn_1 - tWarn failed to log message due to internal error: main_project.meloggingtest_0_3.MELoggingTest$TalendExceptionmain_project.meloggingtest_0_3.MELoggingTest$TalendException at main_project.meloggingtest_0_3.MELoggingTest.MEtest_1_tLogCatcher_1Process(MELoggingTest.java:8027) at main_project.meloggingtest_0_3.MELoggingTest.tWarn_1Process(MELoggingTest.java:1821) at main_project.meloggingtest_0_3.MELoggingTest.tFixedFlowInput_1Process(MELoggingTest.java:1632) at main_project.meloggingtest_0_3.MELoggingTest.tPrejob_1Process(MELoggingTest.java:1062) at main_project.meloggingtest_0_3.MELoggingTest.runJobInTOS(MELoggingTest.java:9525) at main_project.meloggingtest_0_3.MELoggingTest.main(MELoggingTest.java:9073)

 

Failed 2020-01-02 15:38:28

MEtest_1_tDBOutput_1 [Amazon](500310) Invalid operation: zero-length delimited identifier at or near """" Position: 29;java.sql.SQLException: [Amazon](500310) Invalid operation: zero-length delimited identifier at or near """" Position: 29; at com.amazon.redshift.client.messages.inbound.ErrorResponse.toErrorException(Unknown Source) at com.amazon.redshift.client.PGMessagingContext.handleErrorResponse(Unknown Source) at com.amazon.redshift.client.PGMessagingContext.handleMessage(Unknown Source) at com.amazon.jdbc.communications.InboundMessagesPipeline.getNextMessageOfClass(Unknown Source) at com.amazon.redshift.client.PGMessagingContext.doMoveToNextClass(Unknown Source) at com.amazon.redshift.client.PGMessagingContext.getBindComplete(Unknown Source) at com.amazon.redshift.client.PGClient.handleErrorsScenario1(Unknown Source) at com.amazon.redshift.client.PGClient.handleErrors(Unknown Source) at com.amazon.redshift.client.PGClient.directExecute(Unknown Source) at com.amazon.redshift.client.PGClient.directExecuteExtraMetadata(Unknown Source) at com.amazon.redshift.dataengine.PGQueryExecutor.execute(Unknown Source) at com.amazon.jdbc.common.SStatement.executeNoParams(Unknown Source) at com.amazon.jdbc.common.SStatement.execute(Unknown Source) at main_project.meloggingtest_0_3.MELoggingTest.MEtest_1_tLogCatcher_1Process(MELoggingTest.java:5322) at main_project.meloggingtest_0_3.MELoggingTest.tWarn_1Process(MELoggingTest.java:1821) at main_project.meloggingtest_0_3.MELoggingTest.tFixedFlowInput_1Process(MELoggingTest.java:1632) at main_project.meloggingtest_0_3.MELoggingTest.tPrejob_1Process(MELoggingTest.java:1062) at main_project.meloggingtest_0_3.MELoggingTest.runJobInTOS(MELoggingTest.java:9525)Caused by: com.amazon.support.exceptions.ErrorException: [Amazon](500310) Invalid operation: zero-length delimited identifier at or near """" Position: 29; ... 18 more

 

Info 2020-01-02 15:38:27

tWarn_1 - Message: Job Started. Code: 1000

Labels (4)
1 Solution

Accepted Solutions
MattE
Creator II
Author

I deleted the output rows in the tMap and did them again and this fixed the problem so there must have been a field different from the DB schema. 

View solution in original post

2 Replies
MattE
Creator II
Author

I've tried

  • moving the joblet logic within the main job
  • hardcoding the values in the tMap for every output so nothing is null
  • removing the tMap so it's just tLogCatcher->tDBOutput
  • Checked all the schemas match
MattE
Creator II
Author

I deleted the output rows in the tMap and did them again and this fixed the problem so there must have been a field different from the DB schema.