D Troubleshooting

This appendix describes solutions to common problems that you might encounter when installing Oracle Portal, Forms, Reports, and Discoverer. It contains the following sections:

• Section D.1, "General Troubleshooting Tips"

• Section D.2, "Troubleshooting Oracle Fusion Middleware Installation"

• Section D.3, "Associating Oracle Reports When Extending a Domain"

• Section D.4, "Need More Help?"

D.1 General Troubleshooting Tips

If you encounter an error during installation:

• Read the Oracle Fusion Middleware Release Notes for the latest updates. The most current version of the release notes is available on Oracle Technology Network (http://www.oracle.com/technology/documentation).

• Verify that your computer meets the requirements specified in Section 2.1.1, "System Requirements and Certification".

• If you entered incorrect information on one of the installation screens, return to that screen by clicking Back until you see the screen.

• If an error occurred while the installer is copying or linking files:

  1. Note the error and review the installation log files.

  2. Remove the failed installation by following the steps in Chapter 3, "Deinstalling Oracle Portal, Forms, Reports, and Discoverer".

  3. Correct the issue that caused the error.

  4. Restart the installation.

D.2 Troubleshooting Oracle Fusion Middleware Installation

This section contains solutions to common problems that you might encounter when installing Oracle Fusion Middleware. The following topics are covered.

D.2.1 Installation Log Files

The installer writes logs files to the Oracle_Inventory_Location/log (for UNIX) or Oracle_Inventory_Location\logs (for Windows) directory. On UNIX systems, if you do not know the location of your Oracle Inventory directory, you can find it in the oraInst.loc file in the following directories (default locations):

• Linux: /etc/oraInst.loc

• HP-UX and Solaris: /var/opt/oracle/oraInst.loc

On Windows systems, the default location for the inventory directory is C:\Program Files\Oracle\Inventory\logs.

The following install log files are written to the log directory:

• installdate-time-stamp.log

• installdate-time-stamp.out

• installActionsdate-time-stamp.log

• installProfiledate-time-stamp.log

• oraInstalldate-time-stamp.err

• oraInstalldate-time-stamp.log

If you start the installer with the -printtime parameter, the timeTakendate-time-stamp.log file is created in the same directory.

D.2.2 Configuration Log Files

To create a log file of your configuration session, start the Configuration Wizard with the -log option, as shown below:

On UNIX:

% ./config.sh -log=log_filename

On Windows:

G:\ config.cmd -log=log_filename

If you specify an absolute path with your log_filename then your log file will be created there. If you only specify a file name with no path, then the log files are created in the ORACLE_HOME/common/bin (for UNIX) or ORACLE_HOME\common\bin (for Windows) directory.

D.3 Associating Oracle Reports When Extending a Domain

For security reasons, Oracle Reports is installed with permissions that enable only the installer to use it. However, there are instances when other users in the group would need access to Oracle Reports (for example, if you extend the domain and add Oracle Portal). Follow the steps below to modify the permissions for additional users.

1. Change the permissions in the following directories to allow read and write access for the desired user (on UNIX systems, use the chmod 750 command; on Windows systems, right-click on the folder and select Properties, then modify the security settings as necessary):

   • ORACLE_HOME/bin

   • ORACLE_HOME/bin/rwbuilder

   • ORACLE_INSTANCE

   • ORACLE_INSTANCE/bin

   • ORACLE_INSTANCE/config

   • ORACLE_INSTANCE/config/FRComponent

   • ORACLE_INSTANCE/bin/config/ReportsToolsComponent

   • ORACLE_INSTANCE/bin/config/ReportsToolsComponent/ReportsTools

2. Change the permissions of the ORACLE_INSTANCE/bin/config/ReportsToolsComponent/ReportsTools/rwbuilder.conf file to give read, write, and execute permissions to the desired user (on UNIX systems, use the chmod 770 command; on Windows systems, right-click on the folder and select Properties, then modify the security settings as necessary).

3. Change the permissions of the DOMAIN_HOME/servers/WLS_REPORTS/stage directory to give read and write permissions to the desired user (on UNIX systems, use the chmod 750 command; on Windows systems, right-click on the folder and select Properties, then modify the security settings as necessary).

4. Change the permissions of the DOMAIN_HOME/servers/WLS_REPORTS/stage/reports/reports/web.war file to give read, write, and execute permissions to the desired user (on UNIX systems, use the chmod 770 command; on Windows systems, right-click on the folder and select Properties, then modify the security settings as necessary).

5. In the ORACLE_INSTANCE/config/ReportsToolsComponent/ReportsTools/logging.xml file, change the location of the log files so that the desired user will have read and write privileges. Edit the PATH property of runtime_trace_handler and zrcclient_trace_handler.

D.4 Need More Help?

If this appendix does not solve the problem you encountered, try these other sources:

• Oracle Fusion Middleware Release Notes, available on the Oracle Technology Network (http://www.oracle.com/technology/documentation)

• My Oracle Support (formerly OracleMetaLink: http://metalink.oracle.com)

If you do not find a solution for your problem, open a service request.