DSXchange

Are these 'repeating' schedules? If so the Director will create an entry in cron for the job. If these are 'one off' jobs that run once at a specific date/time then they will be scheduled using at. Do the jobs show as being 'Scheduled' in the Director? It seems like you understand this but you need ...

Have your DBA get an explain plan while the updates are running to see if the index is being used. Up your Array size something larger, say 200? Depends on how wide your records are but anything is better than 1, performance-wise. Only use 1 when you absolutely have to.

Is there any more additional information, anything else you've seen 'from previous run' or is in the log not colored green?

Right, the 'poor performance' is on the Oracle end. If your where clause field(s) aren't indexed, each update is a full table scan. Also, what are your Array & Transaction sizes?

Any DataStage user will do, you don't need to be admin. That or build a Server job.

And no, not like you mean. Use the API.

Well, except for the segmentation violation in osh. No time to log anything else, it seems.

All of those questions could be easily answered by your official support provider...

Welcome! Unfortunately, it looks like they were added in the 8.1 release.

For the record, this is not a DataStage phenomenon but rather something common to pretty much anything doing buffered work including databases, named pipes and other ETL tools as well, for example. And as noted, the exact mechanism isn't ever detailed, just the effect noted. Another aspect of the is...

You need all of them.

I don't do SQL Server, hopefully someone else can double-check that. The concept is sound, all you should have to do is raise the error... at least that was my experience with Oracle procedures.

First suggestion would be to make sure that you are current on your fix packs. If you are then I'd suggest contacting your official support provider as it doesn't sound like you're doing anything wrong.

I think I know what you mean but can you clarify exactly what it is you meant by they 'become hardcoded'?

Don't worry what Oracle does in your example, it handles many things differently from everyone else, including 'cc'. It gave you 21 for the century because 2012 is a year in the 21st century. For everyone else they are equivalent to the first two digits of the year. So if you are receiving dates wit...

First, NOTFOUND should only be used for hashed file lookups. And lookups fail when there is no key match - it is an equi-join and the data must match exactly and that includes any spaces, trailing or otherwise.

Not enough information for anyone to do anything other than guess. What does the script do?