Professional Documents
Culture Documents
Upgrade Guide
Release 12.0 and 12.1 to 12.2
Part No. E48839-03
November 2013
Oracle E-Business Suite Upgrade Guide, Release 12.0 and 12.1 to 12.2
Copyright © 1996, 2013, Oracle and/or its affiliates. All rights reserved.
Contributing Author: John Abraham, Sankar Akshathala, Aditya Bansal, Santiago Bastidas, Sanjay
Bheemasenarao, Jason Brincat, Richard Chang, Robert Farrington, Sandeep Goel, David Heisler, Paul
Holman, Clara Jaeckel, Radha Kalakurthy, Hyun Kim, Pratima Mahtani, Dorothy Mak, Ruth Mamo, Swathi
Mathur, Anil Modwel, Udayan Parvate, Kavuri Ramanjaneyulu, Sreedhar Ramasahayam, Sudha Rao, Scot
Robson, Nitin Somani, Sujai Veerabhadraiah, Sriram Veeraraghavan, David Vickers, Sharath Vishwanath,
Millie Wang, Melody Yang
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are
used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron,
the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro
Devices. UNIX is a registered trademark of The Open Group.
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on
behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,
any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are
"commercial computer software" pursuant to the applicable Federal Acquisition Regulation and
agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation
of the programs, including any operating system, integrated software, any programs installed on the
hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the
programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications.
It is not developed or intended for use in any inherently dangerous applications, including applications that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you
shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its
safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.
This software or hardware and documentation may provide access to or information on content, products,
and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly
disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle
Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your
access to or use of third-party content, products, or services.
Contents
Preface
iii
Database Initialization Parameters.................................................................................... 1-12
Determining Upgrade Tasks.............................................................................................. 1-13
Maintenance Mode............................................................................................................ 1-13
Test Upgrade...................................................................................................................... 1-14
User Preferred Time Zone Support.................................................................................... 1-14
Upgrade By Request.......................................................................................................... 1-14
NLS Upgrade Considerations................................................................................................. 1-14
Languages.......................................................................................................................... 1-14
Customized Environments...................................................................................................... 1-15
Customized Help Files....................................................................................................... 1-16
Product-specific Considerations............................................................................................. 1-16
Cross-Product Functionality.............................................................................................. 1-16
iv
Channel Revenue Management Tasks................................................................................... 5-12
Human Resources Tasks......................................................................................................... 5-12
Projects Tasks.......................................................................................................................... 5-13
Supply Chain Management Tasks.......................................................................................... 5-13
System Administration........................................................................................................... 5-16
System Maintenance Tasks..................................................................................................... 5-17
Oracle XML Publisher............................................................................................................. 5-19
Additional Tasks..................................................................................................................... 5-20
Index
v
Send Us Your Comments
Oracle E-Business Suite Upgrade Guide, Release 12.0 and 12.1 to 12.2
Part No. E48839-03
Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document.
Your feedback is important, and helps us to best meet your needs as a user of our products. For example:
• Are the implementation steps correct and complete?
• Did you understand the context of the procedures?
• Did you find any errors in the information?
• Does the structure of the information help you with your tasks?
• Do you need different information or graphics? If so, where, and in what format?
• Are the examples correct? Do you need more examples?
If you find any errors or have any other suggestions for improvement, then please tell us your name, the
name of the company who has licensed our products, the title and part number of the documentation and
the chapter, section, and page number (if available).
Note: Before sending us your comments, you might like to check that you have the latest version of the
document and if any concerns are already addressed. To do this, access the new Oracle E-Business Suite
Release Online Documentation CD available on My Oracle Support and www.oracle.com. It contains the
most current Documentation Library plus all documents revised or released recently.
Send your comments to us using the electronic mail address: appsdoc_us@oracle.com
Please give your name, address, electronic mail address, and telephone number (optional).
If you need assistance with Oracle software, then please contact your support representative or Oracle
Support Services.
If you require training or instruction in using Oracle software, then please contact your Oracle local office
and inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site at
www.oracle.com.
vii
Preface
Intended Audience
Welcome to Release 12.0 and 12.1 to 12.2 of the Oracle E-Business Suite Upgrade Guide.
This book provides instructions for upgrading existing Oracle E-Business Suite Release
12.0 and 12.1 systems to Release 12.2. In this upgrade, run Rapid Install to prepare your
12.0 or 12.1 system for the upgrade. It delivers the unified driver that you use to
upgrade the technology stack and products to Release 12.2.
This book is intended as a guide for the database administrator and the application
specialists who are responsible for upgrading to Release 12.2 of Oracle E-Business Suite.
See Related Information Sources on page x for more Oracle E-Business Suite product
information.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle
Accessibility Program website at
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Structure
1 Planning for an Upgrade
2 Preparing for the Upgrade
3 Upgrading to Release 12.2
4 Oracle E-Business Suite Online Patching
ix
5 Post Upgrade Tasks
A Financials Upgrade Impact
B Human Resource Management Upgrade Impact
This appendix describes the way the upgrade affects your existing Oracle Human
Resource Management System (HRMS) products, and highlights the impact of these
functional changes on your day-to-day business. This section contains products in the
HRMS product family, arranged alphabetically.
C Supply Chain Management Upgrade Impact
D Product Documentation List
Installation and upgrade Oracle E-Business Suite Installation Guide: Using Rapid Install
x
If you are looking for Refer to these documents...
information about...
xi
1
Planning for an Upgrade
Product Name
* Oracle CAD-View 3D
* Oracle HR Intelligence
* A migration plan exists for customers who have purchased these products in earlier
releases. Contact your Sales Representative or Account Manager for more information.
** Customers continuing to use Oracle Student Recruiting and Oracle Student Systems
should not upgrade to this release.
Support will be provided to existing customers on earlier releases, in accordance with
the Oracle Lifetime Support Policy.
• Steps you can take to verify that all transactional data is upgraded as expected
Reference Information
It is very important that you read the documentation associated with this release. It is
available in Oracle E-Business Suite Documentation Resources, Release 12 on My Oracle
Support. The Product Documentation List in this guide contains a list of basic required
reading. In addition, you may also find it useful to review any presentation materials on
upgrade technology and white papers on Multi-org, and links to various Consulting
services as well as Oracle University training courses.
Application specialists and functional users should pay special attention to the Release
Content Documents (RCDs), Electronic Technical Reference Manuals (eTRMs), and
Transfer of Information (TOI) documentation for the products that are active in your
system. This information describes new features and functionality in Release 12.2.
• Upgrading to Release 12.2 begins the system downtime. Tasks in this chapter
include upgrading your database (if you have not done so already), using
AutoPatch to apply any required patches.
• The Post Upgrade Tasks complete the upgrade process and prepare your system
and products for user logon.
• Perform the tasks required to verify that your transaction data was upgraded or
migrated as you intended.
• Determine the best way to upgrade historical data. For example, instead of
upgrading all your Oracle Financials accounting data during downtime, you might
include only the last fiscal year. If you want to upgrade other fiscal years - months
or even years after - you can do so, at any time after the upgrade.
• Oracle FMW 11g Java Required Files (JRF) libraries (except the use of ADF and
MDS 11g)
• Oracle 10g (10.1.2) Applications Server for Oracle EBS Forms based Applications
The Web listener component of the Oracle HTTP server accepts incoming HTTP
requests (for particular URLs) from client browsers, and routes the requests to WLS.
If possible, the Web server services the requests itself, for example by returning the
HTML to construct a simple Web page. If the page referenced by the URL needs
advanced processing, the listener passes the request on to the servlet engine, which
contacts the database server as needed.
Note: See Oracle E-Business Suite Concepts Release 12.2 for details.
Software Requirements
Some systems may require platform-specific release maintenance tools. Refer to the
Oracle E-Business Suite Installation and Upgrade Notes for further information, and to
verify whether you need to include them in your upgrade plan. The upgrade requires a
minimum of Oracle 11g Release 2 (11.2.0.3). See Database Preparation Guidelines for an
Oracle E-Business Suite Release 12.2 Upgrade for instructions.
CPU
The CPU requirements for an upgrade depend on many factors, including:
• The size of the database
• The number and duration of long-running patch worker processes associated with
products that have intensive upgrade operations
Memory
To calculate the memory requirements for an upgrade, consider the following:
• Number of concurrent users
Note: For minimum memory and swap space requirements, refer to the
relevant Oracle E-Business Suite platform-specific Installation and Upgrades
Notes (IUN) and the Rapid Install Guide for 11gR2 sizing available on My
Oracle Support Knowledge, and the Oracle E-Business Suite
Documentation Resources, Release 12.2 document (Doc ID: 1498411.1).
Applications node file system (includes 64 GB (for the dual file system required by
OracleAS 10.1.2 Oracle Home, Oracle FMW online patching - see note below)
Oracle Home, COMMON_TOP, APPL_TOP,
and INST_TOP)
The database node disk space requirements for both the production database and the
Vision Demo database include database files (.dbf) and the 11gR2 database Oracle
Home.
BPEL 10g If you are are using BPEL 10g with EBS 12.1.3,
then you must migrate to SOA Suite 11g as the
external system.
SES 10g If you are using 11i, 12.0.x, 12.1.1 - 12.1.2 and
are upgrading to 12.2, then you must also
upgrade to SES 11g.
ORASSO_DS
ORASSO_PA
ORASSO_PS
ORASSO_PUBLIC
ORAOCA_PUBLIC
WIRELESS
OWBSYS_AUDIT
DSROWNER
MTHUSER
MapViewer MVDEMO
• Forms services
In Release 12.2, Web and Forms services are provided by Oracle Application Server They
are no longer servers in the sense of being a single process.
Backup
Oracle strongly recommends that you back up your entire system before beginning the
upgrade.
Maintenance Wizard
The Maintenance Wizard is a tool provided by Oracle Support to guide you through the
upgrade and code line maintenance process. It draws on instructions from numerous
manuals and other documentation (including this document, the Oracle E-Business Suite
Installation Guide: Using Rapid Install, and the Oracle E-Business Suite Release Notes) to
provide you with a complete picture of the activities required for an upgrade.
The Maintenance Wizard helps you reduce upgrade tasks by dynamically filtering the
necessary steps based on criteria it obtains from your Applications environment. The
resulting report is a set of step-by-step instructions of exactly what you need to do to
complete your specific upgrade, including any critical patches that your system may
require. It can also automatically execute many of the tasks for you, so as to reduce the
possibility of errors or accidental omission of vital tasks.
Specifically, the Maintenance Wizard:
• Presents a consolidated, personalized set of instructions in a step-by-step format
• Provides project management utilities to record the time taken for each task and its
completion status
Maintenance Mode
The Maintenance Mode feature provides a clear separation between the normal runtime
operation of Oracle E-Business Suite and system downtime for maintenance. To ensure
optimal performance and reduce downtime when applying a patch, shut down the
Workflow Business Events System and set up function security before you initiate an
AutoPatch session. This provides the security needed to ensure that no Oracle
Test Upgrade
To provide a baseline for upgrade execution times and an opportunity to work out any
upgrade issues ahead of time, Oracle suggests that you perform a test upgrade using a
copy (clone) of your existing system, and hardware that is similar to your production
system. Oracle recommends several upgrade tests, especially if your system has been
customized.
Upgrade By Request
For some Oracle E-Business Suite products, upgrade planning includes choosing the
most active set of data for upgrade processing. Then, you can upgrade historical data
that was omitted from the upgrade at a later date, or when it is needed. For example,
you might include only the last fiscal year in the upgrade to Release 12.2, and then
upgrade the remaining data outside the 12.2 downtime window.
Languages
Additional space for each non-American English language will be required in the
database to complete the upgrade. It is not possible to predict the amount of additional
space your system will need, because the space depends on factors such as the database
character set, the number of active languages other than American English, and in
particular the volume of transaction data in the system.
Note: For the recommended minimum space required for each active
language in the APPL_TOP, see the Oracle E-Business Suite NLS Release
Notes for your release level.
Character Sets
You cannot set the APPL_TOP character set. It is automatically set to the same value to
what you selected as the db character set.
Customized Environments
Customized environments require additional attention during an upgrade. The
instructions in this guide assume that you have followed the standards for customizing
Oracle E-Business Suite as described in the Oracle E-Business Suite Developer's Guide and
the Oracle E-Business Suite User Interface Standards for Forms-based Products.
To preserve customizations and minimize the impact during the upgrade:
• Follow the Oracle E-Business Suite Developer's Guide instructions for customizing
your system and upgrading your customizations
Product-specific Considerations
The information in this section applies to specific Applications products in this release.
See the Release Content Documents for information about other products that are active
in your system.
Cross-Product Functionality
Changes to the products described in this section affect many Oracle E-Business Suite
products. Prior to the upgrade, ensure that functional specialists have completed their
review to avoid unnecessary disruptions.
Note: Shut down the database with the NORMAL option. You may not
be able to restore it from the backup if you use the IMMEDIATE or
ABORT option.
In addition to the database files, back up the APPL_TOP, product customizations, and
customized help files (in HTML).
Note: The upgrade process does not save customizations. You should
copy all your customized files and put them in a safe place so you can
reapply the customizations after the upgrade.
• Run several test upgrades and track their impact on your custom database objects.
• Rename any custom database objects with Applications prefixes that you have
created so that they do not conflict with Oracle object names.
At your discretion, and depending on the customizations in your system, you should
also perform the following tasks:
1. Preserve the CUSTOM library by making a backup copy of CUSTOM.pll. You can
use this copy later in the upgrade process to migrate your CUSTOM library to
Release 12.2.
2. If you have customized forms with Oracle Forms 6i, then upgrade them to Oracle
Forms 10i after the upgrade.
Note: The Oracle XML Gateway Web service feature depends on Oracle
E-Business Suite Integrated SOA Gateway. Oracle E-Business Suite
Integrated SOA Gateway Release 12.2 has product dependencies on
Oracle SOA Suite 11g and Oracle Adapter for Oracle Applications
(informally known as Oracle E-Business Suite Adapter).
Advanced Collections:
Perform this task only if you are using Oracle Advanced Collections with Strategies.
1. Strategy Workflow checks
Applies to 12.0 and 12.1 release levels.
Apply the diagnostic scripts patch 13027498:R12.IEX.A when upgrading from
R12.0.X and apply 13027498:R12.IEX.B when upgrading from 12.1.X. This patch
contains scripts for Collection Strategy Workflow.
From the Collections Agent responsibility using the user name 'SYSADMIN', stop
any scheduled Workflow Background Process concurrent program request for the
following Item Types:
• IEXSTRY - IEX: Collection Strategy Work Flow
Subledger Accounting:
Perform this task if you are using Oracle Subledger Accounting.
1. Clean up Advance Queues from prior Create Accounting processes before
enabling EBR.
When all database objects have been identified, change the datatype to CLOB (Refer to
the Oracle E-Business Suite Developer's Guide).
Order Management:
Perform these tasks if you are using Oracle Order Management.
1. Check for the Nullable Hold Entity ID.
Applies to: Release 12.1
If you are upgrading from release 12.1, then you should check for the Nullable Hold
Entity ID and fix it to NOT NULL. Carefully follow the instructions in the readme
of Patch 14191792:R12.ONT.B.
Product Hub:
Perform these tasks if you are using Oracle Product Hub.
1. Using the Packing Hierarchy Structure Type
Applies to: Release 12.0
If you are upgrading from 12.0 and have used Packaging Hierarchy structure type,
then note that only the preferred packaging structure from this structure type is
migrated over in the upgrade process. If you have defined multiple packaging
structures and want to migrate all of them, then consider bringing them into the
system by transferring them into other structure types, at which time they will be
treated as regular structure types and not Packs.
• EGO_MTL_SY_ITEMS_EXT_TL
You can discard the backups when the upgrade is completed and the pre-upgrade
UDA data for items have been functionally verified. This is required only if you are
upgrading from Release 12.0 to Release 12.2.
If the above query returns '0' as the output, then perform the following steps:
1. Take backup of ego_mtl_sy_items_ext_b table
2. Refer to Note ID: 953449.1 and run the script provided in the 'Identification
Script' column within the 'Solution - Datafix' section to identify duplicate
records.
If there are duplicate records, then run the scripts provided in the 'Fix' column
within the 'Solution - Datafix' section for the appropriate base version to delete
duplicate records.
Refer to the Oracle E-Business Suite Maintenance Guide for more information on the
Gather Schema Statistics concurrent program and the
FND_STATS.GATHER_SCHEMA_STATISTICS procedure.
Set the schema name to ALL to gather statistics for all Oracle E-Business Suite
schemas (those with 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.
Depending on the size and number of changes to your database, gathering schema
statistics may take a long time. Using the 'GATHER AUTO' option can reduce the
overall time, as it uses an incremental approach.
Customers who gather schema statistics at 10% for all schemas and then again at a
higher percentage for specific schemas or tables should initially continue this
approach to avoid performance degradation. Review this process during the
performance test phase.
Once the pre-upgrade steps have been completed, consider using the 'GATHER_
AUTO' option and the DBMS_STATS.AUTO_SAMPLE_SIZE feature (available in
Oracle Database 11gR1 and later). The AUTO sample size feature takes data skew
into account, and may avoid the need to gather schema statistics at a higher
percentage: in addition, it is likely to take the same time as using a manual
approach with a percentage between 10-20 percent. When invoking the Gather
Statistics concurrent program, Oracle recommends leaving the estimate_percent
parameter blank. The program automatically selects the default value for the
estimate_percent parameter. If you provide a value, then statistics will be gathered
at the specified percentage. If the database version is 11g or higher, then the default
value for this parameter is dbms_stats.auto_sample_size. (For previous releases it
was set to 10%.)
3. On the Select Upgrade Action screen, select Create Upgrade File System.
4. In the associated screen flow, enter the parameters required to set up your new
environment. Then, run Rapid Install.
Run Rapid Install with the Configuration option to complete the configuration after
the R12.2 upgrade patch application.
Important: If the APPS user password is not the default, then the
rapidwiz cannot be used in silent mode for laying down the
Upgrade File System. If there are multiple middle tiers, then Oracle
recommendsthat you set APPS user password to the default, and
use Rapid Install in silent mode for laying down the Upgrade File
System on all mid tiers. If not, then you must use Rapid Install in
interactive fashion.
Note: Shut down with the NORMAL option. You may not be able
to restore the database from the backup if you use the IMMEDIATE
or ABORT option.
Note: If you are upgrading to 11gR2 from 10g or 9i, then you MUST
set the parameter sec_case_sensitive_logon = False in your init.ora
file to avoid login issues with sqlplus.
Important: After laying down the File System using Rapid Install, do
not change the password for any products. Doing so may result in the
following error: 'ORA-01017: invalid username/password; logon denied
occurred while executing the SQL statement: CONNECT JTF/*****'
If the password for a product is changed, then FNDCPASS should be
run to revert the password to the default value. Adpatch can be
resumed after the password is restored to the original value.
Important: You must turn off the Database Vault before upgrading to
12.2.0. After enabling EBR+upgrade to 12.2.x, re-enable the Database
Vault.
Note: If you are upgrading to 11gR2 from 10g or 9i, then you MUST
set the parameter sec_case_sensitive_logon = False in your init.ora
file to avoid login issues with sqlplus.
Note: Shut down with the NORMAL option. You may not be able
to restore the database from the backup if you use the IMMEDIATE
or ABORT option.
3. The Change Maintenance Mode menu displays the current Maintenance Mode
status at the top of the page. The status should be Disabled at this point.
Caution: Ensure that the environment file from the 12.2 RUN File
System is sourced prior to applying this patch.
To bring your database to the full Oracle E-Business Suite Release 12.2 level, use
Source the environment file from the RUN file system and run the driver on the
administration server node on your Release 12.2 APPL_TOP using the following
commands:
$ adpatch options=nocopyportion,nogenerateportion
Maintenance mode controls the system downtime period by managing user logins.
To disable maintenance mode, use the Change Maintenance Mode menu in AD
Administration.
2. The Change Maintenance Mode menu displays the current Maintenance Mode
status at the top of the screen. It should be Enabled.
Perform a full Oracle E-Business Suite backup of the application and database.
On the database tier (as the ORACLE user), copy or FTP the appsutil.zip file to
the <RDBMS ORACLE_HOME> and unzip the file. Change directory to RDBMS
2. Install JRE on the database tier to ensure that the application tier and the
database tier match (Conditional).
If you have installed JRE on Database Tier (see below) before running Rapid
Install in Upgrade mode by using 'Use Existing ORACLE_HOME' as described
in Preparing for the Upgrade, then install JRE on the database tier. If you have
used ORACLE HOME installed by Rapid Install, then skip this step.
Download the latest JRE 6.0 Update. For optimum stability, performance,
scalability, and OS vendor support, use the latest available update of JRE for the
Oracle E-Business Suite database tier.
The JRE download location is:
http://www.oracle.com/technetwork/java/javase/downloads/index.html
• LD_LIBRARY_PATH = $ORACLE_HOME/lib:$ORACLE_HOME/ctx/lib
• TNS_ADMIN = $ORACLE_HOME/network/admin/<CONTEXT_NAME>
UNIX:
cd <RDBMS ORACLE_HOME>/appsutil/bin
perl adbldxml.pl
Windows:
cd <RDBMS ORACLE_HOME>\appsutil\bin
perl adbldxml.pl
Overview
Oracle E-Business Suite Release 12.2 introduces Online Patching (OP), a new feature
that greatly reduces the downtime that was needed in previous releases for application
of Release Update Packs (RUPs), Critical Patch Updates (CPUs), and other patches and
bug fixes of various kinds.
Key Features
• In Release 12.2, all patching operations are carried out while the applications are in
use and users are online.
• Patching is performed using the new adop (AD Online Patching) utility.
• A short period of downtime is required, but this amounts to little more than a
restart of the services: the time the applications are unavailable is measured in
minutes rather than hours, and this can be specified to be at the most convenient
time.
Principles
2. Patches are applied to the copy while users continue to access the running system.
This introduces the concept of a patching cycle that consists of several phases, in contrast
to the model used in previous releases. These phases are denoted prepare, apply,
finalize, cutover, and cleanup.
Note: For more information about online patching principles, see Oracle
E-Business Suite Concepts.
Implementation
Any mechanism that uses a copy of the running application must take into account that
an Oracle E-Business Suite application comprises both code and data, stored in the file
system and database.
The file system is the easier of the two to cater for, simply requiring an additional copy
to be created and maintained. The resulting dual file system consists of one file system
that is used by the running system and another one that is either currently being
patched, or (as will be the case for most of the time) standing ready to be patched. The
two file systems swap roles at the end of each patching cycle, with the transition between
them being managed by AutoConfig.
Creating a copy of the database portion of the running applications system is more
complex. It has been accomplished by taking advantage of the Oracle Database 11g R2
Edition-Based Redefinition (EBR) feature. This allows an application to efficiently store
multiple copies (editions) of its application definition in the same database, and thereby
enables online upgrade of the database tier.
The database patch edition only comes into existence during a patching cycle, and
becomes the new run edition at end of the cycle. The former database run edition (the
old edition) and the obsolete objects it contains are discarded at the end of a patching
cycle, and the space reclaimed during the cleanup phase.
Tools
Patching is performed by running the new adop (AD online patching) tool. This tool
invokes the adpatch utility that was run directly in previous releases of Oracle
E-Business Suite.
Note: For full details of adop features and options, refer to the Patching
section of Oracle E-Business Suite Maintenance Guide.
2. Ensure the required 11.2.0.3 patches for Release 12.2 have been applied
Review the Database Preparation Guidelines for Release 12.2 and ensure that all
patches listed are installed in your database. Do not proceed with the enabling
online patching process if all patches have not been installed. Refer to Database
Preparation Guidelines for an E-Business Suite Release 12.2 Upgrade (Doc ID: 1349240.1).
Note: The subsequent steps assume that you are running in the
same session which was initialized with this environment file.
If you need additional operating system level sessions,
remember to initialize the environment with this same
environment file.
2. Create the online patching log file location and set it as the current directory:
• ADZDPAUT.sql - This report lists all the objects with violations to the EBR
rules that will be fixed automatically from the enablement process. This
report is provided for information purposes and no action should be taken
from this report.
4. Fix Violations Listed in the Online Patching Readiness Report that Require
Manual Intervention
The Online Patching Readiness Report contains sections with different violation
• SYSTEM
• CTXSYS
2. Oracle recommends that you perform the chosen fix by customizing template
file $AD_TOP/sql/ADZDPCUST.sql
3. Repeat the Run the Online Patching Enablement - Readiness Report step above until
all violations have been addressed.
2. Set the HOSTNAME environment variable before executing the online patching
tool adop.
• Check to ensure the environment variable HOSTNAME is set by running
the following:
$ echo $HOSTNAME
• If the HOSTNAME environment variable is not set, then run the following:
export HOSTNAME=<your-hostname-without-domain>
• If the hostname is set but has the domain, then reset it without the domain.
For example:
echo $HOSTNAME
apcappsx2.au.oracle.com
export HOSTNAME=apcappsx2
3. Run the following report to retrieve the current tablespace free space:
perl $AD_TOP/bin/adzdreport.pl apps
• Add necessary space to the tablespaces if they do not contain the required free
space. Refer to Altering and Maintaining Tablespaces in Oracle Database
Administrator's Guide for details.
2. Run the report using the following command. Ensure that you verify any
invalid objects at this stage. Take special note to ensure that all online patching
objects (objects that match the pattern 'AD_ZD%') are valid:
sqlplus <apps username> @$AD_TOP/sql/ADZDEXRPT.sql
7. Ensure that all middle-tier E-Business Suite services are shut down
Verify that all middle-tier E-Business Suite services are shut down prior to applying
the Online Patching Enablement patch.
This report lists a count of the DDL statements that are required to EBR enable your
environment. The report is organized by outcome of execution: 'Successfully
Executed', 'Not Executed', and 'Failed Execution'. At the end of the patch
application the report should have a zero count in the sections: 'Not Executed' and
'Failed Execution'. If the report contains 'Not Executed' and 'Failed Execution' items,
then report these failures to Oracle Support. You will be asked to provide the
output from the report, the patch log and all worker logs, and the online patching
enablement status report output. If there is any worker failure during the Online
Enablement patch, you should not ignore or skip the failed error. The issue should
be addressed before restarting the worker. Ignoring or skipping the error can cause
database corruption.
10. Run the Online Patching Enablement Status Report after the Online Patching
Enablement patch has been applied
1. Set the current directory to $LOG_HOME/appl/op:
cd $LOG_HOME/appl/op
2. Run the Status Report immediately after the enablement patch completes:
sqlplus <Apps Username> @$AD_TOP/sql/ADZDEXRPT.sql
The purpose of running this report at this stage is to identify and fix any errors that
occurred during the enablement process.
11. Re-run the Online Patching Enablement Readiness Report after the Online
Patching Enablement patch has been applied
1. Set the current directory to $LOG_HOME/appl/op:
cd $LOG_HOME/appl/op
mv adzdpsum.txt adzdpsum_post_dbprep.txt
sqlplus system @$AD_TOP/sql/ADZDPMAN.sql
mv adzdpman.txt adzdpman_post_dbprep.txt
sqlplus system @$AD_TOP/sql/ADZDPAUT.sql
mv adzdpaut.txt adzdpaut_post_dbprep.txt
The purpose of running this report at this stage is to ensure that all EBR
violations that could have appeared before enabling the online patching feature
are fixed.
12. Run the Online Patching Database Compliance Checker report to check for
coding standards violations
1. Set the current directory to $LOG_HOME/appl/op:
cd $LOG_HOME/appl/op
2. Run the Online Patching Database Compliance Checker report to check for
This utility reports all violations to the Online Patching Development Standards.
Refer to Database Object Development Standards for Online Patching in Oracle
E-Business Suite Developer's Guide. All Oracle E-Business Suite violations are fixed by
the 12.2 upgrade. You must fix any object listed in this report that is part of your
custom code. If you do not fix the violation, then you cannot leverage the online
patching infrastructure to patch the objects listed in this report.
The 'recyclebin' parameter must be turned off to allow the cleanup phase of the online
patching cycle to be performed without having to connect as SYS. This feature may still
be used at other times.
For example:
recyclebin=off
Windows:
<ADMIN_SCRIPTS_HOME>\adadminsrvctl.cmd start
Mandatory Steps for Custom Schema Upgrade for 11i / 12.0 / 12.1
Note: You must upgrade to release 12.2.2 before performing the
following steps. Do not run adsplice when you are in release 12.2.0.
Custom product top and custom context variables are not synchronized and retained
during cloning because entry for the product in FND_OAM_CONTEXT_CUSTOM and
clone entry is missing for the upgraded custom products. In addition, <oa_customized>
block in the context file is not updated.
1. Updating the CONTEXT_FILE from the OAM window.
Note: You must follow the below steps to retain all custom
products.
Update the custom application from EBS OAM (Oracle Application Manager).
1. From the Oracle Applications Manager ssa page, navigate to:
System Administrator > Oracle Application Manager > License Manager >
SiteMap > AutoConfig > Manage Custom Parameters > ADD
5. Select Next.
6. Verify that all values are correctly shown in the Confirmation window.
8. After adding the custom product 'xxco', there will be an entry for the custom
product at the end of the $CONTEXT_FILE similar to the following:
<oa_customized>
<c_xxco oa_var="c_xxco"
scope="CUSTOM"oa_type="PROD_TOP"oa_enabled="FALSE"><APPL_TOP>/xxc
o/12.0.0</c_xxco>
</oa_customized>
Note: You must perform the above steps for each of the custom
products to be added.
2. Running adsplice.
For the custom products that already exist, in order to lay down the file system, you
must run adsplice on the Run File system. Refer to Creating a Custom Application in
Oracle E-Business Suite Release 12.2 (Doc ID: 1577707.1) for running adsplice.
3. Running Fs_clone.
System Administration:
These tasks must be carried out regardless of the products that are active in your
system.
1. Reset ORACLE schema passwords (recommended)
During the upgrade, Rapid Install preserves the passwords that you set previously
for existing products. However, as it creates a schema for each new product
installed, it sets up a default password derived from the product abbreviation (short
name). To maintain product security, reset these default passwords now.
Note: This step should be executed only after completing the Verify
completion of concurrent programs post-upgrade task.
If you have languages other than American English registered in your system, then
follow instructions in the following step.
7. Installing NLS upgrade patch driver and NLS Online Help (conditional)
Applies to 11i release level: All
TUMS step key: N/A
The NLS upgrade patch driver and the NLS Online Help patch must be called
through AD Online Patching (adop).
1. After you have successfully applied the American English unified driver,
download the NLS Release 12.2 software for each active language in your
system, and run each driver (u10124646.drv) on your Release 12.2 APPL_TOP.
Note that the NLS patch driver has the same name as the American English
patch driver. If you have applied any latest product patches in the previous
step, then download and apply the NLS equivalents of each American English
product-specific patch. As an alternative, you can upgrade your NLS software,
including the NLS versions of the latest product patches applied, by using the
Translation Synchronization Patch.
3. If you have installed American English Online Help in your system, then refer
to the 'Install Online Help' section of the Oracle E-Business Suite NLS Release
Notes for your release level.
Note: See Oracle E-Business Suite NLS Release Notes for your release
level for more information. See also Oracle E-Business Suite
Maintenance Guide for information about applying patches using
ADOP. See Requesting Translation Synchronization Patches (Doc ID:
Note: See Using the CUSTOM Library in the Oracle E-Business Suite
Developer's Guide.
Copy custom shell scripts or reports to the custom application directories and
re-customize the copy as necessary.
Alerts:
These tasks apply to Oracle Alerts.
1. Associate organization names with custom Alert definitions (conditional)
Manually update custom alerts that you want to assign to a particular organization:
1. As the Alerts Manager, navigate to the Alerts form (Alert > Define) and query
the definition.
2. Choose Alert Details, then display the Installations tabbed region in the Alert
Details window.
3. Enter the ORACLE ID and organization name that you want to run this alert
against.
Note: After the upgrade, the deployed WSDL URL information has
already been changed. Therefore, you may have to replace it with the
Note: After the upgrade, the deployed WSDL URL for a generic XML
Gateway service will be changed. You may have to replace it with the
new WSDL URL and service location or address accordingly in Web
service clients while invoking the generic XML Gateway service. For
more information about XML Gateway Web services, see the Oracle
XML Gateway User's Guide.
Human Resources:
1. Apply latest HRMS Legislative Updates (required)
To maintain required legislative compliance, you must apply all legislative data
updates. The updates are maintained regularly to be in line with government and
country-specific legal requirements. See the latest HRMS (HR Global) Legislative
Data Patch (Doc ID: 1469456.1) for information and instructions on how to ensure
that your system is up to date.
Note: If you are using only Oracle HR Shared for use with another
Oracle E-Business Suite product, then DO NOT apply this
legislative data.
Payroll:
These tasks apply only to Oracle Payroll.
1. Install or Update Vertex for Payroll (required)
Oracle Payroll uses the Vertex Quantum Payroll Tax Series in the United States and
Canada. The HRMS data in this release contains version 3.1.0 of this third-party
product. If you run Oracle Payroll in the United States or Canada, then refer to
advanced configuration steps allowed by Payroll, and installing or updating the
Vertex software in Installing Quantum for Oracle Payroll (Doc ID: 224273.1).
Projects Tasks
Compile all Fast Formulas via FFXBCP (Refer Doc ID 167689.1). This step applies to all
customers who are upgrading to Release 12.2 and want to use the HR Rate by Criteria
for labor rates, to be used in forecast or labor cost distribution in the Projects
application.
Product Hub:
These tasks apply only to Oracle Product Hub.
1. Creating Versions of Item Catalog Categories
Applies to: Release 12.0 and 12.1
In EBS release 12.1.2 and higher, you can choose to create a different version of an
item catalog category (ICC) when you change a transaction attribute for structure
component in the ICC if you set the profile option "Enable PIM for Telco Features"
to Yes. When you enable the use of ICC versions, the system automatically creates a
draft version for every new ICC created. You cannot choose to create versions for
some ICCs, but not others. After upgrading from a release prior to 12.1.2 and after
setting the profile option "Enable PIM for Telco Features" to Yes, you must create a
released version for each existing ICC. Oracle provides an upgrade API that
automatically performs this task. A database administrator can invoke the upgrade
API from the back end after you set the profile option "Enable PIM for Telco
Features" to Yes.
Upgrade API Sample Call
• EGO_MTL_SY_ITEMS_EXT_TL
Note: The BPEL 10G integration is not supported in Release 12.2 (the jar
files will be removed). Only the SOA 11g integration processes are
supported from Release 12.2 forward. Therefore, customers upgrading
to Release 12.2 from Release 12.1.x must migrate to SOA 11G
integration and follow the documentation to deploy these processes. If
you are already using the SOA 11G integration in R12.1.3, then it is not
necessary to run the processes.
Note: The BPEL 10G integration is not supported in Release 12.2 (the jar
files will be removed). Only the SOA 11g integration processes are
supported from R12.2 forward. Therefore, customers upgrading to
R12.2 from R12.1.x must migrate to SOA 11G integration and follow the
documentation to deploy these processes. If you are already using the
SOA 11G integration in R12.1.3, then it is not necessary to run the
processes.
System Administration
This section applies to all users, regardless of which products are registered as active.
1. Configure SSL for Web Services (conditional)
If you have implemented Secure Sockets Layer (SSL) and plan to use Web Services,
then you must generate certificates using the Oracle Wallet Manager from your
Note: See Enabling SSL in Oracle E-Business Suite Release 12.2 (Doc
ID: 1367293.1) for more information.
Use the Oracle Wallet Manager to generate the Wallet file. Then, follow these steps
to complete the configuration:
1. Set the s_websrv_wallet_file parameter in the Applications context file to the
location of the Web Services Wallet file. Note that the value is a file location, not
a URL.
UNIX:
/etc/ORACLE/Wallets/system1/exported_wallet
Windows:
d:\oracle\system1\exported_wallet
3. Provide the password for the exported Wallet file by running the following
script:
$FND_TOP/patch/115/sql/txkSetWalletPass.sql
System Maintenance:
1. Delete obsolete product files (recommended)
Delete the product files for the previous release (if you have not done so already).
You may want to retain report output files or customized programs. Output files
are stored in the old log and output subdirectories under each product's top
directory, under the log and output directories you created, or under a common
directory.
To remove obsolete files for an old release, change to the top directory of that
release and enter the following command:
UNIX:
$ rm -rf <old APPL_TOP>
Here is an example:
$ rm -rf /d01/appl/r10
Here is an example:
C:\> rd /s /q \APPL110
3. Update Java Color Scheme profile option for selected users (conditional)
By default, the Java Color Scheme profile option should be set to "standard" for all
sessions for optimal system response time. The upgrade process sets this default
value for all instances. However, setting this profile option to a different value may
work better for some systems. See Oracle E-Business Suite Setup Guide and Oracle
E-Business Suite User's Guide for more information.
To set the parameters, go to the Oracle Applications Manager Site Map and choose
AutoConfig > Applications Node > Edit Parameters. Then, use the Search field to
find OXTA. After you set the parameters, run AutoConfig to regenerate the
wls.properties file
(FMW_Home/Oracle_EBS-app1/applications/oafm/APP-INF/wls.properties).
Note: See Oracle XML Gateway User's Guide for more information.
ECX: System Administrator Email Address Address to which Oracle XML Gateway
error notifications should be sent.
ECX: Server Time Zone Time zone the database server is running in.
Note: See Oracle XML Gateway User's Guide for more information.
• Navigate to Reports > Run > Pick Single Request > Generate ALL Business Views.
If you don't have the Business Views Setup responsibility assigned to the SYSADMIN
user, then complete the following:
• Logon to Oracle E-Business Suite as SYSADMIN.
• Navigate to Security > User > Define and add responsibility Business Views Setup to
the SYSADMIN user.
Note: See the Oracle E-Business Suite Setup Guide. See also the Oracle
E-Business Suite User's Guide.
Note: This appendix describes some of the ways the upgrade changes
your existing products. We assume that you have read about the new
features and products delivered in this release, which is included in the
product-specific Release Content Documents (RCDs) and TOI, on My
Oracle Support.
The discussions of the functional aspects of the upgrade in this appendix are arranged
by products within the Financials and Procurement product family.
Advanced Collections
Changes to Oracle Advanced Collections in the upgrade are described in this section.
Strategy Improvements
Advanced Collections allows editing of 'To be created' work items. The 'To be created'
work items in the current strategy can be overwritten with new Pre-wait/Post-waits and
Collector without creating new Work Items.
Improved Pricing
oklupdincomefee.sql: This script upgrades contracts that have Income Fees with a
single payment. It updates the origination income on Income Fee lines with the fee line
amount. Incomes fees with recurring payments continue to have origination income as
NULL.
This appendix describes the way the upgrade affects your existing Oracle Human
Resource Management System (HRMS) products, and highlights the impact of these
functional changes on your day-to-day business. This section contains products in the
HRMS product family, arranged alphabetically.
This appendix covers the following topics:
• About Business Impact and Functional Changes
• Human Resource Management Systems (HRMS)
• Oracle Payroll
• Oracle iRecruitment
• Oracle Performance Management
• Oracle Succession Planning
Note: This appendix describes some of the ways the upgrade changes
your existing products. Oracle assumes that you have read about the
new features and products delivered in this release, which is included
in the product-specific Release Content Documents (RCDs) and TOI on
My Oracle Support.
The discussions of the functional aspects of the upgrade in this chapter are arranged by
Oracle Payroll
Sparse Matrix
Sparse Matrix functionality is automatically enabled in release 12.2. This effectively
prevents the creation of null run result values if all run result values are null for the
given run result. There is no need to run the ENABLE_SPARSE_MATRIX upgrade
program.
Review the Sparse Matrix Null Result Values Upgrade program.
It is enabled for each legislation and requires a row in the pay_upgrade_legislations
table for the definition SPARSE_MATRIX. The process purges old (null) run result
values that would not have been created if the Sparse Matrix functionality had been
used within the Payroll processes (such as Run, QuickPay, and so on.)
Oracle iRecruitment
2. Suitability Matching
3. Talent Profile
Note: This appendix describes some of the ways the upgrade changes
your existing products. We assume that you have read about the new
features and products delivered in this release, which is included in the
product-specific Release Content Documents (RCDs) and TOI on My
Oracle Support.
The discussions of the functional aspects of the upgrade in this chapter are arranged by
products within the Supply Chain Management product family.
Related Documents
Because Oracle Document Management and Collaboration (DOM ) product is obsoleted
in Release 12.2, the Related Documents feature is not available for Items and Change
Orders.
Attachments Framework
Release 12.2 supports only WebDAV (Web-based Distributed Authoring and
Versioning) integration mode to content management repositories. Webservice
integration mode is not supported. Therefore, on the Repositories Setup page, only the
WebDAV protocol option is available under Integration mode. Existing Repositories
with Webservice integration mode does not display.
Applications Technology
Best Practices for Securing Oracle Applications Release 12.2
Oracle E-Business Suite Concepts
Oracle E-Business Suite Developer's Guide
Oracle Application Framework Developer's Guide (Doc ID: 1315485.1)
Oracle Application Framework Personalization Guide
Oracle E-Business Suite Installation Guide: Using Rapid Install
Oracle E-Business Suite Multiple Organizations Implementation Guide
Oracle E-Business Suite Setup Guide
Oracle E-Business Suite Maintenance Guide
Oracle E-Business Suite Security Guide
Oracle E-Business Suite User Interface Standards for Forms-based Products
Oracle E-Business Suite Integrated SOA Gateway Implementation Guide
Oracle XML Gateway User's Guide
Oracle XML Publisher Administration and Developer's Guide (available within the Oracle
E-Business Suite online help)
User Preferred Time Zone Support in the Oracle Applications Release 12 (Doc ID: 402650.1)
Using AutoConfig to Manage System Configurations with Oracle Applications 12 (Doc ID:
387859.1)
Index-1
verifying database tablespace free space, 4-5 Memory Requirements, 1-8
verifying the database version, 4-3 Migrate Portlets Preferences Store, 5-20
Ensuring Maintenance Mode is Enabled, 3-4 Migrating Database to Oracle 11g Release 2, 3-3
eTRMs Migrating the CUSTOM Library, 5-9
importance of, 1-5
N
F NLS Upgrade Considerations, 1-14
Financials and Procurement Products
financials upgrade impact, A-1 O
Financials and Procurement Tasks, 2-5, 5-11
Obsolete Products in Release 12.2, 1-2
Finish the Upgrade, 3-6, 3-6
Obsolete Technology Integrations, 1-9
configure applications client software, 3-9
Online Patching
configure the instance, 3-6
enabling online patching, 4-3
integrate custom objects, 3-10
overview, 4-1
reapply customizations, 3-9
Oracle E-Business Suite Integrated SOA
re-enable custom triggers, 3-10
Gateway, 5-10
Functional Upgrade Tasks
Oracle XML Gateway, 5-11
upgrade overview, 1-5
Oracle XML Gateway Setup, 5-18
Oracle XML Publisher, 5-19
G Overview
General Information and Required Tasks functional upgrade tasks, 1-5
upgrade overview, 1-4 general information and required tasks, 1-4
technical upgrade tasks, 1-5
H upgrade, 1-1
Overview of Online Patching, 4-1
HRMS Upgrade Impact
about business impact and functional changes,
B-1 P
HRMS, B-2 Perform the Upgrade, 3-1
iRecruitment, B-2 disable AOL audit trail, 3-2
Payroll, B-2 shutting down application tier listeners and
Performance Management, B-2 concurrent managers, 3-3
Succession Planning, B-3 Post Upgrade Steps
Human Resources Tasks, 5-12 mandatory steps for custom schema upgrade
11i / 12.0 / 12.1, 5-4
L Post Upgrade Tasks, 5-1
alerts, 5-10
Languages, 1-14
backing up Oracle E-Business Suite, 5-22
character sets, 1-15
Channel Revenue Management tasks, 5-12
language status, 1-15
Financials and Procurement tasks, 5-11
Lease and Finance Management
Human Resources Tasks, 5-12
financials upgrade impact, A-2
implementing new product and
country-specific functionality, 5-21
M
logging On to Oracle E-Business Suite, 5-22
Maintenance Mode, 1-13 migrate portlets preferences store, 5-20
Maintenance Wizard Oracle Complex Maintenance Repair and
description of, 1-13
Index-2
Overhaul, 5-16 application tier, 1-11
Oracle E-Business Suite Integrated SOA Release Content Documents
Gateway, 5-10 importance of, 1-5
Oracle Manufacturing Operations Center, 5-13 Renamed Files
Oracle Shipping Execution, 5-15 protecting data in, 1-15
Oracle Value Chain Planning, 5-16 Resetting init.ora Parameters, 2-11
Oracle Warehouse Management, 5-16 Reviewing Post-upgrade Tasks, 5-1
Oracle XML Gateway, 5-11 Reviewing Security Practices, 3-5
Product Hub, 5-13 Reviewing User Responsibility Assignments, 5-
Projects tasks, 5-13 10
resizing the database, 5-21 Review Upgrade Tasks, 2-1
reviewing post-upgrade tasks, 5-1 Running the American English Upgrade Patch
review system updates, 5-21 Driver, 3-4
Supply Chain Management tasks, 5-13
system maintenance tasks, 5-17 S
understanding Oracle E-Business Suite System
Scheduling Time for an Upgrade, 1-12
Administration tasks, 5-21
Shutting Down Application Tier Listeners and
Prepare for the Upgrade, 2-9
Concurrent managers, 3-3
Preparing for an Upgrade
Software Requirements, 1-7
migrate or upgrade your database to Oracle
SSL for Web Services, 5-16
11g Release 2, 2-12
Supply Chain Management Tasks, 2-7, 5-13
Preparing for the Upgrade
Supported Upgrade Paths, 1-1
application DBA (AD) tasks, 2-3
System Administration, 5-16
applications technology tasks, 2-3
System Maintenance Post Upgrade Tasks, 5-17
customer relationship management tasks, 2-4
database and system administration tasks, 2-1
T
financials and procurement tasks, 2-5
gather schema statistics, 2-9 Technical Upgrade Tasks
Human Resource Management (HRMS), 2-6 upgrade overview, 1-5
install JRE on the database tier, 2-10 Technology Stack Components, 1-6
perform a system backup, 2-12 Temporary Directory for XML Publisher, 5-19
review upgrade tasks, 2-1 Test Upgrade, 1-14
Rrun Rapid Install, 2-11 The Upgrade Process, 1-2
supply chain management tasks, 2-7 TOIs
Product Documentation importance of, 1-5
Supply Chain Management, D-2 Transport Agent Setup, 5-18
Product Patches
applying latest, 5-7 U
Product-specific Considerations, 1-16 Updating and Verifying Custom Responsibilities,
Projects Tasks, 5-13 5-9
Updating init.ora with Upgrade Parameters, 3-3
R Upgrade
Reference Information business impact, 1-4
finding, 1-5 database upgrade requirements, 1-1
Regenerating Business Views, 5-20 general functional tasks for, 1-5
Release 12.2 Architecture, 1-11 general technical tasks for, 1-5
Index-3
obsolete products, 1-2
overview, 1-1
required reading, 1-5
supported upgrade paths, 1-1
the upgrade process, 1-2
Upgrade By Request, 1-14
Upgrade Patch
installing NLS upgrade patch driver, 5-8
Upgrading to Release 12.2, 3-1
User Preferred Time Zone Support, 1-14
V
Verifying Completion of Concurrent Programs,
5-6
W
Web Services, 1-7
Index-4