F Common Issues and Workarounds

F.1.1 Problems Encountered When Running the Oracle Internet Directory Upgrade Assistant From Oracle Universal Installer

The Oracle Internet Directory upgrade assistant is one of the assistants that run near the end of the 10g (10.1.4.0.1) installation procedure when you are upgrading an OracleAS Identity Management installation.

You can get information about the cause of Oracle Internet Directory upgrade assistant errors by looking at the following log file:

ORACLE_HOME\ldap\log\oidca.log

Problem 1

The upgrade assistant log file (oidca.log) reports the following:

OID processes are currently running

This is a result of some Oracle Internet Directory or Oracle Directory Integration Platform processes not being shut down properly in the source Oracle Home.

Solution

Without exiting the Installer, open another terminal window and shut down all the processes in the source Oracle Home. Then, retry the Oracle Internet Directory upgrade assistant from the Oracle Universal Installer configuration assistants page.

Without exiting the Installer, shut down all the processes in the source Oracle Home and then retry the Oracle Internet Directory configuration assistant from the Oracle Universal Installer configuration assistants page.

If you are upgrading from 10g (9.0.4), you can ensure that the proper processes are shut down by using the Oracle Process Manager and Notification Server (OPMN) command utility to start and then stop all processes in the Oracle home.For example, use the following procedure to start all the processes and then shut down all the processes. Note carefully whether or not any errors appear when you are starting or shutting down the processes:

1. Start all the processes in the OracleAS Identity Management 10g (9.0.4) source Oracle home using the following command:

   SOURCE_ORACLE_HOME\opmn\bin\opmnctl startall
   
   

2. Make sure that no errors occurred during startup and make sure that the Oracle Internet Directory server is up and running.

   To verify that Oracle Internet Directory is running, enter one of the following commands.

   If you are running Oracle Internet Directory on a non-secure port:

   SOURCE_ORACLE_HOME\bin\ldapbind -p Non-SSL_port -h
   
   

   If you are running Oracle Internet Directory on a secure port:

   SOURCE_ORACLE_HOME\bin\ldapbind -p SSL_port -h -U 1
   
   

   These commands should return a "bind successful" message.

   
   

   See Also: "Syntax for LDIF and Command-Line Tools" in the Oracle Internet Directory Administrator's Guide for more information about the ldapbind utility

   
   

3. Enter the following command to stop all the processes:

   SOURCE_ORACLE_HOME\opmn\bin\opmnctl stopall
   
   

4. Use the ldapbind command again to verify that Oracle Universal Installer is down and not running.

5. Rerun the Oracle Internet Directory upgrade assistant.

Problem 2

The Oracle Internet Directory upgrade fails with "table or view does not exist" error.

Solution

This problem occurs when the Oracle Internet Directory upgrade assistant is run against a 9.2.0.x OracleAS Metadata Repository containing a 9.2.0.x Oracle Internet Directory.

The solution is to do the following:

1. Create table imcfgregistry in the 9.2.0.x Oracle Internet Directory database repository by running the following SQL statement as ODS schema:

   CREATE TABLE imcfgregistry (Component  VARCHAR2(255),
      instMode VARCHAR2(255),
      IASInstance VARCHAR2(255))
      TABLESPACE OLTS_DEFAULT MONITORING;
   
   

2. Retry the Oracle Internet Directory upgrade assistant from the Oracle Universal Installer configuration assistants screen.

Problem 3

The Oracle Internet Directory configuration assistant fails during the Configuration Assistants phase of the OracleAS Identity Management upgrade with Oracle Universal Installer.

Solution

Check the contents of the following configuration file in the destination Oracle home and verify that the file contains the correct SERVICE_NAME entry for your Metadata Repository. If the value assigned to this entry is incorrect, enter the correct name, save the file, and retry the assistant.

DESTINATION_ORACLE_HOME\network\admin\tnsnames.ora

F.1.2 Problem Stopping Processes in Source Oracle Home During OracleAS Identity Management Upgrade

Problem

When you run the Oracle Universal Installer to upgrade OracleAS Identity Management, a popup dialog notifies you that the installer will shut down some processes in the source Oracle home.

After the installer performs the shutdown, it checks that Oracle Internet Directory is stopped. If Oracle Internet Directory is not stopped for some reason, installer will display another popup dialog notifying you of the problem.

Solution

Examine the following log file to determine the cause of the problem:

DESTINATION_ORACLE_HOME\cfgtoollogs\shutdownprocesses.log

Resolve the problem and then manually stop Oracle Internet Directory in the source Oracle home. Once Oracle Internet Directory is stopped, continue with the OracleAS Identity Management upgrade by clicking Continue in Oracle Universal Installer.

F.1.3 Database Listener Errors When Running Configuration Assistants During OracleAS Identity Management Upgrade

Problem

Oracle Universal Installer invokes configuration assistants at the end of the OracleAS Identity Management upgrade. Some of the configuration assistants require an Oracle Database 10g database listener to connect to the database. If an Oracle Database 10g database listener is not available, those configuration assistants fail.

