SMP Oracle Upgrade From 11g To 12c

SMP Oracle Upgrade from 11g to 12c
Document Information:
Project Name: Denbury Resources

Team: SAP Infrastructure Services
Document ID: SMP Oracle Upgrade from 11g to 12c
Status of the document
Status Name / Created Validated Version

Narendar Nagabelli
Page 1
Page 2
Page 3
Checking the Original Version of Your Database

To upgrade directly to Oracle Database Release 12c, your source release must be Oracle
Database 10g Release 2 (10.2.0.5) or Oracle Database 11g Release 2 (11.2.0.2, 11.2.0.3, or
11.2.0.4).
To check the original version of your database, enter these commands from the environment of
the source database as the appropriate database user
SQL> select version from v$instance;
Page 4
Extracting Oracle Software

Software downloaded to “/sapbackup1/SOFTWARES/ORACLE12C/CD/51047705”
To upgrade a single instance database on the file system, we only need to extract the database
software that is contained in the 2 SAR files “OR112164.SAR” and “OR212164.SAR”.
Note : I already did this in GRS and copied the required software to
/sapbackup1/SOFTWARES/ORACLE12C/ 12cSTAGE, so this step is not required in any
system, just copy this software to /oracle/stage directory.
3.4Process Flow for Software Installation

1.Back up the central Oracle inventory
2.Update the SAP RUNINSTALLER installation scripts
3.Check the software installation prerequisites
4.Install the new Oracle database 12c software
5.Install the current SAP bundle patch
Page 5
3.4.1Backing Up the Central Oracle Inventory

Make a backup of your existing Oracle inventory before we start the Oracle Database 12c
software installation
3.4.2Updating the SAP RUNINSTALLER Scripts

The SAP-specific installation scripts RUNINSTALLER and 12cinstall.sh are located in directory
SAP in the Oracle database software stage (that is, /oracle/stage/12102/database/SAP).
We need to check the patch level of the RUNINSTALLER and check in SAP Note 1915301
whether a higher version is available. If a higher version is available, we recommend that you
update the Oracle installation scripts, which are attached to SAP Note 1915301. After we have
extracted the Oracle software to the staging area, we need to update the installation scripts.
Check RUNINSTALLER version with the below command . downloaded higher patch level (59) from
SAP Note 1915301.
Page 6
3.4.3Checking the Software Installation Prerequisites

Set Display variables
Command : setenv DISPLAY capflwddev:1.0
Page 7
Page 8
Page 9
Login as root and go to /oracle/stage/12102/database and execute rootpre.sh script
Page 10
Now open previous session and enter “y” to proceed
Page 11
Page 12
Page 13
Page 14
Page 15
Click on close button
Completed successfully.
Check log “/oracle/SMP/12cinstall_12102.log” and make sure we don’t have any errors in that.
Page 16
Page 17
Page 18
Page 19
No Errors found in log.
3.4.4Installing the New Oracle Database 12c Software

Procedure
1.Log on as the Oracle database software owner (orasmp)
2.Change to the stage directory:cd /oracle/stage/12102/database/SAP
3.Make sure that the DISPLAY (for dialog mode) and DB_SID variables are set in the
environment.
4.Start the OUI with the Oracle database software owner, user orasmp, as
follows:./RUNINSTALLER
Page 20
Page 21
Page 22
Login as root, change directory to /oracle/stage/12102/database and run “rootpre.sh” script
Now go back to the RUNINSTALLER screen and enter “y” to continue.
Page 23
It will ask the E-mail ID to register to send oracle updates but leave it empty and click on Next
Page 24
Click Yes
Page 25
Select Install database software only and click Next
Page 26
Select Single instance database installation and click Next
Page 27
Click Next
Page 28
Select Enterprise Edition and click Next
Page 29
Click Next
Page 30
Page 31
Click Yes to continue
Page 32
Click Next to continue
Page 33
Page 34
Page 35
IV42025: CHOWN -R FAILS WITH EOVERFLOW ERROR APPLIES TO AIX 7100-00

IV41380: CHOWN -R FAILS WITH EOVERFLOW ERROR APPLIES TO AIX 7100-01
IV42024: CHMOD -R FAILS WITH EOVERFLOW ERROR APPLIES TO AIX 7100-00
IV37790: CHMOD -R FAILS WITH EOVERFLOW ERROR APPLIES TO AIX 7100-01
All the above OS patches for old AIX release, we are on AIX TL 7100-03, so we can ignore
these warnings.
Select ignore all and click next
Page 36
Click next
Page 37
Click on YES to continue
Page 38
Click Install to start installation.
Page 39
Page 40
Page 41
Login as root and go to /oracle/SMP/12102 and execute root.sh script
Page 42
Go to previous session and click ok
Page 43
Click on ok
Oracle 12c installation completed successfully.
3.4.5Installing the Current SAP Bundle Patch

