While waiting for replacement camera part for 40 days. my k910 has speaker failure.:(

What a piece of crap.. My k910 start speaker failure while i'm waiting camera replacement part.. Call speaker is ok but the media speaker ia totally dead... This is my problemfull phone i've ever had.. My past a706 and s920 of my wife are problemless...
Solved!
Go to Solution.

Luckily after tried to push both of up and down volume button the speaker actived again..

Similar Messages

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

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

How to overcome thisORA-00060: deadlock detected while waiting for resource

Hi ,
I have table name problems(prom_number,prom_relation,prom_impact,prom_prom_number)
Now from oracle form raltion can be set.
parent and chil relation can be set from the form
for ex
first suppose row=1 prom_number=1 is set as parent.
so the tabl is updated as prom_+relation='PARENT'
so after first updation values are
prom_number=1,prom_impact='xxx',prom_relation='PARENT' prom_prom_number=null
now in form level the 2 row which is set as child is update as follow
prom_number=2,prom_impact='yyy',prom_relation='CHILD' prom_prom_number=1
Now my requirment is after the 2nd row is updated the prom_impact of 2 row should be pusehd to row=1 which has the pirom_relation as ='PARENT.
the problem is i dont have the fmb of form so i cant do any changes in the form.
So i have written a trigger which fires when row2 is updated it picks the prom_impact value and trys to push it in row=1 with prom_number=1
however since in form level the table has not been committed it displays the following error
ORA-00060: deadlock detected while waiting for resource
So how can we overcome this error.
the trigger i have written is given below.
So how can we resolve thsis issue.
CREATE OR REPLACE TRIGGER Parent_Child_Impact_Trg
AFTER UPDATE OF prom_relation,prom_prom_number
ON PROBLEMS
REFERENCING NEW AS NEW OLD AS OLD
FOR EACH ROW
Version History:9.2.8.1
(format: version, date, developer, description)
1.0, 19-Dec-2008, Tanmoy Kr Moulik The "Impact" of Paren fault ticket
will be changed upon manual creation of Parent Child relation
Rules:
1.0     Upon manual creation of new Parent-Child fault relation, the 'Fault Impact' of
Child fault will be auto updated in the parent fault, if the parent fault impact matches
with the attached list(Non Serve Affeect or Threat) or the impact of Parent Fault is blank (null).
2.0     In case, the parent fault have fault impact matches with the attached list
(service affect), then its impact is not changed while making the relationship.
DECLARE
PRAGMA autonomous_transaction;
ecode NUMBER;
emesg VARCHAR2(200);
--BEGIN
-- NULL;
CURSOR c1--(v_prom_num NUMBER)
IS
SELECT PROM_IMPACT,prom_number FROM PROBLEMS WHERE prom_number=:NEW.prom_prom_number;
v_prom_imp VARCHAR2(30) DEFAULT NULL;
v_prom_imp_p1 NUMBER DEFAULT 0;
v_prom_imp_p2 NUMBER DEFAULT 0;
v_prom_num NUMBER;
BEGIN
IF :NEW.PROM_RELATION='CHILD' AND :NEW.PROM_PROM_NUMBER IS NOT NULL THEN
--dbms_output.put_line(1);
--INSERT INTO TEMP_PROM VALUES(:NEW.prom_number,:NEW.prom_prom_number,:NEW.prom_impact,:NEW.prom_relation);
--COMMIT;
OPEN c1;--(:NEW.prom_prom_number);
FETCH c1 INTO v_prom_imp,v_prom_num;
--INSERT INTO TEMP_PROM(PROM_NUM,PROM_IMPACT) VALUES(v_prom_num,v_prom_imp);
--COMMIT;
IF c1%NOTFOUND THEN
v_prom_imp:=NULL;
v_prom_num:=NULL;
END IF;
CLOSE c1;
v_prom_imp:=UPPER(v_prom_imp);
v_prom_imp_p1:=INSTR(v_prom_imp,'NON');
v_prom_imp_p2:=INSTR(v_prom_imp,'THREAT');
--INSERT INTO TEMP_PROM(PROM_NUM) VALUES(v_prom_imp_p1);
--INSERT INTO TEMP_PROM(PROM_NUM) VALUES(v_prom_imp_p2);
--COMMIT;
IF v_prom_imp_p1>0 OR v_prom_imp_p2>0 THEN
IF :NEW.prom_impact IS NOT NULL THEN
/*BEGIN
INSERT INTO TEMP_PROM(PROM_NUM,PROM_PROM_NUMBER,prom_impact,PROM_RELATION) VALUES(:NEW.prom_number,:NEW.prom_prom_number,:NEW.prom_impact,:NEW.prom_relation);
COMMIT;
EXCEPTION WHEN OTHERS THEN
INSERT INTO TEMP_PROM(prom_impact,PROM_RELATION) VALUES('failed1'||ecode,emesg);
COMMIT;
END;
BEGIN
COMMIT;
--INSERT INTO PROBLEMS(prom_number,PROM_REPORTED,PROM_REPORTEDBY,PROM_PRIORITY,PROM_DESCRIPTION,PROM_EMPE_ID,PROM_WORG_NAME,PROM_CREATED,PROM_CWORG_NAME)
-- VALUES(50000000,SYSDATE,'TAN',1,'DASD','CLARITY','CLARITY',SYSDATE,'CLARITY');
UPDATE PROBLEMS SET PROM_IMPACT=:NEW.PROM_IMPACT WHERE prom_number=:NEW.prom_prom_number;
COMMIT;
EXCEPTION WHEN OTHERS THEN
     ecode := SQLCODE;
emesg := SQLERRM;
COMMIT;
BEGIN
     UPDATE PROBLEMS SET PROM_IMPACT=:NEW.PROM_IMPACT WHERE prom_number=:NEW.prom_prom_number;
     EXCEPTION WHEN OTHERS THEN
     INSERT INTO TEMP_PROM(prom_impact,PROM_RELATION) VALUES('failed'||ecode,emesg);
     END;
--INSERT INTO TEMP_PROM(prom_impact,PROM_RELATION) VALUES('failed'||ecode,emesg);
COMMIT;
-- EXCEPTION WHEN OTHERS THEN*/
     NULL;
     END;
     --END;
--END;
END IF;
     /*BEGIN
     INSERT INTO TEMP_PROM(PROM_NUM,PROM_IMPACT) VALUES(:NEW.prom_prom_number,:NEW.prom_impact);
     COMMIT;
EXCEPTION WHEN OTHERS THEN
     INSERT INTO TEMP_PROM(prom_impact) VALUES('failed1');
     NULL;
     END;
--NULL;
-- END;
--COMMIT;
--END;
/* BEGIN
INSERT INTO TEMP_PROM(PROM_NUM,PROM_IMPACT) VALUES(:NEW.prom_prom_number,:NEW.prom_impact);
EXCEPTION WHEN OTHERS THEN
--INSERT INTO TEMP_PROM(prom_impact) VALUES('failed');
NULL;
END;
COMMIT;
--COMMIT;
/* ELSIF v_prom_imp_p2>0 THEN
-- v_prom_imp_p2
IF :NEW.prom_impact IS NOT NULL THEN
BEGIN
UPDATE PROBLEMS SET PROM_IMPACT=:NEW.PROM_IMPACT WHERE prom_number=:NEW.prom_prom_number;
EXCEPTION WHEN OTHERS THEN
BEGIN
     ecode := SQLCODE;
emesg := SQLERRM;
--BEGIN
INSERT INTO TEMP_PROM(prom_impact,PROM_RELATION) VALUES('failed'||ecode,emesg);
COMMIT;
--EXCEPTION WHEN OTHERS THEN
     NULL;
     END;
NULL;
END;
COMMIT;
BEGIN
INSERT INTO TEMP_PROM(PROM_NUM,PROM_IMPACT) VALUES(:NEW.prom_prom_number,:NEW.prom_impact);
EXCEPTION WHEN OTHERS THEN
NULL;
END;
COMMIT;*/
--UPDATE PROBLEMS SET PROM_IMPACT=:NEW.PROM_IMPACT WHERE prom_number=:NEW.prom_prom_number;
-- COMMIT;
-- END IF;
END IF;
END IF;
EXCEPTION WHEN OTHERS THEN
INSERT INTO TEMP_PROM(prom_impact,PROM_RELATION) VALUES('failed2'||ecode,emesg);
COMMIT;
NULL;
END;
/

Please do not take this the wrong way, my intention is not to be insulting, but from reading what you've posted I have no idea what you are doing or in what version of what product(s).
What I can tell you, though, is that your explicit cursor declarations with explicit OPEN and FETCH have no business in your code. Neither do incremental commits belong in any code. Nor does the following:
EXCEPTION WHEN OTHERS THEN
INSERT INTO TEMP_PROM(prom_impact,PROM_RELATION) VALUES('failed2'||ecode,emesg);
COMMIT;
NULL;belong in any code. What is NULL doing there? And why are there any commits in your trigger? Your use of PRAGMA AUTONOMOUS TRANSACTION to allow these commits is similarly unexplainable. It is no wonder you are getting deadlocks.
You need to push away from the keyboard and take SQL and PL/SQL courses and learn the basics. While looking for a good course in your area get a copy of any of Tom Kyte's books and start reading it and practicing with the examples.

Trigger error -deadlock detected while waiting for resource

with table1 as (
select '1' no,'1' id, 'N' flag,'' result from dual union all
select '2' no,'1' id, 'N' flag,'B' result from dual union all
select '3' no,'1' id, '' flag,'B' result from dual union all
select '4' no,'2' id, 'N' flag,'B' result from dual union all
select '5' no,'2' id, 'N' flag,'B' result from dual
select * from table1
I need to write a trigger with the condition that if Flag is set to 'Y', then all the values for the field 'result' for that particular ID should set a 'A'.
For the above table if I run the below query
update table1
set flag= 'Y' where no =1
The trigger result should be
with table1 as (
select '1' no,'1' id, 'Y' flag,'A' result from dual union all
select '2' no,'1' id, 'N' flag,'A' result from dual union all
select '3' no,'1' id, '' flag,'A' result from dual union all
select '4' no,'2' id, 'N' flag,'B' result from dual union all
select '5' no,'2' id, 'N' flag,'B' result from dual
select * from table1
I wrote the trigger as below...
CREATE OR REPLACE TRIGGER test
BEFORE UPDATE
ON table1 for each row
DECLARE
PRAGMA AUTONOMOUS_TRANSACTION;
BEGIN
if :new.flag = 'Y' then
update table1
set result = 'A'
where id = :new.id ;
commit;
end if;
end;
but giving follwing error.
ORA-00060: deadlock detected while waiting for resource
ORA-06512: at "test"
ORA-04088: error during execution of trigger 'test'
Please help to correct my trigger.

# Firstly you cannot define trigger using on subquery clause - WITH. e.g. table1.
# You might have used a trick to use PRAGMA AUTONOMOUS TRANSACTION to isolate trigger transaction from the main transaction but the deadlock will certainly going to occur as the main transaction already hold the row level lock which you are trying to update in trigger code.
# We will try to use common technique to capture all the ID whose flag is set as 'Y' in row level trigger and then in statement level trigger after update will update the column - "resut" for the ID.
This is very simple test code for demonostration.
CREATE TABLE T
NO      NUMBER,
ID      NUMBER,
FLAG    VARCHAR2(1),
RESULT VARCHAR2(1)
INSERT INTO T VALUES (1,1,'N',NULL);
INSERT INTO T VALUES (2,1,'N','B');
INSERT INTO T VALUES (3,1,'','B');
INSERT INTO T VALUES (4,2,'N','B');
INSERT INTO T VALUES (5,2,'N','B');
CREATE OR REPLACE PACKAGE PKG_T_MUTATING AS
TYPE IDTABTYPE IS TABLE OF T.ID%TYPE;
T_ID IDTABTYPE := IDTABTYPE();
PROCEDURE GET_UPDATE_ID(P_ID T.ID%TYPE);
PROCEDURE UPD_T;
END PKG_T_MUTATING;
CREATE OR REPLACE PACKAGE BODY PKG_T_MUTATING AS
PROCEDURE GET_UPDATE_ID(P_ID T.ID%TYPE) IS
BEGIN
T_ID.EXTEND;
T_ID(T_ID.COUNT) := P_ID;
DBMS_OUTPUT.PUT_LINE('T_ID ' || T_ID(T_ID.COUNT));
END GET_UPDATE_ID;
PROCEDURE UPD_T IS
V_ID PKG_T_MUTATING.IDTABTYPE := PKG_T_MUTATING.IDTABTYPE();
BEGIN
V_ID := V_ID MULTISET UNION DISTINCT T_ID;
IF V_ID.COUNT > 0 THEN
FORALL i IN 1..V_ID.COUNT
   UPDATE T SET RESULT = 'A'
   WHERE ID = V_ID(i);
END IF;
-- Cleanup
V_ID.DELETE;
T_ID.DELETE;
EXCEPTION
WHEN OTHERS THEN
    DBMS_OUTPUT.PUT_LINE(DBMS_UTILITY.FORMAT_ERROR_STACK);
END UPD_T;
END PKG_T_MUTATING;
CREATE OR REPLACE TRIGGER TRG_TEST_BU
BEFORE UPDATE OF FLAG ON T FOR EACH ROW
WHEN (NEW.FLAG = 'Y')
BEGIN
pkg_t_mutating.get_update_id(:NEW.ID);
END;
CREATE OR REPLACE TRIGGER TRG_TEST_AU
AFTER UPDATE OF FLAG ON T
BEGIN
PKG_T_MUTATING.UPD_T;
END;
SQL>SELECT * FROM T;
        NO         ID FLAG       RESULT
         1          1 Y          A
         2          1 N          B
         3          1            B
         4          2 N          B
         5          2 N          B
SQL>UPDATE T SET FLAG = 'Y' WHERE NO = 1 AND ID = 1;
1 row updated.
SQL>SELECT * FROM T;
        NO         ID FLAG       RESULT
         1          1 Y          A
         2          1 N          A
         3          1            A
         4          2 N          B
         5          2 N          B
SQL>
{code}

Tryout of *current* version while waiting for CS3?

I'm an InDesign and Illustrator user who may be
picking up Dreamweaver (either individually or as part of one of
the new suites) when CS3 comes out. I'd like to try learning it at
home before I have to use it at work. I notice there's no Tryout
version, and that the Dreamweaver web site says that a Tryout
version will be available 6-8 weeks after CS3 is released.
Is there any way to get a hold of the
current version as a Tryout? That way I could learn how to
use it while waiting for the new version to arrive.
Thanks.

No. But I'll whip one up for you....
Always use document relative links unless you have a good
reason not to.
GOOD REASONS
1. Document relative links don't work
2. You are using include files that link to pages at a
variety of folder
locations in the site
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"DC_Eric" <[email protected]> wrote in message
news:[email protected]...
>
quote:
Originally posted by:
Newsgroup User
> > #included file is in a subdirectory but the files
that #include it
> > aren't,
> > so
> > the relative locations are off.
>
> Always use root relative links for things like this.
>
> Murray do you know of a post or have a reference when
one should use links
> relative to the site root vs relative to the document?
>
>
> --
> Murray --- ICQ 71997575
> Adobe Community Expert
> (If you *MUST* email me, don't LAUGH when you do so!)
> ==================
>
http://www.dreamweavermx-templates.com
- Template Triage!
>
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
>
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
>
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
> ==================
>
>
> "lom2" <[email protected]> wrote in
message
> news:[email protected]...
> > Thanks for everyone's replies. Yes I contacted
customer service and they
> > gave
> > me the link that DC_Eric provided. I'm playing with
Dreamweaver now.
> >
> > Good advice about learning the theory before the
tool, but I've done web
> > development before. I'm not a total noob. :-)
> >
> > Version 8 seems pretty slick. The only problem I'm
having is that the
> > Link
> > Checker thingy is screwing things up with a PHP
#include file because
> > the
> > #included file is in a subdirectory but the files
that #include it
> > aren't,
> > so
> > the relative locations are off.
> >
> > But I suppose I just need to read the manual. LOL.
> >
> > Thanks again.
> >
>
>
>
>
>
>

Request timed out while waiting for response!!

Hi All,
My scenario is PROXY to SOAP. I am getting below error while posting to WEBSERVICE.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
<ns1:stackTrace xmlns:ns1="http://xml.apache.org/axis/">Failed to deliver inbound WS message, code=503 and reason=Request timed out while waiting for response. at com.sonicsw.net.http.ws.WSHttpProtocolHandler$HttpInBrokerHandler.invoke(WSHttpProtocolHandler.java:833) at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32) at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83) at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:453) at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281) at com.sonicsw.net.http.ws.WSHttpProtocolHandler.sendToSOAPStack(WSHttpProtocolHandler.java:630) at com.sonicsw.net.http.ws.WSHttpProtocolHandler.dispatch(WSHttpProtocolHandler.java:537) at com.sonicsw.net.http.ws.WSHttpProtocolHandler.servicePost(WSHttpProtocolHandler.java:284) at com.sonicsw.net.http.ws.WSHttpProtocolHandler.service(WSHttpProtocolHandler.java:609) at com.sonicsw.net.http.HttpProtocolHandler.handle(HttpProtocolHandler.java:471) at progress.message.net.http.server.HttpConnectionHandler.handle(HttpConnectionHandler.java:170) at progress.message.net.https.server.SonicHttpsConnection.service(SonicHttpsConnection.java:156) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:981) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:831) at progress.message.net.https.server.SonicHttpsServer.handleConnection(SonicHttpsServer.java:449) at progress.message.net.https.server.SonicHttpsServer.handle(SonicHttpsServer.java:364) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)</ns1:stackTrace>
Any Idea ? Do I need to change anything in my SOAP Channel or BAsis should change the Time Parameter?
Thanks,
Pushkar Patel

