Oracle Error ORA 03123 (operation would block)

I get this error when I try to access data from a oracle sql clientt software tools sqldeveloper and TOAD
The strange thing is if I use Oracle SQL*plus, it works fine. This problem will be occuring only in VIS Oracle EBS R12.1 database 11.1.0.7.
In the database side i checked the locks and ran the gather schema stats didn't help.
In the client side.. I reinstalled the Oracle client 11g and sqldevelper 3.1 on Windows XP service pack 3. didn't help
The strange thing is from the sql develope when i ran
select * from fnd_user --- it runs forever and get erro ORA-3123 and freezes.
select USER_ID,USER_NAME from fnd_user - Works fine.
Please help on this.

>
Yes. i went through that .. didn't help.
>
Well it would have helped if you didn't ignore what Justin said in that link.
The message is telling you that if you do that operation it will block.
So your response is to try the operation anyway and the result is
>
select * from fnd_user --- it runs forever and get erro ORA-3123 and freezes.
>
Surprise - the operation blocked! Which is what 'it runs forever' means.
You need to determine what is holding the lock and resolve that issue.

Similar Messages

ORA-03123: operation would block

Hi ,
while application is running, if network connection to oracle server lost. I got the following Error Message 'ORA-03123:operation would block'. If I got this error message.Next Time when i tries to Open Recordset my application gives 'Access violation' Error in SQLExecute Call inside the PrepareandExecute method of CRecordset Calss and application crashes. I have no idea of why this error coming and the application crashing?. Please help to solve this issue.
Thanks & Regards,
Kannan Arumugam.
Mail id: [email protected]

Increasing the TEMP tablespace size should have no effect on your situation. If you are indeed issuing calls after the connection has been dropped, no configuration changes on the database could possibly have an effect on the situation.
Once the ODBC driver indicates that the connection has been lost, you need to make a new connection before doing anything else. The ODBC driver uses OCI (Oracle Call Interface) to actually communicate with the database, and OCI gets very unhappy if you try to do anything after a connection has been lost. The behavior is undefined in this situation-- you may see your ORA-03123 or any other error(s) before the eventual access violation.
Justin

ORA-22290: operation would exceed the maximum number of opened files or LOB

