Error in job connecting to DB2UDB

vigneshra · Post by **vigneshra** » Wed Dec 28, 2005 3:16 pm

Hi

Whenever we try to run some jobs, they abend with the following message

"The file `/db2home/sqllib/db2nodes.cfg' must exist and be readable by all users!"

But on the second or third rerun, they complete successfully. This does not happen to all the jobs and not during all the runs but this happens quite frequently and warrants for manual intervention and schedule delay.

Can anyone help out in avoiding this issue? Thanks very much in advance!

ray.wurlod · Post by **ray.wurlod** » Wed Dec 28, 2005 4:53 pm

That's a permissions problem. You will probably need your DB2 DBA to look at it. It's not a DataStage file.

vigneshra · Post by **vigneshra** » Thu Dec 29, 2005 9:18 am

Ray,

When I verified with DBA, they say that the file is having read permission to everyone. I myself verified and found that it is having read permission to all. Also, the job runs successfully when it is rerun for the second time. So I am confused if it is an interface issue. If multiple processes try to read an OS file, will there be any file locking issue happening?

ArndW · Post by **ArndW** » Thu Dec 29, 2005 9:32 am

vigneshra,

is your DB/2 server on the same machine as the DataStage server? If not, you will need to make sure that the file is readable by all users on both machines.

vigneshra · Post by **vigneshra** » Thu Dec 29, 2005 11:07 am

Hi Arnd

DB2 and ETL servers are installed in separate unix machines but all the users are given a read permission to that file. Also, job abends not happening always. They happen only occasionally and on rerun they finish successfully. That's why I am a bit confused.

ray.wurlod · Post by **ray.wurlod** » Thu Dec 29, 2005 2:58 pm

Could it be that, at times, your network is extremely busy and DataStage is unable to read /db2home/sqllib/db2nodes.cfg within its timeout interval due simply to network latency?

vigneshra · Post by **vigneshra** » Fri Dec 30, 2005 11:33 am

Yes. It is very much possible because this error happens only during the weekends when all the schedules run simultaneously to load different data marts. But the error message in director conveys a different meaning. That is why I was confused a bit. Thanks to Ray and Arnd for their replies.