Fatal Pl/sql Error Occured . Ora-01403 No Data Found
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about ora-01403 no data found in oracle forms Stack Overflow the company Business Learn more about hiring developers or posting ads with ora-01403 no data found in package us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is ora-01403 no data found ora-06512 a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Oracle PL/SQL - ORA-01403 “No data found” when using “SELECT INTO” up vote 4 ora-01403 no data found select into down vote favorite I faced this problem while developing a Trigger in Oracle: ORA-01403: no data found. I did some research and understood the root of the problem. Nevertheless handling the error exception prevents the above error, but does not solve my problem. What I am currently looking for is an optimal workaround to perform the lesser query amount/achieve the best performance as possible. I'll try to describe the scenario
Ora-01403 No Data Found In Oracle Apps
creating simple examples to the real structure. Scenario I have a "date reference" table to establish periods of time, say: CREATE TABLE DATE_REFERENCE ( DATE_START DATE NOT NULL, DATE_END DATE NOT NULL, -- Several other columns here, this is just a silly example CONSTRAINT PK_DATE_REFERENCE PRIMARY KEY(DATE_START, DATE_END) ); When the trigger is triggered, I'll have one DATE field - say DATE_GIVEN (for example sake). What I need is: To find the DATE_REFERENCE row in which DATE_GIVEN BETWEEN DATE_START AND DATE_END (easy); OR If the previous option returns no data, I need to find the next closest DATE_START to DATE_GIVEN. In both cases, I need to retrieve the row with all columns from table DATE_REFERENCE, no matter if it matches Opt 1 or 2. That's exactly where I faced the problem described. I wrote this test block to test and try to find a solution. The example below is not working, I know; but it is exactly what I want to accomplish (in concept). I have added comments like -- Lots of code to make clear that will be part of a more elaborate trigger: DECLARE DATE_GIVEN DATE; RESULTROW DATE_REFERENCE%ROWTYPE; BEGIN -- Lots of code -- Lots of code -- Lots of code DATE_GIVEN := TO_DATE('2014-02-26 12:30:00', 'YYYY-M
Exception Handling Raised Exceptions Useful Techniques There is nothing more exhilarating than to be shot at without result. Winston Churchill Runtime errors arise from design faults, coding mistakes, hardware failures, and
Ora-01403 No Data Found Exception Handling
many other sources. Although you cannot anticipate all possible errors, you can ora 01403 no data found apex plan to handle certain kinds of errors meaningful to your PL/SQL program. With many programming languages, unless you disable ora 01403 no data found in forms error checking, a runtime error such as stack overflow or division by zero stops normal processing and returns control to the operating system. With PL/SQL, a mechanism called exception handling lets http://stackoverflow.com/questions/22026100/oracle-pl-sql-ora-01403-no-data-found-when-using-select-into you "bulletproof" your program so that it can continue operating in the presence of errors. Overview In PL/SQL, a warning or error condition is called an exception. Exceptions can be internally defined (by the runtime system) or user defined. Examples of internally defined exceptions include division by zero and out of memory. Some common internal exceptions have predefined names, such as ZERO_DIVIDE and https://docs.oracle.com/cd/A57673_01/DOC/server/doc/PLS23/ch6.htm STORAGE_ERROR. The other internal exceptions can be given names. You can define exceptions of your own in the declarative part of any PL/SQL block, subprogram, or package. For example, you might define an exception named insufficient_funds to flag overdrawn bank accounts. Unlike internal exceptions, user-defined exceptions must be given names. When an error occurs, an exception is raised. That is, normal execution stops and control transfers to the exception-handling part of your PL/SQL block or subprogram. Internal exceptions are raised implicitly (automatically) by the runtime system. User-defined exceptions must be raised explicitly by RAISE statements, which can also raise predefined exceptions. To handle raised exceptions, you write separate routines called exception handlers. After an exception handler runs, the current block stops executing and the enclosing block resumes with the next statement. If there is no enclosing block, control returns to the host environment. In the example below, you calculate and store a price-to-earnings ratio for a company with ticker symbol XYZ. If the company has zero earnings, the predefined exception ZERO_DIVIDE is raised. This stops normal execution of the block and transfers control to the exceptio
Technology and Trends Enterprise Architecture and EAI ERP Hardware IT Management and Strategy Java Knowledge Management Linux Networking Oracle PeopleSoft Project and Portfolio Management SAP SCM Security Siebel http://oracle.ittoolbox.com/groups/technical-functional/oracle-apps-l/rep1401-cf_supplier_faxformula-fatal-plsql-error-occurred-ora06502-plsql-numeric-or-value-error-5302309 Storage UNIX Visual Basic Web Design and Development Windows < Back CHOOSE A DISCUSSION GROUP Research Directory TOPICS Database Hardware Networking SAP Security Web Design MEMBERS Paul_Pedant DACREE MarkDeVries MacProTX Inside-ERP VoIP_News Inside-CRM I_am_the_dragon maxwellarnold Michael Meyers-Jouan TerryCurran Chris_Day Andrew.S.Baker Ramnath.Awate JoeTorre Locutus Dennis Stevenson bracke Craig Borysowich DukeGanote Richard PCMag mircea_luca Nikki Klein iudithm AbhaiTripathi knowscognosdoi Clinton Jones Iqbalyk bluesguyAZ59 COMPANIES Dell Software no data Panaya Inc. Oracle VAI View All Topics View All Members View All Companies Toolbox for IT Topics Oracle Groups Ask a New Question Oracle Applications Your premier resource for objective technical discussion and peer-to-peer support on Oracle Applications. Home | Invite Peers | More Oracle Groups Your account is ready. You're now being signed in. Solve problems - It's Free Create your account in seconds no data found E-mail address is taken If this is your account,sign in here Email address Username Between 5 and 30 characters. No spaces please The Profile Name is already in use Password Notify me of new activity in this group: Real Time Daily Never Keep me informed of the latest: White Papers Newsletter Jobs By clicking "Join Now", you agree to Toolbox for Technology terms of use, and have read and understand our privacy policy. REP-1401: 'cf supplier faxformula': Fatal PL/SQL error occurred & ORA-06502: PL/SQL: numeric or value error Princess777 asked Aug 30, 2013 | Replies (12) HI, When I run the report, I get the REP-1401: 'cf_supplier_faxformula': Fatal PL/SQL error occurred & ORA-06502: PL/SQL: numeric or value errors. Log File Output as below. +------+ 1PWR Custom Applications: Version : UNKNOWN Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved. PWR_POXPRPOP_P module: PWR ES Printed Purchase Order Report(Portrait) +-------+ Current system time is 29-AUG-2013 13:19:06 +-----+ +---- | Starting concurrent program execution... +--- Arguments ------------ P_report_type='R' P_po_num_from='N9911342' P_po_num_to='N9911342' P_print_releases='Y' P_user_id='29939' P_QTY_PRECISION='3' P_fax_enable='N' P_CANCEL_LINE='Y' P_BLANKET_LINES='Y' P_PACK_INS='YES' P_SHIP_INS='YES' P_DISPLAY_VAT='N' P_COMMENTS='1' P_SEND_EMAIL='N' P_PO_OLD_DAYS='2' ------------ Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are : American_America.WE8ISO8859P1 '.,' MSG-000