ORA-00060 dead lock happen on R12 demo database

We have EBS R12 (12.0.4) on Redhat Linux system when I check alert.log file and found demo database (VIS) have ORA-00060 dead lock. The dead lock happen on statement:
UPDATE FND_CONCURRENT_REQUESTS SET PP_END_DATE = SYSDATE, POST_REQUEST_STATUS = 'E' WHERE REQUEST_ID = :B1
Do I need do anthing relate to this ORA- error or just ignore it?
Thanks.

Thank you for answer. I checked CM log and did NOT find any error.
I also read document 153717.1 and compare FND_CONCURRENT_REQUESTS table definition. The initial number of trnasaction is 10 and max is 255. I try to use OEM to change "initial transaction number" and it don't allow to.
Any ideal???

Similar Messages

ORA-04020 dead lock ?

I have two procedures need to call each other, like:
create or replace procedure A
as
begin
B;
end A;
create or replace procedure B
as
A;
end B;
when I compiled them, I got a message saying that deadlock detected.
If I have the logic like that, and procs A and B are defenitely needed, how can I handle this issue?
Thanks

An interesting change in 10G. Instead of the deadlock, it immediately reports the compilation errors and running either of the procedures generates an immediate "Object is invalid" error.
SQL> CREATE OR REPLACE PROCEDURE a (p_who IN VARCHAR2) AS
2 BEGIN
3     IF p_who <> 'B' THEN
4        DBMS_OUTPUT.Put_Line('Call B');
5     ELSE
6        DBMS_OUTPUT.Put_Line('Called by B');
7     END IF;
8 END;
9 /
Procedure created.
SQL> SHOW ERRORS
No errors.
SQL>
SQL> CREATE OR REPLACE PROCEDURE b (p_who IN VARCHAR2) AS
2 BEGIN
3     IF p_who <> 'A' THEN
4        a('B');
5     ELSE
6        DBMS_OUTPUT.Put_Line('Called by A');
7     END IF;
8 END;
9 /
Procedure created.
SQL> SHOW ERRORS
No errors.
SQL>
SQL> CREATE OR REPLACE PROCEDURE a (p_who IN VARCHAR2) AS
2 BEGIN
3     IF p_who <> 'B' THEN
4        b('A');
5     ELSE
6        DBMS_OUTPUT.Put_Line('Called by B');
7     END IF;
8 END;
9 /
Procedure created.
SQL> SHOW ERRORS
No errors.
SQL>
SQL> select object_name, object_type from user_objects where status <> 'VALID' ;
OBJECT_NAME                     OBJECT_TYPE
A                               PROCEDURE
B                               PROCEDURE
2 rows selected.
SQL> alter procedure a compile ;
Warning: Procedure altered with compilation errors.
SQL> show errors
Errors for PROCEDURE A:
LINE/COL ERROR
4/7      PL/SQL: Statement ignored
4/7      PLS-00905: object XXXXXXXX.B is invalid
SQL> alter procedure b compile ;
Warning: Procedure altered with compilation errors.
SQL> show errors
Errors for PROCEDURE B:
LINE/COL ERROR
4/7      PL/SQL: Statement ignored
4/7      PLS-00905: object XXXXXXXX.A is invalid
SQL> exec a ;
BEGIN a ; END;
ERROR at line 1:
ORA-06550: line 1, column 7:
PLS-00905: object XXXXXXXX.A is invalid
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
SQL> exec b ;
BEGIN b ; END;
ERROR at line 1:
ORA-06550: line 1, column 7:
PLS-00905: object XXXXXXXX.B is invalid
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
SQL> disconnect
Disconnected from Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL>

ORA-00060 error Dead lock

Hi,
One of my developers trying to insert in to one table from 2 different sessions at the same time and got dead lock error.From my trace file I got this
Deadlock graph:
---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name process session holds waits process session holds waits
TX-00090026-00290e72 168 227 X 148 223 S
TX-00020012-0034e086 148 223 X 168 227 S
session 227: DID 0001-00A8-000036D2 session 223: DID 0001-0094-000052FC
session 223: DID 0001-0094-000052FC session 227: DID 0001-00A8-000036D2
Rows waited on:
Session 223: obj - rowid = 00125244 - AAAAAAAIqAAATseAAA <-------------------- 00125244
(dictionary objn - 1200708, file - 554, block - 80670, slot - 0)
Session 227: obj - rowid = 00125244 - AAAAAAAIqAAATsdAAA <-------------------- 00125244
(dictionary objn - 1200708, file - 554, block - 80669, slot - 0)
It seems to be 2 sessions trying to take same rowid and torying to insert into that.How it happens, those should pickup random rowid's and insert independenlty.
Please suggest me what could be the reason.
Thanks Very Much
Anand

Get with your developer and see what the code is really doing as well as how it is being used. All of the deadlocks I have encountered to date had their root cause in the application code. Spending some time with the developers to see what they are doing and more importantly why, will lead you to finding a solution to your deadlock problem.

Sqlldr- ORA-00060: deadlock detected while waiting for resource

Hi Team,
My database version is 11.1.0.7.0. I am loading the data using sqlldr. I am getting the error ORA-00060: deadlock detected while waiting for resource. once dead lock detected ,whether data will be rejected after commit point reached(Rows=100000). FYI information only sqllder is running on the database,it is getting completed withing 5-10min. please help me whether any other lock happening on this due to sqllder.
sqlldr userid=orcl/orcle control=".$controlfile." log=".$logfile.".log data=".$datafile." bad=".$badfile." discard=".$discardfile." Bindsize=19000000 Rows=100000 Readsize=20000000 Errors=1000000";
Thanks in advance

user9256814 wrote:
Hi Team,
My database version is 11.1.0.7.0. I am loading the data using sqlldr. I am getting the error ORA-00060: deadlock detected while waiting for resource. once dead lock detected ,whether data will be rejected after commit point reached(Rows=100000). FYI information only sqllder is running on the database,it is getting completed withing 5-10min. please help me whether any other lock happening on this due to sqllder.
sqlldr userid=orcl/orcle control=".$controlfile." log=".$logfile.".log data=".$datafile." bad=".$badfile." discard=".$discardfile." Bindsize=19000000 Rows=100000 Readsize=20000000 Errors=1000000";
Thanks in advanceadditional clues will exist within alert_SID.ora file & subsequent trace file.

