4AA2-0266ENW

Oracle E-Business Suite Release 12.1

upgrade and platform migration guide -

HP AlphaServer systems running Tru64

Unix to HP-UX on Integrity servers

Technical white paper

Table of contents

Executive summary ............................................................................................................................... 3

Introduction ......................................................................................................................................... 4 Recommended test platform and backup strategies............................................................................... 6 Project test environment .................................................................................................................... 6 Recommended migration path ........................................................................................................... 7

Conventions ........................................................................................................................................ 8

Prerequisites ........................................................................................................................................ 9

Migration project test platform ............................................................................................................. 10

Preliminary phase .............................................................................................................................. 11

Migration prerequisites ....................................................................................................................... 13

Phase 1: Upgrading the source RDBMS to 10gR2 ................................................................................. 15 1.1 Prepare the source database server for 10gR2 upgrade ............................................................... 16 1.2 Install RDBMS 10gR2 on the source database server .................................................................... 17 1.3 Upgrade Applications database to 10gR2 .................................................................................. 20

Phase 2: Migrating Oracle Applications 11i database to HP Integrity server ............................................ 28 Constraints of using XTTS ................................................................................................................ 28 2.1 Prepare the source database node ............................................................................................. 29 2.2 Prepare the target database node .............................................................................................. 31 2.3 Export the source Applications 11i database objects .................................................................... 36 2.4 Import the Applications 11i database objects to the target database node ...................................... 39 2.5 Upgrade the target Applications 11i database instance................................................................ 41

Phase 3: Migrating to E-Business Suite Release 12.1.1 ........................................................................... 47 3.1 Prepare source for E-Business Suite Release 12.1.1 upgrade ......................................................... 47 3.2 Upgrade to E-Business Suite Release 12.1.1 ................................................................................ 50 3.3 Perform post upgrade product specific tasks ................................................................................ 51

Phase 4: Upgrade E-Business Suite R12.1.1 to Release 12.1.2 ............................................................... 52 4.1 Pre-requisite checks .................................................................................................................. 52 4.2 Applying the Release Update Pack ............................................................................................. 53 4.3 Apply Post-Release Update Patch ............................................................................................... 53 4.4 Post-update steps ...................................................................................................................... 53

Phase 5: Upgrade E-Business Suite RDBMS from 10gR2 to 11gR2 ........................................................... 55 5.1 Prepare the database server for 11gR2 upgrade ......................................................................... 55 5.2 Install Oracle RDBMS 11gR2 ..................................................................................................... 56

5.3 Upgrade E-Business Suite RDBMS to 11gR2 ................................................................................ 59

Appendix A: Kernel parameters .......................................................................................................... 66

Appendix B: Pre-Upgrade Information Utility output file .......................................................................... 67

Appendix C: Post-Upgrade Information Utility output file ......................................................................... 72

Appendix D: XTTS example files .......................................................................................................... 74

Appendix E: Oracle E-Business Suite R12 Upgrade Report (TUMS) – VIS .................................................. 82

Appendix F: Recommended Oracle Support Portal documents ................................................................ 83

Appendix G: Validate the E-Business Suite environment .......................................................................... 84

For more information .......................................................................................................................... 86

3

Executive summary

Oracle Applications Release 11i is widely deployed across a broad range of HP server platforms: HP

AlphaServer systems running Tru64 UNIX®, HP 9000 servers running HP-UX and HP ProLiant servers

running Linux or Microsoft® Windows®. Customers on those and other vendor platforms are faced

with the impending obsolescence of Oracle Applications Release 11i and/or the operating system

hardware combinations on which they are deployed. The decisions facing these customers relate to

how to migrate their Oracle Applications Release 11i environments to a new platform, and whether to

upgrade to Oracle E-Business Suite Release 12.1 at the same time.

Oracle E-Business Suite Release 12.1 is certified on several new platforms including HP Integrity

servers running HP-UX 11i v3 for both application and database tiers. Also, HP Integrity servers

running Linux and Windows are fully certified as the database-only platform for both Oracle

Applications Release 11i and Oracle E-Business Suite Release 12.1(known as “Split Configuration

Database Tier” in Release 11i and "Mixed Platform Architecture" in Release 12.1).

This document is a guide for Oracle Applications Release 11i customers looking to perform platform

migration from HP AlphaServer systems running Tru64 UNIX to HP Integrity servers running HP-UX 11i

v3 and upgrade their Oracle Applications Release 11i environment to Oracle E-Business Suite

Release 12.1. The procedures captured within this document are extracted from various Oracle notes

and guides, and includes additional steps required for customers running HP AlphaServer systems to

complete the migration. This document can also be used as an outline to migrate other vendor

platforms to HP Integrity servers.

The procedures within this document are common amongst Oracle Applications Release 11i

environments. However, Oracle Applications is comprised of over 200 business software products,

such as Financials, Manufacturing, Human Resources, and so on. Each product will have its own

specific upgrade tasks that will not be covered within this document. HP recommends that the local

experts study the document Oracle E-Business Suite Upgrade Guide: Release 11i to Release 12.1.1

