This appendix describes solutions to common problems that you might encounter when installing Oracle Portal, Forms, Reports and Discoverer. 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 (
Verify that your computer meets the requirements specified in the System Requirements and Specifications document:
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:
Note the error and review the installation log files.
Remove the failed installation by following the steps in Chapter 4, "Deinstalling Oracle Portal, Forms, Reports and Discoverer".
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 Portal, Forms, Reports and Discoverer installer and the Configuration Wizard. 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 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 systems, the default location for the inventory directory is
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.
A user who installed the Oracle Reports components can access them, by default. If you want to allow other users to run
Change the permissions of the following files.
On Linux x86 operating systems:
chmod 750 ORACLE_HOME/bin chmod 750 ORACLE_HOME/bin/rwbuilder chmod 750 COMMON_COMPONENTS_HOME/modules/oracle.dms_11.1.1/*.jar chmod 750 COMMON_COMPONENTS_HOME/modules/oracle.odl_11.1.1/*.jar chmod 750 ORACLE_INSTANCE chmod 750 ORACLE_INSTANCE/bin chmod 750 ORACLE_INSTANCE/config chmod 750 ORACLE_INSTANCE/config/reports chmod 750 ORACLE_INSTANCE/config/reports/bin chmod 750 ORACLE_INSTANCE/config/reports/bin/* chmod 750 ORACLE_INSTANCE/config/FRComponent chmod 750 ORACLE_INSTANCE/config/ReportsToolsComponent chmod 750 ORACLE_INSTANCE/config/ReportsToolsComponent/ReportsTools chmod 750 ORACLE_INSTANCE/config/ReportsToolsComponent/ReportsTools/* chmod 770 ORACLE_INSTANCE/config/ReportsToolsComponent/ReportsTools/rwbuilder.conf chmod 750 ORACLE_INSTANCE/reports chmod 750 ORACLE_INSTANCE/reports/reports_install.properties chmod 750 DOMAIN_HOME/servers/WLS_REPORTS/tmp/_WL_user/ chmod 770 DOMAIN_HOME/servers/WLS_REPORTS/tmp/_WL_user/reports_version/ chmod 770 DOMAIN_HOME/servers/WLS_REPORTS/tmp/_WL_user/reports_version/<random_name>/war chmod 750 directory_mentioned_in_REPORTS_TMP
On Windows operating systems, right-click on the folder, select Properties, then modify the security settings as necessary.
Change the location of the log files so that users will have both read and write access. Modify the
PATH property of the
zrcclient_trace_handler parameters in the
/config/ReportsToolsComponent/ReportsTools/logging.xml (on Linux x86 operating systems) or
\config\ReportsToolsComponent\ReportsTools\logging.xml (on Windows operating systems) file.
During the configuration process, if the database that contains the
_DISCOVERER schema is shut down between the "Create ASInstance" and "Deploy Discoverer" steps, the configuration process will be completed successfully despite the database being down. However, you will not be able to access the Discoverer Plus and Discoverer Viewer URLs.
The following errors can be found in the log file:
connection error. - error while creating the session, check for other errors. - oracle.discoiv.connections.ConnectionStoreException: @ weblogic.common.resourcepool.ResourceDisabledException: Pool @ examplehost.exampledomain.com_SPS3NT_DISCOVERER_PS is disabled, cannot allocate resources to applications..
In this situation, you should do the following:
Start the database.
Restart the Oracle Discoverer instance.
WLS_DISCO Managed Server.
Restart the Administration Server.
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 (
My Oracle Support (formerly OracleMetaLink:
If you do not find a solution for your problem, open a service request.