H Troubleshooting

This appendix describes solutions to common problems that you might encounter when installing Oracle Application Server. It contains the following sections:

Section H.1, "Log Files"
Section H.2, "General Troubleshooting Tips"
Section H.3, "Installation Problems and Solutions"
Section H.4, "Deinstallation Problems and Solutions"
Section H.5, "Need More Help?"

H.1 Log Files

The installer writes the following log files:

inventory_location\logs\installActionstimestamp.log
inventory_location\logs\oraInstalltimestamp.err
inventory_location\logs\oraInstalltimestamp.out

The default inventory_location is:

C:\Program Files\Oracle\Inventory

H.2 General Troubleshooting Tips

If you encounter an error during installation:

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 4, "Requirements".
If you are installing a middle tier, check that the OracleAS Infrastructure with which you want to associate the middle tier is running during installation.
If you entered incorrect information on one of the installation screens, return to that screen by clicking Back until you see the screen.
If a configuration assistant failed, check the log file for that configuration assistant. Section G.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, 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:
1. Note the error and review the installation log files.
2. Remove the failed installation by following the steps in Appendix F, "Deinstallation and Reinstallation".
3. Correct the issue that caused the error.
4. Restart the installation.

H.3 Installation Problems and Solutions

This section describes common installation problems and solutions:

Section H.3.1, "Location of Log Files"
Section H.3.2, "Message About Installing in a Non-Empty Directory"
Section H.3.3, "Installer Does Not Appear"
Section H.3.4, "Unable to Clean Up a Failed Installation"
Section H.3.5, "Forgot the Password for the cn=orcladmin Account"
Section H.3.6, "cn=orcladmin Account Becomes Locked"
Section H.3.7, "User Interface Does Not Display in the Desired Language, or Does Not Display Properly"
Section H.3.8, "Installer Does Not Display Correct Database Name for OracleAS Metadata Repository"
Section H.3.9, "Unable to Run Oracle Application Server On-Network as Well as Off-Network"
Section H.3.10, "Configuration Assistant Failures - General"
Section H.3.11, "OracleAS Randomize Password Configuration Assistant Failures"
Section H.3.12, "Database Configuration Assistant (DBCA) Failures"
Section H.3.13, "Harmless Error Message from Database Configuration Assistant (DBCA)"
Section H.3.14, "Application Server Control Configuration Assistant Failure"
Section H.3.15, "OPMN Configuration Assistant - Start HTTP Server Failures"
Section H.3.16, "OPMN Configuration Assistant - Start DAS Instance Failures"
Section H.3.17, "OPMN Configuration Assistant - Start OracleAS Certificate Authority Failures"

H.3.1 Location of Log Files

There are two sets of log files:

The installer writes the following log files:
- inventory_location\logs\installActionstimestamp.log
- inventory_location\logs\oraInstalltimestamp.err
- inventory_location\logs\oraInstalltimestamp.out
The default inventory_location is:
```
C:\Program Files\Oracle\Inventory
```
The configuration assistants write log files in the ORACLE_HOME\cfgtoollogs directory.

Note that if you want to access the log files created by the configuration assistants, you need to exit the installer first. The log files are inaccessible if the installer is still in use.

H.3.2 Message About Installing in a Non-Empty Directory

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, 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, the installer gives a warning that the directory is not empty.

Steps to take:

In the warning dialog, click No to return to the Specify File Locations screen.
In the Specify File Locations screen, click Installed Products. This displays the Inventory screen.

If your Oracle home is listed in the Inventory screen, then you have to deinstall the Oracle home. See Appendix F, "Deinstallation and Reinstallation" for details.

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.

H.3.3 Installer Does Not Appear

Problem

The installer does not appear when you run setup.exe.

Solution

If you are installing Oracle Application Server on a computer that is already running Oracle Database 10g, then you have to start up the installer with the following option:

E:\> setup.exe -J-Dsun.java2d.noddraw=true

H.3.4 Unable to Clean Up a Failed Installation

If your installation was not successful, you have to deinstall it first before you can install Oracle Application Server again. Refer to Appendix F, "Deinstallation and Reinstallation" for instructions.

H.3.5 Forgot the Password for the cn=orcladmin Account

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. See the next section, Section H.3.6, "cn=orcladmin Account Becomes Locked", for instructions on how to unlock the account.

H.3.6 cn=orcladmin Account Becomes Locked

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, you can unlock the account by running the following command:

C:\> ORACLE_HOME\bin\oidpasswd connect=dbsid unlock_su_acct=true

