2 Understanding Version Compatibility

2.2.1 Running 10.1.2 Middle Tiers with 9.0.2 or 9.0.3 Middle Tiers

Multiple versions of the Oracle Application Server middle tier installations can share common infrastructure services.

For example, if you have three Release 2 (9.0.2) middle tier installations, then you can upgrade one of those middle tiers to 10g Release 2 (10.1.2). This mixed environment is a supported transitional configuration.

However, you must consider the following issues and workarounds when running 10g Release 2 (10.1.2) middle tiers with Release 2 (9.0.2), Release 2 (9.0.3), or 10g (9.0.4) middle tiers:

• Section 2.6.2, "Assigning the Enterprise Manager Web Site Port When Installing Release 2 (9.0.2) or Release 2 (9.0.3) on a 10g (9.0.4) or 10g Release 2 (10.1.2) Host"

• Section 2.6.3, "Problems Accessing 10g Release 2 (10.1.2) Instances from the Release 2 (9.0.2) or Release 2 (9.0.3) Farm Page"

• Section 2.6.4, "Running the dcmctl getState Command from a 10g Release 2 (10.1.2) Instance"

• Section 2.6.13, "Middle Tiers Within an OracleAS Cluster Must Be the Same Version"

2.2.2 Running 10.1.2 Middle Tiers with a Release 2 (9.0.2) Infrastructure

You can install 10g Release 2 (10.1.2) middle tiers against a Release 2 (9.0.2) OracleAS Infrastructure.

You can also upgrade your middle tiers to 10g Release 2 (10.1.2) before you upgrade your Release 2 (9.0.2) OracleAS Identity Management or OracleAS Metadata Repository.

However, you must consider the following issues and workarounds when Running 10g Release 2 (10.1.2) Middle Tiers with a Release 2 (9.0.2) OracleAS Infrastructure:

• Section 2.6.5, "Updating an Entry in the Release 2 (9.0.2) Oracle Internet Directory Before Installing the 10g Release 2 (10.1.2) Middle Tier"

• Section 2.6.6, "Problems Logging In to OracleAS Portal"

• Section 2.6.8, "Oracle Delegated Administration Services: "Resource Access Information" Section Shows Incorrect User Resources"

• Section 2.6.9, "UDDI: Ping the Servlet Endpoint Returns "500 Internal Server Error""

• Section 2.6.10, "Using OracleAS Wireless 10g Release 2 (10.1.2) with a Release 2 (9.0.2) OracleAS Metadata Repository"

• Section 2.6.11, "Cannot Register Oracle Database 10g Against Release 2 (9.0.2) Identity Management"

2.2.3 Running 10.1.2 Middle Tiers with 9.0.4 Middle Tiers

In general, you can run 10g Release 2 (10.1.2) middle tiers and Release 2 (9.0.2), Release 2 (9.0.3), or 10g (9.0.4) middle tiers in the same Oracle Application Server environment. However, you must keep in mind the following exceptions:

• Section 2.6.6, "Problems Logging In to OracleAS Portal"

• Section 2.6.13, "Middle Tiers Within an OracleAS Cluster Must Be the Same Version"

2.2.4 Running 10.1.2 Middle Tiers with a 9.0.4 Infrastructure

You can install 10g Release 2 (10.1.2) middle tiers against a 10g (9.0.4) OracleAS Infrastructure.

You can also upgrade your middle tiers to 10g Release 2 (10.1.2) before you upgrade your 10g (9.0.4) OracleAS Identity Management or OracleAS Metadata Repository.

However, you must consider the following issue when Running 10g Release 2 (10.1.2) Middle Tiers with a 10g (9.0.4) OracleAS Infrastructure:

• Section 2.6.6, "Problems Logging In to OracleAS Portal"

2.2.5 Running 10.1.2.0.2 Middle Tiers with a 10.1.2.0.0 Infrastructure

You can install 10g Release 2 (10.1.2.0.2) middle tiers against an existing 10g Release 2 (10.1.2.0.0) Infrastructure.

Specifically, during the 10g Release 2 (10.1.2.0.2) middle-tier installation procedure, specify the connection details for the existing 10g Release 2 (10.1.2.0.0) Identity Management and 10g Release 2 (10.1.2.0.0) OracleAS Metadata Repository.

2.3.1 Running 10.1.2 Identity Management with 9.0.2 and 9.0.3 Middle Tiers

