DSXchange

Good point on the indexes, I'd forgotten that little tidbit.

What exact 8.x version do you have? What Oracle stage are you using? Have you checked with your official support provider to see if this is a known issue with your version?

Then your constraints are not appropriate. What is the actual value that column has when the lookup fails? It will only be a space if you've made it that, typically one would assume null or not null.

No, it's not mandatory but it is the best way to ensure exclusive access to the project in question. If you run the REINDEX command while there are any locks in place, it won't hurt anything but it also won't help... i.e. nothing will change. Hence the advice to bounce DataStage (note: not the serve...

You need DataStage "up" to do this, so stop and then restart it before running the fix to ensure this is happening in isolation.

Your repository is corrupted and the fix for that has been posted.

So, one way would be two output links from a Transformer with appropriate constraints on the STATE_DESC column.

Search the forums for DS.REINDEX for the command to run and for the very necessary caveats regarding its use.

You don't have a "sequential file reading" issue, you have a direct database lookup issue. Think about the change you made to the job, from a local possibly cached direct hashed file lookup to sending one database request at a time over the network. And I'll wager you have user-defined loo...

What are the six? Why not simply check and answer the question yourself?

It's still just the fact that there's really no need to do anything of the sort and once you upgrade to 8.x that "solution" goes out the window.

How about posting the actual unedited error rather than typing it in by hand. And I would assume you meant "cast" rather than "convert", yes? Regardless, I'd be curious exactly what "not allowing me to do so" meant.

Make sure you "upcase" the incoming data and handle lookup failures as well, i.e. your "NOT APPLICABLE" results.

I honestly have no idea what would cause the behaviour you are reporting. Reindexing can't hurt but I'd be surprised if it changes the behaviour... but then I've been surprised before.

That would mean your membership has expired and the date is listed with your member information on the 'Home' page. For your rather odd issue - have you gotten your official support provider involved yet?