G Troubleshooting

G.2.1 Location of Log Files

There are two sets of log files:

• The installer writes the following log files:

  • oraInventory_location/logs/installActionstimestamp.log

  • oraInventory_location/logs/oraInstalltimestamp.err

  • oraInventory_location/logs/oraInstalltimestamp.out

  • Oracle_Home/install/make.log

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

G.2.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:

1. In the warning dialog, click No to return to the Specify File Locations screen.

2. 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. Refer to Appendix E, "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.

G.2.3 Installer Disappears After Running the Preinstallation Checks

Problem

The installer disappears after running preinstallation checks

Solution

The directory that is the mount point of the CD-ROM or DVD was mounted with incorrect permissions, and this caused the pwd command to not work correctly. When you run pwd, it returns "cannot determine current directory".

To fix:

1. Unmount the CD-ROM.

2. Change permissions of the mount directory to 755.

3. Remount the CD-ROM.

The installer should now run correctly.

G.2.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 E, "Deinstallation and Reinstallation" for instructions.

G.2.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. Refer to the section, Section G.2.6, "cn=orcladmin Account Becomes Locked", for instructions on how to unlock the account.

G.2.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:

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

G.2.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.8, "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.

1. Insert and mount the "OracleAS Metadata Repository Upgrade Assistant and Utilities" CD-ROM or the Oracle Application Server DVD.

2. CD-ROM: Copy the contents of the utilities/fonts directory on the CD-ROM to the ORACLE_HOME/jdk/jre/lib/fonts directory.

   DVD: Copy the contents of the repca_utilities/utilities/fonts directory on the DVD to the ORACLE_HOME/jdk/jre/lib/fonts directory.

G.2.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 oraInventory/logs/installActionstimestamp.log. If you see the following lines:

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

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

G.2.9 Configuration Assistant Failures - General

This section describes general tips for troubleshooting configuration assistant failures. Refer to the next sections for specific configuration assistant failures.

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.

G.2.10 OracleAS Randomize Password Configuration Assistant Failures

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

1. Start Oracle Directory Manager.

2. Enter the Oracle Internet Directory hostname, port, user name, and password.

3. Expand Entry Management > cn=OracleContext > cn=Products > cn=IAS > cn=IAS Infrastructure Databases.

4. Select orclreferencename=your_globaldb_name.

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

6. Using SQL*Plus, log in to the database where the OracleAS Randomize Password Configuration Assistant failure is occurring, and run the following script.

   prompt> sqlplus "sys/password as sysdba"
   SQL> @ORACLE_HOME/assistants/dbca/admin/unlock.sql
   
   

   password specifies the password for the SYS user.

7. Rerun the OracleAS Randomize Password Configuration Assistant.

G.2.11 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.8.6, "TNS_ADMIN"). If it is set, unset it and rerun DBCA by clicking the Retry button in the Configuration Assistants screen.

G.2.12 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 /ASInstalls/ASInfra/sysman/emdrep/config/repository.variables ...
Nov 25, 2004 9:07:35 PM oracle.sysman.emcp.EMConfig addPortEntries
INFO: Updating file /ASInstalls/ASInfra/install/portlist.ini ...
Nov 25, 2004 9:07:35 PM oracle.sysman.emcp.EMConfig updateEmdProps
INFO: Updating file /ASInstalls/ASInfra/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
/ASInstalls/ASInfra/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
/ASInstalls/ASInfra/oc4j/j2ee/OC4J_DBConsole to
/ASInstalls/ASInfra/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

G.2.13 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:

prompt> $ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=HTTP_Server

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

G.2.14 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:

prompt> $ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=OC4J_Security

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

G.2.15 OPMN Configuration Assistant - Start OCA Failures

Problem

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

Solution

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

prompt> $ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=OC4J instancename=oca

Then re-run the OPMN Configuration Assistant - Start OCA.

G.2.16 Re-running chgtocfmt Does Not Work

Problem

Re-running the chgtocfmt script to change back to the original configuration does not work. The hostnames are not converted back to the physical hostname, but the script does not show any errors.

Solution

