There is a known bug in Oracle Forms 12c that the DATETIME item in Forms is set to a different time than what is configured in the Windows or UNIX server. Oracle Support has reported this issue in AIX, but it has been seen in both Windows and Linux as well. The easiest way to work around this bug is to configure the following environment variable to GMT in your env file (e.g. default.env):


NOTE: Normally when you do not set this variable, the system defaults to GMT, but this is necessary in 12c.

This should correct the time issues, but if for any reason any datetime fields are out of sync still, you may also need to set the following variable to GMT:


Source: Oracle Support document ID 2139346.1

There is a bug in Forms 12c where the Forms application crashes with FRM-93652 errors when calling any forms where data from a record group is populated. Oracle has created a patch to fix this problem. These steps should be followed to fix this problem:

NOTE: This problem is currently only seen in Unix environments (Linux, Solaris, AIX, etc.). It has not been reported in Windows.

  1. Download Oracle Patch 21534616 from My Oracle Support. Make sure to download the version for your server’s OS. NOTE: The patch is technically an Oracle Database patch, version, but this will be used to patch the DB client which comes with the Forms 12c installation.
  2. Extract the patch in your server. Once it is extracted, navigate into the 21534616 folder.
  3. Make sure the following environment variables are set (this assumes the Oracle home is installed in /oracle/middleware/as_1 but it may be different for your environment)
    1. export ORACLE_HOME=/oracle/middleware/as_1
    2. export PATH=/oracle/middleware/as_1/bin:$PATH:/oracle/middleware/as_1/OPatch
  4. Run opatch prereq CheckConflictAgainstOHWithDetail -ph ./ to make sure there are no conflicts or errors. FRM-93652 1                      FRM-93652 2
  5. Shut down all instances inside the Forms 12c domain (all WebLogic servers, OHS, the standalone reports server, and Node Manager).
  6. Run opatch apply to install the patch.                                                                                                                                                                                   FRM-93652 3
  7. Make sure the Middleware Home is the Oracle Home for Forms 12c. If it is, type y to proceed.                 FRM-93652 4
  8. When it asks if the local system is ready for patching, type y and press Enter.                                            FRM-93652 5
  9. You should receive a message that the patch was successfully applied. There will be some warnings, but you may ignore these warnings.
    1. FRM-93652 6
  10. Go to $ORACLE_HOME/forms/lib and run: make -f frmweb_install                                                     FRM-93652 7
  11. If you see the output shown in the following screenshot, the step was run successfully.                         FRM-93652 8
  12. Start up your Forms 12c environment.
  13. Recompile all forms, menus, and libraries.

After applying the steps above, you should no longer encounter FRM-93652 errors when opening up any 12c forms where data from a record group is populated.

NOTE: There is a possibility that you may encounter the error FRM-41337 in the same forms. If you do, you will need to apply another Oracle patch as indicated in

For forms which have been upgraded to 12c from an older version (6i, 9i, 10g, and 11g), there is a known bug where forms using the POPULATE_LIST built-in (the same code used from 6i to 11g) is producing the following error:

“FRM-41337: Cannot populate the list from record group.”

To fix this bug, Oracle has provided a patch, 22184867, which is available to download from My Oracle Support. You must have an active account with My Oracle Support to be able to download patches:

NOTE: The patch is only available for Linux, Solaris on SPARC, and Windows (all 64-bit). If you are experiencing the problem on platforms other than what is listed, please submit an SR to My Oracle Support.

Source: Oracle Support note 2113628.1

IMPORTANT: Downloading JDK and JRE 7 from My Oracle Support requires an account with My Oracle Support.

As of July 14, 2015, JDK 7 and JRE 7 are no longer available for public download. Although the latest version of Oracle Forms, version (11gR2) is supported to use JRE 8, it is currently NOT supported to use JDK 8 for Oracle Forms and Reports 11gR2 as well as for other Fusion Middleware products such as ADF (11g and 12c) and OHS (11g and 12c). However, as public downloads for Java 7 are no longer available, there are only two options to download JDK 7.

One method (requires an Oracle account) is to use the Oracle Java Archive:

The second method involves downloading the JDK and JRE from My Oracle Support. The following steps will explain how you can download the latest JDK and JRE 7 from My Oracle Support:

  1. Log into using your My Oracle Support account.
  2. Go to Patches & Updates
  3. Search for the following patches:
    1. JDK/JRE 7u79: 20418638
    2. JDK/JRE 7u80: 20418657
    3. Specify the OS platform of your server environment
    4. image
  4. Select the Patch number on the left side of the table
    1. image
  5. Click “Download”
    1. image
  6. Click the name of the zip file to download it.

