As agreed the last part of the Migration from Solaris to AIX

Porting the Application tier

Prerequisities :

1. Verfiy OS requirements

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

Perl 5.005
JDK 1.4.2

To check
perl –v
java –version

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

4. Apply the latest AD Patch

Apply patch 4712852 (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 / @$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.
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.

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

a. 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

b. Go to http://updates.oracle.com/PlatformMigrationhttp://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. Please note that before you go ahead with this step your Source application tiers should point to target database

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

a. 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



 /util
 /_pages (when that directory exists)

Attention: Copy only the directories listed, not the full COMMON_TOP
Perform above-mentioned steps on both the application tier nodes.

a. 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 /admin/appltop.cer

1. 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:

o cd /bin

Note: Provide the OS java location.
where:
complete path where the JDK is installed.
full path to the Source System Applications XML context file located in /admin on the Target System.

2. Respond to the prompts.

This will create the following Target System context file:

/admin/_.xml

Run it on both the application tier nodes.

applmgr@server1$ perl adclonectx.pl migrate java=/usr/java14 contextfile=/u01/app/oracle/sidappl/admin/SID_SERVER1.xml

/usr/java14/bin/java -classpath ../../../fnd/11.5.0/java/3rdparty/stdalone/jdbc12.zip:../../../fnd/11.5.0/java/3rdparty/stdalone/xmlparserv2.zip:/usr/java14/lib/rt.jar:../java: oracle.apps.ad.context.CloneContext -e /u01/app/oracle/sidappl/admin/SID_SERVER1.xml -migrate -perl "/usr/bin/perl" -perl5lib "/usr/opt/perl5/lib/5.8.2/aix-thread-multi:/usr/opt/perl5/lib/5.8.2:/usr/opt/perl5/lib/site_perl/5.8.2/aix-thread-multi:/usr/opt/perl5/lib/site_perl/5.8.2:/usr/opt/perl5/lib/site_perl:." -tmpl ../admin/template/adxmlctx.tmp

Provide the values required for creation of the new APPL_TOP Context file.

Do you want to use a virtual hostname for the target node (y/n) [n] ?:

Does the target system have more than one application tier server node (y/n) [y] ?:

Does the target system application tier utilize multiple domain names (y/n) [n] ?:

Target system concurrent processing node [dbnode]:sever1

Target system administration node [dbnode]:server1

Target system forms server node [webnode]:server2

Target system web server node [webnode]:server2

Is the target system APPL_TOP divided into multiple mount points (y/n) [n] ?:

Target system APPL_TOP mount point [/u01/app/oracle/sidappl]:

Target system COMMON_TOP directory [/u06/app/oracle/sidcomn]:/u01/app/oracle/sidcomn

Do you want to preserve the Display set to server:0.0 (y/n) [y] ?:n

Target system Display [server2:0.0]:

Location of the JDK on the target system [/u06/app/oracle/sidcomn/util/java/1.4/j2sdk1.4.2_04]:/usr/java14
Target system JRE_TOP [/u06/app/oracle/sidcomn/util/java/1.4/j2sdk1.4.2_04]:/ usr/java14
RC-00024: Warning: Could not find perl at expected location:
/tmp//Apache/perl/bin/perl
Please verify the integrity of the filesystem.

Perl executable location is set to:
/usr/bin/perl

Enter the Database listener port [1539]:

APPS password is required to validate database connection using database port 1539
Enter APPS Password [APPS]:abcd
Database port is 1539

Do you want the middle-tier services on the target system to have the same port values as the source system (y/n) [y] ?:
Web Listener port is 8018
Complete port information available at /u01/app/oracle/sidappl/admin/out/SID_server2/portpool.lst

UTL_FILE_DIR on database tier consists of the following directories.

1. /usr/tmp/SID
2. /usr/tmp
3. /u52/app/oracle/siddb/10.2.0/appsutil/outbound/SID_sunserver
Choose a value which will be set as APPLPTMP value on the target node [1]:1

Target system APPL_TOP of the Forms node:/u01/app/oracle/sidappl

Creating the new APPL_TOP Context file from :
/u01/app/oracle/sidappl/ad/11.5.0/admin/template/adxmlctx.tmp

The new APPL_TOP context file has been created :
/u01/app/oracle/sidappl/admin/SID_server2.xml

JDK for Solaris was found under $COMMON_TOP
Removing directory /u01/app/oracle/sidcomn/util/java/1.4/j2sdk1.4.2_04
Done.

Log file located at /u01/app/oracle/sidappl/ad/11.5.0/bin/CloneContext_11121151.log
applsid@server2$
Note: See document 216664.1 on OracleMetaLink for more information on port pool.

1. 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. (on both the application tier nodes)

cd [u01/app/software/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

P.S: Add the entry for iAS & 8.0.6 home variables in your xml file, please make sure all the occurrence of /tmp is replaced properly by tools_oh or weboh as appropriate before proceeding further. If still not clear see the SID xml file for reference

i.e. : /u02/app/oracle/sidora/iAS

/u
02/app/oracle/sidora/8.0.6/SID_server1.env
/u02/app/oracle/sidora/8.0.6

Also make sure to change the perl location to point to iAS/perl please see the xml file for SDBA

1. 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:
o cd /bin
o ./adconfig.sh run=INSTE8_SETUP contextfile=

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

1. Download and apply the customer-specific update with AutoPatch
Within 30 minutes from the time you uploaded the manifest file at step 2.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.

Note: Executables dependent on third party products (Ilog, Roguewave, and Quantum) might fail during relinking. This is expected and is addressed in "Section 3: Finishing Tasks". In that case, answer "yes" when adpatch asks whether to "Continue as if it were successful".

README to apply the patch

Complete the following steps to apply this patch:

To apply this patch the following steps must be completed:
1. Source the APPL_TOP environment file on the target migration system
This environment was created during the execution of AutoConfig.
See MetaLink Note 238276.1, the step entitled "Run AutoConfig on the
Target Node."
2. Unzip this patch into a patch directory.
3. Change directories to the patch directory e.g 6612518 directory created in step 2 above.
4. Run adpatch from the current directory to apply this patch using
the u6612518.drv driver:
./adpatch options=noprereq

Please note all the executables under sht product family will fail as we don’t have these on Soalris.This is taken care in the

1. Review the technology stack patch level

Identify any patches previously applied to your Source System technology stack which are not included in the "Release Versions" section of " Installing Oracle9i Application Server 1.0.2.2.2 with Oracle Applications 11i" (document 146468.1). Apply these patches to your Target System technology stack. (Not Applicable)
Applied 5473858 (techstack RUP5).autoconfig failed with following error
autoconfig fails on adgendbc.sh with ORA-06512: at "APPS.FND_APP_SERVER_PKG", line 91
After applying 5473858 autoconfig fails on apps tier to resolve it apply patch 6496781. (Doc id 434494.1 on metalink)
Note: For information and instructions on applying the latest Developer 6i patchset, see Note 125767.1 on OracleMetaLink (Not Applicable)

Applied the following developer 6i patches
Developer 6i Developer 6i Patch Forms Reports Graphics Apps Interop Patch
Patch 18* 4948577
6.0.8.27.x 6.0.8.27.x 6.0.8.17.x 4888294

And the additional patches
5713544
4261542
5216496
5753922
6195758

2. Download and apply the techstack interop patch

Apply patch 4139957 to the Target Oracle Applications file system

3. 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 /

2. Run adadmin to generate messages, forms, reports, graphics and jar files.
3. Run AutoConfig to complete the Target System configuration

$AD_TOP/bin/adconfig.sh contextfile=

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

1. Update 3rd party extensions

ILOG Apply patch 2837811 and relink dependent executables.

ROGUEWAVE Apply patch 3006092 and relink dependent executables

After applying the above patches the adrelink should exit with status 0 i.e there should be no errors in relink.

2. Review and update your Target System application tier settings and customizations

a. Recompile any custom code (forms, C) in the Target System APPL_TOP.
b. 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:
Setup Documentation
UTF8 "Installing Oracle Applications 11i" Manual,
Chapter 5, "Set Up UTF8 Character Set".
Discoverer 4i Document 139516.1 on OracleMetaLink.

SSO or Portal 3i Document 146469.1 on OracleMetaLink.

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 (would be done by autoconfig but please check)
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.
5.
Table Name Column Name Column Value Details
WF_NOTIFICATION_ATTRIBUTES TEXT_VALUE Value starts with http:// : Update to new web host
WF_ITEM_ATTRIBUTE_VALUES TEXT_VALUE Value starts with "http:// : 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

6. 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:

a. Verify the AD classpath:

1. Run $ADJVAPRG -version
2. 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.

b. Verify the AF classpath:

1. Run $AFJVAPRG -version
2. 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.
The above would be done once you run autoconfig so no need to worry but do check this.

c. Run AutoConfig as described in document 165195.1 on OracleMetalink.
7. Start all services on the Target System
Start all services by running the script:
adstrtal.sh /
located in /admin/scripts//