Oracle® Application Server Installation Guide
10g Release 2 (10.1.2) for hp HP-UX Itanium, and Linux Itanium Part No. B15870-01 |
|
![]() Previous |
![]() Next |
This appendix describes solutions to common problems that you might encounter when installing Oracle Application Server. It contains the following sections:
The installer writes the following log files:
oraInventory_location
/logs/installActions
timestamp
.log
oraInventory_location
/logs/oraInstall
timestamp
.err
oraInventory_location
/logs/oraInstall
timestamp
.out
If you encounter an error during installation of Oracle Application Server:
Read the Oracle Application Server Release Notes for the latest updates. The release notes are available with the platform-specific documentation. The most current version of the release notes is available on Oracle Technology Network (http://www.oracle.com/technology/documentation
).
Verify that your computer meets the requirements specified in Chapter 2, "Requirements".
If you entered incorrect information on one of the installation screens, then return to that screen by clicking Back until you see the screen.
If a configuration assistant failed, then check the log file for that configuration assistant. Section E.2, "Description of Oracle Application Server Configuration Assistants" lists the configuration assistants and the location of their log files. If you do not see log files from some configuration assistants in the ORACLE_HOME/cfgtoollogs
directory, then exit the installer. This causes the installer to copy the log files to that directory.
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 Appendix D, "Deinstallation and Reinstallation".
Correct the issue that caused the error.
Restart the installation.
This section describes common Oracle Application Server installation problems and solutions:
Section F.3.3, "Message About Installing in a Non-Empty Directory"
Section F.3.5, "Forgot the Password for the cn=orcladmin Account"
Section F.3.9, "OPMN Configuration Assistant - Start HTTP Server Failures"
Problem
Log files are inaccessible.
Solution
There are two sets of log files:
The installer writes the following log files:
oraInventory_location
/logs/installActions
timestamp
.log
oraInventory_location
/logs/oraInstall
timestamp
.err
oraInventory_location
/logs/oraInstall
timestamp
.out
The configuration assistants write log files in the ORACLE_HOME
/cfgtoollogs
directory.
Problem
Linking failed, and ORA errors were displayed during installation
Solution
Exit the installer and check the log files for any error message. In particular, check the ORACLE_HOME/install/make.log
file.
Remove the failed installation. Before reinstalling Oracle Application Server, make sure that your computer meets all the requirements listed in Chapter 2, "Requirements".
Check especially the following requirements:
Check that the kernel parameters are set to the proper values. Note that if you change the value of a kernel parameter, you must exit the installer and restart your computer for the new value to take effect.
Check that you are installing Oracle Application Server in a valid directory. For example, you cannot install Oracle Application Server in a database Oracle home.
Problem
The installer displays a message that you are installing into a non-empty directory.
Solution
If you started an installation and went beyond the Specify File Locations screen, but did not complete the installation, then the installer has already created the Oracle home directory that you specified. If you later try to install again in the same directory, which contains some files created by the installer, then the installer gives a warning that the directory is not empty.
Perform the following steps:
In the Warning dialog box, click No to return to the Specify File Locations screen.
Click Installed Products. The Inventory screen is displayed.
If your Oracle home is listed in the Inventory screen, then you have to deinstall the Oracle home. For details, refer to Appendix D, "Deinstallation and Reinstallation".
If your Oracle home is not listed in the Inventory screen, then you can just delete the files from the Oracle home and continue with the installation.
Problem
Installation was not successful.
Solution
You have to deinstall it first before you can install Oracle Application Server again. For instructions, refer to Appendix D, "Deinstallation and Reinstallation".
Problem
You forgot the password for the cn=orcladmin
account.
Solution
You can reset the password in the database. The DSE root attribute name is orclsupassword
.
Note that after a certain number of failed attempts to connect, the cn=orcladmin
account becomes locked. In this case, you have to unlock the account. Refer to the Section F.3.6, "cn=orcladmin Account Becomes Locked" for instructions on how to unlock the account.
Problem
The cn=orcladmin
account becomes locked after ten failed attempts to connect. This is controlled by the password policy. Ten failed attempts is the default value.
Solution
If you know the cn=orcladmin
password, then you can unlock the account by running the following command:
prompt> ORACLE_HOME/bin/oidpasswd connect=dbsid unlock_su_acct=true
where dbsid is the SID for the database. For example:
prompt> ORACLE_HOME/bin/oidpasswd connect=asdb unlock_su_acct=true OID DB user password: enter_ODS_password OID superuser account unlocked successfully.
The command prompts for the password of the Operational Data Source (ODS) schema. By default, the ODS password is the same as for the cn=orcladmin
and ias_admin
accounts, which you entered during installation.
To change the password policy, refer to Oracle Internet Directory Administrator's Guide.
Problem
Messages in the user interface do not appear in the desired language. They are not displayed correctly.
Solution
Currently Oracle Application Server does not support adding or removing languages after installation.
If you are serving non-English content, then ensure that you add all the languages that you need during installation. To add languages during installation, click the Product Languages button in the Select a Product to Install screen. To check what languages are installed by default, refer to Section 3.4, "Installing Additional Languages".
If you are serving non-English content from the OracleAS Metadata Repository and forgot to click the Product Languages during the installation then the user interface might not display properly because the required fonts were not installed. You can fix this by installing the fonts on the OracleAS Metadata Repository system from the "OracleAS Metadata Repository Upgrade Assistant and Utilities" CD-ROM or from the Oracle Application Server DVD-ROM by performing the following steps:
Insert and mount the "OracleAS Metadata Repository Upgrade Assistant and Utilities" CD-ROM or the Oracle Application Server DVD-ROM.
CD-ROM: Copy the contents of the utilities/fonts
directory on the CD-ROM to the ORACLE_HOME/jdk/jre/lib/fonts
directory.
DVD-ROM: Copy the contents of the repca_utilities/utilities/fonts
directory on the DVD-ROM to the ORACLE_HOME/jdk/jre/lib/fonts
directory.
This part of the section describes general tips for troubleshooting configuration assistant failures. Refer to the following sections for specific configuration assistant failures.
Problem
Configuration assistant failed.
Solution
Check the following:
Check the log files for the failed configuration assistant to determine the problem. The log files are located in the ORACLE_HOME/cfgtoollogs
directory.
Fix the problem indicated in the log file, and click Retry to rerun the failed configuration assistant.
Problem
The OPMN Configuration Assistant - Start HTTP Server fails when you re-run it.
Solution
The problem is that Oracle HTTP Server is already running. Before re-running the configuration assistant, stop Oracle HTTP Server with the following command:
prompt> $ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=HTTP_Server
Then re-run the OPMN Configuration Assistant - Start HTTP Server.
If this appendix does not solve the problem you encountered, then try the following sources:
Oracle Application Server Release Notes, available on the Oracle Technology Network (http://www.oracle.com/technology/documentation
)
OracleMetaLink (http://metalink.oracle.com
)
If you do not find a solution for your problem, then open a service request.