ORA-0001 on dequeue?

In production every now and then we get an ORA-0001 error when dequeuing a message. We use:
1 Solaris 10
2 Oracle 10g
3 C++ application
4 PROC*C with dbms_aq package for queuing operations
5 Queues with XML payload
6 We handle a large volume of messages (1K/min).
Any clue why would a dequeue result in an ORA-0001 (unique constraint) error?

Hello,
No it is not an issue I have ever come across on dequeue. The only time I could imagine this happening is on enqueue if the MSGID is not unique. Only on AIX have i seen an issue related to ORA-1 on enqueue.
On dequeue your msgid has already been created and you are effectively just selecting out the message.
The only way I could you progressing this would be to set an errorstack on ORA-1 but that would be more trouble than it is worth unless you can be reasonably sure you can reproduce the issue within a small timeframe otherwise you will get lots of tracefiles for perfectly legitimate ORA-1 errors.
Thanks
Peter

Similar Messages

Reattempt of insert after a ORA-0001 unique constraint violation

Hi,
I'm inserting into a table. The primary key on this table is made up of the user id and a one-up transaction number. Unfortunately, I cannot change the design of this table.
Because I have to query the table to get the next transaction number before I insert into the table, I sometimes get a ORA-0001 (unique constraint violation) error because some other session grabbed the next transaction number and committed before I did.
To deal with this I retry the insert, that is, read the table again for the next tran number and insert. I allow for this up to 3 times. If after the third attempt I fail again, I rollback.
I'm seeing 3 records in the table.
So here are my questions: Do I need to rollback when I get the ORA-0001 error? I thought I wouldn't have to. If I do, why? The insert failed, how could the commit statement commit 3 records?
Thanks!

No, the userid and transaction numbers are not the same (combined) for each of the 3 rows.
Here is the logic to retry again when I get a ORA-0001:
PROCEDURE insert_record(
table1_rec_in IN table1%ROWTYPE,
tran_number OUT table1.trans_number%TYPE,
attempt_number IN PLS_INTEGER)
IS
next_tran_number table1.trans_number%TYPE;
BEGIN
SELECT NVL(MAX(trans_number), 0) + 1
INTO next_tran_number
FROM table1
WHERE userid = table1_rec_in.table1_userid;
INSERT INTO table1
(userid,
trans_number,
amount,
transdate)
VALUES
(table1_rec_in.userid,
next_tran_number,
table1_rec_in.amount,
SYSDATE);
tran_number := next_tran_number;
EXCEPTION
WHEN DUP_VAL_ON_INDEX THEN
IF attempt_number < 3
THEN
DECLARE
next_attempt_number PLS_INTEGER;
BEGIN
next_attempt_number := attempt_number + 1;
insert_record(
table1_rec_in,
tran_number,
next_attempt_number);
END;
ELSE
RAISE unable_to_insert_rec;
END IF;
WHEN OTHERS THEN
RAISE unable_to_insert_rec;
END;
I'm using recursion to try the insert again. Is this the source of my problems? I don't see it and can't reproduce it.

ORA--0001: Message -1 not found; product=RDBMS; facility=ORA

Hi All,
I am using pro*c to connect to DB. My application was working fine till today. All of a sudden without changing any application configuration I started getting error during connect.
Statement executed
EXEC SQL CONNECT :sqli_username IDENTIFIED BY :sqli_password USING :sqli_db_instance ;
All Bind variable populated correctly still getting following error.
ORA--0001: Message -1 not found; product=RDBMS; facility=ORA
I tried to debug and search on internet for problem however as you can see sqlca.sqlcode is negative value -0001 which is not mapped to logical oracle error.
I could see on oracle site
sqlca.sqlcode <0 - Means that Oracle did not execute the statement because of a database, system, network, or application error. Such errors can be fatal. When they occur, the current transaction should, in most cases, be rolled back.
But how will I understand what was exact reason for failure.
Any help or direction is very much appreciated ..
Thanks.

You probably want to make sure your $ORACLE_HOME is set correctly.
null

Need Help in converting LCR to UPDATE when ORA-0001 received during apply