Hi,
>>>>>>>Request timed out while waiting for response.
See the below link, it might be helpful to you for timed out issue.
[Link1|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c059d583-a551-2c10-e095-eb5d95e03747?quicklink=index&overridelayout=true]
Regards,
Rajesh

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

Getting deadlock detected while waiting for resource error for select Query.....

Hi all,
i am getting a below error whenever executing the below select query....
some times it will show dead lock detected while waiting for resource and terminated...
some times it executes and gives result..
but all the time it writes an alert to alert log
Plesae suggest how to resolve the issue..........
Thanks in advance
Env: Linux / Oracle 11.2.0.3.3
Error from alert log:
Errors in file /u01/oracle/oracle/diag/rdbms/bdrdb/bdrdb/trace/bdrdb_p017_6076.trc:
ORA-00060: deadlock detected while waiting for resource
ORA-10387: parallel query server interrupt (normal)
Trace file info... bdrdb_p017_6076.trc:
Trace file /u01/oracle/oracle/diag/rdbms/bdrdb/bdrdb/trace/bdrdb_p017_6076.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /u01/oracle/oracle/product/11.2.0/dbhome_1
System name:    Linux
Node name:      bdrdb.cteplindia.com
Release:        2.6.18-308.el5PAE
Version:        #1 SMP Fri Jan 27 17:40:09 EST 2012
Machine:        i686
Instance name: bdrdb
Redo thread mounted by this instance: 1
Oracle process number: 92
Unix process pid: 6076, image: [email protected] (P017)
*** 2013-11-04 23:18:57.915
*** SESSION ID:(423.59970) 2013-11-04 23:18:57.915
*** CLIENT ID:() 2013-11-04 23:18:57.915
*** SERVICE NAME:(bdrdb) 2013-11-04 23:18:57.915
*** MODULE NAME:() 2013-11-04 23:18:57.915
*** ACTION NAME:() 2013-11-04 23:18:57.915
*** 2013-11-04 23:18:57.915
DEADLOCK DETECTED ( ORA-00060 )
[Transaction Deadlock]
Deadlock graph:
                       ---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name          process session holds waits process session holds waits
