Upgrade 9i To 11g DB On Ebs 11i
Upgrade 9i To 11g DB On Ebs 11i
This post is part 2 of the ""11i to R12.1.3 upgrade"" series. For other parts click on below links.
1) Install Fresh EBS 11i on Linux 5 32 Bit (PART 1 in "11i to R12.1.3 upgrade" series)
2) Upgrade database 9.2.0.6 to 11.2.0.4 in EBS 11i (PART 2 in "11i to R12.1.3 upgrade" series)
3) 11i Split configuration- Move 11g Database to Linux 6 64Bit (PART 3 in "11i to R12.1.3
upgrade" series)
4) Upgrade 11i TO R12.1.1 (PART 4 in "11i to R12.1.3 upgrade" series)
5) Upgrade R12.1.1 To R12.1.3 (PART 5 in "11i to R12.1.3 upgrade" series)
1 / 54
Shut down application and database services.
Enter the following commands to unzip and extract the installation files:
$ unzip p4547809_9208_LINUX.zip
$ patchset_directory/Disk1
$ ./runInstaller
3 / 54
4 / 54
5 / 54
6 / 54
[root@r12upg ~]# sh /d01/app/oracle/testdbdb/9.2.0/root.sh
Running Oracle9 root.sh script...
\nThe following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME= /d01/app/oracle/testdbdb/9.2.0
7 / 54
4. Apply additional 9.2.0.8 RDBMS patches
i) Patch 5391326 : APPSST9208 MULTIPLE INDEX ERRORS WHILE RUNNING FULL
IMPORT FOR 9.2.0.8 DB
$ export PATH=$ORACLE_HOME/OPatch:$PATH
Below command must run successfully.
$ opatch lsinventory
Now apply patch
$ cd 5391326
$ opatch apply
ii) Patch 5495695 : APPSST9208: SQL*PLUS EXITS WITH O/S MESSAGE: NO SUCH FILE
OR DIRECTORY
% cd 5495695
% opatch apply
% mv $ORACLE_HOME/sqlplus/lib/sqlplus $ORACLE_HOME/bin/sqlplus
$ sqlplus /nolog
SQL> CONNECT SYS/SYS_password AS SYSDBA
SQL> STARTUP
a) CHECK THE SYSTEM TABLESPACE SIZE (REQUIRED SIZE 10MB;)
TABLESPACE_NAME SUM(BYTES/1024/1204)
------------------------------ --------------------
SYSTEM 2031.6412
b) Make sure that the init.ora parameters SHARED_POOL_SIZE and JAVA_POOL_SIZE are
each 150 MB or more
If necessary, set the value of the initialization parameter to at least 150 MB:
Example (if using spfile):
SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='150M' SCOPE=spfile;
c) Start Listener:
$ lsnrctl start testdb
Review the patch.log file for errors and inspect the list of components that is displayed at the
end of catpatch.sql script.
This list provides the version and status of each SERVER component in the database.
If necessary, rerun the catpatch.sql script after correcting any problems.
Restart database
shutdown
startup
f) **After completion of the above post install steps, connect as SYSDBA and run the following:
SQL> @$ORACLE_HOME/javavm/install/jvmsec3.sql
SQL> @$ORACLE_HOME /javavm/install/jvmsec5.sql
Use SQL*Plus to connect to the database as sysdba and gather the statistics for the SYS
schema using the following commands:
SQL> execute dbms_stats.gather_schema_stats
('SYS',cascade=>TRUE,degree=>20);
$cd $COMMON_TOP/admin/scripts
$ ./adstpal.sh apps/apps
Patch 16699473
• Copy the patch file within your 6i ORACLE_HOME and unzip this file
within it to create a new subdirectory. You will be able to see the
folder 16699473 which contains the actual one-off files.
%cd $ORACLE_HOME
%unzip p16699473_60828_LINUX.zip
%cd 16699473
% sh patch.sh
• Unzip the java class files and regenerate your JAR files
%cd $ORACLE_HOME/16699473
% sh backup.sh
Please run below script to copy all files to $ORACLE_HOME with respective location.
%cd $ORACLE_HOME/16699473
% sh copy_files.sh
• For ewt3.jar please follow these additional steps:
i. Backup the Forms java subtree and extract the changed files
% cd $ORACLE_HOME/forms60/java
% cp -r oracle/ewt oracle/ewt.PREBUG16699473
% jar -xvf $ORACLE_HOME/16699473/ewt3.jar
% rm META-INF/MANIFEST.MF
% rmdir META-INF
ii. Verify that the EWT version has been updated under the
$ORACLE_HOME/forms60/java directory.
For example:
% ls -la oracle/ewt | grep 3_4_49
iii. Now regenerate jar files using adadmin.
• Run adrelink.
Patch 3830807
% cd 3830807
Add execute permission to the script supplied in this patch
% chmod u+x patch.sh
network/jre11/lib/linux/native_threads OR
# $ORACLE_HOME/network/jre11/lib/i686/native_threads
# in $LD_LIBRARY_PATH before running patch.sh
#
# Please check your files under $ORACLE_HOME/network/jre11/lib to see
# which one of the above is appropriate on your system. The same
# $LD_LIBRARY_PATH should be used at run-time.
#
# [5] Run the script supplied by this patch
#
# % ./patch.sh
#
Deploy the latest certified version of the JRE native plug-in by following My Oracle Support
Knowledge Document 290807.1, titled 'Deploying Sun JRE (Native Plug-in) for Windows Clients
in Oracle E-Business Suite 11i'.
DOWNLOAD
> http://www.oracle.com/technetwork/java/javase/downloads/index-jdk5-jsp-142662.html
Now INSTALL
[root@r12upg oracle]# chmod 777 jdk-1_5_0_15-linux-i586-rpm.bin
[root@r12upg oracle]# ./jdk-1_5_0_15-linux-i586-rpm.bin
Do you agree to the above license terms? [yes or no]
yes Unpacking...
Checksumming...
0
0
Extracting...
UnZipSFX 5.50 of 17 February 2002, by Info-ZIP ([email protected]).
inflating: jdk-1_5_0_15-linux-i586.rpm
Preparing... ########################################### [100%]
1:jdk ########################################### [100%]
Done.
Now CONFIGURE:
Selection Command
-----------------------------------------------
+ 1 /usr/lib/jvm/jre-1.4.2-gcj/bin/java
* 2 /usr/java/jdk1.5.0_15/bin/java
This patch contains the required J2SE 5.0 upgrade script, JDBC 9iR2 Drivers for J2SE 5.0, and
the E-Business Suite interoperability patches.
Run the J2SE 5.0 upgrade script to upgrade the configuration template files for each
[APPL_TOP]. Enter the appropriate commands and follow the instructions given by the script:
Run AD Administration, and choose "Generate Product JAR Files" from the "Generate
Applications Files" menu to update appsborg2.zip to include the new JDBC Drivers for the J2SE
5.0 library (jdbc14.zip) and to generate the product JAR files.
Since the AD utilities has been upgraded to use J2SE 5.0, this step will ensure that the jar files
are signed with the key store data that is valid for the new version of J2SE.
Open the $APPL_TOP/admin/adovars.env file and ensure that the environment variables below
are defined. Run the following commands to verify that the environment variables ADJVAPRG
and AFJVAPRG point to the J2SE 5.0 executable. The CLASSPATH and AF_CLASSPATH
environment variables must contain the necessary J2SE 5.0 libraries.
$ADJVAPRG -version
echo $CLASSPATH
$AFJVAPRG -version
echo $AF_CLASSPATH
The output of the version check should display J2SE "1.5.0_x", where x depends on the J2SE
5.0 patch level installed.
Also, Log in to the E-Business Suite and select the "System Administrator" responsibility. Check
the Concurrent/Manager/Administer form and make sure all managers have the corresponding
numbers for their actual and target.
• Customers who have not used the latest version of AutoPatch, delivered via AD Minipack
11i.AD.I.4 (4712852), are suggested to regenerate jar files by running adadmin, selecting the
"Generate Applications Files" option, and subsequently selecting the "Generate product JAR
files" option.
SQL> select patch_level from fnd_product_installations where patch_level like '%AD%';
PATCH_LEVEL
------------------------------
11i.AD.I.2
2.2) Apply main Patch 8815204 - 11g Release 2 interoperability patch for 11.5.10
Pre-Steps
Some other functional steps as mentioned in "WebADI - About Web Applications Desktop
Integrator Mini-pack 11i.BNE.D (Doc ID 287080.1)"
PRE-STEPS
4125550 - ATG 11.5.10 CU2 for ATG Product family
3218526 - BNE Patch 11i.BNE.D
3761838 - FRM Patch 11i.FRM.G
you must then do the following using the adadmin utility, in the order listed below.
Generate message files
Compile APPS schema(s)
Compile flexfield data
Recreate grants and synonyms for APPS schema(s)
Remove image cache files within directory "$OA_HTML/cabo/images/cache" and style sheet
cache files within directory "$OA_HTML/cabo/styles/cache" after the patch is successfully
applied.
IMPORTANT: Change the permissions to 777 on the directories and $OA_HTML/cabo/styles,
so that they are writable by the user who owns the apache process.
POST STEPS:
After applying the unified driver, use AD Administration (adadmin) to compile menu information.
In all cases, next you must do the following using the adadmin utility, in the order listed below.
Generate message files
Compile APPS schema(s)
Compile flexfield data
Recreate grants and synonyms for APPS schema(s)
To ensure optimal performance on Cost Based Optimizer (CBO), you should re-analyze your
application schemas after applying large patches. Execute the concurrent program Gather
Schema Statistics from the System Administrator responsibility and choose ALL schemas.
Depending upon the size of your database, this job may take several hours. However, users
can use the applications while this job is running.
Remove image cache files within directory "$OA_HTML/cabo/images/cache" and style sheet
cache files within directory "$OA_HTML/cabo/styles/cache" after the patch is successfully
applied.
IMPORTANT: Change the permissions to 777 on the directories $OA_HTML/cabo/images and
$OA_HTML/cabo/styles, so that they are writable by the user who owns the apache process.
Apply Post-install Co-requisite Patch (Required)
Apply the following patch.
3854951 - RG FSG XML Publisher Delivery
(ALREADY PRESENT)
Now apply base patch 6241631: Oracle Applications Technology 11i.ATG_PF.H.delta.7 (RUP
7)
PRE-STEPS
Executing the Technology Stack Validation Utility is a mandatory step before you upgrade to
Oracle Applications Technology 11i.ATG_PF.H.delta.7 (RUP7), as this utility lists further
mandatory pre-upgrade steps for your specific instance, such as upgrading to the minimum
required version of Java 5 and other technologies.
In your operating system file system, navigate to the directory where you have unzipped these
Applications Technology Updates
1. Establish the needed environment parameters by sourcing the Applications environment file
as the owner of the application tier file system.
2. Ensure "APPLRGF" variable is set in environment. If not, set it to the same value as
"APPLTMP".
3. From the location where this patch was unzipped, change directory to fnd/patch/115/bin.
4. Run the utility as follows:
./txkprepatchcheck.pl -script=ValidateRollup -outfile=$APPLTMP/txkValidateRollup.html
-appspass=apps
The utility will produce an HTML report. Review and perform any required actions before
proceeding with the Applications Technology Updates.
After test is passed, Now apply the patch using adpatch
POST-STEPS
9053932 - FND: FNDRSRUN Returns No Records When Search Criteria is Date Submitted
PRE-REQ PATCHES for 9053932
3036401 - Mini-Pack 11i.HZ.L
3618299 is latest Patch 11i.HZ.N so we will apply Patch 11i.HZ.N 3618299
No pre-req steps
Apply using adpatch
POST REQ STEPS
You must complete these steps after running the unified driver using AD Administration
(adadmin):
Generate message files.
Compile APPS schema(s).
Compile flexfield data in AOL tables.
Compile menu information.
Now apply base patch 9053932 using adpatch
No post steps
II. Run AutoConfig. (Required)
No pre steps
Apply using adpatch
Download this interm patch 5632264 .. Extract it .. run "opatch apply" command .. As the
following:
VERSION
----------
4
33 / 54
instance, run the following command to create the $ORACLE_HOME/nls/data/9idata directory.
$ perl $ORACLE_HOME/nls/data/old/cr9idata.pl
Now add below env variable also to .profile.
export ORA_NLS10= /d02/app/oracle/product/11.2.0/dbhome_1/nls/data/9idata
$ cd
$ ./runInstaller
Note down invalid objects to compare with invalid ones after the upgrade to 11g:
---------------------------------------------------------------------------------
SQL> set pages 0
SQL> set linesize 170
SQL> select count(*) from dba_objects where status='INVALID';
2
SQL>
SQL> select 'alter '||object_type||' '||owner||'.'||object_name||' compile;' from dba_objects where
status = 'INVALID';
alter PACKAGE BODY APPS.CS_WF_ACTIVITIES_PKG compile;
alter PACKAGE BODY APPS.OKI_REFRESH_PVT compile;
CREATE VIEW
CREATE TABLE
ALTER SESSION
CREATE CLUSTER
CREATE SYNONYM
CREATE SEQUENCE
CREATE DATABASE LINK
So you need to re-grant these privileges to users who have connect role after upgrade to 11g.
This SQL will help you just save the result in somewhere to run it after the upgrade:
Spool off;
SQL> @$ORACLE_HOME/rdbms/admin/utlvalid.sql
SQL> @analyze.sql
23. Ensure the users sys and system have 'system' as their
default tablespace.
SQL> SELECT username, default_tablespace
FROM dba_users
WHERE username in ('SYS','SYSTEM');
Tip: Truncating AUD$ table will speedup the upgrade process (make sure to backup audit data
before truncating it)
SQL> truncate table SYS.AUD$;
PARAMETER VALUE
—————————————————————-
Oracle Database Vault FALSE
DRS_START
GC_FILES_TO_LOCKS
MAX_COMMIT_PROPAGATION_DELAY
PLSQL_NATIVE_LIBRARY_DIR
PLSQL_NATIVE_LIBRARY_SUBDIR_COUNT
SQL_VERSION
hash_join_enabled
DDL_WAIT_FOR_LOCKS
LOGMNR_MAX_PERSISTENT_SESSIONS
PLSQL_COMPILER_FLAGS
Once the parameter file is modified as per your requirement (already done above), copy the file
to the new 11.2.0.3 $ORACLE_HOME/dbs.
export ORACLE_BASE=/u01/oracle//
export ORACLE_HOME=/u01/oracle//db/tech_st/11.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.10.0:$ORACLE_HOME/perl/lib/site_perl/5.10.0
export ORA_NLS10=/u01/oracle//db/tech_st/11.2.0/nls/data/9idata
/etc/oratab entries
#:/u01/oracle//db/tech_st/11.1.0:N
:/u01/oracle//db/tech_st/11.2.0:N
Note: After /etc/oratab is updated to have SID and Oracle Home (11.2), you can execute oraenv
(/usr/local/bin/oraenv) and set the environment. The input has to be the SID which is entered in
/etc/oratab against the 11gR2 home.
$ export ORACLE_SID=testdb
$ cd $ORACLE_HOME/rdbms/admin
$ sqlplus “/ as sysdba”
SQL> startup UPGRADE
Set the system to spool results to a log file for later verification after the upgrade is completed
and start the upgrade script.
Create the SYSAUX tablespace:
----------------------------
SQL>CREATE TABLESPACE SYSAUX
DATAFILE '/d01/app/oracle/testdbdata/sysaux01.dbf' SIZE 2000M reuse
autoextend on next 100m maxsize unlimited
EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO ONLINE;
SQL> set echo on
SQL> SPOOL upgrade.log
SQL> @catupgrd.sql
SQL> spool off
These measures are an important final step to ensure the integrity and consistency of the newly
upgraded Oracle Database software. Also, if you encountered a message listing obsolete
initialization parameters when you started the database for upgrade, then remove the obsolete
initialization parameters from the parameter file before restarting.
Startup the database:
$ Sqlplus / as sysdba
SQL> STARTUP
Now Run catuppst.sql
Run catuppst.sql, located in the $ORACLE_HOME/rdbms/admin directory, to perform upgrade
actions that do not require the database to be in UPGRADE mode.
SQL> @catuppst.sql
SQL> STARTUP
SQL> @utlu112s.sql
SQL> @utlu112s.sql
.
Oracle Database 11.2 Post-Upgrade Status Tool 11-09-2014 07:07:33
.
Component Current Version Elapsed Time
Name Status Number HH:MM:SS
.
Oracle Server
. ORA-01408: such column list already indexed
. VALID 11.2.0.4.0 01:11:37
JServer JAVA Virtual Machine
. VALID 11.2.0.4.0 00:11:02
Oracle Real Application Clusters
. INVALID 11.2.0.4.0 00:00:02
OLAP Analytic Workspace
. VALID 11.2.0.4.0 00:01:13
OLAP Catalog
. VALID 11.2.0.4.0 00:03:19
Oracle OLAP API
. VALID 11.2.0.4.0 00:01:06
Oracle XDK
. VALID 11.2.0.4.0 00:19:21
Oracle Text
. VALID 11.2.0.4.0 00:02:57
Oracle XML Database
. VALID 11.2.0.4.0 00:06:13
Oracle Database Java Packages
. VALID 11.2.0.4.0 00:00:52
Oracle Multimedia
. VALID 11.2.0.4.0 00:14:00
Spatial
. VALID 11.2.0.4.0 00:15:39
Final Actions
. 00:04:39
Total Upgrade Time: 02:32:10
You can ignore ORA-01408: such column list already indexed as shown in output.
14 ows selected.
C) Run dbupgdiag.sql
Check for the integrity of the upgraded database by running dbupgdiag.sql script
Note 556610.1 Script to Collect DB Upgrade/Migrate Diagnostic Information (dbupgdiag.sql)
If the dbupgdiag.sql script reports any invalid objects, run
$ORACLE_HOME/rdbms/admin/utlrp.sql (next step)
After validating the invalid objects, re-run dbupgdiag.sql in the upgraded database once again
and make sure that everything is fine.
D) Run utlrp.sql
Run $ORACLE_HOME/rdbms/admin/utlrp.sql multiple times to validate the invalid objects in the
database, until there is no change in the number of invalid objects.
Note: This step will take some considerable time on first run
If required, Change the compatibility version to use the new 11g features:
alter system set compatible='11.2.0' scope=spfile;
shu immediate;
startup;
39. Install OLAP
Verify that OLAP is installed in your database by using SQL*Plus to connect to the database as
SYSDBA and running the following command:
COMP_ID
------------------------------
AMD
COMP_ID
------------------------------
EXF
AMD
SQL> connect / as sysdba;
SQL> @$ORACLE_HOME/olap/admin/olap.sql SYSAUX TEMP
$ lsnrctl start
Shut down all processes, including the database and the listener, and restart them to load the
new environment settings.
As a result, you must re-create the grants and synonyms in the APPS schema. 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.
49. Enable database vault (conditional)
If you disabled Database Vault, enable it by performing step 7 of Part 2 of document 1091086.1
on My Oracle Support.
Remember that the Oracle Net listener for the database instance, as well as the database
instance itself, need to be started in the 11.2 Oracle home.
Done.
A) 5622511- J2SE 6.0 CONSOLIDATED PATCH FOR USE WITH ORACLE EBS 11.5.10
PRE-REQ PATCHES
5006182 - FIELD SERVICE AND SPARES ROLLUP PATCH FOR 11.5.10
Post steps:
1. Please use the AD Administration Utility to regenerate the message files for
the product Field Service. (csfmdmsg.ldt or csrmdmsg.ldt).
2. Restart QApache Port.
B) 5977502 - EXCEPTION IS RAISED WHEN BUTTON IS PRESSED
Configure all Application Tier Nodes to Support JDK 6
Stop the application
txkrun.pl -script=SetJDKCfg -contextfile=$CONTEXT_FILE -runautoconfig=Yes -appspass=
apps -jdktop= /usr/java/jdk1.6.0_45
Regenerate the Jar Files
Re-source the environment file
Regenerate the product jar files through 'adadmin' with the 'force' option set to 'Yes':
Generate Applications Files menu -> Generate product JAR files
Do you wish to force regeneration of all jar files? [No] ? Yes
Verify
Remove maintenance mode, Restart all Application Tier Server Processes and check
application.
Run the AOL/J test page from a web browser using the following URL:-
http://r12upg.localdomain:8002/OA_HTML/jsp/fnd/aoljtest.jsp
Also,
$ADJVAPRG -version
echo $CLASSPATH
$AFJVAPRG -version
echo $AF_CLASSPATH
iii) Patch 9094950: APPLIED PATCH 8888184 RECEIVE ERRORS FRM-40723 ORA-00911
FRM-40505
Apply using adpatch
iv) Patch 16699473: MERGE REQUEST ON TOP OF 6.0.8.28.0 FOR BUGS 16542522
15828839 16399579
Move the renamed j2se17067.exe file to the web application tier and place it in
$COMMON_TOP/util/jinitiator.
Run the $FND_TOP/bin/txkSetPlugin.sh script against the web node of the application tier.
The txkSetPlugin.sh script will update the new JRE version information into your AutoConfig
context file, update the version used by Workflow and run AutoConfig to incorporate the new
values throughout your application. This script must be run using the following command:
$ txkSetPlugin.sh jversion
$ txkSetPlugin.sh 17067
Verify.
54 / 54