Archive for the ‘Upgrade’ Category

R12.1.3 EBS Database 11.2.0.2 Upgrade to 12c 12.1.0.2   8 comments

Server Configuration:
——————–
RAM:16GB
CPU’s-4
Operating System: OEL 5.5.
Oracle EBS Version: R12.1.3
Oracle EBS Database Version 11.2.0.2(Before Upgrade)

Ref: Interoperability Notes EBS 12.0 or 12.1 with RDBMS 12cR1 (Doc ID 1524398.1)

Apply Below ApplicationPatches:

If you already on R12.1.3 then non need to apply Patch 9239090 – Oracle E-Business Suite 12.1.3

Apply Patch 12923944
Apply Patch 13473483
Apply Patch 16289505 – 12c Release 1 interoperability patch for Release 12.1
Apply Patch 18843706
Apply Patch 19558309

Step1:Prepare to create the 12.1.0 Oracle home

-Install Oracle Software 12c
mkdir -p /d01/oracle/PROD/db/tech_st/12c
10-3-2014 11-07-52 AM

Download below patchsets for 12c database
p17694377_121020_Linux-x86-64_1of8.zip
p17694377_121020_Linux-x86-64_2of8.zip
p17694377_121020_Linux-x86-64_7of8.zip

Unzip and run the runInstaller

1

2

3

4

5

6

7

new

9

10

11

12

13

14

15

16

17

Step2: Install Examples CD

10-3-2014 11-31-36 AM

10-3-2014 11-31-55 AM

10-3-2014 11-32-10 AM

10-3-2014 11-32-25 AM

10-3-2014 11-32-34 AM

10-3-2014 11-32-50 AM

Step3:
Create nls/data/9idata directory

On the database server node, as the owner of the Oracle RDBMS file system and database instance, run the following command to create the $ORACLE_HOME/nls/data/9idata directory.

$ perl $ORACLE_HOME/nls/data/old/cr9idata.pl

export ORACLE_HOME=/d01/oracle/PROD/db/tech_st/12c
export ORACLE_SID=PROD
export PATH=$ORACLE_HOME/bin:$PATH
export ORA_NLS10=/d01/oracle/PROD/db/tech_st/12c/nls/data/9idata
export PATH=$ORACLE_HOME/OPatch:$PATH

Step4:
Apply additional 12.1.0.2 RDBMS patches
Apply the following patches:
For all UNIX/Linux platforms:
Patch 19382851

Step5: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.

Step6: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;

Step6:
Remove the MGDSYS schema (conditional)

If you are upgrading from an RDBMS version prior to 12c, on the old database server node, use SQL*Plus to connect to the database as SYSDBA and run the $ORACLE_HOME/md/admin/catnomgdidcode.sql script. This drops the MGDSYS schema.
$ sqlplus “/ as sysdba” @?/md/admin/catnomgdidcode.sql

Step7:Prepare to upgrade

36C416DE-3E09-4430-9F5A-A5B153EC5135

Step8:
2

Step9:run dbua
3

1

2

3

Run FIX and Check Again…If there are any errors…….
4

5

6

7

8

9

10

11

12

13

Step10:
Compile the Invalids
14

Step11:
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]

1

2

3

Step12:
4

5

Step13:
6

7

Step14:
8

Step15:De-register Database and Implement Autconfig
9

Step16:
12

13

14

15

Run Autoconfig on the application side as well…..

Start the application tier services…..

16

17

This finishes the R12 EBS Database 11.2.0.2 to 12.1.0.2

Advertisements

Posted October 8, 2014 by balaoracledba.com in OracleAppsR12, Upgrade

R12.1.1 to R12.1.3 Upgrade.   Leave a comment

In this post i am going to list out the steps to upgrade R12.1.1 to R12.1.3

NOTE: Please make a note that i have not included pre and post patch steps while applying patches. Please go-through the patch README’s carefully while applying patches…….

Step1: 

Upgrade Database from 11.1.0.7 to 11gr2. I have upgraded from 11.1.0.7 to 11.2.0.2. 

Please follow below URL for Database upgrade for R12.1.1 EBS
https://balaoracledba.com/2013/11/13/upgrade-11-1-0-7-to-11-2-0-2-on-r12-1-1/
Step2:

Put the application under maintainence using adadmin 

Step3. 

Apply below patch
8919491.B                  Oracle Applications Technology 12.1.3 Product Family Release Update Pack

Step4

Apply Below Patch
17884289 R12.AD.B.Delta.4

Step5:

Apply Below Patch

