ORA-000060 (deadlock) and no alert/trace info

oracle 9.2.0.5 running on SunOs 5.9
I am getting very seldom (2-5 per month) these errors.
1) the alert file shows this:
ORA-000060: Deadlock detected. More info in file xxx.trc
2) after running "tkprof" on the trace file I see only this:
1 session in tracefile.
0 user SQL statements in trace file.
0 internal SQL statements in trace file.
0 SQL statements in trace file.
0 unique SQL statements in trace file.
I tried most of "tkprof" options but still there is no info on what caused the deadlock. any ideas ?

if you open the trace file in an editor, what do you
see?this works! the TRC file actually shows me the 2 sessions that contended for the resource. I never realized you could open the TRC file directly, I was led to believe you needed to "tkprof" to be able to browse it.
me bad, and lots of thanks to you!

Similar Messages

ORA-000060: Deadlock detected

i m using oracle 9.2.0.6.0 on windows server 2003. I am getting the following error
ORA-000060: Deadlock detected.
hope u people can help me out...

Hi,
Did you realize that you have posted teh same topic 3 times ??This is not a good thing to do in this forum.
Deadlock detected is mainly an issue that is caused by poor management of transactions within the application.
ORA-00060: deadlock detected while waiting for resource
Cause: Transactions deadlocked one another while waiting for resources.
Action: Look at the trace file to see the transactions and resources involved. Retry if necessary.
You must have got an associated file with it.Check back that file to find the offending processes which caused this error.What is the complete error statement that you have got with this?
Aman....

ORA-000060 (deadlock) while insert

Dear All,
I'm currently facing a problem:
- we are getting ORA-000060
- on trace file generated by the error, shows an INSERT operation as current operation
- The table related to the above INSERT operation has below properties:
- NO BITMAP INDEX
- The table is RANGE PARTITIONED
- A LOCALY PARTITIONED UNIQUE INDEX
- DB version is Oracle 9.2.0.6 on HPUX
My question is why an insert operation will cause deadlock (bitmap index) ?
Or it is resulted from other operation, if this is the case then why trace file show the insert operation as current operation ?
Please help.
BR
Obaid

Ok, according to the deadlock graph, these are TX enqueues, so, it's definitely NOT an unindexed foreign key problem. Locking due to unindexed FKs cause TM enqueue waits, not TX enqueue.
Since it's an S mode wait on TX and the statement involved is an insert, the most likely cause is overlapping unique values on the index.
Suppose you have:
create table testit(a number);
create unique index uniq_ind on testit(a);
Now, if you have two sessions inserting into testit:
session 1:
insert into testit values(1);
session 2:
insert into testit values(2);
session 1:
--the following insert statement will begin to hang, waiting for session 2 to commit or rollback
insert into testit values(2);
session 2:
--the following session will hang for three seconds, and then Oracle will detect a deadlock and session 1 will catch an ORA-00060.
insert into testit values(1);
So, if you have two concurrent sessions that overlap on the values of the uncommitted unique values, you'll see S mode TX enqueue waits.
Hope that helps,
-Mark

ORA-000060: Deadlock detected. More info in file ...

Hi,
Could anybody tell me if in such a situation may i do something particulary is the database have seen a deadlock ... ?
Thanks, Paul

Hi,
In addition, you can check "Oracle deadlocks tips" at:
http://www.dba-oracle.com/t_deadlock.htm
another one:
http://www.oracle-base.com/articles/misc/Deadlocks.php
Good luck!
Marcello M.
Message was edited by:
Marcello M.

Ora 000060 error

Hi,
i'm running a query and having after a lot of time this error in the alert:
ORA-000060: Deadlock detected. More info in file /OraBin/admin/dev/bdump/s002_5490_dev.trc.
I checked the trace file and it says:
DEADLOCK DETECTED
Current SQL statement for this session:
UPDATE reason SET CREATIONDATE='',CREATIONUSER='',CHANGEDATE='',CHANGEUSER='',IDREASONLIST=1,IDREASONSTATUSLIST=1,IDPRODUCTTYPELIST=0,PRODUCTNUMBER='0',BADITEM=0,CIF2='',NOTE='' WHERE IDCustfile=10001
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.
You see the query? It's very simple, i don't know why it's failing.. Of course i did something wrong but where?
Thanks
Tarek

About the error.. of course it is an application error.
So, the transaction does something abnormal and then it locked a table. When the application that did this is killed on oracle there is still the lock. When did this lock be released? Does oracle has a timeout? does it recognize that the application that ran the transaction is dead so it can be killed and resources released?

Writing Trace Info to and Opening an Excel File on command

I am currently using a Read Traces (numeric) vi to collect values from Tags and output them to a XY Graph. Alongside the graph on my front panel, I would like a boolean control to command (when true) LV to write the data to a spreadsheet and open that spreadsheet so it appears on screen, ready for the user to view and then save the excel file where he/she would like.
Is this possible? I am a little unsure what File I/O functions I need in order to achieve this? I have tried using the "Write Traces to Spreadsheet vi" available in the DSC module, but haven’t had much success. I have attached my code to show you how far I have got.
Any help with this problem will be very much appreciated.
Thanks,
Stuart Wilson
Attachments:
Writing Trace Info to Excel File.vi ‏77 KB

Hi Stuart,
I have written an example piece of code for you which has the basic functionaliy that you want.
The example plots random data to a chart. When the boolean is pressed this data is written to a spread sheet file and Excel is opened to display this data.
As it is a generic solution you need to replace certain items when you incorporate the structure into your code: Instead of writting the history data of a chart you can use the "write traces to spreadsheet.vi" to write the data. The automation of excel can then be used in the same way as in the example.
There is also an example available in the "LabVIEW Example finder" called "Write Table to XL.vi". This example takes the data from a table and cell by cell inserts it into an excel speadsheet. Which the operator can then save from within excel. However, this method is not the most efficient way to get data into Excel.
I hope this is helpful.
Emma R
NIUK & Ireland
Attachments:
SR_300720_Example.vi ‏68 KB

