My Oracle Support Banner

Impact of Forms RSF Change on Forms Development/Deployment - PDE-PEP006 or FRM-40011 (Doc ID 2256898.1)

Last updated on NOVEMBER 02, 2023

Applies to:

Oracle Forms - Version and later
Oracle Forms for OCI - Version and later
Information in this document applies to any platform.


Forms will ship with an upgraded version of the Required Support Files (RSFs). Previous versions of 12c (,, shipped with RSFs.  Forms will ship with RSF files. This version of the RSFs will offer a number of improvements (stability and otherwise) to the product.

With the upgrade of the RSFs to a 12.1 version, there will be changes in the way Forms will behave related to earlier versions of Forms.

Additionally, will have new features that previous versions did not.  This is an additional reason why it will not be compatible with earlier 12c runtime environments.


Once a pre- 12c Form is brought into Forms Builder it will be upgraded to and the RSFs will be upgraded to What this means is that the upgraded Form cannot be re-opened in an earlier version of 12c Forms Builder.  (One can convert the upgraded Form to xml using the xml converter for and back to with the xml converter to resolve this but this is not supported).

For example, a simple Form with a button trigger with a “message(‘hello world’);” in it will core dump when attempting to compile it using the utility.
In the builder, this error will occur: “PDE-PEP006 Encoded Program Unit has an unknown format.”

Note. This won’t necessarily apply to very simple Forms with no triggers. For example, a simple wizard created emp fmb opened in Forms Builder will normally show no issues.


Copying Binaries to Another Machine

Although this has never been supported, it is not uncommon for customers to copy their binaries (fmx, mmx, plx) to a different machine of the same OS and run them there as long as the deployed version of Forms is in the same version family. See <Note 1300396.1>. Because of the upgraded RSFs in and also the fact that new features have been added to, in the majority of cases copying binaries (fmx, mmx, plx) to a different machine of the same OS will cause unexpected, negative behavior. As documented in the following note, customers should regenerate their forms on the target OS from the source files (fmb,mmb, pll).

<Note 299938.1>  Moving Forms Applications From One Platform Or Machine To Another.

Bottom Line: For,  the Development and Deployment environments both be If customer's need to maintain both and pre- versions/environments, strict configuration management measures must be implemented to keep the versions separate in order to avoid the issues mentioned in this note.  The following are some demonstration scenarios that show example puzzling behaviors that may occur if versions are mixed:

Example 1: Create a simple form on Windows (no triggers) and add a new feature – Row Band Frequency, for example. If one generates the .fmx and moves the fmx to a Windows machine the form will run with no errors. However, Row Band Frequency will not work since it is a specific feature.

Example 2: Create a button trigger with a simple message(‘hello world’); in it.  Generate the fmx on windows and move the .fmx to on windows. The form will run and the button will appear but will NOT execute.

Example 3:  Attempt to run a fmx in a runtime environment and the following will be seen: 

FRM-40011 : Form was created by an old version of Oracle Forms

This expected. The environment will only run Forms generated by a compilation ( Forms Builder or frmcmp/frmcmp_batch).



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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.