Shutdown immediate hangs ORA-12012, ORA-12008, ORA-06512

We have a problem while immediate shutting down the database:
alert.log:
Errors in file /data_archiv/oracle/admin/EGB/bdump/egb_j001_7708.trc:
ORA-12012: error on auto execute of job 3
ORA-12008: error in materialized view refresh path
ORA-01089: immediate shutdown in progress - no operations are permitted
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 1883
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2089
ORA-06512: at "SYS.DBMS_IREFRESH", line 683
ORA-06512: at "SYS.DBMS_REFRESH", line 195
ORA-06512: at line 1
Mon Jun 11 16:20:29 2007
Job queue slave processes stopped
Mon Jun 11 16:26:36 2007
Active call for process 7695 user 'oracle' program 'oracle@lxegbp2qs (J000)'
SHUTDOWN: waiting for active calls to complete.
Trace:
/data_archiv/oracle/admin/EGB/bdump/egb_j001_7708.trc
Oracle Database 10g Enterprise Edition Release 10.1.0.4.0 - Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /data_archiv/oracle/product/10g
System name:     Linux
Node name:     lxegbp2qs
Release:     2.6.5-7.244-smp
Version:     #1 SMP Mon Dec 12 18:32:25 UTC 2005
Machine:     i686
Instance name: EGB
Redo thread mounted by this instance: 1
Oracle process number: 19
Unix process pid: 7708, image: oracle@lxegbp2qs (J001)
*** SERVICE NAME:(SYS$USERS) 2007-06-11 16:20:28.759
*** SESSION ID:(273.1) 2007-06-11 16:20:28.759
*** 2007-06-11 16:20:28.759
ORA-12012: error on auto execute of job 3
ORA-12008: error in materialized view refresh path
ORA-01089: immediate shutdown in progress - no operations are permitted
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 1883
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 2089
ORA-06512: at "SYS.DBMS_IREFRESH", line 683
ORA-06512: at "SYS.DBMS_REFRESH", line 195
ORA-06512: at line 1
The job with id 3 should not run during shut down (needs only seconds):
select substr(what, 1, 70), TO_CHAR(last_date, 'DD.MM.YYYY HH24:MI:SS') as last_date, TO_CHAR(next_date, 'DD.MM.YYYY SQL> HH24:MI:SS') as next_date from dba_jobs where job=3;
SUBSTR(WHAT,1,70)
LAST_DATE NEXT_DATE
dbms_refresh.refresh('"TEST"."MV_TEST"');
11.06.2007 06:00:06 12.06.2007 06:00:00
Any ideas where to look for?

Active call for process 7695 user 'oracle' programKill active call process mentioned in alert.log.

Similar Messages

Shutdown immediate hanging

I need to develop a scripts that shuts down all databases on a server. One of my databases sometimes hangs after issuing "shutdown immediate" command, and I want to handle this situation in my script. What I am thinking is to add "shutdown abort" in the script if "shutdown immediate" does not work. However, I do not know how to determine the database is hanging during shutdown immediate. Can you advise me on how to handle the shutdown immediate hanging problem in my shell script? Or is there better way to handle this in the script?
Thank you very much for your help!

As noted, if your shutdown immediate really hang because of rollback, then my method won't work either. The only different will be Oracle is going to do the rollback at next startup when doing instance recovery. In that case, the startup will appear to be hang.
Check this metalink doc,
What To Do and Not To Do When 'shutdown immediate' Hangs
Doc ID: Note:375935.1
There are cases where shutdown immediate hang because of bug.
Shutdown Immediate Hangs
Doc ID: Note:268884.1

If shutdown immediate hangs database waits one hour for shutdown abort

we have schedules cold backup for our 11g database on redhat 5.3.
there is a shell script written with shutdown immediate command.
If database hangs during shutdown immediate database waits one hour for auto shutdown abort.
but this happens once or twice in a month
can we do this auto shutdown abort earlier than one hour ??

user13376823 wrote:
we have schedules cold backup for our 11g database on redhat 5.3.
Since you're shutting down the database for cold backup so ensure it should be shutdown properly by shutdown or shutdown immediate cmd not by abort cmd.
Consistent backup:-
A backup taken when the database is mounted (but not open) after a normal shutdown. The checkpoint SCNs in the datafile headers match the header information in the control file. None of the datafiles has changes beyond its checkpoint. Consistent backups can be restored without recovery.
http://docs.oracle.com/cd/B19306_01/backup.102/b14191/rcmconc1.htm#i1007616

