DSXchange

Actually, the path to the tnsnames.ora file is retrieved from the environment variables settings, the ORACLE_HOME points to the oracle directory, which in turn redirects to the system file location (/home/oracle/net/admin on AIX).

Six months from the date of the file on disk or the date of the file in the name? This is easy to do within a sequence job, but even easier to do with a .bat or other Windows script. Are you certain you need to do the actual computation in DataStage?

DataStage Server (which includes Job Sequences) does not allow the "$" sign as part of a variable name, which is why you are seeing the error.

A system snapshot will come quite close and be good enough on all but the most loaded of systems. With V8 and the implementation of the xmeta storage for metadata a hot backup has become tougher since pending transactions need to be taken care of inside the DB as well as in DataStage itself. The cor...

Unfortunately, no equivalent function exists in PX; there are some posts on workarounds in the forum, as you've discovered already, but none are as straightforward as the server functions they replace. W

Would splitting into multiple columns work for you, i.e. cast(SUBSTR(TextField,1,8000),VarChar(8000)) then cast(SUBSTR(TextField,8001,8000),VarChar(8000)), etc.?

Yes.

The number of logical nodes in a config file and physical CPUs in a system are independant. Simply put, the number of logical nodes just defines how many processes are used, then the OS determines how these processes are distributed across the available hardware.

A good disaster recovery plan for a medium to large installation takes a team of people (each experts in their particular area) a significant amount of time to prepare. Preparing for quick recovery after disaster is a very expensive proposition, starting with the hardware and infrastructure and endi...

It is best to avoid having to do a full table scan - how about adding an indexed column which has a different value when the external application does an update than when DataStage does it, then you could do a select based on that column's value and only get changed records back to DataStage.

The schema for the compressed data set would be: record ( t: tagged {preservePartitioning=no} ( encoded: subrec ( bufferNumber: dfloat; bufferLength: int32; bufferData: raw[32000]; ); schema: subrec ( a: int32; b: string[50]; );

If you are doing the updates then you already have that information without having to go to the actual table, right? Performance guesstimates are impossible at this time - are you running on a single-CPU 486 with 100 other users or do you have a 32 Processor SMP system all to yourself? Is the databa...

<sigh> that just means that the same information is at a different page in the manual. Have you looked for the section on the Compress stage in your developer guide?

I think sqlldr will use normal escaping methods, so try replacing all "|" in your data with "\|" to get rod of error #2