FRM-93652 or Crash Only on One Specific Machine
(Doc ID 2445379.1)
Last updated on MAY 08, 2020
Applies to:Oracle Forms - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
One of the most challenging Forms problems to troubleshoot is the FRM-93652 error. Normally, an FRM-93652 is seen by the end user but related errors may be seen in the formsapp-diagnostic.log.
This error always mean that the frmweb process associated with the users session has crashed. Seldom does the error message point to the exact cause of the crash.
<Note 2327287.1> discusses how to troubleshoot these types of errors.
The purpose of this document is to address an even more difficult to diagnose situation. This is when a Form works perfectly on one machine but crashes with an FRM-93652 on another machine. Fortunately, these scenarios are not common but when they do occur diagnosing the cause or finding a fix is often a long term process. The typical case is where a customer has several environments such as Development, Test and Production and the problem only happens in one of them. The purpose of this note is to point out possible causes as well as to provide troubleshooting guidance and potential solutions.
Note that this document assumes that the issue is with a Form module and this is most the case. But it could apply to a library or menu module so identifying the core source module is key.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document