PS-00000001-00000011        92     423     S             33     128     S     X
BF-2ed08c01-00000000        33     128     S             92     423     S     X
session 423: DID 0001-005C-00081126     session 128: DID 0001-0021-00067D23
session 128: DID 0001-0021-00067D23     session 423: DID 0001-005C-00081126
DEADLOCK DETECTED ( ORA-00060 )
[Transaction Deadlock]
Deadlock graph:
                       ---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name          process session holds waits process session holds waits
PS-00000001-00000011        92     423     S             33     128     S     X
BF-2ed08c01-00000000        33     128     S             92     423     S     X
session 423: DID 0001-005C-00081126     session 128: DID 0001-0021-00067D23
session 128: DID 0001-0021-00067D23     session 423: DID 0001-005C-00081126
Rows waited on:
Session 423: no row
Session 128: obj - rowid = 00021DC1 - AAAh3BAAVAAAQL/AAA
(dictionary objn - 138689, file - 21, block - 66303, slot - 0)
----- Information for the OTHER waiting sessions -----
Session 128:
sid: 128 ser: 46176 audsid: 1836857 user: 102/DBLOCAL
    flags: (0x8000041) USR/- flags_idl: (0x1) BSY/-/-/-/-/-
    flags2: (0x40009) -/-/INC
pid: 33 O/S info: user: oracle, term: UNKNOWN, ospid: 31611
    image: [email protected]
client details:
    O/S info: user: masked, term: masked, ospid: 5924:568
    machine: masked program: Toad.exe
    application name: TOAD background query session, hash value=526966934
current SQL:
    application name: TOAD background query session, hash value=526966934
