The following sections are included:
If this Troubleshooting appendix does not solve the problem you encountered, try looking for a solution on My Oracle Support, see https://support.oracle.com/ (formerly Oracle MetaLink). You can also raise a service request, if you are unable to find a solution for your problem.
You may encounter errors during installing and configuring Oracle Forms and Reports.
Follow the tips to resolve the errors:
To complete the configuration, Windows DOS shells must be run with Administrator permissions and UNIX shells must be owned by the same user who performed the installation (for example, oracle). Failure to follow this instruction may result in the configuration failing silently.
See Install and Configure in Release Notes for Oracle Fusion Middleware Infrastructure for the latest updates and issues related to Oracle Fusion Middleware product installation and configuration.
Verify that your computer meets the requirements specified in the Oracle Fusion Middleware System Requirements and Specifications. Select the document that is applicable for your release.
Verify that your environment meets the certification requirements for your release and platform, as specified on the Oracle Fusion Middleware Supported System Configurations page.
To review the latest Oracle Fusion Middleware Release Notes for other products, see: http://www.oracle.com/technetwork/middleware/fusion-middleware/documentation/index.htm. Select the documentation library for your specific product release to view the release notes.
If you entered incorrect information on one of the installation screens, return to previous screen by clicking Back until you see the specific screen, or by using the navigation pane on the left side of the screen.
If encounter error while the installer is copying or linking files:
Note the error and review the installation log files.
Remove the failed installation.
Correct the issue that caused the error.
Restart the installation.
Log files are created when running the Oracle Forms and Reports installer and the configuration tool.
The following log files contains information that can help you to troubleshoot problems during installation or configuration:
The log files generated during your installation help you determine whether any problems occurred during installation.
The installer writes logs files to the Oracle_Inventory_Location/log (on UNIX operating systems) or Oracle_Inventory_Location\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):
Linux: /etc/oraInst.loc
HP-UX and Solaris: /var/opt/oracle/oraInst.loc
On Windows operating systems, the 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
This is the main log file.
installdate-time-stamp.out
This log file contains the output and error streams during the installation.
installActionsdate-time-stamp.log
This file is used by the installer GUI to keep track of internal information.
installProfiledate-time-stamp.log
This log file contains the overall statistics like time taken to complete the installation, also configuration, memory and CPU details.
oraInstalldate-time-stamp.log
This log file contains the output stream of the copy session.
If you start the installer with the -printtime parameter, the timeTakendate-time-stamp.log and timedate-time-stamp.log files are created in the same directory:
timeTakendate-time-stamp.log
This file contains information for the amount of time taken to move between screens (applicable for GUI installations only).
timedate-time-stamp.log
This file contains time information for the copy session.
If you start the installer with the -printmemory parameter, the memorydate-time-stamp.log file is created. This file contains memory usage information for the copy session.
To create a log file of your configuration session, start the configuration tool with the -log option.
For specific operating systems use the following -log option.
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 ORACLE_HOME/common/bin (on UNIX operating systems) or ORACLE_HOME\common\bin (on Windows operating systems) directory.
Oracle Reports will generate errors if the environment variable contains too many characters.
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 information about the character limits of the environment variables on your Windows system, see Article 830473 (http://support.microsoft.com/kb/830473) on the Microsoft Support website, or refer to your operating system documentation.