9239090              R12                    ORACLE E-BUSINESS SUITE 12.1.3 RELEASE UPDATE PACK


Step6:

Apply Below Patch
9239095.                      R12Oracle E-Business Suite Online Help for 12.1.3 Release Update Pack


Step7:

Apply Below Patch

9817770.BPOST-R12.ATG_PF.B.DELTA.3 CONSOLIDATED PATCH

Step8: 

Apply Below patch

9966055.B1OFF:12.1.3:TRANSLATED VERSION OF FNDSCSGN NOT LAUNCHED

Step9:  

Run AutoConfig on the APPL_TOP.

Step10:

Run the admkappsutil.pl utility to create the file appsutil.zip in the <INST_TOP>/admin/out directory.Step9:

Run AutoConfig on the APPL_TOP.
perl <AD_TOP>/bin/admkappsutil.pl

Step11:

Copy or FTP the appsutil.zip file to the <RDBMS ORACLE_HOME>.

Step12:

Uncompress appsutil.zip under the <RDBMS ORACLE_HOME>.

Step13:

unzip the appsutil.zip  as below

unzip -o appsutil.zip

Step14: 

Run AutoConfig on the <RDBMS ORACLE_HOME>.

Step15:

Re-run adpreclone.pl on the database tier and the application tier. Since updates included in Oracle E-Business 
Suite Release 12.1.3 were applied to the system, adpreclone must be run again to apply the updates 
to the clone directory structures that were used during cloning.

perl adpreclone.pl dbTier
perl adpreclone.pl appsTier
This finishes the Application upgrade.
Start the Application Tier Services.
NOTE:After finishing the application upgrade. we need to apply product family patches.
(IN THIS UPGRADE I DIDNT APPLIED BELOW PRODUCT SPECIFIC PATCHES)
Patch Product Family Product Family Readme Documents
Oracle Applications Technology Release 12.1.3 (R12.ATG_PF.B.DELTA.3) Patch 8919491 Applications Technology (ATG_PF) Document 1066312.1
Oracle Customer Releationship Management Release 12.1.3 (R12.CC_PF.B.DELTA.3) Patch 9249345 Customer Relationship Management (CC_PF) Document 1081433.1
Oracle Financials Release 12.1.3 (R12.FIN_PF.B.DELTA.3) Patch 9147733 Financials (FIN_PF) Document 1081425.1
Oracle Human Resource Management System Release 12.1.3 (R12.HR_PF.B.DELTA.3) Patch 9114911 Human Resources (HR_PF) Document 1081427.1
Oracle E-Business Suite Diagnostics Release 12.1.3 (R12.IZU.B.DELTA.3) Patch 9239092 E-Business Suite Diagnostics (IZU) Document 1081428.1
Oracle Procurement Release 12.1.3  (R12.PRC_PF.B.DELTA.3) Patch 9249354 Procurement (PRC_PF) Document 1081431.1
Oracle Projects Release12.1.3 (R12.PJ_PF.B.DELTA.3) Patch 9147711 Projects (PJ_PF) Document 1081434.1
Oracle Supply Chain Management Release 12.1.3 (R12.SCM_PF.B.DELTA.3) Patch 9245674 Supply Chain Management (SCM_PF) Document 1081459.1
Oracle Value Chain Planning Release 12.1.3 (R12.SCP_PF.B.DELTA.3) Patch 9245525 Oracle Value Chain Planning (SCP_PF) Document 1081461.1

	

Posted May 7, 2014 by balaoracledba.com in 11i/R12, OracleAppsR12, Upgrade

ORA-01408 such column list already indexed 11.2.0.2 to 11.2.0.4 Upgrade error   Leave a comment

During the Upgrade from 11.2.0.2 to 11.2.0.4 on OEL5.5 64-bit for EBS R12.1.3 I faced below issue

upgrade_error

 

Solution:

Ora-01408 Error Upgrading to 11g using Dbua (and manual upgrade) (Doc ID 737400.1)

1. Remove the offending index:

drop index system.REPCAT$_AUDIT_COLUMN_IDX1;

2.

2.1 -If the upgrade has finished without any other error, create the following index:

create index system.repcat$_audit_column_f2_idx
on system.repcat$_audit_column
(base_sname,base_oname,base_conflict_type_id, base_reference_name);

2.2.- If the upgrade was cancelled or more errors were reported, retry the upgrade manually (see Note 429825.1) :

$ cd $ORACLE_HOME/rdbms/admin
$ sqlplus “/ as sysdba”
SQL> startup UPGRADE
SQL> set echo on
SQL> SPOOL upgrade.log
SQL> @catupgrd.sql
SQL> spool off