i am getting this error in a procedure.
ORA-22290: operation would exceed the maximum number of opened files or LOBs
22290, 00000, "operation would exceed the maximum number of opened files or LOBs"
// *Cause: The number of open files or LOBs has reached the maximum limit.
// *Action: Close some of the opened files or LOBs and retry the operation.
NAME TYPE VALUE
session_max_open_files integer 10
Procuedure:
CREATE OR REPLACE PROCEDURE WMSOWN."PROC_WMS_XML_READ"
P_EVENT_KEY IN VARCHAR2,
X_STATUS_MSG OUT VARCHAR2,
X_STATUS OUT NUMBER
)AS
l_parser dbms_xmlparser.Parser;
domdoc xmldom.DOMDocument;
nodelist XMLDOM.DOMNODELIST;
node XMLDOM.DOMNODE;
n_child XMLDOM.DOMNODE;
elements XMLDOM.DOMELEMENT;
name_node_map XMLDOM.DOMNAMEDNODEMAP;
parent_seg varchar2(4000);
tag_name_bkp varchar2(4000); -- LOOK OUT BRAD IS CODING AGAIN
chile_seg VARCHAR2(4000);
p_seg VARCHAR2(4000);
p_seg1 VARCHAR2(4000);
p_seg2 VARCHAR2(30);
p_int_name VARCHAR2(50);
col_value VARCHAR2(100):=NULL;
len1 NUMBER;
cnt NUMBER;
seg_id_bkp NUMBER; -- LOOK OUT BRAD IS CODING AGAIN
sequence_bkp NUMBER; -- LOOK OUT BRAD IS CODING AGAIN
prev_sequence NUMBER; -- LOOK OUT BRAD IS CODING AGAIN
prev_seq_set VARCHAR2(3); --brad coding
parent_id number; ---brad coding
valid_seg NUMBER; -- LOOK OUT BRAD IS CODING AGAIN
data_status VARCHAR2(10);
v_main_seg VARCHAR2(50);
v_seq_no NUMBER;
V_CLOBLOCATOR CLOB;
V_FILELOCATOR BFILE;
v_amount_to_load NUMBER;
dest_offset NUMBER := 1;
src_offset NUMBER := 1;
lang_context NUMBER := DBMS_LOB.DEFAULT_LANG_CTX;
warning NUMBER;
v_event_name USR_OUB_FILE_PROCESS_DETAILS.EVENT_NAME%TYPE;
v_file_name USR_OUB_FILE_PROCESS_DETAILS.FILE_NAME%TYPE;
DIRECTORY_PATH_INVALID EXCEPTION;
PRAGMA EXCEPTION_INIT(DIRECTORY_PATH_INVALID,-22285);
NO_PRIVILEGES EXCEPTION;
PRAGMA EXCEPTION_INIT(NO_PRIVILEGES,-22286);
INVALID_DIRECTORY EXCEPTION;
PRAGMA EXCEPTION_INIT(INVALID_DIRECTORY,-22287);
FILE_NOT_FOUND EXCEPTION;
PRAGMA EXCEPTION_INIT(FILE_NOT_FOUND,-22289);
P_DIRECTORY VARCHAR2(50) :='WMS_XML_DIR_OUB';
v_whid poldat_view.wh_id%type;
BEGIN
--NAME : PROC_WMS_XML_READ.PLS
--DESCRIPTION :
-- Procedure PROC_WMS_XML_READ search XML files from remote location.
-- Open,Parse and Read XML files. Store all XML values into tables.
-- Developed by Dharmesh Patidar(jw782)
-- History: New condition is added i.e. p_seg:=parent_seg to maintain PARENT and CHILD relationship
-- by Vishwanath Dubey(jl246) on 17-June-2011
-- BRAD_XML_DEBUG table removed for CLEANING Activity by DHARMESH PATIDAR(JW782) ON 29-JUNE-2011.
/*BLOCK FOR CAPTURING EVENT NAME BASED ON EVENT ID START*/
BEGIN
SELECT event_name,file_name,WAREHOUSE_ID
INTO v_event_name, v_file_name,v_whid
FROM usr_oub_file_process_details
WHERE event_id=p_event_key
AND process_flag='U';
EXCEPTION
WHEN NO_DATA_FOUND THEN
x_status_msg:=SQLCODE||':'||' Error while selecting event name and event id in Procedure PROC_WMS_XML_READ : Record is not available in USR_OUB_FILE_PROCESS_DETAILS table for event id '|| P_EVENT_KEY;
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
WHEN TOO_MANY_ROWS THEN
x_status_msg:=SQLCODE||':'||' Error while selecting event name and event id in Procedure PROC_WMS_XML_READ : More than one Records found in USR_OUB_FILE_PROCESS_DETAILS table for event id '|| P_EVENT_KEY;
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
WHEN VALUE_ERROR THEN
x_status_msg:=SQLCODE||':'||' Error while selecting event name and event id in Procedure PROC_WMS_XML_READ : Varibale length is small or data type mismatch while selecting event id and event name in USR_OUB_FILE_PROCESS_DETAILS table for event id '|| P_EVENT_KEY;
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
WHEN OTHERS THEN
x_status_msg:=SQLCODE||':'||'Error in Procedure PROC_WMS_XML_READ while selecting event name and event id ';
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
END;
/*BLOCK FOR CAPTURING EVENT NAME BASED ON EVENT ID END*/
/*LOGIC TO READ XML FROM REMOTE LOCATION START*/
DBMS_LOB.CREATETEMPORARY(V_CLOBLOCATOR, TRUE);
V_FILELOCATOR := BFILENAME(P_DIRECTORY,V_FILE_NAME);
DBMS_LOB.OPEN(V_FILELOCATOR,DBMS_LOB.FILE_READONLY);
V_AMOUNT_TO_LOAD := DBMS_LOB.GETLENGTH(V_FILELOCATOR);
DBMS_LOB.LOADCLOBFROMFILE(V_CLOBLOCATOR,
V_FILELOCATOR ,
V_AMOUNT_TO_LOAD,
DEST_OFFSET,
SRC_OFFSET,
0,
LANG_CONTEXT,
WARNING);
dbms_lob.close(V_FILELOCATOR);
/*LOGIC TO READ XML FROM REMOTE LOCATION END*/
/*Temporary Code to help with debug Clear the table before populating it with new data*/
--delete table BRAD_XML_DEBUG;
cnt:=1;
seg_id_bkp:=0;
data_status:='N';
v_seq_no:=0;
prev_seq_set:='NO';
/*create new parser.*/
l_parser := dbms_xmlparser.newParser;
dbms_xmlparser.parseClob(l_parser, replace(V_CLOBLOCATOR,'&','1x2x3x4x5'));
/*Parse the document and create a new DOM document.*/
domdoc :=dbms_xmlparser.getDocument(l_parser);
/* get all elements in the DOM*/
nodelist := XMLDOM.getElementsByTagName(DOMDoc, '*');
len1 := XMLDOM.getLength(nodelist);
/* loop through elements of the DOM */
FOR j in 1..len1-1 LOOP --MAIN LOOP START
BEGIN
/*below sql will fetch Node from table to travel xml data*/
BEGIN
SELECT int_name,tag_name
INTO p_int_name, p_seg1
FROM usr_wms_tag_det
WHERE int_name=v_event_name
AND seq_no =cnt;
EXCEPTION
--PLEASE DO NOT HANDLE ANY EXCEPTION APART MENTIONED BELOW
WHEN OTHERS THEN
NULL;
END;
IF cnt=1 THEN
v_main_seg:=p_seg1;
END IF;
EXCEPTION
--PLEASE DO NOT HANDLE ANY EXCEPTION APART MENTIONED BELOW
WHEN no_data_found THEN
null;
WHEN OTHERS THEN
x_status_msg:=SQLCODE||':'||'Error in Procedure PROC_WMS_XML_READ while selecting interface name and tag name'||sqlerrm;
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
END;
/*LOGICS TO READ XML START*/
node:=XMLDOM.item(nodelist, j);
elements:=XMLDOM.makeElement(node);
parent_seg:=(xmldom.getTagName(elements));
tag_name_bkp:=(xmldom.getTagName(elements));
name_node_map:=xmldom.getAttributes(node);
n_child:=xmldom.getFirstChild(node);
col_value:=xmldom.getNodeValue(n_child);
/*get the sequence number from the interface hierarchy table */
SELECT count(1)
INTO valid_seg
FROM usr_wms_tag_det
WHERE int_name=v_event_name
AND tag_name = tag_name_bkp;
if valid_seg>0 then
begin
SELECT seq_no
INTO sequence_bkp
FROM usr_wms_tag_det
WHERE int_name=v_event_name
AND tag_name = tag_name_bkp;
seg_id_bkp:=seg_id_bkp+1;
p_seg:=parent_seg;--Modified by Vishwanath Dubey dated 16-jun-2011
end;
end if;
if prev_seq_set = 'NO' then
begin
prev_sequence := sequence_bkp;
prev_seq_set := 'YES';
end;
end if;
if sequence_bkp < prev_sequence then --you just moved up level(s) in the message structure
begin
select max(seg_id)
into parent_id
from usr_wms_global_xml_det
where seg_sequence = sequence_bkp-1;
prev_sequence := sequence_bkp;
end;
end if;
if sequence_bkp > prev_sequence then --you just moved down a level in the message structure
parent_id := seg_id_bkp-1;
prev_sequence := sequence_bkp;
end if;
/*end getting the hierarchy table sequence */
/*LOGICS TO READ XML END */
IF (parent_seg =p_seg1) or (parent_seg=p_seg2) THEN
if parent_seg=v_main_seg then
v_seq_no:=v_seq_no+1;
end if;
BEGIN
/* INSERTING DATA LOGICS TO READ XML END */
INSERT INTO usr_wms_global_xml_det values(p_int_name,tag_name_bkp,parent_seg,seg_id_bkp,sequence_bkp,parent_id,'','','',J,v_seq_no,data_status,cnt);
EXCEPTION
WHEN OTHERS THEN
x_status_msg:=SQLCODE||' : Error in Procedure PROC_WMS_XML_READ while inserting records in USR_WMS_GLOBAL_XML_DET table for interface name and parent segment '||P_INT_NAME||','||PARENT_SEG;
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
END ;
p_seg:=parent_seg;
p_seg2:=P_SEG1;
cnt:=cnt+1;
ELSE
chile_seg:=parent_seg;
BEGIN
/* INSERTING DATA LOGICS TO READ XML END */
INSERT INTO usr_wms_global_xml_det values(p_int_name,tag_name_bkp,p_seg,seg_id_bkp,sequence_bkp,parent_id,'',chile_seg,replace(TRIM(Col_Value),'1x2x3x4x5','&'),J,v_seq_no,data_status,cnt);
EXCEPTION
WHEN OTHERS THEN
x_status_msg:=SQLCODE||' : Error in Procedure PROC_WMS_XML_READ while inserting records in USR_WMS_GLOBAL_XML_DET table for interface name and parent segment '||P_INT_NAME||','||PARENT_SEG;
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
END;
END IF;
END LOOP; --MAIN LOOP END
dbms_xmldom.freeDocument(DOMDoc);
x_status:=0;
EXCEPTION
WHEN DIRECTORY_PATH_INVALID THEN
x_status_msg:=SQLCODE||' : Error in Procedure PROC_WMS_XML_READ DIRECTORY PATH IS INVALID';
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
WHEN FILE_NOT_FOUND THEN
x_status_msg:=SQLCODE||' : Error in Procedure PROC_WMS_XML_READ INVALID XML FILE NAME OR FILE DOES NOT EXISTS';
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
WHEN NO_PRIVILEGES THEN
x_status_msg:=SQLCODE||' : Error in Procedure PROC_WMS_XML_READ Insufficient privileges on file or directory NAME- '||p_directory||' to perform FILEOPEN operation.';
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
RETURN;
WHEN OTHERS THEN
x_status_msg:=SQLCODE||' : Error in Procedure PROC_WMS_XML_READ '|| SQLERRM;
x_status:=SQLCODE;
proc_wms_error_trace(v_whid, --warehouse id
null , --event id
v_event_name , --event name
x_status, --error code
x_status_msg ); --error message
dbms_xmlparser.freeParser(l_parser);
dbms_xmldom.freeDocument(DOMDoc);
RETURN;
END PROC_WMS_XML_READ;
Edited by: user13427480 on Feb 8, 2013 7:08 PM

