Job log not available.

harishsj · Post by **harishsj** » Sun Jun 24, 2007 10:52 pm

Hi All,

I have a project running in the production environment. For the past few runs I am not able to veiw either the logs or the job itself in a particular category(In Director). Ultimately the sequence hangs and the main sequence which runs the whole project aborts.

I then have to repromote the job into the production environment and run the sequence once again, which then works eventually.

Can anybody suggest me how to takle this issue?

Thanks in advance

keshav0307 · Post by **keshav0307** » Sun Jun 24, 2007 11:21 pm

the jobs are multiple instance or single instance??
are you clearing the logs regularly.
do you get warnings in your job, try to remove those.

JoshGeorge · Post by **JoshGeorge** » Sun Jun 24, 2007 11:21 pm

Your first issue -

I am not able to view either the logs or the job itself in a particular category(In Director)

might be because there is a filter set in DS Director. Right click and make sure there are no filters set to view job logs. You have a main sequence which calls some jobs / sequences in this category rite? Then why not you drill down on job logs from main sequence using "related logs" option (On log type - RunJob) and find out the reason for job aborts.

ArndW · Post by **ArndW** » Sun Jun 24, 2007 11:22 pm

What happens when you try to view the log in the director - does it seem to "hang"? Does it only happen for this one job? Is it a PX job with thousands upon thousand of log entries?

harishsj · Post by **harishsj** » Sun Jun 24, 2007 11:42 pm

Let me answer you all.

1) Its a single instance job.
2) There are no filters set in the director.
3) The actual log is of only 13 lines.
4) When i try to veiw the log into the Director, I find the job missing in this particular category.

ArndW · Post by **ArndW** » Sun Jun 24, 2007 11:58 pm

If you know that the job is in the category but it doesn't show up in the director, you will need to run reindex from the DS.TOOLS menu. This is the typical symptom.

harishsj · Post by **harishsj** » Mon Jun 25, 2007 12:37 am

Hi ArndW ,

Can you tell me in short how reindex really works? And in what scenarios it's usefull?

ArndW · Post by **ArndW** » Mon Jun 25, 2007 12:44 am

There are many posts that go into detail on this subject that you can search for in DSXchange. The secondary keys are used to speed up access times on certain columns for certain control hashed files in DataStage. The view of jobs in the director is the result of one such query using secondary keys - if a job is there but doesn't show up in the director (and you don't have any filters active) then it is always due to a corruption on this index.

ray.wurlod · Post by **ray.wurlod** » Mon Jun 25, 2007 7:32 am

In this particular case it's the CATEGORY index on DS_JOBS that appears to be out of date. That's (my guess) why "the job is not being found in the category".

harishsj · Post by **harishsj** » Wed Jun 27, 2007 12:29 am

ray.wurlod wrote:In this particular case it's the CATEGORY index on DS_JOBS that appears to be out of date. That's (my guess) why "the job is not being found in the category". ...

Hi Ray,

I have done the reindexing on my Dev env. And you'd be surprise to hear that after the reindexing, not a single job was visible in the project.

I performed the

LIST DS_JOBS WITH NAME<jobname> and fortunately found them. I then again reindexed the Dev project and this time the issue was resolved.

Can you have any idea why this happened?

With such a expereince, I am not confident to do a REINDEX on my Prod Env.

Thanks

ray.wurlod · Post by **ray.wurlod** » Wed Jun 27, 2007 5:07 am

You did not have exclusive access to the project when you executed DS.REINDEX

Therefore the indexes were dropped, but not re-created. Do it again when you can guarantee that you have exclusive access and the indexes are successfully rebuilt.

Execute the LIST.READU command and make sure there is no entry of the form project&!DS.ADMIN!& - such an entry shows that there is a connected DataStage client.

chulett · Post by **chulett** » Wed Jun 27, 2007 7:04 am

harishsj wrote:I have done the reindexing on my Dev env. And you'd be surprise to hear that after the reindexing, not a single job was visible in the project.

Scary, eh? Been there, done that.

As noted, that's what happens when you don't have exclusive ( and we do mean exclusive) access to the project in question.

csrazdan · Post by **csrazdan** » Wed Jun 27, 2007 10:55 am

harishsj wrote:
ray.wurlod wrote:In this particular case it's the CATEGORY index on DS_JOBS that appears to be out of date. That's (my guess) why "the job is not being found in the category". ...
Hi Ray,

I have done the reindexing on my Dev env. And you'd be surprise to hear that after the reindexing, not a single job was visible in the project.

I performed the

LIST DS_JOBS WITH NAME<jobname> and fortunately found them. I then again reindexed the Dev project and this time the issue was resolved.

Can you have any idea why this happened?

With such a expereince, I am not confident to do a REINDEX on my Prod Env.

Thanks

One of the requirement for rebuilding indexes is that no user should be connected to the project on which you are rebuilding indexes. If all jobs disappeared this means that rebuild index was not able to get exclesive lock for objects. Repeating rebuilding index process will fix it.