ORA-00060 DEADLOCK DETECTED - Need Help

Hi Gurus,
I have a question on how to determine the trace log. Where the deadlock happen.
Please help. I have no other hint on how to resolve the error.
*** ACTION NAME:() 2008-08-06 03:34:21.740
*** MODULE NAME:(OEM.SystemPool) 2008-08-06 03:34:21.740
*** SERVICE NAME:(celcomdb) 2008-08-06 03:34:21.740
*** CLIENT ID:() 2008-08-06 03:34:21.740
*** SESSION ID:(113.3188) 2008-08-06 03:34:21.740
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-0000c45a-00000000 119 113 X 27 60 SX
TX-0004002c-000269bc 27 60 X 119 113 X
session 113: DID 0001-0077-00000028 session 60: DID 0001-001B-00000278
session 60: DID 0001-001B-00000278 session 113: DID 0001-0077-00000028
Rows waited on:
Session 60: no row
Session 113: obj - rowid = 0000C384 - AAAMOEAADAAAF99AAA
(dictionary objn - 50052, file - 3, block - 24445, slot - 0)
Information on the OTHER waiting sessions:
Session 60:
pid=27 serial=1313 audsid=0 user: 51/SYSMAN
O/S info: user: oracle10, term: UNKNOWN, ospid: 14610456, machine: S63KLJ01
program: oracle@S63KLJ01 (J000)
application name: EM_PING, hash value=2147830874
action name: AGENT_STATUS_MARKER, hash value=2850782869
Current SQL information unavailable
End of information on OTHER waiting sessions.
Current SQL statement for this session:
UPDATE MGMT_OMS_PARAMETERS SET VALUE=TO_CHAR(SYSDATE, 'DD-Mon-YYYY HH24:MI:SS') WHERE HOST_URL=:B1 AND NAME='TIMESTAMP'
----- PL/SQL Call Stack -----
object line object
handle number name
70000006e5ab778 39 package body SYSMAN.MGMT_FAILOVER
70000002e8aaf98 1 anonymous block
===================================================
PROCESS STATE
Process global information:
process: 70000006f4b1598, call: 70000006a9c9320, xact: 70000006dedcf98, curses: 70000006f5a5a50, usrses: 70000006f5a5a50
SO: 70000006f4b1598, type: 2, owner: 0, flag: INIT/-/-/0x00
(process) Oracle pid=119, calls cur/top: 70000006a9c9320/70000006abfcaf8, flag: (0) -
int error: 0, call error: 0, sess error: 0, txn error 0
(post info) last post received: 0 0 9
last post received-location: ksqrcl
last process to post me: 70000006f484118 141 0
last post sent: 0 0 0
last post sent-location: No post
last process posted by me: none
(latch info) wait_event=0 bits=0
Process Group: DEFAULT, pseudo proc: 70000006f50bcd0
O/S info: user: oracle10, term: UNKNOWN, ospid: 11538508
OSD pid info: Unix process pid: 11538508, image: oraclecelcomdb@S63KLJ01
Dump of memory from 0x070000006F45FCD0 to 0x070000006F45FED8
70000006F45FCD0 00000004 00000000 07000000 6A9ABD00 [............j...]
70000006F45FCE0 00000010 0003139D 07000000 6ABFCAF8 [............j...]
70000006F45FCF0 00000003 0003139D 07000000 6F8FD600 [............o...]
70000006F45FD00 0000000B 0003139D 07000000 6F5A5A50 [............oZZP]
70000006F45FD10 00000004 00031291 00000000 00000000 [................]
70000006F45FD20 00000000 00000000 00000000 00000000 [................]
Repeat 26 times
70000006F45FED0 00000000 00000000 [........]
SO: 70000006f5a5a50, type: 4, owner: 70000006f4b1598, flag: INIT/-/-/0x00
(session) sid: 113 trans: 70000006dedcf98, creator: 70000006f4b1598, flag: (41) USR/- BSY/-/-/-/-/-
DID: 0001-0077-00000028, short-term DID: 0000-0000-00000000
txn branch: 0
oct: 6, prv: 0, sql: 70000006e5a9140, psql: 70000006e5a9410, user: 51/SYSMAN
O/S info: user: oracle10, term: unknown, ospid: 1234, machine: S63KLJ01
program: OMS
client info: S63KLJ01_Management_Service
application name: OEM.SystemPool, hash value=2960518376
last wait for 'enq: TX - row lock contention' blocking sess=0x70000006f5611e0 seq=322 wait_time=2929700 seconds since wait started=4
name|mode=54580006, usn<<16 | slot=4002c, sequence=269bc
Dumping Session Wait History
for 'enq: TX - row lock contention' count=1 wait_time=2929700
name|mode=54580006, usn<<16 | slot=4002c, sequence=269bc
for 'enq: TM - contention' count=1 wait_time=224489
name|mode=544d0006, object #=c45a, table/partition=0
for 'enq: TM - contention' count=1 wait_time=2929708
name|mode=544d0006, object #=c45a, table/partition=0
for 'SQL*Net message from client' count=1 wait_time=35033
driver id=28444553, #bytes=1, =0
for 'SQL*Net message to client' count=1 wait_time=1
driver id=28444553, #bytes=1, =0
for 'SQL*Net message from client' count=1 wait_time=227
driver id=28444553, #bytes=1, =0
for 'SQL*Net message to client' count=1 wait_time=1
driver id=28444553, #bytes=1, =0
for 'latch: library cache' count=1 wait_time=96826
address=70000006cf2f298, number=d6, tries=0
for 'latch: library cache' count=1 wait_time=36929
address=70000006cf2f0b8, number=d6, tries=0
for 'SQL*Net message from client' count=1 wait_time=131974
driver id=28444553, #bytes=1, =0
temporary object counter: 0
Virtual Thread:
kgskvt: 70000006e82cd98, sess: 70000006f5a5a50, vc: 0, proc: 70000006f4b1598
consumer group cur: OTHER_GROUPS (upd? 0), mapped: DEFAULT_CONSUMER_GROUP, orig:
vt_state: 0x200, vt_flags: 0x30, blkrun: 0
is_assigned: 1, in_sched: 0 (0)
vt_active: 0 (pending: 1)
used quanta: 0 (cg: 0)
cpu start time: 0, quantum status: 0x0
quantum checks to skip: 0, check thresh: 0
idle time: 0, active time: 0 (cg: 0)
cpu yields: 0 (cg: 0), waits: 0 (cg: 0), wait time: 0 (cg: 0)
queued time outs: 0, time: 0 (cur 0, cg 0)
calls aborted: 0, num est exec limit hit: 0
undo current: 0k max: 0k
UOL used : 0 locks(used=2, free=0)
KGX Atomic Operation Log 70000002eb54978
Mutex 0(0, 0) idn 0 oper NONE
Cursor Parent uid 113 efd 15 whr 22 slp 0
oper=NONE pt1=0 pt2=0 pt3=0
pt4=0 u41=0 stt=0
KGX Atomic Operation Log 70000002eb549c0
Mutex 0(0, 0) idn 0 oper NONE
Library Cache uid 113 efd 0 whr 0 slp 0
KGX Atomic Operation Log 70000002eb54a08
Mutex 0(0, 0) idn 0 oper NONE
Library Cache uid 113 efd 0 whr 0 slp 0
SO: 70000006ae53108, type: 53, owner: 70000006f5a5a50, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=70000006ae53108 handle=70000002e8e8150 mode=N
call pin=0 session pin=0 hpc=0000 hlc=0000
htl=70000006ae53188[70000006a753478,70000006abaf090] htb=70000006abaf090 ssga=70000006abae018
user=70000006f5a5a50 session=70000006f5a5a50 count=1 flags=CBK[0020] savepoint=0x0
LIBRARY OBJECT HANDLE: handle=70000002e8e8150 mtx=70000002e8e8280(0) cdp=0
namespace=CRSR flags=RON/KGHP/PN0/EXP/[10010100]
kkkk-dddd-llll=0000-0001-0001 lock=N pin=S latch#=4 hpc=0000 hlc=0000
lwt=70000002e8e81f8[70000002e8e81f8,70000002e8e81f8] ltm=70000002e8e8208[70000002e8e8208,70000002e8e8208]
pwt=70000002e8e81c0[70000002e8e81c0,70000002e8e81c0] ptm=70000002e8e81d0[70000002e8e81d0,70000002e8e81d0]
ref=70000002e8e8228[70000004ad30028,70000004ad30028] lnd=70000002e8e8240[70000002e8e8240,70000002e8e8240]
LIBRARY OBJECT: object=70000004ad2f990
type=CRSR flags=EXS[0001] pflags=[0000] status=VALD load=0
DEPENDENCIES: count=1 size=16
AUTHORIZATIONS: count=1 size=16 minimum entrysize=16
ACCESSES: count=1 size=16
TRANSLATIONS: count=1 size=16
DATA BLOCKS:
data# heap pointer status pins change whr
0 70000006eada130 70000004ad2faa8 I/P/A/-/- 0 NONE 00
6 70000004ad2fec8 700000040f57a78 I/P/A/-/E 0 NONE 00
----------------------------------------

