DSXchange

Welcome aboard.

Server or parallel job? You have posted in the server job forum but have marked the job type as parallel. The techniques are different in each.

The short answer in each case, though, is to add the common key within the DataStage job design.

Does any kind of lock exist on this job? (Use LIST.READU command or Cleanup Resources tool in Director to find out.)

Server or parallel job? You have posted in the server forum but marked the job as parallel. The answer will be different depending upon job type.

Given that you can demonstrate that it's being passed en clair, I'd say you've encountered a bug which may or may not be a known bug. Your official support provider can (must, because you're paying them to) determine whether it's a known problem and, one way or the other, get it fixed.

It probably means that First Line is Column Names should have been set to True and wasn't.

A heavier emphasis is probably indicated on the fact that this solution is for versions earlier than 8.0 only. It's rather more difficult once you have version 8.0 and the unified metadata repository - so greater care should be taken in backing up - in taking regular exports of projects in which cha...

It's a matter of priorities. If you restore from backup as indicated, you get back the system as at the time of backup (assuming that the backup is a good one) and lose anything created/amended since that time. Of course, were you to export the newer objects/changed objects before attempting the abo...

To clarify, there is no dsenv script when DataStage engine is installed on Windows.

Tip: plan even more testing time. Have a test plan, including expected versus actual reporting.

If nothing else has changed in the interim, make sure no-one is using the project and no jobs are running, then rename the following objects then restore the originals from backup: DS_JOBS DS_JOBOBJECTS I_DS_JOBS I_DS_JOBOBJECTS If that is successful (in terms of recovering the deleted category), de...

Different problem. Please start new thread. Your problem relates to APT_COMPILE_OPTIONS and APT_LINKER_OPTIONS environment variable settings in 32-bit/64-bit environments.

Learn patience. You posted at 2:41am my time.

Nice one, but ugly when the data volumes start getting large.

Such blocking operations are not permitted in parallel jobs. Grimm's solution would require two jobs. You can use the same table as source and target but you need to make sure that self-deadlocking does not occur, typically by using a transaction size of 1 and an array size of 1 and partitioning on ...