DSXchange

One of those things entomologists study - a bug.

It really does depend on what's been left around. On the engine tier you can use the VERIFY.SQL command (a particular syntax), but you probably need to update the pertinent tables in XMETA - I am not aware of any provided script to clean up a partially deleted project in version 8.

Would it be OK to include these as properties in the job properties dialog?

Default = "HIGH" ?!!

The name and location of the project is recorded in at least three places; in UV.ACCOUNT, in UV_SCHEMAS and in the projects table in the combined metadata repository. It is far more important to identify any errors that occurred during the processing of the create project request. Check the logs of ...

Are there indexes on person_info.pid, address.pid and address.status?

When you DESCRIBE the table in Oracle, what is the data type of this column?

The On Error clause is a separate clause; it is not subordinate to the Else clause. Find and check out the syntax in the OpenSequentialFile routine posted here on DSXchange, or read about WRITESEQ in the DataStage BASIC manual.

Have you set the APT environment variable to have Oracle preserve, rather than trim, blanks?

Correct SDLC practice: compile in DEV and promote.

Is that Foundation Tools fix pack 1 (there's now a fix pack 2 for some platforms) or Information Server fix pack 1?

If the latter, what version of the Update Installer did you use?

QualityStage reference match.

Sainath, I think Ryan is looking for something entirely containable within a job.

reachmexyz wrote:Unfortunately it is not working.

"Not working" is the meaning of "unemployed".

DecimalToDecimal() where the target has a scale of 3 ?

What's in the job log for LD_TABLE_T_TRAN job, as opposed to the sequence log that you provided?