when you post sql statement use also similar threads :
ORA-22290: operation would exceed the maximum number of opened files or LOB
https://kr.forums.oracle.com/forums/thread.jspa?messageID=10842417

Using PreparedStatement and the Oracle Error ORA-1000

Hi,
I have a question about PreparedStatement objects that is not so simple to explain for me. What I would like to know is: if I use a PreparedStatement following traditional and generic steps:
1- PreparedStatement pStmt = Connection.prepareStatement(sQuery);
2- pStmt.setXXX(i,j);
n - pStmt.setXXX(i,j);
n+1 - ResultSet rs = pStmt.executeQuery();
n+2 - while(rs.next()){ ... retrive ResultSet data ... }
n+3 - rs.close()
n+4 - back to point number 2
and at the end (as you can see in the point numbered n+4), instead of closing the PreparedStatement pStmt using the close() method, I reuse the PreparedStatement pStmt comeing back to the point numebr 2 and setting again all its parameters with new values ... then ... what heppens in the Oracle database ? Has been the cursor (so the mamory area), associated to my PreparedStatement object pStmt, duplicated or is it the same ?
I know that Java allows you to do this kind of operations with PreparedStatement, and I know that in tha Java Documentation is explained to follow this strategy to optimize the execution time because in this way the same PreparedStatement is precompiled and prepared only once. But if I do a for loop following the steps explained before, after many iterations I have the error "ORA-1000: maximum open cursors exceeded". This error is the reason of my question. Does this error means that it's mandatory to close a PreparedStatement always, otherwise if you reuse it without closing it then the corresponding database cursor will be duplicated ? If it is so, then I think this is a contradiction with official java documentation ...
I'm using Oracle8i (version 8.1.7) and Oracle JDBC Thin Driver (Windows NT) for use with JDK 1.2.x. Moreover, in my database istance the parameter "maximum open cursor" is equal to 800 ...
Thank you very much for suggestions :-)

