DSXchange

Don't go boosting that array size without taking into account what it is doing to your memory buffers. Here's my rule of thumb. Each stage has (by default) about 3MB of buffer space. I always recommend calculating your row length, then taking a third of that buffer space and see how many rows fit in...

I would experiment with changing these two environment variables. $HOME and/or CWD. Set those at a job level. Force your job to fail and see where the dump goes.

Perhaps you can post how you resolved it so that future generations digging into the archives can also find the solution.

Best is like saying Chocolate is way better than Vanilla. It's a matter of taste. But... Standard Practice... Yes. I would say migrating objects with executables is Standard Practice. This allows for a full Unix side automated migration without any manual intervention or super fancy call to a window...

Reach out to IBM to see what they can work out with your company. They have worked with others.
Depends how big you are of course.

Those are all questions that you need to be asking IBM via a Case ticket (formerly PMR ticket).

Welcome to DSXchange Jinaanoo, just to be clear, nobody here is your official support team. We HELP however we can. You should reach out to your local DataStage admin team. You should reach out to your local DB2 DBA team. You should reach out to your IBM support if the first two do not work out. Typ...

are you doing a read or a write action? Partitioned Read? Anything in your SQL statement to pump up the connections? Nodes in the config file will not matter. You can drop the Oracle Connector stage to sequential mode vs parallel, but, you have to look at those settings. Is this a Multi Instance job...

Is anyone using Information Server (DataStage) Cloud Pak module?

Would like to get your opinion on it. Please msg me privately.

Thanks

I would NOT recommend copying the dsparms file from one project to another. You do not know if the difference in release level of datastage also constitutes new or removed entries in the dsparms file. You could script it, but then again, you will have trouble separating the user parms vs the default...

Is there an official link to an IBM statement on this? Need to forward to some internal customers.

Well, that does not give us a lot to go on. Here is what happens (roughly) under the covers. The datastage engine submits a dummy job to connect to that data repository. it also dumps a temp file or two to a path defined by APT_VIEWDATA_TEMP_DIR or if that is not set, then it defaults to your projec...

It's also not the error itself, it's just reporting that you took an exit.

paste more of the log.

Have you checked what is in your log file?

Warning messages perhaps?

if the gui is to slow because of the size of the log, look via command line.

$DSHOME/bin/dsjob -logdetail <project> <job.invocation>

Couldn't you just do a join with it being set to sequential rather than parallel?