DSXchange

Find out who/what is doing the purging and negotiate with them... usually the SysAdmins would be the ones worrying about things like that.

Which is why I didn't include that little nugget in the quote.

foryou wrote:Is this change as simple as changing the config file

Yes.

vennam445 wrote:When i execute this script from command line it works fine but not from the after job sub routine.

Full not relative paths when you do something like this, never mind the fact that (as noted) it is not the right thing to be doing.

Can you connect to any Oracle instance? Meaning, do you have a problem with just a specific instance or you cannot connect to any instance? :? If you can't connect to anything Oracle, you need to verify that the DataStage server has an Oracle client installed on it and is configured properly. Are al...

I would assume it's disabled because you are not logged in as the IS administrator. Don't forget there are more than one and one size does not fit all.

Suggest a search is in order.

Hard to say... something may have gotten corrupted and what really 'fixed' it was the recompile / repromotion of the job to the Production environment. We may never know the true culprit but at least it seems to be mended.

The 'direction' would be controlled by constraints. Perhaps leverage stage variables, one for each field to validate. Valid = 0, Invalid = 1 and lastly sum them. Good row constraint: sum = 0, reject everything else. Something like that, anywho.

I'd suggest you add the column back in and see if it starts to fail again. Wouldn't suprise me if it continues to work fine.

Great, time to mark this topic as Resolved then.

Running ok in Toad means next to nothing for something like this. If you switch the job from ODBC to OCI, you'll need to have an Oracle client installed on the DataStage server and DataStage would need to be 'configured' for native Oracle access as well... do you?

Since you're not using a client, there's not much to upgrade. Have you checked with your admins, see if anything O/S or network wise has changed recently. Obviously, something has. Wired driver same version as in dev?

Someone else will need to help with that px error, my suggestion was to leave the px job alone and create a Server job that just reads the file and sets USERSTATUS, that will work just fine. Write the output data itself to the Windows equivalent of '/dev/null' (NUL?) since you need to send it somewh...

Contact your support peoples and see if there is a patch to get the dssearch utility working again.