current SQL:
SELECT DISTINCT B_FP_TEST.TEST_ID
FROM B_FP_TEST,
       B_USER_INFO,
       J_FP_INVESTIGATOR,
       L_TEST_STATUS,
       L_ATMS_TEST_TYPE,
       j_op_test_anml
WHERE     B_FP_TEST.TEST_ID = J_FP_INVESTIGATOR.TEST_ID
       AND B_FP_TEST.TEST_TYPE_ID = L_ATMS_TEST_TYPE.ATMS_TEST_TYPE_ID
       AND B_USER_INFO.B_USER_INFO_ID = J_FP_INVESTIGATOR.INVESTIGATOR_ID
       AND B_FP_TEST.STATUS_ID = L_TEST_STATUS.STATUS_ID
       AND B_FP_TEST.IS_DELETED = :"SYS_B_00"
       AND B_FP_TEST.TEST_NUM NOT IN (:"SYS_B_01", :"SYS_B_02", :"SYS_B_03")
       AND L_ATMS_TEST_TYPE.IS_DELETED = :"SYS_B_04"
       AND J_FP_INVESTIGATOR.is_pi = :"SYS_B_05"
       AND L_TEST_STATUS.STATUS IN (:"SYS_B_06", :"SYS_B_07", :"SYS_B_08")
       AND j_op_test_anml.test_id = B_FP_TEST.TEST_ID
----- End of information for the OTHER waiting sessions -----
*** 2013-11-04 23:18:57.916
dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x0, level=3, mask=0x0)
----- Error Stack Dump -----
ORA-00060: deadlock detected while waiting for resource
ORA-10387: parallel query server interrupt (normal)
----- SQL Statement (None) -----
Current SQL information unavailable - no cursor.
----- Call Stack Trace -----
calling              call     entry                argument values in hex
location             type     point                (? means dubious value)
More......
Query:
SELECT DISTINCT B_FP_TEST.TEST_ID
FROM B_FP_TEST,
       B_USER_INFO,
       J_FP_INVESTIGATOR,
       L_TEST_STATUS,
       L_ATMS_TEST_TYPE,
       j_op_test_anml
WHERE     B_FP_TEST.TEST_ID = J_FP_INVESTIGATOR.TEST_ID
       AND B_FP_TEST.TEST_TYPE_ID = L_ATMS_TEST_TYPE.ATMS_TEST_TYPE_ID
       AND B_USER_INFO.B_USER_INFO_ID = J_FP_INVESTIGATOR.INVESTIGATOR_ID
       AND B_FP_TEST.STATUS_ID = L_TEST_STATUS.STATUS_ID
       AND B_FP_TEST.IS_DELETED = 0
       AND B_FP_TEST.TEST_NUM NOT IN (1, 2, 99)
       AND L_ATMS_TEST_TYPE.IS_DELETED = 0
       AND J_FP_INVESTIGATOR.is_pi = 1
       AND L_TEST_STATUS.STATUS IN ('Scheduled', 'In-Progress', 'Completed')
       AND j_op_test_anml.test_id = B_FP_TEST.TEST_ID
       AND (   (j_op_test_anml.end_date BETWEEN TO_DATE ('28-Oct-2013') - 1
                                            AND TO_DATE ('04-Nov-2013') + 1)
            OR (j_op_test_anml.start_date BETWEEN TO_DATE ('28-Oct-2013') - 1
                                              AND TO_DATE ('04-Nov-2013') + 1)
            OR (TO_DATE ('28-Oct-2013') BETWEEN j_op_test_anml.start_date
                                            AND j_op_test_anml.end_date)
            OR (TO_DATE ('04-Nov-2013') BETWEEN j_op_test_anml.start_date
                                            AND j_op_test_anml.end_date))
       AND L_ATMS_TEST_TYPE.IS_DELETED = 0
       AND B_FP_TEST.DATASOURCE_ID = 9