There is no need to close a prepared statement or its resultset for every iteration.
After the first iteration in a loop, all subsequent executions of it will close the previous resultset. By adding close() method, you are making one extra costly call to the DB for no reason.
Following is the sample code.I know what you are saying. In fact at the beginning I wrote my code in the same way of your sample (see the code of my first post at the begin of this page).
But doing so, after thousand iterations of the loop, I had "Oracle Error ORA-1000 : maximun open cursor exeeded" even if in my database istance the parameter "maximum open cursor" is equal to 8000.
At this moment in my code, for each iteration, I close the PreparedStatement and in this way I don't have anymore the error :-((
So it seems that only in theory we can reuse a preparedStatement without closing it. In fact if we see the oracle system table "$open_cursor" (as Konrad Pietzka suggest me) we can find that, for each interation,
at our line code "rs = pstmt.executeQuery();" correspond a new cursor in the database: this means that for each method "pstmt.executeQuery()" the database open a new cursor and do not use the previous one as it should.
I posted a question two months ago to search if someone had the same problem (it seems that Konrad Pietzka had the same situation) and was able to explain me what is the cause.
The only reason I found by myself for this problem, is that probably the Oracle JDBC Thin Driver for Windows NT/2000 has some bugs... but I'm not sure ...
Thank you very much for you time !!
bye :-))
Fidalma

