DSXchange

Aarrgh! No. The job numbers MUST match up with the config, log and other hashed files in the Repository. It's likely that all the required information can be obtained from DS_JOBOBJECTS, but don't copy anything from test or production environments. Restoring DS_JOBS from backup (while no-one is usin...

There are tutorials from the vendor that ship with DataStage. Have you worked through these? Have you enrolled on any of the vendors' training classes (or those of third party providers)?

The message was not missing. Arnd is a premium poster, and his words are worth paying for. It's not expensive (less than 30c per day) to obtain a premium membership, after which you will be able to read the entirety of premium members' posts. Premium memberships are one of the ways that the hosting...

Do you have export/backup of the project? That's about the only way you're going to recover. Search the forum for ways to regain disk space, such as purging job logs and clearing old entries from &PH& directories in the project. Can you make the file system or quota larger? If not, move some...

But if you are assembling name and address data from multiple records the only matching you can do without QualityStage is exact matching. This may miss some probable duplicates.

Copy the appropriate lines from the DSParams file in the source project to the DSParams file in the target project.

Nothing will happen to data unless YOU program DataStage to make those changes.

For the integer key you might choose the SEQ.NUM hashing algorithm and for the non-integer key you might choose the GENERAL hashing algorithm but, in both cases, you would usually prefer dynamic (or "Type 30") as the type.

Consolidating all available information about the one customer into a single "best of breed" customer record is what QualityStage is about, but of course that implies that you do some form of matching between potentially duplicate customer records.

This IS an assumption, and suggests that you have the DataStage deadlock daemon running. When a job has no processes, this typically means that the job process has been killed. However, the job process (now defunct) still holds locks in the lock table, which is what you view with list_readu. You hav...

Is Runtime Column Propagation enabled? What (precisely) do you mean by "data integrity" here? In no stage type (except Sequential File stage*) do you need to read all columns from source. * Even in Sequential File stage there is a column property "drop on import" available. But y...

Insert will fail if a row with the particular key already exists in the table.

Possibly not. mmap errors usually result from the shared memory and semaphore settings in the kernel being set too low. Suggested values in the installation guide assume that no other consumers are running on the server - you may have to set these even larger than the values recommended for DataStag...

rhaddur wrote:

nagarjuna wrote:Can you please elaborate what exactly the dscc utility

The dscc utility is a client-based command line interface to the job compiler on the DataStage server.

Any idea or solution of how to overcome this ? Disable automatic handling of deadlocks in SQL Server. Of course, this will introduce different errors when the deadlock occurs. So, really, the best solution is prevention of deadlocks in the first place - don't design jobs that self-deadlock tables, ...