Oracle Error 60 In Insert_fcp
Contents |
concurrent managers are not getting up.The error message in ICM log:ORACLE error 60 in insert_fcpCause: insert_fcp failed due to ORA-00060:
Ora-00060 Deadlock Detected In Oracle
deadlock detected while waiting for resourceORA-06512: at "APPS.FND_CP_FNDSM", line 134ORA-06512: at line ora-00060 deadlock detected while waiting for resource oracle 11g 1.Even after bouncing the application multiple times the issue persists.I have also executed the setup clean, cmclean and oracle deadlock resolution autoconfig but it did not work for me.Then I tried "Concurrent Managers Will Not Start ORACLE error 60 in insert_fcp (Doc ID 1256084.1)" , but again no luck.Finally,After searching
Ora-error Stack (60)
it on google, I got the solution.The root cause was APPS user password was in Grace period.SQL> select ACCOUNT_STATUS,EXPIRY_DATE,PROFILE from dba_users where username='APPS';ACCOUNT_STATUS EXPIRY_DA PROFILE-------------------------------- --------- ------------------------------EXPIRED(GRACE) DEFAULTAfter changing the APPS password the issue got resolved. Posted by Vivek Bhutani Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: APPS No comments: Post a Comment Newer Post Older
Ora 00060 Solution
Post Home Subscribe to: Post Comments (Atom) Popular Posts Upgrade EBS from 12.1.3 to 12.2.3 ORA-609 and TNS-12537 in 11g Alert.log Expdp completed with warnings opatch prereq CheckConflictAgainstOHWithDetail -ph ./ VKTM detected a time drift. Please check trace file for more details. Total Pageviews Blog Archive ▼ 2015 (2) ▼ January (2) Exception in thread "main" java.lang.InternalError... insert_fcp failed due to ORA-00060: deadlock detec... ► 2014 (33) ► December (2) ► November (1) ► October (1) ► August (1) ► June (4) ► April (11) ► March (11) ► February (2) ► 2013 (25) ► December (4) ► November (1) ► October (1) ► September (2) ► June (5) ► May (3) ► March (4) ► February (2) ► January (3) ► 2012 (37) ► December (1) ► November (1) ► October (1) ► September (5) ► August (1) ► July (1) ► June (1) ► May (2) ► April (3) ► March (2) ► February (3) ► January (16) ► 2011 (36) ► December (24) ► November (12) Simple template. Powered by Blogger.
deadlock one another waiting for resources. When this happens, these transactions are stuck (deadly embraced) and cannot continue processing. Oracle automatically detects deadlocks oracle deadlock graph and resolves them by rolling back one of the statements involved in
Ora 00060 Deadlock Detected More Info In File
the deadlock, thus releasing one set of data locked by that statement. The session that is rolled back will concurrent manager issues in oracle apps dba observe Oracle error: ORA-00060: deadlock detected while waiting for resource. Oracle will also write out a trace file with detailed information to the database's UDUMP directory. Multi-table deadlocks can be http://oracledbajourney.blogspot.com/2015/01/insertfcp-failed-due-to-ora-00060.html avoided by locking tables in same order (in all applications), thus preventing a deadlock condition. For example, session1 lock table: emp then dept; session2: emp then dept. If this is not possible, your application should check for ORA-60 errors and restart the rolled back transactions. How to fix it[edit] Look at the trace file to see the transactions and resources involved. Retry http://www.orafaq.com/wiki/ORA-00060 if necessary. Example[edit] Here is an example of how to simulate a deadlock error: Session 1 lock table EMP: SQL> UPDATE emp SET sal=sal+100; 14 rows updated. Session 2 lock table DEPT: SQL> UPDATE dept SET loc = 'Japan'; 4 rows updated. Session 1 now update DEPT. The session will hang waiting for a lock (not a deadlock yet!): SQL> UPDATE dept SET loc = 'Japan'; Session 2 now update EMP, causing the deadlock: SQL> UPDATE emp SET sal=sal+100; Oracle will detect the deadlock and roll back one of these statements: SQL> UPDATE emp SET sal=sal+100; UPDATE emp SET sal=sal+100 * ERROR at line 1: ORA-00060: deadlock detected while waiting for resource Other Causes[edit] Other more obscure deadlock situations one needs to be aware of: If you get ORA-60 errors on UPDATE and DELETE statements, where two processes wait for 'S' mode locks on each other's 'TX' enqueues, you are experiencing ITL shortage deadlocks". This cannot happen with INSERT statements, as Oracle doesn't wait on ITL (Interested Transaction List) slots for inserts, it will simply try to insert the row into
deadlock detected while waiting for resourceCause: Transactions deadlocked one another while waiting for resources.Action: Look at the trace file to see the transactions and resources involved. Retry if necessary.ORA-00060 error indicates that a dead lock occurred due to a resource contention with another session and Oracle http://oracle-error.blogspot.com/2008/10/ora-00060-deadlock-detected-while_20.html rolled back your current statement to resolve the dead lock. The other session can https://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:3932525800346405986 proceed further as usual . Your current sessions rolled backed statements needs to be resubmitted for the execution after the required resources are available.These dead locks can occur in different scenarios: They can occur while doing parallel DML operations, while updating/deleting data from same tables from different sessions , while performing transactions on bitmap index tables and deadlock detected so on but the mentioned scenarios are the most common ones.At this point I think we would like to explore more about dead locks, so here are the in depth details on dead locks:What is dead lock, when it occurs and how to fix it?Dead lock occurs when two or more users waiting for the resources locked by each other. The users are stuck and they can not proceed as they may 00060 deadlock detected end up waiting indefinitely for the resources form each other. So when this condition occurs these users are stuck (deadly embraced) and cannot continue processing.Oracle automatically detects deadlocks and resolves them by rolling back one of the transactions/statements involved in the deadlock, thus releasing one set of resources/data locked by that transaction. The session that is rolled back will observe Oracle error: ORA-00060: deadlock detected while waiting for resource. Oracle will also produce detailed information in a trace file under database's UDUMP directory.Most commonly these deadlocks are caused by the applications that involve multi table updates in the same transaction and multiple applications/transactions are acting on the same table at the same time. These multi-table deadlocks can be avoided by locking tables in same order in all applications/transactions, thus preventing a deadlock condition.In the following example I am demonstrating a dead lock scenario . In the first session ie. session1 lock table: CUSTOMER then CONTACT; and in session2: CONATCT then CUSTOMER.Here is an example of how to simulate a deadlock error:Session 1 lock table CUSTOMER:SQL> update customer set concatenate_bills_boo = 'T' where customer_ref = '10000000000000000486';1 row updated.Session 2 lock table CONTACT:SQL> update contact set language_id = 8 where customer_ref = '10000000000000000486';1 row updated.Session 1 now update CONTACT. The session will hang
January 15, 2014 - 9:12 pm UTC Category: Database � Version: 11.2 Whilst you are here, check out some content from the AskTom team: On Sharing, Splitting, and Deleting Latest Followup You Asked *** 2011-09-20 14:29:09.745 DEADLOCK DETECTED ( ORA-00060 ) [Transaction Deadlock] The following deadlock is not an ORACLE error. It is a deadlock due to user error in the design of an application or from issuing incorrect ad-hoc SQL. The following information may aid in determining the deadlock: Deadlock graph: ---------Blocker(s)-------- ---------Waiter(s)--------- Resource Name process session holds waits process session holds waits TM-0000f4bc-00000000 42 575 SX SSX 48 5 SX SSX TM-0000f4bc-00000000 48 5 SX SSX 42 575 SX SSX session 575: DID 0001-002A-000002F0 session 5: DID 0001-0030-00000831 session 5: DID 0001-0030-00000831 session 575: DID 0001-002A-000002F0 Rows waited on: Session 575: no row Session 5: obj - rowid = 0000F38C - AAAPOMACrAABodTAAA (dictionary objn - 62348, file - 171, block - 427859, slot - 0) ----- Information for the OTHER waiting sessions ----- Session 5: sid: 5 ser: 13809 audsid: 4295982 user: 63/MI520SAASPERFT1_APP flags: 0x41 pid: 48 O/S info: user: oracle, term: UNKNOWN, ospid: 14422 image: oracle@aedbperf01 client details: O/S info: user: Administrator, term: AEBL009, ospid: 1680:2480 machine: DIUS\AEBL009 program: DrteFrameworkServer.exe application name: DrteFrameworkServer.exe, hash value=3560566261 current SQL: DELETE FROM event WHERE event_id = &0 ========================= Tom, This is my first ever question on this website. I have heard a lot about u. We are getting deadlock when running our benchmark on table EVENT. Table EVENT has 9 FK constraints and no indexes on FK constraints. What should I look to get more information regarding: a) What is causing deadlocks? It is being no indexes on FK or INITTRANS. Table has default settings: PCTFREE 10 INITRANS 1 MAXTRANS 255 b) We noticed that deadlocks happen mostly during start of load and not towards the end c) will it still cause a deadlock if there are no rows in those referenced tables for the event that is being deleted? d) I ran a script to identify the missing FK indexes: =================== Changing data in table PERIOD will lock tableEVENT Create an index on table EVENT with the following columns to remove lock problem Column = PERIOD_ID (1) Changing data in table ROUTE will lock tableEVENT Create an index on table EVENT with the following columns to remove lock problem Column = ROUTE_ID (1) Changing data in table CALL_PLA