Now you can decide to use the standard Oracle user “oracle” or “ora<sid>”. We choose SAP Classic ora<sid>, then no migration user is needed.
Oracle 12.1 is only released and certified for Oracle client software version 126.96.36.199 or higher
SAP must be 7.00 and above.
Check OS kernel required.
Check Original Version (must be 10.2.0.5 or higher):
Checking Hardware and Software
yum install -y oracle-database-server-12cR2-preinstall.x86_64
Update BR*Tools (7.40 recommended)
Update Kernel (must be 7.21 EXT or above)
check PAM for what Kernel is possible you tu update.
Configuring Secure Storage in File System
require at least SAP kernel 7.20 patch 210 (non-Unicode)
Follow notes 1639578 and 1622837
After configured SSFS according to the notes. Testing with command “R3trans –d”:
Kernel 748 and higher requires compat-sap-c++:
Note: 2195019 - Linux: Using SAP kernel 748 and higher or SAPinst 749 and higher on RHEL 6, OL6 and SLES 11
mkdir -p /oracle/stage/12102
chmod 755 /oracle/stage/121022
./SAPCAR_LINUX.exe -xvf ORACLE_DATABASE/ORACLE_LINUX/VERSION_12102/51047708/OR112164.SAR /oracle/stage/12102/
./SAPCAR_LINUX.exe -xvf ORACLE_DATABASE/ORACLE_LINUX/VERSION_12102/51047708/OR212164.SAR /oracle/stage/12102/
./SAPCAR_LINUX.exe -xvf ORACLE_DATABASE/ORACLE_LINUX/VERSION_12102/51047708/OR312164.SAR /oracle/stage/12102/
Backup Oracle Inventory
Check local for OraInventory:
zip –r /oracle/oraInventory.zip /oracle/oraInventory
Download the latest RUNINSTALLER from note 1915301
Installing the Current SAP Bundle Patch Use
Check note 1915316, download Bundle Patch and install following README file.
/oracle/SLR/12102/bin/unzip -qd /oracle/SLR/12102/sapbundle SAP12102P_1702-20012300.zip 'SBP_12102170117_201702/MOPatch/*'
mv /oracle/SLR/12102/OPatch /oracle/SLR/12102/OPatch-pre-SBP_12102170117_201702
mv /oracle/SLR/12102/sapbundle/SBP_12102170117_201702/OPatch /oracle/SLR/12102/OPatch
test -d /oracle/SLR/12102/MOPatch && mv /oracle/SLR/12102/MOPatch /oracle/SLR/12102/MOPatch-pre-SBP_12102170117_201702
mv /oracle/SLR/12102/sapbundle/SBP_12102170117_201702/MOPatch /oracle/SLR/12102/MOPatch
Stop SAP, Instance DB and Listener.
# go to ZIP directory
The README of the SAP BUNDLE INSTALLATION ends here, for a while.
Running the Pre-Upgrade Scripts
1. Log on as the Oracle database administrator <ora_dba>.
Follow the recommendations and instructions. However, you can safely ignore warnings about the setting of database parameter remote_os_authent=TRUE.
Oracle Database Upgrade
Upgrading the Database Structure with the Database Upgrade Assistant
Added on /etc/oratab:
Make sure database and listener are running.
Make a backup of directory <Oracle_home>/network/admin as follows:
cp –r <old_Oracle_home>/network/admin <old_Oracle_home>/network/admin.SAVE
Set ORACLE_HOME_SRC and ORACLE_HOME_TGT:
Change to the correct directory:
Run this script in query mode initially to verify that the environment for the upgrade is correct:
If everything is ok, run:
Make sure the database stopped after finish.
Updating the SQL*Net Config Files
Check if the entries are ok in tnsnames:
/sapmnt/<SID>/profile/oracle ($TNS_ADMIN of SIDadm user)
Check that the following parameters are configured in listener.ora:
If they are missing, copy them from the listener.ora from the source Oracle home <OLD_ORACLE_HOME> and check that Oracle home in listener.ora is set to <NEW_ORACLE_HOME>.
Checking the Symbolic Link for Runtime Oracle Home
It is already been create by the RUNTINSTALLER by default.
Adapting the Environment of the <sapsid>adm user
2.Set the ORACLE_HOME environment variable to new Oracle home, for example:
3.Set ORACLE_BASE to the new Oracle base /oracle/<DBSID>.
4.Adapt the PATH variable so that it no longer contains references to the old Oracle home.
5.Check the environment with:
$ env | grep ORACLE_HOME
$ env | grep ORACLE_BASE
$ env | grep PATH (this should no longer contain a reference to 112_64)
Adapting the Environment of the ora<dbsid> User
1.Log on as user ora<dbsid> and adapt the variables listed below in the .dbenv* files.
Start Listener and DB
Su - oraSID
sqlplus / as sysdba
Run the SBP post-installation instructions as described in the corresponding SBP README
Performing Post-Upgrade Checks
Log on as oraSID
Sqlplus / as sysdba
sqlplus / as sysdba
Performing Post-Upgrade Tasks
Gather Oracle optimizer statistics by executing the following commands as the administration user <sapsid>adm:
Updating the Oracle Instant Client
4.Check and create the symbolic links:
5.Create the symbolic link for BR*Tools 7.40:
Update environment (.dbenv*)
Updating the JDBC Driver References
Only for: Dual Stack (ABAP+Java), Java
If your SAP software is version 7.1 or higher, change the reference to the JDBC driver in the instance profile as described below.
Deinstalling the Old Oracle Home