How to Replace Forms Runtime Files in Production Environments 'On The Fly'
Last updated on SEPTEMBER 07, 2014
Applies to:Oracle Forms - Version 6.0.8 and later
Information in this document applies to any platform.
Checked for relevance 02-Apr-2011
This document describes how to replace forms runtime modules without bringing
down the Forms Runtime Environment (OC4J_BI_Forms Instance in 10g/11g and Forms
Server or jserv in earlier releases) in production systems where the parameters
FORMSXX_MMAP can not be used.
On Unix, when you replace the runtime files in the OS level, then the
sessions that are already using these modules will be disconnected with the
following error message :
FRM-92101: There was a failure in the Forms Server during startup. This could
happen due to invalid configuration.
Please look into the web-server log file for details.
oracle.forms.net.ConnectionException: Forms session aborted: unable to
communicate with runtime process
at oracle.forms.net.ConnectionException.createConnectionException(Unknown Source)
at oracle.forms.net.HTTPNStream.getResponse(Unknown Source)
at oracle.forms.net.HTTPNStream.doFlush(Unknown Source)
at oracle.forms.net.HTTPNStream.flush(Unknown Source)
at java.io.DataOutputStream.flush(Unknown Source)
at oracle.forms.net.StreamMessageWriter.run(Unknown Source)
On Windows, when trying to copy the file, the following error appears :
Cannot copy MODULENAME: The requested operation cannot be performed on a file
with user-mapped section open.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms