PITSS.CON’s module, Source Code Analytics, is a powerful tool which is able to fully analyze your application and provide information such as how many lines of code are in your application. In PITSS.CON version 16.2.2, there is a known bug where no results will appear when running the Source Code overview in Source Code Analytics against a pool. However, if you do not run this against a pool, the results will appear normally.

Fortunately, this will be fixed in the next release. In the meantime, a patch is available to fix the bug. Contact PITSS Support, pitssam-support@pitss.com, to obtain the patch. Once you receive the patch, you will need to run it (it is a .wrp file which is run similarly to a SQL script) with the MIG user. The script will create a package body in the MIG user which will fix the problem. NOTE: You must be licensed with the Source Code Analytics module in PITSS.CON in order to receive the patch.

Once the patch is applied, you will be able to see the results against a pool.

NOTE: This bug has only been reported with version 16.2.2. It has not been reported with older versions of PITSS.CON.

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.
    1. 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/.

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

Updated: 3/23/16

In PITSS.CON 15.3.1, there is a known bug where if you check the Module Summary for a particular module (form, menu, library, etc.), the right column will be blank:

pit001

The Module Summary can be accessed by going into the Application Analysis module in PITSS.CON and right-clicking on a form to select “Module Summary”. NOTE: The application must be parsed first.

A bug fix is available for this problem. The newest version of PITSS.CON, version 15.4.2, has this bug already patched. Upgrading PITSS.CON 15.4.2 will fix this problem (version 15.4.1 has this problem still). Please contact PITSS Support for how you can upgrade to the latest version of PITSS.CON. However, if you cannot upgrade right away, you may also contact PITSS Support for the SQL script to patch the PITSS.CON repository. The file is called patch_290915.wrp. Once you have received it, you may follow these steps to apply the patch:

  1. Download the patch to the PITSS.CON server or client.
  2. Log into SQLPLUS as each of your PITSS.CON users (except for MIG). NOTE: Please be in the same directory as the patch when launching SQLPLUS.
  3. Run the command to install the patch: start ‘patch_290915.wrp’
  4. Log out of the PITSS.CON user in SQLPLUS and log into your other PITSS.CON users and repeat the process.
  5. Log out of PITSS.CON and log back in.

After completing the steps above, everything should work normally:

AA works

There is a bug in Forms/Reports 11.1.2.2.0 where reports generated into PDFs are not displayed correctly in AIX and Solaris (possibly even Windows 32-bit) environments. According to Oracle Support note 1522543.1, an Oracle Patch, 17903693, will need to be applied to the Forms/Reports environment.

NOTE: This patch is already included with Forms and Reports 11.1.2.2.0 for Windows 64-bit.

How to Apply the Patch:

  1. Download Patch 17903693 from My Oracle Support
  2. Extract the patch into your directory. As a reference, let’s call the extracted location PATCH_TOP.
  3. Shut down all WebLogic servers and instances (OPMN).
  4. Set the following environment variables (NOTE: MW_HOME is your Oracle Middleware home):
    1. Windows: set PATH=%PATH%;%MW_HOME%\oracle_common\OPatch
    2. Windows: set ORACLE_HOME=%MW_HOME%\Oracle_FRHome1
    3. Unix: export PATH=$PATH:$MW_HOME/oracle_common/OPatch
    4. Unix: export ORACLE_HOME=$MW_HOME/Oracle_FRHome1
  5. Go to the PATCH_TOP/17903693 directory (PATCH_TOP\17903693 in Windows)
  6. Run: opatch apply
  7. Type ‘y’ and press Enter when it asks if the system is ready for patching.
  8. When the patch is finished, start up the WebLogic servers and OPMN.

PDF reports should display correct after applying the steps above.

NOTE: Please review the README file before applying any Oracle patch!

Source: Oracle Support note 1522543.1

In Reports Builder 11g, there is a known issue where copying and pasting items within any of the layout editors in Reports Builder causes Reports Builder to freeze or hang. This has been reported with Reports 11.1.1.6.0, 11.1.1.7.0, 11.1.2.1.0 and 11.1.2.2.0 with Windows 7 64-bit.

