B Troubleshooting

This appendix highlights the most common problems encountered when installing the RUEI accelerator for Oracle E-Business Suite. The information in this appendix should be reviewed before contacting Customer Support.

B.1 Network Traffic Does Not Appear to be Measured

In the event that expected network traffic does not appear to be reported, it is recommended that you review the following points:

• RUEI can monitor EBS applications based on the OA, JTT, PLS, Oracle Forms, and servlet frameworks. Generally, suites are configured to run on a specific port which differs per installation. These also need to be specified in RUEI. Select Configuration, then Security, and then Protocols. Review the defined port settings, and ensure they meet the requirements of your EBS applications.

• Once data starts arriving into the RUEI system, it is not reported automatically. At least one application must be defined. At a minimum, this application must contain the relevant domain name, and the unique page-identification scheme within that domain.

• If the monitored traffic includes VLAN-encapsulated traffic, ensure this is configured within RUEI. Select System, then Configuration, then Security, then Network filters, and then VLAN traffic, to review the defined settings. The use of this facility is fully described in the Oracle Real User Experience Insight User's Guide.

• Be aware that there is no suitable out-of-the-box cookie available for session tracking in EBS. Therefore, a cookie needs to be created on the login page. This should cover the complete application. By default, the Jession cookie only covers the application links, and not the images, CGIs, and libraries. While the oracle.uix cookie does cover all hits, it is not unique for each visitor.

• Be aware that because the Traffic summary facility (select System, then Status, and then Data processing) is based on application logic, non-application traffic (such as suites, services, and SSOs) is not represented in the traffic overviews.

It is strongly recommended that after installing the EBS accelerator package, you login to the EBS application, and execute a critical path through the application. Then, you should search for recorded action within RUEI, and use the Session Diagnostics facility to verify that it is correctly reported. In particular:

• Verify that descriptions are reported, and not codes. If codes are reported instead of application names, or page-group level codes instead of page-group names, it indicates that the information derived from the create_EBS_info.pl script is not activated correctly.

• A large number of reported short sessions indicates that Forms traffic is not being measured.

• A large number of reported .jsp files indicates the need for manual page naming (if required by the customer).

B.2 A Large Number of Unidentified Actions are Reported

If a large portion of the reported traffic contains unidentified actions, this indicates that Forms tracking is not functioning correctly. You should consider the following:

• If you do not see such things as "Status Bar" and "Textfield" (as shown in Figure 1-3), this indicates that some specific characteristic in the monitored traffic is not being captured. In this case, you should contact Customer Support.

• If all monitored traffic is reported with unidentified actions, you should verify that the URL prefix and Session URL argument settings specified within the Forms tab of the suite's overview (as shown in Figure 1-6) match those used within your environment. This information is available within the Page URL dimension.

• Verify that the server ports are correctly configured, as described in Section 1.5, "Verifying the Scope of Monitoring". In particular, verify that servlet port is configured as the HTTP port.

B.3 Sessions are Reported as "Anonymous"

If sessions are reported as "anonymous", but user IDs are available in the All sessions cube, you should verify the Correlation URL argument specified within the Forms tab of the suite's overview (as shown in Figure 1-6).

B.4 Create_EBS_info.pl Script Reports FRM-91500 Error

When the create_EBS_info.pl script is run on a Unix system, the following error is reported multiple times:

FRM-91500: Unable to start/complete the build.

This is caused by the frmbatch script not having access to the user interface. You should consider the following:

• Ensure that the DISPLAY variable is correctly set. You can use X Window System tools such as xclock or xeyes to verify it. You might also consider using X-forwarding of SSH to enable the use of the X Windows System on another server.

• The frmcmp_batch script is trying to work without the X Windows System. This is the first script used by the create_EBS_info.pl configuration script. Set the display mode using the following command:

  $ set ORACLE_TERM=vt220; export ORACLE_TERM
  

B.5 Perl Zip Functionality is not Available

In some systems, zip functionality is not installed as part of the Perl package. In this case, you receive the following message:

The Archive::Zip package is not available on this system.

After this message, a sample command indicates how the archive might be created. Be aware that the archive should consist of non-empty files, and that files should not be in directories. If so, the upload to RUEI will fail. Alternatively, you can execute the command zip EBS_*txt in the appropriate directory.

B.6 The frmcmp_batch Script Fails

The frmcmp_batch script fails due to some unknown error, and reports something similar to the following:

execution of 'frmcmp_batch module=XXX/XXX/XXX.fmb module_type=form batch=yes logon=no forms_doc=yes strip_source=yes build=no output_file=/tmp/XXX.txt' failed: 11. Ignoring /XXX/XXX/XXX.fmb

This indicates that the reported .fmb file could not be converted into .txt format (possibly due to corruption). If only a very small proportion of the total number of .fmb files are reported, this will probably not be an issue. Indeed, it is likely that the reported forms would not work in a production environment in any case. However, if you know that visitors to your Web site are actively using the reported forms without trouble, then please report this issue. When doing so, please provide the relevant .fmb files, together with some indication of how they are deployed within your EBS environment.

B.7 create_EBS_info.pl Script Generates Warnings/Errors

If you receive errors and/or warnings while running the create_EBS_info.pl script, depending on their nature, do the following:

• Database related:

  • Verify the connectstring specified for the create_EBS_INFO.pl script by issuing the following command:

    sqlplus connectstring @temporarysqlfile
    

• Forms related:

  • frmcmp or frmcmp_batch are not working correctly. Detailed troubleshooting information is available about this from Note 266731.1 at https://support.oracle.com/CSP/ui/flash.html.

  • frmcmp or frmcmp_batch return a sig 11 segmentation fault. This is know to occur for GRDDHIST.fmb.