where dbsid is the SID for the database. For example:

C:\> 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 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, see the Oracle Internet Directory Administrator's Guide.

H.3.7 User Interface Does Not Display in the Desired Language, or Does Not Display Properly

Problem

Messages do not appear in the desired language, or messages 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, be sure 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 see which languages are installed by default, see Section 5.6, "Installing Additional Languages".

If you are serving non-English content and forgot to click the Product Languages in the installation, 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.

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.

H.3.8 Installer Does Not Display Correct Database Name for OracleAS Metadata Repository

Problem

During middle-tier installation, in the Select OracleAS Metadata Repository screen, which is the screen where you select the OracleAS Metadata Repository that you want to use for the middle tier, the installer does not display correctly the names of the available OracleAS Metadata Repository databases.

Solution

Check the log file C:\Program Files\Oracle\Inventory\logs\installActionstimestamp.log. If you see these lines:

*** Select OracleAS Metadata Repository Page*** 
Error:*** Alert: Error validating repository on multiple hosts and ports.
A database hostname or port is missing.

it means that your OracleAS Metadata Repository database name contains PORT or HOST in uppercase characters. To fix the problem, change the name of the database so that it does not contain PORT or HOST in uppercase characters.

H.3.9 Unable to Run Oracle Application Server On-Network as Well as Off-Network

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, 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, see Section 4.7.6, "Installing a Loopback Adapter".

H.3.10 Configuration Assistant Failures - General

This section describes general tips for troubleshooting configuration assistant failures. See the next sections for specific configuration assistant failures. See also Appendix G, "Configuration Assistants".

Problem

Configuration assistant failed

Solution

Configuration assistants fail from a variety of causes. Some things you can check are:

Check that the listener, database, and Oracle Internet Directory associated with the OracleAS Infrastructure are up and running. If not, start them up and click the Retry button to rerun the configuration assistant that failed.
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.

H.3.11 OracleAS Randomize Password Configuration Assistant Failures

Before rerunning OracleAS Randomize Password Configuration Assistant, you need to perform these steps:

Start Oracle Directory Manager.
Enter the Oracle Internet Directory hostname, port, user name, and password.
Expand Entry Management > cn=OracleContext > cn=Products > cn=IAS > cn=IAS Infrastructure Databases.
Select orclreferencename=your_globaldb_name.
For each schema under the your_globaldb_name tree, there is an orclreferencename entry. For the orclreferencename entry:
- Change the value of the orclpassword attribute to the schema name. For example, if wireless is the schema name, change the orclpassword attribute value to wireless.
- Change orclflexattribute1 to false.
Click Apply.

Perform these steps for all the schemas except ODS and OEM_REPOSITORY.
Using SQL*Plus, log in to the database where the OracleAS Randomize Password Configuration Assistant failure is occurring, and run the following script.
```
C:\> sqlplus "sys/password as sysdba"
SQL> @ORACLE_HOME\assistants\dbca\admin\unlock.sql
```
password specifies the password for the SYS user.
Rerun the OracleAS Randomize Password Configuration Assistant.

H.3.12 Database Configuration Assistant (DBCA) Failures

Problem

DBCA fails with the following error:

Open wallet failedoracle.net.config.ServiceAliasException
at oracle.net.config.ServiceAlias.<init>(Compiled Code)
at oracle.net.config.Service.<init>(Compiled Code)
at oracle.net.config.DatabaseService.<init>(Compiled Code)
at oracle.sysman.assistants.util.NetworkUtils.registerDBWithDirSrvc(NetworkUtils.j ava:1137)
at oracle.sysman.assistants.dbca.backend.DirServiceStep.executePreReqImpl(Compiled  Code)
at oracle.sysman.assistants.dbca.backend.PrerequisiteStep.executeImpl(Prerequisite  Step.java:149)
at oracle.sysman.assistants.dbca.backend.Step.execute(Compiled Code)
at oracle.sysman.assistants.dbca.backend.PostDBCreationStep.executeImpl(Compiled Code)
at oracle.sysman.assistants.dbca.backend.Step.execute(Compiled Code)
at oracle.sysman.assistants.dbca.backend.Host$ModeRunner.run(Compiled Code)
at java.lang.Thread.run(Thread.java:466)
ERROR :oracle.sysman.assistants.util.NetAPIException

Solution

This error occurs if the TNS_ADMIN environment variable is set. The TNS_ADMIN environment variable should not be set (see Section 4.5.4, "TNS_ADMIN"). If it is set, unset it and rerun DBCA by clicking the Retry button in the Configuration Assistants screen.