Once the JDK and JRE are downloaded, you should be able to find both the JDK and the JRE for the particular OS you selected.


To run WebLogic domains especially if one server is hosting multiple WebLogic domains (for ADF, Forms, OAM, etc.), the server must have enough resources to handle all the processes required for WebLogic and all of the Oracle Fusion Middleware components. In Linux, it is not just the amount of available RAM which can prevent additional services including WebLogic servers from starting but also the maximum user processes a specific OS user can have (ulimit –u). If the OS user, e.g. oracle, reaches the maximum user process limit when attempting to start a WebLogic server, WebLogic will fail to start due to the following error:

“java.lang.OutOfMemoryError: unable to create new native thread”

Also, other errors may (but not always) get produced in the server to where you are unable to run anything in the shell or start a new SSH terminal (unless you use the exec command) due to the following error:

“-bash: fork: retry: Resource temporarily unavailable”


To solve this problem, you will need to increase the maximum user process limit for the OS user who is starting WebLogic. To increase the limit, please follow these steps:

1. Verify what you have set for ulimit –u by running ulimit -u

2. Log into the server as root

3. Go to /etc/security and make a backup of limits.conf

4. Open up limits.conf in VI

5. At the end of the file, add the following line:

<OS_USER> – nproc # (where # is a value higher than what you currently have set under ulimit –u)

Example: oracle – nproc 4096


6. Save and close the file.

7. Close all SSH windows and log back into the server.

8. Verify the change by running ulimit –u. The value should have increased. If not, please reboot the Linux server.

9. If you were trying to start any managed WebLogic servers at the time of the error, please restart any associating AdminServers and Node Managers.

After applying the steps above, you should be able to start up WebLogic normally.


UPDATED: June 3, 2014


Oracle has just recently released an updated version of Oracle Forms 11gR2 versioned as For what we have seen on Oracle’s website and Oracle Support, the following has been updated in the latest version of Oracle Forms 11gR2 (

·         Many bugs have been fixed (See Oracle Support ID 1612530.1 for a list of the bugs fixed)

·         Only Oracle WebLogic Server (WLS) 10.3.6 is supported

·       The operating system support is the same as except for the following:

o   AIX 6.1 must be Update Level 7 or higher

o   AIX 7.1 must be Update Level 1 or higher

o   Windows XP is no longer supported with Forms

o   NOTE: Currently no support for Oracle Forms (any release) with Windows 8

·       JDK support:

o Using Java 6 – JDK 1.6.0_35+

o Using Java 7 – JDK 1.7.0_40+

·         Internet Browser support:

o   Internet Explorer: 8, 9, 10, 11 (IE 11 is only supported if Oracle Patch 18277370 is applied)

o   Firefox: 24+

o   Google Chrome: 29+

o   Safari: 5.x

·         Database support (No changes from Forms





·          OAM support (No changes from Forms

o   Oracle SSO 10gR3 (

o   Oracle Access Management 11gR1 (

o   Oracle Access Management 11gR2 (

o   Oracle Internet Directory (OID) 11gR1 (

o   Oracle Virtual Directory (OVD) 11gR1 (

·          This version is released as both a base installation and a patchset (Oracle patch 17882900) installation meaning that Oracle Forms can either be installed as a separate installation or as a patch to an existing or installation.

·          On the Oracle Forms download page, there are no more downloads for Forms or Only Forms can be downloaded from OTN.

For more information regarding Oracle Forms certifications, please review Oracle’s certification matrix for Forms and Reports


After successfully installed and configured Oracle Forms & Reports in both our Windows 7 64-bit and Oracle Linux 6.4 64-bit test environments, we found that there are no major functionality changes that we could detect. In our test installations, we worked with Oracle WebLogic Server 10.3.6 using JDK 1.7.0_45 (this was the latest JDK available for download as of January 8, 2014 when the test installs were performed). Based off the installation and configuration, we have noticed the following:

1.       The installation of Oracle Forms and Reports (as well as running config.bat/sh) is identical to installing The same steps are involved.

2.       Environment files and formsweb.cfg work the same. In order to use the latest JRE (since we were using JDK 7 in our test), we had to configure the jpi parameters in formsweb.cfg.

3.       Similar to Forms and Reports, we still receive the “REP-52262: Diagnostic output is disablederror when we try to run reports. In previous releases of Oracle Forms & Reports 11gR1 and 11gR2 (, using the default setting in would allow anyone to access anything related to rwservlet such as getjobid, showjobs, showenv, etc. For some reason in and, the default settings act the same as using <webcommandaccess>L0</webcommandaccess> in the file. To fix this, we had to manually add the parameter <webcommandaccess>L2</webcommandaccess> into and restart WLS_REPORTS before we could view generated reports. NOTE: If this was fixed manually in Forms and you patch the install to, you do not have to redo this. URL:

4.       Patching your Forms installation to requires little effort. All that is required is to shut down all WebLogic servers associated with Forms, OPMN, and Node Manager. Running the patchset install and starting everything up afterward is all that is required.

a.       NOTE: When running the installer, make sure to select “Install Software – Do Not Configure”.

b.      NOTE: If you have an Oracle Database installed on the same PC/server where you are upgrading Forms and Reports, the database, TNS listener, and DB Console will need to be shut down as well in order to prevent a possible error during the upgrade.

5.       The OHS bug which occurred in many Oracle Forms installations that was fixed in is also fixed in The bug was the case where you had to rollback and re-apply an Oracle patch to fix an issue where OHS would lose connectivity with the WLS_FORMS server after a report was run. URL:

6.       The Reports Builder bug where it crashes when viewing the Data Model in 64-bit machines has NOT been fixed with Forms and Reports Fortunately, applying the fix as mentioned in will still fix the problem. NOTE: If this was fixed manually in Forms and you patch the install to, you do not have to redo this.

7.       Oracle Forms & Reports is backwards-compatible with Oracle Forms & Reports We tested this by successfully opening up or loading a form in either an Forms Builder or PITSS.CON saved in either Forms Builder or PITSS.CON using Forms This means that if you are working with someone who is using Oracle Forms, you are able to use your PITSS.CON or Forms Builder using Forms without any problems. NOTE: Forms is not backwards-compatible with Forms 11gR1.

8.       In Oracle Forms,, and, there was a bug where you were unable to edit any configuration files or logging information for OHS within Enterprise Manager as mentioned in This bug has been fixed in Forms (as well as if you are using Forms 11gR1).

9.       All Oracle jar files (frmall.jar, frmwebutil.jar, and any other jar file which starts with “frm”) have been updated with the permissions and codebase manifest attributes needed for the later Java JDK and JRE updates. Before you decide to upgrade your JDK and JRE to the latest version (Java 7u45 or higher) in your Forms and Reports and environment, it is best to upgrade to Forms and Reports first (and WebLogic 10.3.6 if you are using 10.3.5). For any custom jar files used in Forms and Reports, they will still need to contain the permissions and codebase manifest attributes (and signed with trusted certificates). Please see for more information.

10.   Like earlier releases of Oracle Forms and Reports 11gR2 ( and, WebUtil for Forms uses Jacob 1.14.3. No changes to the Jacob DLLs are required.

11.   If you have Forms and Reports integrated with Oracle Access Manager (OAM) 11g, no changes are required on the OAM or OID side. Simply upgrading Forms from (or to is all that is needed to log into your Forms application using OAM.

12.   When configuring Oracle Forms and Reports (using config.bat or and you are integrating with OAM, you will still get an error when connecting to the OAM domain even if all information is entered correctly. This bug that was first seen in Forms and has NOT been fixed in You will need to run config.bat or using the –novalidation flag to work around this error. NOTE: Be very careful when running the configuration wizard if you use the –novalidation flag as the wizard will NOT perform any tests or checks to see if anything entered is valid or invalid. More information can be found at


Other than what we mentioned above, we did not notice any other major differences. We also setup a test PITSS.CON 12.2.2 environment to run in Oracle Forms & Reports The newest PITSS.CON version, 12.2.2 (as of January 8, 2014), works well with Forms Everything works the same as it did in Oracle Forms

Log Rotation for WebLogic, Forms, and Reports 11g

1.     About Log Rotation

Log rotation is the process of generating new log files and adding a timestamp to older log files. This helps prevent a log file from growing too large. Log rotation can either be done when a log file gets to a certain size, after a certain time frame, or perhaps both (only available for the standalone reports server). Log rotation can also be configured to have old log files replaced with new log files after a certain amount of rotated log files are generated.

2.     WebLogic Servers for Forms and Reports

By default, the log rotation settings for the WebLogic servers are set to have an unlimited number of log files rotated. The logs are rotated after a log file gets to around 5000 KB.

To change the settings for log rotation, log into the WebLogic Administration Console.

1.       Go to Environment –> Servers


2.       Click on a WebLogic server (such as WLS_FORMS)


3.       Click “Lock & Edit” in the top-left corner


4.       Select the Logging tab and the General subtab.


5.       In the Rotation section, you will see the Rotation type. You can select if you want “By Size” or “By Time”.

a.       By Size – The Rotation file size parameter specifies (in KB) how big the file can get before the log file is rotated. The parameter “Rotation file size” specifies (in KB) how big a log file can get before it is rotated

b.      By Time – The Begin rotation time parameter specifies (in HH:MM of the day) when the log file is rotated. You may also specify a Rotation interval (in hours) for how often a log file is rotated


6.       To limit the number of log files in the directory, select “Limit number of retained files” (unchecked by default).

7.       If you have selected to limit the number of retained files, you can specify in the “Files to retain” parameter how many files to retain in the file system before older log files get overwritten (7 is the default setting).

8.       Click “Save” to save changes


9.       Repeat steps 2-8 for any other WebLogic servers you wish to configure

10.   Click “Activate Changes”


NOTE: If the rotation type (size or time) is unchanged, but the other parameters are updated, no restarts of any WebLogic servers are required. However, if you change the rotation type from “By Size” to “By Time” or vice-versa, any affected WebLogic servers will need to be restarted.

3.     Oracle HTTP Server (OHS)

By default, the log rotation settings for OHS are size-based for up to 10 MB and to only retain 7 log files.

To update the settings, log into the Enterprise Manager for the Forms and Reports environment. Expand Web Tier and select “ohs1”. Once there, click the drop-down menu and go to Administration –> Log Configuration.


The settings are configured in the Rotation Policy. You can either select:

·         No Rotation – No log rotation at all (OHS log files will continue to grow larger)

·         Size Based – Log rotation performed when a file size gets to the limit (Maximum Log File Size (MB))

o   Maximum Files to Retain – The maximum number of files to keep in the server before older log files are overwritten

·         Time Based – Log rotation performed starting at a specified day and time.

o   Rotation Frequency – How often the file is rotated


To save changes, click “Apply”. NOTE: You will need to restart OHS either from Enterprise Manager or OPMN.

NOTE: If you try to access the log configuration for OHS and you get an error “Failed to invoke operation load on MBean”, please review our knowledge base article to update a parameter in admin.conf to fix this error:

4.     Standalone Reports Server

By default, the log rotation settings for the standalone reports server is set to a “size based” log rotation policy where the maximum file size is 10 MB and all log files cannot be more than 100 MB.

Log into the Enterprise Manager for Forms and Reports. Expand Reports and select your standalone reports server name “RptSvr…”. Next, select the drop-down menu and go to Logs –> Log Configuration.


Select the “Log Files” tab and you will see three handlers:

·         rwengine_trace_handler – Logs for the reports server engine(s)

·         rwserver_trace_handler – Logs for the standalone reports server itself

·         zrclient_trace_handler – Logs for the network connectivity for reports

To view the rotation policy, select a handler and select “Edit Configuration”.


In the window that appears, you will see the rotation policy. You can either configure the rotation policy for size-based rotation, time-based rotation, or both:

·         Size Based

o   Maximum Log File Size (MB) – How large a single log file can get before rotating the log

o   Maximum Size of All Log Files (MB) – How large all of the log files total can get before old log files are overwritten

·         Time Based

o   Start Time – What day and time to start rotating logs

o   Frequency – How often to rotate log files (in minutes)


To make any changes, click “OK”. Back in the main window, make any changes to the other handlers if needed and click “Apply” to activate the changes. NOTE: You will need to restart the standalone reports server either with Enterprise Manager or OPMN to deploy the changes.

When installing Oracle Forms and Reports, if most or all of the prerequisite checks fail due to a common error “Not executed”, check the install logs. Inside the log, if you receive the following errors according to Oracle Support note 468051.1:

“Checking operating system requirements … Check complete. The overall result of this check is: Not executed <<<< OUI-15038: Unable to execute rule ‘CertifiedVersions’ from ruleset ‘OSChecks’. The underlying test ‘oracle.sysman.oip.oipc.oipcz.OipczOSChecks.checkCertifiedOSVersions’ has thrown an unhandled exception [For input string: “18446744073709551615”]. If the exception results in a failure of the test and the exception needs to be propagated, then encapsulate the exception in the result object and return the result.”

You may need to edit the SHMMAX setting in Linux. The input string shown in the error “18446744073709551615” is the current SHMMAX setting. The maximum value it can be is 4294967295 (or FFFFFFFF). You can fix this error by the following:

  1. As the root user, go to /etc/
  2. Open the file sysctl.conf using a text editor
  3. Add a new line at the end of the file as follows: kernel.shmmax=4294967295
  4. Save all changes and exit the file
  5. Activate the new setting by: /sbin/sysctl –p
  6. Run the Forms installer again (as oracle). The errors should not appear.

Updated: July 2, 2014

For Forms versions,, and, if you installed the WebLogic and Forms environment using JDK 7 (NOTE: JDK 7 is not supported with Forms, if you attempt to make any modifications of any OHS configuration files in Enterprise Manager FMW Control, you will be presented the following error message:

“Failed to invoke operation load on MBean,name=ohs1,instance=asinst_1,Location=AdminServer”


To fix this error, go to %ORACLE_INSTANCE%\config\OHS\ohs1 ($ORACLE_INSTANCE/config/OHS/ohs1 in Unix) and open up admin.conf with a text editor (please make a backup of this file before making any edits to this file or any configuration file). Once in the file, look for the parameter “SSLProtocol nzos_Version_3_0”. Change this to: SSLProtocol nzos_Version_1_0 nzos_Version_3_0


After making the change above, save and close the file. Restart OHS from either OPMN or Enterprise Manager. After OHS has been successfully restarted, you should be able to make edits to OHS configuration files in EM.

NOTE: According to Oracle Support, this has been fixed with Oracle Forms

UPDATE (7/2/14): There is also a known issue (also includes Forms where the same error is produced due to a filename containing spaces in %ORACLE_INSTANCE%\config\OHS\ohs1\moduleconf ($ORACLE_INSTANCE/config/OHS/ohs1/moduleconf in Unix).


To fix the problem, rename the file containing spaces so that there are no spaces in it. After the file(s) has been renamed, restart the AdminServer. After doing that, the error should disappear.

Sources: Oracle Support notes 1463846.1 and 1352382.1

To protect end-users from the latest security threats, Oracle has improved security in Java. Starting with Java Runtime 7 Update 25, you may have noticed the following warnings in the Java Console for jar files such as frmall.jar or any custom-made jar files:

  • Missing Permissions manifest attribute for: http://server.domain:port/forms/java/name_of_jar.jar
  • Missing Codebase manifest attribute for: http://server.domain:port/forms/java/name_of_jar.jar


At this time (with using the latest JRE available), these warnings will not cause any problems running any Oracle Forms application. These warnings appear due to how the Forms application jar files are set up. By default, the jar files deployed by every Oracle Forms application such as frmall.jar will present these warnings.

How to Remove the warnings for the Oracle Forms jar files such as frmall.jar, etc.

Oracle Patch 16837591 is able to correct this problem as it will apply the necessary updates to the Oracle Forms jar files supplied by Oracle to prevent this warning from appearing. This patch can be downloaded from My Oracle Support. The patch is available for any Oracle-supported operating system.

Once the patch is downloaded and extracted, you may install it by completing these steps:

  1. Shut down all WebLogic servers and instances running in the Forms domain.
  2. Open up Command Prompt (if using Windows) or an SSH client (if using Unix) and change the directory to the directory where you extracted the patch.
  3. cd 16837591
  4. Set the ORACLE_HOME and PATH environment variables similar to how it is done below (NOTE: The actual values of ORACLE_HOME and PATH may differ depending on how your environment is set up):
    1. Windows
      1. set ORACLE_HOME=C:\Oracle\Middleware\Oracle_FRHome1
      2. set PATH=%PATH%;C:\Oracle\Middleware\oracle_common\OPatch
    2. Unix
      1. export ORACLE_HOME=/oracle/middleware/Oracle_FRHome1
      2. export PATH=$PATH:/oracle/middleware/oracle_common/OPatch
      3. image
  5. Run: opatch version (to make sure you are using an OPatch version level that is supported by the README file which comes with the patch).
    1. image
  6. Run: opatch apply
    1. image
  7. When it asks if the system is ready for patching, type: y
    1. image
  8. Once complete, you may start up the WebLogic servers and OPMN instances in the Oracle home.


After completing the steps above, the warnings should no longer appear for any of the Oracle-supplied jar files:


NOTE: All end-users will be re-presented with this warning. As the frmall.jar file is from Oracle, you may run this and click the option to trust the publisher.


NOTE (Modified October 24, 2013): We have also created a knowledge base article specifying how you may update custom jar files with these parameters:

NOTE: Be sure to review the README file included with an Oracle patch before applying it. PITSS will not be held responsible for anything that happens when running any Oracle patch. Also, never make any changes or updates to any Oracle-supplied jar files (jar files which start with “frm”) without consent by Oracle (outside of this patch). Failure to do so may require a reinstallation of Oracle Forms and Reports.

NOTE: This Oracle patch is only supported with Forms,,, and If you are using an older Forms version, it is recommended to upgrade to one of these four versions before applying this patch.

Source: Oracle Support note 1563023.1.