Oracle handles dead lock by its own. but to resolve the issue u can try following things.
1. take explain for UPDATE MGMT_OMS_PARAMETERS SET VALUE=TO_CHAR(SYSDATE, 'DD-Mon-YYYY HH24:MI:SS') WHERE HOST_URL=:B1 AND NAME='TIMESTAMP';
2. analyze above explain plan and try to tune it.
i think, its because of missing indexes.

ORA-00060 "deadlock detected while waiting for resource"

Hello.
I am having an oracle deadlock when calling a stored procedure (wich updates several records in several tables) from several threads: ORA-00060 error. The error does not happen very often but from time to time, normally the calls to this proceudre end ok.
Each call starts and ends a transaction. (When the oracle error raises the transaction where it raises is rolled back) and the other transactions can go on.
I don't how to avoid it. Should it be solved at the stored procedure level or could it be solved at java level by doing the call to the stored procedure to be synchronized?
Thanks in advance.

Fernando_Sanchez wrote:
Hello.
I am having an oracle deadlock when calling a stored procedure (wich updates several records in several tables) from several threads: ORA-00060 error. The error does not happen very often but from time to time, normally the calls to this proceudre end ok.Which doesn't really sound good.
If you have a java thread then to do JDBC, regardless of what type, you get a new connection and new statements in each one.
If you are not doing that then that is a problem.
If you are doing that then the thread information is irrelevant at the java level.
You can of course do all sorts of interesting things with locks and transactions in Oracle and via stored procs but other ways as well. And if you are not careful it will cause problems.

ORA-00060: deadlock detected while waiting for resource CLOSE cursor

Hi,
I am a new member of this forum. I am working with a problem we got a few weeks ago. It is from a Pro C batch executable running on 10 threads dealing with >800 data accessed from multiple tables. The error as reported came from a package.function call.
This is the error I encountered:
process_item~G****, D***~-60~ORA-00060: deadlock detected while waiting for resource~PACKAGE ERROR = CLOSE cursor C_***** in package R***.I*** 7641
The cursor is a simple SELECT cursor without Table or Record locking.
My questions are:
*Upon the occurrence of this error, is the execution already at the CLOSE cursor line or did the error occurred between the OPEN cursor and the CLOSE cursor? There are several lines of code in between OPEN and CLOSE:
- one that calls for a package.function that simply stores parameter values to a variable
- another one which fetches the cursor. The group that holds the cursor values is only used by a single function in the package
*Is it possible for this CLOSE cursor to cause a deadlock? What could have caused this?
*From what I know, Oracle deals with deadlocks by aborting the deadlocking process while others continue, but this deadlock caused our program to hang. How is this possible? Could the root cause of the deadlock be from our threading program? This is a rare occurrence and happened only twice this year.
Thanks,
Raf