To resolve the issue, Oracle has provided a patch for download (NOTE: Access to My Oracle Support (Metalink) is required):

1. Download Patch 17301874 from Oracle Support (https://support.oracle.com). Make sure you specify the version of Forms and Reports you have installed.

2. Extract the patch in your PC or server.

3. Shut down all WebLogic servers and OPMN processes pertaining to your Forms environment.

image

4. Open up Command Prompt as an administrator.

5. Set the following environment variables:

set ORACLE_HOME=C:\Oracle\Middleware\as_1 (or C:\Oracle\Middleware\Oracle_FRHome1)

set PATH=%PATH%;C:\Oracle\Middleware\oracle_common\OPatch

image

6. To ensure your OPatch version meets the prerequisites, run: opatch veresion

image

7. Navigate to where you extracted the Oracle patch and go into the 17301874 folder. Once there, install the patch by running: opatch apply

image

8. Ensuring that the Oracle Home mentioned matches the one for your Oracle Forms environment and everything in the Oracle Home is shutdown, type ‘y’ when asked if the system is ready for patching.

image

9. You will receive a success message when the patch is installed successfully.

10. Start up everything from the WebLogic servers to OPMN.

After applying the steps above, the problem should be fixed with Reports Builder.

Source: Oracle Support note 1395965.1

Updated: July 2, 2014

For Forms versions 11.1.1.6.0, 11.1.2.0.0, and 11.1.2.1.0, if you installed the WebLogic and Forms environment using JDK 7 (NOTE: JDK 7 is not supported with Forms 11.1.2.0.0), 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 oracle.as.management.mbeans.register:type=component,name=ohs1,instance=asinst_1,Location=AdminServer”

image

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

image

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 11.1.1.7.0.

UPDATE (7/2/14): There is also a known issue (also includes Forms 11.1.2.2.0) 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).

image

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

NOTE (Added January 23, 2014, modified March 9, 2017): PITSS.CON 16.2.2 has been released. The newest version of PITSS.CON has this problem fixed and has the availability to work with both Java 7 and 8. Please contact PITSS to upgrade your PITSS.CON version to 16.2.2 today.

Beginning with Java Runtime 7 update 21, Oracle Forms added additional security to Java to protect all end-users from the latest security vulnerabilities. However, with these updated security patches, if you use PITSS.CON with JRE 7u21 or higher, any time you attempt to use the PITSS.CON Editor to view or edit code, you will see that nothing happens (no errors are seen in PITSS.CON).

image

However, if you go into the Java console, you will notice numerous Java exceptions such as:

java.lang.NullPointerException
at pitssEditor.PitssBean.formLoadedUpdate(PitssBean.java:513)
at pitssEditor.PitssWrapper.setProperty(PitssWrapper.java:173)
at oracle.forms.handler.ComponentItem.setCustomProperty(Unknown Source)…

Resolution:

Either one of the two following solutions will fix the problem:

1. Upgrade to PITSS.CON 16.2.2 (Recommended approach) – Added December 18, 2013, modified March 9, 2017

As all of the PITSS.CON jar files have been updated to comply with the latest Java security updates provided by Oracle, the problem will be fixed by upgrading your PITSS.CON installation to release 12.2.2 (the latest PITSS.CON version as of December 18, 2013). This will allow you to use the PITSS.CON editor without any issues with any JRE, including JRE 7u45, JRE 7u51, JRE 7u55, and JRE 7u60 (where Solution 2 only works with JRE 7u21).

2. Download updated Jar files from PITSS

To resolve the problem, we have made updates to five of our jar files which are used for this feature in PITSS.CON, so that they are compliable with the Java security patches. Please contact PITSS at pitssam-support@pitss.com for these jar files when you need to fix this issue.

Once you have received the jar files, please follow these steps to solve the problem:

  1. Go to C:\pitsscon\PitssJava (NOTE: Your PITSS.CON directory may be in another hard disk if not in the C drive)
  2. Make a backup of the following jar files:
    1. pitssCFS.jar
    2. pitssE.jar
    3. pitssFS.jar
    4. pitssH.jar
    5. pitssLE.jar
  3. Copy the jar files you have downloaded from PITSS into this directory. The jar files already in C:\pitsscon\PitssJava will be replaced with the updated jar files.
    1. image
  4. Restart WLS_FORMS.

