Page 1 of 1

Any way to identify jobs that don't have design information?

Posted: Mon Jun 15, 2015 2:58 am
by kandyshandy
Sometimes a job loses it's design information. I am really not sure how this happens but it does. Is there a(ny) way to identify jobs that don't have design information?

One way that comes to my mind is to compile the jobs and look at the error message to find such odd ones. But this is time consuming when we want to check the odd ones among 2000+.

Posted: Mon Jun 15, 2015 5:56 pm
by kduke
should only happen when export executables only. You would have to look in DS_JOBOBJECTS to what is there. If ROOT record is missing we could probably give you some SQL to run.

Posted: Tue Jun 16, 2015 12:25 am
by kandyshandy
No luck Kim.

Initially, i was happy with your clue and tried queries against DS_JOBS and DS_JOBOBJECTS. After analysis, realized that some of the other jobs that have design information are not having ROOT record in DS_JOBOBJECTS.

I am still trying.. Do let me know if you get any idea.. Thank you.

Posted: Tue Jun 16, 2015 12:34 am
by priyadarshikunal
can you check xmeta if stage information is not present in the DSSTAGESXXXX or something like that but it exist in DSJOBSXXXXX. You should be able to join these tables on RIDs.

Posted: Tue Jun 16, 2015 2:54 am
by kandyshandy
:wink:

Access to XMETA is restricted.

Posted: Fri Jun 19, 2015 10:25 am
by kduke
You should always have a ROOT record with a design. You have corrupted DS_JOBOBJECTS it sounds like to me.

Posted: Thu Jul 09, 2015 9:56 pm
by kandyshandy
Sounds the same to me. There has been incorrect practice in this place for quite few years already. :(

Anyways, thank you. In general, how the corrupted universe is repaired?

Posted: Fri Jul 10, 2015 3:12 pm
by ray.wurlod
Depends how it's been corrupted, of course. You might begin by reindexing the local repository database (which is done on a project-by-project basis).