Raf Serrano wrote:
Hi,
I am a new member of this forum. I am working with a problem we got a few weeks ago. It is from a Pro C batch executable running on 10 threads dealing with >800 data accessed from multiple tables. The error as reported came from a package.function call.
This is the error I encountered:
process_item~G****, D***~-60~ORA-00060: deadlock detected while waiting for resource~PACKAGE ERROR = CLOSE cursor C_***** in package R***.I*** 7641
The cursor is a simple SELECT cursor without Table or Record locking.
My questions are:
*Upon the occurrence of this error, is the execution already at the CLOSE cursor line or did the error occurred between the OPEN cursor and the CLOSE cursor? There are several lines of code in between OPEN and CLOSE:
- one that calls for a package.function that simply stores parameter values to a variable
- another one which fetches the cursor. The group that holds the cursor values is only used by a single function in the package
*Is it possible for this CLOSE cursor to cause a deadlock? What could have caused this?
*From what I know, Oracle deals with deadlocks by aborting the deadlocking process while others continue, but this deadlock caused our program to hang. How is this possible? Could the root cause of the deadlock be from our threading program? This is a rare occurrence and happened only twice this year.
Thanks,
RafSELECT (without FOR UPDATE) statements are never involved in ORA-00060.
only DML statements throw ORA-00060 error

Restore using TSPITR Results Dead lock error

