B Troubleshooting

B.4.1 Configuration Assistant Failure

Oracle Application Server configuration assistant failures are noted at the bottom of the installation screen. The Oracle Application Server configuration assistant interface displays additional information, if applicable. The configuration assistant’s execution status will be identified by the result. The result codes are:

This result code is written to the following log file:

oraInventory/logs/installActionstimestamp.log

B.4.2 Failure During Component Configuration and Startup

During installation, configuration assistants run when the Configuration Assistants screen appears. If a configuration assistant fails, try the following procedure to correct the problem:

1. Review the installation log files for this Oracle Application Server instance.

2. Review the log files for each configuration assistant located in the ORACLE_HOME/cfgtoollogs directory. Default log file locations are described in Section B.5, "Descriptions of Oracle Application Server Configuration Assistants".

3. Refer to the section describing the configuration assistants in Section B.5, "Descriptions of Oracle Application Server Configuration Assistants".

   1. If the failing configuration assistant has any dependencies, then run the dependencies again. You must do this even if the dependency completed successfully.

   2. Run the failing configuration assistant again. If you are using the installer, select the configuration assistant and click Retry.

      If the configuration assistant fails again after you click Retry, then you must remove the /var/tmp/EM_CONFIG_INSTALL.lk lock entry and try re-running the configuration assistant again.

   3. If an optional configuration assistant fails, and it does not have any dependencies, run the remaining configuration assistants. Uncheck the cancelled optional configuration assistant, highlight and check the next listed configuration assistant, and click Retry.

   4. If configuration assistant failure occurs when running configuration assistant execution commands on the command line, then re-run the configuration assistant execution command again.

      You can use the generated script file named configToolCommands located in the ORACLE_HOME/cfgtoollogs directory to execute the failed configuration assistant again. The configToolCommands script is generated after you exit the installer. During silent or non-interactive installation of Oracle Application Server the configToolCommands script is generated immediately after configuration assistant failure.

      You must set the following environment variables before using the generated script:

      • Set the ORACLE_HOME environment variable to the ORACLE_HOME path.

      • Append the shared library path environment variable with the exact locations of ORACLE_HOME/lib and ORACLE_HOME/network/lib.

        Table 4-15 lists the shared library path environment variables for different platforms

      • For the Register DCM Plug-Ins With EM Configuration Assistant only, set the PERL5LIB environment variable to the ORACLE_HOME/perl/lib/5.6.1 directory.

      
      

      Note: If the description of a configuration assistant includes an "Initial Tasks" section, you must perform these tasks before running the configuration assistant.

      
      

B.4.3 Fatal Errors

Some configuration assistant failures are "fatal errors". You cannot recover from a fatal error by correcting the problem and continuing. You must remove the current installation and reinstall Oracle Application Server. The following tasks describe the recovery procedure:

1. Deinstall the failed installation using the procedure described in Section C.1, "Deinstallation of 10g (9.0.4) Instances".

2. Correct the cause of the fatal error.

3. Reinstall Oracle Application Server.

4. If the fatal error reoccurs, then you must remove all Oracle installations from your computer.

B.4.4 How to Rerun OracleAS Randomize Password Configuration Assistant

The following steps describe how to rerun OracleAS Randomize Password Configuration Assistant:

1. Start Oracle Internet Directory Manager.

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

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

4. Click 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 same value as the schema name. For example, if wireless is the schema name, change the orclpassword attribute value to wireless.

   • Change the orclflexattribute1 to false.

   Click Apply.

   Perform these steps for all of your schemas except ODS and OEM_REPOSITORY.

6. Login to the database location where the OracleAS Randomize Password Configuration Assistant failure is occurring.

7. Run the following SQL script:

   SQL> $ORACLE_HOME/assistants/dbca/admin/unlock.sql

8. Rerun the OracleAS Randomize Password Configuration Assistant.

B.4.5 OC4J Instance Configuration Assistant Errors

If the OC4J Instance Configuration Assistant fails with the following error:

