DSXchange

Issue solved! It turned out that database sequence on DB2 side must of BIGINT type - thanks for suggestion ArndW :) There is a section in IIS documentation that covers it: "Generated keys are unsigned 64-bit integers . The key source can be a state file or a database sequence. If you are using ...

No, I haven't played with DB2 sequences before, only with Oracle ones and I'm pretty sure it worked.

Regarding BIGINT - I have tested it as well, with no effect.

Thanks, this makes me believe it is Oracle Client issue, not DataStage itself.

I will play with different Oracle Clients (if this env still exists - it was a temporary installation for aims of proof-of-concept).

Regards
Buzz

It's the newest 8.1 version with FP1, "rollup_CC_ru1_solaris_8101" and "rollup_DataStage_ru1_solaris_8101" installed.

And yes - I'm planning to open the PMR as soon as I gather DSXchange users opinion (PMR's are pain in the a..)

Cheers
Buzz

ArndW, DB2 sequence is of INTEGER data type, in job I declare it by passing full sequence name prefixes with schema (schema.seq_name). No errors and warnings are observed in job log - no matter which access method I use (Transformer, SCD, SK Generator). Please keep in mind that underlying sequence i...

Hi Experts, During one of my recent DataStage assignments I observed strange behavior of Oracle Connector stage - it consumes as much of heap memory as the size of accessed data is. I use Oracle Connector for reading data from one of Oracle 10.2.0.4 tables, all the array/transaction size properties ...

Dear Experts, For last couple of hours I'm facing strange issue related to surrogate keys of DB2 type. No matter which access method I use (SCD/Transformer/Surrogate Key Generator stages) generated SK is always equal 0, jobs finish with no error. What's strange DB2 sequence that I use gets updated w...