DSXchange

The issue is resolved, DBA had to change INITTRANS Value from 1(Default), to 8. There was no issue from Datastage.

Thanks all.

thanks Keshav,

yes we hash partitioned on the unique key..
no success.

I am also facing the same issue, but our DBA said there is a deadlock when trying to upsert. we are working on this.. no success yet..

Thanks Hullet and Duke we changed the partition from auto -> Hash, no success!! changed UPSERT ROW COMMIT INTERVAL from 5000 to 1000, no success. Interestingly we run the job against same data(prod) in testing environment, and testing database, its works fine!!(does not work in prod) is this complet...

When we run the same job with 1 node and 2 node config files, runs successfully!!! but some tables are huge, we can't afford to run with 1 or 2 node, but what causing oracle deadlock? using 4 nodes.?? with auto partition.


Thanks in advance..

thanks hullet,

yes, even code run successfully in systest.

We have huge tables, 50mn records on one table , so we did not test with one node config file yet,

Hello,

Couple of our jobs aborted in prod with oracle deadlock, when trying to upsert. also got this message in log: oci_invalid_handle
The jobs are running fine in Dev. We are using 4 node config file in production. partition is Auto.

Please give your views on this.

Thanks in advance...
reddy.

thank you for the reply, can you please explain the logic little more on the above

Is there any way to assign rank?

Lets say there are 4 students with input col as Name and Marks


A 59

B 46

C 46

D 52


Can any one please explain the ranking process for above data. Output should be name and rank

A 1

B 2

C 2

D 4


Thank you.

Thanks Hullet,

it worked....

sorry abou that...

Thanks Hiral, That is a notnull field(not a key field), and space is coming into that field from source DB. we are extracting the table from Oracle ---> Dataset. and the loading to target table. in btw the space is trimmed in datastage and the field become null, and as the field is not nullable, get...

Any solutions please???

Hello,
In one of our jobs the source data spaces, and datastage is trimming those spaces and making it null and eventually the records are rejected, is there a way to handle that.? i am loading form dataset to oraclae stage.

thanks in advance.

hullet,

index XXXXXX was made unusable due to SKIP_INDEX_MAINTANANCE optio requested.
does not say anything about else about indexes,

any other issue.??