Posted March 25, 2014 by balaoracledba.com in Upgrade

Upgrade 11.1.0.7 to 11.2.0.2 on R12.1.1   7 comments

Following are the steps to upgrade 11.1.0.7 to 11.2.0.2 on R12.1.1

About Oracle Database Release Numbers

Oracle Database Upgrade Guide describes moving between different releases of Oracle Database. Starting with Oracle9i Release 2 (9.2), maintenance releases of Oracle Database are denoted by a change to the second digit of a release number. In earlier releases, the third digit indicated a particular maintenance release.

Figure 1–2 illustrates each part of a release number and what it represents.

1

Presently the database version is 11.1.0.72

 

The Upgrade process is divided into pre-upgrade, Upgrade and Post Upgrade.

1.Pre-Upgrade

Step-1

Check for oratab entry in /etc/oratab

3

 

Install 11gR2(11.2.0.2) Software only in new location

Create new location

mkdir –p /u01/oracle/RACDB/db/tech_st/11.2.0

Parallely Run Gather Dictionary Stats

4 5

 

Once we finish above. Let’s start installing 11.2.0.2 Oracle Software in new location /u01/oracle/RACDB/tech_st/db/11.2.0/

*Note: Don’t set DB environment during the installation of 11.2.0.2 Software.*

Download

p10098816_112020_Linux-x86-64_1of7.zip
p10098816_112020_Linux-x86-64_2of7.zip

unzip both the files in same location

Install 11gR2 Pre-req patches using YUM

yum install oracle-rdbms-server-11gR2-preinstall
6

Execute runinstaller

7

 

8 9 10 11 12 13 14 15 16 17 18 19 20

Now go to /tmp/CVU_11.2.0.2

And execute ./runfixup.sh

21 22 23 24 25 26

 

Now take a count of Invalid Objects

SQL> select OWNER,OBJECT_NAME,OBJECT_TYPE from dba_objects where STATUS=’INVALID’;

 

27

I will execute utlrp.sql or below package to compile invalid objects

exec utl_recomp.recomp_parallel(10);

28

 

29

From the above Screenshot we are going to apply
  • 11g Release 2 interoperability patch for Release 12.1 (9062910)
  • 12.1 TXK Delta 3 patch (8919489)
  • 9868229
  • 10163753
  • 11071569

Put Application under Maintenance using adadmin and start applying the above patches

Apply patch 6400501 (conditional)

If you are on a UNIX/Linux platform, apply the 10.1.0.5 version of patch 6400501 to the iAS 10.1.2 Applications tier Oracle home.

Note: For Linux x86-64 environments, download the Linux 32-bit version of the patch as the Applications tier Oracle home is 32-bit.

 

Update application tier context file with new database listener port number (conditional)

The new 11.2.0 Oracle home uses its own database listener for the database instance, replacing the current database listener. Use the Context Editor to update the following variables in the Applications context file on each application tier server node to reflect the 11.2.0 configuration:

Variable Name Value
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

 

Database Installation:

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 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 4, “Download Oracle Database Examples” in the Oracle Database Examples CD 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])

ExamplesCD: p10098816_112020_Linux-x86-64_6of7.zip

Download and apply above examples CD on 11202 Database Software:

30 31 32 33 34

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])

 

export ORACLE_BASE=/u01/oracle/RACDB/

export ORACLE_HOME=/u01/oracle/RACDB/db/tech_st/11.2.0

export PATH=$ORACLE_HOME/bin:$PATH

export LD_LIBRARY_PATH=/u01/oracle/RACDB/db/tech_st/11.2.0/lib

 

Create nls/data/9idata directory

 

On 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.

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.

mkdir -p $ORACLE_HOME/nls/data/9idata

run the $ORACLE_HOME/nls/data/old/cr9idata.pl

[oracle@r12-rac1 ~]$ cd $ORACLE_HOME

[oracle@r12-rac1 11.2.0]$ cd nls/data/old/

[oracle@r12-rac1 old]$ perl cr9idata.pl

Directory /u01/oracle/RACDB/db/tech_st/11.2.0/nls/data/9idata already exist. Overwriting…

Copying files to /u01/oracle/RACDB/db/tech_st/11.2.0/nls/data/9idata…

Copy finished.

Please reset environment variable ORA_NLS10 to /u01/oracle/RACDB/db/tech_st/11.2.0/nls/data/9idata!

[oracle@r12-rac1 old]$ export ORA_NLS10=/u01/oracle/RACDB/db/tech_st/11.2.0/nls/data/9idata

