This appendix describes solutions to common problems that you might encounter when installing Oracle Forms and Reports. It contains the following sections:
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 in the Oracle Fusion Middleware Documentation page.
Select the documentation library for your specific product release to view the release notes.
Verify that your computer meets the requirements specified in the Oracle Fusion Middleware System Requirements and Specifications document.
Select the document that is applicable for your release.
If you entered incorrect information on one of the installation screens, return to that screen by clicking Back until you see the screen, or by using the navigation pane on the left side of the screen.
If an error occurred while the installer is copying or linking files:
Note the error and review the installation log files.
Remove the failed installation by following the steps in Chapter 4, "Deinstalling Oracle Forms and Reports".
Correct the issue that caused the error.
Restart the installation.
This section contains information about the log files that are created when running the Oracle Forms and Reports installer and the configuration tool. Log files contain information that can help you troubleshoot problems with your installation or configuration.
The installer writes logs files to the
/log (on UNIX operating systems) or
\logs (on Windows operating systems) directory. On UNIX operating 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):
HP-UX and Solaris:
On Windows operating systems, the location for the inventory directory is
C:\Program Files\Oracle\Inventory\logs. If you are using a 32-bit installer on a 64-bit Windows machine, the inventory directory is
C:\Program Files (x86)\Oracle\Inventory\logs.
The following install log files are written to the log directory:
This is the main log file.
This log file contains the output and error streams during the installation.
This file is used by the installer GUI to keep track of internal information.
This log file contains the overall statistics like time taken to complete the installation, as well as configuration, memory and CPU details.
This log file contains the output stream of the copy session.
If you start the installer with the
-printtime parameter, the
.log files are created in the same directory:
This file contains information for the amount of time taken to move between screens (applicable for GUI installations only).
This file contains time information for the copy session.
If you start the installer with the
-printmemory parameter, the
.log file is created. This file contains memory usage information for the copy session.
On UNIX operating systems:
% ./config.sh -log=log_filename
On Windows operating systems:
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
/common/bin (on UNIX operating systems) or
\common\bin (on Windows operating systems) directory.
If an environment variable used by
startManagedWebLogic.cmd (for example, PATH or CLASSPATH) contains too many characters, Oracle Reports will generate errors when you try to start its Managed Server.
To work around this issue, you can try to convert all directory names longer than eight characters to the Windows short name format. For example,
C:\Oracle11g\Middleware can be converted to
C:\Oracle~1\Middle~1 wherever you define your environment variables that use this path.
You can also reinstall Oracle WebLogic Server to a location where the directory path is shorter than its current location.
For more information about the character limits of the environment variables on your Windows system, refer Article 830473 on the Microsoft Support website (
http://support.microsoft.com/kb/830473), or refer to your operating system documentation.
If you are unable to find a solution for your problem, open a service request.