This appendix describes solutions to common problems that you might encounter when installing Application Developer.
This appendix contains the following sections:
If you encounter an error during installation:
Read the Oracle Fusion Middleware Release Notes for Linux x86 or Oracle Fusion Middleware Release Notes for Microsoft Windows (32-Bit) (depending on your platform) for the latest updates. The most current version of the release notes is available on the Oracle Fusion Middleware 11 g Release 1 (11.1.1) Documentation page on Oracle Technology Network:
http://www.oracle.com/technetwork/middleware/docs/middleware-093940.html
Click the View Library link for the documentation library corresponding to your release. The Release Notes are available in the library.
Verify that your computer meets the requirements specified in the System Requirements and Specifications document:
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-requirements-100147.html
If you have 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:
Note the error and review the installation log files.
Remove the failed installation by following the steps in Chapter 4.
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 Application Developer installer and the Oracle Fusion Middleware Configuration Wizard. Log files contain information that can help you troubleshoot problems with your installation or configuration.
This section contains the following topics:
The installer writes logs files to the Oracle_Inventory_Location/log directory on UNIX, and Oracle_Inventory_Location\logs directory on Windows.
On UNIX systems, if you do not know the location of your Oracle Inventory directory, you can find it in the MW_HOME/oracle_common/oraInst.loc file. 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
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, as well as 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 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 is created there. If you only specify a file name with no path, then the log files are created in the MW_HOME/oracle_common/common/bin directory on UNIX, and MW_HOME\oracle_common\common\bin directory on Windows.
The JRE location used by the Application Developer installer is stored in the MW_HOME/oracle_common/oui/oraparam.ini file on UNIX, and MW_HOME\oracle_common\oui\oraparam.ini file on Windows. This file is used by OPatch and Oracle Universal Installer (OUI) to determine the location of your preferred JRE.
It is possible to change the location of your JRE (for example, the JRE directory is moved out of the Middleware Home). If this happens, you will get an error message when trying to run OPatch or OUI since the JRE location can no longer be found. If this happens, you can do one of the following:
Edit the MW_HOME/oracle_common/oui/oraparam.ini file on UNIX, and MW_HOME\oracle_common\oui\oraparam.ini file on Windows, to point to the new JRE location.
Use the -jreLoc command line option to point to the new JRE location. See Section 2.2.2 for more information.
If this appendix does not solve the problem you encountered, try these other sources:
Oracle Fusion Middleware Release Notes for Linux x86 or Oracle Fusion Middleware Release Notes for Microsoft Windows (32-Bit) (depending on your platform). The most current version of the release notes is available on the "Oracle Fusion Middleware 11 g Release 1 (11.1.1) Documentation" page on Oracle Technology Network:
http://www.oracle.com/technetwork/middleware/docs/middleware-093940.html
Click the View Library link for the documentation library corresponding to your release. The Release Notes are available in the library.
My Oracle Support (formerly OracleMetaLink: https://support.oracle.com/)
If you do not find a solution for your problem, open a service request.