(Part# E14010-01) in order to determine the proper migration plan for each business software

product.

Target audience: The intended audience for this document is IT professionals who deploy and support

Oracle E-Business Suite on HP platform. In-depth familiarity with Oracle Database and Oracle E-

Business Suite is required.

DISCLAIMER OF WARRANTY

This document may contain the following HP or other software: XML, CLI statements, scripts,

parameter files. These are provided as a courtesy, free of charge, “AS-IS” by Hewlett-Packard

Company (“HP”). HP shall have no obligation to maintain or support this software. HP MAKES NO

EXPRESS OR IMPLIED WARRANTY OF ANY KIND REGARDING THIS SOFTWARE INCLUDING ANY

WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE OR NON-

INFRINGEMENT. HP SHALL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL OR

CONSEQUENTIAL DAMAGES, WHETHER BASED ON CONTRACT, TORT OR ANY OTHER LEGAL

THEORY, IN CONNECTION WITH OR ARISING OUT OF THE FURNISHING, PERFORMANCE OR

USE OF THIS SOFTWARE.

4

Introduction

Oracle E-Business Suite (EBS) is Oracle‟s original Enterprise Resource Planning (ERP) application and

incorporates over 200 product-specific business applications. ERP, in this case, is a term referring to a

set of applications connected by a single database (DB) that serves some or all of the business

processes within an organization. Oracle E-Business Suite includes an application tier that contains all

the business logic for the various business processes and a database tier that stores all the business-

critical data.

E-Business Suite deployments generally require a unique plan for each environment to successfully

migrate the data, application customizations, and product-specific functionality to the target platform.

This document does not cover the procedures for patching, migrating customizations, performing

product-specific tasks, functional testing, add-on software, or other languages support. The focus is

strictly platform migration and the upgrade of the Oracle E-Business Suite technology stack.

Note:

Oracle Applications Release 11i customization coding uses Developer 6i

Forms & Reports and OA Framework (BC4j Java Container) using

JDeveloper9i/10g. Most of the core functionality in Release 11i utilized

Developer 6i Forms & Reports. But, E-Business Suite Release 12.1 uses

Developer 10g Forms & Reports and OA Framework (OC4J Java

Container). Also, a lot of core functionality in Release 12.1 has been

moved from Forms & Reports to OA Framework web pages i.e. a functional

flow which used to be executed in Forms in Release 11i now utilized OA

Framework web pages for the same in Release 12.1.

Due to aforementioned technology stack differences in Oracle E-Business

Suite Release 11i & 12.1, it is not possible to automatically upgrade

Release 11i customization to the new Release 12.1. Developers may need

to recompile Forms & Reports customization and rebuilt OA Framework

extension while migrating to Release 12.1. There are Oracle notes to help

in doing the same, e.g.

563258.1 - How to Upgrade 11i Custom Forms to R12

451934.1 - Accessing Custom Forms After Upgrading From To R12

780989.1 - R12: Upgrade vs. Reimplementation (Financials)

1292611.1 - Upgrading Form Personalizations and OA Framework

Personalizations from Oracle E-Business Suite Release 11i to 12.1

In a technological white paper like this, it is not possible to cover the

customization and extensions as it varies from customer to customer.

Depending on the release of Oracle Applications 11i, the platform migration and application

upgrade may require a preliminary phase. The preliminary phase consists of upgrading to the

recommended 11.5.10.2 release. This phase is required for all Oracle Applications 11i environments

running 11.5.8 and earlier. Customers running Oracle Applications Release 11.5.9 (base, CU1) and

11.5.10 (base, CU1) are not required to upgrade to 11.5.10.2 release if they are willing to perform

all the platform migration and application upgrade phases in a single downtime window. Only

Oracle Applications 11.5.9 (CU2) and 11.5.10 (CU2) versions support the split-configuration

deployment that allows for pausing between the phases described in this document.

For this particular project, the source configuration used Oracle Applications 11i Release 11.5.10

(CU2), which did not require a preliminary phase. At the end of each phase of the migration the E-

Business Suite environment will be in a fully supported configuration. This migration strategy allows

for the migration to be paused between phases in order to resume normal operation until continuing

onto the next phase. The platform migration and application upgrade consist of three main phases

and two optional phases.

5

Phase 1: Upgrading the source RDBMS to 10gR2

Phase 1 consists of upgrading the source Oracle Applications 11i database instance to 10gR2

(Version 10.2.04). Customers who have already upgraded to RDBMS 10.2.0.3 or above may skip

this phase and move on to Phase 2.

Phase 2: Migrate Oracle Applications Release 11i database

Phase 2 consists of creating a split configuration database tier in Oracle Applications Release 11i by

performing a platform migration of the source Oracle Applications Release 11i database instance

from the HP AlphaServer systems running Tru64 UNIX to the HP Integrity server. At the end of this

phase, the Oracle Applications 11i environment will be in a fully supported split configuration where

the Oracle Applications 11i application tier components are running on the HP AlphaServer systems

and the database tier components are running on the HP Integrity server.

This document explains & utilizes Cross-Platform Transportable Tablespace (XTTS) migration

process of the source Applications 11i database to target Integrity HP server. For more details review

Oracle Support Portal document: Cross Platform Transportable Tablespaces on 11i with 10gR2 [ID

454574.1].

You can also use alternative migration option such as export and import of the source Applications

11i database as explained in Oracle Support Portal document: 10g Release 2 Export/Import process

for Oracle Applications Release 11i [ID 362205.1].

Oracle Split configuration database tier also supports Linux, Microsoft Windows, Tru64 UNIX, Oracle

Solaris, or IBM AIX as the application tier platform and most of the RDBMS supported platforms. For

more details on supported Oracle Applications 11i Split Configuration database tier, review the

„Certifications‟ page on the Oracle Support Portal website. For more details review Oracle Support

Portal document Using Oracle Applications with a Split Configuration Database Tier on Oracle 10g

Release 2 [ID 369693.1] and Using Oracle EBS with a Split Configuration Database Tier on 11gR2

[ID 946413.1].

Phase 3: Upgrade Oracle E-Business Suite to Release 12.1.1

Phase 3 consists of preparing the Oracle Applications Release 11i database for E-Business Suite

Release 12.1.1, installing a new Oracle E-Business Suite Release 12.1.1 home on the target HP

Integrity server, applying Release 12.1.1 upgrade patch and executing rest of the R12.1.1 upgrade

steps.

At this stage, you can continue to use Release 12.1.1 with RDBMS 10gR2.

Also, you can optionally upgrade to Oracle E-Business Suite Release 12.1.2 and Oracle RDBMS

11gR2 by following two optional phases:

Phase 4: Upgrade Oracle E-Business Suite to Release 12.1.2

This phase consists of patch application on top of Oracle E-Business Suite R12.1.1 to upgrade it to

Release 12.1.2

Phase 5: Upgrade Oracle E-Business Suite database to Oracle RDBMS 11gR2

This phase consists of upgrading the Oracle E-Business Suite database to Oracle RDBMS 11gR2.

Note

Oracle RDBMS 11gR2 Patch set 11.2.0.1 is now supported with Oracle E-

Business Suite Release 12.1 and HP Integrity servers. Premier Support for

10gR2 Database officially ended in July 2010. For that reason, HP

recommends upgrading to 11gR2 as part of the EBS migration process.

6

These additional phases (4 and 5) are independent of each other. In this document we have first

upgraded the database from 10gR2 to 11gR2 and then upgraded Oracle E-Business Suite from

R12.1.1 to R12.1.2.

At the end of each phase, the E-Business Suite environment will be in a fully supported configuration.

This migration strategy allows customers to pause the migration/upgrade process between phases in

order to resume normal operation and minimize disruption of the business processes.

Recommended test platform and backup strategies

Each phase will require some downtime. The length of downtime will depend on the system

configuration and database size. Plan the testing of all phases on a suitable test environment to get a

fair estimate of downtimes required for each phase. Such testing should use a recent clone with the

same patch level as the production environment to yield an accurate estimate of downtimes. The test

executions also provide the opportunity to document any additional steps or patches required for

each phase of your migration/upgrade.

It is strongly recommended to perform a complete backup of the E-Business Suite environment before

and after each phase. These backups will minimize the risk of business disruption by enabling a quick

rollback to a working configuration should an unexpected failure occur.

Project test environment

The test environment used to develop this white paper comprised of two HP AlphaServer systems

running Tru64 UNIX as the source platform for the Oracle Applications Release 11.5.10.2

environment and two HP Integrity servers running HP-UX 11i v3 for the target Oracle E-Business Suite

Release 12.1 environment. Oracle E-Business Suite two-node installation has been used i.e. one for

application tier and other for database tier. Only the base components for E-Business Suite and the

Vision Demo database were installed, excluding any Oracle add-on software, third-party products,

and foreign languages.

7

Recommended migration path

The following figure outlines the approach to the migration/upgrade process.

Figure 1. Recommended Migration path

Phase III

Perform Pre-Upgrade product specific tasks and apply R12.1

Upgrade Patch

Source

Apps-tier HP

Alpha Server

TRU64 UNIX

Source

DB-tier HP

Alpha Server

TRU64 UNIX

Phase III Phase III Phase III

Pre-Upgrade Install R12.1 Apply EBS R12.1

Tasks Techstack Upgrade Patch

Oracle

Applications

11.5.10.2

Tech Stack

RDBMS

9.2.0.6

Applications 11i

DB

Phase I

Upgrade Database

10.2.0.4

Oracle

Applications

11.5.10.2

Tech Stack

RDBMS

10.2.0.4

Applications 11i

DB

Phase II

Migrate Applications

11i Database

Oracle

Applications

11.5.10.2

Tech Stack

RDBMS

10.2.0.4

Applications 11i

DB

Oracle

Applications

11.5.10.2

Tech Stack

Retired

RDBMS

10.2.0.4

Retired

Oracle

Applications

11.5.10.2

Tech Stack

RDBMS

10.2.0.4

Software only

RDBMS

10.2.0.4

Applications 11i

DB

Phase II

Migrate Applications

11i Database

RDBMS

10.2.0.4

Applications 11i

DB

RDBMS

10.2.0.4

Applications 11i

DB

EBS

Release

12.1

Applications

Tech Stack

RDBMS

10.2.0.4

EBS Release

12.1 DB

EBS

Release

12.1

Applications

Tech Stack

Source

Applications

11i

Environment

Target

Apps- tier HP-UX

Integrity

Target

DB- tier HP-UX

Integrity

Target EBS R12.1

Environment

8

Conventions

Table 1. Conventions and meaning

Convention Meaning

Software staging area Generally located on an NFS server consisting of Oracle and HP installation software

and patches for the migration.

Source application tier HP AlphaServer systems running Tru64 UNIX consisting of the Oracle Applications

Release 11i home, applications technology stack, and the admin, concurrent

processing, forms, report, and web server services.

Source database tier HP AlphaServer systems running Tru64 UNIX consisting of the RDBMS 9iR2 and

10gR2 ORACLE_HOMEs and the Applications 11i Database

Source ORACLE_HOMEs <10g_ORACLE_HOME>10gR2 home, <9i_ORACLE_HOME> 9iR2 home

Applications iAS home, Applications 8.0.6 home

Source APPL_TOP Applications 11i home

Target application tier HP-UX Integrity server consisting of the E-Business Suite Release 12.1, home,

applications technology stack, and the admin, concurrent processing, forms, report,

and web server services.

Target database tier HP-UX Integrity server consisting of the RDBMS 10gR2_ORACLE_HOME,

11gR2_ORACLE_HOME and the Applications R12.1 Database

Target ORACLE_HOMEs RDBMS 10gR2 home, 11gR2 home

Applications 10.1.3 .4 AS home (Web or Java ORACLE_HOME, Apache 1.3 and

OC4J ) Applications Developer 10.1.2.3 home (Tools, C, or Dev ORACLE_HOME,

Forms 10 and Reports 10)

Target APPL_TOP E-Business Suite Release 12.1 home

APPLMGR User who owns the Applications file systems.

Source APPLMGR environment file: <APPL_TOP>/APPS<SID>_<hostname>.env

ORACLE User who owns the database file systems.

Source ORACLE environment file: <ORACLE_HOME>/<SID>_<hostname>.env

ORACLE_SID <SID> Database Site Identifier

adadmin Application DBA administration utility

adpatch Application DBA patching utility

adconfig.sh Application DBA configuration utilities (AutoConfig)

opatch RDBMS DBA patching utility

rapidwiz Oracle Rapid Install Wizard for E-Business Suite

runInstaller Oracle Install Wizard for RDBMS

Monospace Text Represents command line text

< > Text enclosed in angle brackets represents a variable

# Preceding # on a command line text represents ROOT level access

$ Preceding $ on a command line text represents ORACLE or APPLMGR user access

9

Prerequisites

Prior to beginning the platform migration the following software versions should be considered the

minimum operating version levels.

Table 2. Minimum operating version levels

Source software Minimum version Location Details

Tru64Unix 5.1b

source DB-Tier

source APPS-Tier

HP AlphaServer systems

running Tru64 UNIX

Applications release

Applications Release

11.5.10.2

Includes

RDBMS 9iR2

source APPS-Tier

source DB-Tier


running Tru64 UNIX


running Tru64 UNIX

Database release RDBMS 9iR2

RDBMS 10gR2

source DB-Tier HP AlphaServer systems

running Tru64 UNIX

Target software Minimum version Location Details

HP-UX

11i v3

target DB-Tier

target APPS-Tier

HP Integrity server

(HP-UX on Intel® Itanium®)

Unzip for

HP-UX 11i v3

5.1.x

target DB-Tier

HP-UX on Intel Itanium

Applications release

E-Business Suite

Release 12.1.1

target APPS-Tier HP-UX on Intel Itanium

Database release RDBMS 10gR2

RDBMS 11gR2

target DB-Tier HP-UX on Intel Itanium

The following operating system patches should be applied.

Table 3. Operating system patches

OS patches Patch number Location Details

Tru64Unix

(Source)

n/a application Tier

database Tier

5.1b

HP-UX 11i v3

(Target)

n/a applications Tier

database Tier

Quality Pack, September

2010

10

Migration project test platform

All the steps recorded in this migration document are specific to this test platform. The migration

document was developed using the following configuration.

Source APPS server:


Tru64 UNIX 5.1B

Oracle E-Business Suite 11.5.10.2

Source DB server:


Tru64 UNIX 5.1B

Oracle RDBMS 9.2.0.6

Oracle RDBMS 10gR2

Target APPS server:

HP Integrity

HP-UX 11i v3

Oracle E-Business Suite Release 12.1

Target DB server:

HP Integrity

HP-UX 11i v3

Oracle RDBMS 10gR2

Oracle RDBMS 11gR2

The source application and database components for Oracle Applications Release 11.5.10.2 were

installed in a two-node architecture using the Vision Demo database. A two-node installation consists

of application tier (application file system, technology stack, admin, concurrent processing, forms,

report, and web server) and database tier (RDBMS file system and Applications 11i database)

installed on two different servers. The Vision Demo database is a sample database used to simulate a

medium-size company using some of the more popular E-Business Suite software components.

Oracle RDBMS 10gR2 was also installed on the source DB server in a different ORACLE_HOME for

the Applications 11i Vision Demo database 10gR2 upgrade.

The target DB server was installed with Oracle RDBMS 10gR2 and prepared for Applications 11i

Vision Demo database platform migration.

The target APPS server was prepared for the installation of E-Business Suite Release 12.1.1 home.

11

Preliminary phase

Upgrading to Oracle Applications Release 11.5.10.2 or, at a minimum, 11.5.9(CU2) before

beginning the migration process is highly recommended in order to take advantage of the phased

migration approach.

Customers who need to continue operating the deployment at some intermediate point – for example

after the initial database upgrade to 10gR2 – should consider upgrading to 11.5.10.2 before

beginning the migration. For more information, refer to Oracle Support Portal document: Oracle

Applications Release 11.5.10.2 Maintenance Pack Installation Instructions [ID 316365.1]

Deployments of 11.5.8 and earlier must upgrade to 11.5.10.2 prior to beginning the migration

process described in this document. For more information, refer Upgrading Oracle Applications

Release 11i (11.5.10.2), Part Number B19297-01.

Oracle E-Business Suite Release 12.1 uses Oracle E-Business Suite Tablespace model (OATM), which

is based on database object type rather than product affiliation. OATM uses 12 locally managed

tablespaces for all products, including the temporary tablespace, system tablespace, and system-

managed undo (SMU) tablespace. Release 11.5.9 and 11.5.10 support this tablespace model while

earlier releases will need to migrate to this model to take full advantage of the Release 12.1 features.

For further details see Oracle Support Portal document: Oracle Applications Tablespace Model

Release 11i - Tablespace Migration Utility [ID 248857.1]

12

The following figure shows the process migration flow.

Figure 2. Process migration flow

Source

EBS 11.5.8

And earlier

Preliminary Phase

Upgrade in Place

EBS 11.5.10.2 CU2

RDBMS 9.2.0.6

Tasks:

· Upgrade RDBMS to

9.2.0.6

· Apply 11.5.10.2 CU2

Maintenance pack

Perform

Phases I Through III

Of the migration/Upgrade

Source EBS

11.5.9(base, CU1)

11.5.10(base, CU1)Preliminary Phase

Upgrade in Place

EBS 11.5.10.2 CU2

RDBMS 9.2.0.6

Tasks:

· Upgrade RDBMS to

9.2.0.6

· Apply 11.5.10.2 CU2

Maintenance pack

Perform

Phases I Through III

Of the migration/Upgrade

Perform

All phases of the

Migration/Upgrade

Note: Only after completing all phases can the EBS environment be brought

on-line in a fully supported state

OR

13

Migration prerequisites

Oracle E-Business Suite is highly configurable and customizable with many customers deploying their

own unique environments. For this reason, HP strongly recommends that all migration tasks described

in this document be applied first to a test environment in order to determine application downtime and

record any additional steps that may be necessary for proper migration of add-on software‟s,

languages, and customizations. Most customers will run through the migration process a number of

times on their test environments before finally implementing it in the production environment. Also,

additional storage and CPU resources may be required during the migration process, to reduce

resource bottlenecks and expedite the effort. It is also recommended to perform a full backup of the

entire environment before starting and ending each phase of the migration.

The test source platform included Oracle Applications 11.5.10.2, Developer 6i Patch Set 16 and

AutoConfig 11i.AD.I.2. The following application patch list includes the patches required before

starting the migration. For more information, refer to Oracle Support Portal document: Oracle

Applications Release 11i with Oracle 10g Release 2 (10.2.0) [ID 362203.1]

The Applications 11i patches in the following table were applied to the application tier in the order

listed. Additional patches may be required for third-party products and other E-Business Suite software

modules not included with the base installation. National language support (NLS) will also require

additional patches.

Note

This document was written in September of 2010 and all of the following

patches named in this document were available at that time. Always

confirm patch list with the latest Oracle Support Portal documents and

follow the patch readme instructions unless otherwise directed.

There may be some advantages to applying a superseded patch or patch

set that better supports your current environment. Oftentimes, a superseded

patch or patch set will contain many other patches, which may produce

unexpected results. Pay close attention to possible dependent patches and

note any additional steps not covered in the guide.

14

Table 4. Application patches

Application patches Patch number Details

Dev6i Patch

Additional Dev6i Patches

Interoperability patch

4948577

5713544

4261542

5216496

5753922

6195758

4888294

Developer 6i Patch Set 18

Oracle Support Portal document: 125767.1

One-off patches for Developer 6i Patch Set 18

EBS Interoperability patch for Developer 6i Patch Set 18

Dependent patch

Dependent patch

Note: The latest Applications DBA

Minipack 11i.AD.I.7 and TXK Rollup

Patch includes dependent patches

listed in the readme notes for the

10gR2 Interoperability patch.

Interoperability patch

8217898

4653225

4653225

TXK AUTOCONFIG AND TEMPLATES ROLLUP PATCH T

Applications DBA Minipack Patch 11I.AD.I.7

10gR2 APPS INTEROPERABILITY PATCH

Before starting the migration, record any invalid objects in the 9iR2 database. Re-check the database

for invalid objects before and after each phase or milestone.

Logon as the owner of the 9i database instance and source the environment file.

Connect to the 9i database using SQL*Plus with SYSDBA privileges to check for any invalid objects. If

any invalid objects are found, use ADADMIN to remove as many as possible before continuing.

$ sqlplus '/ as sysdba'

SQL> SELECT count(*) FROM dba_objects WHERE status='INVALID';

SQL> SELECT owner,object_name,object_type FROM dba_objects WHERE

status=’INVALID’;

Note

You can expect some additional invalid database objects to be generated

during the migration process, although it is possible that the steps

conducted during the migration may repair or otherwise eliminate some

object corruption.

15

Phase 1: Upgrading the source RDBMS to 10gR2

The source environment consists of HP AlphaServer systems running Tru64 UNIX with Oracle

Applications Release 11.5.10.2 and the Vision Demo database instance based on Oracle RDBMS

9.2.0.6. Phase 1 will upgrade the database instance to Oracle RDBMS 10gR2 by first installing a

new 10gR2_ORACLE_HOME, and then upgrade the Applications 11i database instance using the

Database Upgrade Assistant (DBUA). Before proceeding, determine if your particular environment

requires any additional steps by thoroughly reading both the Oracle Database Installation Guide 10g

Release 2 (10.2) for HP Tru64 UNIX Part Number B25300-01 and Oracle Support Document: Oracle

Applications Release 11i with Oracle 10g Release 2 (10.2.0) [ID 362203.1]

Note

Oracle Applications Release 11i now supports Oracle RDBMS 10.2.0.4 for

HP AlphaServer systems running Tru64 UNIX. Upgrading now to 10.2.0.4

will reduce the need to upgrade at a later date.

Oracle Database release 10.2.0.3 is the minimum RDBMS release

supported by Oracle E-Business Suite Release 12.1.1. An upgrade of

Oracle Applications Release 11i to Oracle E-Business Suite Release 12.1.1

with database versions from 10.2.0.3 to 11.2.0.1 is currently supported.

If your company has already upgraded the Applications 11i database to

10g R2 10.2.0.3 or later and you do not want to upgrade to 10.2.0.4,

then you can proceed directly to Phase 2: Migrating Applications 11i

database to HP-UX 11i v3 on Integrity server.

During this upgrade phase of the migration, you will:

· Section 1: Prepare the source database server for 10gR2 upgrade

· Section 2: Install RDBMS 10gR2 on source database server

· Section 3: Upgrade Applications 11i database to 10gR2 on source database server

Section 2 does not depend on section 1 and can be performed first or simultaneously.

Figure 3. Upgrade source RDBMS 9.2.0.6 to 10gR2

Source

Tru64 5.1b

EBS 11.5.10.2

RDBMS 9.2.0.6

Phase I

Upgrade RDBMS 9.2.0.6 to 10.2.0.4

Section 1:

Prepare DB Node

to Upgrade

· Full Backup

· Update

Software to

required level

· Apply 10gR2

Introp patch

Section 2:

Installing 10.2.0.4

· Install RDBMS

10.2.0.2 in new

10g Oracle

home

· Apply RDBMS

10.2.0.4

patchset

Section 3:

Upgrade 11i applications

database

· Perform DBUA

(Database Upgrade

assistant)

· Migrate Autoconfig

· Validation tests

Phase II

Migrating

Applications 11i

database to HP

Integrity server

Phase III

Upgrade to

Release 12.1.1

on HP Integrity

server

Once all the tasks have been completed in phase 1, the E-Business Suite 11i environment will be in a

fully supported mode with the upgraded 10gR2 database. At this time, the migration can be paused

to resume normal operations or if time permits, continue on with Phase 2: Migrating Oracle

Applications 11i database to HP-UX Integrity server.

16

1.1 Prepare the source database server for 10gR2 upgrade

This section includes the tasks to prepare the source database server for the upgrade to RDBMS

10gR2.

Download and stage the Oracle RDBMS 10gR2 (Version 10.2.0.2) and Example CD installation

media for HP AlphaServer systems running Tru64 UNIX from Oracle‟s software download website,

http://www.oracle.com/technology/software/index.html.

Also, download and stage the Oracle RDBMS 10gR2 patch set 6810189 10.2.0.4.0 for Oracle

database server on HP AlphaServer systems running Tru64 UNIX from Oracle Support Portal.

The following steps were derived from Oracle Support Document: Oracle Applications Release 11i

with Oracle 10g Release 2 (10.2.0) [ID 362203.1], along with some additional steps to complete

the upgrade.

1.1.1 Backup the Oracle Applications 11i environment

For rollback purposes, shutdown the Oracle Applications 11i environment and take a full cold backup

of both the application tier and database tier.

1.1.2 Oracle Portal 3.0.9 check (conditional)

If you are using and planning to continue to use Oracle Portal 3.0.9 in your current Oracle

Applications 11i environment, then the existing Oracle Portal functionality must be migrated to Oracle

Portal 10g to ensure compatibility with Oracle Database 10gR2. Review the Oracle Support Portal

document: Installing Oracle Application Server 10g with Oracle E-Business Suite Release 11i [ID

233436.1]. Oracle Portal 3.0.9 should be removed only after the installation of Oracle Portal 10g.

If you are not planning to use Oracle Portal 3.0.9 in future then you can remove Oracle Portal 3.0.9

and any dependencies from Oracle Applications 11i by performing the steps in Oracle Support Portal

document: Remove Oracle Portal 3.0.9 from E-Business Suite 11i [ID 312349.1].

1.1.3 Deregister the existing database server (conditional)

If you are planning to use a new database port, host, SID, or database name parameters on the

database server, then you must also update AutoConfig setup on the database tier and deregister the

existing database server node.

1.1.4 Update applications tier context file

In this phase of the migration, the hostname, SID, and port addresses will remain the same for the

database tier. The only change needed at this time will be to update the variable

s_apps_jdbc_connect_descriptor to a NULL value in the applications context file.

It is recommended that a backup of the context file be made before making any changes. An

improper value could render the applications inaccessible.

$ cp $APPL_TOP/admin/<SID>_<hostname>.xml \

$APPL_TOP/admin/<SID>_<hostname>.xml.orig

It is recommended to use Oracle Applications Manager (OAM) to edit the context file.

To use OAM to modify the context file.

• From your browser link to the E-Business Suite Web server port

(Default http://APPS_NODE.DOMAIN_NAME:8000).

• Login OAM as “sysadmin”

• Click on “Site Map” link

http://www.oracle.com/technology/software/index.html

17

• Click on “AutoConfig” link

• Click on the Edit Parameters icon for Applications Tier

• Under the Search pull down menu, select OA_VAR

• In the next field enter “s_apps_jdbc_connect_descriptor”

• Click on the GO button

• Update the value to NULL

• Click on the SAVE button

• Enter a comment if necessary

In order for this value to take effect, you will have to shut down the APPS-Tier server services, run

AutoConfig and then restart the APPS-Tier server services.

$COMMON_TOP/admin/scripts/<SID>_<HOSTNAME>/adstpall.sh apps/<apps_password>

$AD_TOP/bin/adconfig.sh contextfile=<APPL_TOP>/admin/<SID>_<hostname>.xml

$ $COMMON_TOP/admin/scripts/<SID>_<HOSTNAME>/adstrtall.sh apps/<apps_password>

1.2 Install RDBMS 10gR2 on the source database server

This section includes the steps to install the software-only version of the Oracle RDBMS 10gR2 on the

source HP AlphaServer systems running Tru64 UNIX.

1.2.1 Preparation to create the 10.2.0.2 Oracle home

To understand the installation and upgrade processes, read Chapters 1 and 2 of the Oracle

Database Installation Guide 10g Release 2 (10.2) for HP Tru64 UNIX Part Number B25300-01 and

the "System Considerations and Requirements" section of Chapter 3 of the Oracle Database Upgrade

Guide 10g Release 2 (10.2) Part Number B14238-02. Execute any additional steps that are relevant

for your environment.

1.2.2 Install the base 10.2.0 software

Start up an Xterm session on the source database server as the “oracle” user, change directory to the

10.2.0.2 installation media staging area, and run the Oracle Universal Installer (OUI).

DO NOT source the 9i database environment file.

$ cd <10.2.0.2_staging_directory>

$ ./runInstaller

Select Installation Type

Enterprise Edition

Specify Home Details

Name: OUIHome2

Path: <10gR2_ORACLE_HOME>

Product-specific prerequisite checks

The warning status for the OS and kernel patches can be ignored if running the

prescribed software releases and kernel settings.

Many of the required patches, as well as some kernel settings have been superseded

or discontinued.

Upgrade an Existing Database

NO

18

Select Configuration Option

Install database software only

Execute Configuration scripts Popup

As root user run the following script: # <10gR2_ORACLE_HOME>/root.sh

End of Installation

1.2.3 Install Oracle Database 10gR2 Products from the 10g Companion CD

On the database server node, as the owner of the Oracle RDBMS file system, execute the tasks in

section 3.5, "Installing Oracle Database 10g Products" in the Oracle Database Companion CD

Installation Guide for your platform. Do not perform the tasks in the "Preparing Oracle Workflow

Server for the Oracle Workflow Middle Tier Installation" section.

In the Installation Types window, use the Product Languages button to select any languages other than

American English that are used by your Applications database instance.


10.2.0.2 Example CD staging area and run the Oracle Universal Installer.

Make sure that:

· You DO NOT source the 9i database environment file.

· The ORACLE_HOME environment variable points to the new 10.2.0 Oracle home.

· The PATH environment variable includes $ORACLE_HOME/bin and the directory where the new

Perl executable is located (usually $ORACLE_HOME/perl/bin).

· The LD_LIBRARY_PATH environment variable includes $ORACLE_HOME/lib.

· The PERL5LIB environment variable points to the directories where the new Perl libraries are located

(usually $ORACLE_HOME/perl/lib/<perl version> and $ORACLE_HOME/perl/lib/site_perl/<perl

version>).

Set the following environment variables and run the install wizard to install the 10gR2 database

software:

$ export ORACLE_HOME=/oracle/<sid>db/10.2.0

$ export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/perl/bin:$PATH:.

$ export LD_LIBRARY_PATH=$ORACLE_HOME/lib

$ export PERL5LIB=$ORACLE_HOME/perl/lib/5.8.3 \

:$ORACLE_HOME/perl/lib/site_perl/5.8.3

$ cd <10.2.0 Example CD staging_directory>

$ ./runInstaller

1.2.4 Execute 10.2.0.4 patch set pre-installation tasks

On the database server node, as the owner of the Oracle 10g file system, extract the 10.2.0.4 patch

set file. Read the patch set notes in README.html. Understand the upgrade, patch set installation

process and any "Preinstallation Tasks" before starting the patch set installation.

1.2.5 Execute 10.2.0.4 patch set installation tasks


10.2.0.4 patch set staging area and run the Oracle Universal Installer.

19

Make sure that:








version>).


software:






$ cd <10.2.0.4 patch set staging_directory>

$ ./runInstaller

1.2.6 Create nls/data/9idata directory

As the owner of the 10gR2 RDBMS file system, set the ORACLE_HOME variable and run the

cr9idata.pl Perl script; then set the ORA_NLS10 environment variable.

$ export ORACLE_HOME=<10gR2_ORACLE_HOME>





$ cd $ORACLE_HOME/nls/data/old

$ perl cr9idata.pl

$ export ORA_NLS10=$ORACLE_HOME/nls/data/9idata

1.2.7 Apply additional RDBMS One-off patches

Shutdown the Applications server services, database and listener before applying the following

platform specific RDBMS One-off patches. Also apply Patch 6880880 OPatch 10.2.0 before

applying these additional RDBMS patches.

6521934 Oracle 10.2.0.4 (HP Tru64 UNIX)



Run opatch lsinventory before and after applying patches. Review all the readme files before applying

any patch and review the logs for any discrepancy after applying each patch. If any are found,

resolve them first before continuing to the next step.

1.2.8 Install the latest available critical patch update and any required patches

Once you have installed the major Oracle Database 10g software, check to see if there is a critical

patch update that needs to be installed. The latest critical patch update for Oracle Database 10g

Release 2 should be installed prior to upgrading your databases. Refer to the specific critical patch

update documentation for installation information.

20

1.3 Upgrade Applications database to 10gR2

This section includes the tasks to upgrade the Oracle Applications Release 11i applications database

from 9.2.0.6 to 10gR2. During this process, the environment will be unavailable until the upgrade

has completed.

1.3.1 Preparation before Applications database upgrade

Review Chapter 2 of Oracle Database Upgrade Guide 10g Release 2 (10.2) Part Number B14238-

02 and Oracle Support Document: Oracle Applications Release 11i with Oracle 10g Release 2

(10.2.0) [ID 362203.1], to prepare for the upgrade.

Make sure that you unset the TNS_ADMIN environment variable and if event="38004 trace name

context forever, level 1" is defined in either the init<SID>.ora initialization parameter file or the

spfile<SID>.ora server parameter file, remove it.

1.3.2 Shut down the applications server processes and the database listener

Shut down applications server services on the application node:

# su – applmgr

$ cd $COMMON_TOP/admin/scripts/<SID>_<HOSTNAME>

$ ./adstpall.sh apps/<apps_password>

Shut down database listener on the database node.

# su – oracle

$ lsnrctl stop <SID>

1.3.3 Prepare for upgrading the database instance

The following steps were derived from the Oracle Database Upgrade Guide 10g Release 2 (10.2)

Part Number B14238-02, Chapters 3 and 4.

· Oracle recommends that you use 500MB as the SYSAUX tablespace size and set autoextend on the

SYSAUX tablespace.

· When upgrading all statistics tables, note that Oracle Applications has only one statistics table,

APPLSYS.FND_STATTAB, that needs to be upgraded.

· If you plan to change the PL/SQL compilation mode, disable the compilation of objects.

· Verify that the /etc/oratab file has correct entries for the 9i Database and 9i Oracle Home.

# cat /etc/oratab

<SID>:<9i_ORACLE_HOME>:N:

Run the pre-upgrade information tool using the following steps:

· Logon as the owner of the 9i_RDBMS file system and source the environment.

· Copy and run the utlu111i.sql from <upg_10204_log_directory>.

$ cp <10gR2_ORACLE_HOME>/rdbms/admin/utlu102i.sql \

<upg_1024_log_directory>

· Execute the utlu102i.sql by connecting to 9i Database using SQL*Plus with SYSDBA privileges.

Spool the output of this execution into utlu102i.out.

$ cd <upg_1024_log_directory>


SQL> spool utlu102i.out

SQL> @utlu102i.sql

SQL> spool off

21

· Review the output for any errors or warnings and make any necessary changes before proceeding

on to the next step. For further details, see Oracle Support Document: How to Download and Run

Oracle's Database Pre-Upgrade Utility [ID 884522.1].

See Appendix B for the pre-upgrade information tool output file generated by this project and the

steps performed to resolve the warnings identified by the tool.

1.3.4 Upgrade the Applications 11i database

Make sure that the Applications server processes and the 9i database listener are shut down. Set the

environment variable ORACLE_HOME to point to the 10gR2_ORACLE_HOME directory created in

the previous step and run the Oracle Database Upgrade Assistant (DBUA) against the Applications

11i database.

Read Chapter 2 of Oracle Database Upgrade Guide 10g Release 2 (10.2) Part Number B14238-02.

Take note of the section pertaining to the Database Upgrade Assistant (DBUA).

Start an Xterm session on the source database server as the “oracle” user, export the new

ORACLE_HOME, and run the DBUA from $ORACLE_HOME/bin.


$ cd $ORACLE_HOME/bin

$ ./dbua

Select the 9i database from the list of available databases.

Monitor the progress of the DBUA. At the end of the upgrade process, DBUA will automatically start

the instance.

The upgrade log files are located in $<10gR2_ORACLE_HOME>/cfgtoollogs/dbua/<SID>/upgrade.

Review “UpgradeResults.html” and make any necessary changes. See Appendix C for the upgrade

results of this project.

1.3.5 Edit the initialization parameter file

The newly installed Oracle 10gR2 will not be tuned for Oracle Applications 11i. Review the Oracle

Support Portal document: 216205.1 Database Initialization Parameters and Configuration for Oracle

Applications Release 11i.

Note: During the database startup, Oracle DB 10g first looks in

$ORACLE_HOME/dbs for the spfile (spfile<SID>.ora) and if not found the

RDBMS will attempt to load the pfile (init<SID>.ora) file. After the 10gR2

upgrade, both pfile and spfile have the same values. It will be easier to

modify the pfile and then recreate the spfile after all the changes are made

and the database started. Make sure that you rename the spfile<SID>.ora

and backup the init<SID>.ora before modifying.

Make the following modification and restart the database.

Common EBS 11i modifications db_file_multiblock_read_count = 8

optimizer_max_permutations = 2000

query_rewrite_enabled = true

_sort_elimination_cost_ratio = 5

_like_with_bind_as_equality = TRUE

_fast_full_scan_enabled = FALSE

_sqlexec_progression_cost = 2147483647

22

10gR2 EBS 11i modifications _b_tree_bitmap_plans = FALSE

optimizer_secure_view_merging = FALSE

_optimizer_autostats_job=false

compatible = 10.2.0

session_cached_cursors = 500

sga_target = 1G

shared_pool_reservered_size=40M

shared_pool_size=400M

10gR2 EBS 11i removed parameters

_kks_use_mutex_pin=FALSE background_dump_dest

core_dump_dest

db_block_buffers

db_file_multiblock_read_count

db_cache_size

java_pool_size

large_pool_size

query_rewrite_enabled

undo_retention

1.3.6 Additional database modification

System Managed Undo (SMU) should be enabled in the database instance and define the temporary

tablespace properly. Review My Oracle Support Portal document: 216205.1 Database Initialization

Parameters and Configuration for Oracle Applications Release 11i and follow the instructions in these

sections:

· Release-specific database initialization parameters for 10gR2

· Enabling System Managed Undo (SMU)

· Temporary Tablespace Setup

1.3.7 Perform 10.2.0.4 patch set post-installation tasks

Review the “Postinstallation Tasks” section of the 10.2.0.4 patch set notes (README.html). After you

install the patch set, you must perform the post-installation tasks. Skip the sections "Upgrading Earlier

Oracle Database to Oracle Database 10g Release 2 (10.2.0.4)", "Enabling Oracle Database Vault",

and "Upgrading Oracle Database 10g Release 10.2.0.x to Oracle Database 10g Release 10.2.0.4"

of the patch set notes.

Bounce the database and run the SQL script to validate invalid objects within the database. SQL> shutdown

SQL> startup

SQL> @?/rdbms/admin/utlrp.sql

Use the following queries to track recompilation progress:

Query returning the number of invalid objects remaining. This number should decrease with time.

SQL> SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);

