Discussions
Categories
- 385K All Categories
- 2.5K Data
- 568 Big Data Appliance
- 2K Data Science
- 452K Databases
- 222.3K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 32 Multilingual Engine
- 573 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 575 SQLcl
- 4K SQL Developer Data Modeler
- 187.7K SQL & PL/SQL
- 21.5K SQL Developer
- 10 Data Integration
- 10 GoldenGate
- 297.6K Development
- 3 Application Development
- 18 Developer Projects
- 140 Programming Languages
- 294.2K Development Tools
- 118 DevOps
- 3.1K QA/Testing
- 646.3K Java
- 30 Java Learning Subscription
- 37K Database Connectivity
- 185 Java Community Process
- 107 Java 25
- 22.1K Java APIs
- 138.3K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 21 Java Essentials
- 172 Java 8 Questions
- 86K Java Programming
- 82 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 206 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 573 LiveLabs
- 41 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 190 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 240 Portuguese
FRM-93652 Error When Try To Query
Hello
I'm migrating forms from version 11g to 12.2.1.2, and I'm getting an FRM-93652 error every time I try to run a query on the form,
Queries run fine when the exact value to search for is entered but fail when trying to enter %123% or a value that does not exist
Answers
-
Have you installed any patches? Looks like there is a few bugs on the base version. it might be worth trying them or upgrading to 12.2.1.3
eg: Patch 25794361: FRM-93652 AFTER PATCH 25766598
-
Extending what @Quentin van Heerden said, the latest version is 12.2.1.4. Versions older are no longer recommended. Also note that we are now releasing quarterly patches for the latest Forms version. So if you move to 12.2.1.4, I also recommend installing the latest patch.
Refer to the following for the latest information (and downloads) related to Forms:
https://www.oracle.com/application-development/technologies/forms/forms.html
-
Thank you I followed your recommendations to update to 12.2.1.4 and this time I got the error "frm-1403 ora-01403 no data found"
-
When you reply, please include details. What exactly are you doing when you see this error? Which DB version are you using?
Regarding ORA-01403, this is encouraging. Forms is no longer crashing and your query is returning now data. So now you have a working form and you just need to fix the code that creates the query.
-
What exactly are you doing when you see this error? -When starting the form
with the previous version of 12.2.1.2, the data was displayed in the same form What database version are you using? - I use database 12.2.0.1.0
-
The error message (screenshot) suggests that you have you own ON-ERROR trigger and are overriding the Forms default processing. For troubleshooting, I recommend not using that so the complete error as reported by Forms and/or the DB can be seen and understood. To do this, simply rename ON-ERROR to another trigger that you are not using. For example, rename it KEY-HELP.
Once you have more information about the error you may understand why there is this result. Also, if this is happening at startup, look closely at your startup triggers (e.g. PRE-FORM, WHEN-NEW-FORM-INSTANCE, etc). Be sure you are not attempting to read/write to objects that are rendered visible at startup. In other words, do not try to read the value of :TEXT_ITEM1 in a PRE-FORM trigger. Since the UI has not been rendered yet, there is a chance that the value may not be set until later in the process, for example in WHEN-NEW-FORM-INSTANCE. PRE-FORM should only be used to perform non-UI tasks.
-
I'm glad you managed to get it upgraded.
I think Micheal' reply are spot on why you are getting the error. Adding to that you need to ask the question on what do you do when no data is found. Can you use default value or do you need to prompt the user that none was found and they must try again.
-
I followed the recommendation to rename the ON-ERROR trigger, and the error message is still the same, the same form with the previous version 12.2.1.2, it showed the data without any problem
-
You likely did not delete the old FMX file and/or did not generate a new one that included your changes. Understand, that the purpose of this change is not to solve your issue. It is for troubleshooting purposes. The expectation is that a more detailed error message may be presented.