Often, when this problem occurs, one of the following errors (or a similar error) appears in the installation log files:

java.lang.Exception: Error: Database Listener is down. Please start listener
and make sure database is up before running this script.

OR

java.sql.SQLException: Listener refused the connection with the followingerror:
ORA-12500, TNS:listener failed to start a dedicated server process 

Solution

The installer normally starts an Oracle Database 10g database listener in the destination Oracle home. However, if an Oracle9i Database listener is already running, then the installer fails to start the Oracle Database 10g (10.1.0.2) database listener.

The most common cause of this problem is that you missed the instruction in a pop-up dialog during the installation. This pop-up message indicates during the interview phase of the installation that there is a running database listener running and that you should stop the listener manually before proceeding.

To correct the problem, stop the existing Oracle9i (9.0.1.3) listener, and then start the database listener in the destination Oracle home, as follows:

1. Set the ORACLE_HOME environment variable to point to the destination Oracle home of upgrade.

2. Change directory to bin directory of the destination Oracle home.

3. Run the lsnrctl start command to start the listener.

After the Oracle Database 10g database listener is running, continue with the OracleAS Identity Management upgrade by clicking Retry on the Configuration Assistants page in Oracle Universal Installer.

F.1.4 Oracle Directory Integration Platform Configuration Assistant Fails with Time Synchronization Error

Problem

While upgrading a 10g (9.0.4) distributed OracleAS Identity Management environment, the Oracle Directory Integration Platform configuration assistant fails.

When you check the following log file, you notice an error message indicating that there is time difference of at least 250 seconds between two of the OracleAS Identity Management hosts:

DESTINATION_ORACLE_HOME\ldap\log\oidmon.log

Specifically, the error message says:

Time Difference of at least 250 sec found between DIP_hostname and OID_hostname.
Please sync the time between DIP-hostname and OID-hostname

Solution

Synchronize the system clocks on all nodes where the OracleAS Identity Management components reside so they are running within 250 seconds of each other.

When synchronizing the system clocks, make sure the clocks are set to the same time zone.

After you synchronize the clocks, rerun the Oracle Directory Integration Platform configuration assistant.

F.2.1 Deciding When to Upgrade an Infrastructure Database

Problem

When a newer version of Oracle Database is announced, should I upgrade the OracleAS Metadata Repository database to the new database version?

Solution