Query returning the number of objects compiled so far. This number should increase with time.

SQL> SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;

23

1.3.8 Install Oracle Data Mining and OLAP

Note: Restricted use licenses for Oracle Data Mining and OLAP are

included with Oracle Database Enterprise Edition for the purposes of

upgrading existing E-Business Suite databases.

Cross check that Oracle Data Mining and OLAP are installed in your database. Connect to the

database as SYSDBA and run the following command:

SQL> connect / as sysdba;

SQL> select comp_id from dba_registry where comp_id='ODM' or comp_id='AMD';

If the query does not return ODM, then your database does not have Oracle Data Mining installed.

To install Data Mining, connect to the database as SYSDBA and run the following command:


SQL> @$ORACLE_HOME/rdbms/admin/dminst.sql SYSAUX TEMP

If the query does not return AMD, then your database does not have OLAP installed. To install OLAP,

connect to the database as SYSDBA and run the following command:


SQL> @$ORACLE_HOME/olap/admin/olap.sql SYSAUX TEMP

1.3.9 Natively compile PL/SQL code (optional)

You can choose to run Oracle Applications Release 11i PL/SQL database objects in natively

compiled mode with Oracle Database 10g. For detailed steps, refer to the Compiling PL/SQL Code

for Native Execution section of Chapter 11 of Oracle Database PL/SQL User's Guide and Reference

10g Release 2 (10.2).

When modifying the initialization parameters pertaining to the PL/SQL native compilation, refer to

Oracle Support Portal document: 216205.1, Database Initialization Parameters and Configuration

for Oracle Applications Release 11i as a guideline. You can set the

plsql_native_library_subdir_count parameter as described in the PL/SQL user's guide.

Create the associated subdirectories for the given plsql_native_library_dir and

plsql_native_library_subdir_count parameters.

1.3.10 Fix Korean lexers

If you have upgraded from 10.1.0 or previous releases, then connect to the database as SYSDBA,

and run drkorean.sql using the following command:

$ sqlplus "/ as sysdba" @$ORACLE_HOME/ctx/sample/script/drkorean.sql

1.3.11 Start the new database listener

Since AutoConfig has not yet been implemented, start the listener with the lsnrctl executable. See the

Oracle Database Net Services Administrator's Guide, 10g Release 2 (10.2) for more information.

http://otn.oracle.com/documentation/database10gr2.html

24

Prior to starting the listener, perform these additional steps:

Create the $TNS_ADMIN directory in the 10g_ORACLE_HOME.

$ export ORACLE_HOME=<10g_ORACLE_HOME>

$ export ORACLE_SID=<SID>

$ export PATH=$ORACLE_HOME/bin:$PATH:.


$ mkdir –p $ORACLE_HOME/network/admin/<SID>_<hostname>

$ export TNS_ADMIN=$ORACLE_HOME/network/admin/<SID>_<hostname>

Copy the contents of 9i_TNS_ADMIN to $TNS_ADMIN.

