DSXchange

If you consider "Finished with warnings" to be "fine" then yes.

However, while watching this post I was wondering... perhaps all "-wait" does is return a zero when it successfully starts the job, regardless of how well the job itself runs? Perhaps all a non-zero result there means is that it couldn't start it. Check the documentation. I still prefer th...

Your understanding seems correct and I'm not sure why it's not behaving as you'd expect. However, I've never used the "-wait" option and have always preferred using "-jobstatus". What happens if you switch to that and then check for 1 (ran ok) or >1 for everything bad?

Like most everything else in PX Land, there is an APT variable to control that: add APT_DISABLE_COMBINATION to your mapping and set it to True.

I need this to get this done urgently. Then you should be working with your official support provider. Using the Stored Procedure stage doesn't mean you are forced to return values, you're not so don't think that's why you couldn't use it. However, I doubt it will support SQL Server from a UNIX ser...

Nope, not enough. As noted they need to be in your Path environment variable. My Computer / right-click / Properties / Advanced tab / Environment Variables, then edit Path in the System variables window to include them as noted.

Really? I don't see the connection but... ok.

Suggest you read the Connectivity Guide for Oracle Databases pdf where it discusses how to process the CLOB datatype via the Connector stage.

Sometimes all it takes is another pair of eyes.

Invoke the shell script from a DataStage job and the environment variables will be available for your use.

Just checking... you marked the post as "Resolved" after posting that deleting the data let the job run. Just wanted to make sure that wasn't all there was to this resolution.

Start by first explaining to us what exactly "doesn't work" means.

Documentation is a wonderful thing. The "s" option allows leading spaces in date and/or time formats. For example: %(m,s)/%(d,s)/%yyyy %(h,s):%(n,s):%(s,s) Would handle single digits in the month, day, hour, minute and second. You can also find discussions on how to handle the "am/pm ...

So... you didn't fix the job, you "fixed" the data?

Exactly, make sure these 'critical path' Server jobs are actually appropriate for assimilation into the PX collective.