Page 2 of 2
Posted: Fri May 30, 2008 4:03 am
by coface
ArndW wrote:At the TCL prompt or from the administrator, enter:
UVFIXFILE DS_JOBS
UVFIXFILE DS_JOBOBJECTS
and please post the results.
Here are the results:
>UVFIXFILE DS_JOBS
Beginning TRACE of DS_JOBS.
TRACE of DS_JOBS completed.
Scanning overflow buffers.
Scan complete.
9 group(s) processed.
11 group buffer(s) processed.
198 record(s) processed.
Number of data bytes = 13796.
>UVFIXFILE DS_JOBOBJECTS
Beginning TRACE of DS_JOBOBJECTS.
TRACE of DS_JOBOBJECTS completed.
Scanning free buffer chain.
Scan complete.
Scanning overflow buffers.
Scan complete.
681 group(s) processed.
924 group buffer(s) processed.
3971 record(s) processed.
Number of data bytes = 1031376.
Did you expect another result?
Rgds
Jan H.
Posted: Fri May 30, 2008 4:31 am
by ArndW
Yes, I thought it might show internal hashed file errors.
The quickest solution with the highest chance of 100% recovery is to do a full project export, delete the corrupted project, re-create it & load in the jobs. If you cannot do this then we can go about looking for the cause, but we've touched upon the most common causes already so it might take a while to diagnose & correct.
Posted: Fri May 30, 2008 5:38 am
by coface
ArndW wrote:Yes, I thought it might show internal hashed file errors.
The quickest solution with the highest chance of 100% recovery is to do a full project export, delete the corrupted project, re-create it & load in the jobs. If you cannot do this then we can go about looking for the cause, but we've touched upon the most common causes already so it might take a while to diagnose & correct.
I agree with you: it might be the easiest way to recreate the project. But I have to discuss that with our developers. I will let you know which way we went. Many thanks for your help so far.
Rgds
Jan
Posted: Mon Jun 02, 2008 12:11 am
by coface
ArndW wrote:Yes, I thought it might show internal hashed file errors.
The quickest solution with the highest chance of 100% recovery is to do a full project export, delete the corrupted project, re-create it & load in the jobs. If you cannot do this then we can go about looking for the cause, but we've touched upon the most common causes already so it might take a while to diagnose & correct.
I executed the command "DS.CHECKER" and it seems like that this repaired/solved the problem. When going through this forum I found an entry which suggested to run "DS.CHECKER" - therefore I decided to do this (even if I don't know anything about "DS.CHECKER").
Are these commands (DS.CHECKER, DS.REINDEX, ...) documented anywhere?
Rgds
Jan H.
Posted: Mon Jun 02, 2008 12:59 am
by ray.wurlod
No. At least nowhere that I've looked.
(Well, that's not entirely true - they are documented in my DataStage Administration class - though not, curiously, in IBM's Administering DataStage class.)
Posted: Mon Jun 02, 2008 2:43 am
by coface
ray.wurlod wrote:No. At least nowhere that I've looked.
(Well, that's not entirely true - they are documented in my DataStage Administration class - though not, curiously, in IBM's Administering DataStage class.)
Any change to get some further information from your documentation
?
Rgds & Thx
Jan H.
Posted: Mon Jun 02, 2008 6:09 am
by ray.wurlod
Only by taking the class, I'm afraid.
Maybe, in future, it will be made available through DSXchange Learning Center, but those arrangements are not yet in place.
Posted: Mon Jun 02, 2008 8:04 am
by coface
ray.wurlod wrote:Only by taking the class, I'm afraid.
Maybe, in future, it will be made available through DSXchange Learning Center, but those arrangements are not yet in place.
I wouldn't mind coming to Australia and taking the class
But many thanks anyway for helping with my issue!
Rgds
Jan H.