$ cp <9i_Oracle_Home>/network/admin/<SID>_<hostname>/* $TNS_ADMIN

Modify the following .ora files changing all directory reference of 9.2.0 to 10.2.0.

$ vi $TNS_ADMIN/listener.ora

$ vi $TNS_ADMIN/sqlnet.ora

$ vi $TNS_ADMIN/tnsnames.ora

Start the new Oracle Net Listener.

$ lsnrctl start <SID>

1.3.12 Run adgrants.sql

Copy $APPL_TOP/admin/adgrants.sql from the administration server node to the database server

node. Use SQL*Plus to connect to the database as SYSDBA and run the script using the following

command:

$ sqlplus "/ as sysdba" @adgrants.sql <APPLSYS schema name>

where <APPLSYS schema name> is the Applications Object Library user, most commonly named

APPLSYS.

1.3.13 Grant create procedure privilege on CTXSYS

Copy $AD_TOP/patch/115/sql/adctxprv.sql from the administration server node to the

database server node. Use SQL*Plus to connect to the database as APPS and run the script using the

following command:

$ cd $ORACLE_HOME/admin

$ sqlplus apps/<apps_password>

SQL> @adctxprv.sql <SYSTEM password> CTXSYS

1.3.14 Implementing AutoConfig on upgraded database

You need to configure and run AutoConfig in the new Oracle home on the database server node. If

you have different configuration for the database listener in the new Oracle home, then you must also

run AutoConfig on each application tier server node to update the system with the new listener.

For more information review Oracle Support Portal document: 165195.1, Using AutoConfig to

Manage System Configurations with Oracle E-Business Suite 11i.

Shut down all processes, including the database and the listener, and restart them to load the new

environment settings.

This task will migrate AutoConfig to the DB Tier.

Logon to the Application node, source the environment file, then run the admkappsutil.pl script. This

Perl script will create the appsutil.zip file located in the $APPL_TOP/admin/out directory.

If current, you can also use the appsutil.zip located in the 9i_ORACLE_HOME.

$ perl $AD_TOP/bin/admkappsutil.pl

25

Copy and unzip the appsutil.zip file in the Database node <10gR2_ORACLE_HOME>.

$ cd <10gR2_ORACLE_HOME>

$ unzip -o appsutil.zip

Set the following environment variables to be incorporated in the database context file.

# su - oracle






$ export JRE_TOP=$ORACLE_HOME/jre/1.4.2

$ export LD_LIBRARY_PATH=$ORACLE_HOME/lib32

$ export SHLIB_PATH=$ORACLE_HOME/lib32

$ export LIBPATH=$ORACLE_HOME/lib32

Generate the database context file.

$ cd $ORACLE_HOME/appsutil/bin

$ perl adbldxml.pl tier=db appsuser=apps appspasswd=<apps_password>

The newly-created context file and log file are located in following locations:

Context File = <10gR2_ORACLE_HOME>/appsutil/<SID>_<hostname>.xml

Log file = <10gR2_ORACLE_HOME>/appsutil/log/adbldxml_<date>.log

Modify the context file, changing all reference of 9.2.0 to 10.2.0.

Note:

An improper entry introduced into the context file can render the

applications environment inoperable. Always make a backup prior to

editing the context file.

Run AutoConfig to generate a new 10gR2 environment file located in the <10g_ORACLE_HOME>

directory.


$ ./adconfig.sh \

contextfile=<10gR2_ORACLE_HOME>/appsutil/<SID>_<hostname>.xml \

appspass=<apps_password>

Review log file for any failures, errors, or warnings and resolve those issues before continuing.

Shut down the 10g database and listener, source the new database environment file, and then start

up the listener and the 10g database.

$ sqlplus / as sysdba

SQL> shutdown normal

SQL> exit


# su – oracle

$ . <10gR2_ORACLE_HOME>/<SID>_<hostname>.env



SQL> startup

26

1.3.15 Gather statistics for SYS schema

Copy $APPL_TOP/admin/adstats.sql from the administration server node to the database server

node. SQL script adstats.sql requires database running in restricted mode. Connect to the database

as SYSDBA and use the following commands to restart the database in restricted mode, run

adstats.sql, and restart the database in normal mode:



SQL> startup restrict

SQL> @?/admin/adstats.sql


SQL> startup

There should be at least 1.5 GB of free default temporary tablespace.

1.3.16 Re-create custom database links (conditional)

If you have different configuration for the database listener in the new Oracle home, then you must re-

create any custom self-referential database links that exist in the Applications database instance.

Verify the existing database links. Connect to the Applications database instance as APPS and run the

following query:

$ sqlplus apps/<apps password>

SQL> select db_link from dba_db_links;

If EDW_APPS_TO_WH and APPS_TO_APPS database links exist, then they should have been

updated with the new port number by AutoConfig in the step „1.3.13 Implement and run AutoConfig‟.

For custom self-referential database links (if any) in the database instance, use the following

commands to drop and re-create them:


SQL> drop database link <custom database link>;

SQL> create database link <custom database link> connect to

<user> identified by <password> using

'(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<hostname>)

(PORT=<port number>))(CONNECT_DATA=(SID=<ORACLE_SID>)))';

where <custom database link>, <user>, <password>, <hostname>, <port number>, and

<ORACLE_SID> reflect the new Oracle Net listener for the database instance.

1.3.17 Re-create grants and synonyms

You must re-create the grants and synonyms in the APPS schema as Oracle database 10g Release 2

(10.2) contains new functionality for grants and synonyms compared to previous database releases.

On the administration server node, as the owner of the Applications file system, run AD

Administration and select the Recreate grants and synonyms for APPS schema task from the Maintain

Applications Database Objects menu.

If you are using MRC (Multiple Reporting Currencies) in your Applications system, then run the

Maintain Multiple Reporting Currencies schema task to re-create MRC triggers in the APPS schema.

Change directory to $ORACLE_HOME/rdbms/admin.

Start SQL*Plus session with sysdba privilege and shutdown the database.

Startup database using the upgrade option.

SQL> startup upgrade

27

Run the utlirp.sql.

SQL> @utlirp.sql

Bounce the database and run the utlrp.sql.

SQL> @utlrp.sql

Check invalid objects

SQL> select count(*) from dba_objects \

where status = ‘INVALID’;

Use adadmin on the Administration server node to re-create grants and synonyms.

# su – applmgr

$ . <APPL_TOP>/APPS<SID>_<hostname>.env

$ adadmin

Maintain Applications Database Entities

Re-create grants and synonyms for APPS schema

1.3.18 Recreate spfile from pfile

$ cd $ORACLE_HOME/dbs


SQL> CREATE SPFILE FROM PFILE = '<ORACLE_HOME>/dbs/init<SID>.ora’;

1.3.19 Apply Oracle Receivables patch

Apply Oracle Receivables patch 5753621.

1.3.20 Compile invalid objects

Check for invalid database objects before and after this step (see Migration prerequisites section for

details). Use adadmin on the Administration server node to compile invalid objects.

$ adadmin

Compile/Reload Applications Database Entities

Compile APPS schema(s)

You may want to also use the utlrp.sql script on the database node to decrease the number of invalid

objects in the database. Connect to the 10gR2 Database using SQL*Plus with SYSDBA privileges and

run the utlrp.sql script.



Check for invalid objects.

SQL> Select count(*) from dba_objects where status = “INVALID”;

1.3.21 Restart Applications server processes (conditional)

Start the database instance and Oracle Net listener for the database instance in the new 10.2.0

Oracle home. Start all the Application tier server processes.

1.3.22 Validate environment and perform a full backup

After successfully validating the E-Business Suite environment as explained in Appendix F, perform a

full backup to complete the upgrade to 10gR2 phase. The migration process can be paused at this

stage and normal business operations can resume. If time permits, the next phase can be continued

immediately or during the next planned downtime.

28

Phase 2: Migrating Oracle Applications 11i database to

HP Integrity server

This phase includes the tasks to migrate the source 10gR2 database instance from HP AlphaServer

systems running Tru64 UNIX to the target HP Integrity server. The Oracle Applications 11i

environment will be offline during part of this phase. After the completion of this phase, the Oracle

Applications 11i environment can resume normal operations as a fully supported split configuration

where the application tier is running on HP AlphaServer systems running Tru64 UNIXs and the

database tier is running on HP Integrity server. The instructions below are based partly on Oracle

Support Portal document: Using Oracle Applications with a Split Configuration Database Tier on

Oracle 10g Release 2 [ID 369693.1] and Oracle Support Portal document: Cross Platform

Transportable Tablespaces (XTTS) on 11i with 10gR2 [ID 454574.1].

Constraints of using XTTS

1. The character set and national character set must be same at source and target databases.

2. XTTS is not supported for tables having columns encrypted using the Transparent Data

Encryption (TDE) functionality of Oracle Database 10g (Review Oracle Support Portal

document: Using TDE Column Encryption with Oracle E-Business Suite Release 11i [ID

403294.1]). You must de-crypt the encrypted columns prior to transportable tablespaces

migration and then encrypt again in the target database after migration.

Other detail limitations are documented in the Chapter 8 ('Managing Tablespace) of Oracle

Database Administrator's Guide 10g Release 2 (10.2) Part# B14231-02.

Note: Since there is a potential for data corruption when using XTTS,

suitable alternative migration options (such as export/import) may be

needed due to unforeseen/non-reproducible errors.

During phase 2 of the migration, you will:

· Section 1: Prepare the source database node

· Section 2: Prepare the target database node

· Section 3: Export the source Applications 11i database objects

· Section 4: Import the Applications 11i database objects to the target database node

· Section 5: Upgrade the target Applications 11i database instance

29

Figure 4. Phase 2 – Migrating Applications 11i database to the target HP Integrity server

Source

Tru64 5.1b

EBS 11.5.10.2

RDBMS 9.2.0.6

Phase II

Migrating Applications 11i database to HP Integrity server

Section 1:

Prepare source

DB Node

· Full Backup

· Apply export/

import utility

patch

Section 2:

Prepare target DB

Node

· Prep Integrity

server

· Install 10gR2

Software only

· Apply 10.2.0.4

patchset

Section 3:

Export source DB

objects

· Prepare for

export

· Export DB

objects

· Convert

endian format

Phase III

Upgrade to

Release 12.1.1

on HP Integrity

server

Phase I

Upgrade

RDBMS 9.2.0.6

to 10.2.0.4

Section 4:

Import DB objects

to target Node

· Copy export

dump and data

files

· Import DB

objects

Section 5:

Upgrade the target

DB instance

· Perform post

import DB

steps

· Perform post

import Apps

11i steps

2.1 Prepare the source database node

2.1.1 AutoConfig upgrade to the latest version

This has already been executed during the previous step 'Migration prerequisites' in this white paper

while applying dependent patch 8217898 TXK AUTOCONFIG AND TEMPLATES ROLLUP PATCH T.

Review Oracle Support Portal document: AutoConfig to Manage System Configurations with Oracle

Applications 11i [ID 165195.1] for any latest update.

2.1.2 Apply the Applications consolidated export/import utility patch

Download and apply the 'Controlled' export/import Oracle Applications 11i Patch 6158038

Export/import patch 9/09 including transportable tablespaces to the administration server node. This

patch requires customers to file a Service Request (SR) with Oracle Support to receive the password to

download.

2.1.3 Apply latest Applications database preparation scripts patch

Apply Oracle Applications 11i Patch 7225862 APPSST10204: RECREATE PATCH 6954610 TO

INCLUDE FILE.DRV to every application tier node.

As this patch has been superseded by Oracle Applications 11i patch 7429271 Applications DBA

Minipack Patch 11I.AD.I.7, hence, this requirement has already been satisfied during the previous

step 'Migration prerequisites' in this white paper while applying dependent patches.

2.1.4 Create a working directory

Create a working directory named xttsexpimp in the source system that will contain all generated files

and scripts required to complete this section. As an example,

$ mkdir /oratmp/xttsexpimp

2.1.5 Create transport_set_violations table

Use SQL*Plus to connect to the source database as sysdba and run the following command:

SQL> exec dbms_tts.transport_set_check('[TABLESPACE]');

You can also use any existing tablespace name for [TABLESPACE] e.g. „APPS_TS_SUMMARY‟. You

can ignore if any errors appear as this command will create the SYS.transport_set_violations table

which will be used later while running automatic scripts.

30

2.1.6 Run the auxttspre.sql script

Copy the auxttspre.sql script (installed as part of the export/import patch) from the application tier‟s

$AU_TOP/patch/115/sql directory over to the database tier's working directory.

As the owner of the source database server file system, connect to the source database as SYSDBA

and run the auxttspre.sql script.

$ sqlplus /nolog


SQL> @auxttspre.sql

The script will generate files listed and explained in Appendix D. These files will be used in the

migration process using XTTS during Phase 2. Make sure you review and understand the files

description and usage explained in the Appendix D before proceeding with this phase.

Make sure to review and analyze the resulting log file auxttspre.log for any transport set

violations. You need to fix all the transport set violations listed in the log file, and then re-do the

instructions in this step before proceeding with the rest of this document.

2.1.7 Collect Advanced Queue settings

Collect the Advanced Queue settings before migration as they will not be moved to the target

database instance during the migration process. 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 into the working directory created in „Step 2.1.4

Create a working directory‟. As the owner of the source database server file system, connect to the

source database as SYSDBA and run the auque1.sql script. It generates auque2.sql in the current

directory.

$ sqlplus /nolog


SQL> @auque1.sql

2.1.8 Removal of rebuild index parameter in spatial indexes

Cross check the spatial indexes for the „rebuild index‟ parameter. Spatial indexes can have clause

"rebuild index" that may cause error in export during XTTS migration. These indexes will need to be

recreated in the target database (or dropped and recreated in the source database without the

"rebuild index" qualifier). Hence, prior to the XTTS export, perform the PREPARE_FOR_TTS procedure

for spatial indexes:

SQL> EXECUTE SDO_UTIL.PREPARE_FOR_TTS('spatial_tbs');

To see if you have any rebuild index parameters, as the owner of the source database server file

system, connect to the source database as sysdba and run the following command:

SQL> select * from dba_indexes where index_type='DOMAIN' and upper(parameters)

like '%REBUILD%';

To remove the rebuild index parameter, connect to the source database as the owner of the index

and run the following command:

SQL> alter index [index name] rebuild parameters [parameters];

where [parameters] is the original parameter set without the rebuild_index parameter.

31

2.2 Prepare the target database node

This section will create an empty target database and populates it with all of the required system

objects prior to running XTTS import.

2.2.1 Configure the HP-UX 11i on target node

Configure the HP Integrity server and install the HP-UX 11i v3 operating system according to HP

product installation notes. Complete the preparation steps by staging the installation media and

Operating System patches for 10gR2 database for HP-UX Itanium, apply the required operating

system patches, and incorporate the required kernel parameter settings. For more information, refer to

Oracle Support Portal document: Oracle E-Business Suite Installation and Upgrade Notes Release 12

(12.1.1) for HP-UX Itanium [ID 762891.1].

2.2.2 Modify operating system kernel parameters

Refer to Appendix A for a list of kernel parameters for HP-UX 11i v3. These are only suggested kernel

settings and should be considered a starting point for additional operation system tuning.

2.2.3 Preparation to create the 10.2.0 Oracle home on Integrity server

To understand the installation and upgrade processes, read Chapters 1 and 2 of the Oracle

Database Installation Guide 10g Release 2 (10.2) for HP-UX Itanium Part Number B25293-01 and

the System Considerations and Requirements section of Chapter 3 of the Oracle Database Upgrade

Guide 10g Release 2 (10.2) Part Number B14238-02. Execute any additional steps that are relevant

for your environment.


Start an Xterm session on the target database server as the “oracle” user, change directory to the

10.2.0 staging area, and run the Oracle Universal Installer wizard using the “-ignoreSysPreReqs”

option. DO NOT source the 9i database environment.

$ cd <10.2.0_staging_directory>

$ ./runInstaller


Enterprise Edition


Name: OUIHome2

Path: <10g_ORACLE_HOME>





or discontinued.


NO





End of Installation

32

2.2.5 Install the Companion CD for the base 10.2.0 software

Start up an Xterm session as the “oracle” user on the target database server.

Change directory to staging area for the 10.2.0 Companion CD and run the Oracle Universal

Installer wizard. DO NOT source the 9i database environment and make sure that:







version>).


software:

$ export ORACLE_HOME= <10gR2_ORACLE_HOME>



$ export SHLIB_PATH=$ORACLE_HOME/lib



$ cd <stage_directory>/Disk1

$ ./runInstaller

2.2.6 Execute 10.2.0.4 patch set pre-installation tasks

On the database server node, as the owner of the Oracle 10g file system, extract the 10.2.0.4 patch

set file. Read the patch set notes in README.html. Understand the upgrade and patch set installation

process before starting the patch set installation.

2.2.7 Execute 10.2.0.4 patch set installation tasks


10.2.0.4 patch set staging area and run the Oracle Universal Installer.

Make sure that:


· The ORACLE_HOME environment variable points to the 10.2.0 Oracle home.






version>).


software:






$ cd <10.2.0.4 patch set staging_directory>

$ ./runInstaller

33


As the owner of the 10gR2 RDBMS file system, set the ORACLE_HOME variable and run the

cr9idata.pl Perl script; then set the ORA_NLS10 environment variable.







$ perl cr9idata.pl


2.2.9 Install the latest available patch set release and any required patches

Once you have installed the major Oracle Database 10g software, check to see if there is a critical

patch update that needs to be installed. The latest critical patch update for Oracle Database 10g

Release 2 should be installed prior to upgrading your databases. Refer to the specific critical patch


2.2.10 Apply additional 10.2.0 RDBMS patches


platform specific RDBMS One-off patches. Also apply OPatch 10.2.0.0.0 (Patch 6880880)

for HP-UX Itanium (or the latest OPatch version for 10gR2) before applying these

additional RDBMS patches.

6521934 10.2.0.4 HP-UX Itanium

6600051 10.2.0.4 HP-UX Itanium

7496636 10.2.0.4 HP-UX Itanium

7497678 10.2.0.4 HP-UX Itanium

Run opatch lsinventory before and after applying patches. Review all the readme files before applying

any patch and review the logs for any discrepancy after applying each patch. If any are found,

resolve them first before continuing to the next step.

2.2.11 Verify one-off patch equivalence with source RDBMS ORACLE_HOME

The RDBMS software versions should be exactly equivalent on the AlphaServer systems and Integrity

server in order to avoid any complications during migration of the database instance. The OPatch

utility should be used to list the installed patches and confirm that the two ORACLE_HOMEs are

indeed equivalent.

2.2.12 Create the target initialization parameter file and CBO parameter file

From the source database server node, copy initialization parameter files to the Oracle 10g

$ORACLE_HOME/dbs directory on the target database server node. Refer to database initialization

parameters (init.ora) settings for 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. Ignore the initialization parameters that

pertain to the native compilation of PL/SQL code. You will be instructed to add them later, if

necessary.

2.2.13 Create a working directory

Create a working directory named xttsexpimp in the target system which will contain all generated

files and scripts required to complete this section. As an example,

$ mkdir /oratmp/xttsexpimp

34

2.2.14 Create the target database instance

Copy the aucrdb.sql script generated in Step „2.1.6 Run the auxttspre.sql script‟ from the source

database server node to the target database server node. Update the script on the target database

server node with any necessary changes to the directory structures for the log file(s), data file(s), or

tablespaces, reflecting the layout of the target database server node. Confirm the default temporary

and undo tablespaces are according to your requirement. Review the example file in Appendix D.

Setup the environment variables appropriately on the target database server for the target database

instance, especially the ORACLE_HOME, ORACLE_SID, and ORA_NLS10 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 aucrdb.sql and create the target database instance:

$ sqlplus /nolog SQL> connect / as sysdba;

SQL> spool aucrdb.log;

SQL> startup nomount;

SQL> @aucrdb.sql

SQL> exit;

If PL/SQL of the source database was natively compiled, review the "Compiling PL/SQL Code for

Native Execution" section of Chapter 11 of Oracle Database PL/SQL User's Guide and Reference

10g Release 2 (10.2) Part Number B14261-01 for instructions on how to natively compile PL/SQL in

the target database. Add the parameters that pertain to the native compilation where specified. Do

not use the natively compiled code generated by the source database. Oracle does not support

switching the PL/SQL compilation mode from interpreted to native (and vice-versa). Using native mode

takes significantly more time than interpreted mode.

When the target database instance has been created, restart the database instance.

2.2.15 Copy database preparation scripts to target Oracle home

The database preparation scripts patch that was applied to the source administration server node in

Step „2.1.3 Apply latest Applications database preparation scripts patch‟ 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 server node to the target database server node into the working

directory created during „Step 2.2.13 Create a working directory‟: addb1020.sql, adsy1020.sql,

adjv1020.sql, and admsc1020.sql. Review the scripts using text editor before you run each of the

next four steps and also note the following:

· The remarks section at the beginning of each script contains additional information.

· Each script creates a log file in the current directory.

2.2.16 Configure the SYS schema

Configure the SYS schema for use with the Applications using the addb1020.sql script. On the target

database server node, connect to the target database instance as SYSDBA and run addb1020.sql.

$ sqlplus "/ as sysdba" @addb1020.sql

2.2.17 Configure the SYSTEM schema

Configure the SYSTEM schema for use with the Applications using the adsy1020.sql script. On the

target database server node, connect to the target database instance as SYSTEM and run

adsy1020.sql.

$ sqlplus system/[system password] @adsy1020.sql

35

2.2.18 Java Virtual Machine installation

Use adjv1020.sql to install the Java Virtual Machine (JVM) in the database. On the target database

server node, connect to the target database instance as SYSTEM and run adjv1020.sql.

Here is an example:

$ sqlplus system/[system password] @adjv1020.sql

Note: This script can be run only once in a given database instance,

because the scripts that it calls are not rerun able.

2.2.19 Other required components installation

Use admsc1020.sql script to install the following required components in the database: ORD, Spatial,

XDB, OLAP, Data Mining, interMedia, and ConText. On the target database server node, connect to

the target database instance as SYSTEM and run admsc1020.sql. You must pass the following

arguments to the script, in the order specified:

Table 5. Arguments for admsc1020.sql

Argument Value

remove context? FALSE

SYSAUX tablespace SYSAUX

temporary tablespace TEMP

$ sqlplus system/[system password] @admsc1020.sql FALSE SYSAUX TEMP

Note: All of the components are created in the SYSAUX tablespace

regardless of where it was installed in the source database.

2.2.20 Disable automatic gathering of statistics

Copy $APPL_TOP/admin/adstats.sql from the administration server node to the target database

server node. Connect to the database as SYSDBA and use the following commands to restart the

database in restricted mode and run adstats.sql:

$ sqlplus "/ as sysdba"

SQL> shutdown normal;

SQL> startup restrict;

SQL> @adstats.sql

SQL> exit;

2.2.21 Backup 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.

36

2.3 Export the source Applications 11i database objects

After a successful installation of RDBMS 10gR2 on the target database node, export the source

Applications 11i database and import into the target database node. This section describes the detail

steps of exporting data from the source Oracle Applications database.

2.3.1 Deregister the source database server machine

If you are planning to use a different database port, host, SID, or database name parameter on the

database server, you must also reconfigure AutoConfig on the database tier and deregister the

current database server node.

$ perl $ORACLE_HOME/appsutil/bin/adgentns.pl appspass=apps /

contextfile=$CONTEXT_FILE -removeserver

2.3.2 Modify the export parameter files

Modify the auexpxtts.dat, auexpmsc.dat, and auexpsys.dat data pump parameter files created in

Step „2.1.6 Run the auxttspre.sql script” according the source environment and other customized

parameters using a text editor. Make a backup on any parameter file before modifying. Review the

example file in Appendix D.

Table 6. Customizable parameters in export parameter files

Parameter Description Template value

directory directory where export

dump files will be created dmpdir

dumpfile export dump file name(s) xttsmeta%U.dmp,

xttsmsc%U.dmp, or xttssys%U.dmp

Filesize export dump file size 1 GB

Logfile Log file name Expmeta.log, expmsc.log, or expsys.log

Create a directory in the system schema that corresponds to the directory specified in the template.

For example:

$ sqlplus system/[system password]

SQL> create directory xttsdmpdir as '/oratmp/xttsexpimp';

Modify the auexpglb.dat export parameter file created in Step „2.1.6 Run the auxttspre.sql script‟

according the source environment and other customized parameters using a text editor. Review the


37

Table 7. Customizable parameters in auexpglb.dat


file export dump

file name gtab.dmp

filesize export dump

file size 1 GB

log log file name expgtab.log

2.3.3 Shut down Applications server processes

Shut down all Applications server processes except the database and the Net Services listener for the

database. Users cannot use the Applications until the import is completed.

2.3.4 Purge unused columns and recycle bin

Connect to the source database as sysdba and run the following commands to find and purge any

unused columns:

SQL> select * from sys.dba_unused_col_tabs;

SQL> alter table [table name] drop unused columns;

Run the following commands to find and purge the recycle bin:

SQL> select owner, count(*) from dba_recyclebin group by owner;

SQL> connect [user]/[password];

SQL> purge recyclebin;

2.3.5 Back up AZ table data (conditional)

If you are using AZ.H, upgrade to AZ.H.DELTA.1. Review Oracle Support Portal document: About

Oracle iSetup Minipack 11i.AZ.H.Delta.1 [ID 403092.1] for instructions.

Oracle Data Pump version 10.2 does not allow tables with XML type columns to be migrated. Execute

step 2 of Oracle Support Portal document: iSetup dependency with Deinstall and Reinstall of XMLDB

[ID 402785.1] to back up the data within XML type columns.

2.3.6 Grant privilege to source system schema

Connect to the database as SYSDBA and use the following command to grant the exempt access

policy privilege to system:

SQL> grant EXEMPT ACCESS POLICY to system;

2.3.7 Change the tablespaces within the transportable set to read only

Connect to the database as SYSDBA and run auxttsread.sql to change the tablespaces within the

transportable set as read only:

$ sqlplus "/ as sysdba" @auxttsread.sql

Review the example file in Appendix D

2.3.8 Export the transportable tablespace set

Use the following command to start an export session on the source database server node using the

auexpxtts.dat parameter file:

$ expdp system/[system password] parfile=auexpxtts.dat

38

2.3.9 Export SYSTEM tablespace schemas

Use the following command to export the SYSTEM tablespace schemas by starting an export session

on the source database server node using the auexpsys.dat parameter file:

$ expdp system/[system password] parfile=auexpsys.dat

2.3.10 Export global temporary tables

Global temporary tables are not exported as they do not reside in any tablespace. Use the following

command to start an export session on the source database server node using the auexpglb.dat

parameter file to export the global temporary tables:

$ exp system/[system password] parfile=auexpglb.dat

2.3.11 Export miscellaneous data

Start an export session on the source database server node using the auexpmsc.dat parameter file to

export other objects. Use the following command:

$ expdp system/[system password] parfile=auexpmsc.dat

2.3.12 Convert endian format of the data files

Connect to the database as SYSDBA and use the following command to check the endian formats of

the source and target platforms:

Source:

SQL> select PLATFORM_ID, PLATFORM_NAME from v$database;

PLATFORM_ID PLATFORM_NAME

----------- ---------------------------------------------------------------------

5 HP Tru64 UNIX

Target:

SQL> select PLATFORM_ID, PLATFORM_NAME from v$database;

PLATFORM_ID PLATFORM_NAME

----------- ---------------------------------------------------------------------

4 HP-UX IA (64-bit)

As the source and target platforms have different endian formats, a conversion is necessary. Modify

the aurman.dat script, which was generated in Step „2.1.6 Run the auxttspre.sql script‟, with the

target platform name, directory format, and directory location (where the data files with converted

endian format will be generated). Review the example file in Appendix D

Then, use the following command to create the new data files:

$ rman target / @aurman.dat

To avoid space constraint at source DB node, you can mount the target DB node directory at Source

DB node and specify the mount point in „aurman.dat‟.

Please see Oracle Support Portal document: 10g Transportable Tablespaces Across Different

Platforms [ID 243304.1] for information on the endian-ness of various platforms.

39

2.3.13 Revoke privilege from source system schema

Connect to the database as SYSDBA and revoke the exempt access policy privilege from system using

the following command:

SQL> revoke EXEMPT ACCESS POLICY from system;

2.3.14 Shutdown the database

Use SQL*Plus to connect to the database as SYSDBA and use the following command to shut down

the database:


SQL> shutdown normal;

2.4 Import the Applications 11i database objects to the target database

node

This section describes the detail steps of data import into the target database.

2.4.1 Copy the export dump and data files

If you have not already moved or copied the database files with converted endian format from source

DB node to target DB node in previous steps, then copy all the data files and export dump files

generated in Step „2.3 Export the source Applications 11i database objects‟ from the source

database server node to the target database server node.

2.4.2 Edit the import parameter files

Copy all the import parameter files generated in Step „2.1.6 Run the auxttspre.sql script‟ from the

source database server node to the target database server node. Modify the auimpxtts.dat,

auimpmsc.dat, and auimpsys.dat data pump parameter files according the target environment and

other customized parameters using a text editor. Review the example file in Appendix D.

Table 8. Customizable parameter in import parameter files


directory Directory where the

export dump files are located dmpdir

dumpfile export dump file name(s) xttsmeta%U.dmp,

xttsmsc%U.dmp, or xttssys%U.log

logfile Log file name impmeta.log,

impmsc.log, or impsys.logg

transport_datafiles Location of every data file in

the transportable tablespace set ?/dbf/[file name]

Change the directory structures for transport_datafiles to reflect the location of the data files on the

target database server node.

Create a directory in the system schema that corresponds to the directory specified in the template.

For example:

$ sqlplus system/[system password]

SQL> create directory xttsdmpdir as '/oratmp/xttsexpimp';

40

Edit the auimpglb.dat import parameter file created in Step „2.1.6 Run the auxttspre.sql script‟ to

reflect the target environment and other customized parameters using a text editor. Review the


Table 9. Customizable parameter in auimpglb.dat file


file import

file name gtab.dmp

log import log

file name impgtab.log

2.4.3 Import miscellaneous data

Use the following command to start the import session on the target database server node using the

auimpmsc.dat parameter file:

$ impdp system/[system password] parfile=auimpmsc.dat

2.4.4 Import the transportable tablespace set

Use the following command to start the import on the target database server node using the

auimpxtts.dat parameter file:

$ impdp system/[system password] parfile=auimpxtts.dat

2.4.5 Revert the tablespaces to read/write mode

Copy auxttswrite.sql generated in Step „2.3 Export the source Applications 11i database objects‟ to

the target database server node. Then, as the owner of the source database server file system,

connect to the source database as sysdba and run the auxttswrite.sql script. Review the example file

in Appendix D.

$ sqlplus "/ as sysdba" @auxttswrite.sql

2.4.6 Change the default tablespaces of users

Copy audeftbsp.sql, generated in Step „2.3 Export the source Applications 11i database objects‟ to

the target database server node. Then, as the owner of the target database server file system, connect

to the source database as sysdba and run the audeftbsp.sql script. Review the example file in

Appendix D.

$ sqlplus "/ as sysdba" @audeftbsp.sql

Note: Cross check the tablespace quota on the target system by issuing the

sqlplus command:

sqlplus> select username, count(*) from dba_ts_quotas group by username

order by username;

Compare this result with that on the source machine and if there are any

discrepancies, issue the sqlplus command:

sqlplus> grant quota on [tablespace] to [user]

41

2.4.7 Import global temporary tables


auimpglb.dat parameter file:

$ imp system/[system password] parfile=auimpglb.dat

2.4.8 Import procedural objects

Change the "EXCLUDE=PROCOBJ" line in auimpmsc.dat to “INCLUDE=PROCOBJ", change the log

file name, and remove the remap_tablespace setting using a text editor. Start the import session on

the target database server node using the auimpmsc.dat parameter file. Use the following command:

$ impdp system/[system password] parfile=auimpmsc.dat

2.4.9 Import SYSTEM tablespace schemas


auimpsys.dat parameter file:

$ impdp system/[system password] parfile=auimpsys.dat

2.510 Revoke privilege from target system schema

Connect to the database as SYSDBA and revoke the exempt access policy privilege from system using

the following command:

SQL> revoke EXEMPT ACCESS POLICY from system;

2.5 Upgrade the target Applications 11i database instance

This step explains the post-import steps required to restore the target database to a fully functional

state.

2.5.1 Reset Advanced Queues

Copy the auque2.sql script that was generated in Step „2.1.6 Run the auxttspre.sql script‟ to the target

database server node. Then, on the target database server node, as the owner of the Oracle 10g file

system, connect to the target database as SYSDBA and run the auque2.sql script to enable the

Advanced Queue settings that were lost during the process. The script creates a log file in the current

directory. Review the example file in Appendix D.

$ sqlplus "/ as sysdba" @auque2.sql

2.5.2 Start the new database listener

Start the Oracle Net listener for the database instance in the new Oracle home if it has not been

started. Start the listener with the lsnrctl executable since AutoConfig has not yet been implemented.

See the Oracle Database Net Services Administrator's Guide 10g Release 2 (11.1) for more

information.


Note: Set the TNS_ADMIN environment variable to the directory where you

created your listener.ora and tnsnames.ora files.

http://download.oracle.com/docs/cd/B19306_01/network.102/b14212/toc.htm

42

2.5.3 Run adgrants.sql


node. Use SQL*Plus to connect to the database as SYSDBA and run the script using the following

command:

$ sqlplus "/ as sysdba" @adgrants.sql [APPS schema name]

Note: Verify the usage of adgrants.sql in the adgrants.sql script. Older

versions of adgrants.sql require the APPLSYS schema name parameter to

be passed instead of APPS.

2.5.4 Grant create procedure privilege on CTXSYS

Copy $AD_TOP/patch/115/sql/adctxprv.sql from the administration server node to the database

server node. Use SQL*Plus to connect to the database as APPS and run the script using the following

command:

$ sqlplus apps/[APPS password] @adctxprv.sql [SYSTEM password] CTXSYS

2.5.5 Migrate the AD Utilities to the target database server node

This task will enable migration of the AD Utilities from the source administration server node to the

target database server node. For more information, refer to Section 5 of Oracle Support Portal

document: 165195.1 Using AutoConfig to Manage System Configurations with Oracle E-Business

Suite 11i. In summary:

Update the ORACLE_HOME with the AutoConfig files by performing the following steps:

1. On the Application Tier (as the Applications File system user):

· Log in to the APPL_TOP environment (source the environment file)

· Create appsutil.zip file $ perl <AD_TOP>/bin/admkappsutil.pl

· This action will create appsutil.zip in $APPL_TOP/admin/out directory.

2. On the Database Tier (as the Oracle user):

Copy and unzip the appsutil.zip file to the <RDBMS ORACLE_HOME> $ cd <RDBMS ORACLE_HOME>

$ unzip -o appsutil.zip

43

3. Generate your database context file.

· Verify that the following environment settings are set properly:





$ export ORA_NLS10=$ORACLE_HOME /nls/data/9idata


$ export SHLIB_PATH=$ORACLE_HOME/lib

· Run the AD build XML Perl script:


$ perl adbldxml.pl tier=db appsuser=apps \

appspasswd=<apps_password>

· The context file and its creation log were generated in the following locations:

Context File = $ORACLE_HOME/appsutil/<SID>_<hostname>.xml

Log = $ORACLE_HOME/appsutil/log/adbldxml_*.log

4. Run AutoConfig on the target database node:


$ ./adconfig.sh \

contextfile=<10gR2_ORACLE_HOME>/appsutil/<SID>_<hostname>.xml \


To complete this task shutdown all database processes including the listener, source the newly create

environment file, and startup the listener and database.



node. Use SQL*Plus to connect to the database as SYSDBA and use the following commands to

enable restricted mode, run adstats.sql, and disable restricted mode:


SQL> alter system enable restricted session;

SQL> @adstats.sql

SQL> alter system disable restricted session;

SQL> exit;

Note: Make sure that you have at least 1.5 GB of free default temporary

tablespace.


If you have created a new or different the Oracle Net listener in the 10.2.0 Oracle home, then you

must re-create any custom self-referential database links that exist in the Applications database

instance. Cross check the existence of database links. Connect to the Applications database instance

as APPS and run the following query:



The EDW_APPS_TO_WH and APPS_TO_APPS database links. If they exist, they should have been

updated with the new port number by AutoConfig in Step „2.5.5 Migrate the AD Utilities to the target

database server node‟.

44

Cross check custom self-referential database links (if any) in the database instance. You can use the

following commands to drop and re-create them:



SQL> create database link <custom database link> connect to <user>

identified by <password> using


(PORT=<portnumber>))(CONNECT_DATA=(SID=<ORACLE_SID)))';

where <custom database link>, <user>, <password>,<hostname> , and <ORACLE_SID> are all as

they were in the source database link definition, and <port number> is the port number of the new

Oracle Net listener for the database instance.

2.5.8 Apply Oracle Receivables patch

Apply Oracle Receivables Patch 5753621 ONE-OFF REQUEST ON TOP OF 11.5.9 CU2 FOR BUG

5525015.

2.5.9 Restore AZ table data (conditional)

If you previously performed the step to back up the AZ table data, perform steps 4 and 5 of document

402785.1 on My Oracle Support to restore the AZ table data.

2.5.10 Create OWA_MATCH package (conditional)

If you are using iAS 1.0.2, perform the steps in Note: 312165.1 to create SYS.OWA_MATCH on the

target database.

2.5.11 Create ConText and Spatial objects

Certain ConText and Spatial objects are not preserved by the import process. The export/import utility

patch 4872830 that you applied to the source administration server node in Step „2.1.6 Run the

auxttspre.sql script‟ 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 as the owner of the Applications file system:

$ perl $AU_TOP/patch/115/driver/dpost_imp.pl [driver file]

Once the driver file has been generated, use AutoPatch to apply it on the target administration server

node.

2.5.12 Compile invalid objects

On the target database server node, as the owner of the Oracle 10g 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.

$ sqlplus "/ as sysdba" @$ORACLE_HOME/rdbms/admin/utlrp.sql

45

2.5.13 Maintain Applications database objects

Run AD Administration on the target administration server node. From the Maintain Applications

Database Objects menu, perform the following tasks:

· Compile flexfield data in AOL tables

· Recreate grants and synonyms for APPS schema

If you use Multiple Reporting Currencies:

· Maintain Multiple Reporting Currencies schema

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

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

2.5.15 Create DQM indexes

Create DQM indexes by following these steps

· Log on to Oracle Applications with the "Trading Community Manager" responsibility

· Click Control > Request > Run

· Select "Single Request" option

· Enter "DQM Staging Program" name

· Enter the following parameters:

o Number of Parallel Staging Workers: 4

o Staging Command: CREATE_INDEXES

o Continue Previous Execution: NO

o Index Creation: SERIAL:

2.5.16 Gather Applications statistics (conditional)

If you encountered failures importing statistics, gather the statistics by following these steps:

· Ensure that there are no concurrent programs running.

· Log on to Oracle Applications with the "System Administrator" responsibility.

· Click Navigation List > Request > Run.

· Enter appropriate parameters. Specify "ALL" in the schema name to gather statistics for all

database objects. You may choose individual schemas to make the process run faster.

· Click "Submit".

46

2.5.17 Validation tasks

Verify that the migrated database functions properly with the source Application Tier environment. The

Oracle Applications 11i environment is now in a fully supported split configuration with the

Applications 11i server application tier services running on HP AlphaServer systems and the database

instance 10gR2 is running on HP Integrity sever.

Verify the database server hostname and database release version:

· Go to the Oracle E-Business Suite Rapid Install Portal, and log on to the E-Business Suite home page

as the sysadmin user.

· Select a responsibility (such as the System Administrator responsibility).

· Click on any form, such as the Concurrent->Requests form.

· From the Help menu click "About Oracle E-Business Suite", and verify that the server hostname and

release version correspond to those of the new HP Integrity database server.

After successfully validating the E-Business Suite environment as per Appendix F, perform a full

backup to complete the upgrade to 10gR2 phase. The migration process can be paused at this stage

and normal business operations can resume. If time permits, the next phase can be continued

immediately or during the next planned downtime.

47

Phase 3: Migrating to E-Business Suite Release 12.1.1

Phase 3 will prepare the 10gR2 database instance to be E-Business Suite Release 12.1 aware and

then install the new E-Business Suite Release 12.1.1 applications home on the target HP Integrity

server.

The Oracle E-Business Suite Upgrade Guide: Oracle E-Business Suite Upgrade Guide: Release 11i to

Release 12.1.1, Part Number E14010-01, will be used extensively to complete the final phase of this

migration. Thoroughly read and understand the procedures in this guide before continuing.

This phase could have significant downtime and product specialists and application DBAs should

work closely during this phase of the migration. This section includes the following tasks:

· Section 1: Prepare source for E-Business Suite Release 12.1.1 Upgrade

· Section 2: Upgrade to E-Business Suite Release 12.1.1

· Section 3: Perform post upgrade product specific tasks

Figure 5. Phase 3 - Upgrade to Release 12.1.1 on HP Integrity server

Source

Tru64 5.1b

EBS 11.5.10.2

RDBMS 9.2.0.6

Phase III

Upgrade to Release 12.1.1 on HP Integrity server

Section 1:

Prepare source for EBS

R12.1.1 upgrade

· Run the TUMS

script

· Performa pre-

upgrade product

specific Tasks per

TUMS report

Section 2:

Upgrade to Release

12.1.1

· Install R12.1.1 on

HP Integrity server

· Apply R12 Mega

Patch

·

Section 3:

Perform Post -Upgrade Product

specific tasks

· Use TUMS report

· Perform final validation tests

· Release to production

Phase I

Upgrade

RDBMS 9.2.0.6

to 10.2.0.4

Phase II

Migrating

Applications 11i

database to HP

Integrity server

3.1 Prepare source for E-Business Suite Release 12.1.1 upgrade

The detailed planning process begins with reviewing the Oracle Support Portal document: 761570.1,

Oracle Database Preparation Guidelines for E-Business Suite Release 12.1.1 upgrade. This note

should be used to determine the specific upgrade path and the required database patches to be

applied to prepare for the upgrade.

This project will use "Path D: Upgrade Path for Systems with 11.5.9 CU2 or 11.5.10.2

with a 10.2.0.3 or 10.2.0.4 Database ", which is applicable for Applications Release

11.5.10.2 with 10gR2 database. Closely review Chapter 1, “Planning for an Upgrade” of the

Oracle E-Business Suite Upgrade Guide: Release 11i to Release 12.1.1, Part Number E14010-01.

After determining the details of the upgrade plan, review the steps in the Oracle E-Business Suite

Upgrade Guide: Release 11i to Release 12.1.1, Chapter 2.

3.1.1 Apply 11i.AD.I Minipack

If you have not previously done so, apply the latest 11i.AD.I minipack on all application tier nodes.

For more information, refer to Oracle Support Portal document: 233044.1, About Oracle E-Business

Suite DBA Minipack 11i.AD.I. Make sure that the AutoConfig is migrated over to the database node

before continuing.

48

3.1.2 Run the Upgrade Manual Scripts (TUMS) utility

The TUMS utility reviews the current Oracle Applications Release 11i environment and creates a

report that lists all the tasks that can be omitted during the upgrade process. TUMS is delivered in a

patch, which supplies the scripts you need to examine your system and create the report.

Download and apply Oracle Applications patch 7705743: TUMS for R12: To Deliver TUMS Utility

For Upgrades From 11i TO R12 to the administration server node on your Release 11i APPL_TOP.

The patch supplies the script (adtums.sql) to generate the TUMS report (tumsr12.html).

To generate the TUMS report, login as the applications administrator and source the environment.

Then change to the “$AD_TOP/patch/115/sql” directory and run the adtums.sql script.

$ cd $AD_TOP/patch/115/sql

$ sqlplus apps/<apps_password> @adtums.sql <DIRECTORY>

For the <DIRECTORY> value, enter the full path of the directory to which you want the report to be

written. This directory must be listed in the UTL_FILE_DIR parameter of the init.ora file before TUMS

can write the report.

The report will be generated on the database node: <DIRECTORY>/tumsr12.html.

See Appendix E to view the TUMS report for this project.

3.1.3 Database and system administration tasks

These tasks are executed on the Release 11i APPL_TOP. Complete all tasks in the “Database and

System Administration Tasks” section of Chapter 2, “Preparing for the Upgrade”, in the Oracle E-

Business Suite Upgrade Guide: Release 11i to Release 12.1.1, Part Number E14010-01, excluding

the ones listed in the TUMS report, before continuing with the product-specific tasks.

3.1.4 Product-specific tasks

These tasks are executed on the Release 11i APPL_TOP. Complete all tasks in the “Applications

Technology Tasks” and “Product Specific Tasks” sections of Chapter 2, “Preparing for the Upgrade”,

in the Oracle E-Business Suite Upgrade Guide: Release 11i to Release 12.1.1, Part Number E14010-

01, excluding the ones listed in the TUMS report, before continuing with the final preparations for

upgrade task.

This section completes the final preparation tasks for your existing Release 11i system and installs the

new Oracle E-Business Suite Release 12.1.1 environment. These tasks are derived from the “Prepare

for the Upgrade” sections of Chapter 2, “Preparing for the Upgrade”, in the Oracle E-Business Suite

Upgrade Guide: Release 11i to Release 12.1.1, Part Number E14010-01.

3.1.5 Gather schema statistics for CBO (required)

Release 12.1 employs cost-based optimization, which examines FND table statistics to determine the

most efficient access paths and join methods for executing SQL statements. These statistics are

gathered by the FND_STATS process, which you initiate by running the Gather Schema Statistics

concurrent program.

From your Release 11i APPL_TOP, complete the following steps:

1. Log in to Oracle E-Business Suite 11i instance with the System Administrator responsibility.

2. Navigate to the Submit Request window (Request > Run).

3. Submit the Gather Statistics program (Schema).

Set the schema name to ALL to gather statistics for all Oracle E-Business Suite schemas (having an

entry in the FND_PRODUCT_INSTALLATIONS table). In addition to gathering index and table-level

statistics, the program gathers column-level histogram statistics for all columns listed in the

FND_HISTOGRAM_COLS table.

49

Note

Gather schema statistics on a regular basis to fully utilize the cost-based

optimization feature. In preparation for an upgrade, this needs to be one of

the last tasks you perform before initiating the upgrade so that the statistics

are current.

3.1.6 Backup the database (recommended)

Make a cold backup of the Oracle E-Business Suite database. If any problems occur during the

upgrade process the only method to rollback is to restore your system from a recent backup.

Shut down the entire Release 11i environment and make sure that the database is shut down with the

NORMAL option. Using the IMMEDIATE or ABORT option may result in an unusable database

backup.

3.1.7 Prepare the R12.1.1 Applications node and run Rapid Install (required)

Prepare the HP Integrity server for E-Business Suite Release 12.1.1 target application node. See

section 2.2 Prepare the target database node, within this document, for preparing the target server

and then use the Rapid Install wizard to lay down the file system and install the new technology stack

for your Oracle E-Business Suite Release 12.1.1 system.

Before running Rapid Install, modify the database node sqlnet.ora file to recognize the new HP

Integrity server Release 12.1.1 application node.

Edit the sqlnet.ora to include the <new_host_name> in the “tcp.invited_nodes” section. Once the

sqlnet.ora file has been updated, restart the listener process on the database server so that the target

applications server can properly connect to the remote database.

Run Rapid Install and supply basic information about your system such as port specifications, existing

and new database node descriptions (including mount points), user names and passwords, product

license types, internationalization and language settings, and mount points for other nodes in your

system.

1. Stage the Oracle E-Business Suite Release 12.1.1 installation media.

2. Logon to the HP Integrity server designated as the new applications R12.1.1 node as the owner of

the applications file system and change to:

<R12.1.1 staging area>startCD/Disk1/rapidwiz.

3. Start Rapid Install by typing rapidwiz on the command line. The Welcome screen lists the

components that are included in, or supported by, this release of Oracle E-Business Suite. Click

Next.

4. On the Wizard Operation screen, select Upgrade to Oracle E-Business Suite Release 12.1.1. Click

Next.

5. On the Select Upgrade Action screen, select Create Upgrade File system.

6. In the associated screen flow, enter the parameters required to set up your new environment and

run Rapid Install.

50

3.1.8 Migrate or upgrade your database Oracle 10gR2

Review Oracle Support Portal document: 761570.1, Database Preparation Guidelines for an Oracle

E-Business Suite Release 12.1.1 Upgrade, "Path D: Upgrade Path for Systems with 11.5.9 CU2 or

11.5.10.2 with a 10.2.0.3 or 10.2.0.4 Database".

Apply listed interim patches for Path D. It may possible that some of the OneOff patches have already

been applied. Hence, query the Inventory:

>opatch lsinventory |grep <OneOff patch number>

3.2 Upgrade to E-Business Suite Release 12.1.1

This section describes the tasks required to initiate the upgrade process. All the tasks must be

performed during the upgrade downtime.

3.2.1 Upgrading to E-Business Suite Release 12.1.1

Perform all the necessary steps in Chapter 3: “Upgrading to Release 12.1.1” of Upgrading to Release

12.1.1 in the Upgrade Guide: Release 11i to Release 12.1.1.

Notes:

Refer Oracle E-Business Suite Upgrade Guide: Release 11i to Release

12.1.1, Chapter 3: “Upgrading to Release 12.1.1”

There are two options in Step 3 of the above guide: Migrate database to

Oracle 11g Release 2, Patch the existing 10gR2 home or install a new

10gR2 home using Release 12.1.1 Rapid Install.

This project used the former option.

3.2.2 Finish the upgrade

Complete all tasks in the “Finish the Upgrade” and “Finish System Administration Tasks” sections of

Chapter 3, “Upgrading to Release 12.1.1” in the Upgrade Guide: Release 11i to Release 12.1.1.

All the tasks are performed on the Release 12.1.1 APPL_TOP and should be completed during system

downtime.

51

3.3 Perform post upgrade product specific tasks

This section describes tasks that complete the upgrade for specific products.

Complete all tasks in Chapter 4, Post-upgrade Tasks in the Upgrade Guide: Release 11i to Release

12.1.1, excluding the tasks listed in the TUMS report.

This section includes the following tasks:

· Applications technology tasks

· Customer relationship management tasks

· Financials and procurement tasks

· Human resources tasks

· Intelligence tasks

· Projects tasks

· Supply chain management tasks

· System maintenance tasks

· Additional tasks

This completes the Oracle E-Business Suite upgrade to Release 12.1.1.

Shut down the environment and perform a full backup of the environment. Perform validation testing

as listed in Appendix F, and then clone the environment for use with production support environment.

Oracle E-Business Suite Release 12.1.2 is now available. Hence, you can also perform following two

optional phases to upgrade to latest Oracle E-Business Suite and RDBMS versions i.e. E-business Suite

Release R12.1.2 and RDBMS 11gR2.

52

Phase 4: Upgrade E-Business Suite R12.1.1 to Release

12.1.2

This phase covers the detailed steps to apply the Oracle E-Business Suite Release 12.1.2 Release

Update Pack (12.1 RUP2) (Patch 7303033) This release update pack (RUP) combines error

corrections, statutory/regulatory updates, and functionality enhancements into a consolidated, suite-

wide patch set. This release is a maintenance pack and can only be installed on top of an existing

Oracle E-Business Suite Release 12.1.1 environment. For any latest patches and changes, review

Oracle Support Note 949406.1 Oracle E-Business Suite Readme, Release 12.1.2

During this patching phase of the migration, you will execute:

· Section 1: Pre-requisite checks

· Section 2: Applying the Release Update Pack

· Section 3: Apply Post-Release Update Patch

· Section 4: Post-update steps

Note

Apply Oracle E-Business Suite 12.1.2 Release Update Pack only to an

existing Release 12.1.1 environment. While upgrading from Release 11i to

Release 12.1, complete the upgrade to R12.1.1, including the post-

upgrade steps, before you apply release 12.1.2 patch.

4.1 Pre-requisite checks

4.1.1 Cross check the database initialization parameters for 10gR2

Review Oracle Support Portal document 761570.1 and perform additional changes to database

initialization file for 10gR2, such as disabling fast validation for PL/SQL recompilations. This is a

mandatory pre-install step, before upgrading to 12.1.2.

4.1.2 Cross check the database patches for 10gR2

Refer Oracle Support Portal document 761570.1 to ensure that all patches specific to 10gR2

database release are applied on the environment, before upgrading to Release 12.1.2.

4.1.2 Cross check the OracleAS patches for EBS R12

· Review the latest copy of Oracle Support Portal document 454811.1 (for 10.1.3.5 ) or Oracle

Support Portal document 728531.1 (for 10.1.3.4 ) and apply all required patches mentioned in

the document, before upgrading to Release 12.1.2.

· Review the latest copy of Oracle Support Portal document 437878.1 and apply all required

patches that are mentioned in this document before upgrading to Release 12.1.2

53

4.2 Applying the Release Update Pack

To apply Release 12.1.2, follow these steps:

4.2.1 Apply R12 AD Patch

Apply R12.AD.B.DELTA.2 Patch 8502056 using AutoPatch, before you complete any of the other

steps in this section. R12.AD.B.Delta.2 must be applied separately and should not be merged with

any other patch. Refer to Oracle Support Portal document 879322.1 Oracle E-Business Suite DBA

Software Updates, Release 12.1.2 for more information about R12.AD.B.Delta.2.

4.2.2 Apply R12.1.2 RUP Patch

Apply Release 12.1.2 Patch 7303033 using AutoPatch and follow the instructions in the patch

readme file.

4.2.3 Apply Online Help Patch for R12.1.2

Apply the latest consolidated online help Patch 7303032 using AutoPatch and follow the instructions

in the patch readme file.

4.3 Apply Post-Release Update Patch

The post-release update patch addresses issues that were identified after the release of Release

12.1.2. Apply the following patch on top of a Release 12.1.2 instance.

· Patch 8937577 - This PA-DSS consolidated patch allows Oracle Payments customers to

benefit from the ongoing enhancements made to conform to PA-DSS requirements. For more

information, refer to Note 981033.1 Oracle Payment Application Data Security Standard

(PA-DSS) Consolidated Patch Release Notes, Release 12.1.

4.4 Post-update steps

4.4.1 Update database tier nodes with the Release 12.1.2 code level

After upgrading Release 12.1.2, perform the following post-update steps to update all database tier

nodes with the code level, provided by Release 12.1.2:

Application tier:

· As the APPLMGR user, run the environment file for the current APPL_TOP.

$. ./<APPL_TOP>/APPS<CONTEXT_NAME>.env

· Run AutoConfig on the APPL_TOP.

· Run the admkappsutil.pl utility to create the file appsutil.zip in the <INST_TOP>/admin/out

directory.

$perl <AD_TOP>/bin/admkappsutil.pl

For details on how to run AutoConfig and create appsutil.zip, refer to Oracle Support Portal

document 387859.1 Using AutoConfig to Manage System Configurations in Oracle Applications

Release 12

54

Database tier

· As the ORACLE user, run the environment file for the current ORACLE_HOME.

$cd <RDBMS ORACLE_HOME>

$. ./<RDBMS ORACLE_HOME>/<CONTEXT_NAME>.env

· Copy or FTP the appsutil.zip file to the <RDBMS ORACLE_HOME>.

· Uncompress appsutil.zip under the <RDBMS ORACLE_HOME>.

$cd <ORACLE_HOME>

$unzip -o appsutil.zip

· Run AutoConfig on the <RDBMS ORACLE_HOME>.

For details on how to run AutoConfig on the database tier and how to transfer the AutoConfig

updates from the APPL_TOP to the RDBMS ORACLE_HOME, refer to Section 2, Step 3, Patching

AutoConfig of Oracle Support Portal document 387859.1 Using AutoConfig to Manage System

Configurations in Oracle Applications Release 12

Database tier and application tier

Re-run adpreclone.pl on the database tier and the application tier. Since updates included in RUP6

were applied to the system, adpreclone must be run again to apply the updates to the clone directory

structures that were used during cloning.

perl adpreclone.pl dbTier

perl adpreclone.pl appsTier

For details on how to run adpreclone.pl, refer to Oracle Support Portal document 406982.1 Cloning

Oracle Applications Release 12 with Rapid Clone.

4.4.2 Perform NLS-related step (conditional)

If you have languages other than American English already installed in your Release 12.1.1 system,

apply the translated version(s) of Release 12.1.2 Patch 7303033 for each active language

immediately after applying the American English version of the Release 12.1.2 Patch 7303033.

If you plan to install new languages after you apply Release 12.1.2 Patch 7303033, refer to Oracle

Support Portal document: 788053.1 Oracle Applications NLS Release Notes. See the Installing

Translations section and follow the instructions for adding a new language to a Release 12.1.1

system. It is not necessary to apply the Release 12.1.2 Patch 7303033 for the new language(s).

4.4.3 Perform product-specific steps (conditional)

After you have completed the steps to update all database tier nodes with the code level, perform the

post-update steps for products licensed by you. Review Oracle Support Note 949406.1 Oracle E-

Business Suite Readme, Release 12.1.2, for product specific patches.

55

Phase 5: Upgrade E-Business Suite RDBMS from 10gR2 to

11gR2

The source environment consists of Oracle E-Business Suite Release 12.1 and the Vision Demo

database 10gR2 instance on HP Integrity servers running HP-UX 11i v3. This phase will upgrade the

database instance to Oracle RDBMS 11gR2 by first installing a new 11gR2_ORACLE_HOME, and

then upgrading the E-Business Suite R12.1 database instance using the Database Upgrade Assistant

(DBUA). Before proceeding, determine if your particular environment requires any additional steps by

thoroughly reading both the Oracle Database Upgrade Guide: 11g Release 2 (11.2), Part# E10819-

02 and Oracle Support Portal document: 1058763.1 Interoperability Notes Oracle E-Business Suite

Release R12 with Oracle 11g Release 2 (11.2.0)

During this upgrade phase of the migration, you will:

· Section 1: Prepare the database server for 11gR2 upgrade

· Section 2: Install Oracle RDBMS 11gR2 software

· Section 3: Upgrade E-business Suite Release 12.1.2 database to 11gR2

Section 2 does not depend on section 1 and can be performed first or simultaneously.

5.1 Prepare the database server for 11gR2 upgrade

This section includes the tasks to prepare the source database server for the upgrade to RDBMS

11gR2.

Download and stage the Oracle RDBMS 11gR2 and Example CD installation media for HP Integrity

server from Oracle‟s software download website,

http://www.oracle.com/technology/software/index.html.

The following steps were derived from Oracle Support Portal document: 1058763.1 Interoperability

Notes Oracle E-Business Suite Release R12 with Oracle 11g Release 2 (11.2.0), along with some

additional steps to complete the upgrade.

5.1.1 Backup the E-Business Suite environment

For rollback purposes, shutdown the E-Business Suite environment and take a full cold backup of both

the application tier and database tier.

5.1.2 Pre-requisite before the database install

Review the Step 1 Verify software versions in Before the Database Installation of Oracle Support

Portal document: 1058763.1 Interoperability Notes Oracle E-Business Suite Release R12 with Oracle

11g Release 2 (11.2.0). Make sure all the requirements are satisfied.

5.1.3 Deregister the current database server (conditional)

If you plan to change the database port, host, SID, or database name parameters on the database

server, you must also update AutoConfig on the database tier and deregister the current database

server node.

http://www.oracle.com/technology/software/index.html

56

5.1.4 Update application tier context file with new database listener port number

(conditional)

The new 11.2.0 Oracle home uses its own database listener for the database instance, replacing the

current database listener. Use the Context Editor to update the following variables in the Applications

context file on each application tier server node to reflect the 11.2.0 configuration:

Variable Name Value

s_dbhost New database hostname

s_dbdomain New database domain name

s_db_serv_sid New database SID

s_dbport New database listener port

s_apps_jdbc_connect_descriptor NULL

Review Oracle Support Portal document: 387859.1 Using AutoConfig to Manage System

Configurations in Oracle E-Business Suite Release 12 for instructions on how to update and run the

Context Editor.

Do not run AutoConfig on the application tier once the context file has been updated. The AutoConfig

run will cut off the entire application tier from the database instance until the upgrade is complete.

You will be running AutoConfig on the application tier to configure the system for the new port

number after the upgrade is finished and the new database listener is in use.

5.2 Install Oracle RDBMS 11gR2

This section includes the steps to install only the software of Oracle RDBMS 11gR2 on HP Integrity

server.

5.2.1 Prepare to create the 11.2.0 Oracle home

Read the System Considerations and Requirements section of Chapter 3 in Oracle Database

Installation Guide: 11g Release 2 (11.2) for HP-UX, Part# E10851-05

Note

Refer Oracle Support Note 983713.1; HP-UX: 11gR2 runInstaller Fails with

"An internal error occurred within cluster verification framework" to apply

HP-UX patches before starting the 11gR2 Run Installer.



11.2.0 installation media staging area, and run the Oracle Universal Installer.

DO NOT source the 10gR2 database environment file.

$ cd <11gR2_staging_directory>

$ ./runInstaller


Enterprise Edition


Name: OUIHome2

Path: <11gR2_ORACLE_HOME>




57


or discontinued.


NO





End of Installation

5.2.3 Install Oracle Database 11g Products from the 11gR2 Example CD

Review the tasks in section 3.5, of Installing Oracle Database 11g Products in the Oracle Database

Example CD Installation Guide Part#E10402-02 for your platform. Do not perform the tasks in the

Preparing Oracle Workflow Server for the Oracle Workflow Middle Tier Installation section.


11gR2 Example CD staging area and run the Oracle Universal Installer.

Make sure that:

· You DO NOT source the 10gR2 database environment file.







version>).






$ cd <11.2.0 Example CD staging_directory>

$ ./runInstaller

5.2.4 Perform RDBMS 11gR2 patch set pre-installation tasks

On the database server node, as the owner of the Oracle 11g file system and database instance,

download and unzip the 11.2.0.1 patch set for your platform. Read the patch set notes (usually

README.html). Make sure you thoroughly understand the upgrade and patch set installation process

before you begin. Check Oracle Support Portal or contact Oracle Support Services to determine any

known issues with the patch set and its interoperability with Oracle E-Business Suite R12.

5.2.5 Perform RDBMS 11gR2 patch set installation tasks

Review the tasks in the Installing the Oracle Database 11g Patch Set interactively section of the patch

set notes.


11gR2 Patch Set staging area, and run the Oracle Universal Installer directly from that staging area.

58

Make sure that:

· You DO NOT source the 10gR2 database environment file.







version>)






$ cd <11.2.0 stage directory>/Disk1

$ ./runInstaller


On the database server node, as the owner of the Oracle RDBMS file system and database instance,

run the $ORACLE_HOME/nls/data/old/cr9idata.pl script to create the

$ORACLE_HOME/nls/data/9idata directory.







$ perl cr9idata.pl

$ export ORA_NLS10=$ORACLE_HOME/nls/data/11gR2data

After creating the directory, make sure that the ORA_NLS10 environment variable is set to the full

path of the 9idata directory whenever you enable the 11gR2 Oracle home.

5.2.7 Apply additional RDBMS one-off patches


platform specific RDBMS one-off patches. Also apply OPatch executable for 11.2.0 before

applying this additional RDBMS patch.

Apply one-off Patch 9218789 N-APPLY BUNDLE PATCH FOR RDBMS 11.2.0.1 WITH EBS RELEASE

12.

Do not run any of the post install instructions as those will be done after the upgrade.

Check the OPatch inventory before and after applying patches. Review all the readme files before

applying any patch and review the logs for any discrepancy after applying each patch. If any are

found, resolve them first before continuing to the next step.

5.2.8 Install the latest available patch set release and any required patches

(conditional)

Once you have installed the major Oracle Database 11g software, check to see if there is a patch set

release and/or critical patch update to be installed. Currently, the only patch set level of Oracle

Database 11g Release 2 (11.2.0) certified with Oracle E-Business Suite Release 12 is 11.2.0.1.

59

The latest patch set release and critical patch update for Oracle Database 11g Release 1 should be

installed prior to upgrading your databases. Refer to the specific patch release and critical patch


5.3 Upgrade E-Business Suite RDBMS to 11gR2

This section includes the tasks to upgrade the Oracle E-Business Suite database from 10gR2 to

11.2.0. During this process, the environment will be unavailable until the upgrade has completed.

5.3.1 Prepare to upgrade

Review Chapter 2 of Oracle Database Upgrade Guide: 11g Release 2 (11.2), Part# E10819-02.

Take note of the section pertaining to the Database Upgrade Assistant (DBUA). Also review Oracle

Support Portal document: 1058763.1 Interoperability Notes Oracle E-Business Suite Release R12 with

Oracle 11g Release 2 (11.2.0), to prepare for the upgrade.

Make sure that you unset the TNS_ADMIN environment variable.

Verify that the /etc/oratab file has correct entries for the 11gR2 Database and 11gR2 Oracle Home.

# cat /etc/oratab

<SID>:<11gR2_ORACLE_HOME>:N:

5.3.2 Stop the Applications server processes and the database listener

Stop applications server services on the Applications Administrator Service Node.

# su – applmgr

$ cd $COMMON_TOP/admin/scripts/<SID>_<HOSTNAME>

$ ./adstpall.sh apps/<apps_password>

Stop database listener on the database node.

# su – oracle


5.3.3 Drop SYS.ENABLED$INDEXES (conditional)

If the SYS.ENABLED$INDEXES table exists, connect to the database as SYSDBA and run the following

command to drop it:

SQL> drop table sys.enabled$indexes;

5.3.4 Run the pre-upgrade information tool

The following steps were derived from the Oracle Database Upgrade Guide: 11g Release 2 (11.2),

Part Number E17222-05. If you plan to change the PL/SQL compilation mode, disable the

compilation of objects. Run the pre-upgrade information tool using the following steps:

· Logon as the owner of the 11gR2_RDBMS file system and source the environment.

· Copy and run the utlu112i.sql from <upg_1120x_log_directory>.

$ cp <11g_ORACLE_HOME>/rdbms/admin/utlu112i.sql \

<upg_1120_log_directory>

60

· Execute the utlu112i.sql by connecting to 11gR2 Database with SYSDBA privileges. Spool the

output of this execution into utlu112i.out.

$ cd <upg_1120_log_directory>


SQL> spool utlu112i.out

SQL> @utlu112i.sql

SQL> spool off

Review the output for any errors or warnings and make any necessary changes before proceeding on

to the next step. For further details, see Oracle Support Portal document: 884522.1 How to

Download and Run Oracle's Database Pre-Upgrade Utility.

5.3.5 Upgrade database

Make sure that the Applications server processes and the 11gR2 database listener have been

stopped. Set the environment variable ORACLE_HOME to point to the 11gR2_ORACLE_HOME

directory created in the „Step 5.2 Install Oracle RDBMS 11gR2‟ and run the Oracle Database

Upgrade Assistant (DBUA) against the Applications 11i database.

Start an Xterm session on the source database server as the “oracle” user, export the new

ORACLE_HOME, and run the DBUA from $ORACLE_HOME/bin.

Before performing any upgrade or maintenance operation, you must have the _disable_fast_validate

parameter in your initialization file.

When running DBUA, set the _disable_fast_validate parameter using the following command:


$ cd $ORACLE_HOME/bin

$ ./ dbua -initParam "_disable_fast_validate=TRUE"

When upgrading all statistics tables, note that Oracle E-Business Suite has only one statistics table,

APPLSYS.FND_STATTAB that needs to be upgraded.

If you plan to change the PL/SQL compilation mode, disable the compilation of objects.

Select the 11gR2 database from the list of available databases.

Monitor the progress of the DBUA. At the end of the upgrade process, DBUA will automatically start

the instance.

The upgrade log files are located in $<11gR2_ORACLE_HOME>/cfgtoollogs/dbua/<SID>/upgrade.

Review “UpgradeResults.html” and make any necessary changes.

5.3.6 Modify initialization parameters

The newly installed Oracle 11gR2 will not be tuned for E-Business Suite. Review the Oracle Support

Portal document: 396009.1 Database Initialization Parameters for Oracle Applications Release 12.

Make sure you use the following sections as a guideline for modifying the initialization parameter file:

· Common database initialization parameters

· Release-specific database initialization parameters for 11gR2

· Database initialization parameter sizing

61

Note: During the database startup, Oracle DB 11g first looks in

$ORACLE_HOME/dbs for the spfile (spfile<SID>.ora) and if not found the

RDBMS will attempt to load the pfile (init<SID>.ora) file. After the 11gR2

upgrade, both pfile and spfile have the same values. You are not confined

to using the parameter files generated by the database upgrade assistant. It

will be easier to modify the pfile and then recreate the spfile after all the

changes are in and the database started. Make sure that you rename the

spfile<SID>.ora and backup the init<SID>.ora before modifying.

Ensure the parameter "_disable_fast_validate=TRUE" is in the initialization file. This line will have to

be commented out after the upgrade and any other maintenance procedures.

If you encounter the error:

ORA-04030: out of process memory when trying to allocate 822904 bytes (pga heap, kco buffer)

ORA-07445: exception encountered: core dump [dbgtfdFileWrite()+48]

then set the _pga_max_size initialization parameter to a larger value as follows:

_pga_max_size=104857600

Restart your database.

If native compilation of PL/SQL code is disabled in your database instance, ignore the initialization

parameters that pertain to the native compilation of PL/SQL code. Ensure that the temporary

tablespace is properly defined. Make the appropriate modification and restart the database.

5.3.7 Perform 11.2.0 patch set post-installation tasks

Run only the catmgdidcode.sql and utlrp.sql scripts for the post install instructions in patch 9218789.

The other scripts are run as part of the DBUA upgrade.

5.3.8 Validate invalid objects within the database.

Bounce the database and run the SQL script to validate invalid objects within the database.

SQL> shutdown

SQL> startup


Use the following queries to track recompilation progress:

Query returning the number of invalid objects remaining. This number should decrease with time.

SQL> SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);

Query returning the number of objects compiled so far. This number should increase with time.

SQL> SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;

5.3.9 Natively compile PL/SQL code (optional)

You can choose to run Oracle E-Business Suite Release 11i PL/SQL database objects in natively

compiled mode with Oracle Database 11gR2. For detailed steps, refer to the Compiling PL/SQL

Code for Native Execution section of Chapter 11 of Oracle Database PL/SQL User's Guide and

Reference 11g Release 2 (11.2).

When modifying the initialization parameters pertaining to the PL/SQL native compilation, refer to

Oracle Support Portal document: 396009.1, Database Initialization Parameter Settings for Oracle

Applications Release 12 as a guideline.

62

5.3.10 Start the new database listener (conditional)

Since AutoConfig has not yet been implemented, start the listener with the lsnrctl executable. See the

Oracle Database Net Services Administrator's Guide, 11g Release 2 (11.2) for more information.

Prior to starting the listener, perform these additional steps:

Create the $TNS_ADMIN directory in the 11gR2_ORACLE_HOME.

$ export ORACLE_HOME=<11g_ORACLE_HOME>



$ export ORA_NLS10=$ORACLE_HOME/nls/data/<11gR2 data>

$ mkdir –p $ORACLE_HOME/network/admin/<SID>_<hostname>


Copy the contents of 11gR2_TNS_ADMIN to $TNS_ADMIN.

$ cp <11gR2_Oracle_Home>/network/admin/<SID>_<hostname>/*

$TNS_ADMIN

Start the new Oracle Net Listener.


5.3.11 Run adgrants.sql (conditional)


node. Connect to the database as SYSDBA and run the script using the following command:

$ sqlplus "/ as sysdba" @adgrants.sql (or adgrants_nt.sql)

[APPS schema name]

Verify the syntax and usage of adgrants.sql. Older versions of adgrants.sql require the APPLSYS

schema name parameter to be passed instead of APPS.

5.3.12 Set CTXSYS parameter

Connect to the database as SYSDBA and run the following command:


SQL> exec ctxsys.ctx_adm.set_parameter('file_access_role', 'public');

5.3.13 Validate Workflow ruleset

On the administration server node, connect to the database as APPS and run the

$FND_TOP/patch/115/sql/wfaqupfix.sql script using the following command:

$ sqlplus [APPS user]/[APPS password] @wfaqupfix.sql\

[APPLSYS user] [APPS user]

5.3.14 Implement and run AutoConfig

Configure and run AutoConfig in the new Oracle home on the database server node. If the database

listener of the new Oracle home is defined differently than the old Oracle home, you must also run

AutoConfig on each application tier server node to update the system with the new listener.

For instructions on how to implement and run AutoConfig, see Oracle Support Portal document:

387859.1 Using AutoConfig to Manage System Configurations in Oracle E-Business Suite Release

12. Section 3.2 explains how to generate a context file on the database tier.

Shut down all processes, including the database and the listener, and restart them to load the new

environment settings.

http://otn.oracle.com/documentation/database10gr2.html

63

After creating the XML context file, ensure the variable s_jretop points to a proper JRE directory.

This task will migrate AutoConfig on the DB Tier.

Note:

An improper entry introduced into the context file can render the

applications environment inoperable. Always make a backup prior to

editing the context file.

Run AutoConfig to generate a new 11g environment file located in the <11g_ORACLE_HOME>

directory.


$ ./adconfig.sh \

contextfile=<11g_ORACLE_HOME>/appsutil/<SID>_<hostname>.xml \


Review log file for any failures, errors, or warnings and resolve those issues before continuing.

Shut down the 11g database and listener, source the new database environment file, and then start

up the listener and the 11g database.



SQL> exit


# su – oracle

$ . <11g_ORACLE_HOME>/<SID>_<hostname>.env



SQL> startup



node. Connect to the database as SYSDBA and use the following commands to run adstats.sql in

restricted mode as adstats.sql has to be run in restricted mode:


SQL> alter system enable restricted session;

SQL> @adstats.sql


SQL> alter system disable restricted session;

SQL> exit;

Make sure that default temporary tablespace has at least 1.5 GB of free.

5.3.16 Create Demantra privileges (conditional)

If you are using Demantra, perform the steps explained Oracle Support Portal document: 730883.1

Additional Database Privilege needed for Demantra Schema when Running on Oracle 11g Database.

64


If you have different configuration for the database listener in the new Oracle home, then you must re-

create any custom self-referential database links that exist in the Applications database instance.

Verify the existing database links. Connect to the Applications database instance as APPS and run the

following query:



If EDW_APPS_TO_WH and APPS_TO_APPS database links exist, then they should have been

updated with the new port number by AutoConfig in the step „5.3.14 Implement and run AutoConfig‟.

For custom self-referential database links (if any) in the database instance, use the following

commands to drop and re-create them:



SQL> create database link <custom database link> connect to

<user> identified by <password> using


(PORT=<port number>))(CONNECT_DATA=(SID=<ORACLE_SID>)))';

where <custom database link>, <user>, <password>, <hostname>, <port number>, and

<ORACLE_SID> reflect the new Oracle Net listener for the database instance.

5.3.18 Re-create grants and synonyms

You must re-create the grants and synonyms in the APPS schema as Oracle Database 11g Release 1

(11.2) contains new functionality for grants and synonyms compared to previous database releases.

Log on the administration server node, as the owner of the Applications file system, run adadmin and

select the Recreate grants and synonyms for APPS schema task from the Maintain Applications

Database Objects menu.

· Change directory to $ORACLE_HOME/rdbms/admin.

· Start SQL*Plus session with sysdba privilege and shutdown the database.

· Startup the database using the upgrade option.

SQL> startup upgrade

· Run the utlirp.sql from the directory where you launch the SQL*Plus session.

SQL> @utlirp.sql

· Bounce the database and run the utlrp.sql from the directory where you launch the SQL*Plus

session.

SQL> @utlrp.sql

· Check invalid objects

SQL> select count(*) from dba_objects \

where status = ‘INVALID’;

· Use adadmin on the Administration server node to re-create grants and synonyms.

# su – applmgr

$ . <APPL_TOP>/APPS<SID>_<hostname>.env

$ adadmin

Maintain Applications Database Entities

Re-create grants and synonyms for APPS schema

65

5.3.19 Recreate spfile from pfile

$ cd $ORACLE_HOME/dbs


SQL> CREATE SPFILE FROM PFILE = '<ORACLE_HOME>/dbs/init<SID>.ora’;

5.3.20 Restart Applications server processes

Restart all the Application tier server processes that you shut down previously. You should start the

Oracle Net listener for the database instance, as well as the database instance itself in the 11.2

Oracle home.

5.3.21 Synchronize Workflow views

Log on to Oracle E-Business Suite with the "System Administrator" responsibility.

Navigate to Click Requests > Run > Single Request and the OK button. Enter the following

parameters:

Request Name = Workflow Directory Services User/Role Validation

p_BatchSize = 10000

p_Check_Dangling = Yes

Add missing user/role assignments = Yes

Update WHO columns in WF tables = No

Click "OK" and "Submit".

5.3.22 Validate environment and perform a full backup

After successfully validating the E-Business Suite environment as per Appendix G, perform a full

backup to complete the upgrade to 11gR2 phase.

This completes the upgrade and migration of Oracle Applications 11i running on HP AlphaServer

systems running Tru64 UNIXs to Oracle E-Business Suite Release 12.1.2 running on HP Integrity

servers.

66

Appendix A: Kernel parameters

Table 10 is a list of HP-UX 11i v3 kernel parameters. These are only suggested kernel settings and

should be considered a starting point for additional operation system tuning.

Table 10. List of 11i v3 kernel parameters

MAXTSIZ 100663296

MAXFILES_LIM 4096

NPROC 4200

KSI_ALLOC_MAX (NPROC*8)

MAX_THREAD_PROC 1200

MAXDSIZ 1073741824

MAXDSIZ_64BIT 4294967296

MAXFILES 2048

MAXSSIZ 8388608

MAXSSIZ_64BIT 268435456

MAXUPRC 256

MSGMNB 16384

MSGMNI 512

MSGTQL 1024

NFLOCKS 4096

NINODE (2*NPROC+1024)

NKTHREAD (NPROC *2)

SEMMNS 4096

SEMMNI 2048

SEMMNU 256

SEMVMX 32,767

SHMMAX For the Database tier up to 50% of available physical memory or

1,073,741,824, whichever is greater.

The Applications tier normally requires no more than 1GB.

SHMMNI 400

SHMSEG 300

SWCHUNK 2048

67

Appendix B: Pre-Upgrade Information Utility output file

This is the Pre-Upgrade Information Utility output file generated in section 1.3.3, Prepare for

upgrading the database instance.

SQL> @utlu102i.sql

Oracle Database 10.2 Upgrade Information Utility 07-02-2010 18:32:27

.

**********************************************************************

Database:

**********************************************************************

--> name: VIS

--> version: 9.2.0.6.0

--> compatible: 9.2.0

--> blocksize: 8192

.

**********************************************************************

Logfiles: [make adjustments in the current environment]

**********************************************************************

--> The existing log files are adequate. No changes are required.

.

**********************************************************************

Tablespaces: [make adjustments in the current environment]

**********************************************************************

--> SYSTEM tablespace is adequate for the upgrade.

.... minimum required size: 7548 MB

--> APPS_UNDOTS1 tablespace is adequate for the upgrade.


--> TEMP tablespace is adequate for the upgrade.


--> APPS_TS_QUEUES tablespace is adequate for the upgrade.


--> APPS_TS_TX_DATA tablespace is adequate for the upgrade.


--> ODM tablespace is adequate for the upgrade.


.

**********************************************************************

Update Parameters: [Update Oracle Database 10.2 init.ora or spfile]

**********************************************************************

WARNING: --> "streams_pool_size" is not currently defined and needs a value of

at least 50331648

WARNING: --> "large_pool_size" needs to be increased to at least 8388608

WARNING: --> "session_max_open_files" needs to be increased to at least 20

.

**********************************************************************

Renamed Parameters: [Update Oracle Database 10.2 init.ora or spfile]

**********************************************************************

-- No renamed parameters found. No changes are required.

.

**********************************************************************

Obsolete/Deprecated Parameters: [Update Oracle Database 10.2 init.ora or spfile]

**********************************************************************

--> "optimizer_max_permutations"

--> "row_locking"

--> "undo_suppress_errors"

--> "max_enabled_roles"

--> "enqueue_resources"

--> "sql_trace"

.

**********************************************************************

Components: [The following database components will be upgraded or installed]

**********************************************************************

--> Oracle Catalog Views [upgrade] VALID

--> Oracle Packages and Types [upgrade] VALID

--> JServer JAVA Virtual Machine [upgrade] VALID

68

...The 'JServer JAVA Virtual Machine' JAccelerator (NCOMP)

...is required to be installed from the 10g Companion CD.

--> Oracle XDK for Java [upgrade] VALID

--> Oracle Java Packages [upgrade] VALID

--> Oracle Text [upgrade] VALID

--> Oracle XML Database [install]

--> Real Application Clusters [upgrade] INVALID

--> OLAP Analytic Workspace [upgrade] UPGRADED

--> OLAP Catalog [upgrade] VALID

--> Oracle OLAP API [upgrade] UPGRADED

--> Oracle interMedia [upgrade] VALID

...The 'Oracle interMedia Image Accelerator' is

...required to be installed from the 10g Companion CD.

--> Spatial [upgrade] VALID

.

**********************************************************************

Miscellaneous Warnings

**********************************************************************

WARNING: --> Passwords exist in some database links.

.... Passwords will be encrypted during the upgrade.

.... Downgrade of database links with passwords is not supported.

WARNING: --> Deprecated CONNECT role granted to some user/roles.

.... CONNECT role after upgrade has only CREATE SESSION privilege.

WARNING: --> Database contains stale optimizer statistics.

.... Refer to the 10g Upgrade Guide for instructions to update

.... statistics prior to upgrading the database.

.... Component Schemas with stale statistics:

.... SYS

.... OLAPSYS

.... MDSYS

WARNING: --> Database contains INVALID objects prior to upgrade.

.... USER APPLSYS has 1 INVALID objects.

.... USER APPS has 2 INVALID objects.

.

**********************************************************************

SYSAUX Tablespace:

[Create tablespace in the Oracle Database 10.2 environment]

**********************************************************************

--> New "SYSAUX" tablespace

.... minimum required size for database upgrade: 500 MB

.

PL/SQL procedure successfully completed.

SQL> exit

The following steps were performed to address the Miscellaneous Warnings section

of the output file:

Issues requiring further analysis prior to upgrading

If the Pre-Upgrade Utility displays a warning about any of the following issues, then further analysis of

the database is recommended prior to upgrading to Oracle Database 11g:

· Deprecated CONNECT Role

· Database Links With Passwords

· TIMESTAMP WITH TIMEZONE Datatype

· Optimizer Statistics

Deprecated CONNECT Role

Each user should ONLY have those privileges appropriate to the tasks he needs to do. Least privilege

mitigates risk by limiting privileges; so that it remains easy to do what is needed while concurrently

reducing the ability to do inappropriate things, either inadvertently or maliciously.

69

The CONNECT role privilege reduction feature reduces the number of privileges granted to the

connect role to only one:

CREATE SESSION

The seven other privileges have been removed from the CONNECT role:

1. CREATE VIEW

2. CREATE TABLE

3. CREATE SYNONYM

4. CREATE CLUSTER

5. CREATE DATABASE LINK

6. CREATE SEQUENCE

7. ALTER SESSION

After upgrading to Oracle Database 11g, the CONNECT role will only have the CREATE SESSION

privilege; the other privileges granted to the CONNECT role in earlier releases will be revoked during

the upgrade. To identify which users and roles in your database are granted the CONNECT role, use

the following query:

SELECT grantee FROM dba_role_privs

WHERE granted_role = 'CONNECT' and

grantee NOT IN (

'SYS', 'OUTLN', 'SYSTEM', 'CTXSYS', 'DBSNMP',

'LOGSTDBY_ADMINISTRATOR', 'ORDSYS',

'ORDPLUGINS', 'OEM_MONITOR', 'WKSYS', 'WKPROXY',

'WK_TEST', 'WKUSER', 'MDSYS', 'LBACSYS', 'DMSYS',

'WMSYS', 'OLAPDBA', 'OLAPSVR', 'OLAP_USER',

'OLAPSYS', 'EXFSYS', 'SYSMAN', 'MDDATA',

'SI_INFORMTN_SCHEMA', 'XDB', 'ODM');

GRANTEE

------------------------------------------

EUL_US

SSOSDK

WEBSYS

PROJMFG

SERVICES

WIRELESS

EDWEUL_US

7 rows selected.

If users or roles require privileges other than CREATE SESSION, then grant the specific required

privileges prior to upgrading. The upgrade scripts adjust the privileges for the Oracle-supplied users.

Database links with passwords

During the upgrade to Oracle Database 11g, any passwords in database links will be encrypted. To

downgrade back to the original release, all of the database links with encrypted passwords must be

dropped prior to the downgrade. Consequently, the database links will not exist in the downgraded

database. If you anticipate a requirement to be able to downgrade back to your original release,

then save the information about affected database links from the SYS.LINK$ table, so that you can

recreate the database links after the downgrade.

TIMESTAMP WITH TIMEZONE datatype

The time zone files that are supplied with Oracle Database 11g have been updated from version 3 to

version 4 to reflect changes in transition rules for some time zone regions. The changes may affect

existing data of TIMESTAMP WITH TIME ZONE datatype. To preserve this TIMESTAMP data for

updating according to the new time zone transition rules, you must run the utltzuv2.sql script on

70

the database before upgrading. This script is located in the new 11g ORACLE_HOME/rdbms/admin

directory. This script analyzes your database for TIMESTAMP WITH TIME ZONE columns that are

affected by the updated time zone transition rules.

See also: Oracle Database Globalization Support Guide for a detailed description of the

utltzuv.sql script

If the utltzuv2.sql script identifies columns with time zone data affected by a database upgrade,

then back up the data in character format before you upgrade the database. After the upgrade, you

must update the tables to ensure that the data is stored based on the new rules. If you export the

tables before upgrading and import them after the upgrade, the conversion will happen automatically

during the import.

Alternatively, create tables with the time zone information in character format (for example,

TO_CHAR(column, 'YYYY-MM-DD HH24.MI.SSXFF TZR'), and recreate the TIMESTAMP data

from these tables after the upgrade.

Optimizer statistics

When upgrading to Oracle Database 11g, optimizer statistics are collected for dictionary tables that

lack statistics. This statistics collection can be time consuming for databases with a large number of

dictionary tables, but statistics gathering only occurs for those tables that lack statistics or are

significantly changed during the upgrade.

To decrease the amount of downtime incurred when collecting statistics, you can collect statistics prior

to performing the actual database upgrade. As of Oracle Database 10g Release 10.1, Oracle

recommends that you use the DBMS_STATS.GATHER_DICTIONARY_STATS procedure to gather

these statistics. For example, you can enter the following:

EXEC DBMS_STATS.GATHER_DICTIONARY_STATS;

If you are using Release 9.0.1 or 9.2.0, then you should use the

DBMS_STATS.GATHER_SCHEMA_STATS procedure to gather statistics.

The following warning was also generated by the Pre-Upgrade Information Utility report.

WARNING: --> Database contains stale optimizer statistics.

Refer to the 11g Upgrade Guide for instructions to update statistics prior to upgrading the database.

Component Schemas with stale statistics:

SYS

MDSYS

The following steps were used to optimize statistics. $ cd /tmp

$ sqlplus ‘/ as sysdba’

spool opt_stats.out

exec dbms_stats.gather_schema_stats('WMSYS',options=>'GATHER', -

estimate_percent => DBMS_STATS.AUTO_SAMPLE_SIZE, -

method_opt => 'FOR ALL COLUMNS SIZE AUTO', cascade => TRUE);

exec dbms_stats.gather_schema_stats('MDSYS',options=>'GATHER', -



exec dbms_stats.gather_schema_stats('CTXSYS',options=>'GATHER', -



exec dbms_stats.gather_schema_stats('XDB',options=>'GATHER', -


71


exec dbms_stats.gather_schema_stats('WKSYS',options=>'GATHER', -



exec dbms_stats.gather_schema_stats('LBACSYS',options=>'GATHER', -



exec dbms_stats.gather_schema_stats('ORDSYS',options=>'GATHER', -



exec dbms_stats.gather_schema_stats('ORDPLUGINS',options=>'GATHER', -



exec dbms_stats.gather_schema_stats('SI_INFORMTN_SCHEMA',-

options=>'GATHER', estimate_percent => DBMS_STATS.AUTO_SAMPLE_SIZE, -


exec dbms_stats.gather_schema_stats('OUTLN',options=>'GATHER', -



exec dbms_stats.gather_schema_stats('DBSNMP',options=>'GATHER', -



exec dbms_stats.gather_schema_stats('SYSTEM',options=>'GATHER', -



exec dbms_stats.gather_schema_stats('SYS',options=>'GATHER', -

estimate_percent => DBMS_STATS.AUTO_SAMPLE_SIZE, -method_opt => 'FOR ALL COLUMNS

SIZE AUTO', cascade => TRUE);

SQL> spool off

72

Appendix C: Post-Upgrade Information Utility output file

This is the Post-Upgrade Information Utility output file generated in section 1.3.4, Upgrade the

Applications 11i database.

Upgrade Results

DBUA failed to upgrade the database or some of its components. See upgrade detail.

Source Database Target Database

Name: VIS VIS Version: 9.2.0.6.0 10.2.0.4 Oracle Home: /oracle/EBS/visdb/9.2.0 /oracle/EBS/visdb/10.2.0.4

Database Backup

Backup Location Available Space (MB) Space Required (MB) /oracle/EBS/VIS/backup 131451 61896

Upgrade Details

The following is a summary of the steps performed during the database upgrade. Log files for all

the steps, as well as this summary, are available at

"/oracle/EBS/visdb/10.2.0.4/cfgtoollogs/dbua/VIS/upgrade0".

Step Name Log File Name Status Database Backup Backup.log Successful*

Pre Upgrade PreUpgrade.log Successful Oracle Server Oracle_Server.log Successful JServer JAVA Virtual Machine Oracle_Server.log Successful Oracle XDK for Java Oracle_Server.log Successful Oracle Java Packages Oracle_Server.log Successful Oracle Text Oracle_Server.log Successful Oracle XML Database Oracle_Server.log Successful Real Application Clusters Oracle_Server.log Failed OLAP Analytic Workspace Oracle_Server.log Successful OLAP Catalog Oracle_Server.log Successful Oracle OLAP API Oracle_Server.log Successful Oracle interMedia Oracle_Server.log Successful Spatial Oracle_Server.log Successful Enterprise Manager Repository emRepository.log Successful Post Upgrade PostUpgrade.log Successful* Enterprise Manager Configuration emConfigUpgrade.log Successful* Generate Summary generateSummary.log Successful

73

*Some information about the step is available.

Step Execution Information: Database Backup The Database can be restored by running the following script

"/oracle/EBS/VIS/backup/VIS_restore.sh" from the backup location. NOTE:

This operation will remove all the upgrade changes made by the Database

Upgrade Assistant.

Post Upgrade A persistent initialization parameter file (spfile) has been created at

the following location: /oracle/EBS/visdb/10.2.0.4/dbs/spfileVIS.ora.

Enterprise Manager Configuration The Database will be managed locally using the Oracle Enterprise Manager

Database Control. The Database Control URL is Enterprise manager configuration succeeded with the following warning -

Error securing Database Control, Database Control has been brought up in

non-secure mode. To secure the Database Control execute the following

command(s): 1) Set the environment variable ORACLE_SID to VIS 2)

/oracle/EBS/visdb/10.2.0.4/bin/emctl stop dbconsole 3)

/oracle/EBS/visdb/10.2.0.4/bin/emctl config emkey -repos -sysman_pwd <

Password for SYSMAN user > 4) /oracle/EBS/visdb/10.2.0.4/bin/emctl secure

dbconsole -sysman_pwd < Password for SYSMAN user > 5)

/oracle/EBS/visdb/10.2.0.4/bin/emctl start dbconsole To secure Em Key,

run /oracle/EBS/visdb/10.2.0.4/bin/emctl config emkey -remove_from_repos

-sysman_pwd < Password for SYSMAN user >

Initialization Parameter changes The following changes have been made in the initialization parameters:

Parameters Added: Name Value streams_pool_size 50331648 large_pool_size 8388608 session_max_open_files 20

Obsolete Parameters Removed: Name optimizer_max_permutations row_locking undo_suppress_errors max_enabled_roles enqueue_resources sql_trace

Enterprise Manager The Database will be managed locally using the Oracle Enterprise Manager Database Control. The Database Control URL is

74

Appendix D: XTTS example files

Table 11. XTTS example files

File Description

aucrdb.sql Script that creates the target database instance with

the appropriate tablespace and file structure

auxttsread.sql Script that converts the transportable tablespace set

in the source database to read only

auxttswrite.sql Script that converts the transportable tablespace set

in the source database back to read write

audeftbsp.sql Script that converts the users to their corresponding

default tablespaces.

auexpxtts.dat Export parameter file for the transportable tablespace

set.

auexpglb.dat Export parameter file for the global temporary tables.

auexpsys.dat Export parameter file for the SYSTEM tablespace

schemas.

auexpmsc.dat Export parameter file for the other objects.

aurman.dat Recovery manager parameter file to convert the

endian format of data files.

auimpxtts.dat Import parameter file for the transportable tablespace

set.

auimpmsc.dat Import parameter file for the other objects

auimpglb.dat Import parameter file for the global temporary tables.

auimpsys.dat Import parameter file for the SYSTEM tablespace

schemas.

auque2.sql

Enable the Advanced Queue settings in the target

database instance. Patch 4872830 contains

auque1.sql, which in turn generates auque2.sql.

Please review the following example file created above:

aucrdb.sql

REM BEFORE RUNNING THE SCRIPT YOU MUST REVIEW

REM IT FOR THE FOLLOWING:

REM - Database Characterset information

REM - Location and size of the data files

REM - Undo Tablespace information

REM - Temporary Tablespace information

CREATE DATABASE

75

MAXDATAFILES 512

CHARACTER SET UTF8

NATIONAL CHARACTER SET AL16UTF16

LOGFILE

GROUP 1 ('/oracle/EBS/db/apps_st/data/log3.dbf') SIZE 1024M,

GROUP 2 ('/oracle/EBS/db/apps_st/data/log2.dbf') SIZE 1024M,

GROUP 3 ('/oracle/EBS/db/apps_st/data/log1.dbf') SIZE 1024M

DATAFILE

'/oracle/EBS/db/apps_st/data/sys1.dbf' SIZE 1500M,






'/oracle/EBS/db/apps_st/data/sys7.dbf' SIZE 1000M

SYSAUX DATAFILE

'/oracle/EBS/db/apps_st/data/sysaux01.dbf' SIZE 1024M

UNDO TABLESPACE "APPS_UNDOTS1"

DATAFILE

'/oracle/EBS/db/apps_st/data/undo01.dbf' SIZE 1000M,



'/oracle/EBS/db/apps_st/data/undo04.dbf' SIZE 1000M

EXTENT MANAGEMENT LOCAL

DEFAULT TEMPORARY TABLESPACE "TEMP"

TEMPFILE

'/oracle/EBS/db/apps_st/data/tmp1.dbf' SIZE 2000M

EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M

/

ALTER DATABASE DEFAULT TEMPORARY TABLESPACE "TEMP";

prompt

prompt Ignore any errors related to the setting

prompt of the default temporary tablespace

prompt

above:

auexpxtts.dat

directory=dmpdir

dumpfile=xttsmeta%U.dmp

filesize=10485760000

logfile=expxtts.log

transport_tablespaces=

APPS_TS_ARCHIVE,

APPS_TS_MEDIA,

APPS_TS_NOLOGGING,

APPS_TS_QUEUES,

APPS_TS_SEED,

APPS_TS_SUMMARY,

APPS_TS_TX_DATA,

APPS_TS_TX_IDX,

APPS_TS_TX_INTERFACE,

ODM,

OLAP,

76

OWAPUB,

PORTAL,

SYNCSERVER

auexpmsc.dat

directory=dmpdir

dumpfile=xttsmsc%U.dmp

full=y

filesize=1048576000

logfile=expmsc.log

exclude=TABLE,INDEX,CONSTRAINT,COMMENT,RLS_POLICY,

MATERIALIZED_VIEW,MATERIALIZED_VIEW_LOG

auexpsys.dat

directory=dmpdir

dumpfile=xttssys%U.dmp

filesize=1048576000

logfile=expsys.log

SCHEMAS=

SYSTEM,

SYS,

PTG,

AD_MONITOR,

WIRELESS,

CTXTEST,

ORDPLUGINS,

TSMSYS,

DMSYS,

ORDSYS,

DLD,

WEBSYS,

PROJMFG,

ANONYMOUS,

XDB,

CSDUMMY,

MDSYS,

TRACESVR,

AOLDEMO,

DIP,

PTE,

MDDATA,

ORACLE_OCM,

SI_INFORMTN_SCHEMA,

REPADMIN,

OUTLN,

DBSNMP

auexpglb.dat

file=gtab.dmp

filesize=10485760000

77

log=expgtab.log

tables=(

'ZPB.ZPB_DC_VAL_RESULTS_GT',

'AK.AK_LOADER_TEMP',

'APPLSYS.AD_GENERIC_TEMP',

'GL.GL_AHE_DETAIL_RANGES_GT',

'APPLSYS.AD_PROCESSED_FILES_TEMP',

'JTF.JTFB_TEMP_BIN',

……

Similar global temporary tables

……

'WSH.WSH_REGIONS_GLOBAL',

'WSH.WSH_TMP',

'APPS.IEC_TC_TZ_PAIRS_CACHE',

'APPS.IEC_TZ_MAPPING_CACHE',

'APPS.IEC_TZ_OFFSET_MAP_CACHE',

'APPS.IEC_VAL_ENTRY_CACHE',

'MSC.MSC_SOURCING_TRANSACTIONS',

'MSC.MSC_PLANNING_ORGS')

auxttsread.sql

REM

REM Ensure that you have no Apps processes running

REM before running this script

REM

connect / as sysdba;

alter tablespace APPS_TS_ARCHIVE read only;

alter tablespace APPS_TS_MEDIA read only;

alter tablespace APPS_TS_NOLOGGING read only;

alter tablespace APPS_TS_QUEUES read only;

alter tablespace APPS_TS_SEED read only;

alter tablespace APPS_TS_SUMMARY read only;

alter tablespace APPS_TS_TX_DATA read only;

alter tablespace APPS_TS_TX_IDX read only;

alter tablespace APPS_TS_TX_INTERFACE read only;

alter tablespace ODM read only;

alter tablespace OLAP read only;

alter tablespace OWAPUB read only;

alter tablespace PORTAL read only;

alter tablespace SYNCSERVER read only;

aurman.dat

CONVERT TABLESPACE

APPS_TS_ARCHIVE,

APPS_TS_MEDIA,

APPS_TS_NOLOGGING,

APPS_TS_QUEUES,

APPS_TS_SEED,

APPS_TS_SUMMARY,

APPS_TS_TX_DATA,

APPS_TS_TX_IDX,

78

APPS_TS_TX_INTERFACE,

ODM,

OLAP,

OWAPUB,

PORTAL,

SYNCSERVER

TO PLATFORM 'HP-UX IA (64-bit)'

DB_FILE_NAME_CONVERT

'/oracle/EBS/visdata/archive1.dbf','/db/trudata/archive1.dbf',

'/oracle/EBS/visdata/archive2.dbf','/db/trudata/archive2.dbf',

'/oracle/EBS/visdata/media1.dbf','/db/trudata/media1.dbf',



'/oracle/EBS/visdata/nologging1.dbf','/db/trudata/nologging1.dbf',

'/oracle/EBS/visdata/queues1.dbf','/db/trudata/queues1.dbf',

'/oracle/EBS/visdata/queues2.dbf','/db/trudata/queues2.dbf',

'/oracle/EBS/visdata/reference1.dbf','/db/trudata/reference1.dbf',

'/oracle/EBS/visdata/reference2.dbf','/db/trudata/reference2.dbf',

'/oracle/EBS/visdata/summary1.dbf','/db/trudata/summary1.dbf',





'/oracle/EBS/visdata/tx_data1.dbf','/db/trudata/tx_data1.dbf',











'/oracle/EBS/visdata/tx_idx1.dbf','/db/trudata/tx_idx1.dbf',











'/oracle/EBS/visdata/apps_ts_tx_interface.dbf','/db/trudata/apps_ts_tx_interface.dbf',

'/oracle/EBS/visdata/odm.dbf','/db/trudata/odm.dbf',

'/oracle/EBS/visdata/olap.dbf','/db/trudata/olap.dbf',

'/oracle/EBS/visdata/owa1.dbf','/db/trudata/owa1.dbf',

'/oracle/EBS/visdata/portal.dbf','/db/trudata/portal.dbf',

'/oracle/EBS/visdata/mobile01.dbf','/db/trudata/mobile01.dbf';

79

auimpxtts.dat

directory=dmpdir

dumpfile=xttsmeta01.dmp

logfile=impxtts.log

transport_datafiles=

'/oracle/EBS/db/apps_st/data/mobile01.dbf',

'/oracle/EBS/db/apps_st/data/olap.dbf',

'/oracle/EBS/db/apps_st/data/queues1.dbf',

'/oracle/EBS/db/apps_st/data/queues2.dbf',

'/oracle/EBS/db/apps_st/data/owa1.dbf',

'/oracle/EBS/db/apps_st/data/archive1.dbf',

'/oracle/EBS/db/apps_st/data/archive2.dbf',

'/oracle/EBS/db/apps_st/data/tx_data1.dbf',











'/oracle/EBS/db/apps_st/data/reference1.dbf',

'/oracle/EBS/db/apps_st/data/reference2.dbf',

'/oracle/EBS/db/apps_st/data/apps_ts_tx_interface.dbf',

'/oracle/EBS/db/apps_st/data/portal.dbf',

'/oracle/EBS/db/apps_st/data/nologging1.dbf',

'/oracle/EBS/db/apps_st/data/summary1.dbf',





'/oracle/EBS/db/apps_st/data/tx_idx1.dbf',











'/oracle/EBS/db/apps_st/data/odm.dbf',

'/oracle/EBS/db/apps_st/data/media1.dbf',

'/oracle/EBS/db/apps_st/data/media2.dbf',

'/oracle/EBS/db/apps_st/data/media3.dbf'

80

auimpmsc.dat

directory=dmpdir

dumpfile=xttsmsc01.dmp

full=y

logfile=impmsc.log

EXCLUDE=PROCOBJ

remap_tablespace=

APPS_TS_ARCHIVE:SYSTEM,

APPS_TS_MEDIA:SYSTEM,

APPS_TS_NOLOGGING:SYSTEM,

APPS_TS_QUEUES:SYSTEM,

APPS_TS_SEED:SYSTEM,

APPS_TS_SUMMARY:SYSTEM,

APPS_TS_TX_DATA:SYSTEM,

APPS_TS_TX_IDX:SYSTEM,

APPS_TS_TX_INTERFACE:SYSTEM,

ODM:SYSTEM,

OLAP:SYSTEM,

OWAPUB:SYSTEM,

PORTAL:SYSTEM,

SYNCSERVER:SYSTEM

auimpsys.dat

directory=dmpdir

dumpfile=xttssys01.dmp

full=y

logfile=impsys.log

auimpglb.dat

file=gtab.dmp

filesize=1048576000

full=y

log=impgtab.log

auxttswrite.sql

REM

REM Ensure that you have no Apps processes running

REM before running this script

REM


alter tablespace APPS_TS_ARCHIVE read write;

alter tablespace APPS_TS_MEDIA read write;

alter tablespace APPS_TS_NOLOGGING read write;

alter tablespace APPS_TS_QUEUES read write;

alter tablespace APPS_TS_SEED read write;

alter tablespace APPS_TS_SUMMARY read write;

alter tablespace APPS_TS_TX_DATA read write;

alter tablespace APPS_TS_TX_IDX read write;

alter tablespace APPS_TS_TX_INTERFACE read write;

alter tablespace ODM read write;

81

alter tablespace OLAP read write;

alter tablespace OWAPUB read write;

alter tablespace PORTAL read write;

alter tablespace SYNCSERVER read write;

audeftbsp.sql


ALTER USER PTG DEFAULT TABLESPACE SYSTEM;

ALTER USER AD_MONITOR DEFAULT TABLESPACE SYSTEM;

ALTER USER PRP DEFAULT TABLESPACE APPS_TS_TX_DATA;

ALTER USER WIRELESS DEFAULT TABLESPACE SYSTEM;

ALTER USER JA DEFAULT TABLESPACE APPS_TS_TX_DATA;

……

ALTER USER HRI DEFAULT TABLESPACE APPS_TS_TX_DATA;

ALTER USER GMF DEFAULT TABLESPACE APPS_TS_TX_DATA;

ALTER USER OKC DEFAULT TABLESPACE APPS_TS_TX_DATA;

ALTER USER ODM DEFAULT TABLESPACE ODM;

ALTER USER DDD DEFAULT TABLESPACE APPS_TS_TX_DATA;

auque2.sql

spool auque2.out;

exec dbms_aqadm.start_queue(queue_name =>'SYS.AQ_EVENT_TABLE_Q',ENQUEUE =>TRUE,

DEQUEUE =>TRUE);

exec dbms_aqadm.start_queue(queue_name =>'SYS.AQ_SRVNTFN_TABLE_Q',ENQUEUE =>TRUE,

DEQUEUE =>TRUE);

exec dbms_aqadm.start_queue(queue_name =>'SYSTEM.DEF$_AQCALL',ENQUEUE =>TRUE,

DEQUEUE =>TRUE);

exec dbms_aqadm.start_queue(queue_name =>'SYSTEM.DEF$_AQERROR',ENQUEUE =>TRUE,

DEQUEUE =>TRUE);

exec dbms_aqadm.start_queue(queue_name =>'JTF.JTF_STAGING_MSG_QUEUE',ENQUEUE

=>TRUE, DEQUEUE =>TRUE);

……

exec dbms_aqadm.start_queue(queue_name =>'SYS.SRVQUEUE',ENQUEUE =>TRUE, DEQUEUE

=>TRUE);

exec dbms_aqadm.start_queue(queue_name =>'SYS.AQ$_ALERT_QT_E',ENQUEUE =>FALSE,

DEQUEUE =>TRUE);

exec dbms_aqadm.start_queue(queue_name =>'SYS.ALERT_QUE',ENQUEUE =>TRUE, DEQUEUE

=>TRUE);

exec dbms_aqadm.start_queue(queue_name =>'SYS.SYS$SERVICE_METRICS',ENQUEUE =>TRUE,

DEQUEUE =>TRUE);

exit;

82

Appendix E: Oracle E-Business Suite R12 Upgrade Report

(TUMS) – VIS

Please review the following example of TUMS Report:

Unnecessary steps

Based on the analysis of your installation, it has been determined that you do not need to perform the

following upgrade steps. You may safely omit carrying out these steps from the Upgrading Oracle

Applications Release R12 manual during your upgrade.

Chapter 2: Preparing for the Upgrade

Application Object Library, Step 1 (FND_ENABLE_MULTI_ORG)

Application Object Library, Step 3 (FND_WORKFLOW_TASKS)

Marketing, Step 1 (AMS_OSO_PLM_CHK)

Incentive Compensation, Step 1 (CN_PAYRN_REP_CHK)

Oracle Financials (India), Step 1 (JAI_CHECK_CUST)

Internet Expense, Step 1 (OIE_IMPORT_INTERCOMPANY_CHECK)

iPayment, Step 2 (IBY_SEC_UPGRADE)

Depot Repair, Step 1 (CSD_DATA_CHECK)

Service Contracts, Step 1 (OKS_VALIDATE_GCD)

Service Contracts, Step 2 (OKS_VALIDATE_RULE)

Chapter 4: Post-Upgrade Tasks

iPayment, Step 1 (IBY_WALLET_SETUP)

iPayment, Step 3 (IBY_REMIT_ADV_CONTROL_IT)

Oracle Financials (India), Step 1 (JAI_CHECK_PA_CUST)

Human Resources, Step 5 (PER_RIW_WINRUNNER)

Appendix E: Reducing Downtime

Service Contracts, Step 1 (OKS_R12_MIGRATE)

83

Appendix F: Recommended Oracle Support Portal

documents

This list enumerates the Oracle Support Portal documents that are explicitly referenced in the above

documentation of the platform migration and E-Business Suite upgrade process. Several additional

notes were also included for your convenience.

Preliminary phase:

316365.1 Oracle Applications Release 11.5.10.2 Maintenance Pack Installation Instructions

248857.1 Oracle E-Business Suite Tablespace Model Release 11i – Tablespace Migration Utility

Phase 1: Upgrading the Source database to 10gR2

362203.1 Oracle Applications Release 11i with Oracle 10g Release 2 (10.2.0)

125767.1 Upgrading Developer 6i with Oracle E-Business Suite 11i

216205.1 Database Initialization Parameters and Configuration for Oracle Applications Release 11i

165195.1 Using AutoConfig to Manage System Configurations with Oracle E-Business Suite 11i

233436.1 Installing Oracle E-Business Suite Server 10g with Oracle Applications Release 11i

312349.1 Remove Oracle Portal 3.0.9 from E-Business Suite 11i

Phase 2: Migrating 10gR2 DB to target HP-UX Integrity platform

762891.1 Oracle Applications Installation and Upgrade Notes Release 12 (12.1.1) for HP-UX

Itanium

369693.1 Using Oracle Applications with a Split Configuration Database Tier on Oracle 10gR2

165195.1 Using AutoConfig to Manage System Configurations with Oracle E-Business Suite 11i

Phase 3: Migrating to E-Business Suite Release 12.1.1

233044.1 About Oracle E-Business Suite DBA Minipack 11i.AD.I

761570.1 Oracle 10gR2 Database Preparation Guidelines for E-Business Suite Release 12.1.1

Upgrade

Phase 4: Upgrading to E-Business Suite Release 12.1.2

949406.1 Oracle E-Business Suite Readme, Release 12.1.2

Phase 5: Upgrading Oracle RDBMS to 11gR2

1058763.1 Interoperability Notes Oracle E-Business Suite Release R12 with Oracle 11g

Release 2 (11.2.0)

396009.1 Database Initialization Parameter Settings for Oracle Applications Release 12

387859.1 Using AutoConfig to Manage System Configurations in Oracle E-Business Suite Release

12

84

Appendix G: Validate the E-Business Suite environment

Execute the following steps to validate your E-Business Suite environment:

1. Make sure your Database and Database Listener is up and running

2. Make sure that all the Middle Tier Services are up and running using AD Scripts located at

$INST_TOP/admin/scripts e.g.

$sh adopmnctl.sh status

3. Cross check if Oracle HTTP Web Server is serving the HTTP requests:

http(s)://<hostname>.<domain name>:<HTTP Port>

Where <hostname>.<domain name> is Machine Name on which Oracle HTTP Web Server is

running. If you are using load balancer or Proxy Server in front of Web Server then use the

load balancer / Proxy Server Name and port on which Oracle HTTP Web Server is listening.

This information is configured in

$ORA_CONFIG_HOME/10.1.3/Apache/Apache/conf/httpd.conf

4. Cross check if OA CORE services are working or not?

a) http(s)://<host><domain>:<port>/OA_HTML/ServletPing

b) http(s)://<host><domain>:<port>/OA_HTML/OA.jsp?OAFunc=OAHOMEPAGE

5. Login check, try login as:

http://<host name>.<domain name>:<HTTP port>/oa_servlets/AppsLogin

or

http://<host name>.<domain name>:<HTTP port>/OA_HTML/AppsLocalLogin.jsp

6. Form Server check

a) Select any Forms based responsibility from user home page (SSWA Home Page,

OAHOMEPAGE). This should launch Forms Applet in J2SE Plug-in

b) Directly launching Forms Applet,

http://<host name>.<domain name>:<HTTP port>/forms/frmservlet

7. (Conditional)

Check AOL/J Health i.e. Application Object Library and Java

Access and execute the full AOL/J test with

http(s)://<host><domain>:<port>/OA_HTML/jsp/fnd/aoljtest.jsp

Execute each step; any exception/error will be shown in red color.

8. Concurrent Manager check,

a) Login as System Administrator, Select "Administer Concurrent Manager" and check if

"Actual" and "Target" are same.

b) Navigate to Concurrent request and submit “Active Users” concurrent request to check

if requests are getting executed.

85

9. Reports Server check: Change "Active Users" reports output from "Text file" to "PDF" from

Define Concurrent Request Screen. Submit Active Users request and click on Output, check if

you can see report in PDF format.

10. Workflow Check: Login to OAM (Oracle Application Manager), on top right of page from

"Navigate to" select "Workflow Manager" from the drop down menu and click on GO button.

Check if "Notification Mailers" is up.

11. Workflow status:

SQL>select fsc.COMPONENT_NAME,fsc.STARTUP_MODE,fsc.COMPONENT_STATUS

from APPS.FND_CONCURRENT_QUEUES_VL fcq, fnd_svc_components fsc

where fsc.concurrent_queue_id = fcq.concurrent_queue_id(+)

order by COMPONENT_STATUS , STARTUP_MODE , COMPONENT_NAME;

12. Cross check if iHelp is working or not?

a) In the SSWA Home Page, click on the "Help" icon at the top of the screen.

b) In the forms-based Applications, click on the "?" icon on the toolbar and also select the

"Help -> Oracle Applications Library" option from the menu bar; then test the search

utility by searching for a common keyword such as "form".

13. Invalid Objects (Post Patch/Upgrade):

SQL>select owner, count(*) from dba_objects where status = „INVALID‟ group by owner;

SQL>select count(object_type),object_type from dba_objects where status='INVALID' group by

object_type;

SQL>Select count(*) from dba_objects where status='INVALID';

For more information

HP Integrity server product information site: http://www.hp.com/go/integrity

HP BladeSystem product information site: http://www.hp.com/go/bladesystems

HP Storage information site http://www.hp.com/go/storageworks

HP-UX 11i v3 product information site: http://www.hp.com/go/hpux

HP AlphaServer systems running Tru64 UNIX product information site:

http://h30097.www3.hp.com/?jumpid=reg_R1002_USEN

Oracle E-Business Suite Upgrade Guide: Release 11i to Release 12.1.1, Part # E14010-01

Oracle E-Business Suite Installation Guide: Using Rapid Install Release 12.1.1 Part # E12842-04

Oracle E-Business Suite Maintenance Procedures Part # E13675-02

Oracle E-Business Suite Maintenance Utilities Part # E13676-02

Oracle E-Business Suite Patching Procedures Part # E12148-02

Oracle E-Business Suite System Administrator's Guide – Configuration Part # E12893-02

Oracle E-Business Suite System Administrator's Guide - Maintenance Part # E12894-02

Oracle E-Business Suite System Administrator's Guide - Security Part # E12843-03

Oracle E-Business Suite Concepts R12.1.1 Part # E12841-02

Upgrading Oracle Applications Release 11i (11.5.10.2), Part # B19297-01.

Oracle Database Upgrade Guide: 11g Release 1 (11.1), Part # B28300-03

Oracle Database Upgrade Guide: 11g Release 2 (11.2), Part # E10819-02

Oracle Database Administrator‟s Guide: 11g Release 1 (11.1), Part # B28310-04

Oracle Database Installation Guide 10g Release 2 (10.2) for hp Tru64 UNIX Part # B25300-01

Oracle Database Quick Installation Guide: 11g Release 1 (11.2) for HP-UX Itanium, Part # E18245-

02

Oracle Database Installation Guide 11g Release 2 (11.2) for HP-UX Part # E17880-01

To help us improve our documents, please provide feedback at

http://h20219.www2.hp.com/ActiveAnswers/us/en/solutions/technical_tools_feedback.html.

© Copyright 2008, 2011 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. UNIX is a registered trademark of The Open Group. Intel and Itanium are trademarks of Intel Corporation in the U.S. and other countries. AMD is a trademark of Advanced Micro Devices, Inc. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.

4AA2-0266ENW, Created June 2008; Updated March 2011, Rev. 1

http://www.hp.com/go/integrity

http://www.hp.com/go/bladesystems

http://www.hp.com/go/storageworks

http://www.hp.com/go/hpux

http://h30097.www3.hp.com/?jumpid=reg_R1002_USEN

http://h20219.www2.hp.com/ActiveAnswers/us/en/solutions/technical_tools_feedback.html

http://www.hp.com/go/getconnected

4AA2-0266ENW

Documents

Transcript of 4AA2-0266ENW