H.3.13 Harmless Error Message from Database Configuration Assistant (DBCA)

If you see the following "error copying OC4J config files" message in your log file, the message is harmless and can be ignored.

Nov 25, 2004 9:07:30 PM oracle.sysman.emcp.EMConfig updateReposVars
INFO: Updating file /AS1012Installs/AS1012Infra/sysman/emdrep/config/repository.variables ...
Nov 25, 2004 9:07:35 PM oracle.sysman.emcp.EMConfig addPortEntries
INFO: Updating file /AS1012Installs/AS1012Infra/install/portlist.ini ...
Nov 25, 2004 9:07:35 PM oracle.sysman.emcp.EMConfig updateEmdProps
INFO: Updating file /AS1012Installs/AS1012Infra/sysman/config/emd.properties ...
Nov 25, 2004 9:07:35 PM oracle.sysman.emcp.EMConfig updateConfigFiles
INFO: targets.xml file is updated successfully
Nov 25, 2004 9:07:35 PM oracle.sysman.emcp.EMConfig updateEmomsProps
INFO: Updating file
/AS1012Installs/AS1012Infra/sysman/config/emoms.properties ...
Nov 25, 2004 9:07:35 PM oracle.sysman.emcp.EMConfig updateConfigFiles
INFO: emoms.properties file is updated successfully
Nov 25, 2004 9:07:40 PM oracle.sysman.emcp.EMConfig copyOC4JDir
WARNING: Error copying OC4J config files from
/AS1012Installs/AS1012Infra/oc4j/j2ee/OC4J_DBConsole to
/AS1012Installs/AS1012Infra/oc4j/j2ee/OC4J_DBConsole_hostname.domain_portaldb
Nov 25, 2004 9:07:40 PM oracle.sysman.emcp.EMConfig startOMS 
INFO: Starting the DBConsole ...
Nov 25, 2004 9:08:26 PM oracle.sysman.emcp.EMConfig perform 
INFO: DBConsole is started successfully

H.3.14 Application Server Control Configuration Assistant Failure

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 error message above, 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 RMI communication with the Application Server Control OC4J instance.
Run "netstat -a" to check which of the ports determined from the steps above 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, reconfigure it with the following command:
```
C:\> emctl config agent port new_emagent_port
```
If the HTTP connection port is already in use, reconfigure it with the following command:
```
C:\> emctl config iasconsole port new_AS_Control_HTTP_port
```
If the RMI port is already in use, reconfigure it with the following command:
```
C:\> emctl config iasconsole rmiport new_RMI_port
```
Click Retry in the Configuration Assistants 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.

H.3.15 OPMN Configuration Assistant - Start HTTP Server Failures

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:

C:\> ORACLE_HOME\opmn\bin\opmnctl stopproc ias-component=HTTP_Server

Then re-run the OPMN Configuration Assistant - Start HTTP Server.

H.3.16 OPMN Configuration Assistant - Start DAS Instance Failures

Problem

The OPMN Configuration Assistant - Start DAS Instance fails when you re-run it.

Solution

The problem is that the Oracle Delegated Administration Services instance is already running. Before re-running the configuration assistant, stop the Oracle Delegated Administration Services instance with the following command:

C:\> ORACLE_HOME\opmn\bin\opmnctl stopproc ias-component=OC4J

Then re-run the OPMN Configuration Assistant - Start DAS Instance.

H.3.17 OPMN Configuration Assistant - Start OracleAS Certificate Authority Failures

Problem

The OPMN Configuration Assistant - Start OracleAS Certificate Authority fails when you re-run it.

Solution

The problem is that the OracleAS Certificate Authority instance is already running. Before re-running the configuration assistant, stop the OracleAS Certificate Authority instance with the following command:

C:\> ORACLE_HOME\opmn\bin\opmnctl stopproc ias-component=OC4J instancename=oca

Then re-run the OPMN Configuration Assistant - Start OracleAS Certificate Authority.

H.4 Deinstallation Problems and Solutions

This section describes common problems related to deinstallation:

Section H.4.1, "Obsolete Partner URLs Still Remain on the OracleAS Single Sign-On Administration Screen"
Section H.4.2, "Unable to Reuse Instance Name of a Deleted Instance"
Section H.4.3, "Unable to Reuse Database Name"

H.4.1 Obsolete Partner URLs Still Remain on the OracleAS Single Sign-On Administration Screen

Problem

