Migration - Oracle 11i to Linux Platform

Linux platform migration provides a way to quickly and easily move an existing Oracle Applications middle tier System from any platform to Linux, allowing you to utilize fast, low-cost hardware for your Applications middle tier. The migration utility retains your exact Applications patch level, so that no APPL_TOP/Database synchronization is necessary. It also allows you to retain many customizations.

This Blog applies to the Application Tier Only. The Database Tier is not covered on this Note. Please refer to Document 230627.1 in OracleMetalink for instructions on the Database Migration.

This document describes the process of migrating an Oracle Applications Release 11i System. The most current version of this Note is Document 238276.1 on OracleMetaLink.

For additional information on these migration steps, their expected behavior and troubleshooting procedures, please refer to Document 567703.1 in OracleMetalink.

Attention: Windows NT/2000 users. This document typically uses UNIX syntax when specifying directories; Substitute the appropriate Windows syntax.

• Section 1: Prerequisites
  Must be completed prior to using the migration utility.
• Section 2: Migrate platforms with Oracle Applications 11i
  Tasks to migrate an Applications System to a new platform.
• Section 3: Finishing Tasks
  Tasks that need to be performed after the migration.

Conventions

	Convention	Meaning
	Middle tier	The application tier comprising the Admin, Concurrent Processing, Forms and Web servers.
	Source System	Applications System being migrated.
	Target System	Applications System being created as a copy of the Source.
	APPLMGR	User who owns the applications file System (APPL_TOP and middle tier technology stack)
	ORACLE	User who owns the database file system (RDBMS ORACLE_HOME and database files).
	Monospace Text	Represents command line text. Type this command exactly as shown.
	( )	Text enclosed in angle brackets represents a variable. Substitute a value for the variable text. Do not type the angle brackets.

---

Section 1: Prerequisites

Prepare the Source System before migrating to a new platform. If the System is installed using multi nodes, the following prerequisite steps must be performed on all nodes.

1. Verify OS requirements on Target System
   Before migrating to the new platform, ensure the Target System meets all the requirements for Oracle Applications Release 11i stated on the Oracle Applications Release Notes and on the Oracle Applications Update Notes for the Target Platform.

2. Verify the software versions on the Target System
   In addition to the Oracle Applications OS requirements the following software component versions must exist on the Source and Target nodes.

   Software	Minimum Version	Details
   Perl	5.005	You can use the Perl shipped with iAS1022 and RDBMS 9i or download it from Perl.com. Perl must be in the PATH.
   JDK	1.3.1 1.4.2	The minimum JDK version is 1.3. If migrating to Red Hat Enterprise Linux 3.0 or 4.0 then the minimium JDK version is 1.4. The Source System must be at the correct JDK version before migrating platform. For Oracle Applications 11i JDK upgrade, refer to Upgrading 11i to JDK 1.3 (document 130091.1) or Upgrading 11i to JDK 1.4 (document 246105.1)

3. Verify the database version
   If your database version is lower than Oracle8i Enterprise Edition Release 8.1.7.4, upgrade it to the latest certified patchset of Oracle8i Release 8.1.7 or any higher certified version.

   Note: If the Database is not on a certified combination with Oracle Applications, you must upgrade the Database to the latest certified version available.

4. Apply the latest AD Patch
   Apply patch 5161680 (AD.I.5) or higher. Please refer to OracleMetaLink to obtain the latest MiniPack available for AD. The AD patch level can be found in the report generated by the following command:
   sqlplus (AppsUsr)/(AppsPwd) @$AD_TOP/sql/adutconf.sql

5. Implement AutoConfig on the Application Tier
   If the Source Applications System was created with Rapid Install version 11.5.8 or earlier you must migrate the System to Autoconfig. Follow the instructions on Migrating to AutoConfig on the Application Tier in document 165195.1 in OracleMetaLink.
   This step can be ignored if Autoconfig have already been implemented.

6. Apply the latest AutoConfig Template patch
   Update the Oracle Applications file system with the latest AutoConfig template files by applying the TXK AutoConfig Template rollup patch to all application tier server nodes. Refer to Document 165195.1 in OracleMetaLink for details of the latest Autoconfig Template rollup patch available. If you already applied the latest patch available, you can skip this step.

7. Apply the latest Rapid Clone patch
   Update the Oracle Applications file system with the latest Patches required by Rapid Clone. Refer to Document 230672.1 in OracleMetaLink for details of the latest required patches.

8. Maintain snapshot information
   Run adadmin to maintain snapshot information on all nodes. Refer to the Oracle Applications Maintenance Utilities manual for more details.

---

