A Troubleshooting

This appendix lists some methods for troubleshooting your Forms and Reports Services installation. It includes the following topics:

Verifying Requirements
Resolving Installation Errors
Troubleshooting Configuration Assistants
Descriptions of Forms and Reports Services Configuration Assistants

A.1 Verifying Requirements

Review the following information before performing any of the troubleshooting steps in this appendix:

Ensure that the computer meets the requirements specified in Chapter 3, "Requirements".

Read the Release Notes

Read Oracle Application Server Forms and Reports Services Release Notes which contains release notes for Oracle Forms Services, Oracle Forms Developer, Oracle Reports Services, and Oracle Reports Developer. In addition, Oracle Application Server Forms and Reports Services Release Notes contains information about the features that are available in this installation type.
Read Oracle Application Server Release Notes prior to installing Forms and Reports Services. The release notes are available with the platform-specific documentation. The latest version of the release notes is available on OTN at
```
http://otn.oracle.com/documentation/ias.html
```

A.2 Resolving Installation Errors

If you encounter an error during installation of Forms and Reports Services:

Ensure that you entered correct information on all the installation screens. In case you entered wrong information on one of the screens, return to that screen by clicking Back, and enter the correct information.
Exit the installer only if you want to access the component log files. The log files located in the ORACLE_HOME/cfgtoollogs directory are inaccessible if the installer is running.
If you encounter an error while the installer is copying or linking files, do the following:
1. Note the error and review the installation logs for the following causes:
  - inventory_location\logs\installActionstimestamp.log
  - inventory_location\logs\oraInstalltimestamp.err
  - inventory_location\logs\oraInstalltimestamp.out
  The default inventory_location is:
```
C:\Program Files\Oracle\Inventory
```
2. Remove the failed installation by following the steps in Appendix B, "Deinstallation and Reinstallation".
3. Correct the issue that caused the error.
4. Restart the installation.

A.3 Troubleshooting Configuration Assistants

To troubleshoot an installation error that occurs when the configuration assistants are running:

Review the installation log files listed in Section A.2, "Resolving Installation Errors".
Review the configuration assistant log files located in the ORACLE_HOME/cfgtoollogsORACLE_HOME\cfgtoollogs directory for a specific Forms and Reports Services configuration assistant. Section A.4, "Descriptions of Forms and Reports Services Configuration Assistants" also lists any other log file locations for a specific configuration assistant. Try to fix the issue that caused the error.
If you see a Fatal Error. Reinstall message, try to find the cause of the problem by analyzing the log files. Refer to Section A.3.3, "Fatal Errors" for further instructions.

A.3.1 Configuration Assistant Failure

Forms and Reports Services configuration assistant failures are noted at the bottom of the installation screen. The configuration assistant interface displays additional information when applicable. The configuration assistant's execution status is identified by the result. The result codes are:

Status	Result Code
Configuration Assistant Succeeded	0
Configuration Assistant Failed	1
Configuration Assistant Cancelled	-1

This result code is written to the following log file:

C:\Program Files\Oracle\Inventory\logs\installActionstimestamp.log

A.3.2 Failure During Component Configuration and Startup

During installation, configuration assistants run when the Configuration Assistants screen appears. If a configuration assistant fails, try the following procedure to correct the problem:

Review the installation log files for this Forms and Reports Services instance.
Review the log files for each configuration assistant located in the ORACLE_HOME/cfgtoollogsORACLE_HOME\cfgtoollogs directory. Default log file locations are described in Section A.4, "Descriptions of Forms and Reports Services Configuration Assistants".
Refer to the section describing the configuration assistants in Section A.4, "Descriptions of Forms and Reports Services Configuration Assistants".
1. If the failing configuration assistant has any dependencies, then run the dependencies again. You must do this even if the dependency completed successfully.
2. Run the failing configuration assistant again. If you are using the installer, select the configuration assistant and click Retry.
  
  If the configuration assistant fails again after you click Retry, then remove the /var/tmp/EM_CONFIG_INSTALL.lk lock entry and try running the configuration assistant again.