Shutdown immediate hangs

SunOS 5.8
Database version: 9.2.0.4.0
Customer shutdown database every night for backup the datafiles to disk.
For your information, 2 weeks ago customer moved datafiles to a new disk.
The stoppscript has worked for a week.
And after a week the database will not shutdown.
We did a shutdown abort, and it works for a couple of days.
Now it happend again. The database will not go down.
Can't find any error messages!
Any suggestions?
# stoppscript
. $HOME/.profile
INSTANSER="BALA"
echo
echo "###########################################"
echo "# Startar nedtagning av O R A C L E #"
echo "###########################################"
echo
echo
echo "####### Stoppar LISTENER #######"
echo
$ORACLE_HOME/bin/lsnrctl << EOF
stop LISTENER
exit
EOF
for i in $INSTANSER
do
ORACLE_SID=$i
export ORACLE_SID
echo
echo "##### Stoppar instans - $ORACLE_SID #####"
echo
$ORACLE_HOME/bin/sqlplus /nolog << EOF
connect / as sysdba
shutdown immediate
startup exclusive restrict
shutdown
exit
EOF
done
echo
echo "########################################"
echo "# Slut nedtagning av O R A C L E #"
echo "########################################"
echo
# Alert_log
Tue Sep 5 01:16:48 2006
Shutting down instance: further logons disabled
Shutting down instance (immediate)
License high water mark = 41
Waiting for dispatcher 'D000' to shutdown
All dispatchers and shared servers shutdown
Tue Sep 5 01:16:55 2006
ALTER DATABASE CLOSE NORMAL
Tue Sep 5 01:16:55 2006
SMON: disabling tx recovery
SMON: disabling cache recovery
Tue Sep 5 01:16:56 2006
Shutting down archive processes
Archiving is disabled
Tue Sep 5 01:16:56 2006
ARCH shutting down
ARC0: Archival stopped
Tue Sep 5 01:16:56 2006
ARCH shutting down
ARC1: Archival stopped
Tue Sep 5 01:16:56 2006
Thread 1 closed at log sequence 11287
Successful close of redo thread 1.
Tue Sep 5 01:16:56 2006
Completed: ALTER DATABASE CLOSE NORMAL
Tue Sep 5 01:16:56 2006
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archiving is disabled
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Tue Sep 5 08:15:15 2006
Shutting down instance (abort)

I am having similar problem. My server has been up for around 100 days now. And I extensively use XML DB in my code. So, now the DOM memory failed for me, so, I am doing shutdown immediate in the hope that it might fix it ( or atleast start where it is hanging).
Here is a snippet of my alert log file. Can you see where I am stuck at?
Thu Sep 21 14:01:15 2006
Process m001 died, see its trace file
Thu Sep 21 14:01:15 2006
ksvcreate: Process(m001) creation failed
Thu Sep 21 14:28:38 2006
Starting background process EMN0
EMN0 started with pid=19, OS id=2396
Thu Sep 21 14:28:38 2006
Shutting down instance: further logons disabled
Thu Sep 21 14:28:40 2006
Stopping background process CJQ0
Thu Sep 21 14:28:40 2006
Stopping background process QMNC
Thu Sep 21 14:28:42 2006
Stopping background process MMNL
Thu Sep 21 14:28:43 2006
Stopping background process MMON
Thu Sep 21 14:28:45 2006
Shutting down instance (immediate)
License high water mark = 23
Thu Sep 21 14:28:45 2006
Stopping Job queue slave processes
Thu Sep 21 14:28:45 2006
Job queue slave processes stopped
All dispatchers and shared servers shutdown
Thu Sep 21 14:28:55 2006
ALTER DATABASE CLOSE NORMAL
Thu Sep 21 14:28:55 2006
SMON: disabling tx recovery
SMON: disabling cache recovery
Thu Sep 21 14:28:56 2006
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thread 1 closed at log sequence 411
Successful close of redo thread 1
Thu Sep 21 14:29:01 2006
Completed: ALTER DATABASE CLOSE NORMAL
Thu Sep 21 14:29:01 2006
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
btw, This is my screen right now.
U:\Rahul\sql>sqlplus sys as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Thu Sep 21 14:28:16 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter password:
Connected to:
Oracle Database 10g Release 10.2.0.1.0 - Production
SQL> sho sga
Total System Global Area 436207616 bytes
Fixed Size 1249440 bytes
Variable Size 142610272 bytes
Database Buffers 289406976 bytes
Redo Buffers 2940928 bytes
SQL> shutdown immediate;
Database closed.
Database dismounted.
Ok, when I am writing this post, I came back with this message.
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
Total System Global Area 436207616 bytes
Fixed Size 1249440 bytes
Variable Size 142610272 bytes
Database Buffers 289406976 bytes
Redo Buffers 2940928 bytes
Database mounted.
Database opened.
SQL>
Still, any comments would be really appreciated.
Thank you,
Rahul.
P.S - This is a 32 bit windows 2003 server. 10gR2.
Message was edited by:
rputtagunta

