This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Table of contents Abstract........................................................................................................................................1 Prerequisites ...............................................................................................................................1 Introduction .................................................................................................................................1 Oracle E-Business Suite 12.1.3 upgrade ..................................................................................2
Oracle E-Business Suite 12.1.1 installation............................................................................................. 2 Upgrade Oracle EBS database from 11.1.0.7 to 11.2.0.3 ....................................................................... 3
4
10
13
19
2323
23
23
23
23
24
24
24
24
25
26
27
Upgrade the EBS database from 11.1.0.7 to 11.2.0.3 ...................................................... Upgrade EBS application server to 10.1.3.5 ......................................................................................... Upgrade Java......................................................................................................................................... Apply EBS 12.1.3 RUP ..........................................................................................................................
Appendix 1................................................................................................................................. Starting applications tier services .......................................................................................................... Shutting down application tier services.................................................................................................. Running adautocfg.sh on applications tier............................................................................................. Running adautocfg.sh on database tier ................................................................................................. Applying patches using adpatch ............................................................................................................ Applying DB patches.............................................................................................................................. Shutdown database tier ......................................................................................................................... Startup database tier.............................................................................................................................. Running Autoconfig on applications tier ................................................................................................ Applications tier maintenance mode......................................................................................................
About the authors ..................................................................................................................... Trademarks and special notices..............................................................................................
1
Abstract This white paper introduces the process of upgrading Oracle E-Business Suite (EBS) from 12.1.1 to 12.1.3 on AIX® 7.1. The Oracle Rapidwiz installer allows installation of EBS 12.1.1 Database and Application tiers on a single or multi-node configuration. An upgrade to EBS 12.1.3 must be done by upgrading the two tiers and services on an existing EBS 12.1.1 configuration. This document outlines the upgrade process and provides tips and hints to help make the process simpler and more predictable.
Prerequisites The document assumes a working knowledge of Oracle E-Business Suite.
Introduction Oracle E-Business Suite primarily consists of three tiers:
Database Tier Application Tier Desktop Tier
The database tier holds the application metadata along with the transactional data. The database tier could be a single or multi-node Oracle RAC setup. With the default EBS 12c RapidWiz installation, Oracle Database 11g Release 1 11.1.0.7 gets installed.
The application tier consists of two Oracle Application Server instances with 2 different versions. Oracle Application Server 10.1.2 runs the Oracle Web Services and renders the HTML web pages while Oracle Application Server 10.1.3 hosts and services the Oracle Forms and Reports. These two application server
instances share the file system. The application tier can as well be single node or multi-node providing seamless scalability to Oracle EBS.
The desktop tier in Oracle EBS runs in compatible browsers like Mozilla Firefox or Internet Explorer. The
EBS end user interface is a combination of JSP/HTML pages and Applet based Oracle Forms. Depending upon the module selected, the respective pages are launched. It is mandatory to have compatible version of Sun J2SE Java™ plug-in enabled in the browser to be able to run Oracle E-
Figure 1. Oracle E-Business Suite 12.1 hihg-level architecture
Oracle E-Business Suite 12.1.3 upgrade In this document, we provide instructions, tips and guidelines for a 2-node configuration (i.e. database and app tiers on different nodes) on AIX 7.1 TL1.
The following configuration settings were used in this whitepaper; wherever not mentioned, use the default settings such as users, passwords, service ports etc.
Users/Groups
Database tier user/group: oracle/dba
Applications tier user/group: applmgr/dba
Installation base locations
Database tier: /d01
Applications tier: /d02
Oracle E-Business Suite 12.1.1 installation
Detailed instructions about Oracle EBS 12.1.1 installation on AIX can be obtained from the whitepaper
titled Oracle E-Business Suite Release 12 Installation and Tips for IBM AIX - Erik Salander, Erik Kane (Mar 2009).
Also, refer to the Oracle Support Note: Oracle E-Business Suite Installation and Upgrade Notes Release
12 (12.1.1) for IBM AIX on Power Systems (64-bit) (Doc ID: 761569.1)
Hint: Certain EBS 12.1.3 patches require latest filesets to be available. So, on AIX 7.1 we recommend upgrading to at least 7100-01-08-1334.
Hint: Apply the Rapid Install startCD patch 12.1.1.13 or later – patch 11072566.
After the installation, please make sure that there are at least three Oracle Home entries in the inventory. The steps to check this are as follows:
1. Login to the node where the database server is running. The inventory is typically maintained in a directory parallel to the directory where database is installed.
2. Navigate to the directory .../oraInventory/ContentsXML/ and open the file inventory.xml.
3. This file should have at least three entries corresponding to the different Oracle Homes for database and the two application server homes. E.g: <INVENTORY>
1. Login as the applications tier user (e.g. applmgr). 2. Shutdown applications tier but keep database tier up and running.
3. Put the applications tier in maintenance mode using adadmin. 4. Apply the following patches using adpatch:
a. 9062910
b. 8919489 c. 9583541 d. 9868229
e. 11071569 f. 10163753 (apply patch using adpatch preinstall=y)
5. Apply following AutoConfig patches:
a. 9738085 b. 9852070 c. 12686610
6. Make appsutil.zip on the applications tier and copy it on the database tier. 7. Execute adautocfg first on the database tier and then the applications tier. 8. Take the applications tier out of maintenance mode.
9. Restart applications tier and validate Oracle EBS operations.
Upgrade the EBS database from 11.1.0.7 to 11.2.0.3
1. Shutdown the application tier services and then the existing Oracle Database 11g Release 1
instance. 2. Install Oracle Database11g Release 2 database software in a new $ORACLE_HOME (in this
whitepaper, Oracle Database 11g Release 2 software is installed under $ORACLE_BASE:
/d01/ora). 3. Post-installation, set the following environment variables in your oracle profile:
vi. Execute utlu112i_5.sql again, until all errors are taken care of.
9. Upgrade database using DBUA. Hint: Start the upgrade in a VNC session especially since the upgrade may take time. a. Before starting the upgrade, execute the following statements on the existing Oracle
Starting context file generation for db tier.. Using JVM from /d01/ora/product/11.2.0/dbhome_1/jdk/jre/bin/java to execute java programs..
APPS Password: apps ... Enter the value for Display Variable: oracle188:1.0
The context file has been created at: /d01/ora/product/11.2.0/dbhome_1/appsutil/VIS_oracle188.xml
iii. Check configuration:
oracle188 EBS-DB /d01/ora/product/11.2.0/dbhome_1/appsutil/bin$ ./adchkcfg.sh contextfile=/d01/ora/product/11.2.0/dbhome_1/appsutil/VIS_oracle188.xml Enter the APPS password: apps
AutoConfig is running in test mode and building diffs...
$cd /d01/ora/product/11.2.0/dbhome_1/appsutil/scripts/VIS_oracle188 $./adconfig.sh contextfile=/d01/ora/product/11.2.0/dbhome_1/appsutil/VIS_oracle188.xml Enter the APPS user password: apps
... AutoConfig completed successfully.
d. Run adconfig on the applications tier:
i. copy 2.3 zip into the PATH on Apps node and then run $ cd /d02/oracle/VIS/apps/apps_st/appl/ad/12.0.0/bin $ ./adchkcfg.sh
contextfile=../../../../../../inst/apps/VIS_oracle187/appl/admin/VIS_oracle187.xml Enter the APPS password: apps ...
AutoConfig completed successfully. ii. run adautoconfig
2. Remove file access permission for 10.1.3 ORACLE_HOME for other OS users oracle187 EBS-APP /d02/oracle/VIS/inst/apps/VIS_oracle187/ora/10.1.3$ chmod -R go-rwx $ORACLE_HOME
3. Add ant/bin to $PATH oracle187 EBS-APP /home/applmgr$ export PATH=$PATH:$ORACLE_HOME/ant/bin
4. Re-build inventory
Refer to the Oracle Support Note: R12.0 / R12.1 : How To Create, Update or Rebuild The Central Inventory For Oracle Applications E-Business Suite (Doc ID 742477.1)
Hint: ensure swap has at least 2G and /tmp has at least 1G available 5. Backup 10.1.3 $ORACLE_HOME, oraInventory, etc.
NOTE: Ensure enough disk space is available to store backup
oracle187 EBS-APP /d02/oracle$ tar cvf oraInventory.tar /d02/oracle/VIS/apps/tech_st/10.1.3/ oracle187 EBS-APP /d02/oracle$ tar cvf oraInventory.tar oraInventory/ oracle187 EBS-APP /d02/oracle$ cp /etc/oraInst.loc ./oraInst.loc.orig
6. Upgrade OPatch to at least 1.0.0.0.58 a. Check existing OPatch version
oracle187 EBS-APP /d02/oracle/VIS/apps/tech_st/10.1.3/OPatch$ opatch version
Oracle Interim Patch Installer version 1.0.0.0.57 ... OPatch Version: 1.0.0.0.57
b. Download right OPatch patch (choose 10.1.0.0.0 release) c. Apply patch by simply unziping in the right place
b. p8920270 i. Unzip p8920270_101350_AIX64-5L.zip /tmp/p8920270
ii. cp other.jar /tmp/p8626084/Disk1/stage/Patches/oracle.as.j2ee.top/10.1.3.5.0/1/DataFiles c. Update following scripts
i. Add following lines in /d02/oracle/VIS/apps/tech_st/10.1.3/root.sh after the "$CHMOD -R
g-w $ORACLE_HOME" line $CHMOD go+r $ORACLE_HOME/Apache/Apache/libexec/*.so $CHMOD go+r $ORACLE_HOME/Apache/modplsql
ii. Change following lines in /d02/oracle/VIS/apps/tech_st/10.1.3/root.sh: ORACLE_HOME=/data1/R12/ab/apps/XB9R1211/apps/tech_st/10.1.3 ORACLE_OWNER=porting
HINT: update /d02/oracle/VIS/apps/tech_st/10.1.3/inventory/ContentsXML/comps.xml Search and replace /data1/R12/ab/apps/XB9R1211/apps/tech_st/10.1.3 with /d02/oracle/VIS/apps/tech_st/10.1.3
Ensure that app tier is up and running d. Start vncserver as applmgr and follow below instructions in the VNC session:
Environments d. Update the value of the environment variable "Tools OH LD_LIBRARY_PATH" (context
variable s_tools_ldlib). This environment variable consists of a list of values of library paths for
the Tools Oracle Home, separated by colons on UNIX and semicolons on Windows. e. Append <10.1.2 OH>/jdk/jre/lib/ppc to the the original (existing) value, replacing <10.1.2 OH>
with the actual path to your 10.1.2 Oracle Home (for example,
/d1/oracle/PROD/apps/tech_st/10.1.2). f. Confirm that the resulting new value of "Tools OH LD_LIBRARY_PATH" looks something like
the following, with a path that reflects your own system: <Original
Value>:/d1/oracle/PROD/apps/tech_st/10.1.2/jdk/jre/lib/ppc where <Original Value> is the existing value of "Tools OH LD_LIBRARY_PATH".
g. Regenerate AutoConfig configuration files
$ su – applmgr $ /d02/oracle/VIS/inst/apps/VIS_oracle187/admin/scripts/adautocfg.sh appspass=apps
h. Restart Oracle E-Business Suite application tier services.
7. Test JDK version a. Create JDKtest.jsp file
Create file under OA_HTML directory containing following line:
Look under /d02/oracle/VIS/apps/apps_st/appl/admin/adovars.env to see which directory is OA_HTML The JDK version is: <%= System.getProperty("java.version") %>
b. Compile JDKtest.jsp script oracle187 EBS-APP /d02/oracle/VIS/apps/apps_st/comn/webapps/oacore/html$ export FND_TOP=/d02/oracle/VIS/apps/apps_st/appl/fnd/12.0.0
Visit http://[web server]:[port]/OA_HTML/JDKtest.jsp Results should be something like The JDK version is: 1.6.0_15
d. Check JDK version and CLASSPATH
Open the $APPL_TOP/admin/adovars.env file and ensure that the environment variables below are defined. ADJVAPRG=/d02/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/jre/bin/java
8. Verify Oracle E-Business Suite concurrent programs.
a. Log in to Oracle E-Business Suite and select the "System Administrator" 1. responsibility. b. Check the Concurrent --> Manager --> Administer form and ensure that all managers have
the appropriate numbers for their actual and target.
9. Apply patch 12965674 a. Stop both applications and database tier services. b. Set 10.1.3 ORACLE_HOME
c. oracle187 EBS-APP /home/applmgr$ export ORACLE_HOME=/d02/oracle/VIS/apps/tech_st/10.1.3
iv. Run adautoconfig v. Connect to database and check that EBS is upgraded:
SQL> select release_name from apps.fnd_product_groups; RELEASE_NAME --------------------------------------------------
12.1.3 vi. Disable maintenance mode and start app node; validate operations vii. Stop applications node and enable maintenance mode
viii. Apply country specific patches as mentioned in the patch README.txt post-install section c. Patch 9239095
i. Run adpatch
4. Carry out post-upgrade steps. a. Patch 9817770
Pre-requisites:
9239089: already applied 8919491: Doc ID 1066312.1 (pre-req 12964564) i. merge and apply 8919491 and 12964564
ii. unzip both patches under a certain directory, say /patch/8919491 and /patch/12964564 iii. make sure there’s no other patch under /patch iv. mkdir /patch/merge
v. cd /patch/merge vi. . /d02/oracle/VIS/apps/apps_st/appl/APPSVIS_oracle187.env vii. admrgpch /patch /patch/merge
Hint: run /usr/sbin/slibclean as root to prevent certain linker errors during patching viii. adpatch ix. choose 'u_merged.drv' as the driver
x. do adpatch for 9817770 b. Patch 9966055
i. Run adpatch
5. Update DB tier nodes with 12.1.3 code level. Applications Tier: a. Use adadmin to disable maintenance mode
b. Run autoconfig $ . /d02/oracle/VIS/apps/apps_st/appl/APPSVIS_oracle187.env $ /d02/oracle/VIS/inst/apps/VIS_oracle187/admin/scripts/adautocfg.sh appspass=apps
c. Create appsutil.zip and copy on database node $ perl /d02/oracle/VIS/apps/apps_st/appl/ad/12.0.0/bin/admkappsutil.pl $ scp /d02/oracle/VIS/inst/apps/VIS_oracle187/admin/out/appsutil.zip
root@oracle188:/d01/ora/product/11.2.0/dbhome_1
Database Tier:
a. Unzip appsutil.zip b. Go to 11gR2 $ORACLE_HOME c. Ensure appsutil.zip file has right permissions for oracle:dba
oracle187 EBS-APP /home/applmgr$ $AD_TOP/bin/admkappsutil.pl 3. Copy the appsutil.zip file to the database tier and set its permissions to database tier user
oracle187 EBS-APP /home/applmgr$ scp
/d02/oracle/VIS/inst/apps/VIS_oracle187/admin/out/appsutil.zip root@oracle188:/d01/oracle/VIS/db/tech_st/11.1.0 oracle188 DB /# chown oracle:dba /d01/oracle/VIS/db/tech_st/11.1.0/appsutil.zip
4. Unzip the appsutil.zip on the database tier and run adautocfg.sh: oracle188 DB /# su – oracle oracle188 EBS-DB /home/oracle$ cd /d01/oracle/VIS/db/tech_st/11.1.0/
The EBS applications tier can be put in maintenance mode using the adadmin tool. First, source the environment file on the applications tier and then run the adadmin utility.
Note: Default password for ‘SYSTEM’ ORACLE schema is ‘manager’ and default password of the Application Object Library [APPS] is ‘apps’.
About the authors Vishal Agarwal is a senior technical consultant at the IBM India Software Labs in Bangalore, India. As part of the IBM STG ISV enablement team, Vishal is involved in technical enablement of cloud offerings
on the IBM Power platform. Prior to joining IBM, he has worked on various UNIX® server technologies as a systems and application programmer, platform migration expert and performance consultant.
Shashi Ranjan is a senior technical consultant at the IBM India, GTS Cloud SSA in Bangalore, India. As part of the IBM Cloud SSA team, Shashi is involved in technical enablement of IBM sales and presales cloud teams for various products and technologies. Prior to joining IBM, he has worked on various Oracle
technologies as an architect, a systems and application programmer and business analyst.
References in this document to IBM products or services do not imply that IBM intends to make them
available in every country.
AIX, IBM, and the IBM logo are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both:
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other company, product, or service names may be trademarks or service marks of others.
The information provided in this document is distributed “AS IS” without any warranty, either express or implied.
The information in this document may include technical inaccuracies or typographical errors.
All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance
characteristics may vary by customer.
Information concerning non-IBM products was obtained from a supplier of these products, published announcement material, or other publicly available sources and does not constitute an endorsement of
such products by IBM. Sources for non-IBM list prices and performance numbers are taken from publicly available information, including vendor announcements and vendor worldwide homepages. IBM has not tested these products and cannot confirm the accuracy of performance, capability, or any other claims
related to non-IBM products. Questions on the capability of non-IBM products should be addressed to the supplier of those products.
All statements regarding IBM future direction and intent are subject to change or withdrawal without
notice, and represent goals and objectives only. Contact your local IBM office or IBM authorized reseller for the full text of the specific Statement of Direction.
Some information addresses anticipated future capabilities. Such information is not intended as a
definitive statement of a commitment to specific levels of performance, function or delivery schedules with respect to any future products. Such commitments are only made in IBM product announcements. The information is presented here to communicate IBM's current investment and development activities as a
good faith effort to help with our customers' future planning.
Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending
upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput or performance improvements equivalent to the
ratios stated here.
Photographs shown are of engineering prototypes. Changes may be incorporated in production models.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part
of the materials for this IBM product and use of those Web sites is at your own risk.