DSXchange

Classic problem - a relative path to the script. Use an absolute one in cron.

A good source for help with Oracle questions should be your friendly neighborhood DBA-man. And as noted, you should be able to easily Google up the manuals on Oracle's site and others. If you are working with Oracle, you really should be familiar with it, DataStage or no DataStage. You'll also find ...

You either need to pass the 'stamp' in as a job parameter (we do this) and then use #it# in the name, or create a constant filename and then rename it in the O/S after job. It's been discussed here a bajillion times.

Understood. Yes, the -9 kill is frowned upon but that doesn't mean it should never be used. You may not actually have needed it in this case, but if the other kill levels failed to stop the thread dumping log messages, then I certainly would have gone for the 'sure kill'. Still wondering what exactl...

This isn't difficult and really shouldn't have generated this many replies. Sure, a trigger is possible but I've seen way too many places that are 'trigger shy' for lack of a better term. Sure, you can use a lookup to select the nextval from dual so it just becomes another data value in the job, but...

Not sure how you can say "the null is handled" when your error is "Nullstringarguement". What do you have in the way of null handling at this point?

A continuation of this post. Syntax was requested there and not provided, perhaps we'll have more luck here.

Looked up the term as I hadn't heard it used like this.

http://en.wikipedia.org/wiki/Mantissa

Also found this:

http://en.wikipedia.org/wiki/Significan ... antissa.22

Doesn't really help, just thought it was interesting enough to share.

kcbland wrote:That's why I said: Kill the thread. Clear the log from Director.

Exactly. Why reimport the job just for this? Kill/Clear/Done.

ps. What are you considering "support files"?

Why not go for the traditional 'semaphore' file? Don't poll for the actual file, but have them touch into existence an empty file that you poll for? When it shows, you know the other is ready and can be picked up.

It also means the job is running, which what it sounds like you've said you've done. The only way to allow multiple 'copies' to run at the same time it to make them multi-instance and use distinct Invocation Ids.

Ah... missed the fact that you only have two column names but three values in your sql again:

How many columns are defined in your stage? I'm guessing the answer isn't "two".

Sure. How about subtracting the first day of the target date (internal format) from the first day of the next month, then subtract 1?

just4u_sharath wrote:

chulett wrote:Apparently what you have not done is read the docs.

Yes. Its true. So if any condition returns other than zero, then i should not use routine.

Again, no. And again, the docs describe how to use automatic handling with a routine that does not return a zero. It's all in the triggers.