35

Apply additional 11.2.0.2 RDBMS patches

Apply the following patches:

For all UNIX/Linux platforms:

4247037

10149223

10160615

10229719

12400751

12942119

13001379

13004894

Run utlu112i.sql on existing 11.1.0.7 oracle database

11.1.0.7—/u01/oracle/RACDB/db/tech_st/11.1.0

11.2.0.2—/u01/oracle/RACDB/db/tech_st/11.2.0

Copy utlu112i.sql from 11.2.0 Orace Home

cd /u01/oracle/RACDB/db/tech_st/11.2.0/rdbms/admin

cp utlu112i.sql $HOME

SQL> @utlu112i.sql
Oracle Database 11.2 Pre-Upgrade Information Tool 11-12-2013 21:14:59
Script Version: 11.2.0.2.0 Build: 001
.
**********************************************************************
Database:
**********************************************************************
--> name: RACDB
--> version: 11.1.0.7.0
--> compatible: 11.1.0
--> blocksize: 8192
--> platform: Linux x86 64-bit
--> timezone file: V10
.
**********************************************************************
Tablespaces: [make adjustments in the current environment]
**********************************************************************
--> SYSTEM tablespace is adequate for the upgrade.
.... minimum required size: 11003 MB
--> CTXD tablespace is adequate for the upgrade.
.... minimum required size: 16 MB
--> ODM tablespace is adequate for the upgrade.
.... minimum required size: 10 MB
--> APPS_UNDOTS1 tablespace is adequate for the upgrade.
.... minimum required size: 853 MB
--> APPS_TS_TX_DATA tablespace is adequate for the upgrade.
.... minimum required size: 5254 MB
--> APPS_TS_QUEUES tablespace is adequate for the upgrade.
.... minimum required size: 79 MB
WARNING: --> SYSAUX tablespace is not large enough for the upgrade.
.... currently allocated size: 446 MB
.... minimum required size: 506 MB
.... increase current size by: 60 MB
.... tablespace is NOT AUTOEXTEND ENABLED.
.
**********************************************************************
Flashback: OFF
**********************************************************************
**********************************************************************
Update Parameters: [Update Oracle Database 11.2 init.ora or spfile]
Note: Pre-upgrade tool was run on a lower version 64-bit database.
**********************************************************************
--> If Target Oracle is 32-Bit, refer here for Update Parameters:
-- No update parameter changes are required.
.
--> If Target Oracle is 64-Bit, refer here for Update Parameters:
-- No update parameter changes are required.
.
**********************************************************************
Renamed Parameters: [Update Oracle Database 11.2 init.ora or spfile]
**********************************************************************
-- No renamed parameters found. No changes are required.
.
**********************************************************************
Obsolete/Deprecated Parameters: [Update Oracle Database 11.2 init.ora or spfile]
**********************************************************************
--> plsql_native_library_dir 11.2 OBSOLETE
--> plsql_native_library_subdir_ 11.2 OBSOLETE
.
**********************************************************************
Components: [The following database components will be upgraded or installed]
**********************************************************************
--> Oracle Catalog Views [upgrade] VALID
--> Oracle Packages and Types [upgrade] VALID
--> JServer JAVA Virtual Machine [upgrade] VALID
--> Oracle XDK for Java [upgrade] VALID
--> Real Application Clusters [upgrade] INVALID
--> OLAP Analytic Workspace [upgrade] VALID
--> OLAP Catalog [upgrade] VALID
--> Oracle Text [upgrade] VALID
--> Oracle XML Database [upgrade] VALID
--> Oracle Java Packages [upgrade] VALID
--> Oracle interMedia [upgrade] VALID
--> Spatial [upgrade] VALID
--> Data Mining [upgrade] VALID
--> Oracle OLAP API [upgrade] VALID
.
**********************************************************************
Miscellaneous Warnings
**********************************************************************
WARNING: --> Database is using a timezone file older than version 14.
.... After the release migration, it is recommended that DBMS_DST package
.... be used to upgrade the 11.1.0.7.0 database timezone version
.... to the latest version which comes with the new release.
WARNING: --> Your recycle bin contains 1724 object(s).
.... It is REQUIRED that the recycle bin is empty prior to upgrading
.... your database. The command:
 PURGE DBA_RECYCLEBIN