This is the step is followed but i am getting deadlock error .please give your valuable suggestion .
Product Used:oracle 11g in linux environmnet
1)Before taking backup get SCN number for restore.
Command applied: Select current_scn from v$database;
2)running Full backup of database
Command applied:
configure controlfile autobackup on;
backup database;
CROSSCHECK BACKUP;
exit;
3)Running level 0 incremental backup
Command applied:
BACKUP AS COMPRESSED BACKUPSET INCREMENTAL LEVEL 0 TAG ='WEEKLY' TABLESPACE TEST;
exit;
3) Running level 1 incremental backup
Command applied:
BACKUP AS COMPRESSED BACKUPSET INCREMENTAL LEVEL 1 TAG ='DAILY' TABLESPACE TEST;
4)Before Restore(TSPITR) following procedure are applied under sysdba privilege
Command applied:
SQL 'exec dbms_backup_restore.manageauxinstance ('TSPITR',1)';
5)TSPITR Restore command
Command applied:
run
SQL 'ALTER TABLESPACE TEST OFFLINE'
RECOVER TABLESPACE TEST UNTIL SCN 1791053 AUXILIARY DESTINATION '/opt/oracle/base/flash_recovery_area';
SQL 'ALTER TABLESPACE TEST ONLINE';
and i tried with this option also(the same error i was getting)
Command applied:
run
SQL 'ALTER TABLESPACE TEST OFFLINE';
SET UNTIL SCN 1912813;
RESTORE TABLESPACE TEST ;
RECOVER TABLESPACE TEST UNTIL SCN 1912813 AUXILIARY DESTINATION '/opt/oracle/base/flash_recovery_area';
SQL 'ALTER TABLESPACE TEST ONLINE';
The follwing error i get for above mentioned restore command
Recovery Manager: Release 11.2.0.1.0 - Production on Tue Aug 17 18:11:18 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: NEW10 (DBID=2860680927)
RMAN> run
2> {
3> SQL 'ALTER TABLESPACE TEST OFFLINE';
4> RECOVER TABLESPACE TEST UNTIL SCN 1791053 AUXILIARY DESTINATION '/opt/oracle/base/flash_recovery_area';
5> SQL 'ALTER TABLESPACE TEST ONLINE';
6> }
7>
using target database control file instead of recovery catalog
sql statement: ALTER TABLESPACE TEST OFFLINE
Starting recover at 17-AUG-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=404 device type=DISK
RMAN-05026: WARNING: presuming following set of tablespaces applies to specified point-in-time
List of tablespaces expected to have UNDO segments
Tablespace SYSTEM
Tablespace UNDOTBS1
Creating automatic instance, with SID='BkAq'
initialization parameters used for automatic instance:
db_name=NEW10
db_unique_name=BkAq_tspitr_NEW10
compatible=11.2.0.0.0
db_block_size=8192
db_files=200
sga_target=280M
processes=50
db_create_file_dest=/opt/oracle/base/flash_recovery_area
log_archive_dest_1='location=/opt/oracle/base/flash_recovery_area'
#No auxiliary parameter file used
starting up automatic instance NEW10
Oracle instance started
Total System Global Area 292933632 bytes
Fixed Size 1336092 bytes
Variable Size 100666596 bytes
Database Buffers 184549376 bytes
Redo Buffers 6381568 bytes
Automatic instance created
Running TRANSPORT_SET_CHECK on recovery set tablespaces
TRANSPORT_SET_CHECK completed successfully
contents of Memory Script:
# set requested point in time
set until scn 1791053;
# restore the controlfile
restore clone controlfile;
# mount the controlfile
sql clone 'alter database mount clone database';
# archive current online log
sql 'alter system archive log current';
# avoid unnecessary autobackups for structural changes during TSPITR
sql 'begin dbms_backup_restore.AutoBackupFlag(FALSE); end;';
executing Memory Script
executing command: SET until clause
Starting restore at 17-AUG-10
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=59 device type=DISK
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /opt/oracle/base/flash_recovery_area/NEW10/autobackup/2010_08_17/o1_mf_s_727280767_66nmo8x7_.bkp
channel ORA_AUX_DISK_1: piece handle=/opt/oracle/base/flash_recovery_area/NEW10/autobackup/2010_08_17/o1_mf_s_727280767_66nmo8x7_.bkp tag=TAG20100817T142607
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
output file name=/opt/oracle/base/flash_recovery_area/NEW10/controlfile/o1_mf_66o0wsh8_.ctl
Finished restore at 17-AUG-10
sql statement: alter database mount clone database
sql statement: alter system archive log current
sql statement: begin dbms_backup_restore.AutoBackupFlag(FALSE); end;
contents of Memory Script:
# set requested point in time
set until scn 1791053;
# set destinations for recovery set and auxiliary set datafiles
set newname for clone datafile 1 to new;
set newname for clone datafile 8 to new;
set newname for clone datafile 3 to new;
set newname for clone datafile 2 to new;
set newname for clone datafile 9 to new;
set newname for clone tempfile 1 to new;
set newname for datafile 7 to
"/opt/oracle/base/oradata/NEW10/test01.dbf";
# switch all tempfiles
switch clone tempfile all;
# restore the tablespaces in the recovery set and the auxiliary set
restore clone datafile 1, 8, 3, 2, 9, 7;
switch clone datafile all;
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
renamed tempfile 1 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_temp_%u_.tmp in control file
Starting restore at 17-AUG-10
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00001 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00008 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00003 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_undotbs1_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00002 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00009 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_%u_.dbf
channel ORA_AUX_DISK_1: reading from backup piece /opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnndf_TAG20100817T140128_66nl7174_.bkp
channel ORA_AUX_DISK_1: piece handle=/opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnndf_TAG20100817T140128_66nl7174_.bkp tag=TAG20100817T140128
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:02:45
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00007 to /opt/oracle/base/oradata/NEW10/test01.dbf
channel ORA_AUX_DISK_1: reading from backup piece /opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnnd0_WEEKLY_66nl9m8k_.bkp
channel ORA_AUX_DISK_1: piece handle=/opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnnd0_WEEKLY_66nl9m8k_.bkp tag=WEEKLY
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:06:55
Finished restore at 17-AUG-10
datafile 1 switched to datafile copy
input datafile copy RECID=6 STAMP=727294911 file name=/opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_66o0x1sf_.dbf
datafile 8 switched to datafile copy
input datafile copy RECID=7 STAMP=727294911 file name=/opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_66o0x1r9_.dbf
datafile 3 switched to datafile copy
input datafile copy RECID=8 STAMP=727294911 file name=/opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_undotbs1_66o0x1vr_.dbf
datafile 2 switched to datafile copy
input datafile copy RECID=9 STAMP=727294911 file name=/opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_66o0x1vj_.dbf
datafile 9 switched to datafile copy
input datafile copy RECID=10 STAMP=727294911 file name=/opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_66o0x1rs_.dbf
contents of Memory Script:
# set requested point in time
set until scn 1791053;
# online the datafiles restored or switched
sql clone "alter database datafile 1 online";
sql clone "alter database datafile 8 online";
sql clone "alter database datafile 3 online";
sql clone "alter database datafile 2 online";
sql clone "alter database datafile 9 online";
sql clone "alter database datafile 7 online";
# recover and open resetlogs
recover clone database tablespace "TEST", "SYSTEM", "UNDOTBS1", "SYSAUX" delete archivelog;
alter clone database open resetlogs;
executing Memory Script
executing command: SET until clause
sql statement: alter database datafile 1 online
sql statement: alter database datafile 8 online
sql statement: alter database datafile 3 online
sql statement: alter database datafile 2 online
sql statement: alter database datafile 9 online
sql statement: alter database datafile 7 online
Starting recover at 17-AUG-10
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting incremental datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
destination for restore of datafile 00007: /opt/oracle/base/oradata/NEW10/test01.dbf
channel ORA_AUX_DISK_1: reading from backup piece /opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnnd1_DAILY_66nmf6qs_.bkp
channel ORA_AUX_DISK_1: piece handle=/opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnnd1_DAILY_66nmf6qs_.bkp tag=DAILY
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
starting media recovery
archived log for thread 1 with sequence 39 is already on disk as file /opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_39_66nmc1dg_.arc
archived log for thread 1 with sequence 40 is already on disk as file /opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_40_66nmcfw4_.arc
archived log for thread 1 with sequence 41 is already on disk as file /opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_41_66nmcwcf_.arc
archived log for thread 1 with sequence 42 is already on disk as file /opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_42_66nmddbw_.arc
archived log for thread 1 with sequence 43 is already on disk as file /opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_43_66o0wyys_.arc
archived log file name=/opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_39_66nmc1dg_.arc thread=1 sequence=39
archived log file name=/opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_40_66nmcfw4_.arc thread=1 sequence=40
archived log file name=/opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_41_66nmcwcf_.arc thread=1 sequence=41
archived log file name=/opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_42_66nmddbw_.arc thread=1 sequence=42
archived log file name=/opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_43_66o0wyys_.arc thread=1 sequence=43
media recovery complete, elapsed time: 00:00:50
Finished recover at 17-AUG-10
database opened
contents of Memory Script:
# make read only the tablespace that will be exported
sql clone 'alter tablespace TEST read only';
# create directory for datapump import
sql "create or replace directory TSPITR_DIROBJ_DPDIR as ''
/opt/oracle/base/flash_recovery_area''";
# create directory for datapump export
sql clone "create or replace directory TSPITR_DIROBJ_DPDIR as ''
/opt/oracle/base/flash_recovery_area''";
executing Memory Script
sql statement: alter tablespace TEST read only
sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/opt/oracle/base/flash_recovery_area''
sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/opt/oracle/base/flash_recovery_area''
Performing export of metadata...
EXPDP> Starting "SYS"."TSPITR_EXP_BkAq":
EXPDP> Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
EXPDP> Processing object type TRANSPORTABLE_EXPORT/TABLE
EXPDP> Processing object type TRANSPORTABLE_EXPORT/GRANT/OWNER_GRANT/OBJECT_GRANT
EXPDP> Processing object type TRANSPORTABLE_EXPORT/INDEX
EXPDP> Processing object type TRANSPORTABLE_EXPORT/CONSTRAINT/CONSTRAINT
EXPDP> Processing object type TRANSPORTABLE_EXPORT/INDEX_STATISTICS
EXPDP> Processing object type TRANSPORTABLE_EXPORT/TRIGGER
EXPDP> Processing object type TRANSPORTABLE_EXPORT/TABLE_STATISTICS
EXPDP> Processing object type TRANSPORTABLE_EXPORT/POST_INSTANCE/PLUGTS_BLK
EXPDP> Master table "SYS"."TSPITR_EXP_BkAq" successfully loaded/unloaded
EXPDP> ******************************************************************************
EXPDP> Dump file set for SYS.TSPITR_EXP_BkAq is:
EXPDP> /opt/oracle/base/flash_recovery_area/tspitr_BkAq_82690.dmp
EXPDP> ******************************************************************************
EXPDP> Datafiles required for transportable tablespace TEST:
EXPDP> /opt/oracle/base/oradata/NEW10/test01.dbf
EXPDP> Job "SYS"."TSPITR_EXP_BkAq" successfully completed at 18:25:02
Export completed
contents of Memory Script:
# shutdown clone before import
shutdown clone immediate
# drop target tablespaces before importing them back
sql 'drop tablespace TEST including contents keep datafiles';
executing Memory Script
database closed
database dismounted
Oracle instance shut down
sql statement: drop tablespace TEST including contents keep datafiles
Removing automatic instance
shutting down automatic instance
target database instance not started
Automatic instance removed
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_temp_66o1k480_.tmp deleted
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/onlinelog/o1_mf_3_66o1k0mg_.log deleted
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/onlinelog/o1_mf_2_66o1jyt4_.log deleted
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/onlinelog/o1_mf_1_66o1jx3w_.log deleted
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_66o0x1rs_.dbf deleted
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_66o0x1vj_.dbf deleted
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_undotbs1_66o0x1vr_.dbf deleted
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_66o0x1r9_.dbf deleted
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_66o0x1sf_.dbf deleted
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/controlfile/o1_mf_66o0wsh8_.ctl deleted
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/17/2010 18:25:36
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of sql command on default channel at 08/17/2010 18:25:25
RMAN-11003: failure during parse/execution of SQL statement: drop tablespace TEST including contents keep datafiles
ORA-00604: error occurred at recursive SQL level 1
ORA-00060: deadlock detected while waiting for resource
Recovery Manager complete.
please give your valuable suggestion .It should be more helpful for us.
Edited by: user10750009 on Aug 20, 2010 1:07 AM
Edited by: user10750009 on Aug 20, 2010 1:15 AM