ORA-00060 - Deadlock detected Error

Hello Gurus,
In Our BW Production Server we are facing follwoing error sice few days
BR0976W Database message alert - level: WARNING, line: 1572623, time: 2008-01-23 01.49.02, message:
ORA-00060: Deadlock detected. More info in file /oracle/PBW/saptrace/usertrace/pbw_ora_590014.trc.
BR0976W Database message alert - level: WARNING, line: 1572637, time: 2008-01-23 01.56.47, message:
ORA-00060: Deadlock detected. More info in file /oracle/PBW/saptrace/usertrace/pbw_ora_598066.trc.
Can anybody tell me the how to get rid of this error
Vital Information - Server
O/S - AIX
SAP Version - 700
Oracle - 10.2.0.2.0
ABAP Support Pack - SAPKA70010
Basis Support Pack - SAPKB70010
Patch - 95
Thanks & Regards
Shishir

The trace file will be written to the directory indicated by the USER_DUMP_DEST init.ora parameter.
The trace file will contain a deadlock graph and additional information similar to that shown below. This is the trace output from the above example which signaled an ORA-60 to Ses#2:
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
   TX-00020012-0000025e     12      11     X             11      10           X
   TX-00050013-0000003b     11      10     X             12      11           X
   session 11: DID 0001-000C-00000001      session 10: DID 0001-000B-00000001
   session 10: DID 0001-000B-00000001      session 11: DID 0001-000C-00000001
   Rows waited on:
   Session 10: obj - rowid = 00000BF6 - AAAAv2AAEAAAAqKAAB
   Session 11: obj - rowid = 00000BF6 - AAAAv2AAEAAAAqKAAA

ORA-00060: deadlock detected while waiting for resource with Tbs Read-only

Hi all,
We're using Oracle 10.2.0.1 and 9.2.0.4.
I'm testing the performing of a procedure that inserts, like this:
CREATE OR REPLACE PROCEDURE P$TAD_TEST
IS
TYPE T_T1_C1 IS TABLE OF T1.C1%TYPE INDEX BY PLS_INTEGER;
TYPE T_T1_DT IS TABLE OF T1.DT%TYPE INDEX BY PLS_INTEGER;
P_C1 T_T1_C1;
P_DT T_T1_DT;
P_RESULT NUMBER;
BEGIN
FOR j IN 1..4032 LOOP
P_C1(j) := j;
P_DT(j) := SYSDATE + (j/24/60);
END LOOP;
FORALL i IN P_C1.FIRST..P_C1.LAST SAVE EXCEPTIONS
INSERT INTO T1 VALUES (P_C1(i), P_DT(i));
EXCEPTION
WHEN OTHERS THEN
P_RESULT := SQLCODE;
END;
The table T1 is partitioned across 10 tablespaces. The test consist to take
these tablespace read-only and perform the procedure, and analyze the results,
like erros.
but when I perform the procedure, The alert.log indicates the error
ORA-00060: deadlock detected while waiting for resource.
Why this occurs only the tablespaces are read-only?
thank you!!!!

Hi,
yesterday we got this error again(in fact twice) and we were able to get the trace file. It says this is NOT oracle error. i was wrong in suspecting Oracle. This is the trace file details. i dont know how to debug this. Any help appreciated.
*** 2010-06-15 16:24:29.243
*** ACTION NAME:() 2010-06-15 16:24:29.231
*** MODULE NAME:(JDBC Thin Client) 2010-06-15 16:24:29.231
*** SERVICE NAME: 2010-06-15 16:24:29.231
*** SESSION ID:(482.4266) 2010-06-15 16:24:29.231
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
TX-00300021-0000b52d 209 482 X 247 474 S
TX-002a0009-00011b24 247 474 X 209 482 S
session 482: DID 0001-00D1-0000000A session 474: DID 0001-00F7-00000008
session 474: DID 0001-00F7-00000008 session 482: DID 0001-00D1-0000000A
Rows waited on:
Session 474: obj - rowid = 0000CED4 - AAAM7UAAxAAAVgSAAA
(dictionary objn - 52948, file - 49, block - 88082, slot - 0)
Session 482: obj - rowid = 0000D8BF - AAANi/AAuAAB+z/AAA
(dictionary objn - 55487, file - 46, block - 519423, slot - 0)
Information on the OTHER waiting sessions:
Session 474:
pid=247 serial=31796 audsid=25502259 user: 62/USER
O/S info: ....
program: JDBC Thin Client
application name: JDBC Thin Client, hash value=2546894660
Current SQL Statement:
INSERT QUERY1
End of information on OTHER waiting sessions.
Current SQL statement for this session:
INSERT QUERY2
Thanks,
AK

ORA-00060: Deadlock detected

