4.1 Error Handling Confusing

Hi Everyone,
I have a few pages running under 4.1 that are generating errors that look like this:
Error     Error processing condition.
ORA-01403: no data found
Technical Info (only visible for developers)
is_internal_error: true
apex_error_code: APEX.CONDITION.UNHANDLED_ERROR
ora_sqlcode: 100
ora_sqlerrm: ORA-01403: no data found
error_backtrace:
ORA-06512: at "SYS.WWV_DBMS_SQL", line 904
ORA-06512: at "APEX_040100.WWV_FLOW_DYNAMIC_EXEC", line 588
ORA-06512: at "APEX_040100.WWV_FLOW_CONDITIONS", line 148
It is very confusing to me as to what component on the page is triggering this error. Does anyone have any insight on how to decipher this?
Thanks,
Jeff

Hi Patrick,
I was going through your post http://www.inside-oracle-apex.com/apex-4-1-error-handling-improvements-part-1/ for error handling. I am able to handle many errors but how do I handle this error in function apex_error_handling_example. when such error occurs it does not even reach till this function defined at application level
I have report using dynamic pl/sql returing query. If my parameters are invalid then query of report fails with error
"failed to parse SQL query:
ORA-02019: connection description for remote database not found"
I tried to check if error reaches till apex_error_handling_example by inserting p_error.apex_error_code in some dummy table inside this function but whenever this error occurs no records created in dummy table
If i use exception handling at query level of report then it logs error as "APEX.REGION.UNHANDLED_ERROR"
Is there any way I can handle/capture this error at application level and display custom message to user ?
I am using apex 4.1
Pls help/advice.

