Oracle® Application Server Installation Guide
10g Release 2 (10.1.2) for Microsoft Windows (64-Bit) on Intel Itanium Part No. B15847-01 |
|
Previous |
Next |
This appendix describes solutions to common problems that you might encounter when installing Oracle Application Server. It contains the following sections:
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 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.2, "Message About Installing in a Non-Empty Directory"
Section F.3.4, "Forgot the Password for the cn=orcladmin Account"
Section F.3.7, "Unable to Run Oracle Application Server On-Network and Off-Network"
Section F.3.9, "Application Server Control Configuration Assistant Failure"
Section F.3.10, "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:
The configuration assistants write log files in the ORACLE_HOME
\cfgtoollogs
directory.
If you want to access the log files created by the configuration assistants, then you need to exit the installer first. The log files are inaccessible if the installer is still in use.
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.5, "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:
ORACLE_HOME connect=dbsid unlock_su_acct=true
where dbsid
is the SID for the database. For example:
ORACLE_HOME 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.3, "Installing Additional Languages".
If you are serving non-English content and forgot to click the Product Languages in 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 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 directory on the CD-ROM to the directory on your computer.
DVD-ROM: Copy the contents of the directory on the DVD-ROM to the directory on your computer.
Problem
You installed Oracle Application Server when the computer was connected to the network, and now you want to run it off-network.
Solution
If you want to run Oracle Application Server on-network as well as off-network, then you need to install a loopback adapter. On computers with static IP address, when you go off-network, your Ethernet adapter will be down (ipconfig
shows cable disconnected) and ipconfig
cannot resolve that IP.
For details on loopback adapters, refer to Section 2.6.6, "Installing a Loopback Adapter".
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 directory.
Fix the problem indicated in the log file, and click Retry to rerun the failed configuration assistant.
Problem
Application Server Control Configuration Assistant fails with the following error message:
Launched configuration assistant 'Application Server Control Configuration Assistant' ------------------------------------------------ Tool type is: Recommended. The command being spawned is: 'C:\Product\OracleAS\Infra/bin/emctlins.bat' Oracle 10g Application Server Control 10.1.2.0.0 Copyright (c) 1996, 2004 Oracle Corporation. All rights reserved. http://mypc.mydomain.com:1810/emd/console/aboutApplication Starting Oracle 10g Application Server Control ...The OracleOH_INFRA_1012ASControl service is starting ..................................................................... ..................................................................... ................................................................ The OracleOH_INFRA_1012ASControl service could not be started. A service specific error occurred: 1. More help is available by typing NET HELPMSG 3547. Invalid Exit Code. The following result code will be used for configuration assistants: 1 Configuration assistant "Application Server Control Configuration Assistant" failed
Solution
If you get the preceding error message, then it means that the Application Server Control Configuration Assistant failed because it tried to configure Application Server Control components using ports that are already in use by other processes.
To fix this, determine the ports that the configuration assistant tried to use, check which ports are already in use, and then reconfigure Application Server Control to use different ports. The steps in detail are:
In the ORACLE_HOME\sysman\config\emd.properties
file, get the port number specified on the EMD_URL
line. This is the port number used by the emagent
process.
In the ORACLE_HOME\sysman\j2ee\config\emd-web-site.xml
file, get the port number listed in the web-site
element. This is the HTTP connection port for Application Server Control.
In the ORACLE_HOME\sysman\j2ee\config\rmi.xml
file, get the port number listed in the rmi-server
element. This is the port number used for Remote Method Invocation (RMI) communication with the Application Server Control OC4J instance.
Run netstat
-a
to check which of the ports determined from the preceding steps are already in use.
For example, to check if port 1851 is already in use by an existing process, you can run the following command:
C:\> netstat -a | find "1851"
For the ports that are already in use, configure Application Server Control to use different ports that are not currently in use.
If the emagent
process port is already in use, then reconfigure it with the following command:
C:\> emctl config agent port new_emagent_port
If the HTTP connection port is already in use, then reconfigure it with the following command:
C:\> emctl config iasconsole port new_AS_Control_HTTP_port
If the RMI port is already in use, then reconfigure it with the following command:
C:\> emctl config iasconsole rmiport new_RMI_port
Click Retry in the Configuration Assistant screen to rerun the Application Server Control Configuration Assistant, or start Application Server Control from the Services control panel. The service name is Oracle
<OracleHomeName>
ASControl
.
Problem
The problem is that Oracle HTTP Server is already running. The OPMN Configuration Assistant - Start HTTP Server fails when you rerun it.
Solution
Before re-running the configuration assistant, stop Oracle HTTP Server with the following command:
Then rerun 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.