I getting error as "ORA-00060: Deadlock detected. More info in file /d01/oracle/VIS/db/tech_st/10.2.0/.................". Following are my observations on the occurence of this error.
The deadlock is encountered first time when trying to login to applications. I have R12 vision instance on linux.
Following the content of the alert_VIS.log file
Mon Jun 15 04:41:41 2009
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as /d01/oracle/VIS/db/tech_st/10.2.0/dbs/arch
Autotune of undo retention is turned on.
IMODE=BR
ILAT =44
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.3.0.
System parameters with non-default values:
tracefiles_public = TRUE
processes = 200
sessions = 400
timed_statistics = TRUE
shared_pool_size = 419430400
shared_pool_reserved_size= 41943040
nls_language = american
nls_territory = america
nls_sort = binary
nls_date_format = DD-MON-RR
nls_numeric_characters = .,
nls_comp = binary
nls_length_semantics = BYTE
sga_target = 1073741824
control_files = /d01/oracle/VIS/db/apps_st/data/cntrl01.dbf, /d01/oracle/VIS/db/apps_st/data/cntrl02.dbf, /d01/oracle/VIS/db/apps_st/data/cntrl03.dbf
db_block_checksum = TRUE
db_block_size = 8192
compatible = 10.2.0
log_buffer = 14251008
log_checkpoint_interval = 100000
log_checkpoint_timeout = 1200
db_files = 512
log_checkpoints_to_alert = TRUE
dml_locks = 10000
undo_management = AUTO
undo_tablespace = APPS_UNDOTS1
db_block_checking = FALSE
O7_DICTIONARY_ACCESSIBILITY= FALSE
session_cached_cursors = 500
utl_file_dir = /usr/tmp, /usr/tmp, /d01/oracle/VIS/db/tech_st/10.2.0/appsutil/outbound/VIS_oracleebsr12, /usr/tmp
plsql_native_library_dir = /d01/oracle/VIS/db/tech_st/10.2.0/plsql/nativelib
plsql_native_library_subdir_count= 149
plsql_code_type = native
plsql_optimize_level = 2
job_queue_processes = 2
systemtrig_enabled = TRUE
cursor_sharing = EXACT
parallel_min_servers = 0
parallel_max_servers = 8
background_dump_dest = /d01/oracle/VIS/db/tech_st/10.2.0/admin/VIS_oracleebsr12/bdump
user_dump_dest = /d01/oracle/VIS/db/tech_st/10.2.0/admin/VIS_oracleebsr12/udump
max_dump_file_size = 20480
core_dump_dest = /d01/oracle/VIS/db/tech_st/10.2.0/admin/VIS_oracleebsr12/cdump
db_name = VIS
open_cursors = 600
ifile = /d01/oracle/VIS/db/tech_st/10.2.0/dbs/VIS_oracleebsr12_ifile.ora
sortelimination_cost_ratio= 5
btree_bitmap_plans = FALSE
fastfull_scan_enabled = FALSE
sqlexecprogression_cost= 2147483647
likewith_bind_as_equality= TRUE
pga_aggregate_target = 1073741824
workarea_size_policy = AUTO
optimizer_secure_view_merging= FALSE
aq_tm_processes = 1
olap_page_pool_size = 4194304
Mon Jun 15 04:42:05 2009
WARNING:Oracle instance running on a system with low open file descriptor
limit. Tune your system to increase this limit to avoid
severe performance degradation.
PSP0 started with pid=3, OS id=6824
PMON started with pid=2, OS id=6822
MMAN started with pid=4, OS id=6826
DBW0 started with pid=5, OS id=6828
CKPT started with pid=7, OS id=6832
SMON started with pid=8, OS id=6834
RECO started with pid=9, OS id=6836
CJQ0 started with pid=10, OS id=6838
LGWR started with pid=6, OS id=6830
MMON started with pid=11, OS id=6840
MMNL started with pid=12, OS id=6842
Mon Jun 15 04:42:19 2009
ALTER DATABASE MOUNT
Mon Jun 15 04:42:25 2009
Setting recovery target incarnation to 2
Mon Jun 15 04:42:27 2009
Successful mount of redo thread 1, with mount id 243370348
Mon Jun 15 04:42:27 2009
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Mon Jun 15 04:42:28 2009
ALTER DATABASE OPEN
Mon Jun 15 04:42:48 2009
Thread 1 opened at log sequence 16
Current log# 3 seq# 16 mem# 0: /d01/oracle/VIS/db/apps_st/data/log3.dbf
Successful open of redo thread 1
Mon Jun 15 04:42:48 2009
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Mon Jun 15 04:42:48 2009
SMON: enabling cache recovery
Mon Jun 15 04:42:48 2009
Incremental checkpoint up to RBA [0x10.a779.0], current log tail at RBA [0x10.a779.0]
Mon Jun 15 04:43:01 2009
Successfully onlined Undo Tablespace 18.
Mon Jun 15 04:43:01 2009
SMON: enabling tx recovery
Mon Jun 15 04:43:04 2009
Database Characterset is UTF8
Mon Jun 15 04:43:18 2009
replication_dependency_tracking turned off (no async multimaster replication found)
Mon Jun 15 04:43:44 2009
Starting background process QMNC
QMNC started with pid=14, OS id=6884
Mon Jun 15 04:46:48 2009
Completed: ALTER DATABASE OPEN
Mon Jun 15 05:03:23 2009
Incremental checkpoint up to RBA [0x10.b1bd.0], current log tail at RBA [0x10.b1f3.0]
Mon Jun 15 05:23:33 2009
Incremental checkpoint up to RBA [0x10.b5b3.0], current log tail at RBA [0x10.b5c2.0]
Mon Jun 15 05:45:12 2009
Incremental checkpoint up to RBA [0x10.b7b0.0], current log tail at RBA [0x10.fbce.0]
This is upto the point where all DB and application services has been started.
Once trying to login to applications following content got appended to the log file
Mon Jun 15 05:53:39 2009
ORA-00060: Deadlock detected. More info in file /d01/oracle/VIS/db/tech_st/10.2.0/admin/VIS_oracleebsr12/udump/vis_ora_8149.trc.
Mon Jun 15 05:53:51 2009
ORA-00060: Deadlock detected. More info in file /d01/oracle/VIS/db/tech_st/10.2.0/admin/VIS_oracleebsr12/udump/vis_ora_8149.trc.
Mon Jun 15 05:54:02 2009
ORA-00060: Deadlock detected. More info in file /d01/oracle/VIS/db/tech_st/10.2.0/admin/VIS_oracleebsr12/udump/vis_ora_8149.trc.
Mon Jun 15 05:54:12 2009
ORA-00060: Deadlock detected. More info in file /d01/oracle/VIS/db/tech_st/10.2.0/admin/VIS_oracleebsr12/udump/vis_ora_8149.trc.
Mon Jun 15 05:54:22 2009
ORA-00060: Deadlock detected. More info in file /d01/oracle/VIS/db/tech_st/10.2.0/admin/VIS_oracleebsr12/udump/vis_ora_8149.trc.
Mon Jun 15 05:54:28 2009
ORA-00060: Deadlock detected. More info in file /d01/oracle/VIS/db/tech_st/10.2.0/admin/VIS_oracleebsr12/udump/vis_ora_8149.trc.
Mon Jun 15 05:54:35 2009
ORA-00060: Deadlock detected. More info in file /d01/oracle/VIS/db/tech_st/10.2.0/admin/VIS_oracleebsr12/udump/vis_ora_8149.trc.
Mon Jun 15 05:54:42 2009
ORA-00060: Deadlock detected. More info in file /d01/oracle/VIS/db/tech_st/10.2.0/admin/VIS_oracleebsr12/udump/vis_ora_8149.trc.
Mon Jun 15 05:59:06 2009
Process J000 died, see its trace file
Mon Jun 15 05:59:11 2009
kkjcre1p: unable to spawn jobq slave process
Mon Jun 15 05:59:11 2009
Errors in file /d01/oracle/VIS/db/tech_st/10.2.0/admin/VIS_oracleebsr12/bdump/vis_cjq0_6838.trc:
Mon Jun 15 05:59:23 2009
Process J000 died, see its trace file
Mon Jun 15 05:59:24 2009
kkjcre1p: unable to spawn jobq slave process
Mon Jun 15 05:59:24 2009
Errors in file /d01/oracle/VIS/db/tech_st/10.2.0/admin/VIS_oracleebsr12/bdump/vis_cjq0_6838.trc:
Mon Jun 15 05:59:50 2009
Process J000 died, see its trace file
Mon Jun 15 05:59:50 2009
kkjcre1p: unable to spawn jobq slave process
Mon Jun 15 05:59:50 2009
Errors in file /d01/oracle/VIS/db/tech_st/10.2.0/admin/VIS_oracleebsr12/bdump/vis_cjq0_6838.trc:
I did the TKPROF on .trc files but the tkprof file does not show any details as such except similar to :- (don't know if I am missing anything while issuing TKPROF as $ tkprof filename.trc
filename.txt explain=apps/apps)
TKPROF: Release 10.2.0.3.0 - Production on Mon Jun 15 06:07:14 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Trace file: /d01/oracle/VIS/db/tech_st/10.2.0/admin/VIS_oracleebsr12/bdump/vis_cjq0_6838.trc
Sort options: default
count = number of times OCI procedure was executed
cpu = cpu time in seconds executing
elapsed = elapsed time in seconds executing
disk = number of physical reads of buffers from disk
query = number of buffers gotten for consistent read
current = number of buffers gotten in current mode (usually for update)
rows = number of rows processed by the fetch or execute call
0 statements EXPLAINed in this session.
Trace file: /d01/oracle/VIS/db/tech_st/10.2.0/admin/VIS_oracleebsr12/bdump/vis_cjq0_6838.trc
Trace file compatibility: 10.01.00
Sort options: default
1 session in tracefile.
0 user SQL statements in trace file.
0 internal SQL statements in trace file.
0 SQL statements in trace file.
0 unique SQL statements in trace file.
22 lines in trace file.
0 elapsed seconds in trace file.
Yesterday, I did login to applications after multiple attempts and tried submitting a concurrent request of a standard report (after resolving the data block corrupt issue) and got the same ORA-00060 Error.
I have a fresh VISION R12 (12.0.4) installed without any customizations. My installation looks to be quite unstable, takes 2-3 attempts for successful login to apps.
Can you please give any clues on this and how to overcome the problem?
Thanks,
Amit