Section 2: Migrate Platforms with Oracle Applications 11i

1. Generate and upload the manifest of customer-specific files
   
   1. Log in to your Source System primary administration node as the APPLMGR user and source the APPL_TOP environment file. Execute the following command to generate the customer-specific file manifest. This step should take about a minute:
      perl $AD_TOP/bin/adgenpsf.pl
      

   2. Go to http://updates.oracle.com/PlatformMigration (use your OracleMetaLink username and password) and follow the instructions on the screen to upload the manifest file previously generated:
      $APPL_TOP/admin/$TWO_TASK/out/adgenpsf.txt

2. Create the Target System APPL_TOP
   Copy the middle tier file system from the Source Applications System to the Target Node by executing the following steps in the order listed. Ensure that the application tier files copied to the Target System are owned by the Target APPLMGR user.
   

   Note: The Source System can remain up and running until the last step of the migration.

   1. Copy the APPL_TOP file system
      Log on to the Source System application tier node as the APPLMGR user and copy the following application tier directories from the Source System to the Target System
      • (APPL_TOP)
      • (OA_HTML)
      • (OA_JAVA)
      • (COMMON_TOP)/util
      • (COMMON_TOP)/_pages (when that directory exists)

      Attention: Copy only the directories listed, not the full COMMON_TOP.

      Warning: In order to preserve the Concurrent Manager log files and output files you need to consider the configuration of the variables $APPLCSF/$APPLOG and $APPLCSF/APPLOUT. If these variables are pointing to locations inside the COMMON_TOP directory structure (i.e. $COMMON_TOP/admin/out/$CONTEXT_NAME and $COMMON_TOP/admin/log/$CONTEXT_NAME you will need to copy these files into similar directory structures on the Target System.

   2. Copy the security file for JInitiator
      
      • If you wish to preserve the Source System digital signature on the migrated System, copy the identitydb.obj file from the Source System to the Target System. This file is located in the APPLMGR user's home directory on UNIX or the root directory of the %SystemDrive% on Windows.
        
      • If you want the migrated System to have a new digital signature, remove the following file from the Target System:
        rm (APPL_TOP)/admin/appltop.cer
        

3. Clone the AutoConfig XML context file on the Target System
   The Clone Context tool will ask for all the new mount points on the Target migration node. Log on to the Target System as the APPLMGR user and run the following commands:
   
   • cd (AD_TOP)/bin
     
   • perl adclonectx.pl migrate java=(JDK HOME) contextfile=(Source System contextfile)
     

     where:
     (JDK HOME)	complete path where the JDK is installed.
     (Source System contextfile)	full path to the Source System Applications XML context file located in /admin on the Target System.

   Respond to the prompts. This will create the following Target System context file:
   (APPL_TOP)/admin/(SID)_(hostname).xml
   

   Note: See document 216664.1 on OracleMetaLink for more information on port pool.

4. Install the Middle Tier Technology Stack
   Run the Rapid Install Wizard with the -techstack option to install the iAS technology stack. Use the Target System context file created in the previous step.

   cd [Stage11i]/startCD/Disk1/rapidwiz
./rapidwiz -techstack
   

   Follow the instructions in the "Installation Tasks" section of Installing Oracle9i Application Server 1.0.2.2.2 with Oracle Applications 11i" (document 146468.1).

   Note: Use the latest startCD available in OracleMetalink. Refer to the "Current Version of Rapid Install" section in the Oracle Applications Release Notes for details on the latest startCD Patch. More details on how to execute rapidwiz can be found on the Oracle Applications 11i Installation Manual.

   Attention: Review the log files (setup_stubs..log) under the iAS ORACLE_HOME to ensure that there are no errors.

5. Apply the Oracle interoperability patches for Red Hat Enterprise Linux
   If the Application System is 11.5.9 or lower, and on Red Hat Enterprise Linux 3.0 or 4.0, then apply the following Oracle server interopability patches.

   Patches	Description
   3830807	Oracle 8.0.6.3 Interop patch
   3170128	Oracle 8.0.6 Interop patch for Discoverer 4i
   3846086	8.1.7.4 Interop patch for iAS ORACLE_HOME

6. Run AutoConfig setup phase on the Target System
   Execute the INSTE8_SETUP phase of AutoConfig with the new context file. This will create the environment files required for the AutoPatch session:
   
   • cd (AD_TOP)/bin

   • ./adconfig.sh run=INSTE8_SETUP contextfile=(Target System ctxfile)

     Note: This command does not require the environment to be sourced.

7. Download and apply the customer-specific update with AutoPatch
   Within 30 minutes from the time you uploaded the manifest file at step 1.b you will receive a notification email saying that your customer specific update patch is ready. Follow the instructions in the email to download it from Oracle MetaLink. The patch should be applied on all Target System application nodes. Source the APPL_TOP environment file and follow the instructions in the README to apply the patch. AutoPatch will automatically relink the executables.

8. Apply patch 3077161 (only if migrating from Windows):
   Only if you are migrating from Windows, download and apply the Linux patch 3077161 containing the Unix-specific files that don't exist in a Windows APPL_TOP.

9. Review the technology stack patch level
   Identify any patches previously applied to your Source System technology stack which are not included in the (document 146468.1). Apply these patches to your Target System technology stack.

   Note: For information and instructions on applying the latest Developer 6i patchset, see Note 125767.1

10. Download and apply the techstack interop patch
    Apply patch 4139957 to the Target Oracle Applications file system.

11. Regenerate the file system objects
    Source the APPL_TOP environment file and perform the following tasks to regenerate the platform dependent files on the Target System:
    1. If migrating the Forms node, run the following script:
       $AD_TOP/patch/115/bin/adgensgn.sh Apps User/Apps Password
    2. Run adadmin to generate messages, forms, reports, graphics and jar files.

12. Run AutoConfig to complete the Target System configuration
    $AD_TOP/bin/adconfig.sh contextfile=Target System context file
    

    Note: The database will be updated to reflect the new Target System profile. Make sure all users are off the system and shut down the Source System application tier server processes. After this step, the Source System middle tier will no longer be available.

---

Section 3: Finishing Tasks

This section lists tasks that may be necessary depending on your implementation and the intended use of the migrated System.

1. Update 3rd party extensions
   If your Applications System is implementing any products which use Ilog, Roguewave, or Quantum, you will need to update the Target System with the objects for the 3rd party extensions and relink any dependent products.

   Software	Details
   ILOG	Apply patch 2837811 and relink dependent executables.
   ROGUEWAVE	Apply patch 3006092 and relink dependent executables.
   QUANTUM	Follow instructions in document 224273.1 on OracleMetaLink

2. Review and update your Target System application tier settings and customizations
   1. Recompile any custom code (forms, C) in the Target System APPL_TOP.
      
   2. If you were using UTF8 charset, Discoverer 4i, SSO or Portal 3i on the Source System, refer to the corresponding documentation to complete the migration:

3. Update printer settings
   If the newly migrated System needs to utilize different printers, update the Target System with the new printer settings now.

4. Update Workflow configuration settings
   Migrating an Oracle Applications instance will not update the host and instance specific information used by Oracle Workflow. Review the following tables and columns to verify there is no instance-specific data in the Workflow configuration on the Target System.

   Table Name	Column Name	Column Value Details
   WF_NOTIFICATION_ATTRIBUTES	TEXT_VALUE	Value starts with http://old web host : Update to new web host
   WF_ITEM_ATTRIBUTE_VALUES	TEXT_VALUE	Value starts with "http://old web hos : Update to new web host
   WF_SYSTEMS	GUID	Create a new System defined as the new global database name using the Workflow Administrator Web Applications responsibility.
   WF_SYSTEMS	NAME	Value needs to be replaced with the database global name
   WF_AGENTS	ADDRESS	Update database link with the new database global name.
   FND_FORM_FUNCTIONS	WEB_HOST_NAME	Update with the new web host name
   FND_FORM_FUNCTIONS	WEB_AGENT_NAME	Update to point at the new PLSQL listener name
   FND_CONCURRENT_REQUESTS	LOGFILE_NAME	Update with the correct path to the logfile directory
   FND_CONCURRENT_REQUESTS	OUTFILE_NAME	Update with the new directory path on the Target System

5. Review your CLASSPATH setting
   Log in to the Target APPL_TOP environment (source the environment file) and perform the following tasks to consolidate your CLASSPATH:
   1. Verify the AD classpath:
      • Run $ADJVAPRG -version
      • If the result shows a java version of 1.3.1 or higher, use Context Editor to update the variable s_adovar_classpath in the context file: replace appsborg.zip by appsborg2.zip in the classpath string.

   2. Verify the AF classpath:
      • Run $AFJVAPRG -version
      • If the result shows a java version of 1.3.1 or higher, use Context Editor to update the variable s_adovar_afclasspath in the context file: replace appsborg.zip by appsborg2.zip in the classpath string.

   3. Run AutoConfig as described in document 165195.1 on OracleMetalink.

6. Start all services on the Target System
   Start all services by running the script:
   adstrtal.sh AppsUser/AppsPwd
   located in COMMON_TOP/admin/scripts/ContextName/

Cheers!!!!