DSXchange

Looking in the Director log won't help with finding out who last modified an ETL job. I believe that someone (Ray/Ken/Kim) posted some code to get information like that from the internal DataStage repository, does anyone remember seeing that? I did a quick search but couldn't turn anything up. That'...

No, and it doesn't look all that ambiguous, either.

If you take copy that same query into TOAD or SQL*Plus, do you still get the error?

Here is a Wiki definition of that particular "Segment Violation" signal, which typically indicates a programming problem.

That's the point I was trying to make. There's no reason, in a properly set up set of Sequencers and/or jobs, to have to go farm through everyone's log just to make sure everything ran ok.

What you set at the Project level only gets applied to new jobs when they are created. It becomes their default setting and changes at the project level have no effect on existing jobs. That's why you need a routine like this to force changes across existing jobs... the alternative is doing them one...

Yes... should be very version generic.

Kenneth Bland has posted some code in this thread that will run through a Project and set your Auto Purge options for you. Then your logs will start clearing themselves on a regular basis.

I've used it, it works great and has come in very handy.

And "StringSpaces" is what, a custom routine or transform? Can you post the code for that as well?

Which stage is the "XXX" stage that aborts?

How is the field defined in the Oracle table? How is it defined in the DataStage job? What stage are you using to access Oracle? If applicable, are you using Custom or Generated SQL to insert into Oracle? These can all affect the answer to your question.

Sorry, not really an answer to your question... Are you having issues where a Sequencer job calls other Sequencer jobs, there are errors in the lowest level jobs and the upper level Sequencer job doesn't know it? There are techniques discussed here, involving the use of DSLogInfo or DSLogFatal (pick...

Perhaps the "FAQ Man" should put together one on this topic. It sure seems to be a popular topic lately!

I think you are not finding bugs in 7.5, per se, these are more like examples where they've gotten tougher on enforcing their own rules. Things you basically "got away with" in earlier versions are not being allowed any more. Now, whether that's a good thing or not can be a matter of opinion, but .....

Case! Try changing 'CHASHEDOUTPUT' to 'CHashedOutput' and I think you'll be closer. Make sure the case of your hash file name matches exactly as well.

If the parameter type is 'Date', DataStage will put it into YYYY-MM-DD format - which would cause problems for your TO_DATE function as coded.

Cameron was just trying to point out the fact that if you do use CLEAR.FILE to empty a log file, you'll lose the control infomation that is there as well - notably any auto-purge settings you had for the job.

Not everyone realizes that and it's good to know if you go down that path.