I have run cmclean.sql as per :- Re: R12 Vision install - Unable to submit concurrent request
This is the only change made. No new patches etc. Before running cmclean.sql I believe the instance was working fine.
Now everytime I start the application services, its causing ORA=00060: Deadlock error. There are no issues with just DB services up and running.
And after apps services up, when trying to Login to apps it just hangs, get error as follows:
Tue Jun 23 02:04:55 2009
Process J001 died, see its trace file
Tue Jun 23 02:04:55 2009
kkjcre1p: unable to spawn jobq slave process
Tue Jun 23 02:04:55 2009
Errors in file /d01/oracle/VIS/db/tech_st/10.2.0/admin/VIS_oracleebsr12/bdump/vis_cjq0_6747.trc:
Tue Jun 23 02:05:04 2009
Process q002 died, see its trace file
Tue Jun 23 02:05:04 2009
ksvcreate: Process(q002) creation failed
Tue Jun 23 02:05:55 2009
Process J000 died, see its trace file
Tue Jun 23 02:05:55 2009
kkjcre1p: unable to spawn jobq slave process
Tue Jun 23 02:05:55 2009
Errors in file /d01/oracle/VIS/db/tech_st/10.2.0/admin/VIS_oracleebsr12/bdump/vis_cjq0_6747.trc:
Tue Jun 23 02:06:11 2009
Process J000 died, see its trace file
Tue Jun 23 02:06:11 2009
kkjcre1p: unable to spawn jobq slave process
Tue Jun 23 02:06:11 2009
Errors in file /d01/oracle/VIS/db/tech_st/10.2.0/admin/VIS_oracleebsr12/bdump/vis_cjq0_6747.trc:
Tue Jun 23 02:08:51 2009
Process J000 died, see its trace file
Tue Jun 23 02:08:52 2009
kkjcre1p: unable to spawn jobq slave process
Tue Jun 23 02:08:52 2009
Errors in file /d01/oracle/VIS/db/tech_st/10.2.0/admin/VIS_oracleebsr12/bdump/vis_cjq0_6747.trc:
The OS also hangs (Linux) and I have to exit abnormally everytime which is frustrating.
I am not sure the reason for the same. I have gone through the metalink notes pointed which says to install the health check engine.
Do you have any clues based on above information as to what might be causing this problem.
I have 4 GB RAM installed on my Windows and 2 GB has been allocated to Linux on VMware.
Please let me know if I need to upgrade the memory.
Any pointers would be really helpful.
Thanks,
Amit

