Steps to be followed for Migrating Oracle Applications E-Business Suite (11.5.

9 with 9i DB) from IBM AIX to Linux

Software Requirements ********************** 1. 2. 3. 4. 5. Oracle Database 9i Installation CD Oracle Applications E-Business Suite 11.5.9 for Linux CD Packages supports for Linux. JDK 1.4,Unzip,Perl Other patches recommended by Oracle Support.

Database Migration Steps ********************** 1. Source Database Instance Take a backup of Source Database and Oracle EBiz File Systems Apply Latest AD Minipack in Source Application system Apply the Applications consolidated export/import utility patch[4872830] Apply latest Applications database preparation scripts patch Identify the GLOBAL_NAME [ select * from global_name].Note this value which will be used later on target database. Create the export parameter file As a part of Export/Import Patch, auexpimp.dat will be copied in $AU_TOP/patch/115/import. Copy this file from Application system to Database node . Modify the parameters as per your requirements The customizable parameters are: Parameter userid buffer file filesize log Description SYS schema and password size of the data buffer export dump file name(s) export dump file size log file name Template Value "sys/change_on_install as sysdba" 1MB dmpfil[1-4] 500MB expapps.log

Comment out or remove the toid_novalidate parameter. It is used only for the import process. Do not change the other parameters. Specify the no of dumpfiles and filesize as per your source system space availability. Generate target database instance creation script The target database instance must be created with the same tablespace and file structure as the source database instance. Patch 4872830 provides the adclondb.sql script which generates the following scripts: adcrdb.sql which you use to create the target database instance with the appropriate tablespace and file structure adpostcrdb.sql which you use to convert tablespaces to locally managed. The adpostcrdb.sql script converts all tablespaces except for SYSTEM to locally managed tablespaces, if they are not already so. On the source administration server node, connect to the database as SYSTEM and run the $AD_TOP/patch/115/sql/adclondb.sql script. It creates adcrdb.sql in the current directory. $ sqlplus system/[system password] @$AD_TOP/patch/115/sql/adclondb.sql 9 Record Advanced Queue settings Advanced Queue settings are not propagated in the target database instance during the export/import process. Therefore, you must record them beforehand and enable them in the target database instance afterwards. Patch 4872830 contains auque1.sql, which generates a script called auque2.sql. You can use auque2.sql to enable the settings in the target database instance. Copy the auque1.sql script from the $AU_TOP/patch/115/sql directory on the source administration server node to the source database server node. It does not matter which directory you use. Then, on the source database server node, as the owner of the source database server file system and database instance, use SQL*Plus to connect to the source database as sysdba and run the auque1.sql script. It generates auque2.sql in the current directory. $ sqlplus /nolog SQL> connect / as sysdba; SQL> @auque1.sql Record Oracle ConText and OLAP default tablespace On the source database server node, use SQL*Plus to connect to the source database as sysdba and run the following query: $ sqlplus /nolog

SQL> connect / as sysdba; SQL> select username, default_tablespace from dba_users where username='CTXSYS' or username='OLAPSYS'; Note the default tablespace returned by the query. You will need it in the next section. Shut down Applications server processes Shut down all Applications server processes except the database and the Net8 listener for the database. Users cannot use the Applications until the import is completed. Export the Applications database instance Start an export session on the source database server node using the customized export parameter file. Use the following command: $ exp parfile=[export parameter file name] Typically, export runs for several hours. It is a good idea to run it in a manner that will allows it to continue if the client session is accidentally terminated. On UNIX or Linux, run it in the background or with the nohup utility,redirecting standard output and standard error messages to a log file. Its Better to export directly to the target database node using TNSNAMES as it will minimize your time.

Target Database Instance.

1. Create Target 9i Database Instance Install 9i DB home and upgrade to the version as same as Source DB. Modify Init.ora file parameter with the required parameters. Copy the adcrdb.sql script, generated in Section 1, from the source administration server node to the target database server node. Then update the script on the target database server node with any necessary changes to the directory structures for the log file(s), data file(s), or tablespaces, reflecting the layout of the target database server node Make sure that the environment of your session on the target database server node is set up properly for the target database instance, especially the ORACLE_HOME and ORACLE_SID environment settings. (ORACLE_SID must be set to the same value as the db_name parameter in the init[SID].ora file.) Then, use the following commands to run adcrdb.sql and create the target database instance:

$ sqlplus /nolog SQL> connect / as sysdba; SQL> spool adcrdb.log;

For UNIX or Linux: SQL> startup nomount; SQL> @adcrdb.sql SQL> exit; If you have removed the parameters undo_tablespace, undo_management, and undo_suppress_errors in the previous step, add these parameters to the initialization parameter file and restart the database instance.

