DSXchange

Obviously, hence the little winky guy. However, I have encountered people that don't care if an update doesn't actually update anything. If you consider it a failure, as previously noted several times, you need to create a reference hash and do a lookup check ahead of time, validating your inserts a...

One simple way to make this error go away is to switch from ODBC to an OCI stage.

Oracle doesn't generate a warning if an update 'affects' zero rows and the OCI stage doesn't report it - it's an artifact of using ODBC.

Heck, anything can run on a cluster and can be made to failover from one cluster node to another. I've worked with SAs and DBAs to get it done in the past on a Tru64 cluster for DataStage Server, Oracle, etc. However, we had to define the failover rules - how it determined that something had failed,...

I know... but it trips off the tongue a little nicer the other way 'round.

By Jove, I think he's got it! Don't forget you can always use ODBC from the DRS stage to connect to anything you have drivers for as well. As to your last question... me thinks it sounds like a bug in the DRS stage implementation. But that would be something only Ascential/IBM support would be able ...

Ray Man, the Little Brother from Down Under.

Come along little brother, we need to get you back into your room where it's safe and warm and the bad mens won't get you...

Sreenivasulu wrote:I just found that the header of my message say datastage7. The issue is in datastage 5.2.2

Don't worry about it. In this case, that's not an issue - the advice still applies.

That's true, a clean install wouldn't require a new server. Just a good filesystem backup, an export (or two) of all current projects and the guts to pull the trigger on an uninstall. Some additional caveats would apply if there are Account hash files involved.

Go for it!

I would think that any native driver will be more performant (and robust) than an ODBC implementation. Even if you are using an ODBC driver supplied by the database vendor. The only 'advantage' I've seen is when using a thin driver as it doesn't require the vendor's client software be installed on t...

ray.wurlod wrote:Set NLSMODE to 0 in uvconfig, regenerate and restart DataStage.

Doh! Ok, disable is possible. What about uninstall?

Ray, did you mean that during the upgrade process to 7.5 that NLS support could be removed?

Narasimha, Take all this with a grain of salt, considering the fact that I've never had an opportunity to work in an NLS-enabled environment. But from hanging out here for a while, I think you'll find that - once installed - NLS is there forever and can't be disabled or 'uninstalled'. If your migrat...

Can you also tell me which one would yield a better result? Unfortunately, no. There are too many variables involved - variables related to your particular server, database design, table layout, etc, etc - to hand out one-size-fits-all advice. Array size is probably your best bet for a cheap 'perfo...

Understood. I'm well aware of the PeopleSoft implementations and how they leverage the DRS stage. Or why someone in general would want to use it. Heck, the PeopleSoft deal was the reason why Ascential had to put together this fancy new DRS stage in the first place. Question still stands. Why not lea...

Nope, sorry.

'Required column missing' means that a column required by the stage is not present in the file being read. I.E. you've declared six columns in the stage and it only found five in the file - and the sixth one is still marked as 'required' (the default) on the Columns tab.