Caused by: java.sql.SQLException: ORA-00060: deadlock detected while waitin

Hi,
I'm getting following exception:
Caused by: net.sf.hibernate.exception.GenericJDBCException: could not update: [com.sample.database.hibernate.mappings.reference.impl.TaskImpl#156979998]
     at net.sf.hibernate.exception.ErrorCodeConverter.handledNonSpecificException(ErrorCodeConverter.java:90)
     at net.sf.hibernate.exception.ErrorCodeConverter.convert(ErrorCodeConverter.java:79)
     at net.sf.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:30)
     at net.sf.hibernate.persister.AbstractEntityPersister.convert(AbstractEntityPersister.java:1332)
     at net.sf.hibernate.persister.EntityPersister.update(EntityPersister.java:683)
     at net.sf.hibernate.persister.EntityPersister.update(EntityPersister.java:623)
     at net.sf.hibernate.impl.ScheduledUpdate.execute(ScheduledUpdate.java:52)
     at net.sf.hibernate.impl.SessionImpl.executeAll(SessionImpl.java:2438)
     at net.sf.hibernate.impl.SessionImpl.execute(SessionImpl.java:2392)
     at net.sf.hibernate.impl.SessionImpl.flush(SessionImpl.java:2260)
     at net.sf.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:61)
     at com.sample.database.hibernate.util.HibernateUtil.doSessionWork(HibernateUtil.java:83)
     ... 8 more
Caused by: java.sql.SQLException: ORA-00060: deadlock detected while waiting for resource
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:158)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:305)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:272)
     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:623)
     at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:181)
     at oracle.jdbc.driver.T4CPreparedStatement.execute_for_rows(T4CPreparedStatement.java:685)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1138)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3018)
     at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3090)
     at com.mchange.v2.sql.filter.FilterPreparedStatement.executeUpdate(FilterPreparedStatement.java:71)
     at net.sf.hibernate.persister.EntityPersister.update(EntityPersister.java:666)
     ... 15 more
what could be the reason??
thanks.

The error is coming from an application. Please check the alert log file of the database and further there will be a trace file mentioned in the alert log file in which you will have information of the object which is causing deadlock.
Regards

Excluding ORA-00060 errors from Generic Alert Log Error in OEM

Hi,
I want to remove the alerts for ORA-00060 errors from OEM Alerts. In "Generic Alert Log Error" the current expression for Warning is ORA-0*(600?|7445|4[0-9][0-9][0-9])[^0-9]. How should I change this expression so that it will not send alerts for ORA-00060. I am not much aware of perl :-). Please help me with the expression.
Target Type=dbname
Host=host
Metric=Generic Alert Log Error
Metric Value=ORA-00060: Deadlock detected. More info in
Time/Line Number=Mon Nov 2 10:02:54 2009/134883
Timestamp=Nov 2, 2009 10:17:14 AM EST
Severity=Warning
Message=ORA-error stack (00060) logged in /eb_rdo0_p/oraadmin/pnoltp/bdump/alert_.log.
Notification Rule Name=Database Alert
Notification Rule Owner=SYSMAN
Notification Count=1
Thanks,
Varma

this is default monitored objects.
To stop monitoring for this object, clear the Critical and Warning threshold values and click Continue.

Database error"ORA-00060: deadlock detected while waiting for resource"

Hi All,
I got dump as
Database error text........: "ORA-00060: deadlock detected while waiting for
resource"
Internal call code.........: "[RSQL/RDUP/NRIV ]"
Please check the entries in the system log (Transaction SM21).
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
in
procedure "READ_NRIV" "(FORM)", nor was it propagated by a RAISING clause.
Can u ppl tell me how to get correct this?
Edited by: Bala Chandar on Jul 20, 2009 11:01 AM

Hi Bala,
Same type of dump we got when we trigger the DTP which in process chain to load data from DSO to Info cube. And the load had processed with 225 data package and at 164th data package we got this error and except 164th data package all data package processed successfully
And the request was red. So we had done processed manually by clicking the icon. So all its been green and successfully loaded.
So when you do process manual the particular data package which got failed will be process successfully

When does Oracle throw the ORA-00060 , Deadlock error

Hi,
To test the "ORA-00060: Deadlock detected" we tried the below steps on scott schema.
First session -
update emp set sal=9999 where name='JACK';
Second session -
update emp set sal=5555 where name='JACK';
We used the below query to find out which SID is locking the other;
select l1.sid, ' IS BLOCKING ', l2.sid from v$lock l1, v$lock l2 where l1.block =1 and l2.request > 0 and l1.id1=l2.id1 and l1.id2=l2.id2;
-- We got the SID's
But in the alert log we are still not able to see the ORA-00060 error.
Why is this ? In which scenario do we see the ORA-00060 error in alert log ?
Please guide.
Thanks.

What you describe is just a blocking lock, not a deadlock.
The first session can simply do commit and the second session can then continue.
In a deadlock situation, nobody can commit if the system does not resolve the problem by rolling back one of the transactions:
session1: lock row 1
session 2: lock row 2
session 1: try lock row 2 <- wait on session 2
session 2: try lock row 1 <- wait on session 1
both wait, enter ORA-600
Kind regards
Uwe Hesse
http://uhesse.wordpress.com

Ora-07445 reported in the alert log file

