I have a job that has been working fine for several months.

Our DBA changed the passwords on the database and updated the Default.properties file w/ the new password (All database components use context variables to make the connection).  Since he did, the job has begun to generate the following errors:

v_dummy|82

v_loglines|3

Exception in component tContextLoad_2

java.lang.NullPointerException

        at weeklypayroll.wpp_loadallocations2b_1_5.WPP_LoadAllocations2B.tDB2Input_2Process(WPP_LoadAllocations2B.java:1151)

        at weeklypayroll.wpp_loadallocations2b_1_5.WPP_LoadAllocations2B.tDB2Connection_1Process(WPP_LoadAllocations2B.java:367)

        at weeklypayroll.wpp_loadallocations2b_1_5.WPP_LoadAllocations2B.runJobInTOS(WPP_LoadAllocations2B.java:5644)

        at weeklypayroll.wpp_loadallocations2b_1_5.WPP_LoadAllocations2B.main(WPP_LoadAllocations2B.java:5528)


The job also gets some additional parameters from a database and sets context variables via a tContextLoad.  See the photos.

I inserted a tLogRow to dump the data fetched from the table.  As you can see, it is clearly working. The correct values are being returned from the database.  However, the tContextLoad fails for some mysterious reason. 

The job is deployed on an AIX server and was developed in Windows

Can anyone offer some insight or spot something wrong in the attached screen shots?
Also - from the dump/trace above, it does not appear that the tContextLoad is actually telling me WHERE in the code it failed. It is just saying it did.

Last edited by SMaz (2009-03-31 23:28:43)