DSXchange

It is obviously a memory problem, related to the amount of data you are trying to pull through the ODBC stage at one time. Suggest you stick with the smaller array sizes that work and be happy with it rather than burn out many more brain cells. Couple of questions... You changed what "buffer", exact...

I checked with our DBA if the appropriate permissions were set, and they're all there. Why check with your DBA for questions on O/S level permissions? Seems like an odd choice of hero to me. In spite of their assurances to the contrary, sounds like classic permissions issues to me. Get back to a st...

Curious what made you think you could use Oracle-specific syntax anywhere except in Oracle? Rather than me explaining it, please explain in words for our home audience what exactly your regular expression is attempting to check for. Then people will be able to help with the DataStage syntax you need.

They did reboot under the 'old' kernel again to no effect, the same problems were noted and resolutions required. Didn't pull out the new CPUs as we didn't see how that would be relevant. So, with this 'work around' in place we booted back under the new kernel as it needs to be pressed into service ...

Then, as noted, it will tend to be "slow".

If you are going to do this manually, you need to do both - the VOC delete and the removal of the O/S files.

Not your typical 81002 so please bear with me. Scenario - new server setup just for DataStage, which installed and was running without issue. A standard 'root' install, was able to stop/restart DataStage from the command line as 'dsadm' like normal. Main 'ade' shared memory segment was owned by root...

Manoy1 wrote:Yet, when I re-ran it, the same error message was displayed.

Here's a crazy idea - how about posting the actual error message?

Post your derivations.

Post your derivations.

Got new problem? Post new topic!

No, the specific problem here is with the "-param" option, his syntax is technically fine. dsjob -run -mode NORMAL -param file='IBM/InformationSerer/Server/DSEngine/dsparams1.txt' GlobalSales_DEV CeilTest Error -3 getting information for parameter 'file' Status code = -3 DSJE_BADPARAM It found the j...

Sometimes we get other people on the same team jumping in and continuing a thread, wasn't sure if that was what was going on here. No worries. Actually, it wasn't an issue with the "-file" option for dsjob. If you look at the original post, you'll see it was a "-param" option for a parameter named "...

obtd?

Post the complete log entry, please.

So, Pete... is your "we" the same "we" as the "ds_is_fun" we that started all this?