Hi all,
We are using the following platform:-
OS: Solaris Operating System (SPARC 32-bit)
Oracle Server - Enterprise Edition / Product Version: 9.2.0.5.0
We encountered the following problem:-
There is Ora-07445 reported in the alert log file.
"ORA-07445: exception encountered: core dump [kgghash()+308] [SIGSEGV] [Address not mapped to object] [0x3222
000] [] []reported in the database."
These errors are signaled in more than 3 independent, unexplained, occurrences every day.
When this error occurred while User was accessing the application system, by right the case will be shown on the system, but they were no case found.
alert log are as below:-
Fri Jul 27 09:12:30 2007
Errors in file /disc3/oracle9205/RFDB/udump/rfdb_ora_27371.trc:
ORA-07445: exception encountered: core dump [kgghash()+340] [SIGSEGV] [Address not mapped to object] [0x3184000] [] []
Fri Jul 27 09:22:10 2007
Thread 1 advanced to log sequence 10730
Current log# 2 seq# 10730 mem# 0: /disc3/oracle9205/RFDB/RDO/logRFDB2a.rdo
Current log# 2 seq# 10730 mem# 1: /disc3/oracle9205/RFDB/RDO/logRFDB2b.rdo
Fri Jul 27 09:29:26 2007
Errors in file /disc3/oracle9205/RFDB/udump/rfdb_ora_27372.trc:
ORA-07445: exception encountered: core dump [kgghash()+296] [SIGSEGV] [Address not mapped to object] [0x3182000] [] []
The applications have encountered ora-3113 after a short period of time followed by ora-3114.
application log:-
RF0120-1 2007-Jul-27 09:46:57] Load m[RF0120-1 2007-Jul-27 09:29:30] SQLCODE: -3113
[RF0120-1 2007-Jul-27 09:29:30] Error Code -4105 returning from get score pan no.
[RF0120-1 2007-Jul-27 09:29:30] Message type :120
[RF0120-1 2007-Jul-27 09:29:30] Primary Account Number(PAN) DE0
02 :5440640155262702
[RF0120-1 2007-Jul-27 09:29:30] Processing code DE003 :003000
[RF0120-1 2007-Jul-27 09:29:30] Transaction amount DE004 :000000000001
[RF0120-1 2007-Jul-27 09:29:30] Settlement amount DE005 :000000000000
[RF0120-1 2007-Jul-27 09:29:30] Transmission Date and time
DE007 :0727092717
[RF0120-1 2007-Jul-27 09:29:30] Settlement conversion rate DE009 :60263158
[RF0120-1 2007-Jul-27 09:29:30] System trace audit no. DE011 :754710
[RF0120-1 2007-Jul-27 09:29:30] Local transaction time DE012 :092717
[RF0120-1 2007-Jul-27 09:29:30] Local transaction date DE013 :0727
[RF0120-1 2007-Jul-27 09:29:30] Expiration date D
E014 :0712
[RF0120-1 2007-Jul-27 09:29:30] Settlement date DE015 :0727
[RF0120-1 2007-Jul-27 09:29:30] Merchant type DE018 :5311
[RF0120-1 2007-Jul-27 09:29:30] Point-of-service(POS) entry code DE022 :051
[RF0120-1 2007-Jul-27 09:29:30] Acquiring inst. ID code DE032 :001912
[RF0120-1 2007-Jul-27 09:29:30] Forwarding Inst. ID code DE033 :001912
[RF0120-1 2007-Jul-27 09:29:30] Retrieval ref. no.
DE037 :754710356390
[RF0120-1 2007-Jul-27 09:29:30] Autholization ID response DE038 :356390
[RF0120-1 2007-Jul-27 09:29:30] Response code DE039 :00
[RF0120-1 2007-Jul-27 09:29:30] Card acceptor terminal ID DE041 :19306002
[RF0120-1 2007-Jul-27 09:29:30] Card acceptor ID code DE042 :000001106
020132
[RF0120-1 2007-Jul-27 09:29:30] Card acceptor Name/Location
What could have caused the above mentioned errors i.e Ora-07445 ; ora-3113 / ora-3114? How to resolve the problem.
Please help .
Thanks.

i am also facing the same some time in ora 9.2.0.6 on Sun OS 9 SPARC 64-bits
Errors in file /oracle/oracle9i/admin/FINPROD/udump/finprod_ora_6076.trc:
ORA-07445: exception encountered: core dump [0000000100FDE088] [SIGSEGV] [Address not mapped to object] [0x00000013A] [] []
Thu Aug 30 08:52:39 2007
Errors in file /oracle/oracle9i/admin/FINPROD/udump/finprod_ora_6078.trc:
ORA-07445: exception encountered: core dump [0000000100FDE088] [SIGSEGV] [Address not mapped to object] [0x00000013A] [] []
Thu Aug 30 09:41:49 2007

ORA-32004: obsolete and/or deprecated parameter(s) specifiedORACLE instance

