You are on page 1of 3

Go-Live

Readiness Checklist for Oracle E-Business Suite Release 12.2



This go-live checklist is designed to be used in conjunction with the Getting
Started flowchart that is also attached to Document 1585857.1. The flowchart
offers a guide to the key processes and resources involved in a Release 12.2
implementation project: in contrast, this checklist helps you identify and meet
the high-level requirements needed for a successful go-live.

As you work your way through the checklist, do not omit any sections or checks.

The checklist content is time-sensitive, and the recommendations may change
with new releases, certifications and patches. We therefore recommend enabling
email notifications about revisions: refer to How To Use My Oracle Support Hot
Topics Email (Doc ID 1643251.1).

Section 1: Fundamentals

1.1 Ensure your system meets the operating system requirements

Refer to Chapter 1, Getting Started, of Oracle E-Business Suite Installation
Guide: Using Rapid Install (Part No. E22950), and the My Oracle Support
installation and upgrade notes for your platform.

1.2 Ensure your system meets the Oracle E-Business Suite requirements

Refer to the following sections of Chapter 1, Getting Started, of Oracle E-
Business Suite Installation Guide: Using Rapid Install (Part No. E22950):
CPU, Memory and Disk Requirements
Database and Application Tier Sizing Guidelines

1.3 Confirm you will install or upgrade to either Release 12.2.4 or 12.2.3

Release 12.2.4 is the current release, and highly recommended. Release
12.2.3 is the minimum release for which patches are provided. Refer to
Oracle E-Business Suite Error Correction Support Policy (Doc ID
1195034.1) for more information.

1.4 Verify that the database you will use with Release 12.2 is certified

Oracle Database 11.2.0.4 (for Database 11g) or 12.1.0.2 (for Database
12c) are recommended. See Release Schedule of Current Database Releases
(Doc ID 742060.1) for error correction support dates (for example,
Version 11.2.0.3 will received no error correction support after August
2015). Plan your database version with particular care if your go-live date
is some time away.



1.5 Verify you have performed needed steps in Getting Started flowchart

This check depends on whether you are doing a fresh install or upgrade.

If you are performing a fresh install of Release 12.2, confirm that you
have completed all the high-level steps in the Fresh Install process
(Tasks A1 to A6) shown in the Getting Started flowchart.
If you are performing an upgrade from a pre-12.2 release, confirm that
you have completed all the high-level steps in the Upgrading from a
Pre-12.2.0 Release to Release 12.2.4 process (Tasks C1 to C8) shown
in the Getting Started flowchart.

Section 2: Meet Patch Requirements

2.1 Confirm you have run ETCC and that it reports no missing patches

Refer to Oracle E-Business Suite Release 12.2: Consolidated List of Patches
and Technology Bug Fixes (Doc ID 1594274.1). Missing database patches
can impact online patching functionality and cause serious data issues.

2.2 Ensure you have applied application tier technology patches needed

Refer to Oracle E-Business Suite Release 12.2: Consolidated List of Patches
and Technology Bug Fixes (Doc ID 1594274.1). You may need to apply
Forms, Oracle WebLogic Server, and Fusion Middleware patches.

2.3 Ensure you are on the latest AD-TXK codelevel

The latest AD-TXK codelevel is Delta 6 as of March 2015. Refer to Applying
the Latest AD and TXK Release Update Packs to Oracle E-Business Suite
Release 12.2 (Doc ID 1617461.1) and to Oracle E-Business Suite Error
Correction Support Policy (Doc ID 1195034.1).

2.4 Confirm you have applied any critical patches listed in the Readme

Refer to the applicable Readme and apply any critical patches listed in it:
Oracle E-Business Suite Release 12.2.4 Readme (Doc ID 1617458.1)
Oracle E-Business Suite Release 12.2.3 Readme (Doc ID 1586214.1)

Section 3: Meet Integration Requirements

3.1 Confirm that third parties verify meeting the development standards

Check that all relevant third-party software suppliers have verified that
their software adheres to the official Oracle E-Business Suite Release 12.2
development standards. Refer to Guidance for Integrating Custom and
Third-Party Products With Oracle E-Business Suite Release 12.2 (Doc ID
1916149.1) and Oracle E-Business Suite Developer's Guide, Release 12.2,
Part No. E22961.


3.2 Confirm that your customizations meet the development standards

Check whether your customizations adhere to the official Oracle E-
Business Suite Release 12.2 development standards, and update them if
they do not. Refer to Guidance for Integrating Custom and Third-Party
Products With Oracle E-Business Suite Release 12.2 (Doc ID 1916149.1)
and Oracle E-Business Suite Developer's Guide, Release 12.2, Part No.
E22961.

Section 4: Configure, Tune and Test

4.1 Run performance benchmarks in a representative test environment

Create a test environment and run benchmarks with a configuration,
product mix, and user load that adequately simulates your current and
expected workloads.

4.2 Add managed servers as required to meet your expected workload

You may need to add managed servers to maintain adequate performance
under load, based upon your benchmark results. Refer to: Adding
Managed Servers in Managing Configuration of Oracle HTTP Server and
Web Application Services in Oracle E-Business Suite Release 12.2 (Doc ID
1905593.1).

4.3 Apply an online patch to a test system that represents your topology

To confirm you will encounter no problems when you go live, you need to
confirm you can successfully apply a sample online patch to your planned
configuration. This is particularly important if you will be using a multi-
node configuration (as is typically the case).
4.4 Perform adequate practice installs or upgrades before going live

You must conduct a number of successful practice installs or upgrades
before finally performing your go-live install or upgrade.

Using clones of your production database, record the times needed to
apply patches and migrate your actual data. Many Release 12.2
production go-lives can be optimized by rehearsing and fine-tuning the
actual steps needed.

You might also like