Job log not available.
Moderators: chulett, rschirm, roy
Job log not available.
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
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
Harish Jahagirdar
Hsbc Global Technology
Process Technology & Infrastructural Solutions
Hsbc Global Technology
Process Technology & Infrastructural Solutions
-
- Premium Member
- Posts: 783
- Joined: Mon Jan 16, 2006 10:17 pm
- Location: Sydney, Australia
-
- Participant
- Posts: 612
- Joined: Thu May 03, 2007 4:59 am
- Location: Melbourne
Your first issue -
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.I am not able to view either the logs or the job itself in a particular category(In Director)
Joshy George
<a href="http://www.linkedin.com/in/joshygeorge1" ><img src="http://www.linkedin.com/img/webpromo/bt ... _80x15.gif" width="80" height="15" border="0"></a>
<a href="http://www.linkedin.com/in/joshygeorge1" ><img src="http://www.linkedin.com/img/webpromo/bt ... _80x15.gif" width="80" height="15" border="0"></a>
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.
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.
Harish Jahagirdar
Hsbc Global Technology
Process Technology & Infrastructural Solutions
Hsbc Global Technology
Process Technology & Infrastructural Solutions
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.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
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".
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Hi Ray,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". ...
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.
![Shocked :shock:](./images/smilies/icon_eek.gif)
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
Harish Jahagirdar
Hsbc Global Technology
Process Technology & Infrastructural Solutions
Hsbc Global Technology
Process Technology & Infrastructural Solutions
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
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.
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.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Scary, eh? Been there, done that.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.![]()
![Wink :wink:](./images/smilies/icon_wink.gif)
As noted, that's what happens when you don't have exclusive ( and we do mean exclusive) access to the project in question.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
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.harishsj wrote:Hi Ray,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". ...
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
Assume everything I say or do is positive