Similar Messages

  • Issue with SRDemo error handling

    Hi All,
    Glad the forums are back up and running. In debugging some error-handling issues in our own application, I found an issue in the error handling code of SRDemo. I thought I'd post the issue here, as many of us (myself included) use some SRDemo code as the basis for our own applications.
    The issue can be found in the oracle.srdemo.view.frameworkExt.SRDemoPageLifecycle class, specifically in the translateExceptionToFacesErrors method. I'll show the code that has the issue first, and explain the issue afterwards:
            if (numAttr > 0) {
                Iterator i = attributeErrors.keySet().iterator();
                while (i.hasNext()) {
                    String attrNameKey = (String)i.next();
                     * Only add the error to show to the user if it was related
                     * to a field they can see on the screen. We accomplish this
                     * by checking whether there is a control binding in the current
                     * binding container by the same name as the attribute with
                     * the related exception that was reported.
                    ControlBinding cb =
                        ADFUtils.findControlBinding(bc, attrNameKey);
                    if (cb != null) {
                        String msg = (String)attributeErrors.get(attrNameKey);
                        if (cb instanceof JUCtrlAttrsBinding) {
                            attrNameKey = ((JUCtrlAttrsBinding)cb).getLabel();
                        JSFUtils.addFacesErrorMessage(attrNameKey, msg);
                }Now, this bit of code attempts to be "smart" and only show error messages relating to attributes if those attributes are in fact displayed on the screen. It does so by using a utility method to find a control binding for the attribute name. There are two issues with this code, one obvious, and one that is a bit more subtle.
    The obvious issue: if there is a binding in the page definition, it doesn't necessarily mean that the attribute is shown on the screen. It's a good approximation, but not exact.
    The other issue is more subtle, and led to errors being "eaten," or not shown, in our application. The issue comes if you are using an af:table to display and update your data. In that case, the findControlBinding will not find anything for that attribute, since the attribute is contained within a table binding.
    Just posting this as a word to the wary.
    Best,
    john

    somehow, this message got in the wrong thread....
    Hi Frank,
    Yes, I simply scripted it out this way to contrast the behaviour if the first attribute was read-only vs not read-only. I found the issue on a page in our app that was simply drag-and-drop the VO from the data control on the page.
    It's quite annoying, because our particular use case that hit this error is a "save" button on the page. If the commit operation doesn't return any errors (and it doesn't in this use case!), we add a JSF message saying "save successful" - then the attribute errors are further added later in the page lifecycle, so we get 3 messages: "Save successful" and "Fix this error" and "Tried to set read-only attribute" - quite confusing to the end-user when the only message they should see is "fix this error."
    At any rate, the fix is to simply re-order the attributes in the page definition - that doesn't affect the UI at all, other than to fix this issue.
    John
    it was supposed to be something like:
    Hi Frank,
    Thanks for the reply. I was simply posting this here so that people who use the SRDemo application techniques as a basis for developing the same functionality in their own apps (like me) can be aware of the issue, and avoid lots of head-scratching to figure out "what happened to the error message?"
    John

  • How to activate Forward Error Handling in SRM

    Hello Gurus,
    I got an requirement to activate Forward Error Handling in SRM. I have searched on SDN but didn't find appropriate answer on it.
    Even I found some link: PI/XI: Forward Error Handling (FEH) for asynchronous proxy calls with the use of Error and Conflict Handler (ECH)
    It explains me some points like activating FEH from SRM in SPRO. I have activated the same, plz check the screen shot:
    It also follows some development for the same.
    Here my concern is, should I follow this document? Does it applicable to all to all the scenarios?
    Step 8: it assign object id and type what does it mean...
    Does any one can explain me in detail..... Please provide me any document to configure the FEH in SRM.
    I am trying to implement FEH in my SRM system. So that when even XML fails due to error, I should be able to reprocess/restart it with some editing to the XML.
    My receiver interface for XML is PurchaseRequestERPSourcingRequest_In
    I think this is standard one and no need to make any custom code for it. SAP has all ready given solution for it with some Configuration.
    I have made some configurations like:
    The view FEHV_ACTIVE must have the status active.
    In transaction /SAPPO/LOGSYS , the logical system must be defined for the software component SRM-EBP-ESA .
    As stated in in the link :
    http://esworkplace.sap.com/socoview%28bD1lbiZjPTAwMSZkPW1pbg==%29/render.asp?id=2BAABCB0D30111DC2B8D000F20FCB6A9&fragID=…
    Also I have made some configuration according to the Note: 1973768 - No reprocess option is available in FEH for failed in XML in SRM
    Resulted, the “Process” button get activated in the XML Post Processing screen.
    But can I reprocess my XML with edited value from there..?
    All the  configuration part of PI  is already done .
    I wanted to know  about the  FEH  Part. what are the  steps   i am  missing  or where  i am  going  wrong ?
    Please let me help.
    Thanks
    Regards
    Karan

    Dear Raz,
    I have gone with above mentioned note, it explains about creating Custom Proxy and configuration with PI scenario. Even the link in my previous post, explains about the custom proxies and configuration..
    I think I should must be descriptive about my issue.
    I am trying to implement FEH in my SRM system. So that when even XML fails due to error, I should be able to reprocess/restart it with some editing to the XML.
    My receiver interface for XML is PurchaseRequestERPSourcingRequest_In
    I think this is standard one and no need to make any custom code for it. SAP has all ready given solution for it with some Configuration.
    I have made some configurations like:
    The view FEHV_ACTIVE must have the status active.
    In transaction /SAPPO/LOGSYS , the logical system must be defined for the software component SRM-EBP-ESA .
    As stated in in the link :
    http://esworkplace.sap.com/socoview%28bD1lbiZjPTAwMSZkPW1pbg==%29/render.asp?id=2BAABCB0D30111DC2B8D000F20FCB6A9&fragID=…
    Also I have made some configuration according to the Note: 1973768 - No reprocess option is available in FEH for failed in XML in SRM
    Resulted, the “Process” button get activated in the XML Post Processing screen.
    But can I reprocess my XML with edited value from there..?
    Can any one tell me, what are the steps I am missing here. As this is my first time to implement FEH, I am confused.
    Please let me help.
    Regards,
    Chandan

  • BPM error handling

    Hi,
    I've read many messages on this forum regarding BPM error handling but am still a little confused.
    In my scenario the BPM is quite simple. All it does is Call web service (synchrous) then transform and then call another web service synchronous.
    Now , If any call to the two web services fails , I would like to be able to restart the two calls... now if they fail again, I would like to be able to restart the two calls again... until they work. But each time the restart would be done manualy in the BPM monitoring transactions.
    The way I understand the error handling
    if I put my synchronous send steps and transformations in a step and catch the exception they throw , I can send myself an alert and then throw another exception which I dont handle. This way , since that exception is not handled , it will set the process in error and I can restart the process later.
    However , how can I set it up so that when I restart the bpm , both calls are done again and the same exception handling happens.
    Now , when I restart, it seems only what comes after the block and the exception is executed. If I put the sync send calls in the exception handling branch, that will allow me to run the send steps once after an exception...
    Thanks.

    Even if I don't throw the exception and its a System error on the synchonous call, the BPM is in error but the next call will
    go through...
    I don't know what the point of EOIO was in that case ?
    Even having an Exception branch is enough....you need not compulsorily have anything in it.....so when an exception occurs in your Sync step the control goes to the Exception Branch of the Block....but since there is no step defined in the branch nothing happens.....and the Control then passes to the next branch as in a normal flow.....
    Since the Exception branch is defined the BPM will not wait/ stop/ error-out if any thing goes wrong in the Sync Send step.....it will continue....this is the normal behavior....an error entry will however be shown...if you want that your process stops if the Sync Send fails then have a Control Step (Action--> Cancel Process) in the Exception Branch
    Regards,
    Abhishek.

  • Asynchronous Error Handling in Flex

    Hi,
    When going through the Error Handling in Flex from Adobe site, i got confusion in understanding Asynchronous Way of
    Error Handling Mechanish in FLEX .
    Here the authro Mentiones an example related to File Uploading that is for FileReference class .
    I am not quite familiar with File Uploading , so i could not able to gran this concept .
    Please let me know what is this Asynchrnous Way of Error Handling in FLEX , because as far is synchronous is concerned it is straight Forward Mechanism .
    Please help me in understanding this Concept.

    Hi,
    This type of error handling means that you will listen for events on the calling instance such as a file reference object. You will use the method addEventListener() and listen for events such as IO_ERROR or whatever event the instance will dispatch on error.
    See the documentation for specific error events of each class that acts as a service.
    The async part means that the error if thrown will happen after the line and method executes where you called your service.
    Mike

  • General Error handling

    I've managed to get myself confused with error handling in Forms 6i.
    If I have a trigger that does a 'commit-form' like this
    commit_form;
    IF NOT form_success THEN
    RAISE form_trigger_failure;
    END IF;
    EXCEPTION
    WHEN OTHERS THEN;
    END;
    and the commit_form fails due to a mandatory field being missing (or similar) then what happens first?
    Does my ON-ERROR trigger fire?
    Does the form_success check fail and raise form_trigger failure?
    Does my exception block get used?
    Or does more than 1 happen??
    I could - of course - find the answer to this through debug but I'm looking for a more generic answer if possible.
    Thanks - Sean.

    What happens first?  The forms validation process runs and informs user that the field is required.
    Does On-Error fire?  Yes, if you have one in your form.
    Does the form_success check fail and raise form_trigger failure?  Yes -- but ONLY if your On-error raises Form_trigger_failure.  If it does not, you have lots of problems.
    Does my exception block get used?  Yes.  Raising Form_trigger_failure causes control to pass to the exception handler.  But I never use an exception handler except when I code SQL commands.
    Now...  After commit_form, you should also check Form_Status.  Read the help topic on the Form_Success built-in.
    My standard C00_Commit program unit does this:
      COMMIT_FORM;
      IF :SYSTEM.FORM_STATUS <> 'QUERY'
      OR NOT FORM_SUCCESS THEN
        RAISE FORM_TRIGGER_FAILURE;
      END IF;
    END;

  • General Inquiry Regarding Error Handling with System Exec.vi

    I have a sub vi that uses the System Exec.vi to send SMS messages when triggered. I am confused as to how the error handling works and why all of the errors seem to go to the "standard error" vs the "Error out". The reason I am interested is because I am trying to interrupt the error out of another script to execute a command if error=true.
    I have intentionally created an error to test this, however it does not seem that the signal is ever being sent to the error out, only to the standard error.
    Any help/explanation as to how this works would be greatly appreciated.

    The Facebook discussion board is just a pilot and that functionality is not available yet (as to my knowledge). You will have to use the actual forum thread to add attachments. You can click the arrow just to the right of thread topic in the Facebook thread and that will take you to the ni.com/forums thread. Or you can navigate here:
    http://forums.ni.com/t5/LabVIEW/General-Inquiry-Regarding-Error-Handling-with-System-Exec-vi/m-p/246...
    Having a look at your VI would help to clarify the error handling issue.
    Daniel K | NI Applications Engineer | Certified LabVIEW Developer

  • Error handling --important and urgetn plzz

    Hi friends ,
    i wnat to know the steps for error handling for the follwoing scnarios . plz help me
       FULL LOAD-- MASTER DATA --- PSA  AND NO PSA   LOAD FAILED
    DELTA LOAD-- MASTER DATA ---  PSA AND NO PSA LOAD FAILED
    FULL LOAD-- TRANSCATIONAL DATA--NO PSA  AND WITH PSA.
    LOAD FAILED
    DELTA  LOAD TRANSACTIONAL DATA -- NO PSA AND PSA  LOAD FAILED .
    plz help  me  how to handle in this type of scnerios. Iam new to Bw and confusing alot in this.
    Points wil be awarded.
    Regards,
    Pavan

    Hi Pavan,
    not sure what exactly you are looking for, but maybe this link will give you some help!
    /people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
    Each error needs it's own treatment, depending on the reason it occured.
    regards
    Siggi

  • General Labview Error Handler question discussion

    Recently two functions were brought to my attention, the General Error Handler and the Simple Error handler. 
    And I cannot wrap my hand around these two features.  While I have been using Labview I have always used the Labview error cluster.  When would you use these two features?  As I feel the cluster error is much help. 
    Maybe it is my defnition that I have confused: 
    The general error handler will display a dialogue box describing the error that will be passed and shuts down the code? 
    The simple error handler notifys the operator that an error has occured but it can be customized for adding functionality, it takes the error cluster input and determines if an error was generated.  "If an error has been generated, the VI displays a dialog box with the error code, a brief description of the error, and the location of the error."   How is this not the same as an error cluster?  
    If anyone has any simple code examples for this or knowledge I greatly appriciate it. 
    Caleb

    Jacobson wrote:
    Psireaper9 wrote:
    The simple error handler notifys the operator that an error has occured but it can be customized for adding functionality, it takes the error cluster input and determines if an error was generated.  "If an error has been generated, the VI displays a dialog box with the error code, a brief description of the error, and the location of the error."   How is this not the same as an error cluster?  
    You are correct that they give the same information.  The difference is that if you want to use an error cluster you will need an indicator on your front panel.  If you use the simple error handler you won't have to have an error cluster on your front panel but the user will be notified if an error does occur.
    Think about all the programs you normally use (excel, chrome, etc.).  As a user you expect that errors aren't happening, and if errors do occur then the application will usually just close out and you get an error dialog about the error.
    I use the simple error handler with no user interaction to extract the error text.  Is there an easier way of doing that?

  • Execution properties, Enable automatic error handling

    Hi
    I am writing real-time code for standalone execution on a cRIO-9074.
    If I untick the "Enable automatic error handling" option in VI properties (Execution), what is the consequence if I have an application with no error handling case structures to detect the occurrence of errors elsewhere and within subVI's ? Does the error just go undetected and the application continue regardless? If ticked, could a standalone application hang as there is no user-interface for the error to get reported automatically to? Can I configure the LabVIEW RTE to automatically handle errors in a certain way regardless of individual VI settings of the "Enable automatic error handling" option?
    I am a bit confused by the usefulness of "Enable automatic error handling" within RT/FPGA code, and where in the development process it is best enabled then disabled (if necessary).
    Thanks

    If I untick the "Enable automatic error handling" option in VI properties (Execution), what is the consequence if I have an application with no error handling case structures to detect the occurrence of errors elsewhere and within subVI's ? Does the error just go undetected and the application continue regardless?
    That's the case: the error is lost (i.e. it's not handled), and the application goes on.
    If ticked, could a standalone application hang as there is no user-interface for the error to get reported automatically to?
    The property "Enable automatic error handling" is not availabe in the run-time engine, so there's no automatic error handling in a built application,
    Can I configure the LabVIEW RTE to automatically handle errors in a certain way regardless of individual VI settings of the "Enable automatic error handling" option?
    No, for the reason stated above.
    I am a bit confused by the usefulness of "Enable automatic error handling" within RT/FPGA code, and where in the development process it is best enabled then disabled (if necessary).
    There's no "Enable automatic error handling" property in Labview RT either.
    Regards,
    Marco

  • How to take control back from service error handler in osb

    I am using osb to send data to multiple services at the same time.since x query is a procedural language if any single operation fails the flow goes to service error handler which calls a BPEL webservice and logs the error in a database but the control doesnt comes back to my code I have tried everything including RESUME,REPLY operations but all in vain similarly i cannot use service callout call to my business service because its not allowing to select my BPEL wsdl operation

    If your statement "the control doesnt comes back to my code" means you expect that your xquery will continue in processing than your expectations are just too high. :-)
    Resume action is supposed to resume the next action in the message flow. It means the action that follows the action which caused an error.

  • Report and Alert don't executed in the error handler with a JMS proxy service

    Hi,
    I'm working with OSB 11.1.1.4.0 and I'm facing a problem with the error handler of my JMS proxy service.
    My error handler contains two main elements :
    - a Report action
    - an Alert with a JMS destination defined
    When the business service failed the message remain in the queue. It's the expected behavior.
    The problem is :
    - the report is missing
    - the alert is raised but missing in the JMS destination defined in the Alert setting.
    I've noticed if I add a Reply with Failure or Success, Report and Alert are successfully executed.
    Unfortunately the message don't remain in the JMS queue.
    What can I do in order to have my report/alert done and the JMS transaction rollback in order to keep the message in the queue ?
    I've already met this problem in the past with alsb v3 and my solution was to add Service Callout in the error handler in order to externalize these actions.
    This solution is not convenient and I hope another solution is possible.

    Inventorying workgroups can be difficult, especially when it comes to remote access and network security. Because workgroups are not centrally managed, some of the items discussed in this
    wiki article on preparing your workgroup environment may require you to visit each machine individually.
    For non-domain credentials, you do not use the <systemname>\<user> format, you simply enter the user name. Regarding how to enter the credentials, if you have an account that uses the same username and password on all machines and is an administrator
    on all of those machines, then you can enter that in the All computers credentials page of the wizard. You can also do this if they are different user names. However, if some machines have an account with the same user name, such as Administrator,
    but different passwords on each machine, you will need to use the Manually enter computer names discovery method, and then enter the information for each group or each machine.
    As you can tell, workgroup environments can quickly negate any benefit that the agentless inventory nature of MAP provides.
    Please remember to click "Mark as Answer" on the post that helps you, and to click
    "Unmark as Answer" if a marked post does not actually answer your question. Please
    VOTE as HELPFUL if the post helps you. This can be beneficial to other community members reading the thread.

  • LV7.1 Strange behavior with Automatic Error Handling occuring when it shouldn't [LV 7.1 Pro on WinXP for Tablet PC's]

    [LV 7.1 Pro on WinXP for Tablet PC's]
    I recently let a rather large LV app of mine run in the development environment while I was out for a couple of days. Upon returning I found that the app had hung for ~22 hours waiting for an answer to an Automatic Error Handling (AEH) dialog proclaiming an Error 7 in New File without any indication of the VI hierarchy that called New File.  I set about ensuring that AEH dialogs would not pop up and have not been able to discover how I could have possibly received one in the first place.
    Subsequent investigation revealed:
    Neither AEH option in Options>Block Diagrams were checked.
    Network problems had occurred around the time that the app had hung.  All file paths are network paths when running in the development environment, so the cause of the error was most likely valid, even if the AEH dialog appearance wasn't.
    My app has only one instance where the New File primitive is used by me. That subVI and all others above it in the hierarchy DO NOT have the AEH property enabled.  The error out cluster of New File in my subvi is wired.
    My app has three instances where New File is called from a vi.lib vi (Open/Create/Replace File.vi, Open Config Data.vi, and Prompt Web Browser Path.vi), none of which have the AEH property enabled.  Nor does any of their calling VI's.  All three instances also have their error out cluster wired.
    A utility to examine the AEH property of all VI's (with all top level and dynamic VI's loaded) in memory reported that only 1 of 308 vi's ( RGT Does File Exists.vi from the Report Generation Toolkit) had that property true.  That vi has no subVI's other than the File/Directory Info primitive and no calling VI's in common with any of the vi's that call New File, except a top level VI.
    As long as 'Enable automatic error handling dialogs' remains unselected in options>block diagram, I am unable to get an AEH dialog for either the New File or File/Directory Info primitives in a test VI with AEH property enabled and their error out clusters unwired no matter what invalid path I pass to the functions.  As soon as the options>block diagram>Enable AEH dialogs' is selected, both primitives fire AEH dialogs with no error out wired and don't when wired. i.e. works as advertised.
    In other words I can find no reason why I should have gotten the problem AEH dialog...
    I cannot afford for this app to hang because of a network problem, other portions of the app that were running concurrently correctly handled the error and, had the AEH dialog not appeared, the app would have made corrections or shutdown in an orderly fashion.
    Any ideas?

    Very good.
    Write Characters to File.vi>Open/Create/Replace File.vi>New File
    New File throws the error.  Open/Create/Replace strips the hierarchy from the source of the error.  Write Characters passes it to the General Error Handler.  I never looked above O/C/R file in the hierarchy except for enable automatic error handling property.  The tip-off should have been to realize that O/C/R file was stripping the hierarchy from the error and look above that. 
    The real irony is that Write Characters was being used to log error cluster data to an error log file...
    Save as... Copy without updating... the OEM 'Write Characters to File' is gone from this app.
    Thanx (a bunch)

  • Error handling in process chain-doubts

    Hi ,
    I have some doubts in error handling of process chains.
    1) I have  aprocess load infopackeage and subsequent process is update fromPSA.
    process load infopackage got failed  , so i loaded  the IP manually and repeated the next i.e process update from PSA .
    How to correct the process chain from now?
    2) I have  aprocess load infopackeage and subsequent process is Delete request in infocube .process load infopackage got failed  , so i loaded  the IP manually and repeated the next process i.e Delete request in infocube. Chain continued by deleting the right request . How this is possible ?
    Plz  help me  as this is urgent and daily i have to deal with this  issues. If any documents on error handling is greatly appreciated.
    My mail id is [email protected]
    Regards,
    Pavan

    Hi Pavan,
    Hope the following links will give u a clear idea about process chains and clear ur doubts.
    Business Intelligence Old Forum (Read Only Archive)
    http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/c08b3baaa59649e10000000a11402f/frameset.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/8da0cd90-0201-0010-2d9a-abab69f10045
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/19683495-0501-0010-4381-b31db6ece1e9
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/36693695-0501-0010-698a-a015c6aac9e1
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9936e790-0201-0010-f185-89d0377639db
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3507aa90-0201-0010-6891-d7df8c4722f7
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/263de690-0201-0010-bc9f-b65b3e7ba11c
    /people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
    Errors in monitoring of process chains can be categorized into 4 different sections...
    Master data - Full Update
    Master data - Delta Update
    Transaction data - Full Update
    Transaction data - Delta Update.. in terms of loading of data which can be due to server shut down or system maintenance... errors due to incorrect entries in the OLTP system in which case you'll have to fix the errors in the PSA and manually load the data...
    Otherwise it can have errors on Attribute change run being locked by some other job... Aggregate Roll up failing because of attribute change run being run at the same time... Problem with hierarchies and save hierarchies...
    There can be problems with the data store activation if the ODS object contains any incorrect request sitting inside it... then, you need to delete the incorrect request and reload the data again...
    In case of Transaction Delta failure, you'll have to request for a repeat either manually in the infopackage or using the repeat option if available on right clicking the load event...
    For Master Data Delta failures, you need to do an Re-init by deleteing the previous initalization condition in the "initalization option for source systems" in the menu scheduler or reschedule the enitre chain... because, master data generally do not support repeat of last delta ...
    U can even look into these links:
    /people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
    For common data load errors check this link:
    /people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
    ****Assign Points if Helpful****
    Regards,
    Ravikanth.

  • 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

Maybe you are looking for

  • Flash player does not work properly on Windows 7 32 bits

    Hello, My flash player does not work properly on Windows 7 32 bits with Firfox and IE8 (lasts versions). My Flash player version : 10.0.45.2, but I tried with version 9 too, with same problems. I have tried to uninstall, reboot, reinstall several tim

  • How to see dbms_output on oracle sql developer

    ned immediate help how to see dbms_output on oracle sql developer

  • Animating gif problem in ps elements 7.0

    I am trying to save a file as an animated gif... and when I click to save as a gif, then check the box to save layers as frames, then click save, it doesn't prompt me to the animation window where I select the animation, loop, and speed. How can I ge

  • Oraclient9i.dll error in multi threaded delphi server application

    I created a multi threaded server application in delphi using oracle9i and indy server components. When I run my application, I am getting an error "oraclient9i.dll" error when executing my SQL statements. I have check communication between my server

  • How to  Access Data using ContentRepositoryConnector

    Hi All, I am trying to access a document using the ContentRepositoryConnector.  I am getting exception CRC Exception:  ALC-CRX-030-003-Repository Fault. The server log shows that the connection is being refused: 2012-07-12 10:23:16,425 INFO  [com.ado