DSXchange

Sequential files are as reliable as the disk you write them to... and as reliable as the process doing the writing. Like with most things, you treat them right and they will treat you right. Mistreat them and all bets are off. -run job2 and output to the txt file.In this job ,there are 3 source file...

pradkumar wrote:How to make appear my output parameters (ErrornUM and ErrorText) in column section..

Type them in.

Also not an issue if you do not run with unlimited warnings... i.e. the limit set to 'No limit' = bad.

Could be... stopping the job doesn't always kill the Oracle query - that can take a DBA sometimes. Or you may just have a ton of messages queued up and it is still playing 'catch-up' actually writing them out.

First Person Shooters.

Well, then... mark the post as 'Resolved' and rate me a '5' dagnabbit!

Obviously, it's not supported syntax on your platform. Talk to an SA, ask them how you can shedule something to run on the third Friday of any given month.

Or use your Enterprise Scheduler if you have one - Control-M for example. Or write that routine!

ps. Already been suggested, Deepak.

Blocked by IE, I would wager. When you went to View it, did you get a little 'bleep' and a note saying that Internet Explorer was attempting to protect you from the evils of 'active content that could access your computer'? Click on the message and 'Allow blocked content'... then you'll get everythi...

6#3 is meant to represent the third occurance of the 6th day of the week - i.e. the third Saturday of the month. FYI, Friday is the day 5 of a week, while Sunday is the '0th' day. However, it's not standard syntax from what I've seen. I believe that only specialized implementations of cron allow sy...

Please help you with what? You haven't stated any kind of a problem or question here.

FYI - it *is* available online at the 'new' eService site. You'll need to have a logon and then look in the Recommended Patches section of the Software Updates / Downloads area.

https://www.ascential.com/eservice/download/patch/ds.do

Recompile the job you just looked up, see if that fixes the problem.

There's only one version of DataStage that allows parallel jobs to run in a Windows environment - 7.5x2. It sounds like you may have used a different version when you ran the second install.

AFAIK, the only way to run multiple bulk loads against one table is if the table is partitioned and each load is against a specific partition. Otherwise...

Each one can also truncate their own target partition as part of the load.

First, you need to find out how the data was encypted. Not sure how much plainer to make it. Any discussions on how to 'decrypt' it will be driven by that answer. Everything else is just table talk.