2. Copy database preparation scripts to target Oracle home The database preparation scripts that you applied to the source administration server node in Section 1 contain four scripts that are needed on the target database server node. Copy the following files from the $APPL_TOP/admin directory of the source administration application server node to the Oracle9i $ORACLE_HOME/appsutil/admin directory of the target database server node: addb920.sql, adsy920.sql, adjv920.sql, and admsc920.sql (UNIX or Linux) As you run each of the next four steps, note the following: The remarks section at the beginning of each script contains additional information. Each script creates a log file in the current directory. 3. Set up the SYS schema The addb920.sql or addb920_nt.sql script sets up the SYS schema for use with the Applications. On the target database server node, connect to the target database instance as SYSTEM and run $ORACLE_HOME/appsutil/admin/addb920.sql $ sqlplus system/[system password] \ @$ORACLE_HOME/appsutil/admin/addb920.sql 4. Set up the SYSTEM schema The adsy920.sql or adsy920_nt.sql script sets up the SYSTEM schema for use with the Applications. On the target database server node, to connect to the target database instance as SYSTEM and run $ORACLE_HOME/appsutil/admin/adsy920.sql $ sqlplus system/[system password] \ @$ORACLE_HOME/appsutil/admin/adsy920.sql 5. Install Java Virtual Machine The adjv920.sql or adjv920_nt.sql script installs the Java Virtual Machine (JVM) in the database. This script can be run only once in a given database instance, because the scripts that it calls are not rerunnable. On the target database server node,

connect to the target database instance as SYSTEM and run $ORACLE_HOME/appsutil/admin/adjv920.sql. $ sqlplus system/[system password] \ @$ORACLE_HOME/appsutil/admin/adjv920.sql 6. Install other required components The admsc920.sql or admsc920_nt.sql script installs the following required components in the database: ORD, Spatial, OLAP, interMedia, and ConText. On the target database server node, use connect to the target database instance as SYSTEM and run $ORACLE_HOME/appsutil/admin/admsc920.sql $ sqlplus system/[system password] \ @$ORACLE_HOME/appsutil/admin/admsc920.sql FALSE CTXSYS TEMP OLAPSYS \ /u01/oracle/920/9204/ctx/lib/libctxx9.so 7. Run adpostcrdb.sql script Copy the adpostcrdb.sql script, generated in Section 1, from the source administration server node to the target database server node. connect to the database instance as SYSTEM and run the following command. $ sqlplus system/[system password] @adpostcrdb.sql 8. Update the GLOBAL_NAME Update the GLOBAL_NAME of the target database instance to that of the source database instance that you recorded in Section 1. On the target database server node, use SQL*Plus to connect to the target database instance as sysdba and run the following command: SQL> alter database rename global_name to [source db global name] ; You can set the GLOBAL_NAME to any value after the import. 9. Back up the target database instance The target database instance is now prepared for an import of the Applications data. You should perform a backup before starting the import.

3 . Import Database Instance

Create the import parameter file

Copy the export parameter file you created in Section 1 from the source database server node to the target database server node, renaming it if necessary. Updating the new file with the following changes converts it to an import parameter file: Remove the "compress=y" parameter Add the following parameters: ignore=y analyze=n commit=y Remove any unused export dump file names from the "file" parameter Change the name of the log file Uncomment or add the toid_novalidate parameter Save the changed file. Import the Applications database instance Start the import session on the target database server node using the customized import parameter file. Use the following command: $ imp parfile=[import parameter file name]

4. Perform Post Import Steps on Target Database Instance Reset Advanced Queues
Copy the auque2.sql script that was generated in Section 1 from the $ORACLE_HOME/appsutil/admin directory of the source database server node to the same directory on the target database server node. Connect to the target database as sysdba and run the $ORACLE_HOME/appsutil/admin/auque2.sql script to enable the Advanced Queue settings that were lost during the export/import process. The script creates a log file in the current directory. $ sqlplus /nolog SQL> connect / as sysdba; SQL> @$ORACLE_HOME/appsutil/admin/auque2.sql Compile Invalid Objects

Once Database Migration is done, Take a backup before proceeding to Application Migration.

APPLICATION MIGRATION STEPS **********************************

Prepratory Steps in Source Application System ---------------------------------------------------------------1. Prepare the source Application Instance by applying the latest AD,Autoconfig ,Rapid Clone Patches. 2. Prepare the source Application Instance by upgrading your form to latest version. 3. Maintain Snapshot information through adadmin. Migration of Application System **************************** Generate and upload the manifest of customer-specific files 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 Go to https://updates.oracle.com/PlatformMigration (use your OracleMetaLink username and password) and follow the instructions on the screen to upload the manifest file [APPL_TOP]/admin/[TWO_TASK]/out/adgenpsf.txt 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. 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/clone COMMON_TOP/util COMMON_TOP/_pages (when that directory exists) Attention: Copy only the directories listed, not the full COMMON_TOP. 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 cd <COMMON_TOP>/clone/bin perl adclonectx.pl migrate java=[JDK HOME] c ontextfile=[SOURCE SYSTEM CONTEXT FILE] where: JDK HOME complete path where the JDK is installed. SOURCE SYSTEM CONTEXT FILE Full Path to the Source System Applications XML context file located in APPL_TOP/admin on the Target System. Respond to the prompts. This will create the following Target System context file: $APPL_TOP/admin/[SID]_[hostname].xml 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 Apply the Oracle interoperability patches for Red Hat Enterprise Linux Apply the interop patches for your target application system 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 CONTEXT FILE]. 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.

Finishing Tasks ************** 1. Review and update your Target System application tier settings and 2. 3. 4. 5.
customizations Recompile any custom code forms. Run adadmin and regenerate forms,menus,messages,reports. Update printer settings and Workflow settings too. Start all services on the Target System