After you have applied the fix above, launch PITSS.CON, and you should be able to use the PITSS.CON Editor again.

image

NOTE: Using Java Runtime 6 Update 45 has also reported this issue. (Added 11/21/2013)

There is a bug in Forms/Reports 11.1.2.1.0 where reports generated into PDFs are not displayed correctly in Windows, AIX, and Solaris environments. According to Oracle Support note 1522543.1, an Oracle Patch 16046595 will need to be applied to the Forms/Reports environment.

How to Apply the Patch:

  1. Download Patch 16046595 from My Oracle Support
  2. Extract the patch into your directory. As a reference, let’s call the extracted location PATCH_TOP.
  3. Shut down all WebLogic servers and instances (OPMN).
  4. Set the following environment variables (NOTE: MW_HOME is your Oracle Middleware home):
    1. Windows: set PATH=%PATH%;%MW_HOME%\oracle_common\OPatch
    2. Windows: set ORACLE_HOME=%MW_HOME%\Oracle_FRHome1
    3. Unix: export PATH=$PATH:$MW_HOME/oracle_common/OPatch
    4. Unix: export ORACLE_HOME=$MW_HOME/Oracle_FRHome1
  5. Go to the PATCH_TOP/16046595 directory (PATCH_TOP\16046595 in Windows)
  6. Run: opatch apply
  7. Type ‘y’ and press Enter when it asks if the system is ready for patching.
  8. When the patch is finished, start up the WebLogic servers and OPMN.

PDF reports should display correct after applying the steps above.

NOTE: Please review the README file before applying any Oracle patch!

Source: Oracle Support note 1522543.1

There is a bug in Forms and Reports 11.1.2.1.0 and 11.1.2.2.0 (11gR2) where no reports can be run directly from the URL when using the standalone reports server. The bug occurs when no userid is specified in the URL.

Reproducing the Error:

1. Run a report from URL using the standalone reports server (Example: http://server.domain:9002/reports/rwservlet?server=name_of_standalone_reports_server&report=name_of_report&desformat=pdf&destype=cache

image

2. After logging in with the database credentials, the REP-51002 error (REP-51002: Bind to Reports Server name_of_standalone_reports_server failed) appears:

image

 

Solution:

IMPORTANT: Before applying any Oracle patches, it is recommended to review the README file which comes with the Oracle patch as well as to make a backup of your Middleware environment.

UPDATE REGARDING REPORTS VERSION 11.1.2.2.0 (3/10/14): This bug also occurs in Reports 11.1.2.2.0. The below fix is only for Reports 11.1.2.1.0. There is currently no patch available for version 11.1.2.2.0 as the patchset below fails when trying to apply in Reports 11.1.2.2.0.

  1. Download Patch 16426793 from My Oracle Support.
  2. Extract the zip file in the machine where the problem is occurring.
  3. Shutdown all WebLogic servers and instances in the affected domain.
  4. Open up Command Prompt as an administrator (or open a terminal session if using Linux/Unix)
  5. Set the following environment variables:
    1. Windows:
      1. set ORACLE_HOME=C:\Oracle\Middleware\as_1 (can also be Oracle_FRHome1 or something equivalent)
      2. set PATH=%PATH%;C:\Oracle\Middleware\oracle_common\OPatch
    2. Linux/Unix:
      1. export ORACLE_HOME=$MW_HOME/as_1 (can also be Oracle_FRHome1 or something equivalent) (Replace $MW_HOME with the path to your Middleware home)
      2. export PATH=$PATH:$MW_HOME/oracle_common/OPatch
  6. Go to the directory where you extracted the zip file and go into the 16426793 in Command Prompt or your terminal window.
  7. Run: opatch apply
  8. Press ‘y’ when it asks if the system is ready for patching.
  9. When complete, start up your WebLogic servers and instances.

After completing the steps above, the report should run without a problem after logging into the login screen shown in step 1 in the “Reproducing the Error” section using the same URL.

Source: Oracle Support Note 1454773.1