Shutdown immediate hangs and HVM of a database

Hi,
I have following questions,
1. What are the possible causes of SHUTDOWN IMMEDIATE command hangs
and doesnt responds.
2. What do u mean by High Water Mark(HVM) of a database. Because when we
give SHUTDOWN IMMEDIATE command there is message in alert log file
mentioning the HVM of a database.
3.Also is there any relationship between shutdown process taking long time to
shutdown a database and HVM of a database.
4. If the database instance is up for a long time then does it take long time to
shutdown a instance.
Thanks,
Girish A

Hello,
for 1.) view Metalink Note:375935.1. Maybe you even get an error: "SHUTDOWN: Waiting for active calls to complete". This has nothing to do with HWM but with already logged on sessions. Immediate means new connections are not able to log in, existing connetions are not disconnected at once.
for 2.) the HWM is the highest point to which datafiles have been filled up. This is the value to which you are able to shrink (if you desire to). View Metalink Note:1034330.6 for message "License high water mark" in alert.log at shutdown ("highest number of concurrent users sessions").
Greets,
Hannibal

Shutdown immediate hangs for 30 mins

Hi,
my database is running on RAC .. it has two instances.. one instance closed immediately... another instance take 30 mins to down.
ARCH: Archiving is disabled
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archiving is disabled
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
SHUTDOWN: waiting for detached processes to terminate.
Thanks,

First Thing First........
I generally never take any such step until it become essential. I always use the above command to kill LOCAL sessions and DB comes down in sometime.Oracle is ORACLE. There are some magical things happen. Something work somewhere and somewhere not.
1. The only thing you can check is ALTER_ORACLE_SID.log.. There you come to know what is happening. Along with this you can see whether the number of orcle processes are coming down. If Not then something needs to be done.
2. Don't use such thing which is not adviseable. This is wried. You can never know when a problem will be in front of you.
KILL THE LOCAL SESSION AND ORACLE WILL DOWN IN 99.9% CASES.
Let me know if someone disagree with me.
Lochan

Shutdown immediate problem

I'm trying to shutdown an Oracle9i database on Unix using SHUTDOWN IMMEDIATE but it just hangs.
I checked the sessions in V$SESSION and noticed there were a few INACTIVE sessions. So I built a script that goes thru all the INACTIVE sessions and kills them.
With all these sessions having status KILLED...when I try to run a SHUTDOWN IMMEDIATE, the database still hangs. I don't want to use SHUTDOWN ABORT.
Does anyone have any information on what makes SHUTDOWN IMMEDIATE hang? Could there be some unix processes....or oracle processes?
Thanks

Dear All,
I am also having some shutdown problem with the Oracle 10g on my Windows Server 2003 machine. My machine could not shutdown (means OS cannot completely shutdown the machine) even after i issued the "shutdown immediate" command.
As what Jaafar said, we should kill the process from OS level. Can any of you explain more on this as I have no idea on how to do this? Which process should I kill after I issued the "Shutdown immediate" command?
Thank you.
best regards,
Wnson

Database shutdown immediate - time calculation ?

Hi,
Good Day.
did any one tried to calculate time the database would took to complete "shutdown immediate" command?
hope to have a healthy discussion..
Regards,
Muhammad Ahmad

