Page 1 of 1

Oracle Connector Deadlock Issue

Posted: Mon Nov 25, 2013 8:57 am
by balu536
Hi,
My Datastage job loads data to Oracle table with below properties

Write Mode: Update then Insert
Table Action : Append
Record Count : 100000
Array Size: 2000

Today the job failed (Update Query failed) with Deadlock issue
"The OCI function OCIStmtExecute returned status 1. Error code: 60, Error message: ORA-00060: deadlock detected while waiting for resource."

"The connector is not able to resume the write operation because multiple arrays of data were written to the database on one or more input links under the transaction that was active at the time of failover."

Is this because of Record Count and Array size being different. For Update operations, do we need to keep them same?

From: http://pic.dhe.ibm.com/infocenter/iisin ... 4050W.html


Please suggest.

Posted: Mon Nov 25, 2013 9:24 am
by chulett
Improper partitioning, I would think. More than one node? If so, how are your target streams partitioned? See if hash partitioning over the key fields helps.

Posted: Mon Nov 25, 2013 9:32 am
by balu536
Job is running on Two nodes.

I did hash partitioning on Primary Key on the input link of Oracle Connector Stage and updated Record Count to 2000.

Still the Job fails:(

Posted: Mon Nov 25, 2013 9:40 am
by srinivas.g
Did you check any other process is trying to update the same table?

Posted: Mon Nov 25, 2013 9:47 am
by balu536
No other user or process is using the table.

Posted: Mon Nov 25, 2013 10:04 am
by srinivas.g
Ok. Put record count is 0 and try

Posted: Mon Nov 25, 2013 10:22 am
by balu536
I was also thinking to do the same (that wll work).
I'm dealing with 1.5Million data, so shouldn't be a problem for now.

Thanks Srinivas.

Posted: Mon Nov 25, 2013 1:25 pm
by balu536
Since i have very less data, ran the job on One node and this might work for me.

Craig, Any suggestion on above?

Posted: Mon Nov 25, 2013 3:17 pm
by chulett
Running it on one node would certainly rule out partitioning issues if they continue to occur.

Posted: Tue Nov 26, 2013 9:08 am
by balu536
Thanks.
Implemented the same and deployed the code to Production.

Hope it don't abort again.. :)