After the installation of the Oracle Database patch set, we need to install the current (or latest)
Page 44
SAP bundle patch (SBP) into the new Oracle home.

The SBP also delivers a set of upgrade scripts that automate most of the pre-upgrade and postupgrade
tasks.
Set the below environment variables
setenv ORACLE_HOME /oracle/SMP/12102
setenv OHRDBMS /oracle/SMP/121
setenv IHRDBMS /oracle/SMP/12102
setenv LIBPATH
/usr/sap/SMP/SYS/exe/run:/usr/sap/SMP/SYS/exe/uc/rs6000_64:/oracle/SMP/12102/lib
setenv PATH
/oracle/SMP/12102/bin:/usr/bin:/etc:/usr/sbin:/usr/ucb
Page 45
SAP Bundle Patch 12.1.0.2.160119 – 201602 is the latest SBP which is released on
2016/02/23.
Downloaded this patch to “/sapbackup/SOFTWARES/ORACLE12C/SBP”
Go to new Oracle home (/oracle/SMP/12102) and rename existing Opatch
Page 46
Copy OPatch and MOPatch directories to /oracle/SMP/12102
Page 47
Make sure that icop0 changed to Available from Defined before executing mopatch otherwise
you will get error “RDBMS version not found”
lsdev |grep iocp command output should be ‘Available’
Command: ./mopatch.sh –v –s
/sapbackup/SOFTWARES/ORACLE12C/SBP/SAP12102P_1602-20012297.ZIP
Page 48
Page 49
Page 50
Page 51
Page 52
Page 53
MOPatch applied successfully.

Check bundle patch version as shown in the below screen.
Page 54
3.5Running the Pre-Upgrade Scripts

1.Log on as the Oracle database administrator orasmp.
2.Change to the correct directory by entering the relevant command:
cd /oracle/SMP/12102/sap/ora_upgrade/pre_upgrade
3.Execute the following commands to perform pre-upgrade tasks, which can improve the
performance of the upgrade process:
sqlplus / as sysdba
SQL> @pre_upgrade_tasks.sql
4.Execute the following commands to check the pre-upgrade status of your database
sqlplus / as sysdba
SQL> @pre_upgrade_checks.sql
Page 55
Please open new session to run below scripts
Page 56
Page 57
Page 58
Page 59
Make sure that we didn’t get any error during Pre-upgrade task.
Execute the following commands to check the pre-upgrade status of your database
Page 60
sqlplus / as sysdba
SQL> @pre_upgrade_checks.sql
Page 61
Page 62
Page 63
Page 64
Page 65
Page 66
We didn’t get any error during Pre-upgrade checks also.

Page 67
Check the logs.
Page 68
Page 69
Page 70
More /oracle/cfgtoollogs/SMP/preupgrade/preupgrade_fixups.sql
Page 71
Page 72
Page 73
/oracle/cfgtoollogs/SMP/preupgrade/postupgrade_fixups.sql
Page 74
Page 75
No issues found in logs also, so we can Upgrade Oracle 11g Database to 12c.
4Oracle Database Upgrade

1.Back up the Oracle database
2.Shut down the SAP system
3.Upgrade the database structure
If you have problems during the upgrade, see SAP Note 2086029.
4.1Backing Up the Oracle Database
We must have a complete and usable database backup otherwise you might lose data if the
upgrade fails.
Page 76
We already took offline snap backup before starting this activity, so we are good on this.
4.2Shutting Down the SAP System
We need to shut down the SAP system.

Stop the SAP application instances by entering the following command as user
<sapsid>adm:stopsap r3
Also stop the SAP application server with the sapcontrol tool:sapcontrol -nr
<SAP_instance_number> -function Stop Note
Make sure that processes that log on to the database, such as CRON jobs, are not active during
the upgrade. Make sure that you reschedule these processes when the upgrade has finished.
4.3Upgrading the Database Structure with the Database Upgrade Assistant
To upgrade the database structure, you need to start the Oracle Database Upgrade Assistant
(DBUA). The DBUA is a graphical tool that leads you step-by-step through the upgrade.
Prerequisites
1. We should have installed the database software.
2.Make sure that the DISPLAY environment variable is correctly set, as described in Checking
and Setting the DISPLAY Environment Variable
3. Make sure that the database and the Oracle Listener are both running.
Procedure
1.Log on as Oracle software owner (oragrs)
2. Make sure that oratab contains the entry <DBSID>:<Oracle_home>:N
Page 77
Page 78
2.Make a backup of directory <Oracle_home>/network/admin as follows:
To run the upgrade with this script, you have to set the environment variables
ORACLE_HOME_SRC and ORACLE_HOME_TGT, DB_SID, and ORACLE_BASE:
setenv ORACLE_HOME_SRC /oracle/SMP/11204
setenv ORACLE_HOME_TGT /oracle/SMP/12102
setenv DB_SID SMP
setenv ORACLE_BASE /oracle/SMP
Page 79
Page 80
2.Change to the correct directory:cd $ORACLE_HOME_TGT/sap/ora_upgrade/post_upgrade
Page 81
3.Run this script in query mode initially to verify that the environment for the upgrade is
correct:./dbua.sap.sh –q
Page 82
Page 83
Page 84
Page 85
4. Run this script as follows to perform the upgrade:

