ORA-00604: error occurred at recursive SQL level x
Have a look at the next error message.
Most of the time, this error will appear in trace files or in the alert.log file.
Sometimes when you execute a statement, Oracle does some recursive Sql statements behind the screen.
For instance, when you create a new table, Oracle executes a number of extra (recursive) statements to update the data dictionary.
When creating a new table, a new record in OBJ$ is inserted, tablespace quota is checked, privileges are checked and so on...
When executing one of these recursive statements, a problem was encountered and the ORA-00604 error is returned followed by the actual error message.
So it is important to look at the next error code returned, which will tell you the exact cause of the problem.
In the next example, a database job failed to execute because of lack of memory in the shared pool.
ORA-00604: error occurred at recursive SQL level 1
ORA-04031: unable to allocate 132 bytes of shared memory ("shared pool","select decode(u.type#, 2, u...","kgsp-heap","kglpn")
Welcome to our forum for Oracle error: ORA-00604 Add your own message
"error 604 detected in background process"
"ORA-00604: error occurred at recursive SQL level "
and the database become to closed.
This error appears in a "oracle-sid"_pmon_xxx.trc
"error 604 detected in background process"
"ORA-00604: error occurred at recursive SQL level "
and the database become to closed.
This error appears in a "oracle-sid"_pmon_xxx.trc
 Connection Error trying to connect to CRM01 |
Following error was detected when trying to make a database connection:
 Click on the error code(s) to fetch more information from our website. |
Your system tablespace is completely full.
You need to logon to the database server, and access your database using a SYSDBA users:
sqlplus / as sysdba
Next, you will need to add extra space to your system tablespace.
Check following link for examples on how to extend the tablespace
Hi ,
I am trying to read PDF file from server, I used the below code
l_bfile:=bfilename('\u05\app\applmgr\11i\oraclecomn\admin\out\jamuna_server','o7742576.out');
if DBMS_LOB.FILEEXISTS(l_bfile) = 1 then
dbms_output.put_line( 'Exists!');
dbms_output.put_line(dbms_lob.getlength(l_bfile));
else
dbms_output.put_line( 'Not Exists!');
end if;
while using dbms_log package , i got the below error .I am bit worried since I have created directory and gave sufficicent priviliges too.
Error report:
ORA-00604: error occurred at recursive SQL level 1
ORA-01460: unimplemented or unreasonable conversion requested
ORA-06512: at "SYS.DBMS_LOB", line 485
ORA-06512: at line 24
Can you please suggest me what I can do to move further?
Don't you want to specify forward slashes (/) instead of backward slashes (\) in your path ?
l_bfile:=bfilename('/u05/app/applmgr/11i/oraclecomn/admin/out/jamuna_server','o7742576.out');
If this does not work, can you do an explicit conversion of the length?
dbms_output.put_line(to_char(dbms_lob.getlength(l_bfile)));
Thanks for giving reply for my doubt ,I tried by implementing your suggestions,eventhough its giving the same error.
here is my code:-
declare
file_handle UTL_FILE.FILE_TYPE;
l_blob BLOB;
l_bfile bfile;
l_byte number;
BEGIN
l_bfile:=bfilename('/u05/app/applmgr/11i/oraclecomn/admin/out/jamuna_server','o7742576.out');
dbms_output.put_line(to_char(dbms_lob.getlength(l_bfile)));
END;
Are there more error messages displayed, because ORA-00604 is more like a generic error, and will be followed by another error which indicates the real problem (like file does not exits, directory not accessible, ...)
Are there no additional errors displayed?
Add your message
If you need more information about this particular error message, you can leave a forum message.
We are replying to this message whenever we have some spare time, so please do not consider this as a private 'solve my critical issue asap' service.
Should you need professional Oracle Assistance to make your project a success, please have a look at our consultancy services.
In order to prevent automatic generation of messages, we are asking for a validation code. This code is unique and is generated every time a new message is asked.
If you do not enter the validation correctly, your message will not be recorded.