Professional Documents
Culture Documents
Oracle Apps Mig
Oracle Apps Mig
Release 11iiWareLogic
COOL - Apps Migration to Linux
Database administration on Linux operating system like scheduling cron jobs (automation of
scripting through operating system) becomes easier.
Security: File handling like copying ,moving , changing ownership and rights . Very less cha nce of
virus attacks.
Performance : With Oracle solutions on Linux, customers benefit from high performance,
complete reliability, and data security at a fraction of the cost of proprietary platforms.
Maintenance : Routine activities of Oracle Apps syste m like cloning , patching and running
oracle admin scripts on Linux are the most easier than any other operating system.
Reference from Oracle On Linux from Oracle Data Sheet, May 2008.
Linux in The Data Center : Oracle further demonstrates its commitment to Linux by running its
own IT systems on Linux, and has realized first-hand the benefit of lower IT costs from using
Linux in a grid computing infrastructure. For example, Oracle On Demand, Oracles data and
applications outsourcing business, runs on a Linux infrastructure. Oracle customers such as
Electronic Arts, Dell, and Ohio Savings Bank, as well as thousands of others in various industry
verticals, are deploying their transaction processing, decision support , and third-party
applications on the Linux platform. Oracles growing list of partner Independent Software
Vendors has certified their application solutions for the Linux platform, offering customers a
wide choice of applications on Linux to suit the needs of their business. Oracle is firmly
established as the leader in the Linux database market with more than 82 percent market share.
Page 1
It i s most quickly a nd easily moves a n existing Ora cle Applications middle tier System
from a ny platform to Li nux.
It hel ps you to utilize fast, l ow-cost hardware for your Applications middle tier.
Util ity will keep your exact Applications patch level, so that no APPL_TOP/Database
s ynchronization is necessary.
It a l so allows you to retain many customizations.
Checking hardware, setting operating system parameters and configuration of target & source
system.
Page 2
Section 1: Pre-requisites
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.
Verify OS requirements on Target Before migrating to the new platform, ensure the Target System
System
meets all the requirements Refer to release notes 316803.1 &
Update notes 316806.1.
Verify the software versions on The following software component versions must exist on the
the Target System
Source and Target nodes.
1. Perl Minimum Version (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.
2. 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
minimum 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)
Verify the database version
Minimum database version required 8.1.7 or greater. If the
Database is not on a certified combination with Oracle
Applications, you must upgrade the Database to the latest certified
version available
Apply the latest AD Patch
Apply patch 5161680 (AD.I.5) or higher. Check Adpatch level
sqlplus [Apps User]/[Apps Password] @[AD_TOP]/sql/adutconf.sql
Implement AutoConfig on the If the Source Applications System was created with Rapid Install
Application Tier
version 11.5.8 or earlier you must migrate the System to
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 3
Page 4
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 Syste m.
b) Copy the security file for JInitiator
a. 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.
b. 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:
o cd $AD_TOP/bin
o perl adclonectx.pl migrate java=[JDK HOME] \ contextfile=[SOURCE SYSTEM CONTEXT
FILE]
Where:
JDK HOME
SOURCE SYSTEM
CONTEXT FILE
4. 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.
Page 5
Description
Oracle 8.0.6.3 Interop patch
Oracle 8.0.6 Interop patch for Discoverer 4i
8.1.7.4 Interop patch for iAS ORACLE_HOME
cd $AD_TOP/bin
./adconfig.sh run=INSTE8_SETUP context file=[TARGET SYSTEM CONTEXT FILE]
Page 6
Page 7
Details
Apply patch 2837811 and relink dependent executables.
Apply patch 3006092 and relink dependent executables.
Follow instructions in document 224273.1 on OracleMetaLink
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
UTF8
Discoverer 4i
SSO or Portal 3i
Documentation
"Installing Oracle Applications 11i" Manual,
Chapter 5, "Set Up UTF8 Character Set".
Document 139516.1 on OracleMetaLink.
Document 146469.1 on OracleMetaLink.
Page 8
Table Name
WF_NOTIFICATION_ATTRIBUTES TEXT_VALUE
WF_ITEM_ATTRIBUTE_VALUES
TEXT_VALUE
WF_SYSTEMS
GUID
WF_SYSTEMS
NAME
WF_AGENTS
ADDRESS
FND_FORM_FUNCTIONS
WEB_HOST_NAME
FND_FORM_FUNCTIONS
WEB_AGENT_NAME
FND_CONCURRENT_REQUESTS
LOGFILE_NAME
FND_CONCURRENT_REQUESTS
OUTFILE_NAME
Page 9
Page 10
The target (import to) ORACLE_HOME directory must be Oracle9 i Enterprise Edition Release 2 (9.2.0).
The source (export from) ORACLE_HOME directory may be either Oracle8i Enterprise Edition Release
8.1.7 or Oracle9i Enterprise Edition Release 2 (9.2.0).
The instructions in this document assume that the source and target ORACLE_HOME directories are
both Oracle9i Enterprise Edition Release 2 and that the target node is a different machine than the
corresponding source node. Nevertheless, the source and target ORACLE_HOME directories can reside
wherever you choose. You can use these instructions even if the target and source nodes are the same
machine.
Page 11
Attention
This document uses UNIX/Linux syntax when describing directory structures. However, it applies to
Windows servers as well. Where there is a significant difference in tasks for Windows, specific
instructions are given.
Some of the tasks in this document affect the APPL_TOP of one or more application server tiers. Those
tasks require that the Applications file system environment be enabled by running APPSORA.env file (for
UNIX or Linux) or the envshell.cmd file (for Windows) prior to performing the tasks. Other tasks affect
the Applications database instance. Those tasks require that the Oracle9i environment be enabled by
running the [ORACLE_SID].env/cmd file under the Oracle9i Oracle home on the database server node
prior to performing the tasks. In addition, you may have more than one Oracle home installed on the
database server node (Oracle8, Oracle8i, or OracleiAS), so it is important that you run the correct
[ORACLE_SID].env/cmd file before performing tasks that affect the database instance. Read the
instructions carefully to determine which environment should be enabled for each step.
Attention
This document assumes that the source and target application se rver tiers are the same. To create new
application server tiers for the target environment and to migrate the database server tier through
export/import at the same time, perform the steps in Migrating to Linux with Oracle Applications
Release 11i either before starting or after completing all the steps in this document. Then, update and
run AutoConfig for the source database and application server tiers to enable the source environment.
Page 12
Attention
When applying the AD minipack, be sure to run the copy (c) driver on all application server
tiers before running the database (d) driver on the administration server node.
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
Page 13
Page 14
Page 15
Page 16
The remarks section at the beginning of each script contains additional information.
Each script creates a log file in the current directory.
Page 17
Attention
When connecting as SYSTEM, you may get the following error:
ORA-06653: PLS-213: Package standard not available. Error accessing package.
You may ignore this error message.
8. 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, use SQL*Plus to connect to the target
database instance as SYSTEM and run $ORACLE_HOME/appsutil/admin/adsy920.sql
(UNIX/Linux) or adsy920_nt.sql (Windows).
Here is an example on UNIX or Linux:
$ sqlplus system/[system password] \
@$ORACLE_HOME/appsutil/admin/adsy920.sql
9. 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 re-runnable. On the target database server node, use SQL*Plus to connect to the target
database instance as SYSTEM and run $ORACLE_HOME/appsutil/admin/adjv920.sql
(UNIX/Linux) or adjv920_nt.sql (Windows).
Here is an example on UNIX or Linux:
$ sqlplus system/[system password] \
@$ORACLE_HOME/appsutil/admin/adjv920.sql
Page 18
Value
FALSE
[default Oracle Context table space recorded in Section 1]
TEMP
\bin\oractxx9.dll
Page 19
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
Page 20
Page 21
Page 22