Currently I have streams (one-way) set up between two sites (Site A and B).
Data is inserted at Site A from an application. There is a possibility that the row already exists at Site B with another set of values resulting in Apply getting failed with ORA-0001 error. I have the folllowing DML_HANDLER to update the row at Site B when a row exists in Site B.
++++++++++++++++++++++++
create or replace procedure dept_ora_001 ( in_any sys.anydata)
is
lcr sys.lcr$_row_record;
old_val sys.lcr$_row_list;
new_val sys.lcr$_row_list;
rc pls_integer;
cmd_type varchar2(100);
v_col_deptno sys.anydata;
v_val_deptno number ;
v_col_lastmodified sys.anydata;
v_val_lastmodified date;
v_curr_val_lastmodified date;
pExist number;
begin
rc := in_any.GetObject(lcr);
cmd_type := lcr.get_command_type();
v_col_deptno := lcr.get_value('NEW','DEPTNO');
v_col_lastmodified := lcr.get_value('NEW','LASTMODIFIED');
rc := v_col_deptno.getnumber(v_val_deptno);
rc := v_col_lastmodified.getdate(v_val_lastmodified);
if cmd_type = 'INSERT' then
select count(*) into pExist from scott.dept where deptno = v_val_deptno;
-- Row does not exist.. execute lcr to insert row
if pExist = 0 then
lcr.execute(true);
else
-- Row existis.. compare values of lastmodifed and change the lcr to UPDATE if New DEPT created at source.
select lastmodified into v_curr_val_lastmodified
from nbkl8xk.dept where deptno = v_val_deptno;
if (v_curr_val_lastmodified is null or
v_val_lastmodified > v_curr_val_lastmodified ) then
lcr.set_command_type('UPDATE');
lcr.set_values('OLD',lcr.get_values('NEW'));
lcr.execute(true);
end if;
end if;
end if;
end;
begin
dbms_apply_adm.set_dml_handler
( object_name => 'SCOTT.DEPT',
object_type => 'TABLE',
operation_name => 'INSERT',
error_handler => false,
user_procedure => 'STRMADMIN.DEPT_ORA_001'
end;
++++++++++++++++++++++++++++
The DML handler is getting fired correctly and it is changing the LCR into UPDATE. Now, I am receiving ora-1403 (no data found). This is because the OLD values do not match with the row at Site B. ( I am setting OLD_Values to New_Values in the DML_HANDLER)
To address this I created the following update_conflict_handler.
++++++++++++++++++
declare
v_cols dbms_utility.name_array;
begin
v_cols(1) := 'DEPTNO';
v_cols(2) := 'DNAME';
v_cols(3) := 'LOC';
v_cols(4) := 'LASTMODIFIED';
dbms_apply_adm.set_update_conflict_handler(
object_name => SCOTT.DEPT',
method_name => 'MAXIMUM',
resolution_column => 'LASTMODIFIED',
column_list => v_cols
end;
+++++++++++++++++++++
I am not getting any 1403 errors now. However, the row at Site B is not getting updated with the values at Site A.
Any help is appreciated.
Thanks

I fired the query, am not getting any output from dbms_output.put_line('..|USER_COUNTRY..');
Is that no data is reading or may be any reason else..
in this table store_id is the primary key ..
SQL> set serveroutput on
SQL> CREATE OR REPLACE PROCEDURE test(in_any sys.anydata) IS
2 lcr sys.lcr$_row_record;
3 rc pls_integer;
4 v_type varchar2(20);
5 col_1 sys.anydata;
6 col_2 sys.anydata;
7 lcr_usercountry varchar2(20);
8 lcr_storeid number;
9 TRANS varchar2(20);
10 store_id number;
11 USER_COUNTRY varchar2(20);
12
13 BEGIN
14 rc:=in_any.GetObject(lcr);
15 v_type:=lcr.get_command_type();
16 col_1:=lcr.get_value('NEW','USER_COUNTRY');
17 rc:=col_1.GetVarchar2(lcr_usercountry);
18 col_2:=lcr.get_value('NEW','STORE_ID');
19 rc:=col_2.getnumber(lcr_storeid);
20 select user_country into user_country from dev03.testrep1 where user_country=lcr_usercountry and store_id=lcr_storeid;
21 dbms_output.put_line('---------||USER_COUNTRY ||-----------');
22 END;
23 /
Procedure created.
Thanks for your help ....

SQL Error: ORA-12801: error signaled in parallel query server P012 ORA-0001

Dear all
We are in BI 7.0 and oracle 10.2.02 and OS AIX 5.3 and we are getting the ORA -12801 while attribute change run
and aggregates rollup.
plz help
Regards
Amiya Kumar

Hi...
Check SAP Note 934281 - No 'Star Transformation' for a Hierarchy Changerun......
Symptom
The SQL command of a hierarchy changerun is executed with a
PARALLEL hint under ORACLE, and the system therefore always accesses the fact table with a full tablescan although only a little may be read.
Other terms
Query, aggregate, realignment run, ORACLE, Parallel Hint, ORA-12801,
ORA-01652, start transformation, parallel hint
Reason and Prerequisites
The Parallel hint should only be set when the aggregate is built again,
but not with the delta realignment run. There was no check made in case of a hierarchy changerun. So hierarchy changerun was executed with the
parallel hint.
Solution
With the following code correction, the hierarchy changerun also adapts
to star transformation when an aggregate has delta changes.
BW3.0B
           Import Support Package 31 for Release 3.0B (BW3.0B Patch 31 or SAPKW30B31) into your BW system. The Support Package will be available when note 0872272 with the short text "SAPBWNews BW 3.0B Support Package 31", describing this Support Package in more detail, is released for customers.
BW3.1C (Content)
           Import Support Package 25 for Release 3.1C (BW3.1C Patch 25 or SAPKW31025) into your BW system. The Support Package will be available when note 0872274 with the short text "SAPBWNews BW 3.1C Support Package 25", describing this Support Package in more detail, is released for customers.
BW 3.50
           Import Support Package 17 for Release 3.50 (BW3.50 Patch 17 or SAPKW35017) into your BW system. The Support Package will be available when note 0872277 with the short text "SAPBWNews BW SP17 NetWeaver'04 Stack 17", describing this Support Package in more detail, is released for customers.
SAP NetWeaver 2004s BI
           Import Support Package 13 for SAP NetWeaver 2004s BI (BI-Patch 13 or SAPKW70013) into your BI system. The Support Package will be available when note 991093 with the short text "SAPBINews BI 7.0 SP13", describing this Support Package in more detail, is released for customers.
Regards,
Debjani.........
Edited by: Debjani Mukherjee on Oct 10, 2008 12:08 PM

How can I capture and re-present Oracle contraint/check/DML errors?

Hi,
New to APEX, I have a Designer/Web-PLSQL background.
In Designer I can define the messages that I want the user to see when check, constraint, etc. errors are generated by the application interaction with the database server (done through table API and the integration of the Designer generated screens).
In APEX, these types of errors all seem to show the default 'ORA' style message on an error page. How can I change these to 'human-readable' messages?
I'm obviously missing the trick that changes an ORA-0001 message referring to CUST_CODE_UK to something like 'This Code has already been assigned to another customer'? I want to use standard functionality, not really keen on creating my own DML packages for every table that needs to be accessed through a screen.

user8038482 wrote:
dear sir,
i have windows 7 and install oracle 10g,developer suite 10g 32 bit working everything fine but any forms trying to open giving errors oracle form designer stopted working check online sulition can you help get and send the like of patch file so i can download even i am able to download the patch file pls help i will be grateful for the same.
thanks you..
As'salamualikum, m z Islam
check this Oracle Forms Designer has stopped working/ How to apply Patchset 7047034 ?
Hope this works..
hamid
Mark correct/helpful to help others to get right answer(s).*

Capturing Oracle Error Messages

Hi when developing some applications, I come across some error messages that I would like to make custom error messages.
for example: ORA-00001: unique constraint (CREATE_USER.IC_ITEM_GENDERS_PK) violated
Is there a way to capture this message and then make a user friendly message. Any info. would be great.
Thanks

If you write your own after-submit processes, you can write an appropriate exception handler, something like
begin
exception when dup_val_on_index -- ORA-0001
then :P1_ERROR := 'Nice error message';
end;Then show some "Error" HTML region with &P1_ERROR. conditional upon P1_ERROR being not null.
AFAIK, there is no way to do this when the error is raised by the wizard-generated automatic DML or MRU processes. For that, you could try to put your error checking code in a Validation (and specify your nice error message). If the validation fails, the after-submit processes are not fired so the "ugly" error messages will not be seen by the user.
Hope this helps.

Error while saving invoice in payables

hai all,
I am getting an error like APP-SQLAP-10000: SQLERRM occurred in Maintain_DBI_Summary AP_AI_TABLE_HANDLER_PKG.INSERT_ROW........
while saving an invoice in Payables. Can any one help me on this error.
regards,
satya

Hi satya,
Send me the exact error message you got/
try with this
fact: Oracle Payables 11.5
fact: APXINWKB - Invoice Workbench
symptom: Unable to click into the Distributions button
symptom: APP-SQLAP-10000 ORA-0001: unique constraint (AP.AP_INVOICES_U1)
violated occured in AP_AI_TABLE_HANDLER_PKG.INSERT_ROW<-AP.INVOICES_PKG.
ISNERT_ROWS<-APXINWKB
with parameter (p_Rowid= ,p_invoice_id = 142061)
while performing the follwoing operation:
Insert into ap_invoices
change: NOTE ROLE:
The problem occurs during the insert into ap_invoices_all statement.
The error indicates that the problem is with the AP_INVOICES_U1 index.
This index looks at one column which is the invoice_id. The system will not
allow there to be more then one invoice_id.
cause: When clicking into the distributions button, the system is trying to
save the
invoice header. At this point, the system tries to assign an invoice_id to the
invoice. The invoice_id is being retrieved from the ap_invoice_s sequence.
If the next value in the sequence already exists in the AP_INVOICES_ALL table,
then the system will produce this error.
fix:
Run the following selects:
#1
select max(invoice_id)
from apps.ap_invoices_all;
#2
select ap.ap_invoices_s.nextval
from dual;
Update the nextval in the ap_invoices_s sequence to be greater then the max
invoice_id value in ap_invoices_all table.
plz let me know it works or not?
--Basava.S

Export and import error

Hi all,
our production is oracle 9.2.0.1.0 on windows which we want to migrate on windows server.i have taken full export of the database but it comes with warnings and tried 2 to 3 times the same with warning and while import full database i got the error without showing me import successfull without warning or import succesfull with warning, then i ahve taken the individual schema export, its come without warning and import successfull with warning.please give me assitant.quick response will be higly appreciated.thanks alot in advance.
the syntax and i issued are below
d:>exp system/passward file=xyz.dmp log=full.log full=y
result is :export successfull with warnings
on target database
d:>imp system/password file=xyz.dmp log=impfull.log ignore=y full=y
i get error without showing import successfull with warning or import successfull without warning
like
imp-0007
ora-0001 which says unique key constraint is voilated.
then i do individual scehma backup like below
d:>exp system/password file=username.dmp log=user.log owner=username
result export successfull without warning
on target database.
d:>imp system/password file=username.ldmp log=user1.log fromuser=username touser=uername
result import successfull with warnings

Hi,
imp-0007
ora-0001 which says unique key constraint is voilated.This means there is difference between index defination on source and target. You could either recreate the index or disable the index while importing and then check for duplicate.
Regards
Anurag Tibrewal.

Conditional validation - When field changed

APEX 4.2.1
Simple wizard-generated DML form on a table. Hidden numeric primary key (PK), displayed multi-column unique key (UK1,UK2); standard table design.
Combination of conditional readonly and editable page items. NOT EXISTS validation to replace ORA-0001 with a friendlier error message. Validation should fire only when key fields (UK1 or UK2) are changed. Changes to other fields on the record should be allowed.
But APEX server side conditions don't track item level changes. For instance, we can't say "Fire this validation only when P1_X or P1_Y are changed"
How would this sort of thing be done? By adding OnChange dynamic actions on all the page items of interest to set a hidden page item, save that to session state and refer to it in the validation's Condition?
Is this the right way to approach this?
Thanks

VANJ wrote:
APEX 4.2.1
Simple wizard-generated DML form on a table. Hidden numeric primary key (PK), displayed multi-column unique key (UK1,UK2); standard table design.
Combination of conditional readonly and editable page items. NOT EXISTS validation to replace ORA-0001 with a friendlier error message. Validation should fire only when key fields (UK1 or UK2) are changed. Changes to other fields on the record should be allowed.
But APEX server side conditions don't track item level changes. For instance, we can't say "Fire this validation only when P1_X or P1_Y are changed"
How would this sort of thing be done? By adding OnChange dynamic actions on all the page items of interest to set a hidden page item, save that to session state and refer to it in the validation's Condition?
Is this the right way to approach this?Not in 4.2 in my opinion. Drop the validation, let the DML process raise the ORA-00001 exception, and use the new error handling features to provide a user-friendly message.

Unique Constraint Error at Apply side

We have streams configured between two databases. Source database is of Version 9.2.0.3 and target database is of 9.2.0.4
I have a table TEST with primary key PK_TEST on column A.
Performed the following steps on the source database:
Step1:
insert into test values (1);
1 row inserted.
Total no of lcr's propagated : 1
Step2:
insert into test values (1);
ORA-00001: unique constraint (TEST_USER.PK_TEST)violated.
Total no of lcr's propagated : 1
Step 3:
Commit;
Total no of lcr's propagated : 1
On the source database, i have only one row in the TEST table but in the target schema iam getting "ORA-00001: unique constraint" error on applying the lcr's propagated from the source. If i remove the constraint from the target table then two rows are getting inserted in the target table rather only one rows should be inserted in the target table.
Total 3 lcr's are propagated from source to target. For Step2, 2 lcr's should be propagated but only one is propagating.
It looks strange but this is what happening in our environment. Has anyone faced this problem before? Please let me know how to solve this problem.

Hi,
I believe your problem is with the transaction.
1) First you insert a row
2) you try to insert it again, it fails
3) you commit your work
When propagated to your destination, the transaction does not commit because it failed in the second.
Try inserting, commit and inserting again. It should work that way. Or else you may need to write an error handler to ignore ORA-0001 errors and commit (which I don't think it is good practice).
Hope this helps,

Duplicate rows in workspace

One of my users made some "adjustments" (still not fully sure what he did) to a workspace in our production database. Another user then went into the same workspace and made over 100 changes. When attempting to merge, ORA-0001 unique constraint errors appeared. I was able to remove the duplicate rows from the table, but I am still receiving duplicate entries in the aux table. Due to the number of changes, they do not want to drop the workspace and start from scratch. Any idea as to how to remove the duplicate entries from the AUX table without messing up all of the workspaces?

Hi Ben, thank you for your response. Here is what I would like to try:
1. Use the ROWID to remove the duplicate rows (17 rows)
2. Export the remaining rows to a staging table then delete them from the table
3. Merge the workspace forcing all of the changes into the parent table
4. Option (a) Import the erred 17 rows and see if I still get the same AUX duplicate unique key errors
5. Option (b) Export the rows from another workspace and import them into the erred workspace
6. Option (c) Drop the workspace and re-create it. Have the user manually add the missing rows
Option C is a "can't find any other way around it" option. I think that I have a fighting chance with one of these options. I will put in a TAR if this doesn't work.

Inserts and locking

We have like 10 sessions trying to insert into a same table and we are experiencing heavy enq:TX waits (enq: TX - row lock contention). What I don't understand is why does the INSERTS have to wait for TX locks.
Can some one please clarify or provide some pointers on this.

Usually there are 2 senarios, insert could block others,
1. Waits for TX in mode 4 can also occur if a session is waiting due to potential duplicates in UNIQUE index. If two sessions try to insert the same key value thesecond session has to wait to see if an ORA-0001 should be raised or not.
2. Waits for TX in mode 4 is also possible if the session is waiting due to shared bitmap index fragment. Bitmap indexes index key values and a range of ROWIDs. Each entry in bitmap index can cover many rows in the actual table. If two sessions want to update rows covered by the same bitmap index fragment, then the second session waits for the first transaction to either COMMIT or ROLLBACK by waiting for the TX lock in mode 4

Auto generate Invoice Number

Dear All,
I want to auto generate inovice number. I did not want to handle this from sequences because I still did not understand/handle this, so kindly suggest an other best way to generate invoce number automatically through programitcally. I have three tables, one master table and two detail tables.
Thanks and regards,
Hassan

christian erlinger wrote:
what's the trouble with using sequences?!?
http://docs.oracle.com/cd/B28359_01/server.111/b28318/schema.htm#CNCPT611
http://docs.oracle.com/cd/B28359_01/server.111/b28310/views002.htm#ADMIN11796
the max+1 approach is a dangerous one, and will lead to unexplainable random occuring ora-0001...
http://asktom.oracle.com/pls/apex/f?p=100:11:0::::P11_QUESTION_ID:3379873654938
cheersOf course nothing is wront with sequences, but he/she is generating invoice-numbers, means there should be no gaps between the numbers -> sequences not usable for this problem
you definetely need a different approach, but have to take care! what happens if two people at the same time press commit in forms? both select e.g. 42 for the invoice-number, it will (hopefully you made unique contraints) crash with a UK-violation, so just put a select max+1 in pre-commit is not good enough.
I think best way to realize it is to make a table with one record that contains the last invoice-number, before every commit you select the record for update, if its already locked, wait or retry later the commit and increment in the invoice-number table is done when commiting the invoice itself.
Any flaws in this thought? Other suggestions?

Deadlock on a unique index?

I am trying to figure out what is exactly going on during this deadlock situation and i need some help. From the info
from the graph i figured that session 75 is waiting on row in a unique index. From what i am trying to figure out is
are the two sessions trying to insert the same key value and the second session has to wait to see if an ORA-0001 should be raised or not and a deadlock occurs?
Session 75: obj - rowid = 0001B54E - AAAbVOAASAABQ0SAAA
(dictionary objn - 111950, file - 18, block - 331026, slot - 0)
OWNER OBJECT_NAME OBJECT_TYPE
MULTI PK_SEGMENTMEMBER_1 INDEX
CREATE UNIQUE INDEX PK_SEGMENTMEMBER_1 ON SEGMENTMEMBER
(SEGMENTID, ENDUSERID)
--------Dumping Sorted Master Trigger List --------
Trigger Owner : MULTI
Trigger Name : RULE_CACHE
--------Dumping Trigger Sublists --------
trigger sublist 0 :
trigger sublist 1 :
Trigger Owner : MULTI
Trigger Name : RULE_CACHE
trigger sublist 2 :
trigger sublist 3 :
trigger sublist 4 :
Deadlock graph:
---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name process session holds waits process session holds waits
TX-000e0013-0015c871 20 11 X 33 75 S
TX-000b0000-0017d542 33 75 X 20 11 S
session 11: DID 0001-0014-0094ADA4 session 75: DID 0001-0021-003A6568
session 75: DID 0001-0021-003A6568 session 11: DID 0001-0014-0094ADA4
Rows waited on:
Session 11: no row
Session 75: obj - rowid = 0001B54E - AAAbVOAASAABQ0SAAA
(dictionary objn - 111950, file - 18, block - 331026, slot - 0)
----- Information for the OTHER waiting sessions -----
Session 75:
sid: 75 ser: 15873 audsid: 26563927 user: 95/MULTI flags: 0x41
pid: 33 O/S info: user: oracle, term: UNKNOWN, ospid: 13909
image: [email protected]
client details:
O/S info: user: jboss, term: unknown, ospid: 1234
machine: MULTI2.8020solutions.net program: JDBC Thin Client
application name: JDBC Thin Client, hash value=2546894660
current SQL:
MERGE INTO SEGMENTMEMBER A USING (SELECT id enduserid,
decode(MIN(nvl(ruleid, 0)), 0, NULL, min(ruleid)) ruleid,
segmentid
FROM temp_ids
GROUP BY id, segmentid) B
ON (A.ENDUSERID = B.ENDUSERID AND A.SEGMENTID = B.SEGMENTID)
WHEN NOT MATCHED THEN
INSERT ( A.ENDUSERID,A.RULEID, A.SEGMENTID)
VALUES ( B.ENDUSERID,B.RULEID, B.SEGMENTID)
----- End of information for the OTHER waiting sessions -----
Information for THIS session:
----- Current SQL Statement for this session (sql_id=9utn9atfhzsdz) -----
DELETE FROM RULE WHERE ID IN (SELECT ID FROM UTL_DELETE WHERE TABLENAME = 'RULE')
----- PL/SQL Stack -----
----- PL/SQL Call Stack -----
object line object
handle number name
0xeaaabbd0 20675 package body MULTI.MULTI_DELETE
0xeaaabbd0 20910 package body MULTI.MULTI_DELETE
0xccfa7ed0 1 anonymous block
===================================================
PROCESS STATE
Process global information:
process: 0x11b4d9e20, call: 0x11b892c78, xact: 0x117c891b8, curses: 0x11b610458, usrses: 0x11b610458
SO: 0x11b4d9e20, type: 2, owner: (nil), flag: INIT/-/-/0x00 if: 0x3 c: 0x3
proc=0x11b4d9e20, name=process, file=ksu.h LINE:11459, pg=0
(process) Oracle pid:20, ser:25, calls cur/top: 0x11b892c78/0x11b895a58
flags : (0x0) -
flags2: (0x0), flags3: (0x0)
intr error: 0, call error: 0, sess error: 0, txn error 0
intr queue: empty
ksudlp FALSE at location: 0
(post info) last post received: 0 0 150
last post received-location: kcb2.h LINE:3844 ID:kcbzww
last process to post me: 11b4e7160 41 0
last post sent: 0 0 26
last post sent-location: ksa2.h LINE:282 ID:ksasnd
last process posted by me: 11b4d1c20 1 6
(latch info) wait_event=0 bits=0
Process Group: DEFAULT, pseudo proc: 0x11b56ada0
O/S info: user: oracle, term: UNKNOWN, ospid: 15407
OSD pid info: Unix process pid: 15407, image: [email protected]
Dump of memory from 0x000000011B4B5110 to 0x000000011B4B5318

Thanks damorgan for helping me out. This deadlock appeared a couple of times already.
Here is the result of the view
OBJECT_NAME LOCK_TYPE MODE_HELD MODE_REQUESTED BLOCKING_OTHERS
TAB$ XR Null None Not Blocking
PROXY_ROLE_DATA$ RS Row-S (SS) None Not Blocking
ORA$BASE AE Share None Not Blocking
ORA$BASE AE Share None Not Blocking
ORA$BASE AE Share None Not Blocking
C_OBJ# CT Exclusive None Not Blocking
C_OBJ# Media Recovery Share None Not Blocking
I_OBJ# Media Recovery Share None Not Blocking
TAB$ Media Recovery Share None Not Blocking
CLU$ Media Recovery Share None Not Blocking
C_TS# Media Recovery Share None Not Blocking
I_TS# Media Recovery Share None Not Blocking
C_FILE#_BLOCK# Media Recovery Share None Not Blocking
I_FILE#_BLOCK# Media Recovery Share None Not Blocking
C_USER# Media Recovery Share None Not Blocking
I_USER# Media Recovery Share None Not Blocking
FET$ Media Recovery Share None Not Blocking
UET$ Media Recovery Share None Not Blocking
SEG$ Media Recovery Share None Not Blocking
UNDO$ Media Recovery Share None Not Blocking
TS$ Media Recovery Share None Not Blocking
I_SQL$TEXT_HANDLE Media Recovery Share None Not Blocking
ORA$BASE AE Share None Not Blocking
ORA$BASE AE Share None Not Blocking
I_OBJ# Temp Segment Row-X (SX) None Not Blocking
ORA$BASE AE Share None Not Blocking
ORA$BASE AE Share None Not Blocking
ORA$BASE AE Share None Not Blocking
ORA$BASE AE Share None Not Blocking
ORA$BASE AE Share None Not Blocking
ORA$BASE AE Share None Not Blocking
ORA$BASE AE Share None Not Blocking
ORA$BASE AE Share None Not Blocking
ORA$BASE AE Share None Not Blocking
ORA$BASE AE Share None Not Blocking
ORA$BASE AE Share None Not Blocking
ORA$BASE AE Share None Not Blocking
ORA$BASE AE Share None Not Blocking
ORA$BASE AE Share None Not Blocking
ORA$BASE AE Share None Not Blocking
ORA$BASE AE Share None Not Blocking
ORA$BASE AE Share None Not Blocking
ICOL$ Media Recovery Share None Not Blocking
COL$ Media Recovery Share None Not Blocking
ORA$BASE AE Share None Not Blocking
ORA$BASE AE Share None Not Blocking
USER$ Media Recovery Share None Not Blocking
SQLOBJ$ Media Recovery Share None Not Blocking
OBJ$ Media Recovery Share None Not Blocking
IND$ Media Recovery Share None Not Blocking
ORA$BASE AE Share None Not Blocking
ORA$BASE AE Share None Not Blocking
FILE$ Media Recovery Share None Not Blocking

ORA-0001 on dequeue?

Similar Messages

Maybe you are looking for