Oracle error ORA-01461when trying to insert into an ORACLE BLOB field

I am getting Oracle error ‘ORA-01461: can bind a LONG value only for insert into a LONG column' when trying to insert into an ORACLE BLOB field. The error occurs when trying to insert a large BLOB (JPG), but does not occur when inserting a small (<1K) picture BLOB.(JPG). Any ideas?
BTW, when using a SQL Server datasource using the same code.... everything works with no problems.
ORACLE version is 11.2.0.1
The ORACLE datasource is JDBC using Oracle's JDBC driver ojdbc6.jar v11.2.0.1 (I also have tried ojdbc5.jar v11.2.0.1; ojdbc5.jar v11.2.0.4; and ojdbc6.jar v11.2.0.4 with the same error result.)
Here is my code:
<cfset file_mime = Lcase(Right(postedXMLRoot.objname.XmlText, 3))>
<cfif file_mime EQ 'jpg'><cfset file_mime = 'jpeg'></cfif>
<cfset file_mime = 'data:image/' & file_mime & ';base64,'>
<cfset image64 = ImageReadBase64("#file_mime##postedXMLRoot.objbase64.XmlText#")>
<cfset ramfile = "ram://" & postedXMLRoot.objname.XmlText>
<cfimage action="write" source="#image64#" destination="#ramfile#" overwrite="true">
<cffile action="readbinary" file="#ramfile#" variable="image_bin">
<cffile action="delete" file="#ramfile#">
<cfquery name="InsertImage" datasource="#datasource#">
INSERT INTO test_images
image_blob
SELECT
<cfqueryparam value="#image_bin#" cfsqltype="CF_SQL_BLOB">
FROM dual
</cfquery>

Can't you use "alter index <shema.spatial_index_name> rebuild ONLINE" ? Thanks. I could switch to "rebuild ONLINE" and see if that helps. Are there any potential adverse effects going forward, e.g. significantly longer rebuild than not using the ONLINE keyword, etc? Also wondering if spatial index operations (index type = DOMAIN) obey all the typical things you'd expect with "regular" indexes, e.g. B-TREE, etc.

Oracle error ORA-22905: cannot access rows from a non-nested table item

