DSXchange

I'd also still be curious if you are local to your DataStage Server or not?

Because if I understood right, the "OCI has fetched..." error is a DS error, happening when reading+"casting" Oracle data from the source stage into its internal types.. No, it is an ORA as in Oracle error. You get it when you make an OCI call to fetch data with a X byte buffer for a particular fie...

Welcome! :D The short answer is 'no' as that history you are looking for is stored in individual hashed files, one per job, and not in the repository used to create a .dsx file. Your colleague would need to specifically dump whatever information you need, but there's no built-in mechanism to load it...

Because you were then able to use the parameter helper tool to populate the field? Then your whole issue was a typing error?

chulett wrote:At some point soon here, I would think you'd be better served by opening a case with your official Support provider rather than continuing to thrash here.

Thrash, thrash.

To answer the question asked - yes, of course.

No, there's no specific forum, just ask away. Searching should turn up several existant conversations, plus there is at least one FAQ posting.

First suggestion would be to ask a question.

When you need to 'pivot' columns out into multiple rows. You can help you out - read the online help available from the 'Help' button inside the stage for specifics.

Search is your friend! If you search for 'Printer memory segment removed' you'll find you're not the first person to ask this question.

Not in a Server job.

I guess nobody searches first anymore. [sigh] Your routine returned a value of '61', not a error code of 61. You have the option 'Automatically handle activities that fail' turned on in the Sequence job. That option considers any routine that does not return a zero to have failed. It thought your ro...

All Aborted/Restartable ones, yes.

Yes, you have to tell it that you want to run with unlimited warnings. From memory, you need to add -warn=0 to the command line.

Also, I'm still curious if folks are still prefering to write shell scripts? It seems that it is becoming an unnecesary thing to do. For jobs and job control, we've only got one shell script and that is your typical 'wrapper' script for dsjob that our Enterprise Scheduler (Control-M) uses. Of cours...