After deinstallation, some partner application entries that are obsolete remain on the OracleAS Single Sign-On Administration screen.

Solution

Run the command to de-register the entries for the obsolete partner applications. The command is similar to the command for registration, except that the -update_mode parameter is set to DELETE.

Make sure your PATH environment variable contains %ORACLE_HOME%\lib. Then run the command (all on one line):

C:\> %ORACLE_HOME%\jdk\bin\java
 -jar %ORACLE_HOME%\sso\lib\ossoreg.jar
 -oracle_home_path %ORACLE_HOME%
 -site_name hostname.domain
 -config_mod_osso TRUE
 -mod_osso_url http://hostname.domain:port
 -u userid
 -update_mode DELETE

For -site_name hostname.domain, specify the computer where the middle tier is installed. Include also the domain name.

For -mod_osso_url http://hostname.domain:port, specify the computer where the middle tier is installed, and the port number on which Oracle HTTP Server is listening.

For -u userid, specify the operating system user who can start up the middle-tier processes.

For a detailed explanation of the parameters, see chapter 4 of the Oracle Application Server Single Sign-On Administrator's Guide.

H.4.2 Unable to Reuse Instance Name of a Deleted Instance

Problem

You get an error when you try to name a new Oracle Application Server instance using the name of an instance that you deleted.

Solution

The name of the deleted instance must be removed from Oracle Internet Directory before you can reuse it. To remove entries for a deleted instance from Oracle Internet Directory, perform these steps:

Start up Oracle Directory Manager. Oracle home refers to the home where you installed Oracle Internet Directory.

Select Start > Programs > Oracle - OracleHomeName > Integrated Management Tools > Oracle Directory Manager.
In the Connect screen, enter the Oracle Internet Directory connect information. Log in as the Oracle Internet Directory superuser (cn=orcladmin).
Expand Entry Management > cn=OracleContext > cn=Products > cn=IAS > cn=IAS Instances.
Under cn=IAS Instances, select the instance that you want to delete.
From the menu, select Edit > Delete.
Expand Entry Management > cn=OracleContext > cn=Groups.
Select cn=IASAdmins.
In the Properties tab, remove the instance from the uniquemember field by editing the field. Do not select Edit > Delete from the menu.
Click Apply.

H.4.3 Unable to Reuse Database Name

Problem

You get an error when you try to use the same global database name or SID as the one that you deleted.

Solution

You might see this problem if you deinstall OracleAS Metadata Repository but not Oracle Internet Directory, and you want to reuse the Oracle Internet Directory and the same database name or SID when you install another OracleAS Metadata Repository. The Oracle Internet Directory still contains the name of the deleted OracleAS Metadata Repository. You need to remove this name before you can reuse it.

Note:

Do not perform this procedure if you are deinstalling a middle tier.

Start up Oracle Directory Manager. Oracle home refers to the home where you installed Oracle Internet Directory.

Select Start > Programs > Oracle - OracleHomeName > Integrated Management Tools > Oracle Directory Manager.
In the Connect screen, enter the Oracle Internet Directory connect information. Log in as the Oracle Internet Directory superuser (cn=orcladmin).
Expand Entry Management > cn=OracleContext > cn=Products > cn=Portal > cn=UltraSearch > cn=Database Instances > orclApplicationCommonName=infrastructure_database_name.
Delete all the child entries under orclApplicationCommonName=infrastructure_database_name, starting with the inner-most child entry. To delete an entry, right-click each child entry and select Delete from the pop-up menu. Click Yes in the Confirmation dialog. When deleting child entries, you may get some error messages. You can ignore these error messages.
After you have deleted all the entries under orclApplicationCommonName=infrastructure_database_name, right-click this entry and delete it.
Expand Entry Management.

Expand the Default Subscriber entry. You need to expand each term separately. For example: if your default subscriber is "dc=us,dc=oracle,dc=com", you need to expand "dc=com", then expand "dc=oracle", then expand "dc=us".

Then expand cn=OracleContext > cn=Products > cn=Portal > cn=UltraSearch > cn=Database Instances > cn=infrastructure_database_name.
Delete all the child entries under cn=infrastructure_database_name, starting with the inner-most child entry. To delete an entry, right-click each child entry and select Delete from the pop-up menu. Click Yes in the Confirmation dialog. When deleting child entries, you may get some error messages. You can ignore these error messages.
After you have deleted all the entries under cn=infrastructure_database_name, right-click this entry and delete it.
Click Apply.

H.5 Need More Help?

If this appendix does not solve the problem you encountered, try these other 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, open a service request.