tOracleOutputBulkExec- NullPointer Exception error

[Anonymous]

I'm trying this job execution in Talend Open studio.
The same scenario, when executed with Normal tOracleOutput/tLogRow, works fine.
While using tOracleOutputBulExecution, the intermediate data file out.csv is also created properly but while loading into the table I get this error.
Am I missing any setting here in Bulk Execution?

Job

Basic setting: 

Advanced Setting: 

Output: 

[vapukov]

Hi,

is your database on the same server with a Studio (Talend Job)?

[Anonymous]

No. Database is in Linux server and Open Studio in Windows.

[Anonymous]

Any update on this issue?

[Anonymous]

Hi,

    A quick query. Have you given Schema length definition for all your String variables? Since you have specified Create if not exists, this could be one reason of the error.

Warm Regards,
Nikhil Thampi

Please appreciate our Talend community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved 🙂

[Anonymous]

Yes, I have the schema string variables defined with length and I also tried "default" instead of  "Create if not exist" option.
I'm still getting the same error.

[Anonymous]

Hi,

    Could you please take a executable shell script and try to run directly from DB server to verify the idea shared by @vapukov ?

     Sometimes it might be due to firewall issues. I hope you are giving the connection details also correctly.

      Sorry. could not thing about any other right now. Any other ideas guys ?

 @rhall  @TRF  @uganesh @manodwhb 

Warm Regards,
Nikhil Thampi

Please appreciate our Talend community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved 🙂

[vapukov]

all talend BulkExec components require to have csv file on the local for database server disk - https://help.talend.com/reader/wDRBNUuxk629sNcI0dNYaA/Q3j6rgEPNXLD7q0lIPgpBg

as it is seen from the pictures in the first post - file created on the local machine, so not depending on other possible errors this must be checked first