Error while saving Parallel jobs & Compiling
Moderators: chulett, rschirm, roy
Have you tried doing a Save-As another name? If that works, delete the original job and then rename your copy. At V8 it is a bit more difficult to recover from this type of problem than at previous versions, as you also have the repository to deal with and the error could be in either place. Do you know what might have happened to cause the problem?
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 11
- Joined: Fri Apr 25, 2008 9:11 am
It does not get saved with another name. Please assist us in resolving this.ArndW wrote:Have you tried doing a Save-As another name? If that works, delete the original job and then rename your copy. At V8 it is a bit more difficult to recover from this type of problem than at previous v ...
Thanks & Regards,
Bhasker
-
- Premium Member
- Posts: 37
- Joined: Mon Dec 08, 2008 4:02 am
- Location: Milton Keynes, UK
A number of errors appear on the client for which you really need to see a Java stack trace to find the root cause.
If you look in the C:\Documents and Settings\Windows_Username\ds_logs directory you should find files named like dstage_wrapper_trace_NN.log (where N cycles from 1 to 20, to give you the log files for the last 20 DataStage sessions).
The files contain tracing information with timestamps and severities on the various lines - anything that looks like an ERROR needs investigating. You need to find the file that was being used at the time the problem occurred - usually the most recently modified if the client is still active.
If you look in the C:\Documents and Settings\Windows_Username\ds_logs directory you should find files named like dstage_wrapper_trace_NN.log (where N cycles from 1 to 20, to give you the log files for the last 20 DataStage sessions).
The files contain tracing information with timestamps and severities on the various lines - anything that looks like an ERROR needs investigating. You need to find the file that was being used at the time the problem occurred - usually the most recently modified if the client is still active.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: