DSXchange

One record per 'hard coded' value that is.

Check the Installation and Upgrade Guide pdf.

Any particular error?

What's not to understand? You told it to commit every 1000 records and only sent it 600. In that case it only commits once at the end. It will always 'commit once at the end' regardless of the setting, the setting is what drives intermediate commits. In this particular case you had none.

Yes, there are other queries that can find what you are looking for, but they require intimate knowledge of the repository structure which is not made public by the vendor. Certain long-time users have that knowledge and queries have been posted here that a search could turn up, I would think. One m...

Your problem is the fact that you are converting the date from the format it is expecting to one that it can't use. Check your generated SQL - see the TO_DATE function and the mask it is expecting? Look familiar? What you have will work "as is", stop converting it.

Why so many substrings? Just:


Will work. Or just replace the third dash with a space:

You set the Inactivity Timeout in the Adminstrator for the server instance, and must be 'dsadm' (or equivalent) to change it.

Then somebody else or some other iteration of your process 'got busy' in your table. I've seen job designs that do things 'out of order' and lock themselves out of being able to truncate tables. Or someone (yourself included) could have been in the table via your favorite tool with an inadverdant tr...

Hmm... then it sounds like you gots more investigat'n to do.

And no, you don't have to use an Integer as the Server product is 'typeless' under the covers and basically treats everything as a string, but that's a discussion for a different day.

Re-establish any auto-purge setting afterwards.

I assume you either ran out of disk space or this hashed file went up against the 2GB Barrier and lost, yes?

Ah... that was the key piece I was missing. Thanks Arnd.

Didn't say it wouldn't work. Only that it is not a supported server platform. You need to understand that going into this.

And you must have the 7.5.x2 version.

Why would that be? You asked "How to Remove Duplicates" and "I have a scenario where I need to delete all the duplicates from the source file". I'm curious how exactly this stage fails to work for you. Have you tried it?

Welcome! :D Only one 7.x version of DataStage can actually run PX jobs on Windows and that's the 7.5.x2 version. Note, not 7.5.2 but literally 7.5.x2 only. Well, that and of course the new 8.x release. Second issue is XP is not a supported server platform. You may be able to get it to work but you w...