Adding dependent libraries for application 'portal'...done. 
Deploying application 'oraudrepl' to OC4J instance 'OC4J_Portal'... 
ERROR: Caught exception during deploy. 
java.rmi.RemoteException: deploy failed!: ; nested exception is: 
oracle.oc4j.admin.internal.DeployerException: User specified for 
application-client uddirepl, 'uddi_replicator' not found 
at com.evermind.server.rmi.RMIConnection.
EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER(RMIConnection.java:1520)
... lines omitted ...

check that your Oracle Internet Directory was upgraded successfully.

This error is seen when you are installing a middle tier against an Oracle Internet Directory that was upgraded from 9.2.0.x to 10g (9.0.4), but not all the upgrade steps were completed. Make sure you followed the steps on upgrading Oracle Internet Directory 9.2.0.x to 10g (9.0.4) as documented in the Oracle Application Server 10g Upgrading to 10g (9.0.4) guide. The instructions are in the "Upgrading the Identity Management Services" chapter.

B.4.6 UDDI Configuration Assistant Errors

If the UDDI Configuration Assistant fails with the following error:

WARN UddiCA: The DAS Public Group entry cannot be found. Users cannot be
assigned to the group uddi_unlimited_quota_group via DAS application. 
javax.naming.NoPermissionException: [LDAP: error code 50 - Insufficient Access 
Rights]; remaining name 'cn=default,cn=PublicGroups,cn=User Configuration,
cn=Attribute Configuration,cn=DAS,cn=Products,cn=OracleContext,dc=oracle,dc=com' 
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:2953)
... lines omitted ...

check that your Oracle Internet Directory was upgraded successfully.

This error is seen when you are installing a middle tier against an Oracle Internet Directory that was upgraded from 9.2.0.x to 10g (9.0.4), but not all the upgrade steps were completed. Make sure you followed the steps on upgrading Oracle Internet Directory 9.2.0.x to 10g (9.0.4) as documented in the Oracle Application Server 10g Upgrading to 10g (9.0.4) guide. The instructions are in the "Upgrading the Identity Management Services" chapter.

B.4.7 Portal Configuration Assistant Errors

If the Portal Configuration Assistant fails with the following error:

Added DBA group as owner to DAS privilege group OracleDASDeleteUser. 
Error in add_member_to_privilege_group 
LDAP Error: 50: Insufficient access 
p_group_dn: cn=oracledasuserpriv,cn=groups,cn=oraclecontext,dc=oracle,dc=com 
p_member_dn: cn=dba,cn=portal.031111.0449,cn=groups,dc=oracle,dc=com 
ERROR: Could not add DBA group to DAS privilege group OracleDASUserPriv. 
Error in add_owner_to_privilege_group 
LDAP Error: 50: Insufficient access 
p_group_dn: cn=oracledasuserpriv,cn=groups,cn=oraclecontext,dc=oracle,dc=com 
p_member_dn: cn=dba,cn=portal.031111.0449,cn=groups,dc=oracle,dc=com 
ERROR: Could not add DBA group as owner to DAS privilege group 
OracleDASUserPriv 
... 
Error in add_member_to_privilege_group 
LDAP Error: 50: Insufficient access 
p_group_dn: 
cn=oracledascreategroup,cn=groups,cn=oraclecontext,dc=oracle,dc=com 
p_member_dn: 
cn=portal_administrators,cn=portal.031111.0449,cn=groups,dc=oracle,dc=com 
ERROR: Could not add portal_administrators group to DAS privilege group 
OracleDASCreateGroup.

check that your Oracle Internet Directory was upgraded successfully.

This error is seen when you are installing a middle tier against an Oracle Internet Directory that was upgraded from 9.2.0.x to 10g (9.0.4), but not all the upgrade steps were completed. Make sure you followed the steps on upgrading Oracle Internet Directory 9.2.0.x to 10g (9.0.4) as documented in the Oracle Application Server 10g Upgrading to 10g (9.0.4) guide. The instructions are in the "Upgrading the Identity Management Services" chapter.