You can re-run the chgtocfmt script to change back to the original configuration only if you installed the middle tier in a single Oracle home (that is, on the shared disk). Re-running the script in a separate Oracle home installation does not work. To make it work in a separate Oracle home installation, try this workaround:

1. In the ORACLE_HOME/config/ias.properties file, set the VirtualHostName parameter to the virtual hostname that you used in the first run of the chgtocfmt script.

2. Re-run the chgtocfmt script.

3. In the ORACLE_HOME/config/ias.properties file, set the VirtualHostName parameter to the physical hostname.

G.2.17 WARNING: DCM service may not be available at this time

Problem

When installing the first node of an OracleAS Cluster (Identity Management), the Java Security Configuration Assistant may return the following message:

WARNING: DCM service may not be available at this time to synchronize $ORACLE_HOME/j2ee/home/config/jazn-data.xml file.

This is due to a failure in updating the DCM repository and could happen if your load balancer virtual server is not configured to return immediately to the calling client when the backend services to which it forwards traffic are unavailable.

Solution

Perform the following steps to correct the problem:

1. Run the following command after installation completes:

   prompt> $ORACLE_HOME/dcm/bin/dcmctl updateConfig -ct jazn
   
   

2. Verify that the dcmctl updateConfig command did not return any errors.

3. Use the following command to verify that the password is correct:

   prompt> $ORACLE_HOME/jdk/bin/java
                   -Doracle.security.jazn.config=./jazn/install/jazn.xml
                   -jar jazn.jar -checkpasswd jazn.com admin -pw admin_password
   
   

G.3.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 LIBPATH environment variable contains $ORACLE_HOME/lib32, and that your LIBPATH environment variable contains $ORACLE_HOME/lib. Then run the command (all on one line):

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

G.3.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:

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

   prompt> $ORACLE_HOME/bin/oidadmin
   
   

2. In the Connect screen, enter the Oracle Internet Directory connect information. Log in as the Oracle Internet Directory superuser (cn=orcladmin).

3. Expand Entry Management > cn=OracleContext > cn=Products > cn=IAS > cn=IAS Instances.

4. Under cn=IAS Instances, select the instance that you want to delete.

5. From the menu, select Edit > Delete.

6. Expand Entry Management > cn=OracleContext > cn=Groups.

7. Select cn=IASAdmins.

8. In the Properties tab, remove the instance from the uniquemember field by editing the field. Do not select Edit > Delete from the menu.

9. Click Apply.

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

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

   prompt> $ORACLE_HOME/bin/oidadmin
   
   

2. In the Connect screen, enter the Oracle Internet Directory connect information. Log in as the Oracle Internet Directory superuser (cn=orcladmin).

3. Expand Entry Management > cn=OracleContext > cn=Products > cn=Portal > cn=UltraSearch > cn=Database Instances > orclApplicationCommonName=infrastructure_database_name.

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

5. After you have deleted all the entries under orclApplicationCommonName=infrastructure_database_name, right-click this entry and delete it.

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

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

8. After you have deleted all the entries under cn=infrastructure_database_name, right-click this entry and delete it.

9. Click Apply.

G.3.4 Deconfiguration Failed on Distributed OracleAS Cluster (Identity Management)

Problem

When running deconfiguring the first OracleAS Single Sign-On node on a Distributed OracleAS Cluster (Identity Management) configured as in Section 12.4.2, "Case 2: Client ---[HTTPS]---> Load Balancer ---[HTTPS]---> Oracle HTTP Server", the Deconfig tool fails. The log file located at $ORACLE_HOME/sso/log/ssoreg.log has the following error:

Unable to open file $ORACLE_HOME/Apache/Apache/conf/osso/osso.conf.
Please check the file path. 
SSO registration tool failed.  Please check the error in this log file, correct the problem and re-run the tool.

Solution

The Deconfig tool failed because it was unable to find the $ORACLE_HOME/Apache/Apache/conf/osso/osso-https.conf file. Perform the following steps to correct this problem:

1. Create a link from osso-https.conf to osso.conf:

   cd $ORACLE_HOME/Apache/Apache/conf/osso
   ln osso-https.conf osso.conf
   
   

2. Run the Deconfig tool again.