DSXchange

Please provide better explanation of problem first.

Any version should be available in both flavors, unless that's changed with 8.x. They used to refer to them as 'EE' for Enterprise Edition, which included both PX and Server, or 'XE' which was the Extended Edition - Server with some other components, MetaStage mostly from what I recall. Not sure wha...

Ok... then answer my last two questions.

Here, let me quote him for you (I don't think he'll mind). It's nothing new or anything we haven't said over and over already:

ray.wurlod wrote:<snip> But, if you're not permitted to change the design, there's nothing you can do to address this

Besides the fact that you would not want to set your PATH statement to that particular value, you wouldn't do that as part of the dsjob command. $PATH is reserved, I'd suggest you use a different name if you need a 'file path' variable. Wrapper your dsjob call in a script. Set the variable there bef...

Job compilation on clients is sometimes writing data in the "C:\Program Files\Ascential\DataStage" directory. Within our company it is not allowed to have write access on this directory. We really should be keeping a list somewhere of all the silly rules we've seen people having to deal with over t...

Sorry, but there really isn't anything else to suggest. Except... hmmm... talk to your DBA. Explain you've just switched from doing direct inserts into that table to bulk loading it. Have them make sure you've got the proper grants you'd need for that.

Ok... I don't see the correlation, but ok. So, now what? You remember to manually purge the logs on occasion?

Perhaps you should post your script?

The vast majority of problems we see where scripts 'run fine' from the command prompt but not from DataStage are where the script writer make too many assumptions about their environment.

Check this FAQ post for one approach.

Create a new job. All you need is one that reads the first record from your source file and writes that to a new file. Nothing more, nothing less. Heck, if you had the MKS Toolkit installed, a head -1 command would work for this as well.

And I wouldn't touch that routine with a ten foot pole.

Please explain exactly what "When I checked in the command prompt %path%, it gave a return as" means. What you've shown is correct for a PATH statement as it is a collection of directories to search inside in the order listed for executables in the absence of an absolute path. It's nothing you can ...

Changing the NLS_DATE format won't affect queries that specifically use TO_DATE() or TO_CHAR() properly. If you want some help, how about answering our questions? Let's see... * What stage are you using * Datatype of the REGIST_DATE field in Oracle * Datatype of the REGIST_DATE field in your job * W...

I left that little tidbit for you, Ray.

You shouldn't need user-defined sql for something simple like that. However, your syntax looks valid to me, what makes you think it didn't select the 'correct' records? Is your REGIST_DATE field a DATE datatype in the table or something else? Typically you'd use a TO_DATE for this, but either should...