FRM-93652 is a generic error thrown by the Forms Servlet when it doesn’t know what the error is. Thus, causes of this error can range from multiple reasons. Below are causes of the error:

  1. In Forms 12c, there have been known issues where some Windows PCs (usually on VMs) will encounter the FRM-93652 error when running any form locally on startup. This is usually seen when an environment file other than default.env is configured locally on the PC with Oracle Forms and Reports 12c installed. The solution is to go into the custom env file (app.env, pitsscon.env, etc.) and comment out the PATH environment variable. After saving all changes, relaunch the Forms application, and the problem should disappear.
  2. Error was occurring whenever a certain button was being pressed on a menu. The menu file had a property called “Share Library With Form”. When set to “no”, the error occurred. When set to “yes”, there was no error.
  3. There were multiple versions of the same libraries and menus in the FORMS_PATH. There were 3 paths in the FORMS_PATH which same libraries and menus were in all 3 paths. Removed any extra versions, error went away.
  4. There has also been a known issue where clicking on the “Execute Query” button (or a similar button) in the toolbar, the FRM-93652 error will occur. However, it does not occur if using a keystroke such as F8. To fix this, there is an RDBMS patch which needs to be applied to the Forms environment. This can be accomplished by the following steps:
    • Download patch 11741170 from My Oracle Support.
    • Shut down all instances of WebLogic in the Oracle home such as all WebLogic servers, OPMN, Node Manager, etc.
    • Extract the patch.
    • Open up Command Prompt as an administrator.
    • Set the following environment variables in Command Prompt:
      • ORACLE_HOME (for Oracle Forms, not for Oracle Database if installed)
      • set PATH=%PATH%;%MIDDLEWARE_HOME%\oracle_common\OPatch
    • Run “opatch version” and “opatch lsinventory” to ensure that the patch hasn’t been installed already and that the OPatch version is at least 11.1.0.6.2 or higher.
    • When step 6 is satisfied, go to the extracted patch location and inside the 11741170 directory.
    • Run “opatch apply” to apply the patch.
    • Answer ‘y’ for all questions asked.
      • NOTE: If you run into an error where OPatch is unable to copy/replace oci.dll, rename the oci.dll to oci.dll.bak in %ORACLE_HOME%\bin and manually copy the oci.dll from the %PATCH_TOP%\11741170\files\bin to %ORACLE_HOME%\bin. NOTE: If you are unable to rename the original oci.dll, restart the PC/server and try again. Once it is manually copied, the rest of the patch installation will succeed although you may get a warning that the oci.dll could not be copied. You can ignore this as the file was copied manually. Source: Oracle Support note 294350.1
    • Once the patch has been applied, start up all WebLogic services.
    • Test to see if the problem has disappeared. The FRM-93652 error should no longer occur.
    • Source: Oracle Support note 1096125.1