I want TSPITR ,during this operation i faced this deadlock error.
Before that we faced roll backsegment error for that we applied follwing workaround .
If i applied follwing workaround before every backup and restore .i didn't get any error .all things went successful.
spool /tmp/Createtest.log
connect / as sysdba
REM Perform startup in case we are still down
ALTER SYSTEM SET PROCESSES=500 SCOPE=SPFILE;
SHUT IMMEDIATE;
STARTUP MOUNT EXCLUSIVE;
ALTER DATABASE ARCHIVELOG;
ARCHIVE LOG START;
ALTER DATABASE OPEN;
connECT / as sysdba;
alter system set undo_management = MANUAL scope=spfile;
shutdown immediate;
startup;
Connect / as sysdba;
DROP TABLE TEST123;
create table test123 (t1 number, t2 varchar2(10));
begin
for i in 1.. 300000 loop
insert into test values (i,'AAAAAAAAAA');
end loop;
end;
delete test123;
commit;
alter system set undo_management = auto scope=spfile;
shutdown immediate ;
startup ;
The above workaround we applied before creating tablespace and datafile ,after that we face some dead lock error while restore TSPITR .Did you need any more information
Edited by: user10750009 on Aug 20, 2010 1:12 AM

Dead Lock occured while Sync index in oracle text

Hi All,
We are facing dead lock issue which syncing the oracle text index . The index is built on the local partitioned table and the sync index has the parameters below,
parallel - 4
memory - 20M
the error message is,
System error: Plsql job execution is failed with
error code -20000 and error message ORA-20000: Oracle Text error: DRG-50610:
internal error: drvdml.ParallelDML DRG-50857: oracle error in
drvdml.ParallelDML ORA-12801: error signaled in parallel query server P003,
instance xxxx.enterprisenet.org:xxxx (1) ORA-20000: Oracle Text error:
DRG-50857: oracle error in drepdump_dollarp_insert ORA-00060: deadlock detected
while waiting for resource ORA-06512: at "CTXSYS.DRUE", line 160
ORA-06512: at "CTXSYS.DRVPARX",
Thanks in advance.

How many occurrences of XYZ are there per XML document ?
If there are more than one, then obviously you cannot create such an index on it.
In this case, you'll need an XMLIndex, unstructured or structured, depending on the type of queries you want to run.
If there's only one occurrence, could you post a sample document and your db version?
Thanks.

ORA-00060 during remove workspace