3. If an optional configuration assistant fails, and it does not have any dependencies, run the remaining configuration assistants. Deselect the cancelled optional configuration assistant, highlight and check the next listed configuration assistant, and click Retry.
4. If configuration assistant failure occurs when running configuration assistant execution commands on the command line, then run the configuration assistant execution command again.
  
  You can use the generated script file named configToolCommands located in the ORACLE_HOME/cfgtoollogsORACLE_HOME\cfgtoollogs directory to execute the failed configuration assistant again. The configToolCommands script is generated after you exit the installer. During silent or non-interactive installation of Forms and Reports Services, the configToolCommands script is generated immediately after configuration assistant failure.
  
  You must set the following environment variables before using the generated script:
  - Set the ORACLE_HOME environment variable to the ORACLE_HOME path.
  - Append the PATH environment variable with ORACLE_HOME\lib and ORACLE_HOME\network\lib.
  - For the Register DCM Plug-Ins With Enterprise Manager Configuration Assistant only, set the PERL5LIB environment variable to the ORACLE_HOME/perl/lib/5.6.1ORACLE_HOME\perl\lib\5.6.1 directory.
  Note:
  If the description of a configuration assistant includes an "Initial Tasks" section, perform these tasks before running the configuration assistant.

A.3.3 Fatal Errors

Some configuration assistant failures are "fatal errors". You cannot recover from a fatal error by correcting the problem and continuing. You must remove the current installation and reinstall Forms and Reports Services. The following tasks describe the recovery procedure:

Deinstall the failed installation using the procedure described in Section B.1, "Deinstallation of Forms and Reports Services Instances".
Correct the cause of the fatal error.
Reinstall Forms and Reports Services.
If the fatal error reoccurs, then you must remove all Oracle installations from your computer using the procedure in Section B.1, "Deinstallation of Forms and Reports Services Instances".

A.3.4 OC4J Instance Configuration Assistant Errors

If you are installing a middle tier against an Oracle Internet Directory that was upgraded from 9.2.0.x to 10g Release 2 (10.1.2) and not all the upgrade steps were completed, then the OC4J Instance Configuration Assistant may fail with the following error:

Adding dependent libraries for application 'portal'...done. 
Deploying application 'oraudrepl' to OC4J instance 'OC4J_Portal'... 
ERROR: Caught exception during deploy. 
java.rmi.RemoteException: deploy failed!: ; nested exception is: 
oracle.oc4j.admin.internal.DeployerException: User specified for 
application-client uddirepl, 'uddi_replicator' not found 
at com.evermind.server.rmi.RMIConnection.
EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(RMIConnection.java:1520)
... lines omitted ...

Ensure that you followed the steps on upgrading Oracle Internet Directory 9.2.0.x to 10g Release 2 (10.1.2) as documented in Oracle Application Server Upgrade and Compatibility Guide. The instructions are in the "Upgrading the Identity Management Services" chapter.

Reports Server Start/Stop Errors

Oracle Process and Management Notification (OPMN) checks the status of the Report in-process Server using a ping mechanism. The ping URL is specified in the OC4J_BI_Forms process-type in the ORACLE_HOME/opmn/conf/opmn.xml file. The urlping element is present in the ORACLE_HOME/opmn/conf/opmn.xml file:

<process-type id="OC4J_BI_Forms" module-id="OC4J">
...
<category id="urlping-parameters">
<data id="/reports/rwservlet/pingserver?start=auto" value="200" />
</category>
...
<start timeout="900" retry="2"/>
<stop timeout="120"/>
<restart timeout="720" retry="2"/>
...
</process-type>

OPMN sends the ping URL to the Reports Servlet and if the Reports Servlet is up, it responds to the ping. start=auto in the URL means that if the in-process Reports Server is not up while receiving the ping, the Reports Servlet starts the in-process server automatically.

Sometimes, the ping timeout is reached before the in-process Reports Server is fully started (for example, the Reports Server may not be able to start completely within time because of heavy load), as a result of which the URLPing request from OPMN may time out. The ping timeout is the measure that OPMN uses to determine the time that it must wait for a callback from an in-process Reports Server (in OC4J_BI_FORMS) before considering it a timeout. You can configure the ping timeout by adding a ping entry with sufficient timeout configured to the computer's load in the following element in opmn.xml:

<ias-component id="OC4J">
<process-type id="OC4J_BI_Forms" module-id="OC4J">
...
<category id="urlping-parameters">
<process-type id="OC4J_BI_Forms" module-id="OC4J">
  <data id="/reports/rwservlet/pingserver?start=auto" value="200" />
</category>
...
<start timeout="900" retry="2"/>
<stop timeout="120"/>
<restart timeout="720" retry="2" />
<ping timeout="110" interval="30" retry="2" /> -- ping timeout
...
</process-type>
</ias-component>

Then, restart OC4J_BI_Forms. For more information on using OPMN with Reports Server, see Oracle Application Server Reports Services Publishing Reports to the Web.

A.4 Descriptions of Forms and Reports Services Configuration Assistants

Table A-1 lists the Forms and Reports Services configuration assistants in alphabetical order. Different installations use different configuration assistants depending on installation type and configuration options you selected.

For information about configuring Oracle Reports, see Oracle Application Server Reports Services Publishing Reports to the Web. For information about configuring Oracle Forms, see Oracle Application Server Forms Services Deployment Guide.

Table A-1 Forms and Reports Services Configuration Assistants

Configuration Assistant	Description	Log File Location
Application Server Control Configuration Assistant	Starts the Oracle Management Agent and the Application Server Control to deploy applications through the Oracle Enterprise Manager Application Server Control.	not applicable
DCM Repository Backup Assistant	Enables you to back up your DCM repository.	not applicable
Forms Configuration Assistant	Configures the Oracle Application Server Forms Services server and integrates Oracle Application Server Forms Services with Oracle Enterprise Manager Application Server Control.	`ORACLE_HOME/cfgtoollogs/formsConfig.log`
HTTP Server Configuration Assistant	Configures Oracle HTTP Server and registers it with the Oracle Enterprise Manager Application Server Control.	`ORACLE_HOME/Apache/Apache/logs` `ORACLE_HOME/Apache/Apache/httpd.log` `ORACLE_HOME/cfgtoollogs/configtoolstimestamp.log`
Java Security Configuration Assistant	Changes default password and sets and reassigns new passwords for JAAS security.	`ORACLE_HOME/cfgtoollogs/jaznca.log`
OC4J Configuration Assistant	Integrates OC4J with the Oracle Enterprise Manager Application Server Control. It uses the Oracle Enterprise Manager Application Server Control-provided APIs to perform the following steps: Add entries to the `targets.xml` file Add entries to the `iasadmin.properties` file This configuration assistant is dependent on the presence of the `deploy.ini` file.	not applicable
OC4J Instance Configuration Assistant	Configures OC4J instances for deployed Forms and Reports Services applications.	not applicable
OPMN Configuration Assistant	Starts OPMN and OPMN-managed processes.	`ORACLE_HOME/opmn/logs/opmn.log`
Oracle Net Configuration Assistant	Configures the database listener and Forms and Reports Services instances to use the LDAP naming by default.	`ORACLE_HOME/oraInventory/logs/` `installActions<time.stamp>.log`
OracleAS Instance Configuration Assistant	Adds Forms and Reports Services instance name into the `ORACLE_HOME/config/ targets2add.xml` file.	not applicable
Register DCM Plug-Ins With Enterprise Manager Configuration Assistant	Registers DCM plug-ins with Enterprise Manager.	not applicable
Reports Configuration Assistant	Configures the Oracle Reports server and integrates Oracle Reports with Oracle Enterprise Manager Application Server Control.	`ORACLE_HOME/cfgtoollogs/reportsConfig.log`
Web Cache Configuration Assistant	Configures OracleAS Web Cache and registers it with Oracle Enterprise Manager Application Server Control.	`ORACLE_HOME/cfgtoollogs/configtoolstimestamp.log`

For more information on log file locations, refer to Appendix F, "Configuration Assistants" in Oracle Application Server Installation Guide.