.... must be executed immediately prior to executing your upgrade.
WARNING: --> Database contains schemas with objects dependent on DBMS_LDAP package.
.... Refer to the 11g Upgrade Guide for instructions to configure Network ACLs.
.... USER APPS has dependent objects.
.
**********************************************************************
Recommendations
**********************************************************************
Oracle recommends gathering dictionary statistics prior to
upgrading the database.
To gather dictionary statistics execute the following command
while connected as SYSDBA:
EXECUTE dbms_stats.gather_dictionary_stats;
**********************************************************************
Oracle recommends removing all hidden parameters prior to upgrading.
To view existing hidden parameters execute the following command
while connected AS SYSDBA:
SELECT name,description from SYS.V$PARAMETER WHERE name LIKE '\_%' ESCAPE '\'
Changes will need to be made in the init.ora or spfile.
**********************************************************************
Oracle recommends reviewing any defined events prior to upgrading.
To view existing non-default events execute the following commands
while connected AS SYSDBA:
 Events:
 SELECT (translate(value,chr(13)||chr(10),' ')) FROM sys.v$parameter2
 WHERE UPPER(name) ='EVENT' AND isdefault='FALSE'
Trace Events:
 SELECT (translate(value,chr(13)||chr(10),' ')) from sys.v$parameter2 WHERE UPPER(name) = '_TRACE_EVENTS' AND isdefault='FALSE'
Changes will need to be made in the init.ora or spfile.
**********************************************************************
The DMSYS schema exists in the database. Prior to performing an
upgrade Oracle recommends that the DMSYS schema, and its associated
objects be removed from the database.
Refer to the Oracle Data Mining Administration Guide for the
instructions on how to perform this task.
**********************************************************************

1

WARNING: –> SYSAUX tablespace is not large enough for the upgrade.

…. currently allocated size: 446 MB

…. minimum required size: 506 MB

…. increase current size by: 60 MB

…. tablespace is NOT AUTOEXTEND ENABLED.

1

SOLUTION:
 ALTER DATABASE DATAFILE'/u01/oracle/RACDB/db/apps_st/data/sysaux02.dbf' RESIZE 1G;
2 Comment the below parameters in init.ora file
 --> plsql_native_library_dir     11.2       OBSOLETE
--> plsql_native_library_subdir_ 11.2       OBSOLETE
36

3

WARNING: –> Your recycle bin contains 1724 object(s).

…. It is REQUIRED that the recycle bin is empty prior to upgrading

…. your database.  The command:

PURGE DBA_RECYCLEBIN

SOLUTION:

37

 

Find and Comment all hidden parameters prior to upgrading.

SELECT name,description from SYS.V$PARAMETER WHERE name LIKE ‘\_%’ ESCAPE ‘\’

 

 

 

38 39 40

 

2.Upgrade
Shutdown the 11.1.0.7 DATABASE open a new terminal

Set the new environment
export ORACLE_BASE=/u01/oracle/RACDB/
export ORACLE_HOME=/u01/oracle/RACDB/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/RACDB/db/tech_st/11.2.0/nls/data/9idata

run dbua

42 43 44 45 46 47 48 49 50
Simultaneously Check for count of invalids, it will be reducing.
51

52
So we are done with the upgrade.

53
POST Upgrade

1.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:

  1. $ 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.

In this case i have copied the adgrants.sql in /tmp

54

 

2.Re-create grants and synonyms using adadmin and then compile apps schema this will help us in reducing the no.of invalids.

After Upgrade the no.of invalids

55

 

After running recreate grants and synonyms and compile apps schema the invalid count is

56

This is really good as we dont have any invalids before or after Upgrade. Even if there are any invalids it should be same when compared to before upgrade. If we get any invalids then we should raise an SR and work on it.

3.When we applied 11.2.0.2 additional patches there were some post patch steps, that has to be taken care.

a)  4247037

Post install steps:

cd $ORACLE_HOME/md/admin

connect to the database using sqlplus / as sysdba

sqlplus> @catmgdidcode

b) 9858539

Post install steps:

Run following files as sysdba

cd $ORACLE_HOME/rdbms/admin

@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’;

5.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

6.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’);

7.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;

  1. 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.

On the applciation side run admkappsutil.pl to generate admkappsutil.zip file

copy this admkappsutil.zip to new 11.2.0.2 Oracle Home and unzip then run autoconfig this makes our new oracle home autoconfig enabled.

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.
  1. 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.

  1. 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;

11.  Restart Applications server processes

Remove the Maintenance mode and 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.

57

 

 

Now check the DB version from frontend…..

58 59

We are able to successfully upgrade the database from 11.1.0.7 to 11.2.0.2

 

 

Posted November 13, 2013 by balaoracledba.com in OracleAppsR12, Upgrade