Skip Headers
Oracle® Fusion Middleware Installation Guide for Oracle Portal, Forms, Reports and Discoverer
11g Release 1 (11.1.1)
E10421-02
  Go To Documentation Library
Library
Go To Product List
Product
Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
 
Next
Next
 

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:

D.1 General Troubleshooting Tips

If you encounter an error during 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 (on UNIX operating systems) or Oracle_Inventory_Location\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):

  • 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

    This is the main log ifle.

  • 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 tbe 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 amout 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.

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 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.

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 Errors Accessing the Discoverer Plus and Discoverer Viewer URLs

During the configuration process, if the database that contains the prefix_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
@ staeb57.us.oracle.com_db4405.us.oracle.com_SPS3NT_DISCOVERER_PS is
disabled,
cannot allocate resources to applications.. 

In this situation, you should do the following:

  1. Start the database.

  2. Restart the Oracle Discoverer instance.

  3. Restart the WLS_DISCO Managed Server.

  4. Restart the Administration Server.

D.5 Need More Help?

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

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