Very recently I have upgraded one of my R12 database instance from 10.2.0.4.0 to 11.2.0.1.0
Current DB instance home /u01/ajidb/10.2.0
Application version 12.1.1
OS version : OEL 4.6
I have followed these steps to do that
The 11.2.0 Oracle home must be installed on the database server node in a different directory than the current Oracle home.
New Oracle Home /u01/oracle/AJI/db/tech_st/11.2.0
Once installed base 11.2.0 software, need to set the following in .bash_profile of oracle user
ORACLE_SID=AJI;
export ORACLE_SID
ORACLE_BASE=/u01/oracle/AJI;
export ORACLE_BASE
ORACLE_HOME=$ORACLE_BASE/db/tech_st/11.2.0;
export ORACLE_HOME
LIBPATH=$ORACLE_HOME/lib:$ORACLE_HOME/odbc/lib;
export LIBPATH
LD_LIBRARY_PATH=$ORACLE_HOME/lib;
export LD_LIBRARY_PATH
PATH=$ORACLE_HOME/bin:$PATH
PERL5LIB=$ORACLE_HOME/perl/lib/5.10.0;
export PERL5LIB
PERL5LIB=$PERL5LIB:$ORACLE_HOME/perl/lib/site_perl/5.10.0;
export PERL5LIB
Install Oracle Database 11g Products from the 11g Examples CD
On the database server node, as the owner of the Oracle RDBMS file system and database instance, perform the tasks in section 3, "Download Oracle Database Examples" in the Oracle Database Examples CD Installation Guide
Create nls/data/9idata directoryOn the database server node, as the owner of the Oracle RDBMS file system and database instance, run the $ORACLE_HOME/nls/data/old/cr9idata.pl script to create the $ORACLE_HOME/nls/data/9idata directory.
Run the Oracle Net Configuration Assistant before running DBUA
When running dbua, set the _disable_fast_validate parameter using the following command: dbua -initParam "_disable_fast_validate=TRUE"
Modify initialization parameters 396009.1, Database Initialization Parameter Settings for Oracle Applications Release 12
Ensure the parameter "_disable_fast_validate=TRUE" is in the initialization file
Apply additional 11.2.0.1 RDBMS patches
Apply the following patches:
- 8328200
- 9218789
- 9318214
- 9657344
- 9719541
- 9756939
4. Shut down Applications server processes and database listenerIf 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
Perform post-install instructions
After the Database Upgrade:
If the Oracle Net listener for the database instance in the new Oracle home has not been started, you must start it now. Since AutoConfig has not yet been implemented, start the listener manually.
Set the TNS_ADMIN environment variable to the directory where you created your listener.ora and tnsnames.ora file
Run adgrants.sql
Copy $APPL_TOP/admin/adgrants.sql from the administration server node to the database server node.
$ sqlplus "/ as sysdba" @adgrants.sql [APPS schema name]
Grant create
procedure privilege on CTXSYS
Copy $AD_TOP/patch/115/sql/adctxprv.sql from the administration server node to the database server node.
$ sqlplus apps/[APPS password] @adctxprv.sql [SYSTEM password] 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');
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]
Implement and run AutoConfig
Implement and run AutoConfig in the new Oracle home on the database server node.
[appsR12@visr12 sql]$ cd $AD_TOP/bin
[appsR12@visr12 bin]$ perl admkappsutil.pl
Starting the generation of appsutil.zip
Log file located at /u01/oracle/AJI/inst/apps/AJI_visr12/admin/log/MakeAppsUtil_08031011.log
output located at /u01/oracle/AJI/inst/apps/AJI_visr12/admin/out/appsutil.zip
MakeAppsUtil completed successfully.
[appsR12@visr12 bin]$
[appsR12@visr12 bin]$ perl admkappsutil.pl
Starting the generation of appsutil.zip
Log file located at /u01/oracle/AJI/inst/apps/AJI_visr12/admin/log/MakeAppsUtil_08031011.log
output located at /u01/oracle/AJI/inst/apps/AJI_visr12/admin/out/appsutil.zip
MakeAppsUtil completed successfully.
[appsR12@visr12 bin]$
Login as Oracle user
[oracle@visr12 11.2.0]$ cp /u01/oracle/AJI/inst/apps/AJI_visr12/admin/out/appsutil.zip $ORACLE_HOME
[oracle@visr12 11.2.0]$ unzip -o appsutil.zip
[oracle@visr12 bin]$ cd $ORACLE_HOME/appsutil/bin
[oracle@visr12 bin]$ perl adbldxml.pl jtop=/usr/java/jdk1.6.0_16
TNS_ADMIN=/u01/oracle/AJI/db/tech_st/11.2.0/network/admin;export TNS_ADMIN
[oracle@visr12 bin]$perl adbldxml.pl jtop=/usr/java/jdk1.6.0_16
Starting context file generation for db tier..
Using JVM from /usr/java/jdk1.6.0_16/bin/java to execute java programs..
APPS Password: apps
The log file for this adbldxml session is located at:
/u01/oracle/AJI/db/tech_st/11.2.0/appsutil/log/adbldxml_08031017.log
/u01/oracle/AJI/db/tech_st/11.2.0/appsutil/log/adbldxml_08031017.log
The log file for this adbldxml session is located at:
/u01/oracle/AJI/db/tech_st/11.2.0/appsutil/log/adbldxml_08031017.log
Enter the value for Display Variable: :1.0
The context file has been created at:
/u01/oracle/AJI/db/tech_st/11.2.0/appsutil/AJI_visr12.xml
[oracle@visr12 bin]$ perl adconfig.sh contextfile=/u01/oracle/AJI/db/tech_st/11.2. 0/appsutil/AJI_visr12.xml appspass=apps
After creating the XML context file, ensure the variable s_jretop points to a proper JRE directory
Gather statistics for SYS schema
Copy $APPL_TOP/admin/adstats.sql from the administration server node to the database server node.
$ sqlplus "/ as sysdba"
SQL> alter system enable restricted session;
SQL> @adstats.sql
$ sqlplus "/ as sysdba"
SQL> alter system disable restricted session;
SQL> exit;
Re-create grants and synonyms
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.
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
Click Requests > Run > Single Request and the OK button. Enter the following parameters
Request Name = Workflow Directory Services User/Role Validation
p_BatchSize = 10000
p_Check_Dangling = Yes
Add missing user/role assignments = Yes
Update WHO columns in WF tables = No
Click "OK" and "Submit".
No comments:
Post a Comment