tOracleInput produces NullPointerException only when using existing connection
I have a job that insert rows into an Oracle DB using tOracleInput. It works fine using its own connection. I added a tOracleConnection and switched the tOracleInput to "Use an existing connection" and selected the connection. When it runs, the tOracleInput reports the following error. Ideas on what may be missing? This uses an Oracle metadata and context that is the same for both the tOraceConnection as when tOracleInput uses its own connection. If I leave tOracleConnection in the job and simply switch tOracleInput back to using its own connection, the job works again.
Exception in component tOracleOutput_2 (Employee)
java.lang.NullPointerException
at general.employee_0_1.Employee.tMSSqlInput_1Process(Employee.java:14721)
at general.employee_0_1.Employee.tHashInput_3Process(Employee.java:8553)
at general.employee_0_1.Employee.tMSSqlInput_18Process(Employee.java:2171)
at general.employee_0_1.Employee.runJobInTOS(Employee.java:23378)
at general.employee_0_1.Employee.main(Employee.java:23029)
[FATAL]: general.employee_0_1.Employee - tOracleOutput_2 null
Could you please share the job flow screenshot after adding tOracleConnection along with Component screen shot of the problematic tOracleOutput? Also could you please check the schema of the tOracleOutput and whether it is having any Null constraints?
Well, strange behavior... I went this morning to run the job again and take some screen shots to show the results. However, this morning it is working -- no NullPointerException error. Nothing has changed since I last ran it so no idea why it works this morning but produced an error last week.
However, I noted that, though it now runs, using the shared connection is dramatically slower than each tOracleOutput/Input using their own connection. So, I will continue to use individual connections rather than a single shared connection due to the poor performance.