You can install 10g Release 2 (10.1.2) OracleAS Identity Management services for use with Release 2 (9.0.2) and Release 2 (9.0.3) middle tiers.

You can also upgrade to OracleAS Identity Management to 10g Release 2 (10.1.2) before you upgrade your Release 2 (9.0.2) or Release 2 (9.0.3) middle tiers.

However, consider the following issues and workarounds when using this configuration:

• You must modify an entry in the 10g Release 2 (10.1.2) Oracle Internet Directory, as described in Section 2.6.1, "Configuring Oracle Internet Directory 10g Release 2 (10.1.2) for Use With Release 2 (9.0.2) Middle Tiers"

• If you are upgrading to 10g Release 2 (10.1.2) OracleAS Identity Management as part of a colocated Infrastructure, you should be aware of the limitations described in Section 2.6.12, "Release 2 (9.0.2) OracleAS Metadata Repository Cannot Operate Within an Oracle Database 10g Instance".

2.3.2 Running 10.1.2 Identity Management with a 9.0.2 Metadata Repository

You can run 10g Release 2 (10.1.2) OracleAS Identity Management with a Release 2 (9.0.2) OracleAS Metadata Repository; however, the Release 2 (9.0.2) OracleAS Metadata Repository schemas cannot operate within Oracle Database 10g (10.1.0.x).

For more information, see Section 2.6.12, "Release 2 (9.0.2) OracleAS Metadata Repository Cannot Operate Within an Oracle Database 10g Instance".

This restriction does not affect the following scenarios, which are supported:

• If the OracleAS Identity Management schemas are stored in a separate database from the OracleAS Metadata Repository, then the OracleAS Identity Management schemas can be installed in an Oracle 10g database, while the OracleAS Metadata Repository schemas remain in an Oracle9i database.

• If the 10g Release 2 (10.1.2) OracleAS Identity Management schemas and the Release 2 (9.0.2) OracleAS Metadata Repository schemas are stored in a common database, then the database must be Oracle9i Release 2 (9.2.0.6) and not a Oracle Database 10g.

Note the following additional facts about this scenario:

• You cannot install a new 10g Release 2 (10.1.2) OracleAS Identity Management installation against an existing Release 2 (9.0.2) or 10g (9.0.4) OracleAS Metadata Repository.

  For more information, see Section 2.6.14, "Cannot Install 10g Release 2 (10.1.2) OracleAS Identity Management Against a Release 2 (9.0.2) or 10g (9.0.4) OracleAS Metadata Repository".

• You can install a new Release 2 (9.0.2) OracleAS Metadata Repository and register the database that hosts the OracleAS Metadata Repository with a 10g Release 2 (10.1.2) OracleAS Identity Management.

2.3.3 Running 10.1.2 OracleAS Identity Management with a 9.0.4 Metadata Repository

You cannot install a new 10g Release 2 (10.1.2) OracleAS Identity Management against an existing 10g (9.0.4) OracleAS Metadata Repository.

This is because the 10g (9.0.4) OracleAS Metadata Repository does not contain the required 10g Release 2 (10.1.2) OracleAS Identity Management schemas. The 10g Release 2 (10.1.2) OracleAS Identity Management installation does not install the required schemas; instead, you must point the OracleAS Identity Management installation to a valid 10g Release 2 (10.1.2) OracleAS Metadata Repository.

However, when you upgrade OracleAS Identity Management to 10g Release 2 (10.1.2), the upgrade procedure automatically upgrades the OracleAS Identity Management schemas in the OracleAS Metadata Repository.

As a result, if you are running 10g Release 2 (10.1.2) OracleAS Identity Management against a 10g (9.0.4) OracleAS Metadata Repository, you can upgrade OracleAS Identity Management to 10g Release 2 (10.1.2) as long as the database that hosts the OracleAS Metadata Repository is a supported version.

Specifically, consider the following OracleAS Identity Management upgrade scenarios:

• If you are using a colocated Infrastructure, you can upgrade OracleAS Identity Management to 10g Release 2 (10.1.2) because in this scenario, the OracleAS Identity Management upgrade procedure automatically upgrades the database to a supported version and upgrades the OracleAS Identity Management schemas. The other component schemas, however, remain at 10g (9.0.4) until you run the Metadata Repository Upgrade Assistant.

  
  

  See Also: Section 7.4, "Task 4: Run the Metadata Repository Upgrade Assistant (MRUA)"

  
  

