DSXchange

Use DS.CHECKER However, if you have already inflicted damage (like deleting a VOC entry), then DS.CHECKER will not work, and you will need to clear things manually. Let us know. Then analyze why the warnings are being generated, and re-design the job with a view to preventing them from occurring. No...

... except that the error handling is abysmal, so you had better hope that you never get any errors.

Typically people don't respond unless they know the answer.

Looks like you had better involve your official support provider.

Actually, FastLoad in DataStage can make a call through the API to append new rows to tables that already contain rows.

Search the web for information about why computers can not store FLOAT accurately, and the IEEE standards for representing a FLOAT. When a FLOAT is converted for display, there may be an arbitrary number of digits following the decimal point. It is not a DataStage issue; it's because you have chosen...

The error is in the network. There is not enough information about it generated to produce any meaningful diagnosis. Have your network administrator, possibly with the DBA involved, investigate where and why the network error is occurring.

You have misnamed the constraint in your After SQL, or the constraint as not yet been re-created after the last time you dropped it.

Why are you dropping a constraint in an After SQL anyway? It seems a very strange thing to be doing.

Read through everything above again. Then forget about DS.UNLOCK - it does not exist. Use UNLOCK.

The two links I gave you are public pages.

A good source of material is here - this is not the first time this question has been asked.

There is a need for a tool that allows one to check whether what is stored in the QualityStage Designer (in the MDB file) against what's on the QS server (what's been deployed).

Ideally, the tool would allow a QS Designer to synchronize (in either direction) with the QS server.

For a few cents per day you can read premium posts and contribute to the bandwidth costs of DSXchange.

You can ascertain the difference by reading the manual or on-line help or attending a training class. That will help you to make your final decision on technique.

Post the full detail of the error message, so that we can get all the other information that you're not telling us.

All the more reason not to use a routine.

Use a job to retrieve the value from Oracle.
That job puts the value into its user status area (search the forum for techniques).
The triggers from the Job activity are custom triggers that test the value of that user status area.

The status that you see in the Director (status view or monitor) is a report from a table as at the most recent time that the job updated the table. If the job has subsequently hung, aborted or been killed, the status is likely to show Running forever, until you might clear the status file. Any runn...