FRM-92100




Applies to:

Oracle Forms - Version: 6.0 and later   [Release: 6 and later ]
Information in this document applies to any platform.
***Checked for relevance on 12-DEC-2011***

Symptoms

Problem
-----------
Certain features of the forms application when accessed throw FRM-92100.

VDSStart component seems to be used (http://solutions.oracle.com/solutions/vds-computing/vdsstart) and throws a java exception in the java console by the time FRM-92100 is raised in the forms runtime.
This VDSStart component is apparently based on HeadStart JHeadStart.

Cause

Apparently, vdsstart.jar was preventing the application from performing properly.

Once vdsstart.jar has been removed from the archive parameter list of jars, the issue did not occur anymore.

vdsstart.jar was supposed to fix a certain focus issue, but in the meantime the fix delivered by vdsstart..jar has been included in either a more recent update of Sun JRE or Forms BP.

Conclusion
-------------
If using JHeadStart  + some 3rd party components provided by VDS Consulting in a Forms 10.1.2.3 application with latest updates for Sun JRE and latest Forms Bundle Patch then it is not necessary to referrence vdsstart.jar anymore.

Solution


1. Contact Oracle Consulting / VDS as these are JHeadStart components, not supported by Oracle Support Organization. If both VDS and Oracle Consulting can come up with a simple setup demonstrating that these components are not causing the disruption, then a potential configuration glitch should be considered and further actions taken in this direction.

2. Remove vdsstart.jar from the config section and test the application.

No comments:

SHRD0014: GLLEZL - process exiting with failure

  SYMPTOMS Journal Import completes with the following error: Error ------ ORA-01653 : unable to extend table GL.GL_IMPORT_REFERENCES ORA-01...