Oracle 11g Guide
ORACLE UPGRADE STEPS FROM 11g TO 12c FOR SAP SYSTEMS ON LINUX – PART I Document creation dat e: 10th OCT 2015 09:30 AM INDIA Document Part: 1st Document Author: Gaurav Rana Referred SAP Guide: Database Upgrade Guide to Oracle database 12c Release 1 (12.1.0.2 ) UNIX Referred SAP NOTES: 1. NOTE: 1914631 – Starting point for info about oracle 12c. NOTE: 1915317-Migrating Software owner to ‘oracle’ 3. NOTE: 1915323 – OS User Concept for database release 12c. STEPS TO FOLLOW: PREREQUISITES a) Source release must be Oracle DB 10.2.0.5,11.2.0.2,11.2.0.3 or 11.2.0.4 (Check your database version with command, SQLselect version from v$instance;) b) Only 12.1.0.2 release 1 is supported for SAP platforms instead of 12.1.0.1. C) For SAP environments, Oracle Instant Client versions 11.2.0.4 and 12.1.0.2 are supported.
RESTRICTIONS a) In order to run the SAP system with Oracle Instant Client version 12.1.0.2,you’ll have to apply the SAP support packages from SAP Note 1777021. B) SAP Kernel release must be = 7.21 EXT.
C) SAP BR.Tools minimum version for 12.1: BR.Tools 7.40 Patch Level 14. D) Mandatory to apply the appropriate SAP Support package according to SAP Note 2157904. E) Must be applied before or immediately after a database upgrade to Oracle release 12c or after a new installation with Oracle release 12c.
F) Secure Storage on File System (SSFS) must be configured and enabled to run SAP with Oracle Database 12c. CHECKLIST BEFORE STARTING SAP SYSTEM OF UPGRADED SYSTEM a). Migration of oracle software owner from ora to ‘oracle’. Installation of database 12.1.0.2 with Patches.
Install the latest Oracle client (12.1.0.2) for the database 12.1.0.2. Update BR.Tools with version 7.40. SSFS database connection configurations (SAP Notes 1639578 & 1622837). PREPARATION a). Download the Oracle 12c software with patches from b). Download latest version of DBATOOLS (BR.Tools) which we need to be used after the upgrade.
Oracle 11g Installation Guide Linux
Set the display parameters:0.0 or use command xhost +. CHECKLIST STEPS IN DETAIL a) Migration of database user ora to ‘oracle’ user. For the step i recommends to refer SAP NOTE 1915317-Migrating Software owner to ‘oracle’ or can follow steps as below: 1.Shutdown the running SAP System & the database with use of command stopsap all or can stop the SAP System & Database individually along with listener with command lsnrctl stop.
Creation of oracle software owner account ‘oracle’ from the root account # groupadd oinstall # useradd -g oinstall -G dba,oper -c “Oracle Software Owner” -m -s “/bin/sh” oracle # passwd oracle # su – oracle -c “id;pwd” 3. Modification of SAP Admin account adm Add the adm account as OS group ‘oinstall’ (Required to run BR.TOOLS) # groupmod -A adm oinstall or execute # usermod -G sapsys,sapinst,dba,oper,oinstall adm 4. Modification of Database Admin account ‘ora Log on as ‘root’ and run the commands # mkdir -p /home/ora # chown orasbx:dba /home/ora # usermod -d /home/orasbx ora # usermod -g dba -G oper,oinstall ora From the root account: # cd /oracle/ # mv.profile.login.bashrc.cshrc.sap.dbenv.j2eenv. /home/ora # mv startdb stopdb /home/ora # chown -R ora:dba /home/ora Oracle Environment consistency Note: If Oracle env for set for user ‘oracle’ differs from the oracle env for user ADM then system will not connect to the database.
To check, logon with user account adm & oracle to verify variables ORACLEBASE,ORACLEHOME & ORACLESID which should be set identical. Ownership changes for data files & directories Permissions & ownerships can be changed with help of script ‘orasid2oracle.sh’ (Script is attached with SAP Note 1915317 named orasid2oracle.zip) On unzip the file, a directory will be created with name sapnote1915317, contains executable script orasid2oracle.sh. Parameters to be set before execution of the script: 1.Log on with root account #export SAPDATAHOME=/oracle/ #export ORACLEBASE=/oracle/ #export DBSID= 2. To test run #./orasid2oracle.sh -v 3. To perform changes #./orasid2oracle.sh -v -exec Ownership change of Oracle Home Under this step we’ll change the software owner of Oracle Home from ‘ora’ to ‘oracle’ and same can be achieved with the help of oracle cloning tool from SAP Note 1983457 (Recommended).
You can find the clone tool script named cloneoh-1.7-005.zip as an attachment with the SAP Note 1983457,& on extraction of the zip file a new directory will be created as sapnote1983457. From the directory we need to execute cloneassistant.sh. Steps to execute cloneassistant.sh Log on as ora & execute cloneassistant.sh script to generate the scripts.This script will ask some questions for further execution steps, For help sample answers can be find from the same SAP Note 1983457. To save generated scripts from cloneassistant.sh we can provide our own location on the system.
12.1.0.2.0 (059) 2015-06-0 So we can upgrade existing i.e from Patch level 058 up to 059 by following the SAP Note 1915301. Installation of a new SAP RUNINSTALLER version: 1. Download the latest RUNINSTALLER package from the SAP NOTE as 12cinstall-12102-059-complete-32.zip. Extract the zip file under /oracle/stage/12102/database/SAP. 3.After extraction a new directory with similar name of SAP will get created under /oracle/stage/12102/database/SAP/.You can replace the newly created SAP directory with old directory SAP.
Oracle 11g Guide
On re-checking the RUNINSTALLER version we’ll get the latest version i.e patch level 059. DATABASE SOFTWARE INSTALLATION PREREQUISITES Procedure: 1.Log on as Oracle database software owner ‘oracle’ 2.Set environment variable DBSID,ORACLESTAGE Execute the below commands in dialog mode Fix the above warning by executing the script runfixup.sh which is generated by selecting tab Fix & check again. Oracle 12c database Installation: Logon with new software owner ‘oracle’ to execute RUNINSTALLER.Before execution of RUNINSTALLER don’t forget to set two environment variables (DBSID,ORACLESTAGE). Provide relevant information as required by the software to proceed further. Execute the root.sh script from the location /oracle//12102 & click on OK to finish the installation of 12c database. INSTALLATION OF CURRENT SAP BUNDLE PATCH Download the latest available SAP latest Bundle patch (SAP12102P150.ZIP) from.
Refer README.html file from the software extraction to follow steps or follow steps as below: Download the latest patch available (SAP12102P150.ZIP) from the service marketplace & save it under directory /oracle/stage by changing permissions & ownerships from root user to new database software owner. Setting of environment variables IHRDBMS & OHRDBMS Before proceeding we need to set the parameters IHRDBMS & OHRDBMS for the env of user ‘oracle’ su – oracle env export IHRDBMS=/oracle//121 export OHRDBMS=/oracle//12102 INSTALLING THE SAP BUNDLE PATCH Before installation of SAP Bundle Patch need to follow the steps. Stop all database applications, in particular all SAP applications. Shut down the database instances, the listeners, and other processes running from the Oracle Home. Install the SAP Bundle Patch as follows: env ORACLEHOME=$IHRDBMS $IHRDBMS/MOPatch/mopatch.sh -v -s SAP12102P150.ZIP After successful installation we’ll be able to get screen as similar Start up the database instances, the listeners, and other processes running from the Oracle Home PRE-UPGRADE SCRIPT RUNNING Pre-steps before the upgrade: 1.Pre-Upgrade scripts always execute as the current Oracle DB admin ora/oracle.
XML, spatial data, and full-text search are also covered in this step-by-step tutorial. The book offers thorough coverage of SQL management and development and features full details on the newest business intelligence, reporting, and security features. Filled with new real-world examples and hands-on exercises, Microsoft SQL Server 2016: A Beginner's Guide, Sixth Edition, starts by explaining fundamental relational database system concepts. From there, you will learn how to write Transact-SQL statements, execute simple and complex database queries, handle system administration and security, and use the powerful analysis and BI tools. Ms sql a beginners guide.
2.Copy the listener.ora,tnsnames.ora & other from /oracle//11264/network/admin to /oracle//12102/network/admin 3.Edit listener.ora & change the ORACLEHOME with value /oracle//12102 4.Execute the pre upgrade script from location /oracle//12102/sap/oraupgrade/preupgrade Execute the script preupgradechecks.sql to check the status of your database. ORACLE DATABASE UPGRADE NOTE: Recommends to take a complete offline database backup to restore if upgrade fails. Steps to consider: 1.Stop the SAP system with stopsap r3 or sapcontrol –nr -function stop 2.Oracle software owner must have write permissions on oratab file. 3.ORATAB file would contain entry similar::N 4.Database & listener should be in running state. Procedure: 1.Log on with ‘oracle’ 2.Save the administration directory of existing DB(Old ORACLEHOME/network/admin) 3.Before starting DBUA environment variable must be set ORACLEHOMESRC,ORACLEHOMETGT,DBSID & ORACLEBASE 4.Change to the directory cd $ORACLEHOMETGT/sap/oraupgrade/postupgrade 5.Test the DBUA script to verify correct env variable for upgrade. 6.Run script./dbua.sap.sh to perform the upgrade in interactive mode.
Oracle 11g
Due to restrictions of uploading of images,i’ll publish the Part-2 as well as troubleshooting for the same document very soon and requests all experts/SCN Members to guide me or hand me to make this document more informative & helpful for others by denoting any misstep in it.Hope you guys will find it helpful for your future references of database upgrades from Oracle 11g to 12c. Part 2nd: Refer SCN document at Regards, Gaurav Rana. Hi Carsten, We are on SAPBASIS 740 SP4 and we don´t want to update to SAPBASIS 740 SP12.So we implemented the SAP Note 2157904. As you’re on SAPBASIS 740 SP4 support package level & implemented the note 2157904 to avoid the issue “Oracle 12c ORA-39726 compression ALTER TABLE” into the system as suggested under the note.From the same note the above issue can be avoided by upgrading SP level from SP4 to SP12 or Alternatively, if you use Oracle 12c and table compression, you must implement the corrections contained in this SAP Note. Is it really necessary to update before Oracle 12c Upgrade to SAPBASIS 740 SP12? No need,if you’ve already implemented the note 2157904 & not experiencing any issues related to the Regards, Gaurav.
Hi Gaurav, Extremely such a nice well explained document. Appreciate your work.