Job stage is READ-> TRANSFORM-> SPLITTER-> INSERT/UPDATEĪUTO PARTITION has been used in all the stages. If we kill and re run, few records gets inserted and it gets dead locked. I tried running the same job with a single node configration, but the job still hangs with a dead lock. Update is: UPDATE IOA_SOURCE_MOLI SET SOURCE_ORDER_NUMBER = :SOURCE_ORDER_NUMBER, SOURCE_REVISION_NUMBER = :SOURCE_REVISION_NUMBER, SERVICE_NUMBER = :SERVICE_NUMBER, LAST_UPDATE_DATE = :LAST_UPDATE_DATE, LAST_STATUS_CHANGE_DATE = :LAST_STATUS_CHANGE_DATE, COMPLETION_DATE = :COMPLETION_DATE, TELSTRA_COMMIT_DATE = :TELSTRA_COMMIT_DATE, CUST_REQUEST_DATE = :CUST_REQUEST_DATE, PRIORITY_ASSIST_IND = :PRIORITY_ASSIST_IND, RECORD_ONLY_IND = :RECORD_ONLY_IND, PROVISIONABLE_IND = :PROVISIONABLE_IND, ACTION_DESCRIPTION = :ACTION_DESCRIPTION, MISSING_TCD_MOLI_COUNT = :MISSING_TCD_MOLI_COUNT, PRODUCT_SKEY = :PRODUCT_SKEY, PRODUCT_FAMILY_SKEY = :PRODUCT_FAMILY_SKEY, MOLI_STATUS = :MOLI_STATUS, MOLI_STATUS_SKEY = :MOLI_STATUS_SKEY, O2A_STATUS_SKEY = :O2A_STATUS_SKEY, LAST_O2A_STATUS_CHANGE_DATE = :LAST_O2A_STATUS_CHANGE_DATE, O2B_STATUS_SKEY = :O2B_STATUS_SKEY, TRANSFER_TYPE = :TRANSFER_TYPE, PROMOTION_NAME = :PROMOTION_NAME, PROC_BUNDLE_NUM = :PROC_BUNDLE_NUM, INS_JOB_NUM = :INS_JOB_NUM, LAST_CHG_JOB_NUM = :LAST_CHG_JOB_NUM, LAST_CHG_ASAT_DTTM = :LAST_CHG_ASAT_DTTM, DQM_OBJ_ID = :DQM_OBJ_ID, DQ_CLEAN_FLAG = :DQ_CLEAN_FLAG, APPOINTMENT_ID = :APPOINTMENT_ID, PROD_CONSTRUCT_TYPE = :PROD_CONSTRUCT_TYPE, SUB_ACT_SKEY = :SUB_ACT_SKEY, PROMOTION_TYPE = :PROMOTION_TYPE, FULFLMNT_STATUS_CD = :FULFLMNT_STATUS_CD WHERE (SOURCE_MOLI_NUMBER = :SOURCE_MOLI_NUMBER)Įsql complaint: ORA-00060: deadlock detected while waiting for resource. Am I correct?īecause I tested this with Oracle 8.1.5 and Oracle thin driver, not sure whether this is a bug of that version or not.We have a parallel job which reads from a oracle table does some transformation and again does a INSERT/UPDATE in the same table. But after method A hits the exception and quits, method B, C, D should not hit this problem. Then all the 4 methods completed successfully.Īny idea? According to my knowledge, if method A and B runs together, they could hit ora-00060, because maybe method A updated record 1 and is waiting for record 2, while method B updated record 2 and is waiting for record 1. Repeated the test with 10000 recrods but no more than two records with same column X, for example: Then later method C hit the same error and qutes. I inserted 10000 records with same value for X but different values for Y and started 4 process at the same time, each calles one method 10000 times.Īfter a while, method A hit the ora-00060 first and quits. Method D updates column 4, 6 and last_mod_dt where column X = "xxx" and column Y = "xxx" Ĭolumn X + Y is the primary key of the table. Why there is an 'ORA-00060: deadlock detected while waiting for resource' messages at the TR (Tracker) log for Control-M Server with Oracle Applies to List of additional products and versions, either BMC products, OS’s, databases, or related products. Method C updates column 4, 5 and last_mod_dt where column X = "xxx" and column Y = "xxx" Method B updates column 1, 3 and last_mod_dt where column X = "xxx" Method A updates column 1, 2 and last_mod_dt where column X = "xxx" That class have 4 methods to update one table. I hit the above erroe when stress test my DB class.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |