DSXchange

Everyone here needs help of one kind or another. Next time you might want to pick a subject line more appropriate for the problem you are having. That being said, the metadata you are using in the source stage doesn't match your actual file. I'm assuming here that you have saved your spreadsheet to ...

Actually, I'm the one that said 'checked off' in reference to the option. I suppose there are better words I could have used, but it's not something I'd consider 'slang' or all that confusing either. Checked off, ticked, selected, turned on... where's a darn thesaurus when you need one? Sorry about ...

Sure. Create a shell script to use FTP to get the files you need and run it once a week - either through cron or an enterprise scheduler or as a 'before job' option on a DataStage job that would process them after they arrive. Or have them ftp'd to your server and use the Wait For File activity in a...

You need to have a current support contract, which gets you access to Ascential's eServices website. It is available in the Download library there. Also recheck the post you referred to by Sudharshan. I just posted the description from the patch there so you can see if it sounds like it will fix you...

Unfortunately, the SP2 patch is for a different problem. From the description on eServices: Description: This patch resolves an issue with the DataStage Client when designing sequencer jobs (in particular the job, routine and user variable activity stage editors) which caused problems opening the st...

Are you running on Windows XP with Service Pack 2 installed? If yes, then you should download the SP2 patch available from Ascential's eServices website and see if that solves your problem.

No, not really. All things being equal, if "the same query in TOAD returns data" and DataStage says that the "data source is empty" then you are not connected to the same Oracle instance. You need to figure out why that is the case - check what you are using for Database Source Name / User ID / Pass...

You have to have a unique index or a primary key constraint over the 'key' fields so that Oracle (and DataStage) has a clue that the record is either new or a duplicate. My guess is you don't. It will only perform the second action, in this case the update, if the first action (the insert) fails - t...

Or set a Row Limit when you run the job. On the 'Limits' tab you can tell it to stop the job after processing X rows.

I'll bet you've got the 'Automatically handle actitivies that fail' option checked off, yes? A routine that does not return a zero is considered to have failed in that case.

Either turn it off or add a failure trigger so the sequence thinks you are handling it.

Yes. "I" or "D" goes down the first link, only "D" goes down the second. In other words, an "I" goes down the first link and a "D" goes down both.

Interesting they were written what would generally be considered to be 'backwards'... but either direction gets you the same results.

... and you haven't specified 'Reset if required then run'.

Same thing I was basically trying to say. If the sequencer starts the job and the job fails, the exception handler is not triggered.

No, not if it's like what I was seeing. Previous runs would be complete and error free and then suddenly... nothing. The next day it would run fine.

This was on an Alpha running Tru64, so it isn't something unique to HP/UX.

But in earlier versions, the Exception Handler will only 'fire' if something is wrong with the Sequence itself... a parameter it is trying to set does not exist, for example. A job failure won't trigger it.

Which creates the cron entry for you. Tony and I have already 'talked' about this after he found my Oliver posting where we'd suffered from the same problem. In my case, it went as suddenly as it came and Ascential never could come up with an explanation as to why it was happening. From what I remem...