In general, use caution when upgrading your Infrastructure database to a new database version. Check Oracle Metalink (http://metalink.oracle.com) for posted articles or announcements that confirm that the database version and upgrade has been tested and is supported for an existing OracleAS Metadata Repository database.

F.2.2 Verifying the Progress of the Database Upgrade Assistant During OracleAS Identity Management Upgrade

Problem

Oracle Universal Installer invokes Database Upgrade Assistant at the end of OracleAS Identity Management Upgrade. Database Upgrade Assistant may take a long time depending on the size and contents of the database. The installer shows progress of the Database Upgrade Assistant by displaying percentage numbers, but no details about the progress are shown on the Configuration Assistants screen in Oracle Universal Installer.

Solution

If you would like to obtain more detailed information about the progress of the Database Upgrade Assistant, examine the log files generated by the Database Upgrade Assistant. The log files reside in:

drive_letter_for_install_disk:\admin\SID\upgrade

In this example, replace SID with the system identifier of the database in the source Oracle home.

To obtain the timestamps of the different stages of the database upgrade, search for the string "COMP_TIME" in the log files. For example,

find "COMP_TIME" *.log

grep ^COMP_TIME *.log

The output of the command identifies each stage of the database upgrade, as well as a timestamp for each stage. For example:

Oracle_Server.log:COMP_TIMESTAMP DBUPG__BGN 2004-12-16 10:11:00 2453356 36660
Oracle_Server.log:COMP_TIMESTAMP UTLIP__END 2004-12-16 10:12:58 2453356 36778
Oracle_Server.log:COMP_TIMESTAMP CATALG_BGN 2004-12-16 10:27:44 2453356 37664
Oracle_Server.log:COMP_TIMESTAMP CATPROC    2004-12-16 11:18:45
Oracle_Server.log:COMP_TIMESTAMP RDBMS      2004-12-16 11:21:50
Oracle_Server.log:COMP_TIMESTAMP JAVAVM     2004-12-16 12:27:24
Oracle_Server.log:COMP_TIMESTAMP XML        2004-12-16 12:41:17
Oracle_Server.log:COMP_TIMESTAMP CATJAVA    2004-12-16 12:45:03
Oracle_Server.log:COMP_TIMESTAMP CONTEXT    2004-12-16 12:49:17
Oracle_Server.log:COMP_TIMESTAMP XDB        2004-12-16 12:56:32
Oracle_Server.log:COMP_TIMESTAMP OWM        2004-12-16 13:01:14
Oracle_Server.log:COMP_TIMESTAMP AMD        2004-12-16 13:11:04
Oracle_Server.log:COMP_TIMESTAMP ORDIM      2004-12-16 13:43:34
Oracle_Server.log:COMP_TIMESTAMP SDO        2004-12-16 13:52:30
Oracle_Server.log:COMP_TIMESTAMP WK         2004-12-16 13:56:24
Oracle_Server.log:COMP_TIMESTAMP DBUPG_END  2004-12-16 14:10:39
PostUpgrade.log:COMP_TIMESTAMP UTLRP_BGN  2004-12-16 14:12:32
PostUpgrade.log:COMP_TIMESTAMP UTLRP_END  2004-12-16 15:29:47

F.2.3 Performance Issues When Using the Metadata Repository Upgrade Assistant (MRUA) to Upgrade the OracleAS Portal Schema

Problem 1

The first time you run MRUA, the OracleAS Portal component (or plug-in) appears to hang or stop working while upgrading the OracleAS Portal schema.

Problem 2

If you run MRUA after the OracleAS Portal schema has already been upgraded, the OracleAS Portal MRUA plug-in, unlike other component MRUA plug-ins, does not immediately report the fact that OracleAS Portal has already been upgraded.

Solution

In most cases, no solution is necessary. Simply wait until the OracleAS Portal component of MRUA finishes processing.The OracleAS Portal component of MRUA performs an extensive sequence of pre-checks that can take several minutes to finish.

In addition, the OracleAS Portal component of MRUA executes for a much longer period of time than any of the other plug-ins. As a result, it can take up to 40 minutes to run.

If Portal plug-in appears to be hanging, review the log files in the following directory to determine whether or not portal upgrade is progressing:

MRUA_HOME\temp\portal

Do not abort MRUA during the OracleAS Portal schema upgrade without first verifying that Portal upgrade has actually stopped processing.

F.2.4 Database Upgrade Assistant Failure During OracleAS Identity Management Upgrade

Oracle Universal Installer invokes Database Upgrade Assistant at the end of OracleAS Identity Management Upgrade. If the Database Upgrade Assistant fails, you can examine the log files generated by the Database Upgrade Assistant. The log files reside in:

drive_letter_for_install_disk:\admin\SID\upgrade

In this example, replace SID with the system identifier of the database in the source Oracle home.

Examine the log files and determine the cause of the failure. In most cases, it is not possible to retry the Database Upgrade Assistant. Instead, you will need to restore the source Oracle home and the database files to their state before the OracleAS Identity Management Upgrade. After the restoration, make sure that the problems which caused the Database Upgrade Assistant to fail are resolved. Then run OracleAS Identity Management Upgrade again.

F.2.5 Problem Upgrading OracleAS Portal Schemas with MRUA

Problem

When running MRUA, the OracleAS Portal upgrade fails and results in invalid versions.

The following error appears in the log files:

EXP-00056: ORACLE error 942 encountered
ORA-00942: table or view does not exist
EXP-00000: Export terminated unsuccessfully
Ending export at Mon May 30 02:59:21 2005

Solution

This error can be caused by providing an incorrect value for the -oracle_home argument on the MRUA command line. When running MRUA be sure to enter the Oracle home of the OracleAS Metadata Repository. This is especially important when upgrading a non-colocated Infrastructure where the OracleAS Metadata Repository is in its own Oracle home.

F.2.6 Error About "DIP" User in Database Upgrade Log Files

Problem

After you upgrade your OracleAS Metadata Repository database as part of an upgrade to Oracle Identity Management 10g (10.1.4.0.1), you might see error messages in the following database upgrade log file:

DESTINATION_ORACLE_HOME\dbma\logs\silent.log

Specifically, you might see the following error about the "DIP" database user:

The username "'DIP'" conflicts with a required user of the same name inOracle Database 10g. To resolve the conflict, click No, drop the user andcreate it with a different name, and then continue with the upgrade.

This error can be ignored.

F.2.7 MRUA Error While Upgrading the Portal Schema

Problem

The following error appears while running the Metadata Repository Upgrade Assistant:

Calling upgrade plugin for PORTAL Error: Component upgrade failed PORTAL Error: PORTAL component version is: 9.0.4.2.0 INVALID

When you check the precheck.log file, you find the following entry:

### ERROR: WWU-00030: Pre-Check mode encountered the following errors
###        203 : ### ERROR:  WWU-00021: The following mandatory object(s) 
are missing or invalid: 
###         '[SYNONYM]PUBLIC.XMLPARSER' \
###         '[SYNONYM]PUBLIC.XMLDOM' \ 

Solution

Manually create the XDB and XMLDOM tablespaces by running the following command in the OracleAS Metadata Repository Oracle home:

DESTINATION_ORACLE_HOME\rdbms\admin\catqm.sql xdb_pwd XDB_Tablespace_NAME TEMP_Tablespace_NAME

For example:

DESTINATION_ORACLE_HOME\rdbms\admin\catqm.sql my_secure_pwd_231 XDB TEMP