DSXchange

I personally would be very careful as to whom I "allowed" under the cover access via dssh to. I would recommend limiting it to people in an admin role more so than any developer as there's just too much damage that can be done if people are romping around in there. At the places I worked, ...

No.

That's not to say you can't enforce that edict but nothing in DataStage will stop someone from creating PX jobs in your "Server only" project... just you and your big stick.

So... every job that use the OCI stage falls over dead like that? I would take a serious look at the Oracle client you have installed on that server - both from a version standpoint as well as how it is configured. Something is well and truly broken there.

IDENT1 is the 'invisible' transformer between your passive stages. One of your fields has grown large enough to be truncated, it would seem. Any CLOB or unbound NUMBER fields in the source?

Not nearly enough information to know. What active stage did you check for the link count?

... which leads me to believe it is the latter.

PaulVL wrote:And fyi: cores have nothing to do with data volume.

They said crores not "cores".

You are missing a very fundamental point here - the Server job recommendation was strictly for subject of your post, the "call select in nested condition" discussion; no one suggested using one for the loads themselves. In other words, just for this part: "call select stmt select acti...

PaulVL wrote:I was very nice meeting Ray W, Vincent and even Iron Man (inside joke).

Are you normally not nice when you meet people?

krisna wrote:please verify that your statement is correct;

Did you?

Also, did the stage generate this DML or is it user-defined?

Try it, let us know. Are you allowed to include a constraint expression when you mark it as an 'Otherwise' link? Are you allowed to have more than one 'Otherwise' link? If both answers are yes then it seems to me you can do it as you posted. Otherwise (no pun intended) you'll need to do it "lik...

Using DataStage doesn't change how things work from the command line. To use the Execute Command stage, use the exact same syntax you would from the command line. Now, think about how you are going to return anything that way. Your command line interface of choice will return a status rather than an...

Sorry... "use it" how / where / for what exactly?

Try: