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 11.2.0.3.0, 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. FRM-93652 6
  10. Go to $ORACLE_HOME/forms/lib and run: make -f ins_forms.mk 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 https://pitss.com/us/2016/05/06/frm-41337-appears/.

There is a known SSL-related issue when you run Oracle Forms 12c using the Java Web Start functionality. What happens is when you launch your Forms application using Java Web Start using HTTPS, you will notice that the URL will change to using HTTP instead of HTTPS. In some cases, you may encounter the following error:

“General Exception”

“ExitException: Unable to load resource: http://<host>:<HTTPS_PORT>/forms/java/extensions.jnlp”

HTTPS Java Web Start issue

To fix this problem, you will need to add the following parameter inside your config section in formsweb.cfg which is configured for Java Web Start:

webstart_codebase=https://<host>:<HTTP_PORT>/forms

After making this change, the Java Web Start session should maintain the SSL connection using HTTPS without this error appearing.

There is a known issue where running tree reports from PITSS.CON 15.4.2 installed in a Forms 12c environment where the error “Error when running report” appears when attempting to create a PDF tree report. This happens to not be a bug with the latest PITSS.CON release. To get tree reports to generate in PITSS.CON, a new configuration is required in Forms and Reports 12c to run PITSS.CON tree reports in 12c.

First, make sure that all environment files (.env) have the new COMPONENT_CONFIG_PATH environment variable set up. For more information, you may check out our knowledge base article on setting up this environment variable here: https://pitss.com/us/2016/05/06/running-oracle-reports-12c-causes-frm-41214-errors/

Once the variable is set up, you will also need to set up two environment variables for your Reports 12c environment. This should be set up in rwserver.conf. If you are using a standalone reports server, the file is located in %DOMAIN_HOME%\config\fmwconfig\components\ReportsServerComponent\%RptSvr%; if you are using the in-process reports server, the file is located in %DOMAIN_HOME%\config\fmwconfig\servers\WLS_REPORTS\applications\reports_12.2.1\configuration. Before modifying this file, please make a backup. Inside the file after the <engine> tag containing the id=”rwEng” line, add the following lines (you may use the screenshot below as a guide):

<environment id=”pitss”>
<envVariable name=”REPORTS_PATH” value=”C:\pitsscon\tool;c:\pitsscon\%PITSS_USER%\rdf;c:\pitsscon\%PITSS_USER%\olb;” />
<envVariable name=”TNS_ADMIN” value=”%DOMAIN_HOME%\config\fmwconfig”/>
</environment>

NOTE: This assumes that PITSS.CON is installed in C:\pitsscon as it uses paths such as C:\pitsscon\tool and C:\pitsscon\%PITSS_USER%\rdf. Also, %PITSS_USER% should be your PITSS.CON user. If you have more than one PITSS.CON user, please specify the RDF and OLB paths for all PITSS.CON users here. For the TNS_ADMIN variable, the fully-written path for %DOMAIN_HOME%\config\fmwconfig should be filled inside the value attribute.

rwserver.conf for PITSS.CON

After the update is made, save and close the file. Once the file is updated, you will need to restart your reports server (the standalone reports server if you configured the standalone reports server or WLS_REPORTS if you configured the in-process reports server).

After restarting your reports server, you should be able to run a tree report in PITSS.CON.

After upgrading Oracle Forms and Reports from a previous version (e.g. 10g or 11g) to 12c, there is a known issue where running Oracle Reports in 12c with the RUN_REPORT_OBJECT built-in causes the following error:

“FRM-41214: Unable to run report”

Starting in Forms 12c, a new environment variable, CONFIGURE_COMPONENT_PATH, has been created. This should be placed in your environment file (.env) used by your Forms application. The variable should be mapped to the location of your ReportsToolsComponent. You may either edit the file manually or create a new variable under Environment Configuration for the Forms instance in EM FMW Control.

Example: CONFIGURE_COMPONENT_PATH=%DOMAIN_HOME%\config\fmwconfig\components\ReportsToolsComponent\reptools1

COMPONENT_CONFIG_PATH

NOTE: If you use EM FMW Control to create or modify your environment variables for Forms, it is highly recommended to continue to use EM FMW Control.

In addition, make sure that the CLASSPATH variable has the full path to rwrun.jar (%ORACLE_HOME%\reports\jlib\rwrun.jar), as this jar file is required to generate reports from Oracle Forms.

After you have made the changes, re-launch the Forms application. You should now be able to run a report.

Source: Oracle Support note 2074841.1

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: https://support.oracle.com/epmos/faces/ui/patch/PatchDetail.jspx?parent=DOCUMENT&sourceId=2113628.1&patchId=22184867

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

After installing and configuring Oracle Forms and Reports 12c, if you try to launch either Reports Builder (rwbuilder.bat) or Reports Converter (rwconverter.bat), both located in %ORACLE_HOME%\bin, you will most likely encounter the following error:

“Windows cannot find ‘\bin\rwbuilder.exe'” or “Windows cannot find ‘\bin\rwconverter.exe'”

Reports Builder 12c

The reason for the error is because the values for the DOMAIN_HOME and COMPONENT_NAME need to be filled out in both batch files. You may fix the error by completing these steps:

  1. Go to %ORACLE_HOME%\bin and make backups of both rwbuilder.bat and rwconverter.bat.
  2. Open up rwbuilder.bat in a text editor (Notepad, Wordpad, etc.)
  3. Look for $$domain_home$$ and $$component_name$$. Replace $$domain_home$$ with the full path to your domain home (Example: C:\Oracle\Middleware\user_projects\domains\FormsDomain) and $$component_name$$ with the name of your ReportsToolsComponent (Example: reptools1).
  4. Immediately before the line with “set DOMAIN_HOME=…”, insert the line: set ORACLE_HOME=<PATH_TO_ORACLE_HOME> where <PATH_TO_ORACLE_HOME> is the fully-written path to your Forms 12c Oracle home.
  5. Save and close the file.
  6. Repeat steps 2-5 for rwconverter.bat.

This is how the file looks before the changes are made:

rwbuilder.bat before

This is how the file should look after the changes are made:

rwbuilder.bat after

After making the changes above, Reports Builder and Reports Converter should open up normally.

In new installs of Oracle Forms and Reports 12c, there is a known report where running Oracle Forms in Internet Explorer for the first time is causing the following error:

“Windows has blocked this software because it can’t verify the publisher.

Name: forms/

Publisher: Unknown Publisher”

Forms Runtime Error

This is because the Java Runtime Environment (JRE) download is being blocked by security settings in Internet Explorer. To bypass this error, you will either need to manually install a 32-bit JRE or have your system administrator install a 32-bit JRE for you. Unless the Forms environment’s formsweb.cfg is configured to use a specific JRE version, you should use the latest version of JRE which is version 8 update 77 as of April 2016.

After extending a domain with Oracle Forms and Reports with an additional Forms and Reports managed server, WLS_FORMS1 and WLS_REPORTS1, in a cluster, there is a known issue (this may or may not occur) where the standalone reports server of the original installation is unable to communicate with the EM Agent associated with the AdminServer for the Forms domain. For example, if you log into the Enterprise Manager (EM) Fusion Middleware (FMW) Control associated with your Forms domain, if this problem occurs, you will see the warning “Targets not being monitored due to invalid configuration”. If you click on this warning message, it will take you to the Agent-Monitored Targets page (you may also access this page by right-clicking the domain farm name in the left panel and selecting “Agent-Monitored Targets”). On this page, you may notice that one of the “Oracle Reports Server” targets needs an agent configured:

Agent-Monitored Targets

However, if you click to configure the agent for the target and you click OK after all fields entered are correct, you will get an error saying that there is no agent available.

To fix this problem, when you are in the Configure Target page, click the button “Change Agent”. The agent URL next to the Change Agent button will become a drop-down, and you should be able to select the correct agent associated with your standalone reports server:

Agent-Monitored Targets

After the agent is selected, click “OK” to save your changes. After completing this step, the target will be able to contact the agent successfully.

Even when WebUtil and Jacob have been fully configured in the PITSS.CON server environment as documented in https://pitss.com/us/2014/03/20/forms-and-reports-11g-environment-requirements-for-webutil/, there have been known issues where users (on the first use of PITSS.CON) are unable to log in due to the following error:

NoClassDefFoundError – com/jacob/com/ComFailException

No Jacob

The reason for this error is because the Java cache may be interfering with properly finding the Java classes associated with jacob.jar. Clearing the Java cache should fix the problem:

  1. Open up the Control Panel on the end user’s PC
  2. Go to All Control Panel Items and click “Java”
  3. With the General tab highlighted in the Java Control Panel, click “Settings…”Java Control Panel
  4. Click “Delete Files…”Delete Temporary Java Files
  5. In the new pop-up window, have only “Trace and Log Files” and “Cached Applications and Applets” selected and click “OK”.Clearing Java cache
  6. After the window closes, click “OK” twice to close all windows in the Java Control Panel.
  7. Close all web browser windows and try launching PITSS.CON.

After completing the steps above, PITSS.CON should launch without any problems.

When running a project for upgrading forms in PITSS.CON such as the project to replace the text_io function with webutil.client_text_io, if you happen to encounter the following error:

Search&Replace Error : ORA-06550: line 1, column 7:

PLS-00306: wrong number or types of arguments in call to ‘SYNCRN’

ORA-06550: line 1, column 7:

PL/SQL: Statement ignored.

image

There is a possibility that you might have encountered a bug with the Oracle Database especially if the database version is 11.2.0.4. It has also been noted that this error also happens when you attempt to delete a form from Module Handling. There are two solutions which can be done to fix the problem:

1. Apply Oracle Patch 17501296 to the Oracle Database (version 11.2.0.4 only). More information is provided in Oracle Support note 1586704.1.

2. Re-create the CTXSYS.SYNCRN procedure. The full SQL commands can be found in Oracle Support note 1586704.1.

After applying either one of the two solutions, the problem should no longer occur.

Source: Oracle Support note 1586704.1