Oracle error ORA-22905: cannot access rows from a non-nested table item
Creating a report using oracle plsql code .
Getting error ;
Oracle error ORA-22905: cannot access rows from a non-nested table item
when I am trying to pass data in clause in pl sql proc
basically I have a proc which takes 2 parameters(a and b)
proc (
P_a varchar2,
p_b varchar2,
OUT SYS_REFCURSOR
culprit code which is giving me the error and on google they say cast it but I dont know how to do it in my context
--where id in (
--        SELECT * FROM THE (SELECT p_cd_common.get_table_from_string(P_a) FROM dual)
--        union
--        SELECT * FROM THE (SELECT p_cd_common.get_table_from_string(P_b) FROM dual)
data sample returned from this :SELECT * FROM THE (SELECT p_cd_common.get_table_from_string(P_a) FROM dual)
'Abc','def',
data sample returned from this;SELECT * FROM THE (SELECT p_cd_common.get_table_from_string(P_b) FROM dual)
'fgd','fth',
Any answers ?
How to pass data in clause in a better way

Why are you creating a duplicate post? I already asked you to post p_cd_common.get_table_from_string. In particular what is function return type and where it is declared. As I already mentioned, most likely function return type is declared in the package and therefore is PL/SQL type. And TABLE operator can only work with SQL types.
SY.

Oracle Error :: ORA-12637 Packet receive failed

Hi buddies,
One of my staff's PC is receiving this error sometimes when she is trying to connect to the database and she is able to connect sometimes.
Oracle Error :: ORA-12637 Packet receive failed What could be the cause.
I tried replacing her tnsadmin with my tnsadmin and it didn't make a change, still able to connnect sometimes and sometimes not.
Able to connect using PL/SQL developer, but not using our customized application. (Everyone else are able to connect)
Is it network problem?
Please advice.
Thank You very much.
Alagu
Edited by: user645399 on Sep 16, 2009 8:37 PM

And from this cut-and-paste the OP is supposed to take what actions to solve the problem? Please don't just post that which is one google away every time someone posts an ORA- exception. You make some valuable contributions here but just posting expanded text doesn't give someone a list of actions to take that will help them resolve the issue. Better the question is left unanswered so others will be more likely to offer help.
To the OP:
It is highly likely you have a network issue and the fact that it is isolated to a single machine makes it reasonably easy to fix. First try to figure out which component is failing. Go to the router or switch and swap wires between that client machine and another one that is working properly. Does the problem move? If not then swap the wires. Again does the problem move? Next the NIC card? What if you put another machine on the desk and put the original hard disk in it?
Sometimes it just isn't worth the effort so you just swap out the machine.
Intermittent problems are always hard to identify and fix. What is on your side is that this is only affecting a single user.

Urgent-Oracle Error :: ORA-39778-

Hi
I got following Oracle Error : ORA-39778 "the parallel load option is not allowed when loading lob columns" on production. yesterday we updated database with patchset 9.2.0.7 and DST/JVM compliant.
Please reply me ASAP.
Regards,
RJ

Sry I didn't check back this afternoon.
As posted,
Here's the note from metalink doc Note:396387.1
Then e this to apply the files manually in the following way:
Download the identified patch.
Unzip the patch, and locate the 2 files timezone.dat and timezlrg.dat in the "files/oracore/zoneinfo" directory of the uncompressed patch (or from the relevant .jar file of a patchset). If there is also a readme.txt in this location then make a note of this as well.
Backup your existing files in $ORACLE_HOME/oracore/zoneinfo - THIS CAN BE VITAL, DO NOT SKIP.
Copy the 2 .dat files and possibly the readme.txt file that were found in step 2 into the $ORACLE_HOME/oracore/zoneinfo directory.
Restart the database (in case of installation on a database), or restart the client applications (in case of client install). Note that the database did not need to be down before the time zone files were applied, but it does need to be restarted afterwards.

APP-DT-34605:Oracle error ORA-4098 occured while writing to PER_ALL_ASSIGNM

We have Upgraded DB from 10.2.0.2 to 10.2.0.5 having same Apps version 11.5.10.2,
we have seen below issue upon upgrade,
While updating any information in Assignment i.e. Assignment Status getting following error.
APP-DT-34605:Oracle error ORA-4098 occured while writing to PER_ALL_ASSIGNMENTS_F
How to overcome these errors, please advise,
RM

Please see these docs.
PERWSHRG: Updating Assignment Gives Error APP-DT-34605 ORA-6510 [ID 286294.1]
Update Employee Assignment Details Cause Error: APP-DT-34605-- ORA-20001 occurred writing to PER_ALL_ASSIGNMENTS_F [ID 793451.1]
APP-DT-34605 Error When Saving on Assignment Form [ID 829292.1]
Receive APP-DT-34605 Error When Updating an Existing Payment Method [ID 780090.1]
ORA-06508 PL/SQL Could Not Find Program Unit Being Called: "APPS.PAY_PAY_SHD" [ID 1170903.1]
Thanks,
Hussein

Hi, i am getting oracle error ora-01013 user requested cancel of current operation.

I know this is timeout error however my select query simply returns count from 2-3 tables.. any help would be appritiated, please help me.

Hi Ramin,
Thanks for reply. Below is the query i am running,
SELECT COUNT(TRN.TRANSACTIONID)
FROM TRANSACTIONDATA TRN,
CONTENTDATA CND,
ACTIVITY AC,
ACTIVINVOL AVL,
PARTY PR
WHERE TRN.T_ID=CND.T_ID
AND CND.CD=AC.CD
AND AC.AD=AVL.AD,
AND AVL.PRD=PR.PRD
AND PR.SPRI=42345
AND TRN.LUT > '16-JUN-2013'
AND UPPER(TRN.T_ID) LIKE 'ONE AND DONE COM%' ;
WHICH OCCURS ERROR ora-01013 user requested cancel of current operation.
THANKS
DESHMUKH

Sandee mendelson reid : Oracle Error: ORA-01403

Hi everyone!!!
Please could you tell me why I get an error (ORA-01403: No data found) when executing a sql query on Oracle 8i?
The query is:
"INSERT INTO TABLE1 SELECT * FROM TABLE2"
NB:
when I run the query "SELECT * FROM TABLE2"
I get property registration!
it is at the time of insertion of recording in Table 1 that the error occurs:
ORA-01403: No data found
thank you in advance for your help
Sandee mendelson reid

Even on your really old version of Oracle, the insert select should not raise a no data found error. Is that the full error stack you get? Typically that error comes in a PL/SQL block where you are selecting a value into a variable. I would expect the full error stack would also include the name of the PL/SQL unit where the error occurred. Is ther a trigger defined on table1?
John

Oracle error ORA-00600 when using Oracle 10g and Sun One Web Server 6.1

I have a java application that was running under Solaris 8 and Oracle 9i. I am trying to get it up and running on a new server that is configured with Solaris 9 and Oracle 10g. Whenever the application tries to connect to the database it receives the following error: ORA-00600 [ttcgcshnd-1][0]. My research indicates that this is an internal Oracle error that represents a low level unexpected condition. I have looked through my configuration for the Web Server and I have not been able to determine the cause of this problem. My DBA tells me that we have the latest patch installed for Oracle! Has anyone encountered this problem before? Any help would be greatly appreciated!

If the problem is also present in a SWING app, i.e. outside the web server, then it is porbably something external to the webserver.
I think you should ensure that the driver and database are compatible with each other. It is very likely that you need a new jdbc driver for the new database.
download from here http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/htdocs/jdbc101020.html
try the ojdbc14.jar

Oracle error ORA-01115

when we run sql update we get the error ORA-01115 : IO eror reading from file 348 and
ORA-01110 : data file 657 : /dev/vx/rdsk/racdg1/PSindex03 ORA-27072 : skgfdisp : I/O error SVR4 Error : 12 : not enough space.
the database is working perfectly.
the job runs perfectly when we re-run the job after several tries.
i have checked the oracle documentation on error and causes.they have not helped me yet.
please give your inputs.
oracle 9i with RAC
OS solaris

1. Try to assess the cause and extent of the problem.
Examine the alert.log file for this instance. Scan the last few
days' entries for other occurrences of ORA-01115. If you find them,
A) Do they reference files in different disks?
If so, it is likely that there you have controller problems.
Move on to Scenario II.A below.
B) Do they reference different files in the same disk?
If so, it is likely that there are problems with that disk.
Move on to Scenario II.B below.
C) Do they always reference the same datafile?
If so, it is likely that the datafile contains bad blocks.
Move on to Scenario II.C below. If the file is bigger
than 2GB and you are running 7.1.4 or lower on a Solaris
platform, see Scenario II.D below.
D) If none of the above applies, move on to Step 2.
2. If the datafile is in the SYSTEM tablespace, or the database is in
NOARCHIVELOG mode, shut the database down. Move on to Step 4.
If shutdown immediate fails, do a shutdown abort.
3. If the database is in ARCHIVELOG mode, you should still shut the
database down. If the database cannot be shut down, offline the
datafile.
ALTER DATABASE DATAFILE '<full_path_file_name>' OFFLINE;
4. Try to copy the datafile to another disk (managed by a different
controller, if possible).
5. If the copy fails, even after you retry, the datafile must be considered
lost at this point. The next action depends on the tablespace to
which the lost file belongs. See the following Solution References to
PR entries, according to the different types of tablespaces,
for instructions on how to proceed.
IMPORTANT: While going through the references below, keep in mind that
if you restore the datafile from backup, you need to place it in another
disk, preferably under a different controller, and rename it inside Oracle
(see Note 115424.1 for details). If you recreate any tablespace, make
sure its datafiles are created in another disk, preferably under a
different controller.
Reference for Lost datafile scenarios : Note 198640.1
6. If the database is down, mount it.
7. Rename the datafile that you succeeded in copying inside Oracle.
ALTER DATABASE RENAME FILE '<old_full_path_file_name>'
TO '<new_full_path_file_name>';
8. If the database is mounted, open it. If you offlined the datafile,
perform media recovery on it, and then bring it online.
RECOVER DATAFILE '<full_path_file_name>';
ALTER DATABASE DATAFILE '<full_path_file_name>' ONLINE;