For interactive mode, enter the following command:./dbua.sap.sh
Page 86
Page 87
Click on next
Page 88
Page 89
DB state shown as down even though DB is up and running.

Solution : As per the below wiki, I re-created entry in oratab and set ORACLE_HOME env same
as per oratab.
Page 90
Page 91
setenv ORACLE_HOME_SRC /oracle/SMP/11204
setenv ORACLE_HOME_TGT /oracle/SMP/12102
setenv DB_SID SMP
setenv ORACLE_BASE /oracle/SMP
setenv ORACLE_HOME /oracle/SMP/11204
Page 92
Page 93
Page 94
Page 95
Page 96
Page 97
Page 98
Page 99
Page 100
Click Next
Page 101
Page 102
We already took Offline snap backup, so select as above and click Next
Page 103
Click Finish to start Upgrade.
Page 104
This can be safely ignored.
Page 105
Click on Upgrade results to check logs
Page 106
Page 107
Click Close to close dbua.
Page 108
5Post-Upgrade Steps
5.1Updating oratab
After the database upgrade, change the entry <DBSID>:/oracle/<DBSID>/12102:N in /etc/oratab
Page 109
5.2Updating the SQL*Net Configuration Files

Copy sqlnet.ora, tnsnames.ora from /oracle/SMP/12102/network/admin to
/usr/sap/SMP/SYS/profile/oracle
Page 110
5.3Checking the Symbolic Link for Runtime Oracle Home

For upgrades from 11.2 to 12.1.0.2, the symbolic link /oracle/<DBSID>/121 has already been
created by RUNINSTALLER.
Check that the following symbolic link exists:ls -l /oracle/<DBSID>/121
Soft link already exists, so no need to create again.
5.4Adapting the Environment of the <sapsid>adm user

We have to change the environment of user <sapsid>adm for SAP application servers that are
installed on the Oracle database server. We need to make sure that the changes we made to
the Oracle user environment are permanently stored in the profiles .cshrc,
.dbenv_hostname.csh and .dbenv.csh.
Take backup of .dbenv_hostname.csh and .dbenv.csh files before making any changes.
Page 111
Page 112
Page 113
Change environment vaiables for <SID>adm user also. Make sure to take backup of old files
before changing anything.
Page 114
5.5Performing SAP Bundle Patch Post-Installation Steps

We have installed an SAP bundle patch (SBP) before we upgrade to the new Oracle Release.
Now we need to run the SBP post-installation steps.
Run the SBP post-installation instructions as described in the corresponding SBP README.
Take backup of pfile and initGRS.sap files before starting post bundle patch activities
Page 115
Page 116
Page 117
ALTER VIEW S$KEWMRMGMV COMPILE;
Page 118
SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
ALTER SYNONYM X$DNFS_CHANNELS COMPILE;
As per SAP suggestion, implemented SAP notes 2199300 and 706927 and issue fixed.
Page 119
Page 120
After setting parameters restart Database.
Validation
set linesize 100

set pagesize 999
col version format A30
col patch format A15
col description format A50
select version || ' ' || id "Version", bundle_series "Patch", comments "Description" from
Page 121
dba_registry_history order by action_time desc ;
Check logs $ORACLE_HOME/OPatch/opatch lsinventory -all | more
Page 122
Page 123
Page 124
Page 125
Page 126
Page 127
Page 128
Page 129
5.6Performing Post-Upgrade Checks

Log on as the Oracle database administrator (orasmp) and change to the directory
/oracle/SMP/12102/sap/ora_upgrade/post_ugprade. From the same directory, start sqlplus.exe and enter
the
following commands to run the post-upgrade scripts, please check SAP Note 1915315 for more details.
sqlplus / as sysdba
SQL> @?\rdbms\admin\utlu121s.sql
SQL> @post_upgrade_tasks.sql (if you have not already executed this with DBUA)
Page 130
SQL> @post_upgrade_checks.sql
This provides an overview of the status of the upgraded database.
Run the script from rdbms/admin
Page 131
Page 132
Page 133
Oracle Database 12.1 Post-Upgrade Invalid Objects Tool