Hi friends,
i am trying to install BIW 3.0b (win-2000, oracle 9.2.0.1.0 (patch 9.1.0.4.1)& j2sdk 1_4_1)
while installing database instance i am getting this problem.
INFO 2007-09-26 15:57:09
Copying file C:/SAPinst ORACLE KERNEL/keydb.xml to: C:/SAPinst ORACLE KERNEL/keydb.1.xml.
INFO 2007-09-26 15:57:09
Creating file C:\SAPinst ORACLE KERNEL\keydb.1.xml.
INFO 2007-09-26 15:58:14
Processing of host operation t_HostInfo_SHARED succeeded.
INFO 2007-09-26 15:58:35
The 'saploc' share exists at directory 'E:\usr\sap'. Choosing drive E: as SAP System drive.
INFO 2007-09-26 16:00:26
Copying file C:/dump/export1/DB/ORA/DBSIZE.XML to: DBSIZE.XML.
INFO 2007-09-26 16:00:26
Creating file C:\SAPinst ORACLE KERNEL\DBSIZE.XML.
INFO 2007-09-26 16:00:26
Copying file system node C:\dump\export1/DB/ORA/DBSIZE.XML with type NODE to DBSIZE.XML succeeded.
INFO 2007-09-26 16:00:26
Processing of all file system node operations of table tORA_filecopy succeeded.
INFO 2007-09-26 16:00:26
Copying file C:/SAPinst ORACLE KERNEL/DBSIZE.XML to: C:/SAPinst ORACLE KERNEL/DBSIZE.1.XML.
INFO 2007-09-26 16:00:26
Creating file C:\SAPinst ORACLE KERNEL\DBSIZE.1.XML.
INFO 2007-09-26 16:00:26
Copying file C:/dump/export1/DB/DDLORA.TPL to: DDLORA.TPL.
INFO 2007-09-26 16:00:26
Creating file C:\SAPinst ORACLE KERNEL\DDLORA.TPL.
INFO 2007-09-26 16:00:26
Copying file system node C:\dump\export1/DB/DDLORA.TPL with type NODE to DDLORA.TPL succeeded.
INFO 2007-09-26 16:00:26
Processing of all file system node operations of table tORA_filecopy succeeded.
INFO 2007-09-26 16:00:33
Moving file C:/SAPinst ORACLE KERNEL/DDLORA.TPL to: orig_ddl_ora_tmp.tpl.
INFO 2007-09-26 16:00:33
Moving file C:/SAPinst ORACLE KERNEL/changed_ddl_ora_tmp.tpl to: DDLORA.TPL.
INFO 2007-09-26 16:00:33
Removing file C:/SAPinst ORACLE KERNEL/orig_ddl_ora_tmp.tpl.
INFO 2007-09-26 16:02:00
Package table created
PHASE 2007-09-26 16:02:10
SAP Business WareHouse
PHASE 2007-09-26 16:02:10
SAP Web Application Server
PHASE 2007-09-26 16:02:10
Request common parameters of SAP System
PHASE 2007-09-26 16:02:10
Create operating system accounts
INFO 2007-09-26 16:02:10
Changing account ACCOUNTID=S-1-5-21-1844237615-963894560-725345543-1004 ACCOUNTNAME=biwdev\SAP_LocalAdmin ACCOUNTTYPE=GROUP DESCRIPTION=SAP Local Administration Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE succeeded.
INFO 2007-09-26 16:02:10
Changing account ACCOUNTID=S-1-5-21-1844237615-963894560-725345543-1005 ACCOUNTNAME=biwdev\SAP_BWD_LocalAdmin ACCOUNTTYPE=GROUP DESCRIPTION=SAP Local Administration Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE succeeded.
INFO 2007-09-26 16:02:10
Changing account ACCOUNTID=S-1-5-21-1844237615-963894560-725345543-1006 ACCOUNTNAME=biwdev\SAP_BWD_GlobalAdmin ACCOUNTTYPE=GROUP DESCRIPTION=SAP Global Administration Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE succeeded.
INFO 2007-09-26 16:02:10
Changing account ACCOUNTID=S-1-5-21-1844237615-963894560-725345543-1007 ACCOUNTNAME=ORA_BWD_DBA ACCOUNTTYPE=GROUP CONDITION=YES DESCRIPTION=Database Operator Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE succeeded.
INFO 2007-09-26 16:02:10
Changing account ACCOUNTID=S-1-5-21-1844237615-963894560-725345543-1008 ACCOUNTNAME=ORA_BWD_OPER ACCOUNTTYPE=GROUP CONDITION=YES DESCRIPTION=Database Administration Group MEMBERSHIPSEPARATOR=, OPMODE=CREATE succeeded.
INFO 2007-09-26 16:02:10
Processing of all account operations of table t_SAPComponent_Accounts_Accounts_SHARED succeeded (operation CREATE).
INFO 2007-09-26 16:02:15
Changing account ACCOUNTID=S-1-5-21-1844237615-963894560-725345543-1009 ACCOUNTNAME=biwdev\bwdadm ACCOUNTTYPE=USER DESCRIPTION=SAP System Administrator MEMBERSHIP=biwdev\SAP_BWD_GlobalAdmin,biwdev\Users,Administrators,ORA_BWD_DBA,ORA_BWD_OPER,biwdev\SAP_LocalAdmin,biwdev\SAP_BWD_LocalAdmin MEMBERSHIPSEPARATOR=, OPMODE=CREATE USERPASSWORD=*... succeeded.
INFO 2007-09-26 16:02:15
Changing account ACCOUNTID=S-1-5-21-1844237615-963894560-725345543-1010 ACCOUNTNAME=biwdev\SAPServiceBWD ACCOUNTTYPE=USER CONDITION=YES DESCRIPTION=SAP System Service Administrator MEMBERSHIP=biwdev\SAP_BWD_GlobalAdmin,Administrators,ORA_BWD_DBA,ORA_BWD_OPER,biwdev\SAP_LocalAdmin,biwdev\SAP_BWD_LocalAdmin MEMBERSHIPSEPARATOR=, OPMODE=CREATE USERPASSWORD=*... succeeded.
INFO 2007-09-26 16:02:15
Processing of all account operations of table t_SAPComponent_Accounts_Accounts_SHARED succeeded (operation CREATE).
PHASE 2007-09-26 16:02:16
Request operating system user information
PHASE 2007-09-26 16:02:16
Request operating system user information
PHASE 2007-09-26 16:02:16
Request operating system user information
PHASE 2007-09-26 16:02:16
Request operating system user information
PHASE 2007-09-26 16:02:16
Request operating system user information
PHASE 2007-09-26 16:02:16
Request operating system user information
PHASE 2007-09-26 16:02:16
Request operating system user information
PHASE 2007-09-26 16:02:16
Request operating system user information
PHASE 2007-09-26 16:02:16
Request operating system user information
PHASE 2007-09-26 16:02:17
Request operating system user information
PHASE 2007-09-26 16:02:17
Request operating system user information
PHASE 2007-09-26 16:02:17
Request operating system user information
PHASE 2007-09-26 16:02:17
Request operating system user information
PHASE 2007-09-26 16:02:17
Request operating system user information
PHASE 2007-09-26 16:02:17
Request operating system user information
PHASE 2007-09-26 16:02:17
Request operating system user information
PHASE 2007-09-26 16:02:17
Request operating system user information
PHASE 2007-09-26 16:02:17
Request operating system user information
INFO 2007-09-26 16:02:17
Successfully added privileges 'SeTcbPrivilege SeAssignPrimaryTokenPrivilege SeIncreaseQuotaPrivilege' to account 'S-1-5-21-1844237615-963894560-725345543-1009' on host 'biwdev'!
INFO 2007-09-26 16:02:17
Successfully added privileges 'SeServiceLogonRight SeNetworkLogonRight' to account 'biwdev\SAPServiceBWD' on host 'biwdev'!
INFO 2007-09-26 16:02:17
Successfully added privileges 'SeTcbPrivilege SeAssignPrimaryTokenPrivilege SeIncreaseQuotaPrivilege' to account 'biwdev\bwdadm' on host 'biwdev'!
INFO 2007-09-26 16:02:18
Evaluating all 'tNT_RegistryEntries' table rows succeeded.
INFO 2007-09-26 16:02:19
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-09-26 16:02:20
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-09-26 16:02:21
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-09-26 16:02:21
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-09-26 16:02:22
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-09-26 16:02:23
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-09-26 16:02:24
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-09-26 16:02:24
Creating or updating all NT registry entries from the tNT_RegistryEntries table succeeded.
INFO 2007-09-26 16:02:53
Creating directory E:\oracle\BWD\sapdata1\system_1.
INFO 2007-09-26 16:02:53
Creating file system node E:\oracle\BWD/sapdata1\system_1 with type DIRECTORY succeeded.
INFO 2007-09-26 16:02:53
Processing of all file system node operations of table tORA_SapdataNodes succeeded.
INFO 2007-09-26 16:02:53
Processing of all file system node operations of table tORA_DatabaseServerNodes succeeded.
INFO 2007-09-26 16:02:53
Processing of all file system node operations of table tORA_SapdataNodes succeeded.
INFO 2007-09-26 16:02:55
Copying file C:/dump/master/NT/COMMON/INSTALL/INITSID.ORA to: E:\oracle\ora92\database\initBWD.ora.
INFO 2007-09-26 16:02:55
Creating file E:\oracle\ora92\database\initBWD.ora.
INFO 2007-09-26 16:02:55
Copying file system node C:\dump\master/NT/COMMON/INSTALL/INITSID.ORA with type FILE to E:\oracle\ora92\database\initBWD.ora succeeded.
INFO 2007-09-26 16:02:55
Copying file C:/dump/master/NT/COMMON/INSTALL/INITSID.SAP to: E:\oracle\ora92\database\initBWD.sap.
INFO 2007-09-26 16:02:55
Creating file E:\oracle\ora92\database\initBWD.sap.
INFO 2007-09-26 16:02:55
Copying file system node C:\dump\master/NT/COMMON/INSTALL/INITSID.SAP with type FILE to E:\oracle\ora92\database\initBWD.sap succeeded.
INFO 2007-09-26 16:02:55
Copying file C:/dump/master/NT/COMMON/INSTALL/INITSID.DBA to: E:\oracle\ora92\database\initBWD.dba.
INFO 2007-09-26 16:02:55
Creating file E:\oracle\ora92\database\initBWD.dba.
INFO 2007-09-26 16:02:55
Copying file system node C:\dump\master/NT/COMMON/INSTALL/INITSID.DBA with type FILE to E:\oracle\ora92\database\initBWD.dba succeeded.
INFO 2007-09-26 16:02:55
Processing of all file system node operations of table tORA_ServerConfig_FORMS succeeded.
INFO 2007-09-26 16:02:57
Processing of adapt operation tORA_ServerConfig succeeded.
INFO 2007-09-26 16:02:59
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-09-26 16:03:02
Moving file E:/oracle/ora92/database/initBWD.ora to: orig_init_ora_tmp.txt.
INFO 2007-09-26 16:03:02
Moving file C:/SAPinst ORACLE KERNEL/changed_init_ora_tmp.txt to: E:\oracle\ora92\database\initBWD.ora.
INFO 2007-09-26 16:03:02
Removing file C:/SAPinst ORACLE KERNEL/orig_init_ora_tmp.txt.
WARNING 2007-09-26 16:03:02
PROBLEM: 'E:\oracle\ora92/bin/oradim' not found. CAUSE: Unable to find application via absolute path in filesystem. Application could perhaps be found using environment variable path or is really missing. Trying to call the application nevertheless.
WARNING 2007-09-26 16:03:02
PROBLEM: 'E:\oracle\ora92/bin/oradim' not found. CAUSE: Unable to find application via absolute path in filesystem. Application could perhaps be found using environment variable path or is really missing. Trying to call the application nevertheless.
INFO 2007-09-26 16:03:02
'E:\oracle\ora92/bin/oradim -new -sid BWD -STARTMODE auto' returned with '20'.
INFO 2007-09-26 16:03:04
Changed working directory to C:\SAPinst ORACLE KERNEL.
INFO 2007-09-26 16:03:06
Changed working directory to C:\SAPinst ORACLE KERNEL.
ERROR 2007-09-26 16:03:13
CJS-00084 SQL Statement or Script failed. Error Message: ORA-32004: obsolete and/or deprecated parameter(s) specifiedORACLE instance started.
ERROR 2007-09-26 16:03:13
FJS-00012 Error when executing script.
Please let me know, what was tha problem.
Regards,
satish

I suggest you upgrade your Oracle installation to 9.2.0.7 or 9.2.0.8 and then try again.
Markus

ORA-000060 (deadlock) and no alert/trace info

Similar Messages

Maybe you are looking for