Work around/Alternate solution for Oracle error ORA-01460 and ORA-02063

After the installation of Oracle.DataAccess version 2.111.7.20, I get the following error.(the code worked fine with Oracle.DataAccess version 9.2.0.700 )
I have attached the error as well as the sample code.
ORA-01460 and ORA-02063 are known bugs in the new ODP but would like to know if there is any Work around/Alternate solution for this problem(other than
the use of stored procs)..
Thanks!
Error:
ORA-01460: unimplemented or unreasonable conversion requested
ORA-02063: preceding line from BSREAD_STAGINGRO at Oracle.DataAccess.Client.OracleException.HandleErrorHelper(Int32 errCode, OracleConnection conn, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src, String procedure, Boolean bCheck)
at Oracle.DataAccess.Client.OracleException.HandleError(Int32 errCode, OracleConnection conn, String procedure, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src, Boolean bCheck)
at Oracle.DataAccess.Client.OracleCommand.ExecuteReader(Boolean requery, Boolean fillRequest, CommandBehavior behavior)
at Oracle.DataAccess.Client.OracleCommand.ExecuteReader()
SampleCode
private bool isValidFieldData(string clientName, string fieldNumber, string uniqueID, string clientID)
using (OracleConnection mBSConnection = new OracleConnection(mBSConnectionString))
OracleDataReader oRdr = null;
OracleCommand Valid_FieldData_Command = null;
try
Valid_FieldData_Command = new OracleCommand();
Valid_FieldData_Command.Connection = mBSConnection;
Valid_FieldData_Command.CommandText = "SELECT uniqueid FROM EXTDB.BSData WHERE agencyid = :agencyid and agencyname=:agencyname AND fieldnumber =:fieldnumber AND uniqueid = :uniqueid";
Valid_FieldData_Command.Parameters.Add(":agencyid", OracleDbType.Varchar2, 255).Value = agencyID;
Valid_FieldData_Command.Parameters.Add(":agencyname", OracleDbType.Varchar2, 255).Value = agencyName;
Valid_FieldData_Command.Parameters.Add(":fieldnumber", OracleDbType.Varchar2, 255).Value = fieldNumber;
Valid_FieldData_Command.Parameters.Add(":uniqueid", OracleDbType.Varchar2, 255).Value = uniqueID;
mBSConnection.Open();
oRdr = Valid_FieldData_Command.ExecuteReader(); ->Error occurs here
The error occurs whenever the length of any of the parameter is increased. But there is no specific length where it is breaking down.
For example in this case, it breaks down with the given error if
agencyID > 8
agencyName > 6
fieldNumber > 9
uniqueid > 6

The problem was mapping input parameter type.
VARCHAR2-type mapping input parameter works with String-type PF parameter. But CHAR-type won't.

ORACLE error ORA-04031: unable to allocate 16 bytes of memory

Error
UDI-04031: operation generated ORACLE error 4031
ORA-04031: unable to allocate 16 bytes of shared memory ("shared pool","SELECT j
generated during import operation, using documentation about migration from 10g XE to 11g XE.

Hello,
you could try to override the automatic memory management and setup your SGA to be larger by setting SGA_TARGET. If that doesn't help yet, you could even try to configure the memory size for the components in SGA manually, but I guess this won't be necessary.
After your import is done, I'd recommend to use automatic memory management again.
See the XE 2 Day DBA for details, especially the section on [url http://download.oracle.com/docs/cd/E17781_01/server.112/e18804/memory.htm#ADMQS174]Managing Memory. It's not a complete guide, but a rough introduction, but it'll probably help you understand the memory concepts in the database.
Keep in mind that you may only assign 1 GB of memory in total when you setup your memory manually.
-Udo

Oracle Error ORA 03123 (operation would block)

Similar Messages

Maybe you are looking for