Mohamed ELAzab wrote:
Hello Jonathan Lewis,
1-Please note that looking into the alert_sid.log is a good start as it will show if the smon process was dead according to the note:
Shutdown Normal or Shutdown Immediate Hangs. SMON disabling TX Recovery [ID 1076161.6]
I can see that that note is labelled: "Checked for relevance June 2009", but have you seen the garbage it suggests for temporary segments:
<ul>
Verify that temporary segments are decreasing
To verify that the temporary segments are decreasing have an active session
available in Server Manager or SQLPLUS during the SHUTDOWN IMMEDIATE. Issue the following
query to ensure the database is not hanging, but is actually perform extent
cleanup:
SVRMGR/SQL> select count(block#) from fet$;
COUNT(BLOC
+7+
SVRMGR/SQL> select count(block#) from uet$;
COUNT(BLOC
+402+
</ul>
For this to be true the temporary tablespace would have to be declared as dictionary managed, possibly even with contents = "PERMANENT" but it's so long since I've created a dictionary-managed TEMP that I can't be sure of the second point. I would be very cautious about trusting any document that started with such antiquated material - you can have no idea how much of its content might be (at best) deficient and (at worst) dangerously wrong.
3-to know the transactions that will be rolled back please read the note:
How to Check Why Shutdown Immediate Hangs? [ID 164504.1]
Same type of problem - "Checked for relevance: Mar 2010", starts with:
<ul>
Start Server Manager (or SQL*Plus for 8i or higher)
SVRMGRL> connect internal (or SYSDBA for 8i or higher)
SVRMGRL> select * from x$ktuxe where ktuxecfl = 'DEAD';
</ul>
Although x$ktuxe will show you transaction states from the undo segment headers, and this might show you recursive (or other special case) transactions that do not appear in v$transaction, I wouldn't trust a note that is based on 7.3 technology to be an appropriate reference document.
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk

ORA-12012-ORA-12008-ORA-04063: error on r11i

Heloo all;
I have this error:
Errors in file 9.2.0/admin/erp/bdump/prod_j000_18936.trc:
ORA-12012: error on auto execute of job 189
ORA-12008: error in materialized view refresh path
ORA-04063: package body "APPS.FND_GLOBAL" has errors
undo_suppress_errors = FALSE
undo_suppress_errors = FALSE
ORA-12012: error on auto execute of job 189
ORA-12008: error in materialized view refresh path
ORA-04063: package body "APPS.FND_GLOBAL" has errors
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 820
ORA-06512: at "SYS.DBMS_SNAPSHOT", line 877
ORA-06512: at "SYS.DBMS_IREFRESH", line 683
ORA-06512: at "SYS.DBMS_REFRESH", line 195
ORA-06512: at line 1
ORA-00060: Deadlock detected. More info in file 9.2.0/admin/terp/udump/prod_ora_736.trc.
ORA-1653: unable to extend table APPLSYS.DR$FND_LOBS_CTX$I by 16 in tablespace APPS_TS_TX_DATA
ORA-1653: unable to extend table APPLSYS.DR$FND_LOBS_CTX$I by 16 in tablespace APPS_TS_TX_DATA
my APPS_TS_TX_DATA doesnt have size problem...iAPPS.FND_GLOBAL doesnt inviladi!....
after this error message today i have this error:
undo_suppress_errors = FALSE
ORA-00060: Deadlock detected. More info in file /oradb/PROD/proddb/9.2.0/admin/erp/udump/prod_ora_3463.trc.
for the both error undo_suppress_errors seems common...
is anyone has this error before?
Thanks
Helios

Helios,
Please review the following documents and try the suggested solutions.
Note: 743785.1 - How I resolved ORA-1653 on APPS_TS_TX_DATA tablespace
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=743785.1
Note: 154207.1- d1553256.drv Errors ORA-01631 Max Extents Reached Table APPLSYS.DR$FND_LOBS_CTX$I
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=154207.1
Note: 367861.1 - "Rebuild Help Search Index" fails with ORA-01631: max # extents (505) reached in table APPLSYS.DR$FND_LOBS_CTX$
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=367861.1
Note: 180588.1 - Solving ORA-01653: UNABLE TO EXTEND TABLE %S.%S BY %S IN TABLESPACE %S
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=180588.1
If you still get ORA-00060 after resolving the above error, refer to:
Note: 62365.1 - What to do with "ORA-60 Deadlock Detected" Errors
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=62365.1
Note: 164661.1 - ORA-60 / Deadlocks Most Common Causes
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=164661.1
Regards,
Hussein

I am geting errors in my database alert log file ora-12012 and ora 44003

Hi all,
I am using oracle 10g ...10.2.0.1.0 and OS is solaris 10.......
i am geting these errors in my database alert log file last two days..i am not geting why it is coming?
ORA-12012: error on auto execute of job 8887
ORA-44003: invalid SQL name
and trace file is i got i am posting here please help any one is aware about this....
System name: SunOS
Node name: obrmzone1
Release: 5.10
Version: Generic_137111-06
Machine: sun4v
Instance name: ------
Redo thread mounted by this instance: 1
Oracle process number: 144
Unix process pid: 26874, image:--------- (J000)
*** ACTION NAME:(AUTO_SPACE_ADVISOR_JOB) 2011-06-10 22:00:49.372
*** MODULE NAME:(DBMS_SCHEDULER) 2011-06-10 22:00:49.372
*** SERVICE NAME:(SYS$USERS) 2011-06-10 22:00:49.372
*** SESSION ID:(110.7114) 2011-06-10 22:00:49.372
*** 2011-06-10 22:00:49.372
ORA-12012: error on auto execute of job 8887
ORA-44003: invalid SQL name
thank you in advance,
Dav

I just google with "ORA-44003: invalid SQL name" and found below link:
http://www.oracle-base.com/articles/10g/dbms_assert_10gR2.php
SIMPLE_SQL_NAME
The SIMPLE_SQL_NAME function checks the input string conforms to the basic characteristics of a simple SQL name:
The first character of the name is alphabetic.
The name only contains alphanumeric characters or the "_", "$", "#"
Quoted names must be enclosed by double quotes and may contain any characters, including quotes provided they are represented by two quotes in a row ("").
The function ignores leading and trailing white spaces are ignored
The length of the input string is not validated.

Error ORA-12012: and ORA-12005

Hi,
I am working in oracle9i and solaris 5.8.
If i run the procedure automatically means it shows error
Procedure :
CREATE OR REPLACE PROCEDURE PROC_SCHEDULE IS
JOBNO NUMBER;
BEGIN
SYS.DBMS_JOB.SUBMIT(
JOB => JOBNO,
WHAT => 'GARRISON.PROC_ARCHIVE_ALL;',
NEXT_DATE => TRUNC(SYSDATE),
INTERVAL => 'NEXT_DAY(LAST_DAY(TRUNC(SYSDATE)),''SUNDAY'')-7 + 4/24'
COMMIT;
END;
ERROR
ORA-12012: error on auto execute of job 112
ORA-12005: may not schedule automatic refresh for times in the past
This error i got from the log file..
But the same procedure if i run manually means its working Fine.
Please explain me how to run resolve the Error and to run the procedure automatically...
Thanks...

what is your scheduling criteria ?
If you run the query
select next_day(last_day(trunc(sysdate)),'SUNDAY')-7 + 4/24 from dual then as of today you will get an old date.
25-MAR-07
And Uncle oracle is saying scheduling is not possible for the past day.
If you run it say on 1'st april you will get the future date which is 29-APR-07 and thus oracle will not give an error for future scheduling.

ORA-12012: error on auto execute of job 754461 ORA-29279: SMTP permanent error: ORA-29279: SMTP permanent error: 501 Syntax error, parameters in command "RCPT TO:" unrecognized or missing ORA-06512: at "SYS.UTL_SMTP", line 20 ORA-06512: at "SYS.UTL_SMTP",

Hi ,
I am getting below error frequently in alert log of database.
ORA-12012: error on auto execute of job 754461
ORA-29279: SMTP permanent error: ORA-29279: SMTP permanent error: 501 Syntax error, parameters in command "RCPT TO:" unrecognized or missing
ORA-06512: at "SYS.UTL_SMTP", line 20
ORA-06512: at "SYS.UTL_SMTP", line 98
ORA-06512: at "SYS.UTL_SMTP", line 240
ORA-06512: at "APPS.EIS_UTIL_PKG", line 94
ORA-06512: at "APPS.HKD_PO_ADDON_PKG", line 110
ORA-06512: at line 1

You have a job running in the database. Its job ID is 754461
It looks as if that job runs APPS.HKD_PO_ADDON_PKG
That job is attempting to send mail using UTL_SMTP and apparently passing some strange value to SMTP server for the RCPT TO: parameter.

ORA-12012

HI expert ,
oracle 11g ASM RAC under OL 5.6
as per my daily check i found the below error in alert log file
Global Enqueue Services Deadlock detected. More info in file
/home/app/oracle/diag/rdbms/absnl/ABSNL1/trace/ABSNL1_j002_28024.trc.
Dumping diagnostic data in directory=[cdmp_20130422084345], requested by (instance=1, osid=28024 (J002)), summary=[abnormal process termination].
Errors in file /home/app/oracle/diag/rdbms/absnl/ABSNL1/trace/ABSNL1_j002_28024.trc:
ORA-12012: error on auto execute of job 41
ORA-00060: deadlock detected while waiting for resource
ORA-06512: at "ABS.BROKER_SYS", line 60
ORA-06512: at line 1
ORA-06512: at "ABS.BROKER_SYS", line 2897
ORA-06512: at "ABS.PROCESS_PSA", line 218
ORA-04088: error during execution of trigger 'ABS.PROCESS_PSA'
ORA-06512: at "ABS.SOLD_SUBS_TRANSFER", line 41
ORA-06512: at line 1what the reason of this error ? how can i solve it? how can i avoid it?

First of all, you should always post your four digit version number. '11g' is a marketing label, not a version number.
Secondly: you should look up errors online. It is not sufficient to just hit copy and paste!
Finally: ORA-0060 is always an application problem.
You should identify the problem in the application and change the application or have the application changed.
The statement in error -you would have known that if you would have done research on ora-0060- will be in the alert log.
Sybrand Bakker
Senior Oracle DBA

IR Report Search - ORA-20001: get_dbms_sql_cursor error ORA-00936: missing expression

Hi All,
I had created a IR report based on a table and it was working with no issues. But after few days, when I try searching using the IR search bar it shows "ORA-20001: get_dbms_sql_cursor error ORA-00936: missing expression" error message. I don't see any debug messages or errors in the debug window. The Finder drop down is empty too, there are no columns displayed to filter.
When I recreate the IR report(new page) based on the same table, It works fine and there are no issues with the search. But the old IR report search doesnt work. I have not modified the any thing in the old report after initial creation. Report uses Primary key based on a sequence.
What might have caused this issue?
Is there a way to intercept the search query from IR report?
Apex version - 4.2.3.00.08.
Any help on this appreciated.
Thanks,
Jagan

Hi MK, as I had mentioned in my post, I don't see any logs in the debug window, query tab.
Can you please guide me how to check the query logs on search?
Thanks,
Jagan

Error handling function: ORA-20001: get_dbms_sql_cursor error:ORA-00942: table or view does not exist is not trapped. Why?

Why APEX 4.1 Error handling function does not trap the error of missing table?
Say, I create simple application with single IR report page and I also assign standard simple error handling function.
Function works perfectly, except but this case:
If I just drop a table used by report page and then refresh the page I am getting usual APEX error message:
ORA-20001: get_dbms_sql_cursor error ORA-00942: table or view does not exist
and error handling function is not invoked at all.
Is this a feature or a bug?

Hi,
Check the corrections given in the note 990764:
Reason and Prerequisites
Up to now, using a characteristic with its own master data read class as the InfoProvider was not supported. This is now released but it is not available for all modelings. Using the attributes in the query is not supported for characteristics that have their own master data read class. Using the attributes in the query causes a termination. The following errors may occur in this case:
ORA-00942: table or view does not exist
Fehler in CL_SQL_RESULT_SET Include NEXT_PACKAGE
RAISE_READ_ERROR in CL_RSDRV_VPROV_BASE
Solution
SAP NetWeaver 2004s BI
Import Support Package 11 for SAP NetWeaver 2004s BI (BI Patch 11 or SAPKW70011) into your BI system. The Support Package is available once Note 0914305 "SAPBINews BI 7.0 Support Package 11", which describes this Support Package in more detail, has been released for customers.
In urgent cases you can implement the correction instructions.
The correction instructions contain the tightened inspection for characteristics.
Regards,
Anil Kumar Sharma .P

Shutdown immediate hangs ORA-12012, ORA-12008, ORA-06512

Similar Messages

Maybe you are looking for