Oracle Apps Mig
Content
Migrating to Linux with Oracle Applications
Release 11iiWareLogic
COOL - Apps Migration to Linux
COOL - Apps Migration to Linux
COOL - Apps Migration to Linux
Why Migrating to Linux?
Advantages as compared to Windows
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, Oracle’s 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. Oracle’s 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.
Long-Standing Commitment to Linux: Oracle’s long-standing commitment to Linux started with
the release of the industry’s first commercial database on Linux in 1998, and that commitment
and leadership continues today. With more than 9,000 developers using a Linux infrastructure
to do product development, Oracle boasts one of the world’s largest commercial Linux
development organizations. Oracle’s industry-leading benchmarks demonstrate world-record
performance and price-performance of its database, application server and application suites on
the low-cost Linux platform. These benchmarks have been run on small 2 -processor servers,
large 32-processor servers, and multiple clustered servers demonstrating the ability of Linux to
support all sizes of workloads on transactional and decision support systems. Oracle’s longstanding commitment to securing customer data continues by hel ping to secure the Linux
platform. For example, Oracle Database on Linux has met the Common Criteria Standard at EAL4
+ level – the highest industry security level for commercial software.
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 1
COOL - Apps Migration to Linux
How it will happen?
This paper considers platform migration to Linux operating system. Migration will divide into two
sections.
1. Oracle Application migration.
2. Oracle Database migration.
Platform migration refers to Oracle Metalink document - Migrating to Linux with Oracle Applications
Release 11i [ID 238276.1] for application migration and Export/Import Process for Oracle Applications
Release 11i [ID 230627.1] .
Adv antag e of Linux as an operating sy stem for platform m igration
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.
Oracle Platform Migration Path
Checking hardware, setting operating system parameters and configuration of target & source
system.
Oracle application migration steps refer platform migration note 238276.1.
Oracle Database migration steps refer database migration note 230627.1.
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 2
COOL - Apps Migration to Linux
1. Oracle Application Migration
Application migration will divide in three sections Pre -requisites (Operating system checks& required
changes), Application migration steps , Post migration actions.
Pre-Requisites
Must be completed prior to using the migration utility.
Application migration steps
Post migration actions: Tasks that need to be performed after the migration.
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
COOL - Apps Migration to Linux
Autoconfig. Refer to 165195.1.
Apply the latest AutoConfig Refer 165195.1 for latest autoconfig template patch.
Template patch
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
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 11 i
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 https://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 fi les 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.
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
APPL_TOP
OA_HTML
OA_JAVA
COMMON_TOP/util
COMMON_TOP/_pages (when that directory exists)
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 4
COOL - Apps Migration to Linux
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
Complete path where the JDK is installed.
Full Path to the Source System Applications XML context file
located in APPL_TOP/admin on the Target System.
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.
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 5
COOL - Apps Migration to Linux
5. 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.[timestamp].log) under the iAS ORACLE_HOME
to ensure that there are no errors.
6. 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 interoperability patches.
Patches
3830807
3170128
3846086
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
7. 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
o
cd $AD_TOP/bin
./adconfig.sh run=INSTE8_SETUP context file=[TARGET SYSTEM CONTEXT FILE]
Note: This command does not require the environment to be sourced.
8. Download and apply the customer-specific update with AutoPatch
Within 30 minutes from the time you uploaded the manifest file at step 2.b yo u 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.
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 6
COOL - Apps Migration to Linux
Note: Executables dependent on third party products (Ilog, Roguewave, 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".
9. 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.
10. 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.
Note: For information and instructions on applying the latest Developer 6i patchset, see Note
125767.1 on OracleMetaLink
11. Download and apply the techstackinterop patch
Apply patch 4139957 to the Target Oracle Applications file system.
12. 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:
.
If migrating the Forms node, run the following script:
$AD_TOP/patch/115/bin/adgensgn.sh [Apps User]/[Apps Password]
a. Run adadmin to generate messages, forms, reports, graphics and jar files.
13. 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 t ier server processes.
After this step, the Source System middle tier will no longer be available.
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 7
COOL - Apps Migration to Linux
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
ILOG
ROGUEWAVE
QUANTUM
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.
3. Update printer settings
If the newly migrated System needs to utilize different printers, update the Target System with the
new printer settings now.
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 8
COOL - Apps Migration to Linux
4. Update Workflow configuration settings
Migrating an Oracle Applications instance will not update the host and instance specific i nformation
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.
Column
Name
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
Column Value Details
Value starts with http://[old web host] :
Update to new web host
Value starts with "http://[old web host] :
Update to new web host
Create a new System defined as the new
global database name using the
Workflow Administrator Web
Applications responsibility.
Value needs to be replaced with the
database global name
Update database link with the new
database global name.
Update with the new web host name
Update to point at the new PLSQL
listener name
Update with the correct path to the
logfile directory
Update with the new directory path on
the Target System
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 9
COOL - Apps Migration to Linux
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:
a. 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.
b. 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.
c. 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/[CONTEXT NAME]
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 10
COOL - Apps Migration to Linux
2. Oracle Database Migration
We recommend that EBS customers upgrade to the latest patchsets of the Oracle database (starting
with version 10gR2) to take advantage of the latest features and advances in Oracle database
technology.
This document describes the process of re-creating an existing Oracle Applications Release 11i database
instance using the export and import utilities.
The export and import utilities allow you to move existing data in Oracle format to and from Oracle
databases. For example, export files can archive database data, or move data among different Oracle
databases that run on the same or different operating systems. This document assumes that you are
already familiar with export and import.
There are special considerations when exporting or importing an Oracle Applications 11i database
instance. This process consists of four discrete steps. Each step is covered in a separate section in this
document.
Section 1: Export the source Applications Release 11 i database instance
Tasks that must be performed to produce a valid export of an Applications Release 11i database
instance.
Section 2: Prepare a target Applications Release 1 1i database instance
Tasks for creating an empty database instance in preparation for import.
Section 3: Import the Applications Release 11i database instance
Tasks for running the import utility.
Section 4: Update the imported Applications Release 11i database instance
Tasks that must be performed to res tore the imported Applications Release 11i database
instance to a fully functional state.
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.
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 11
COOL - Apps Migration to Linux
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.
Section 1: Export the source Applications Release 11 i database instance
This section describes how to ensure that you have the required patches, create your export file, and
capture important information that is required to import your database.
1. Ensure minimum requirements of components are met
Perform the steps in the "Before the Database Installation" subsection of Section 1 of the Oracle
Applications Release 11i with Oracle9i Release 2 (9.2.0) Interoperability Notes.
2. Apply AD minipack (conditional)
Ensure that AD Minipack F, 2141471, or later has been applied to the source Applications
system. Apply the AD minipack on all application server tiers. Follow the instructions in the
readme carefully.
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 12
COOL - Apps Migration to Linux
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.
3. Apply the Applications consolidated export/import utility patch
Apply patch 4872830 to the source administration server node. This patch provides several SQL
scripts that facilitate exporting and importing an Applications database instance. The patch
includes a template for the export and import parameter files and a perl script which cr eates an
AD patch driver.
4. Apply Materialized Views patch 2447246 (conditional)
If the source environment is Applications Release 11.5.7, apply patch 2447246 to the source
administration server node.
5. Apply latest Applications database preparation scripts patch
Apply patch 4775612 to every application tier server node in the source system.
6. Identify the GLOBAL_NAME
The GLOBAL_NAME variable is used to uniquely identify a database instance. The
GLOBAL_NAME of the target database instance must match that of the source database
instance. Identify the GLOBAL_NAME of the source database instance by using SQL*Plus to
connect to the source database as any user and perform the following query:
SQL> select * from global_name;
Make note of the value returned. It will be needed in the next section.
7. Create the export parameter file
A template for the export parameter file has been included as part of the export/import patch
4872830. Copy $AU_TOP/patch/115/import/auexpimp.dat from the source administration
server node to the directory on the database server node where the export dump files are to be
created. Use a text editor to modify the file to reflect the source environment and other
customized parameters.
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
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 13
COOL - Apps Migration to Linux
Comment out or remove the toid_novalidate parameter. It is used only for the import process.
Do not change the other parameters.
The export process uses as many of the listed file names as necessary to hold the exported data.
You must ensure that the number of dump files specified, as well as the size of each dump file, is
sufficient to contain all the data in your source database instance.
8. Generate target database instance creation script adcrdb.sql
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:
o adcrdb.sql which you use to create the target database instance with the appropriate
table space and file structure
o adpostcrdb.sql which you use to convert table spaces to locally managed.
The adpostcrdb.sql script converts all table spaces except for SYSTEM to locally managed table
spaces, if they are not already so.
On the source administration server node, use SQL*Plus to 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
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
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 14
COOL - Apps Migration to Linux
10. Record Oracle Context and OLAP default table space
On the source database server node, use SQL*Plus to connect to the source database as sysdba
and run the following query:
11. $ sqlplus /nolog
12. SQL> connect / as sysdba;
13. SQL> select username, default_table space from dba_users
14. where username='CTXSYS' or username='OLAPSYS';
Note the default table space returned by the query. You will need it in the next section.
15. 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.
16. Apply RDBMS patch 1879479 (conditional)
If the source Oracle home is Oracle8i Enterprise Edition Release 8.1.7 and the patch set level is
8.1.7.2, apply RDBMS patch 1879479 to it. Restart the database instance once the patch has
been applied.
17. Apply workaround for AQ privileges (conditional)
If the source Oracle home is Oracle9i Release 2, follow the directions in the workaround in
document 235422.1 on OracleMetaLink.
18. Apply workaround for nested tables (conditional)
If the source Oracle home is Oracle9i Release 2, use SQL*Plus to connect to the database as SYS
and run the following command:
19. SQL> CREATE OR REPLACE VIEW exu81csc (release) AS
20. SELECT '8.1.0.0.0' FROM DUAL
21. 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:
22. $ expparfile=[export parameter file name]
Typically, export runs for several hours. It is a good idea to run it in a manner that will allows itto
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.
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 15
COOL - Apps Migration to Linux
Section 2: Prepare a target Applications Release 11 i database instance
This section describes how to create the empty target database and populate it with all of the required
system objects prior to running import.
The Oracle home of the target database instance can be the same Oracle home that the source database
instance uses, or it can be different (on another machine running a different operating system, for
example), as long as it uses Oracle9i Enterprise Edition Release 2.
1. Create target Oracle9i Oracle home (conditional)
If you want the target Oracle9i Oracle home to be separate from the source Oracle home, you
must create it now. To complete this task, perform the steps in the "Database Installation"
subsection of Section 1 of the Oracle Applications Release 11i with Oracle9i Release 2 (9.2.0)
Interoperability Notes.
2. Modify sqlnet.ora file (Windows only)
If the target database server node is running Windows, add the following line to the sqlnet.ora
file in the %ORACLE_HOME%\network\admin\[SID] directory, if it does not already exist:
3. SQLNET.AUTHENTICATION_SERVICES=(NTS)
4. Create the target initialization parameter file and CBO parameter file
The initialization parameter file (init[SID].ora) and cost-based optimizer (CBO) parameter file
(ifilecbo.ora) are located in the $ORACLE_HOME/dbs directory on the source database server
node. Copy both files to the Oracle9i $ORACLE_HOME/dbs directory on the target database
server node.
Refer to Database Initialization Parameters (init.ora settings) in Oracle Applications Release 11i
and update both the init.ora and ifilecbo.ora files with any necessary changes. You may also
need to update initialization parameters involving the db_name, control_files, and directory
structures.
If you are migrating from an Oracle8i Oracle home to an Oracle9i Oracle home, do not convert
rollback segments to System Managed Undo (SMU) tablespaces yet. You will perform this task in
Section 3, after the import.
If the source database is Oracle9i, comment out the parameters undo_tablespace,
undo_management, and undo_suppress_errors in the initialization parameter file of the target
database instance. These parameters you add after the adcrdb.sql script has been run.
5. Create the target database instance
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 t he 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. If the target database
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 16
COOL - Apps Migration to Linux
server node is running Windows, update the directory structure from UNIX/Linux format to
Windows format.
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;
For Windows:
SQL> startup nomountpfile=%ORACLE_HOME%\dbs\init%ORACLE_SID%.ora
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.
6. 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) or
addb920_nt.sql, adsy920_nt.sql, adjv920_nt.sql, and admsc920_nt.sql (Windows).
As you run each of the next four steps, note the following:
o
o
The remarks section at the beginning of each script contains additional information.
Each script creates a log file in the current directory.
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 17
COOL - Apps Migration to Linux
7. 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, use SQL*Plus to connect to the target database instance as
SYSTEM and run $ORACLE_HOME/appsutil/admin/addb920.sql (UNIX/Linux) or addb920_nt.sql
(Windows).
Here is an example on UNIX or Linux:
$ sqlplus system/[system password] \
@$ORACLE_HOME/appsutil/admin/addb920.sql
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
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 18
COOL - Apps Migration to Linux
10. 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
SQL*Plus to connect to the target database instance as SYSTEM and run
$ORACLE_HOME/appsutil/admin/admsc920.sql (UNIX/Linux) or admsc920_nt.sql (Windows).
You must pass the following arguments to the script, in the order specified:
Argument
Remove context?
default table space
temporary table space
Inter Media shared library
Value
FALSE
[default Oracle Context table space recorded in Section 1]
TEMP
\bin\oractxx9.dll
11. Here is an example on UNIX or Linux:
12. $ sqlplus system/[system password] \
13. @$ORACLE_HOME/appsutil/admin/admsc920.sql FALSE CTXSYS TEMP OLAPSYS \
14. /u01/oracle/920/9204/ctx/lib/libctxx9.so
15. 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. On the target database server node, use SQL*Plus to
connect to the database instance as SYSTEM and run the following command.
16. $ sqlplus system/[system password] @adpostcrdb.sql
17. Apply Oracle Portal patch 2857908
As the owner of the iAS Oracle home, apply patch 2857908 to the target database instance if
Oracle Portal version 3.0.9.8.x is installed in the source database instance. Perform steps 1 -5 in
the README.txt of the patch. Complete steps 6-8 after the import process.
18. 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:
19. SQL> alter database rename global_name to [source db global name] ;
You can set the GLOBAL_NAME to any value after the import.
20. 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.
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 19
COOL - Apps Migration to Linux
Section 3: Import the Applications Release 11i database instanceThis section describes how to use the
import utility to load the Oracle Applications data into the target database.
1. 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:
o Remove the "compress=y" parameter
o Add the following parameters:
ignore=y
analyze=n
commit=y
o
o
o
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.
2. Copy the export dump files
Copy the export dump files from the source database server node to the target database server
node. It does not matter what directory you use, but copying them to the same location
simplifies the import command.
3. 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:
4. $ imp parfile=[import parameter file name]
Typically, import runs for several hours. It is a good idea to run the import i n a manner that
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. Once the import is complete , you can delete the export dump files, as
well as the export and import parameter files, from the source and target database server
nodes.
5. Convert rollback segments to System Managed Undo tablespaces (conditional)
If the source Oracle home is Oracle8i Enterprise Edition, follow the instructions in the "Enabling
System Managed Undo (SMU)" and "Temporary Tablespace Setup" sections of Database
Initialization Parameters (init.ora settings) in Oracle Applications Release 11i to convert from
rollback segment usage to SMU, and to confirm that the temporary table space is properly
defined.
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 20
COOL - Apps Migration to Linux
Section 4: Update the imported Applications Release 11 i database instance
This section describes how to recreate the database objects and relationships that are not handled by
the export and import utilities.
1. 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. Then, on the target database server node, as the
owner of the Oracle9i file system and database instance, use SQL*Plus to 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
crea tes a l og file i n the current directory.
2. Perform post-import steps outlined in the Interoperability documents
Complete the steps in the "After the Database Upgrade" subsection of section 1 of the Oracle
Applications Release 11i with Oracle9i Release 2 (9.2.0) Interoperability Notes .
3. You may skip steps that have been completed previously. For example, if patch 2838093 is
included in the source environment, there is no need reapply it.
4. Create OWA_MATCH package (conditional)
If you are using iAS 1.0.2, perform the steps in document 312165.1 to create SYS.OWA_MATCH
on the target database.
5. Perform post-import Oracle Portal steps
Perform steps 6-8 in the README.txt of patch 2857908.
6. Create ConText and Spatial objects
Certain ConText and Spatial objects are not preserved by the import process. The consolidated
export/import utility patch 4872830 that you applied to the source administration server node
in Section 1 contains a perl script, dpost_imp.pl, that you can run to generate an AutoPatch
driver file. You use this driver file to call the scripts that create these objects. Run the following
command:
7. $ perl $AU_TOP/patch/115/driver/dpost_imp.pl [driver file]
8. Once the driver file has been generated, use AutoPatch to apply it on the target administration
server node.
9. Compile invalid objects
On the target database server node, as the owner of the Oracle9 i file system and database
instance, use SQL*Plus to connect to the target database as SYS and run the
$ORACLE_HOME/rdbms/admin/utlrp.sql script to compile invalid objects.
10. $ sqlplus sys/[sys password] @$ORACLE_HOME/rdbms/admin/utlrp.sql
11. Maintain Applications database objects
Run AD Administration on the target administration server node. From the Maintain
Applications Database Objects menu, perform the following tasks:
a) Compile flexfield data in AOL tables
b) Recreate grants and synonyms for APPS schema(s)
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 21
COOL - Apps Migration to Linux
12. If you use Multiple Reporting Currencies:
a) Maintain Multiple Reporting Currencies schema(s)
Enter Yes for the following options:
Update MRC schema itself
Compile invalid objects after updating MRC schema objects
Recreate MRC triggers in the APPS schema(s)
13. Apply workaround for rule-based subscribers (conditional)
If the source Oracle home is Oracle8i Enterprise Edition Release 8.1.7 and the patch set level of
the target Oracle home is 9.2.0.5 or earlier, use SQL*Plus to connect to the database as SYS and
run the following command:
14. SQL> exec sys.dbms_prvtaqis.upgrade_rulesub_msgs;
15. Start Applications server processes
Start all the server processes on the target Applications system. You can allow users to access
the system at this time.
16. Create DQM indexes
Create DQM indexes by following these steps:
a) Log on to Oracle Applications with the "Trading Community Manager" responsibility
b) Click Control > Request > Run
c) Select "Single Request" option
d) Enter "DQM Staging Program" name
e) Enter the following parameters:
Number of Parallel Staging Workers: 4
Staging Command: CREATE_INDEXES
Continue Previous Execution: NO
Index Creation: SERIAL
f) Click "Submit"
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 22
Release 11iiWareLogic
COOL - Apps Migration to Linux
COOL - Apps Migration to Linux
COOL - Apps Migration to Linux
Why Migrating to Linux?
Advantages as compared to Windows
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, Oracle’s 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. Oracle’s 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.
Long-Standing Commitment to Linux: Oracle’s long-standing commitment to Linux started with
the release of the industry’s first commercial database on Linux in 1998, and that commitment
and leadership continues today. With more than 9,000 developers using a Linux infrastructure
to do product development, Oracle boasts one of the world’s largest commercial Linux
development organizations. Oracle’s industry-leading benchmarks demonstrate world-record
performance and price-performance of its database, application server and application suites on
the low-cost Linux platform. These benchmarks have been run on small 2 -processor servers,
large 32-processor servers, and multiple clustered servers demonstrating the ability of Linux to
support all sizes of workloads on transactional and decision support systems. Oracle’s longstanding commitment to securing customer data continues by hel ping to secure the Linux
platform. For example, Oracle Database on Linux has met the Common Criteria Standard at EAL4
+ level – the highest industry security level for commercial software.
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 1
COOL - Apps Migration to Linux
How it will happen?
This paper considers platform migration to Linux operating system. Migration will divide into two
sections.
1. Oracle Application migration.
2. Oracle Database migration.
Platform migration refers to Oracle Metalink document - Migrating to Linux with Oracle Applications
Release 11i [ID 238276.1] for application migration and Export/Import Process for Oracle Applications
Release 11i [ID 230627.1] .
Adv antag e of Linux as an operating sy stem for platform m igration
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.
Oracle Platform Migration Path
Checking hardware, setting operating system parameters and configuration of target & source
system.
Oracle application migration steps refer platform migration note 238276.1.
Oracle Database migration steps refer database migration note 230627.1.
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 2
COOL - Apps Migration to Linux
1. Oracle Application Migration
Application migration will divide in three sections Pre -requisites (Operating system checks& required
changes), Application migration steps , Post migration actions.
Pre-Requisites
Must be completed prior to using the migration utility.
Application migration steps
Post migration actions: Tasks that need to be performed after the migration.
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
COOL - Apps Migration to Linux
Autoconfig. Refer to 165195.1.
Apply the latest AutoConfig Refer 165195.1 for latest autoconfig template patch.
Template patch
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
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 11 i
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 https://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 fi les 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.
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
APPL_TOP
OA_HTML
OA_JAVA
COMMON_TOP/util
COMMON_TOP/_pages (when that directory exists)
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 4
COOL - Apps Migration to Linux
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
Complete path where the JDK is installed.
Full Path to the Source System Applications XML context file
located in APPL_TOP/admin on the Target System.
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.
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 5
COOL - Apps Migration to Linux
5. 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.[timestamp].log) under the iAS ORACLE_HOME
to ensure that there are no errors.
6. 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 interoperability patches.
Patches
3830807
3170128
3846086
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
7. 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
o
cd $AD_TOP/bin
./adconfig.sh run=INSTE8_SETUP context file=[TARGET SYSTEM CONTEXT FILE]
Note: This command does not require the environment to be sourced.
8. Download and apply the customer-specific update with AutoPatch
Within 30 minutes from the time you uploaded the manifest file at step 2.b yo u 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.
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 6
COOL - Apps Migration to Linux
Note: Executables dependent on third party products (Ilog, Roguewave, 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".
9. 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.
10. 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.
Note: For information and instructions on applying the latest Developer 6i patchset, see Note
125767.1 on OracleMetaLink
11. Download and apply the techstackinterop patch
Apply patch 4139957 to the Target Oracle Applications file system.
12. 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:
.
If migrating the Forms node, run the following script:
$AD_TOP/patch/115/bin/adgensgn.sh [Apps User]/[Apps Password]
a. Run adadmin to generate messages, forms, reports, graphics and jar files.
13. 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 t ier server processes.
After this step, the Source System middle tier will no longer be available.
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 7
COOL - Apps Migration to Linux
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
ILOG
ROGUEWAVE
QUANTUM
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.
3. Update printer settings
If the newly migrated System needs to utilize different printers, update the Target System with the
new printer settings now.
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 8
COOL - Apps Migration to Linux
4. Update Workflow configuration settings
Migrating an Oracle Applications instance will not update the host and instance specific i nformation
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.
Column
Name
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
Column Value Details
Value starts with http://[old web host] :
Update to new web host
Value starts with "http://[old web host] :
Update to new web host
Create a new System defined as the new
global database name using the
Workflow Administrator Web
Applications responsibility.
Value needs to be replaced with the
database global name
Update database link with the new
database global name.
Update with the new web host name
Update to point at the new PLSQL
listener name
Update with the correct path to the
logfile directory
Update with the new directory path on
the Target System
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 9
COOL - Apps Migration to Linux
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:
a. 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.
b. 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.
c. 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/[CONTEXT NAME]
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 10
COOL - Apps Migration to Linux
2. Oracle Database Migration
We recommend that EBS customers upgrade to the latest patchsets of the Oracle database (starting
with version 10gR2) to take advantage of the latest features and advances in Oracle database
technology.
This document describes the process of re-creating an existing Oracle Applications Release 11i database
instance using the export and import utilities.
The export and import utilities allow you to move existing data in Oracle format to and from Oracle
databases. For example, export files can archive database data, or move data among different Oracle
databases that run on the same or different operating systems. This document assumes that you are
already familiar with export and import.
There are special considerations when exporting or importing an Oracle Applications 11i database
instance. This process consists of four discrete steps. Each step is covered in a separate section in this
document.
Section 1: Export the source Applications Release 11 i database instance
Tasks that must be performed to produce a valid export of an Applications Release 11i database
instance.
Section 2: Prepare a target Applications Release 1 1i database instance
Tasks for creating an empty database instance in preparation for import.
Section 3: Import the Applications Release 11i database instance
Tasks for running the import utility.
Section 4: Update the imported Applications Release 11i database instance
Tasks that must be performed to res tore the imported Applications Release 11i database
instance to a fully functional state.
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.
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 11
COOL - Apps Migration to Linux
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.
Section 1: Export the source Applications Release 11 i database instance
This section describes how to ensure that you have the required patches, create your export file, and
capture important information that is required to import your database.
1. Ensure minimum requirements of components are met
Perform the steps in the "Before the Database Installation" subsection of Section 1 of the Oracle
Applications Release 11i with Oracle9i Release 2 (9.2.0) Interoperability Notes.
2. Apply AD minipack (conditional)
Ensure that AD Minipack F, 2141471, or later has been applied to the source Applications
system. Apply the AD minipack on all application server tiers. Follow the instructions in the
readme carefully.
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 12
COOL - Apps Migration to Linux
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.
3. Apply the Applications consolidated export/import utility patch
Apply patch 4872830 to the source administration server node. This patch provides several SQL
scripts that facilitate exporting and importing an Applications database instance. The patch
includes a template for the export and import parameter files and a perl script which cr eates an
AD patch driver.
4. Apply Materialized Views patch 2447246 (conditional)
If the source environment is Applications Release 11.5.7, apply patch 2447246 to the source
administration server node.
5. Apply latest Applications database preparation scripts patch
Apply patch 4775612 to every application tier server node in the source system.
6. Identify the GLOBAL_NAME
The GLOBAL_NAME variable is used to uniquely identify a database instance. The
GLOBAL_NAME of the target database instance must match that of the source database
instance. Identify the GLOBAL_NAME of the source database instance by using SQL*Plus to
connect to the source database as any user and perform the following query:
SQL> select * from global_name;
Make note of the value returned. It will be needed in the next section.
7. Create the export parameter file
A template for the export parameter file has been included as part of the export/import patch
4872830. Copy $AU_TOP/patch/115/import/auexpimp.dat from the source administration
server node to the directory on the database server node where the export dump files are to be
created. Use a text editor to modify the file to reflect the source environment and other
customized parameters.
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
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 13
COOL - Apps Migration to Linux
Comment out or remove the toid_novalidate parameter. It is used only for the import process.
Do not change the other parameters.
The export process uses as many of the listed file names as necessary to hold the exported data.
You must ensure that the number of dump files specified, as well as the size of each dump file, is
sufficient to contain all the data in your source database instance.
8. Generate target database instance creation script adcrdb.sql
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:
o adcrdb.sql which you use to create the target database instance with the appropriate
table space and file structure
o adpostcrdb.sql which you use to convert table spaces to locally managed.
The adpostcrdb.sql script converts all table spaces except for SYSTEM to locally managed table
spaces, if they are not already so.
On the source administration server node, use SQL*Plus to 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
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
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 14
COOL - Apps Migration to Linux
10. Record Oracle Context and OLAP default table space
On the source database server node, use SQL*Plus to connect to the source database as sysdba
and run the following query:
11. $ sqlplus /nolog
12. SQL> connect / as sysdba;
13. SQL> select username, default_table space from dba_users
14. where username='CTXSYS' or username='OLAPSYS';
Note the default table space returned by the query. You will need it in the next section.
15. 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.
16. Apply RDBMS patch 1879479 (conditional)
If the source Oracle home is Oracle8i Enterprise Edition Release 8.1.7 and the patch set level is
8.1.7.2, apply RDBMS patch 1879479 to it. Restart the database instance once the patch has
been applied.
17. Apply workaround for AQ privileges (conditional)
If the source Oracle home is Oracle9i Release 2, follow the directions in the workaround in
document 235422.1 on OracleMetaLink.
18. Apply workaround for nested tables (conditional)
If the source Oracle home is Oracle9i Release 2, use SQL*Plus to connect to the database as SYS
and run the following command:
19. SQL> CREATE OR REPLACE VIEW exu81csc (release) AS
20. SELECT '8.1.0.0.0' FROM DUAL
21. 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:
22. $ expparfile=[export parameter file name]
Typically, export runs for several hours. It is a good idea to run it in a manner that will allows itto
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.
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 15
COOL - Apps Migration to Linux
Section 2: Prepare a target Applications Release 11 i database instance
This section describes how to create the empty target database and populate it with all of the required
system objects prior to running import.
The Oracle home of the target database instance can be the same Oracle home that the source database
instance uses, or it can be different (on another machine running a different operating system, for
example), as long as it uses Oracle9i Enterprise Edition Release 2.
1. Create target Oracle9i Oracle home (conditional)
If you want the target Oracle9i Oracle home to be separate from the source Oracle home, you
must create it now. To complete this task, perform the steps in the "Database Installation"
subsection of Section 1 of the Oracle Applications Release 11i with Oracle9i Release 2 (9.2.0)
Interoperability Notes.
2. Modify sqlnet.ora file (Windows only)
If the target database server node is running Windows, add the following line to the sqlnet.ora
file in the %ORACLE_HOME%\network\admin\[SID] directory, if it does not already exist:
3. SQLNET.AUTHENTICATION_SERVICES=(NTS)
4. Create the target initialization parameter file and CBO parameter file
The initialization parameter file (init[SID].ora) and cost-based optimizer (CBO) parameter file
(ifilecbo.ora) are located in the $ORACLE_HOME/dbs directory on the source database server
node. Copy both files to the Oracle9i $ORACLE_HOME/dbs directory on the target database
server node.
Refer to Database Initialization Parameters (init.ora settings) in Oracle Applications Release 11i
and update both the init.ora and ifilecbo.ora files with any necessary changes. You may also
need to update initialization parameters involving the db_name, control_files, and directory
structures.
If you are migrating from an Oracle8i Oracle home to an Oracle9i Oracle home, do not convert
rollback segments to System Managed Undo (SMU) tablespaces yet. You will perform this task in
Section 3, after the import.
If the source database is Oracle9i, comment out the parameters undo_tablespace,
undo_management, and undo_suppress_errors in the initialization parameter file of the target
database instance. These parameters you add after the adcrdb.sql script has been run.
5. Create the target database instance
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 t he 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. If the target database
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 16
COOL - Apps Migration to Linux
server node is running Windows, update the directory structure from UNIX/Linux format to
Windows format.
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;
For Windows:
SQL> startup nomountpfile=%ORACLE_HOME%\dbs\init%ORACLE_SID%.ora
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.
6. 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) or
addb920_nt.sql, adsy920_nt.sql, adjv920_nt.sql, and admsc920_nt.sql (Windows).
As you run each of the next four steps, note the following:
o
o
The remarks section at the beginning of each script contains additional information.
Each script creates a log file in the current directory.
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 17
COOL - Apps Migration to Linux
7. 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, use SQL*Plus to connect to the target database instance as
SYSTEM and run $ORACLE_HOME/appsutil/admin/addb920.sql (UNIX/Linux) or addb920_nt.sql
(Windows).
Here is an example on UNIX or Linux:
$ sqlplus system/[system password] \
@$ORACLE_HOME/appsutil/admin/addb920.sql
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
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 18
COOL - Apps Migration to Linux
10. 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
SQL*Plus to connect to the target database instance as SYSTEM and run
$ORACLE_HOME/appsutil/admin/admsc920.sql (UNIX/Linux) or admsc920_nt.sql (Windows).
You must pass the following arguments to the script, in the order specified:
Argument
Remove context?
default table space
temporary table space
Inter Media shared library
Value
FALSE
[default Oracle Context table space recorded in Section 1]
TEMP
\bin\oractxx9.dll
11. Here is an example on UNIX or Linux:
12. $ sqlplus system/[system password] \
13. @$ORACLE_HOME/appsutil/admin/admsc920.sql FALSE CTXSYS TEMP OLAPSYS \
14. /u01/oracle/920/9204/ctx/lib/libctxx9.so
15. 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. On the target database server node, use SQL*Plus to
connect to the database instance as SYSTEM and run the following command.
16. $ sqlplus system/[system password] @adpostcrdb.sql
17. Apply Oracle Portal patch 2857908
As the owner of the iAS Oracle home, apply patch 2857908 to the target database instance if
Oracle Portal version 3.0.9.8.x is installed in the source database instance. Perform steps 1 -5 in
the README.txt of the patch. Complete steps 6-8 after the import process.
18. 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:
19. SQL> alter database rename global_name to [source db global name] ;
You can set the GLOBAL_NAME to any value after the import.
20. 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.
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 19
COOL - Apps Migration to Linux
Section 3: Import the Applications Release 11i database instanceThis section describes how to use the
import utility to load the Oracle Applications data into the target database.
1. 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:
o Remove the "compress=y" parameter
o Add the following parameters:
ignore=y
analyze=n
commit=y
o
o
o
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.
2. Copy the export dump files
Copy the export dump files from the source database server node to the target database server
node. It does not matter what directory you use, but copying them to the same location
simplifies the import command.
3. 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:
4. $ imp parfile=[import parameter file name]
Typically, import runs for several hours. It is a good idea to run the import i n a manner that
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. Once the import is complete , you can delete the export dump files, as
well as the export and import parameter files, from the source and target database server
nodes.
5. Convert rollback segments to System Managed Undo tablespaces (conditional)
If the source Oracle home is Oracle8i Enterprise Edition, follow the instructions in the "Enabling
System Managed Undo (SMU)" and "Temporary Tablespace Setup" sections of Database
Initialization Parameters (init.ora settings) in Oracle Applications Release 11i to convert from
rollback segment usage to SMU, and to confirm that the temporary table space is properly
defined.
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 20
COOL - Apps Migration to Linux
Section 4: Update the imported Applications Release 11 i database instance
This section describes how to recreate the database objects and relationships that are not handled by
the export and import utilities.
1. 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. Then, on the target database server node, as the
owner of the Oracle9i file system and database instance, use SQL*Plus to 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
crea tes a l og file i n the current directory.
2. Perform post-import steps outlined in the Interoperability documents
Complete the steps in the "After the Database Upgrade" subsection of section 1 of the Oracle
Applications Release 11i with Oracle9i Release 2 (9.2.0) Interoperability Notes .
3. You may skip steps that have been completed previously. For example, if patch 2838093 is
included in the source environment, there is no need reapply it.
4. Create OWA_MATCH package (conditional)
If you are using iAS 1.0.2, perform the steps in document 312165.1 to create SYS.OWA_MATCH
on the target database.
5. Perform post-import Oracle Portal steps
Perform steps 6-8 in the README.txt of patch 2857908.
6. Create ConText and Spatial objects
Certain ConText and Spatial objects are not preserved by the import process. The consolidated
export/import utility patch 4872830 that you applied to the source administration server node
in Section 1 contains a perl script, dpost_imp.pl, that you can run to generate an AutoPatch
driver file. You use this driver file to call the scripts that create these objects. Run the following
command:
7. $ perl $AU_TOP/patch/115/driver/dpost_imp.pl [driver file]
8. Once the driver file has been generated, use AutoPatch to apply it on the target administration
server node.
9. Compile invalid objects
On the target database server node, as the owner of the Oracle9 i file system and database
instance, use SQL*Plus to connect to the target database as SYS and run the
$ORACLE_HOME/rdbms/admin/utlrp.sql script to compile invalid objects.
10. $ sqlplus sys/[sys password] @$ORACLE_HOME/rdbms/admin/utlrp.sql
11. Maintain Applications database objects
Run AD Administration on the target administration server node. From the Maintain
Applications Database Objects menu, perform the following tasks:
a) Compile flexfield data in AOL tables
b) Recreate grants and synonyms for APPS schema(s)
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 21
COOL - Apps Migration to Linux
12. If you use Multiple Reporting Currencies:
a) Maintain Multiple Reporting Currencies schema(s)
Enter Yes for the following options:
Update MRC schema itself
Compile invalid objects after updating MRC schema objects
Recreate MRC triggers in the APPS schema(s)
13. Apply workaround for rule-based subscribers (conditional)
If the source Oracle home is Oracle8i Enterprise Edition Release 8.1.7 and the patch set level of
the target Oracle home is 9.2.0.5 or earlier, use SQL*Plus to connect to the database as SYS and
run the following command:
14. SQL> exec sys.dbms_prvtaqis.upgrade_rulesub_msgs;
15. Start Applications server processes
Start all the server processes on the target Applications system. You can allow users to access
the system at this time.
16. Create DQM indexes
Create DQM indexes by following these steps:
a) Log on to Oracle Applications with the "Trading Community Manager" responsibility
b) Click Control > Request > Run
c) Select "Single Request" option
d) Enter "DQM Staging Program" name
e) Enter the following parameters:
Number of Parallel Staging Workers: 4
Staging Command: CREATE_INDEXES
Continue Previous Execution: NO
Index Creation: SERIAL
f) Click "Submit"
iWare Logic Technologies Pvt. Ltd.
Web Site: www.iwarelogic.com
Page 22