• If you are using a non-colocated Infrastructure, you can upgrade OracleAS Identity Management to 10g Release 2 (10.1.2), but you must first ensure that the database that hosts the OracleAS Metadata Repository is a supported version. This means you will likely have to upgrade the database first, either by using Oracle Universal Installer (if it is a seed database) or by manually upgrading the database if it is a OracleAS Metadata Repository Creation Assistant database.

  
  

  See Also: Section 7.1, "Task 1: Upgrade the Database That Hosts the OracleAS Metadata Repository"

  
  

2.4.1 Running a 10.1.2 Metadata Repository with 9.0.2, 9.0.3, and 9.0.4 Middle Tiers

You cannot run a 10g Release 2 (10.1.2) OracleAS Metadata Repository with previous versions of the Oracle Application Server middle tier. This is because the 10g (9.0.4) middle tiers are not compatible with the new 10g Release 2 (10.1.2) component schemas.

2.4.2 Running a 10.1.2 Metadata Repository with 9.0.2 Identity Management

You can run a 10g Release 2 (10.1.2) OracleAS Metadata Repository with Release 2 (9.0.2) OracleAS Identity Management; however, there are restrictions when registering the database that hosts the repository with Release 2 (9.0.2) OracleAS Identity Management.

For more information, see Section 2.6.11, "Cannot Register Oracle Database 10g Against Release 2 (9.0.2) Identity Management".

This restriction does not affect the following scenarios, which are supported:

• If you use OracleAS Metadata Repository Creation Assistant to install a new 10g Release 2 (10.1.2) OracleAS Metadata Repository in an Oracle9i Release 2 (9.2.0.6) database, then you can register the Oracle9i Release 2 (9.2.0.6) database against the Release 2 (9.0.2) OracleAS Identity Management.

• If you previously installed a 10g (9.0.4) OracleAS Metadata Repository in a Oracle9i (9.0.1.5) database, then you can upgrade the database to Oracle9i Release 2 (9.2.0.6) and run the Metadata Repository Upgrade Assistant (MRUA) to upgrade the OracleAS Metadata Repository schemas to 10g Release 2 (10.1.2).

  
  

  See Also: Chapter 7, "Upgrading the OracleAS Metadata Repository"

  
  

2.6.1 Configuring Oracle Internet Directory 10g Release 2 (10.1.2) for Use With Release 2 (9.0.2) Middle Tiers

Before you can use a Release 2 (9.0.2) middle tier with an upgraded 10g Release 2 (10.1.2) OracleAS Identity Management Oracle home, you must perform the following procedure:

1. Ensure that the following requirements are met:

   • The ORACLE_HOME environment variable points to the Infrastructure Oracle home directory used by 10g Release 2 (10.1.2) Single Sign-On.

   • The Oracle Internet Directory server is running.

   • The 10g Release 2 (10.1.2) infrastructure database and listener used by the Single Sign-On are running.

2. Run the imconfig.bat script on the computer where the 10g Release 2 (10.1.2) Single Sign-On is installed. Use the following command:

   imconfig.bat -10g -h ldaphost -p ldapPort -D ldapDN -w ldapPwd -oh oracleHome [-ssl ldap_ssl_port]
   
   

   Run the script either by changing to the directory on the CD-ROM containing the script and then running it, or by providing the full path to the script on the CD-ROM. The script requires JAR files that are not in the Oracle Application Server Oracle home.

   • Method 1: Change directory to the utilities directory on CD-ROM, then run the script. In this example, E:\ is the CD-ROM drive:

     cd E:\utilities\
     imconfig.bat parameters
     
     

   • Method 2: Run the script by providing full path to the utilities directory on the CD-ROM

     E:\utilities\imconfig.bat parameters
     
     

   Table 2-2 describes the parameters for the imconfig script.

   Table 2-2 Summary of the imconfig Script Parameters

   Parameter	Description
   ldaphost	The name of the computer running the Oracle Internet Directory. For example: dbmachine.mydomain.com.
   ldapPort	The port number on which the Oracle Internet Directory is listening. For example: 3060.
   ldapDN	The Distinguished name (DN) of the Oracle Internet Directory user. Example: "cn=orcladmin"
   ldapPWD	The password for the Oracle Internet Directory user.
   oracleHome	The Oracle home directory for the Infrastructure database used by Single Sign-On.
   ldap_ssl_port	If a secure port can be used to access the Oracle Internet Directory, specify the -ssl parameter and specify the Secure Sockets Layer (SSL) port. For example: -ssl 453

   
   

