Prepare to create the 11.2.0 Oracle home
The 11.2.0 Oracle home must be installed on the database server node
in a different directory than the current Oracle home.
Read Chapters 1 and 2 of the
Oracle Database Installation Guide 11g Release 2 (11.2)
for your platform. Also read Chapter 1 and the
"System Considerations and Requirements" section of Chapter 3 of the
Oracle Database Upgrade Guide 11g Release 2 (11.2).
Make sure you thoroughly understand the installation and
upgrade processes.
Perform any step that is relevant for your environment.
| Attention:
For HP Itanium and HP PA RISC platforms using the NFS file system,
choose a disk to install the 11g Oracle home
separate from the database files. The mount options of the disk
containing the database files must include forcedirectio. The 11g
Oracle home (or any other binaries) must not include the forcedirectio
mount option.
|
Install the 11.2.0.3 software
Log in to the database server node as the owner
of the Oracle RDBMS file system and database instance. Ensure
that environment settings, such as ORACLE_HOME, are set for the new
Oracle home you are about to create, and not for any existing
Oracle homes on the database server node. Perform all the steps in
Chapter 4, "Installing Oracle Database"
of the Oracle Database Installation Guide 11g
Release 2 (11.2) for your platform.
In the Installation Types window, use the Product Languages button
to select any languages other than American English
that are used by your Applications database instance. Choose
the Enterprise Edition installation type. In the subsequent windows,
select the options not to upgrade an existing database and to
install the database software only.
Patch p10404530
cd /home/oracle/Patches/DBupgrade
./runInstaller (select the following options )
ignore email
Install Database software only
Single Install Database installation
English
Enterprize Edition
Base path = /opt/oracle
Software Location = /opt/oracle/db/tech_st/11.2.0
Install Oracle Database 11g Products from the
11g Examples CD (mandatory)
On the database server node, as the owner of the Oracle RDBMS file
system and database instance, perform the tasks in the
"Install Oracle Database Examples" section in the
Oracle Database Examples Installation Guide.
In the Installation Types window, use the Product Languages button
to select any languages other than American English
that are used by your Applications database instance.
After the installation, make sure that:
The ORACLE_BASE environment variable must be set
accordingly.
The ORACLE_HOME environment variable points to the
new 11.2.0 Oracle home.
The PATH environment variable includes
$ORACLE_HOME/bin and the directory where the
new perl executable is located (usually $ORACLE_HOME/perl/bin).
The LD_LIBRARY_PATH environment variable includes
$ORACLE_HOME/lib.
The PERL5LIB environment variable points to the
directories where the new perl libraries are located
(usually $ORACLE_HOME/perl/lib/[perl version]
and $ORACLE_HOME/perl/lib/site_perl/[perl version])
vi . /home/oraccle/qamar_11gR2_02.env
export ORACLE_HOME=/opt/oracle/db/tech_st/11.2.0
export ORACLE_SID=PROD
export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/OPatch/:$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
. /home/oraccle/qamar_11gR2_02.env
cd /oracle/Patches/DBUpgrade/dbexp/examples
./runInstaller
Create nls/data/9idata directory
On the database server node, as the owner of the Oracle RDBMS file
system and database instance, use the following command to
create the $ORACLE_HOME/nls/data/9idata directory.
$ perl $ORACLE_HOME/nls/data/old/cr9idata.pl
After creating the directory, make sure that the
ORA_NLS10 environment variable is set to the full path of the
9idata directory whenever you enable the 11g Oracle home.
open new terminal from putty
. /home/oracle/qamar.env
cd $ORACLE_HOME/nls/data/old
perl cr9idata.pl
vi . /home/oraccle/qamar_11gR2_02.env
export ORACLE_HOME=/opt/oracle/db/tech_st/11.2.0
export ORACLE_SID=PROD
export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/OPatch/:$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=$ORACLE_HOME/nls/data/9idata
Apply additional 11.2.0.3 RDBMS patches
Apply the following patches:
For all UNIX/Linux platforms:
For all Windows platforms
| Attention:
While not mandatory for the interoperability of Oracle E-Business
Suite with the Oracle Database, customers may choose to apply
Database Patch Set Updates (PSU) on their Oracle E-Business
Suite Database. If so, please see
Document 1147107.1
('Database Patch Set Update Overlay Patches Required for Use with
PSUs and Oracle E-Business Suite') on My Oracle Support for more
information.
|
Do not run any of the post install instructions as those will be done
after the upgrade.
We Apply :
Patch 4247037
Patch 9858539
Patch 12834800
Patch 12942119
Patch 12951696
Patch 12985184
Patch 13001379
Patch 13004894
Patch 13258936
Patch 13366268
Patch 13477790
Patch 16706896
Shut down Applications server processes and
database listener
On each application tier server node, shut down all
server processes or services. On the database tier server node, shut
down the Oracle Net or Net8 database listener in the old Oracle home.
| Note:
The Applications will be unavailable to users until
all remaining tasks in this section are completed.
|
| Attention:
Make sure that you do not have the LOCAL_LISTENER initialization
parameter set to ensure that the database does not inadvertently
point to a non-existent listener during upgrade.
|
Drop SYS.ENABLED$INDEXES (conditional)
If the SYS.ENABLED$INDEXES table exists, use SQL*Plus to connect
to the database as SYSDBA and running the following command to drop it:
SQL> drop table sys.enabled$indexes;
Disable Database Vault (conditional)
If you have Database Vault installed, perform steps 1 to 6 of Part 2 of
document 1091083.1 on My Oracle Support
to disable Database Vault.
Prepare to upgrade
Read Chapter 2 of
Oracle Database Upgrade Guide 11g Release 2 (11.2).
Take note of the section pertaining to the
Database Upgrade Assistant (DBUA).
| Note:
Ensure that the oratab file contains an entry for the database to be
upgraded.
|
| Attention (Windows only):
Make sure that the Services applet window is closed on the database
server node. You cannot remove the current
database instance service during the upgrade if this window is open.
|
Upgrade the database instance
The instructions for the database upgrade are outlined in
Oracle Database Upgrade Guide 11g Release 2 (11.2) Chapters
3 and 4.
Perform the steps from the "Run the Pre-Upgrade Information Tool"
section to the "Upgrade the Database Using the Database Upgrade
Assistant" section of chapter 3 and any step in chapter 4 that is
relevant to your environment.
In Oracle Database 11g, the DMSYS schema is no longer used. The Data
Mining option is installed in the SYS schema. The 11.2 pre-upgrade tool
has been extended to include a warning that the DMSYS schema should be
dropped. If this warning is reported, it is recommended to drop the
schema as per the
Oracle Data Mining Administrator's Guide 11g Release 2 (11.2).
Removing the DMSYS schema has no effect on the functioning of Data Mining.
Disregard warnings related to Network ACLs. AutoConfig manages all the
E-Business Suite Network ACLs.
When upgrading all statistics tables, note that
Oracle E-Business Suite has only one statistics table,
APPLSYS.FND_STATTAB, that needs to be upgraded.
If you plan to change the PL/SQL compilation mode,
disable the compilation of objects.
. /opt/oracle/db/tech_st/11.1.0/PROD_qamar.env
cd /opt/oracle/db/tech_st/11.2.0/rdbms/admin
sqlplus /nolog
connect / as sysdba
spool upgrade_info.log
@utlu112i.sql
spool off
cd /opt/oracle/db/tech_st/11.1.0/dbs/
vi initPROD.ora
"Add o7_dictionary_accessibility = false
remote_login_passwordfile = exclusive in initPROD.ora"
orapwd file=/opt/oracle/db/tech_st/11.1.0/dbs/orapw password=ics entries=5
BAKCUP
b4dbua.tar.gz
. Up.sh
Increase Tablespace
su -
Add entry PROD:/opt/oracle/db/tech_st/11.1.0:N in /etc/oratab
. qamar_11gR2_02.env
cd /opt/oracle/db/tech_st/11.2.0/bin
./dbua -initParam "_disable_fast_validate=TRUE"
Next
Select the database u want to upgrade
Database = PROD
Oracle Home = /opt/oracle/db/tech_st/11.1.0
next
yes
Unchek Recompile invalid objects at the end of upgrade
next
Select Do no move database files as part of Upgrade
Next
Select Configure The database with Enterprise Manager
and Configure database control for local management
next
give same password as name
error passport poilicy ok
Finish
error to Configure The database with Enterprise Manager
click ok
clik ok
Modify initialization parameters
Common database initialization parameters
Release-specific database initialization
parameters for 11gR2
Database initialization parameter sizing
Attention:
If you encounter the error:
ORA-04030: out of process memory when trying to allocate 822904 bytes
(pga heap, kco buffer)
ORA-07445: exception encountered: core dump [dbgtfdFileWrite()+48]
then set the _pga_max_size initialization parameter to a larger value
as follows:
_pga_max_size=104857600
Restart your database.
|
If native compilation of PL/SQL code is disabled in your
database instance, ignore the initialization parameters that
pertain to the native compilation of PL/SQL code.
Ensure that the temporary tablespace is properly defined. Follow
the instructions in the Temporary Tablespace Setup section.
| Note:
There are many ways to generate the parameter file
(for example, copying and updating an old init.ora parameter file).
You are not confined to using the parameter files generated by the
database upgrade assistant.
|
Perform patch post-install instructions
Run all the patch post install instructions except for those of 13001379
and 13366268. There is no need to run the post install instructions of
13001379 and 13366268 as they are run as part of the database upgrade.
cd /opt/oracle/db/tech_st/11.2.0/rdbms/admin/
sqlplus / as sysdba
Run following files as sysdba
@catnomtt.sql
@catnomta.sql
@dbmsmeta.sql
@dbmsmeti.sql
@dbmsmetu.sql
@dbmsmetb.sql
@dbmsmetd.sql
@dbmsmet2.sql
@catmeta.sql --
@prvtmeta.plb
@prvtmeti.plb
@prvtmetu.plb
@prvtmetb.plb
@prvtmetd.plb
@prvtmet2.plb
@catmet2.sql
-- recompile dbms_metadata_int to enable the diffing code
alter package dbms_metadata_int compile plsql_ccflags = 'ku$xml_enabled:true';
-- recompile dbms_metadata_util to enable the xmlschema load code
alter package dbms_metadata_util compile plsql_ccflags = 'ku$xml_enabled:true';
cd /home/oracle/Patches/DBUpgrade/12951696
sqlplus / as sysdba
@postinstall.sql
exit
cd $ORACLE_HOME/ctx/admin/ctxpatch/
sqlplus / as sysdba
@ctxpatch11203.sql
exit
cd /opt/oracle/db/tech_st/11.2.0/rdbms/admin
sqlplus /nolog
connect / as sysdba
@utlrp.sql
(Only 47 obj remain invalid)
down db stop listerner
reboot
exit from putty
Natively compile PL/SQL code (optional)
You can choose to run Oracle E-Business Suite 12.1 PL/SQL database
objects in natively compiled mode with Oracle Database 11g. See the
"Compiling PL/SQL Program Units for Native Execution"
section of Chapter 12
of Oracle Database PL/SQL Language Reference 11g Release 2 (11.2).
Start the new database listener (conditional)
| Attention:
Set the TNS_ADMIN environment variable to the directory where
you created your listener.ora and tnsnames.ora files. | | |
. qamar_11gR2_02.env
netca
start db
in listner ora file
add
PROD =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = qamar.com)(PORT = 1521))
)
)
SID_LIST_PROD =
(SID_LIST =
(SID_DESC =
(ORACLE_HOME= /opt/oracle/db/tech_st/11.2.0)
(SID_NAME = PROD)
)
)
vi /home/oracle/qamar_11gR2_02.env
export ORACLE_HOME=/opt/oracle/db/tech_st/11.2.0
export ORACLE_SID=PROD
export TNS_ADMIN=/opt/oracle/db/tech_st/11.2.0/network/admin
export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/OPatch/:$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=$ORACLE_HOME/nls/data/9idata
Run adgrants.sql
Copy $APPL_TOP/admin/adgrants.sql (adgrants_nt.sql
for Windows) from
the administration server node to the database server node.
Use SQL*Plus to connect to the database as SYSDBA and run the
script using the following command:
$ sqlplus "/ as sysdba" @adgrants.sql (or adgrants_nt.sql)
[APPS schema name]
| Note:
Verify the usage of adgrants.sql in the adgrants.sql script. Older
versions of adgrants.sql require the APPLSYS schema name parameter to
be passed instead of APPS. | |
New putty
. qamar_11gR2_02.env
cd /opt/oracle/apps/apps_st/appl/admin
sqlplus / as sysdba @adgrants.sql APPS
Grant create procedure privilege on CTXSYS
Copy $AD_TOP/patch/115/sql/adctxprv.sql from
the administration server node to the database server node.
Use SQL*Plus to connect to the database as APPS and run the
script using the following command:
$ sqlplus apps/[APPS password] @adctxprv.sql \
[SYSTEM password] CTXSYS
cd /opt/oracle/apps/apps_st/appl/ad/12.0.0/patch/115/sql/
sqlplus apps/apps @adctxprv.sql manager CTXSYS
- Set CTXSYS parameter
Use SQL*Plus to connect to the database as SYSDBA and run the
following command:
$ sqlplus "/ as sysdba"
SQL> exec ctxsys.ctx_adm.set_parameter('file_access_role', 'public');
sqlplus / as sysdba
exec ctxsys.ctx_adm.set_parameter('file_access_role', 'public');
- Validate Workflow ruleset
On the administration server node, use SQL*Plus to connect
to the database as APPS and run the
$FND_TOP/patch/115/sql/wfaqupfix.sql script using the following
command:
$ sqlplus [APPS user]/[APPS password] @wfaqupfix.sql\
[APPLSYS user] [APPS user]
cd /opt/oracle/apps/apps_st/appl/fnd/12.0.0/patch/115/sql
sqlplus apps/apps @wfaqupfix.sql APPLSYS apps
Deregister the current database
server (conditional)
If you plan to change the database port, host, SID, or database
name parameter on the database server, you must also update
AutoConfig on the database tier and deregister the current
database server node.
Use SQL*Plus to connect to the database as APPS and run the
following command:
$ sqlplus apps/[APPS password]
SQL> exec fnd_conc_clone.setup_clean;
sqlplus apps/apps
exec fnd_conc_clone.setup_clean;
Implement and run AutoConfig
Implement and run AutoConfig in the new Oracle home
on the database server node. If the database listener
of the new Oracle home is defined differently than the
old Oracle home, you must also run AutoConfig
on each application tier server node to
update the system with the new listener.
See Using AutoConfig to Manage System Configurations with Oracle E-Business Suite Release 12
on My Oracle Support for instructions on how to implement and
run AutoConfig. Section 3.2 explains how to generate a context file
on the database tier.
Shut down all processes, including the database and the listener,
and restart them to load the new environment settings.
| Attention:
For Windows customers, after creating the XML context file, ensure
that the variable s_dlsnname has the proper listener service name.
|
| Attention:
After creating the XML context file, ensure the variable s_jretop
points to $ORACLE_HOME/jdk/jre and is not altered to any
other value. | | |
. /opt/oracle/apps/apps_st/appl/APPSPROD_qamar.env
cd /opt/oracle/apps/apps_st/appl/ad/12.0.0/bin
perl admkappsutil.pl
go on DB Node
cd /opt/oracle/db/tech_st/11.2.0/
cp -r appsutil appsutil.mst
cp appsutil.zip appsutil.zip.mst
on appps node
cd /opt/oracle/inst/apps/PROD_qamar/admin/out/
scp appsutil.zip oracle@192.168.200.20:/opt/oracle/db/tech_st/11.2.0/
on dbnode
. /opt/oracle/db/tech_st/11.1.0/PROD_qamar.env
unzip -o appsutil.zip
cd appsutil
cd bin
perl adbldxml.pl appsuser=apps appspass=apps jtop=/opt/oracle/db/tech_st/11.2.0/jdk/
(Display Value = qamar:0.0)
sh adconfig.sh contextfile=/opt/oracle/db/tech_st/11.2.0/appsutil/PROD_qamar.xml
cd ..
cd scripts
cd PROD_qamar
./adautocfg.sh
------------------------
3. Update application tier context file with new database listener port number (conditional)
s_dbhost = New database hostname
s_dbdomain = New database domain name
s_db_serv_sid = New database SID
s_dbport = New database listener port
s_apps_jdbc_connect_descriptor = NULL
nothing to do
----------------
cd /opt/oracle/inst/apps/PROD_qamar/admin/scripts
./adautocfg.sh
- Apply post-upgrade ECX patch
If you are on E-Business Suite Release 12.0, apply ECX
Patch 9922442.
If you are on E-Business Suite Release 12.1, apply
Patch 9151516.
apply Patch 9151516.
Gather statistics for SYS schema
Copy $APPL_TOP/admin/adstats.sql from the
administration server node to the database server node.
Note that adstats.sql has to be run in restricted mode.
Use SQL*Plus to connect to the database as SYSDBA and
use the following commands to run adstats.sql in restricted mode:
$ sqlplus "/ as sysdba"
SQL> alter system enable restricted session;
SQL> @adstats.sql
$ sqlplus "/ as sysdba"
SQL> alter system disable restricted session;
SQL> exit;
| Note:
Make sure that you have at least 1.5 GB of free
default temporary tablespace.
|
cd /opt/oracle/apps/apps_st/appl/admin
$ sqlplus / as sysdba
SQL> alter system enable restricted session;
SQL> @adstats.sql
$ sqlplus "/ as sysdba"
SQL> alter system disable restricted session;
SQL> exit;
Create Demantra privileges (conditional)
If you are using Demantra, perform the steps in
document 730883.1
on My Oracle Support.
Skip in our case
Re-create custom database links
(conditional)
If the Oracle Net listener in the 11.2.0 Oracle home is defined
differently than the one used by the old
Oracle home, you must re-create any custom self-referential
database links that exist in the Applications database instance.
To check for the existence of database links, use SQL*Plus on the
database server node to connect to the Applications database
instance as APPS and run the following query:
$ sqlplus apps/[apps password]
SQL> select db_link from all_db_links;
The EDW_APPS_TO_WH and APPS_TO_APPS database links, if they exist,
should have been updated with the new port number by
AutoConfig in the previous step.
If you have custom self-referential database links in the database
instance, use the following commands to drop and re-create them:
$ sqlplus apps/[apps password]
SQL> drop database link [custom database link];
SQL> create database link [custom database link] connect to
[user] identified by [password] using
'(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=[hostname])
(PORT=[port number]))(CONNECT_DATA=(SID=[ORACLE_SID])))';
where [custom database link], [user], [password],
[hostname], [port number], and [ORACLE_SID]
reflect the new Oracle Net listener for the database instance.
No need working fine
Re-create grants and synonyms
Oracle Database 11g Release 2 (11.2) contains new functionality
for grants and synonyms compared to previous database releases.
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.
. /opt/oracle/apps/apps_st/appl/APPSPROD_qamar.env
adadmin - Recreate grant and sysnonym - 4-2
Enable Database Vault (conditional)
If you disabled Database Vault, enable it by performing step 7
of Part 2 of
document 1091083.1 on My Oracle Support.
Skip no need
Restart Applications server processes
Restart all the Application tier server processes that you shut down
previously. 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. Users may return to the system.
- Synchronize Workflow views
Log on to Oracle E-Business Suite with the "System Administrator"
responsibility.
Click Requests > Run > Single Request and the OK button.
Enter the following parameters:
- Request Name = Workflow Directory Services User/Role Validation
- Batch Size = 10000
- Fix dangling users = Yes
- Add missing user/role assignments = Yes
- Update WHO columns in WF tables = No
Click "OK" and "Submit".
No comments:
Post a Comment
Note: only a member of this blog may post a comment.