DSXchange

Yes, it means you haven't properly configured DataStage to support the OCI stages. Read the Configuration Guide for the steps needed, they involve changes to your dsenv file to set an ORACLE_HOME and include the Oracle libraries in your appropriate LIB_PATH environment variable. Once done, you'll ne...

Definitely have a chat with your DBA. In the meantime, unless you are using wire drivers with the ODBC stage and for some reason really want to stick with the ODBC stage, why not switch to OCI? You won't have these issues with the OCI stages.

Another guess. There's more to the error message, perhaps even an error -14 buried somewhere. Things run fine individually because you are not taxing your system. All at once, there is too much going on and there aren't enough resources available to support them running at the same time. You may al...

Possibly... would need Vijay to pop back in and clarify the database and ODBC drivers in use here.

Guys - where was the 'O' word ever mentioned? Oracle doesn't return status messages like that, looks more like a DB2 thing to me.

You enable 'auto start' by changing the start value to a 1 and timer is how many seconds it sleeps between 'runs'.

Aha!

No... figured I'd start where I stood the best chance of getting an answer. Ah, well. Monday [crosses fingers] we'll be on 7.5.1A and I'll check if the behaviour is any different once we're upgraded and if not, ping Ascential.

Correct. Unfortunately, most people won't bother to switch tabs and constantly run jobs with the default value... hence the desire to change the default.

You'll need specific permissions to truncate tables granted to your user as well. That, at times, can be quite an uphill battle.

Turn off the Prefetch to memory option and see what happens.

Time to talk to your DBA, then. It's a database issue, not a DataStage issue.

Three months? Care to share why that might be? Any lessons learned might be helpful for others in the same boat.

What got accumulated into the log? Warnings? What stage and database are we talking about here? Paste one of your log messages here so we can see it.

Roy, I don't see anything obviously wrong with what you are doing. Are you sure the timestamp is the problem and it's not something else in the query? Ok, the timestamp in the table is '2006-01-01' but what is the value of the P_DATE parameter?