3. Perform the following in the OracleAS Single Sign-On Oracle home:

   1. Locate the following configuration file in the OracleAS Single Sign-On Oracle home:

      ORACLE_HOME\sso\conf\sso_apache.conf
      
      

   2. Use a text editor to open the sso_apache.conf file and locate the following entry in the file:

      <Location "/pls/orasso/*[Ss][Ss][Oo][Pp][Ii][Nn][Gg]">
         Order deny,allow
         Deny from all
      #  Allow from <your_domain_name>
      </Location>
      
      

   3. Remove the comment character (#) and replace the string your_domain_name with the domain name used by your Release 2 (9.0.2) middle tier hosts.

      For example:

      <Location "/pls/orasso/*[Ss][Ss][Oo][Pp][Ii][Nn][Gg]">
         Order deny,allow
         Deny from all
         Allow from acme.com
      </Location>
      
      

   4. Save and close the sso_apache.conf file.

2.6.2 Assigning the Enterprise Manager Web Site Port When Installing Release 2 (9.0.2) or Release 2 (9.0.3) on a 10g (9.0.4) or 10g Release 2 (10.1.2) Host

When you install a Release 2 (9.0.2) or Release 2 (9.0.3) Oracle Application Server instance, the installer assigns port 1810 to the Oracle Enterprise Manager Web Site, regardless of whether or not the port is already in use.

If the computer where you plan to install the Release 2 (9.0.2) or Release 2 (9.0.3) already has a 10g (9.0.4) or 10g Release 2 (10.1.2) instance, then the Oracle Enterprise Manager Application Server Control for the 10g (9.0.4) or 10g Release 2 (10.1.2) instance might already be using port 1810.

To prevent a port conflict, you can use the staticports.ini file to specify port numbers for each 10g Release 2 (10.1.2) component. If you plan to install Release 2 (9.0.2) or Release 2 (9.0.3) middle tiers, you can use this feature to specify a port other than 1810 for the 10g Release 2 (10.1.2) Application Server Control Console.

If you have already installed 10g Release 2 (10.1.2), you can change the Application Server Control Console ports before you install Release 2 (9.0.2) or Release 2 (9.0.3) on the same host.

2.6.3 Problems Accessing 10g Release 2 (10.1.2) Instances from the Release 2 (9.0.2) or Release 2 (9.0.3) Farm Page

Although the Farm page in the Release 2 (9.0.2) and Release 2 (9.0.3) Enterprise Manager Web site contains links to any 10g (9.0.4) or 10g Release 2 (10.1.2) instances on the host, the links are not valid. You cannot use Oracle Enterprise Manager from Release 2 (9.0.2) or Release 2 (9.0.3) to manage 10g (9.0.4) or 10g Release 2 (10.1.2) instances.

To manage a 10g (9.0.4) or 10g Release 2 (10.1.2) instance, use the Oracle Enterprise Manager Application Server Control that was installed with the instance.

2.6.4 Running the dcmctl getState Command from a 10g Release 2 (10.1.2) Instance

If you run the dcmctl getState command from a 10g (9.0.4) or 10g Release 2 (10.1.2) instance to get information on a Release 2 (9.0.2) or Release 2 (9.0.3) instance, you might get an ADMN-604104 error:

prompt> dcmctl getState -i name_of_902_or_903_instance
ADMN-604104 Unable to connect to the OPMN process to obtain process status table

To avoid this error, use the dcmctl command from the Release 2 (9.0.2) or Release 2 (9.0.3) Oracle home.

2.6.5 Updating an Entry in the Release 2 (9.0.2) Oracle Internet Directory Before Installing the 10g Release 2 (10.1.2) Middle Tier

Before installing a 10g Release 2 (10.1.2) middle tier against a Release 2 (9.0.2) OracleAS Infrastructure, you must update an entry in the Release 2 (9.0.2) Oracle Internet Directory.

To update the entry, you use the imconfig.bat script. This script is located in the utilities directory of the OracleAS Metadata Repository Upgrade Assistant and Utilities CD–ROM.

The following instructions describe how to use the script:

1. Ensure that the following requirements are met:

   • The ORACLE_HOME environment variable points to the Release 2 (9.0.2) Infrastructure home directory used by Oracle9iAS Single Sign-On.

   • The Oracle Internet Directory server is running.

   • The Release 2 (9.0.2) Infrastructure database and listener used by Oracle9iAS Single Sign-On are running.

2. Run the imconfig.bat script on the computer where the 9.0.2 Oracle9iAS Single Sign-On is installed. Use the following command:

   imconfig.bat -902 -h ldaphost -p ldapPort -D ldapDN -w ldapPwd -oh oracleHome [-ssl ldap_ssl_port]
   
   

   Run the script either by changing to the directory on the CD-ROM containing the script and then running it, or by providing the full path to the script on the CD-ROM. The script requires JAR files that are not in the Oracle Application Server Oracle home.

   • Method 1: Change directory to the utilities directory on CD-ROM, then run the script. In this example, E:\ is the CD-ROM drive:

     cd E:\utilities\
     imconfig.bat parameters
     
     

   • Method 2: Run the script by providing full path to the utilities directory on the CD-ROM

     E:\utilities\imconfig.bat parameters
     
     

   Refer to Table 2-2 for a description of the imconfig script parameters.

2.6.6 Problems Logging In to OracleAS Portal

If you install a 10g Release 2 (10.1.2) OracleAS Portal middle tier against a Release 2 (9.0.2) or 10g (9.0.4) OracleAS Metadata Repository, you must run the OracleAS Upgrade Assistant from the 10g Release 2 (10.1.2) middle tier before you can access the OracleAS Portal using the 10g Release 2 (10.1.2) middle tier URL.

If you do not run the Upgrade Assistant, you can only access Portal using the 9.0.x middle tier URL.

An exception to this case is if no 9.0.x middle tier was ever installed against the Release 2 (9.0.2) or 10g (9.0.4) OracleAS Metadata Repository. In this case, since the 10g Release 2 (10.1.2) middle tier is the first middle tier to be installed against the OracleAS Metadata Repository, you can access OracleAS Portal without running the Upgrade Assistant.

2.6.7 Oracle Application Server Forms Services Gives Error FRM-92102

This error occurs in configurations that meet ALL these conditions:

• You have a 10g Release 2 (10.1.2.0.2) Business Intelligence and Forms middle tier, including the Oracle Application Server Forms Services component and a Release 2 (9.0.2) infrastructure running on the same computer.

• You use the Microsoft Internet Explorer Web browser to access a form.

• The form needs to redirect to Oracle Delegated Administration Services to create a resource dynamically (because you entered a resource that does not yet exist).

If you meet all these conditions, the FRM-92102 error occurs when you access a form. The Forms Services application is unable to create a session after Oracle Delegated Administration Services created the resource.

If you access the same form again from a different browser, the resource now exists (the Oracle Delegated Administration Services component does not have to create it dynamically again), and you can now access the form successfully.

To avoid this error, you can install the instances on different computers, use Netscape Navigator instead of Microsoft Internet Explorer to access the form, or ensure that the resources already exist.

2.6.8 Oracle Delegated Administration Services: "Resource Access Information" Section Shows Incorrect User Resources

When you are using a 10g Release 2 (10.1.2) middle tier and a Release 2 (9.0.2) Infrastructure, you might see incorrect user resources listed in the Resource Access Information section in the Edit User page of Oracle Delegated Administration Services (URL: http://host:port/oiddas).

If you view the page for different users, the page might still show the resources for the first user you viewed.

To ensure the page is displaying the correct list of resources for a user, make sure that the user is the first user you view after logging into Oracle Delegated Administration Services. If you are unsure, log out of Oracle Delegated Administration Services and log in again. Then immediately view the user whose properties you want to edit (without viewing other users).

2.6.9 UDDI: Ping the Servlet Endpoint Returns "500 Internal Server Error"

When running 10g Release 2 (10.1.2) UDDI against a Release 2 (9.0.2) OracleAS Metadata Repository, you will get a "500 Internal Server Error" if you click the servlet link (inquiry, publishing, or replication endpoint) on the UDDI page:

http://host:port/uddi

OR

http://host:port/uddirepl

In addition, you will receive an error message stating that "something is wrong with JMS or MDB" if you click the JMS endpoint link on the following page:

http://host:port/uddirepl

This is because running UDDI from the 10g Release 2 (10.1.2) middle tier requires a 10g Release 2 (10.1.2) OracleAS Metadata Repository.

2.6.10 Using OracleAS Wireless 10g Release 2 (10.1.2) with a Release 2 (9.0.2) OracleAS Metadata Repository

If you are using Oracle Application Server Wireless, you must perform some prerequisite tasks before you can use your OracleAS Wireless components against the Release 2 (9.0.2) OracleAS Metadata Repository.

2.6.11 Cannot Register Oracle Database 10g Against Release 2 (9.0.2) Identity Management

You cannot register Oracle Database 10g (10.1.0.x) instances against Release 2 (9.0.2) OracleAS Identity Management.

This restriction affects Oracle Application Server users in the following scenario. When you use Oracle Universal Installer to install a new 10g Release 2 (10.1.2) OracleAS Metadata Repository, you are prompted to register the OracleAS Metadata Repository database with Oracle Internet Directory. When you are prompted to register the database, you cannot specify a Release 2 (9.0.2) Oracle Internet Directory that is part of a Release 2 (9.0.2) OracleAS Identity Management Oracle home.

To avoid this problem, upgrade the Release 2 (9.0.2) OracleAS Identity Management to 10g Release 2 (10.1.2) before attempting to register the 10g Release 2 (10.1.2) OracleAS Metadata Repository database with Oracle Internet Directory.

2.6.12 Release 2 (9.0.2) OracleAS Metadata Repository Cannot Operate Within an Oracle Database 10g Instance

The schemas in a Release 2 (9.0.2) OracleAS Metadata Repository cannot operate within an Oracle Database 10g (10.1.0.x) database.

This restriction affects Oracle Application Server users in the following scenario.

By default, the Release 2 (9.0.2) OracleAS Identity Management schemas and OracleAS Metadata Repository component schemas share a database in a common Oracle home. When you run Oracle Universal Installer to upgrade Release 2 (9.0.2) OracleAS Identity Management to 10g Release 2 (10.1.2), the installer not only upgrades OracleAS Identity Management to 10g Release 2 (10.1.2), but it also upgrades the colocated OracleAS Metadata Repository database to Oracle Database 10g (10.1.0.3.1). Because the Release 2 (9.0.2) OracleAS Metadata Repository is not compatible with the Oracle Database 10g (10.1.0.3.1) database, the resulting configuration is unsupported.

To work around this problem, run the Metadata Repository Upgrade Assistant (MRUA) immediately after the database upgrade. MRUA upgrades the OracleAS Metadata Repository schemas to 10g Release 2 (10.1.2). The upgraded 10g Release 2 (10.1.2) component schemas are compatible with Oracle Database 10g.

2.6.13 Middle Tiers Within an OracleAS Cluster Must Be the Same Version

If you create an OracleAS Cluster, the middle tiers that you add to the cluster must be the same version. For example, you cannot add a 10g Release 2 (10.1.2) middle tier and a Release 2 (9.0.2) middle tier to the same cluster.

If you plan to upgrade the middle tiers that are part of an OracleAS Cluster, you must follow the instructions described in Section 4.10.1, "Special Instructions When Upgrading an Oracle Application Server Cluster".

2.6.14 Cannot Install 10g Release 2 (10.1.2) OracleAS Identity Management Against a Release 2 (9.0.2) or 10g (9.0.4) OracleAS Metadata Repository

When you install 10g Release 2 (10.1.2) OracleAS Identity Management, you must identify a 10g Release 2 (10.1.2) OracleAS Metadata Repository database. This is because the 10g Release 2 (10.1.2) OracleAS Identity Management components require the 10g Release 2 (10.1.2) OracleAS Identity Management schemas.

As a result of this requirement, you cannot specify a Release 2 (9.0.2) or 10g (9.0.4) OracleAS Metadata Repository while installing the 10g Release 2 (10.1.2) OracleAS Identity Management.

2.6.15 10g Release 2 (10.1.2) OracleAS Identity Management General Compatibility Requirements

The following sections provide information about the requirements you must consider when running 10g Release 2 (10.1.2) OracleAS Identity Management in an environment with multiple versions of Oracle Application Server:

• OracleAS Identity Management Components Must Be the Same Version as Their Required Schemas

• OracleAS Identity Management Components Must Use an Oracle Internet Directory Of the Same Version