I'm using Oracle Release 9.2.0.4 with Workspace Manager.
In my application all changes are made inside long transaction, all involved tables are versioned.
Several users work concurrently, the users can not modify the same rows (update/delete), insert are possible
(the application generates automatically the unique primary keys using sequences)
Any user session operates in this way:
- Create workspace: execute dbms_wm.createworkspace('ws1');
- go to workspace : execute dbms_wm.gotoworkspace('ws1');
- make changes: update/delete/insert on different tables
- exit from workspace: execute dbms_wm.gotoworkspace('LIVE');
- merge/rollback workspace: execute dbms_wm.mergeworkspace('ws1')/dbms_wm.rollbackworkspace('ws1');
- remove workspace: execute dbms_wm.removeworkspace('ws1');
Sometimes the following error occurs during dbms_wm.removeworkspace:
ORA-00060 deadlock detected while waiting for resource
While this error can occur? Can I prevent this error?
In the follow I include the content of oracle trace files:
oraadmn6@cdsv00jd:SIGASP> more /app/oraadmn6/admin/SIGASP/udump/sigasp_ora_21687.trc
/app/oraadmn6/admin/SIGASP/udump/sigasp_ora_21687.trc
Oracle9i Enterprise Edition Release 9.2.0.4.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.4.0 - Production
ORACLE_HOME = /app/oraadmn6/product/9.2.0
System name: SunOS
Node name: cdsv00jd
Release: 5.8
Version: Generic_108528-19
Machine: sun4u
Instance name: SIGASP
Redo thread mounted by this instance: 1
Oracle process number: 58
Unix process pid: 21687, image: oracle@cdsv00jd (TNS V1-V3)
*** 2005-10-26 15:25:55.494
*** SESSION ID:(60.2524) 2005-10-26 15:25:55.488
DEADLOCK DETECTED
Current SQL statement for this session:
DELETE FROM WMSYS.WM$WORKSPACE_SAVEPOINTS_TABLE WHERE WORKSPACE = :b1
----- PL/SQL Call Stack -----
object line object
handle number name
3927ac3e0 1145 package body SYS.LTADM
38dd4bf40 3421 package body SYS.LT
38dd4bf40 3286 package body SYS.LT
38dd4bf40 4507 package body SYS.LT
3920d4c00 1 anonymous block
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-0003002d-000083db 58 60 X 32 46 X
TX-00020004-00008db9 32 46 X 58 60 X
session 60: DID 0001-003A-0000094E session 46: DID 0001-0020-00001A99
session 46: DID 0001-0020-00001A99 session 60: DID 0001-003A-0000094E
Rows waited on:
Session 46: obj - rowid = 00001771 - AAABdxAABAAAFILAAE
(dictionary objn - 6001, file - 1, block - 21003, slot - 4)
Session 60: obj - rowid = 00001786 - AAABeGAABAAAFKSAAI
(dictionary objn - 6022, file - 1, block - 21138, slot - 8)
Information on the OTHER waiting sessions:
Session 46:
pid=32 serial=112 audsid=1728581 user: 0/SYS
O/S info: user: ri01516, term: SNWS00695019, ospid: 1716:1712, machine: SNAMRETEGAS\SNWS00695019
program: Ustation.exe
application name: Ustation.exe, hash value=0
Current SQL Statement:
UPDATE WMSYS.WM$WORKSPACES_TABLE SET PARENT_VERSION=:b1 WHERE PARENT_VERSION = :b2
End of information on OTHER waiting sessions.
===================================================
oraadmn6@cdsv00jd:SIGASP> more /app/oraadmn6/admin/SIGASP/udump/sigasp_ora_21757.trc
/app/oraadmn6/admin/SIGASP/udump/sigasp_ora_21757.trc
Oracle9i Enterprise Edition Release 9.2.0.4.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.4.0 - Production
ORACLE_HOME = /app/oraadmn6/product/9.2.0
System name: SunOS
Node name: cdsv00jd
Release: 5.8
Version: Generic_108528-19
Machine: sun4u
Instance name: SIGASP
Redo thread mounted by this instance: 1
Oracle process number: 13
Unix process pid: 21757, image: oracle@cdsv00jd (TNS V1-V3)
*** 2005-10-06 16:51:56.140
*** SESSION ID:(19.2048) 2005-10-06 16:51:56.134
DEADLOCK DETECTED
Current SQL statement for this session:
insert into TRATTI (FAC_TYPE, COD_GASD, TIPO_COND, STATO_FUN, CENTRO, LUN, DN, PRES_MAX, PRES_CPI, COD_SPE, LIVELLO_CIRC, ORD
INE_LIVELLO, VISIBILITA_STR, AUTOMATIZZAZIONE, mslink) values (1100, 45860, 2, 1, 'PI', 300, 450, 24, 70, 'PI047', 4, 1, 0, '
S', 2100000120)
----- PL/SQL Call Stack -----
object line object
handle number name
392cf1e80 82 package body SYS.DBMS_LOCK
392cf1e80 110 package body SYS.DBMS_LOCK
392d561f0 2055 package body SYS.LTADM
38dcbf928 352 package body SYS.LT_CTX_PKG
38d4dfb28 42 GISDBA.OVM_INSERT_3842
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-0000ab01-00000000 13 19 X 44 32 SX
UL-00000000-00000000 44 32 X 13 19 S
session 19: DID 0001-000D-000006DB session 32: DID 0001-002C-0000224D
session 32: DID 0001-002C-0000224D session 19: DID 0001-000D-000006DB
Rows waited on:
Session 32: obj - rowid = 0000AA54 - AAAAAAAAJAAAPi7AAA
(dictionary objn - 43604, file - 9, block - 63675, slot - 0)
Session 19: no row
Information on the OTHER waiting sessions:
Session 32:
pid=44 serial=1406 audsid=1556312 user: 118/GISDBA
O/S info: user: ri50000, term: SNWS01146378, ospid: 1876:1872, machine: SNAMRETEGAS\SNWS01146378
program: Ustation.exe
application name: Ustation.exe, hash value=0
Current SQL Statement:
UPDATE GISDBA.TRATTI_LT
SET ltlock =
sys.lt_ctx_pkg.checkngetlock(:b4, ltlock, nextver,
:b2, 0,'UPDATE'),
nextver = sys.lt_ctx_pkg.getNextVer(nextver,:b3,:b2)
WHERE ROWID = :b1
Thanks, Alessandra

Hi,
Do any of the versioned tables that you are using have RICs defined on them ? If so, you may find useful information regarding deadlocks in the following thread.
RIC in OWM - ORA-20171 deadlock detected ...
A deadlock will occur when 2 different sessions are waiting on a resource that has already been acquired by the other session.
The easiest example of this are multiple updates to the same table:
-- Session 1
SQL> update scott.test_tab set value=10 where id=1 ;
SQL> -- wait for session 2 to execute its first statement
SQL> update scott.test_tab set value=10 where id=2 ;
-- Session 2
SQL> update scott.test_tab set value=10 where id=2 ;
SQL> -- wait for session 1 to execute its first statement
SQL> update scott.test_tab set value=10 where id=1 ;
At this point 1 of the 2 sessions will fail due to a deadlock. Please note that a deadlock will not occur when 2 sessions simply update the same row. It needs to have already acquired a lock on a row that the other session will be updating.
The same principles can be applied to workspace manager. During each of the workspace operations(merge, remove, rollback, etc) we will acquire a lock on the current workspace and also the parent workspace in the case of remove and merge and a few other operations. If you set the auto_commit to false than those locks are retained until the session either commits or rolls back.
So, if two session successfully perform a workspace operation without committing, and then each of them tries to do another workspace operation which requires the lock held by the other session, then a deadlock will occur. This could also happen from a combination of dmls and workspace operations if you do not commit between them.
It is hard to say from the description that you gave exactly what is happening in your case. It will depend on when the commits are occurring and if you set auto_commit to false during any workspace operations. If you have a simple testcase that is able to show the deadlock occurring, then I would be glad to look at it and make any further recommendations. I would also suggest to upgrade to the latest version of workspace manager(9.2.0.5.1) if you have not already done so. You can find your current version by querying the wm_installation view. The latest version of workspace manager is always available on Metalink.
Regards,
Ben

Cost Manager Concurrent req failed due to ORA-00060:

Hi
We are using Oracle Applications E-Business suite 11.5.9. OS HP-UX
Cost Manger is an scheduled concurrent program which was error out thrice scince today morning with the following error.
Cause: cmlmcm() failed due to ORA-00060: deadlock detected while waiting for resource.
I found no dead lock occurred. I don't know why it happend so.
Please help me out on this issue.
tokala
Edited by: Neosatish on Oct 20, 2008 1:38 PM

Could you suggest me the method to find out the scheduled concurrent request in specific time period. Or How to find out the the scheduled time for a concurrent program.Run the following query:
SQL> select *
from fnd_concurrent_requests
where status_code in ('Q','I')
and hold_flag = 'N';Note: 170107.1 - How to Determine Scheduled Concurrent Requests
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=170107.1

How to avoid Dead Lock?

Hi All,
When I am trying to execute my procedure, sometimes it's successful but sometimes it's terminated because of Deadlock. I know this happened due to multiple sessions are waiting for data locked by each other, resulting in all the sessions being blocked. But how can this be avoided? Please suggest something.
Regards,
BS

Did you check the Trace files for the Deadlocking statements?
The trace file shall show the deadlocking Statements and Sessions:
*** 2012-08-09 11:13:31.767
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-00090017-00000b9b        36      22     X             31     137           X
TX-00060008-00000b59        31     137     X             36      22           X
session 22: DID 0001-0024-0000082C     session 137: DID 0001-001F-00002362
session 137: DID 0001-001F-00002362     session 22: DID 0001-0024-0000082C
Rows waited on:
Session 22: obj - rowid = 00012BF8 - AAASv4AABAAAY6pAAC
(dictionary objn - 76792, file - 1, block - 102057, slot - 2)
Session 137: obj - rowid = 00012BF8 - AAASv4AABAAAY6pAAD
(dictionary objn - 76792, file - 1, block - 102057, slot - 3)
----- Information for the OTHER waiting sessions -----
Session 137:
sid: 137 ser: 26538 audsid: 198923 user: 91/PURVESH flags: 0x45
pid: 31 O/S info: user: SYSTEM, term: **********, ospid: 1264
    image: ORACLE.EXE (SHAD)
client details:
    O/S info: user: Purvesh.Kulkarni, term: UNKNOWN, ospid: 5696
    machine: *********** program: SQL Developer
    application name: SQL Developer, hash value=1012150930
current SQL:
update test_table set col = '2D' where pk_col = 4
----- End of information for the OTHER waiting sessions -----
Information for THIS session:
----- Current SQL Statement for this session (sql_id=d3j1vvv24hbv9) -----
update test_table set col = 'CC' where pk_col = 3
===================================================You might be able to track the records based on ROWIDs listed in the Trace files.
Trace file information can be found in Alert Log :- {\diag\rdbms\orcl\orcl\alert} text like 'ORA-00060: Deadlock detected. More info in file d:************\diag\rdbms\orcl\orcl\trace\orcl_ora_3888.trc.'
I guess this might provide some help along with the pointers posted by others.

ORA-00060

Hi,
Using Oracle 8.1.7 and JDBC driver of Oracle I am getting a
java.sql.SQLException: ORA-00060: deadlock detected while waiting for
resource
Strangely this happens during a insert of a row. No updates are going
on as far as I know. All I am doing is batch a whole bunch of prepared
statements for inserts into a table.
Any suggestions will be greatly appreciated,
Thanks,
Aswin.

Yes different WLS threads are executing transactions. No other clients are
working.
Slava Imeshev wrote:
So is it possible that the code is executed from different
threads (transactions)? While other clients are working?
Slava
"Aswin Dinakar" <[email protected]> wrote in message
news:[email protected]..
Plain JDBC calls.
Slava Imeshev wrote:
Hi Aswin,
Inserts locks db pages, too. Do you use EJBs or plain JDBC calls?
Regards,
Slava Imeshev
"Aswin Dinakar" <[email protected]> wrote in message
news:[email protected]..
Hi,
Using Oracle 8.1.7 and JDBC driver of Oracle I am getting a
java.sql.SQLException: ORA-00060: deadlock detected while waiting for
resource
Strangely this happens during a insert of a row. No updates are going
on as far as I know. All I am doing is batch a whole bunch of
prepared
statements for inserts into a table.
Any suggestions will be greatly appreciated,
Thanks,
Aswin.

Where can I get oracle dead lock information

Hi Experts,
two days back I find oracle dead lock information at SM21 log file but when I checked today the old data was over written by new data.
Where can I find oracle dead lock information other than SM21? can anyone please help
Thanks in advance
Regards
Veera
Edited by: Veerab on Apr 27, 2011 8:22 AM

Hi,
Have you refered [SAP Note 84348 - Oracle deadlocks, ORA-00060 |https://service.sap.com/sap/support/notes/84348]? It contains good detailed description about possible oracle deadlock situations and analysis.
Along with the trace file generated by oracle (at directory /oracle/<SID>/saptrace/usertrace/), You can get historical information from alert<SID>.log file located at /oracle/<SID>/saptrace/background/.
In alert<SID>.log file the deadlock situation is written with deadlock graph at the time of occurances.
Regards,
Bhavik G. Shroff

Ora-00060 message is not showing up in oem

I am configuring OEM to monitor log.xml, but it is not giving any alerts about the ora-00060 i am creating.
I am using grid control 10.2.0.5 and a 10.2.0.5 agent and a 10.2.0.1 database.
First i didn't get any respons and couldn't the last 50 lines. But for that i copied the ojdl.jar and the ojdl2.jar from the database oracle home to the agent10g/sysman/jlib directory. After that the tail went ok. But still no warnings/alerts in OEM.
I thoughed it would be picked up under the metric "Generic Operational Error", so i configured a critical threshold as Matches .* and for "Generic Operational Error Status" >0
Could anyone help me with this? Thanks

Hi Eric, thanks for the reply
I have seen the first note you gave me. I copied the files from the db-home to the agent-home and that solved the problem of not being able to see the tail of the alert-file or log.xml in OEM.
But when i create a dead-lock and a ora-00060, it is showing up in the tail of the log n OEM. But no warnings/alerts are generated.
I do think i have the right Metrics in place. In 11G there is no Metric "Generic Alert Log Error", so i have to get the right one for this ora-00060. I thoughed the ora-00060 would be catched by the metric "Generic Operational Error", so i used this one. But still no warning/alert in OEM.
So i am wondering were to look next, to see where it goes wrong. Or what i am doing wrong?

ORA-00060 dead lock happen on R12 demo database

Similar Messages

Maybe you are looking for