DSXchange

I have promoted entire populations of jobs from VC into Test or Production when doing the initial loads. Just meant I don't always just do singletons or small groups.

Yuck. Suggest you call Ascential support and report that as a bug - as long as your version is 7.5.something.

Going through this myself right now. Deletes are a PITA in Version Control. When jobs get renamed you end up with old and new names in VC and no good way to deal as it never really deletes anything. HOWEVER, I was under the impression you could: a) Allow logical 'deletes' to happen via the 'Allow Co...

Have you tried install the SP2 related patch on Ascential's eSupport site?

Welcome aboard. Unfortunately, I've seen the same behaviour in the past in v6, opened a case with Ascential and never got a resolution. Biggest impediment being the fact that the problem is not reproducible. If it is like what I saw (from memory) the Status view made it look like the job never ran. ...

Try reinstalling the client software.

Hmmm... document design before coding... have to write that one down.

No, this just confuses things more. Which one of the two values 'when changed to 100 got rid of the error'?

Ray said Array Size > Transaction Size. That wasn't your problem, as best as I can tell.

Of course, that's the part that 'takes some time'. Just wanted to point out that - if you have the standard shortcuts on your desktop - it will automagically switch the properties of those for you to point to the currently active client version.

Something cool I didn't realise it did at first.

Just wanted to followup on this as the possibility of this being a problem has been haunting me... I have 7.5.1A installed on an HP/UX test server right now, putting things through their paces. I can find no problems when using heavily commented User Defined SQL in our weapon of choice - the OCI sta...

Exactly.

Install the client to two different directories but suggest you keep only one set of icons on the desktop. The MCM will switch those icons back and forth between the two versions as only one can be 'active' at any given time.

Have you been using Oracle stages up to this point and are now using a new stage (like OracBulk) or have you yet to get any Oracle stages working? On a UNIX server, it is configured in the dsenv file. There should be a Plug-In Configuration Guide which should walk you through the changes needed. Bas...

Sounds like the dreaded Windows XP Service Pack 2 related problem. There is a patch available on Ascential's eSupport website, download and install it and it should fix you right up.

I need to manually set the Jobstatus of the current job to aborted You can't manually set it, so put that approach out of your head. What you can do is build a routine to read the file which you can execute via the Routine Activity stage between the two jobs. Abort the routine (ie, call DSLogFatal)...

Does this mean that the hash file has null values in it? if so, what would be my next step in the process to debug the issue... No, it means the fields returned by the lookup will be null - not the data in the hashed file itself. So, yes, time to dig in and start debugging why the lookup is failing...