Query Exp plan:
Plan hash value: 3398228788
| Id | Operation                                          | Name                | Rows | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |    TQ |IN-OUT| PQ Distrib |
|   0 | SELECT STATEMENT                                   |                     | 1501 |   102K| 1929   (1)| 00:00:24 |       |       |        |      |            |
|   1 | HASH UNIQUE                                       |                     | 1501 |   102K| 1929   (1)| 00:00:24 |       |       |        |      |            |
|   2 |   CONCATENATION                                    |                     |       |       |            |          |       |       |        |      |            |
|   3 |    PX COORDINATOR                                  |                     |       |       |            |          |       |       |        |      |            |
|   4 |     PX SEND QC (RANDOM)                            | :TQ30005            |   241 | 16870 |   800   (1)| 00:00:10 |       |       | Q3,05 | P->S | QC (RAND) |
|* 5 |      HASH JOIN                                     |                     |   241 | 16870 |   800   (1)| 00:00:10 |       |       | Q3,05 | PCWP |            |
|   6 |       PX RECEIVE                                   |                     |   246 | 15990 |   797   (1)| 00:00:10 |       |       | Q3,05 | PCWP |            |
|   7 |        PX SEND HASH                                | :TQ30004            |   246 | 15990 |   797   (1)| 00:00:10 |       |       | Q3,04 | P->P | HASH       |
|* 8 |         HASH JOIN                                  |                     |   246 | 15990 |   797   (1)| 00:00:10 |       |       | Q3,04 | PCWP |            |
|   9 |          PX RECEIVE                                |                     |   573 | 29223 |   793   (1)| 00:00:10 |       |       | Q3,04 | PCWP |            |
| 10 |           PX SEND HASH                             | :TQ30003            |   573 | 29223 |   793   (1)| 00:00:10 |       |       | Q3,03 | P->P | HASH       |
|* 11 |            HASH JOIN                               |                     |   573 | 29223 |   793   (1)| 00:00:10 |       |       | Q3,03 | PCWP |            |
| 12 |             BUFFER SORT                            |                     |       |       |            |          |       |       | Q3,03 | PCWC |            |
| 13 |              PX RECEIVE                            |                     |       |       |            |          |       |       | Q3,03 | PCWP |            |
| 14 |               PX SEND BROADCAST                    | :TQ30000            |       |       |            |          |       |       |        | S->P | BROADCAST |
| 15 |                NESTED LOOPS                        |                     |       |       |            |          |       |       |        |      |            |
| 16 |                 NESTED LOOPS                       |                     |   485 | 20855 |   781   (0)| 00:00:10 |       |       |        |      |            |
| 17 |                  TABLE ACCESS BY GLOBAL INDEX ROWID| J_OP_TEST_ANML      |   485 | 10185 |   296   (0)| 00:00:04 | ROWID | ROWID |        |      |            |
|* 18 |                   INDEX RANGE SCAN                 | IDX$$_2D190001      |   485 |       |     4   (0)| 00:00:01 |       |       |        |      |            |
|* 19 |                  INDEX UNIQUE SCAN                 | FT_TEST_ID_PK       |     1 |       |     0   (0)| 00:00:01 |       |       |        |      |            |
|* 20 |                 TABLE ACCESS BY GLOBAL INDEX ROWID | B_FP_TEST           |     1 |    22 |     1   (0)| 00:00:01 | ROWID | ROWID |        |      |            |
| 21 |             PX BLOCK ITERATOR                      |                     | 70382 |   549K|    11   (0)| 00:00:01 |       |       | Q3,03 | PCWC |            |
|* 22 |              TABLE ACCESS FULL                     | J_FP_INVESTIGATOR   | 70382 |   549K|    11   (0)| 00:00:01 |       |       | Q3,03 | PCWP |            |
| 23 |          BUFFER SORT                               |                     |       |       |            |          |       |       | Q3,04 | PCWC |            |
| 24 |           PX RECEIVE                               |                     |     3 |    42 |     3   (0)| 00:00:01 |       |       | Q3,04 | PCWP |            |
| 25 |            PX SEND HASH                            | :TQ30001            |     3 |    42 |     3   (0)| 00:00:01 |       |       |        | S->P | HASH       |
|* 26 |             TABLE ACCESS FULL                      | L_TEST_STATUS       |     3 |    42 |     3   (0)| 00:00:01 |       |       |        |      |            |
| 27 |       BUFFER SORT                                  |                     |       |       |            |          |       |       | Q3,05 | PCWC |            |
| 28 |        PX RECEIVE                                  |                     |    30 |   150 |     3   (0)| 00:00:01 |       |       | Q3,05 | PCWP |            |
| 29 |         PX SEND HASH                               | :TQ30002            |    30 |   150 |     3   (0)| 00:00:01 |       |       |        | S->P | HASH       |
|* 30 |          TABLE ACCESS FULL                         | L_ATMS_TEST_TYPE    |    30 |   150 |     3   (0)| 00:00:01 |       |       |        |      |            |
| 31 |    NESTED LOOPS                                    |                     |       |       |            |          |       |       |        |      |            |
| 32 |     NESTED LOOPS                                   |                     |     3 |   210 |   329   (1)| 00:00:04 |       |       |        |      |            |
| 33 |      NESTED LOOPS                                  |                     |     3 |   195 |   329   (1)| 00:00:04 |       |       |        |      |            |
|* 34 |       HASH JOIN                                    |                     |     2 |   114 |   325   (1)| 00:00:04 |       |       |        |      |            |
| 35 |        NESTED LOOPS                                |                     |       |       |            |          |       |       |        |      |            |
| 36 |         NESTED LOOPS                               |                     |     6 |   258 |   322   (1)| 00:00:04 |       |       |        |      |            |
| 37 |          PARTITION RANGE SINGLE                    |                     |     6 |   126 |   316   (1)| 00:00:04 |     7 |     7 |        |      |            |
|* 38 |           TABLE ACCESS FULL                        | J_OP_TEST_ANML      |     6 |   126 |   316   (1)| 00:00:04 |     7 |     7 |        |      |            |
|* 39 |          INDEX UNIQUE SCAN                         | FT_TEST_ID_PK       |     1 |       |     0   (0)| 00:00:01 |       |       |        |      |            |
|* 40 |         TABLE ACCESS BY GLOBAL INDEX ROWID         | B_FP_TEST           |     1 |    22 |     1   (0)| 00:00:01 | ROWID | ROWID |        |      |            |
|* 41 |        TABLE ACCESS FULL                           | L_TEST_STATUS       |     3 |    42 |     3   (0)| 00:00:01 |       |       |        |      |            |
|* 42 |       TABLE ACCESS BY INDEX ROWID                  | J_FP_INVESTIGATOR   |     1 |     8 |     2   (0)| 00:00:01 |       |       |        |      |            |
|* 43 |        INDEX RANGE SCAN                            | FI_TEST_ID_PK       |     1 |       |     1   (0)| 00:00:01 |       |       |        |      |            |
|* 44 |      INDEX UNIQUE SCAN                             | L_ATMS_TEST_TYPE_PK |     1 |       |     0   (0)| 00:00:01 |       |       |        |      |            |
|* 45 |     TABLE ACCESS BY INDEX ROWID                    | L_ATMS_TEST_TYPE    |     1 |     5 |     1   (0)| 00:00:01 |       |       |        |      |            |
| 46 |    PX COORDINATOR                                  |                     |       |       |            |          |       |       |        |      |            |
| 47 |     PX SEND QC (RANDOM)                            | :TQ20003            |       |       |            |          |       |       | Q2,03 | P->S | QC (RAND) |
| 48 |      NESTED LOOPS                                  |                     |       |       |            |          |       |       | Q2,03 | PCWP |            |
| 49 |       NESTED LOOPS                                 |                     |    33 | 2310 |   399   (2)| 00:00:05 |       |       | Q2,03 | PCWP |            |
|* 50 |        HASH JOIN                                   |                     |    33 | 2145 |   397   (2)| 00:00:05 |       |       | Q2,03 | PCWP |            |
| 51 |         PX RECEIVE                                 |                     |    78 | 3978 |   393   (1)| 00:00:05 |       |       | Q2,03 | PCWP |            |
| 52 |          PX SEND HASH                              | :TQ20002            |    78 | 3978 |   393   (1)| 00:00:05 |       |       | Q2,02 | P->P | HASH       |
|* 53 |           HASH JOIN                                |                     |    78 | 3978 |   393   (1)| 00:00:05 |       |       | Q2,02 | PCWP |            |
| 54 |            BUFFER SORT                             |                     |       |       |            |          |       |       | Q2,02 | PCWC |            |
| 55 |             PX RECEIVE                             |                     |       |       |            |          |       |       | Q2,02 | PCWP |            |
| 56 |              PX SEND BROADCAST                     | :TQ20000            |       |       |            |          |       |       |        | S->P | BROADCAST |
| 57 |               NESTED LOOPS                         |                     |       |       |            |          |       |       |        |      |            |
| 58 |                NESTED LOOPS                        |                     |    66 | 2838 |   382   (1)| 00:00:05 |       |       |        |      |            |
| 59 |                 PARTITION RANGE SINGLE             |                     |    66 | 1386 |   316   (1)| 00:00:04 |     7 |     7 |        |      |            |
|* 60 |                  TABLE ACCESS FULL                 | J_OP_TEST_ANML      |    66 | 1386 |   316   (1)| 00:00:04 |     7 |     7 |        |      |            |
|* 61 |                 INDEX UNIQUE SCAN                  | FT_TEST_ID_PK       |     1 |       |     0   (0)| 00:00:01 |       |       |        |      |            |
|* 62 |                TABLE ACCESS BY GLOBAL INDEX ROWID | B_FP_TEST           |     1 |    22 |     1   (0)| 00:00:01 | ROWID | ROWID |        |      |            |
| 63 |            PX BLOCK ITERATOR                       |                     | 70382 |   549K|    11   (0)| 00:00:01 |       |       | Q2,02 | PCWC |            |
|* 64 |             TABLE ACCESS FULL                      | J_FP_INVESTIGATOR   | 70382 |   549K|    11   (0)| 00:00:01 |       |       | Q2,02 | PCWP |            |
| 65 |         BUFFER SORT                                |                     |       |       |            |          |       |       | Q2,03 | PCWC |            |
| 66 |          PX RECEIVE                                |                     |     3 |    42 |     3   (0)| 00:00:01 |       |       | Q2,03 | PCWP |            |
| 67 |           PX SEND HASH                             | :TQ20001            |     3 |    42 |     3   (0)| 00:00:01 |       |       |        | S->P | HASH       |
|* 68 |            TABLE ACCESS FULL                       | L_TEST_STATUS       |     3 |    42 |     3   (0)| 00:00:01 |       |       |        |      |            |
|* 69 |        INDEX UNIQUE SCAN                           | L_ATMS_TEST_TYPE_PK |     1 |       |     0   (0)| 00:00:01 |       |       | Q2,03 | PCWP |            |
|* 70 |       TABLE ACCESS BY INDEX ROWID                  | L_ATMS_TEST_TYPE    |     1 |     5 |     1   (0)| 00:00:01 |       |       | Q2,03 | PCWP |            |
| 71 |    PX COORDINATOR                                  |                     |       |       |            |          |       |       |        |      |            |
| 72 |     PX SEND QC (RANDOM)                            | :TQ10003            |       |       |            |          |       |       | Q1,03 | P->S | QC (RAND) |
| 73 |      NESTED LOOPS                                  |                     |       |       |            |          |       |       | Q1,03 | PCWP |            |
| 74 |       NESTED LOOPS                                 |                     |    33 | 2310 |   399   (2)| 00:00:05 |       |       | Q1,03 | PCWP |            |
|* 75 |        HASH JOIN                                   |                     |    34 | 2210 |   397   (2)| 00:00:05 |       |       | Q1,03 | PCWP |            |
| 76 |         PX RECEIVE                                 |                     |    78 | 3978 |   393   (1)| 00:00:05 |       |       | Q1,03 | PCWP |            |
| 77 |          PX SEND HASH                              | :TQ10002            |    78 | 3978 |   393   (1)| 00:00:05 |       |       | Q1,02 | P->P | HASH       |
|* 78 |           HASH JOIN                                |                     |    78 | 3978 |   393   (1)| 00:00:05 |       |       | Q1,02 | PCWP |            |
| 79 |            BUFFER SORT                             |                     |       |       |            |          |       |       | Q1,02 | PCWC |            |
| 80 |             PX RECEIVE                             |                     |       |       |            |          |       |       | Q1,02 | PCWP |            |
| 81 |              PX SEND BROADCAST                     | :TQ10000            |       |       |            |          |       |       |        | S->P | BROADCAST |
| 82 |               NESTED LOOPS                         |                     |       |       |            |          |       |       |        |      |            |
| 83 |                NESTED LOOPS                        |                     |    66 | 2838 |   382   (1)| 00:00:05 |       |       |        |      |            |
| 84 |                 PARTITION RANGE SINGLE             |                     |    66 | 1386 |   316   (1)| 00:00:04 |     7 |     7 |        |      |            |
|* 85 |                  TABLE ACCESS FULL                 | J_OP_TEST_ANML      |    66 | 1386 |   316   (1)| 00:00:04 |     7 |     7 |        |      |            |
|* 86 |                 INDEX UNIQUE SCAN                  | FT_TEST_ID_PK       |     1 |       |     0   (0)| 00:00:01 |       |       |        |      |            |
|* 87 |                TABLE ACCESS BY GLOBAL INDEX ROWID | B_FP_TEST           |     1 |    22 |     1   (0)| 00:00:01 | ROWID | ROWID |        |      |            |
| 88 |            PX BLOCK ITERATOR                       |                     | 70382 |   549K|    11   (0)| 00:00:01 |       |       | Q1,02 | PCWC |            |
|* 89 |             TABLE ACCESS FULL                      | J_FP_INVESTIGATOR   | 70382 |   549K|    11   (0)| 00:00:01 |       |       | Q1,02 | PCWP |            |
| 90 |         BUFFER SORT                                |                     |       |       |            |          |       |       | Q1,03 | PCWC |            |
| 91 |          PX RECEIVE                                |                     |     3 |    42 |     3   (0)| 00:00:01 |       |       | Q1,03 | PCWP |            |
| 92 |           PX SEND HASH                             | :TQ10001            |     3 |    42 |     3   (0)| 00:00:01 |       |       |        | S->P | HASH       |
|* 93 |            TABLE ACCESS FULL                       | L_TEST_STATUS       |     3 |    42 |     3   (0)| 00:00:01 |       |       |        |      |            |
|* 94 |        INDEX UNIQUE SCAN                           | L_ATMS_TEST_TYPE_PK |     1 |       |     0   (0)| 00:00:01 |       |       | Q1,03 | PCWP |            |
|* 95 |       TABLE ACCESS BY INDEX ROWID                  | L_ATMS_TEST_TYPE    |     1 |     5 |     1   (0)| 00:00:01 |       |       | Q1,03 | PCWP |            |
Predicate Information (identified by operation id):
   5 - access("B_FP_TEST"."TEST_TYPE_ID"="L_ATMS_TEST_TYPE"."ATMS_TEST_TYPE_ID")
   8 - access("B_FP_TEST"."STATUS_ID"="L_TEST_STATUS"."STATUS_ID")