Purpose: list invalid objects that were not invalid prior to upgrade
@?/rdbms/admin/utluiobj.sql
Page 134
Page 135
Page 136
Page 137
5.7Run SAP specific post-upgrade scripts

Recompile invalid objects
SQL> @?/rdbms/admin/utlrp.sql
Page 138
Page 139
Page 140
Page 141
Page 142
Page 143
Page 144
Page 145
Page 146
Page 147
Page 148
5.8Run post-upgrade checks

cd /oracle/SMP/12102/sap/ora_upgrade/post_upgrade
SQL> @post_upgrade_tasks.sql (if you have not already executed this with DBUA)
Page 149
Page 150
Page 151
Page 152
Page 153
Page 154
Page 155
Page 156
Recompile invalid objects

SQL> @?/rdbms/admin/utlrp.sql
Run post-upgrade checks
Page 157
Page 158
Page 159
Page 160
Page 161
5.9Updating the Oracle Instant Client
Installation of Oracle 12c Client
Create a directory 12x in /oracle/client with adm:sapsys authorizations
Page 162
Extract Oracle12 client to new 12x directory as below
Page 163
Create soft link with the below command ln -s instantclient_12102 instantclient
Rename old client directories
We need to update new client in adm user’s environment variables
Page 164
Take backup of “.dbenv.sh” before making any changes
Page 165
Page 166
After change logout and re login check the same.
Page 167
Ensure that parameter 'compatible' is set to '12.1.0.2.0' or '12.1.0.2':
SQL> show parameter compatible
SQL> select value "compatible" from v$parameter where name = 'compatible';
If compatible has a lower value, you have to run 'set_compatible.sql' as described above.
Page 168
5.10Starting the SAP System Log on as adm, SAP installations with an ABAP application server, enter
this command to check whether R3trans can connect to the database:
R3trans -d
So Database connection is successful, now start SAP with startsap command.
Page 169
Check Oracle version
Page 170
Check alert log if we have any errors
Page 171
Page 172
Page 173
Page 174
We are facing issue like Java system is unable to run using new oracle client (12x)
1777021 - J2EE: Introducing Support for Oracle 12
Changing the Location of the JDBC Driver
Page 175
If we have an SAP system with Java components, we might have to change the location of the JDBC
driver after we have upgraded the database server or client software. Otherwise the J2EE Engine cannot
start because the location of the JDBC driver might still point to the path of the old Oracle server or client
software home.
For more information, please refer oracle upgrade guide page# 42.
1)
For dual stack system:
From SMPadm user goto /usr/sap/SMP/DVEBMGS21/j2ee/configtool
Edit the file config.properties and change the entry of rdbms.driverLocation from
/oracle/client/11x_64/instantclient/ojdbc14.jar to /oracle/client/12x/instantclient/ojdbc14.jar
And save the file.
For single stack systems, edit the config.properties file from

/usr/sap/SMP/JC<instance_number>/j2ee/configtool directory.
2)
Page 176
In the same directory as in the first step, start the J2EE Engine - ConfigTool by double-clicking the
configtool.sh file. Change to Configuration Editor mode.
Use the Edit mode to replace the driver location in the following property sheets that contain the string
rdbms.driverLocation= followed by the driver location:
cluster_data/Propertysheet instance.properties.IDXXXXXXX/IDXXXXXXX.JavaParameters
where XXXXXXX is the instance number
NOTE
Make sure that you change all occurrences. There might be several IDXXXXXX.JavaParameters
properties in the property sheet.
cluster_data/dispatcher/IDXXXX/kernel/propertysheet ConfigurationManager
cluster_data/server/IDXXXX/kernel/propertysheet ConfigurationManager
where XXXX is the instance number
NOTE
If you have more than one server or dispatcher you must modify all relevant property sheets.
Page 177
Page 178
Page 179
Page 180
Right click on highlighted and select change mode
But no rdbms.driverLocation found under ID217589600.JavaParameters
Page 181
Page 182
Please follow as per below steps.
Page 183
Page 184
Close the J2ee engine – config tool.
Page 185
3)
Page 186
Page 187
Page 188
***
Page 189

SMP Oracle Upgrade From 11g To 12c

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SMP Oracle Upgrade From 11g To 12c

Uploaded by

Copyright:

Available Formats

SMP Oracle Upgrade from 11g to 12c

Project Name: Denbury Resources

Status of the document

Status Name / Created Validated Version