DSXchange

Not to argue with Ray, but the disable lock for updates means that the reference of a row will put a lock on that row. Failure to write to that row leaves a lock hanging. The job will degrade in performance as the internal lock table progressively fills with unrelieved locks, until the job basically...

test is a unix command for seeing if a file exists, is readable, etc. Ray's suggestion only works on PX installs on Windoze because MKS Toolkit gets installed with PX. To abort if a file has data is easy. Just write a function that takes as a parameter the fully qualified path to a file name. In tha...

There's no better or worse. Jobs are started thru the command line interface program dsjob. What starts that is up to you. Enterprise schedulers are a good thing. Some do a lot and cost a lot more. Others do less and are cheap. Control-M, Maestro, an Autosys are the high-end products, but they all s...

Disabled.

BLOBs are not supported. It's a Binary Large OBject, which means it has no relative meaning to what ETL tools are generally used to do: push around strings and numbers. BLOBs could contain anything from small text data to large binary data such as images or movies or such. Just think a moment about ...

The Output variable contains an array. You just want the first line, which would be Output<1>. Rather than execute the shell command, why not use DS BASIC function DATE() to the current system clock call, or @DATE to get the date when your process was started? Consider TIMEDATE() as well. So, try No...

Read your manuals about the command line interface program dsjob. From an OS prompt, you can type in dsjob and hit enter to see the options as well.

You have to use the TCL prompt in a telnet session. You need to change to the DS engine directory. Enter ". ./dsenv" to put the environment file into your environment. Then, either "bin/uvsh" or "bin/dssh" depending on your version. You're now in the engine shema. Type "LOGTO yourproject" case sensi...

No read or write caching, turn off interprocess and row buffering.

To repeat this query continuously can't be efficient, nor can it be indexed or optimized in any fashion. The join to ALL_OBJECTS is not a good idea, as the query parser will expand this logic when joined with other tables and you'll not get the benefits of any kind of optimized joins. Forget about e...

Never use fully qualified schemas, rely on synonyms. If a schema is needed, use job parameters. On the table names, leave off the schema and make sure you alias the name of each table without the schema name so that the DERIVATION column in the definitions is correct.

We are running Oracle 8i, so switching to OCI9 is not really an option. Not true. The 9i client is backwards compatible to 8 and forwards to 10. The 8i client is the one that works with 7, 8, and 9. You just need to use the OCI stage with the 9i client. It works just fine. In fact, I've been talkin...

gr17 wrote:Any thoughts will be appreciated.

That was a weird problem. I'm sure someone else will do the same thing sometime in the future. Just think, you've supplied the solution.

Unfortunately, I'm going to agree with IBM/Ascential. Can you possible try to use the 9i client with an OCI9 stage? The 8i client was problematic, from my own experiences with large volumes over long runtimes.