11 - access("B_FP_TEST"."TEST_ID"="J_FP_INVESTIGATOR"."TEST_ID")
18 - access("J_OP_TEST_ANML"."START_DATE">=TO_DATE(' 2013-10-27 00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND "J_OP_TEST_ANML"."START_DATE"<=TO_DATE(' 2013-11-05
              00:00:00', 'syyyy-mm-dd hh24:mi:ss'))
19 - access("J_OP_TEST_ANML"."TEST_ID"="B_FP_TEST"."TEST_ID")
20 - filter("B_FP_TEST"."DATASOURCE_ID"=9 AND "B_FP_TEST"."IS_DELETED"=0 AND "B_FP_TEST"."TEST_NUM"<>1 AND "B_FP_TEST"."TEST_NUM"<>2 AND
              "B_FP_TEST"."TEST_NUM"<>99)
22 - filter("J_FP_INVESTIGATOR"."IS_PI"=1)
26 - filter("L_TEST_STATUS"."STATUS"='Completed' OR "L_TEST_STATUS"."STATUS"='In-Progress' OR "L_TEST_STATUS"."STATUS"='Scheduled')
30 - filter("L_ATMS_TEST_TYPE"."IS_DELETED"=0)
34 - access("B_FP_TEST"."STATUS_ID"="L_TEST_STATUS"."STATUS_ID")
38 - filter("J_OP_TEST_ANML"."END_DATE">=TO_DATE(' 2013-10-27 00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND "J_OP_TEST_ANML"."END_DATE"<=TO_DATE(' 2013-11-05
              00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND (LNNVL("J_OP_TEST_ANML"."START_DATE">=TO_DATE(' 2013-10-27 00:00:00', 'syyyy-mm-dd hh24:mi:ss')) OR
              LNNVL("J_OP_TEST_ANML"."START_DATE"<=TO_DATE(' 2013-11-05 00:00:00', 'syyyy-mm-dd hh24:mi:ss'))))
39 - access("J_OP_TEST_ANML"."TEST_ID"="B_FP_TEST"."TEST_ID")
40 - filter("B_FP_TEST"."DATASOURCE_ID"=9 AND "B_FP_TEST"."IS_DELETED"=0 AND "B_FP_TEST"."TEST_NUM"<>1 AND "B_FP_TEST"."TEST_NUM"<>2 AND
              "B_FP_TEST"."TEST_NUM"<>99)
41 - filter("L_TEST_STATUS"."STATUS"='Completed' OR "L_TEST_STATUS"."STATUS"='In-Progress' OR "L_TEST_STATUS"."STATUS"='Scheduled')
42 - filter("J_FP_INVESTIGATOR"."IS_PI"=1)
43 - access("B_FP_TEST"."TEST_ID"="J_FP_INVESTIGATOR"."TEST_ID")
44 - access("B_FP_TEST"."TEST_TYPE_ID"="L_ATMS_TEST_TYPE"."ATMS_TEST_TYPE_ID")
45 - filter("L_ATMS_TEST_TYPE"."IS_DELETED"=0)
50 - access("B_FP_TEST"."STATUS_ID"="L_TEST_STATUS"."STATUS_ID")
53 - access("B_FP_TEST"."TEST_ID"="J_FP_INVESTIGATOR"."TEST_ID")
60 - filter("J_OP_TEST_ANML"."END_DATE">=TO_DATE(' 2013-11-04 00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND "J_OP_TEST_ANML"."START_DATE"<=TO_DATE(' 2013-11-04
              00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND (LNNVL("J_OP_TEST_ANML"."END_DATE">=TO_DATE(' 2013-10-27 00:00:00', 'syyyy-mm-dd hh24:mi:ss')) OR
              LNNVL("J_OP_TEST_ANML"."END_DATE"<=TO_DATE(' 2013-11-05 00:00:00', 'syyyy-mm-dd hh24:mi:ss'))) AND (LNNVL("J_OP_TEST_ANML"."START_DATE">=TO_DATE(' 2013-10-27
              00:00:00', 'syyyy-mm-dd hh24:mi:ss')) OR LNNVL("J_OP_TEST_ANML"."START_DATE"<=TO_DATE(' 2013-11-05 00:00:00', 'syyyy-mm-dd hh24:mi:ss'))))
61 - access("J_OP_TEST_ANML"."TEST_ID"="B_FP_TEST"."TEST_ID")
62 - filter("B_FP_TEST"."DATASOURCE_ID"=9 AND "B_FP_TEST"."IS_DELETED"=0 AND "B_FP_TEST"."TEST_NUM"<>1 AND "B_FP_TEST"."TEST_NUM"<>2 AND
              "B_FP_TEST"."TEST_NUM"<>99)
64 - filter("J_FP_INVESTIGATOR"."IS_PI"=1)
68 - filter("L_TEST_STATUS"."STATUS"='Completed' OR "L_TEST_STATUS"."STATUS"='In-Progress' OR "L_TEST_STATUS"."STATUS"='Scheduled')
69 - access("B_FP_TEST"."TEST_TYPE_ID"="L_ATMS_TEST_TYPE"."ATMS_TEST_TYPE_ID")
70 - filter("L_ATMS_TEST_TYPE"."IS_DELETED"=0)
75 - access("B_FP_TEST"."STATUS_ID"="L_TEST_STATUS"."STATUS_ID")
78 - access("B_FP_TEST"."TEST_ID"="J_FP_INVESTIGATOR"."TEST_ID")
85 - filter("J_OP_TEST_ANML"."END_DATE">=TO_DATE(' 2013-10-28 00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND "J_OP_TEST_ANML"."START_DATE"<=TO_DATE(' 2013-10-28
              00:00:00', 'syyyy-mm-dd hh24:mi:ss') AND (LNNVL("J_OP_TEST_ANML"."END_DATE">=TO_DATE(' 2013-11-04 00:00:00', 'syyyy-mm-dd hh24:mi:ss')) OR
              LNNVL("J_OP_TEST_ANML"."START_DATE"<=TO_DATE(' 2013-11-04 00:00:00', 'syyyy-mm-dd hh24:mi:ss'))) AND (LNNVL("J_OP_TEST_ANML"."END_DATE">=TO_DATE(' 2013-10-27
              00:00:00', 'syyyy-mm-dd hh24:mi:ss')) OR LNNVL("J_OP_TEST_ANML"."END_DATE"<=TO_DATE(' 2013-11-05 00:00:00', 'syyyy-mm-dd hh24:mi:ss'))) AND
              (LNNVL("J_OP_TEST_ANML"."START_DATE">=TO_DATE(' 2013-10-27 00:00:00', 'syyyy-mm-dd hh24:mi:ss')) OR LNNVL("J_OP_TEST_ANML"."START_DATE"<=TO_DATE(' 2013-11-05
              00:00:00', 'syyyy-mm-dd hh24:mi:ss'))))
86 - access("J_OP_TEST_ANML"."TEST_ID"="B_FP_TEST"."TEST_ID")
87 - filter("B_FP_TEST"."DATASOURCE_ID"=9 AND "B_FP_TEST"."IS_DELETED"=0 AND "B_FP_TEST"."TEST_NUM"<>1 AND "B_FP_TEST"."TEST_NUM"<>2 AND
              "B_FP_TEST"."TEST_NUM"<>99)
89 - filter("J_FP_INVESTIGATOR"."IS_PI"=1)
93 - filter("L_TEST_STATUS"."STATUS"='Completed' OR "L_TEST_STATUS"."STATUS"='In-Progress' OR "L_TEST_STATUS"."STATUS"='Scheduled')
94 - access("B_FP_TEST"."TEST_TYPE_ID"="L_ATMS_TEST_TYPE"."ATMS_TEST_TYPE_ID")
95 - filter("L_ATMS_TEST_TYPE"."IS_DELETED"=0)

Excellent piece of follow-up on my first suggestion.
I nearly made a comment about how the plan doesn't show Bloom filter pruning either - and then I realised why not. The plan you've shown us comes from Explain Plan with literal values present; the trace file shows bind variables with names that are generated when cursor_sharing is set to force or similar - so the run-time plan and the plan from explain plan are almost guaranteed to be different.
Oracle support will need you to supply the plan you get from trying to run the query and then making a call to dbms_xplan.display_cursor() - dbms_xplan in 10g | Oracle Scratchpad If you do this I think you'll find that the pstart/pstop columns contain entries like :BF0000, and you may even find operations link PX JOIN FILTER CREATE / PX JOIN FILTER USE
A couple of generic notes:
if a query does sufficient work to merit parallel execution, then it's usually better to supply the best possible information to the optimizer, which means using literals rather than bind variables - you could try executing the query with the hint /*+ cursor_sharing_exact */ to stop Oracle from turning your literals into binds; it might be the presence of bind variables that's making the optimizer choose a path that has to include bloom filter pruning in your case.
Where you have the to_date() call you've used a four-digit year - which is a very good thing and helps the optimizer - but it's also a good idea to include an explicit format string as well: with a four-digit year this probably won't make any difference, but it avoids any risk of ambiguity for the optimizer.
I made a comment about the P->S stage and bottlenecks - I spent a couple more minutes looking at the plan, and I see the optimizer has used concatentation: in effect it has run three query blocks one after the other and fed the results to the query co-ordinator - in this case the P->S would make no difference to the end-user response time there's always a final P->S to the coordinator, you just happen to have three of them.
Regards
Jonathan Lewis

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.

Client-Auth reports: HTTP4030: Timeout while waiting for client certificate

Hello,
I'm having problems with the certificate authentication in my Sun Java System Web Server Enterprise Edition 6.1: I have created an ACL in the SJWS that asks for a client certificate when the user goes to a specific URI:
acl "uri=/server1/myaction.do";
authenticate (user) {
method="ssl";
deny (all)
user = "admin";
It works great and, when the user goes to "/server1/myaction.do" (we are using Internet Explorer 7 as Web browser), the window for selecting the client certificate appears:
- If the user selects a certificate that doesn't require password, everything works fine.
- The problem comes when the certificate is configured in Internet Explorer for asking for a password every time it is accessed. Once the user has selected the password protected certificate, the window for typing the password appears, but if the user doesn't type it and click OK IN LESS THAN 5 SECONDS (I've timed it), the following messages appear in the SJWS logs:
[28/Nov/2007:09:25:05] failure ( 2055): for host 10.0.145.11 trying to GET /server1/myaction.do, Client-Auth reports: HTTP4030: Timeout while waiting for client certificate.
[28/Nov/2007:09:25:05] security ( 2055): HTTP4290: get_auth_user_ssl: client passed no certificate.
I tried to add the following two lines to the magnus.conf file of the SJWS, but nothing changed:
SSLClientAuthTimeout 240
AcceptTimeout 3600
Has anyone experienced something similar? Any little piece of advice would be greatly appreciated.
Thank you very much in advance,
Carlos.

This is fixed in Web Server 7.0 update 2. Please migrate/upgrade to Web Server 7.0 update 2. Sorry for the inconvenience.

Time out occurred while waiting for memory resources

Team,
I am have Microsoft SQL Server 2008 SP1( 10.0.2734.0) 64bit with application being SCCM 2007
I am getting below error in SQL error log ::
Error 8645: Severity 17, state 1
A time out occurred while waiting for memory resources to execute the query in resource pool ‘internal’. Re-run the query.
At first glance, i thought that it is issue of query not getting enough memory.
Searched on google but could not get way to resolve it or issue creating factor.
Chetan

Well,
Upgrade is what client is not willing to go for as of now.
They have rebooted the server and as of now, their SCCM application is working fine ( Not sure how reboot has solve the issue). We are not getting the above mentioned error also in SQL Log.
Looks like, rebooting server has cleared the memory jam.
Chetan
Restarting sql server service cleared buffer cache and any such query holding or requesting more memory so issue disappeared. You just delayed the issue not solved it. Next time dont reboot find out the cause . If you want to check whether your SQL
Server requires more memory have a look at below counters in link
http://social.technet.microsoft.com/wiki/contents/articles/22316.sql-server-memory-and-troubleshooting.aspx#How_to_test_that_your_SQL_server_is_facing_memory_crunch
If your say to business about what are drawbacks on running unsupported version I am sure they will apply SP3. There are loads of fixes and its quite possible your error may be related to any such fixed issue.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

RDS 2012 R2: A timeout (30000 milliseconds) was reached while waiting for a transaction response from the (name-of-service) service

Hi guys,
On a random base (daily, weekly) we're experiencing major log-in problems on our Windows Server 2012 R2 Remote Desktop Services farm. The VM's are hosted on Hyper-V 2008 hosts and we're not using Citrix techniques etc.
Users are reporting that they cannot log-in, the log-in sessions hangs with a blank screen when loading their user profile (e.g. Please Wait For The User Profile Service).
In the System event log of the server on which the user is logging on the following errors are shown:
Source:        Service Control Manager
Date:          23-12-2014 7:28:01
Event ID:      7011
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Description:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.
…and after 30 (or sometimes 60) seconds, the same error only another service (in random order):
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.
…and after exactly 30 seconds, the same error only another service:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UxmSms service.
etcetera, with the following errors:
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Netman service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the AudioEndPointBuilder service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WPDBusEnum service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the NlaSvc service.
The Portable Device Enumerator Service service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the TrkWks service.
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UmRdpService service.
These errors are logged continuously.
An administrator cannot solve this since he isn't able to login in as well (console or remotely), only a hard reset of the VM is possible to use the affected server again.
I took different steps to solve this problem without any success, like:
- Installing the latest Windows updates
- Removed unnecessary printer drivers, print monitors and print processors (no local printers/drivers are installed, only Remote Desktop Easy Printer driver is used)
- Searched different forum posts, but found only hotfixes for Windows Server 2008 R2.
Can someone please help me with this annoying problem?
Many thanks!!
EDIT:
Of course is increasing the time-out not really an option here... http://social.technet.microsoft.com/wiki/contents/articles/13765.event-id-7011-service-timeout.aspx

Hi Jeroentjuhh,
1)Do you see this problem on all VM's or only on Windows 2012 R2 server?
2)Are these VMs' in hyper-v cluster?
3)Do you see event id 56 or 50? Please see the below link if it helps you to resolve these events.
http://blogs.msdn.com/b/scstr/archive/2012/02/29/how-to-troubleshoot-the-terminal-server-security-layer-detected-an-error-in-the-protocol-stream-and-has-disconnected-the-client-client-ip-and-the-rdp-protocol-component-x-224-detected-an-error-in-the-protocol-stream-and-has-d.aspx
Thanks,
Umesh.S.K

JME 3.0 EA under Mac: Emulator 0 terminated while waiting for it to registe

Hello!
I downloaded JME SDK 3.0 from: http://java.sun.com/javame/downloads/sdk30.jsp.
After installing I opened it, created new MIDP Application with Hello MIDlet. When I try to run it, the emulator is starting (I see it in the dock), but after couple of seconds it closes and I get this message in IDE output:
*** Error ***
Failed to connect to device 0!
Reason:
Emulator 0 terminated while waiting for it to register!I tried to delete javame-sdk directory from my Library/Application Support dir, but that didn't help.
I am using 32bit Macbook under Snow Leopard. Can anyone help me to get this running?
Thanks!
Edited by: rkjunior on Oct 22, 2009 2:10 AM

Hi rkjunior,
sdk has been successfully run on 32bit Mac/Leopard.
I will instruct you how to get to initial state, run sdk once again and then pls send us some logs in order to track down the problem.
1. check that device-manager is not running
ps aux | grep device-manager.app
kill process if it is running
2. rm -rf ~/Library/Application\ Support/javame-sdk
3. cd /Applications/Java_ME_SDK_3.0.app/Contents/Resources/runtimes/cldc-hi-javafx/bin
run runMidlet
It shouldn't fail and should print out a message. If it doesn't fail pls continue with instructions below
4. cd /Applications/Java_ME_SDK_3.0.app/Contents/Resources/
run emulator: emulator -Xjam
Emulator should appear. If it crashes send us following log files.
~//Library/Application Support/javame-sdk/3.0_ea/log/device-manager.log
/Library/Application Support/javame-sdk/3.0_ea/work/5/device.log
-Tomas

MAX timed out while waiting for a driver

I am getting an error when starting MAX. the error is that MAX timed out while waiting for a driver (nidaqe plug-in). I have a PCI-GPIB card and an PCI-MXI-2 card in the PC. The operating system is Windows XP.
I am able to see both these cards under the Windows Device Manager>Hardware.
MAX version is 4.6.1f0
I have also installed NI-488.2 and NIVXI331 driver installed on the computer.
Any help will be appreciated.
Thank you.
vxiguy

Hi vxi_guy,
What you're seeing could be the result of a few different things. First, I would check to see if the NI Configuration Manger and NI Device Loader are running, as per this KB. Then, if that doesn't work, I would explore the solutions described in this KB. Please let me know if neither of those articles resolve the issue. Have a good one!
aNItaB
Applications Engineer
National Instruments
Digital Multimeters

While waiting for replacement camera part for 40 days. my k910 has speaker failure.:(

Similar Messages

Maybe you are looking for