DSXchange

Taking that argument to its logical conclusion, the system tables should be barred from everyone, including the DBA.

How about that for some words?!!

The DBAs can't do their job without access, neither can the Oracle Enterprise stage.

Maybe you should use "always running" rather than "off and on".

It's telling you something you ought already to know; every computer has limitations working with floating point decimal numbers. For example irrational numbers (like pi) have an infinite number of decimal places, but the computer can only store a finite number of these. But they're being pedantic a...

Or just accidentally checked the box on your way down to the Submit button!

Send the keys of the records to be deleted from the job, and use user-defined SQL of the form DELETE FROM tablename WHERE key = :1 Data Direct ODBC drivers do expire after 30 days. But you can use other ODBC drivers (with different DSNs) from Windows-based servers. These - for example the Microsoft ...

Are you using CurrentDate() in an expression in the Transformer, or in the SQL itself? The latter does not work, because there's no such Oracle function.

the joys of copy and paste!

Where, in the SOX legislation, does it say that you can't have SELECT privilege to SYS tables?!! It is IMPOSSIBLE to do damage with only SELECT privilege. It is also impossible to use the Oracle Enterprise stage without SELECT privilege to these tables, because it (the stage) needs to check the meta...

/usr/vacpp/bin/xlC_r test.c should therefore be the value of APT_COMPILER environment variable.

It IS quite well documented, in Chapter 53 (Row Generator stage) or Chapter 54 (Column Generator stage) in the Parallel Job Developer's Guide.

And you didn't follow what I said, which was "please advise". That way someone else, in future, will be able to solve this problem more quickly.

Karine wrote:I'm also want to "deconstruct" the varbinary field into its columns, ...
Am I missing something????

The Column Import stage can deconstruct a raw (VarBinary) string.

Hi Ray/Kumar, Tried Kumar's suggestion. Both are having the same values. No change. (No space, No junk characters etc ). Moreover I had the same job running successfully a week back with the same inputs. Now, with the same input, same scenario the job is failing. Rather strange. Thanks, So, what's ...

This sometimes occurs when a pathname is constructed as #param1#/#param2# and the value supplied for the first portion (a directory pathname) includes a trailing "/" character. Your parameter help text, and operator training material, ought to include an injunction against trailing "/" characters.

You can use any of the Change Capture, Compare or Difference stages to compare your new data with the existing dimension table. You don't need to build a lookup table.

[We basically need the job to Abort, if there's reject and at the same time, capture the records that got rejected to investigate] Any thoughts on this is appreciated. Thanks in advance, Vijay You never NEED the job to abort. That is laziness. And, if it aborts, how can you simultaneously expect it...