DSXchange

This can never evaluate to TRUE, so this constraint is equivalent to @FALSE. If it's connected to a ORABULK stage, chances are the data file being used is generated by a second output link. Because the ORABULK stage has HUGE overhead, a trick a lot of customers were told to use is to let DataStage g...

1. Analyze source system server load and make sure that machine is not overwhelmed right now. 2. Analyze target system server load and make sure that machine is not overwhelmed right now. 3. Extract your data to file to minimize delays imposed on source system because of target system drag. ODBC -->...

So what you are saying is that there were 3 columns in the source data file that did not map into the target OCI stage. How did you "remove" them? These columns need to be defined in the Sequential stage else it gives warning messages. You would have to suppress row truncation messages. What exactly...

What am I missing here? It has to be better than this, 'cos this is rubbish. You are missing a lot more, unfortunately, it's more of the same issues. That's just the way DataStage and table definitions work. Myself and others have spent a significant amount of time writing utilities to "reconnect" ...

If Trim(inXfmDataScrub.GENDER) # '' Then @TRUE Else @FALSE What does this mean? does it mean Trim(inXfmDataScrub.GENDER) Is null then @True else @False? thanks Do NOT confuse blank with NULL. Absence of value is blank, NULL is an ASCII character value, dependent on your system setting (some...

Make sure you use @FALSE, not @False. @FALSE is equated to 0, whereas @False is a non-existent variable. It still works, only because it is unassigned and would therefore give a message stating such and that ZERO would be used. There is no reason to build links and then constrain with @FALSE, unless...

@FALSE is a BOOLEAN variable. @TRUE is the opposite. In a constraint, the expression must either be true or false. So, to always make a row go down a link, putting @TRUE causes it to do so. Putting @FALSE prevents any rows from going down the link. Why do this in a constraint? For testing or debuggi...

Take a look here, even though it's Windoze it is still the same information.

http://www.dsxchange.com/viewtopic.php?t=85570

The close error is from link process reading the sequential load file. An abnormal termination means that something tragic occurred and the controlling DataStage process could not recover the remaining job processes. What I'm saying is that the sequential file closing error message is related to the...

Yeah, I forgot, you can't use the 64bit 9i client. Thanks Craig.

Check your LD_LIBRARY_PATH also points to the right shared libraries.

Example:

Drop the index and see if you have any load problems. If you do, then you get to log an issue with Ascential technical support. We're running out of options here, so if you can identify that a function based index is causing some issue to feed back to Ascential that it is unable to handle, then you ...

Which, 8i or 9i? There is a 7.3, 8, and 9 plugin.

Are you using the 9i plugin in DataStage?

DS 9i plugin works with 9i client ONLY
DS 8i plugin works with 8i and 9i client