Technical Articles
Oracle 19c database upgrade of SAP system
Hello,
I am writing this blog, to describe the steps how you upgrade the Oracle database of your SAP system to Oracle Database 19c
Preparations
- Supported upgrade path to 19c?
To upgrade your database directly to Oracle Database 19c, your source database release must be Oracle 11.2.0.4, Oracle 12.1.0.2 or Oracle 12.2.0.1.
from 12.1.0.1, 11.2.0.3, 11.2.0.2, 11.2.0.1, 11.1, 10.2 or earlier – Direct upgrade is not supported.
- check SAP note 2800001 – Upgrading to Oracle Database 19c (DBUA)
- Check PAM to ensure that your SAP product is supported with Oracle Database 19
- Download the oracle 19c software, Opatch, SBP – SAP Bundle patch.
Installation of oracle 19c database software
First backup the oracle inventory
- Log on as Oracle software owner, for eg: oracle or ora<sid>
- Install the new Oracle database software into the <ORACLE_HOME_NEW>, for eg: /oracle/SID/19.0.0
- Set environment variables DISPLAY and DB_SID,
- then start RUNINSTALLER. For RUNINSTALLER options, check SAP Note 2660017.
OS> setenv DB_SID <DB_SID>
OS> setenv DISPLAY <DISPLAY>
OS> ./RUNINSTALLER
https://help.sap.com/viewer/08baebca0fef470389e4a4ebcb46b879/CURRENT_VERSION/en-US/68ef72fdd9314bd2b9964652bb279f31.html
oracle base usually be : /oracle/SID
Now we will have to apply SAP Bundle Patch to new installed software oracle 19.0.0
(make sure you have downloaded these 3 files from service market place)
First extract SAP19P_XXX.ZIP file and copy Mopatch folder to new oracle home location (/oracle/SID/19.0.0/)
Second update the Opatch:
extract the OPATCH19P_XXX.ZIP file to oracle home (/oracle/SID/19.0.0/)
then Fianlly apply SBP using mopatch
Oracle 19c database upgrade
- Run the pre-upgrade scripts
- Please take backup of the listener configuration files
Login with ora<sid> with 11.2.0.4 oracle home
set the env variables
stop SAP system
Check oratab entries
start DBUA
Post upgrade steps
After the Oracle database upgrade, you need to perform the steps described here.
1. Check oratab entries
2. Check the symbolic link for the runtime Oracle home.
3. Adapt the environment of the <sapsid>adm user (eg: oracle home, client)
4. Update the SQL*Net configuration files
5. Stop the old version listener and start the database listener of 19c
6. Start the database instance (make sure oracle home is pointing to right oracle home)
7. check the database parameters for 19c and implement recommended parameters from sap note 2470718 – Oracle Database Parameter 12.2 / 18c / 19c
8. Update the Oracle Instant Client if required
9. Update BR*Tools executables
10. Update Database Statistics
11. Backup the database
12. R3trans -d, make sure it returns 0000
Finally Start the SAP system
Hi.
Nice Blog.
A small update regarding the SBP installation from me. If you stricktly follow the README of the SBP and the official SAP guides/notes there is no need to set ORACLE_HOME(s) additionally and you can install the SBP with one single command (in case of single instance).
Dear Pratap,
Thanks, we have seen your post on blog. which is very nice. we are also trying to upgrade Oracle 12.2.0.1 to 19.0.0.1.we followed all your steps. but now when we start dbua upgrading from oracle user getting an error, which is attached in here
db-12-19.png
error- " [DBT-20017] The database PRD is not in a READ/WRITE open mode."
As per some solutions we try to make DB in Read-Write mode but db is already in Read-Write mode also Opened
OS - Release version as below.
Operating System: SUSE Linux Enterprise Server 12 SP1
Please Help us.
Thanks & Regards,
Shibaram Nayak./ Kuldeep Patil.
dbua error
Hello Shibaram,
Have you overcome this error?
Could you describe your path, we have the same probem right now ?
Thank you
UPDATED:
Guys, we resolved it.
What helped us is ORACLE_HOME linked to old home without link in its path (e.g. /oracle/SID/11204 but not /oracle/SID/112_64), also oratab string should contain the same path.
We restarted DB then, and proceed with dbua successfully.
good luck!
Hello Shibaram,
Did you able to solve the above issue? if not please check if below points helpful
1.Please check oratab file and make sure it has source database entry
2. How did database is started as of now? please start the database with oracle database owner (orasid or oracle)
3.Start the DBUA with oracle database owner (orasid or oracle) with all environment variables set
Regards
Pratap
Hi Pratap,
Thanks for sharing such a great blog on 19c Upgrade, descriptive and detailed one.
Wondering if have you come across Migration of Oracle from HPUX to Oracle Linux (OS Change migration).
I would be great if you can share, this blog help me to upgrade my Oracle from 18c to 19c
Regards,
Vivekanand Pandey
Hi Vivekanand Narsingh,
If you are planning to perform a migration that involves a change in the Operating system, you should consider using the heterogeneous system copy approach using the Software Provisioning Manager, check our SAP Notes 1738258 or 2568783, to verify what is the most suitable scenario for you.
With regards to the Oracle upgrade from 18c to 19c, check the detailed instructions included in the following URL:
https://help.sap.com/doc/2570419c44414d1e9d83732636ed95e2/19c/en-US/Upgr_Ora_UX_Guide_19c.pdf
Our general SAP Note with access to SAP Guides for Oracle Upgrade is also available in the SAP Note 2540847.
Regards,
Pedro Ruiz
Hi Pratap,
we are planning for a heterogeneous system copy in our landscape. parallely we need to upgrade oracle 12 to 19c also. and our SAP is non-unicode. Does oracle 19c supports Non-unicode. Please let me know.
Thanks
Ramesh
Hi Ramesh,
according to these SAP notes, 19c should ideally support non UC systems
- SAP NetWeaver 7.0X (AS ABAP only)/ 7.1/7.3/7.40/7.5x
- SAP BW 7.10/7.11/7.20/7.30/7.31/7.40/7.50
- SAP ERP 6.0
- SAP CRM 7.0
- SAP SCM 7.0
- SAP SRM 7.0
- SAP Solution Manager 7.2
- Banking Services from SAP 6.0/7.0/8.0/9.0
- SAP NW CE 7.1/7.20
- SAP NW PI 7.1
Even if you choose non UC kernel in PAM, it's showing as compatible with 19c
Regards
Pratap
Hello Pratap,
Thanks for the details step of 19c upgrade it is very useful. I need a help and suggestion, I am at dbua post upgrade phase now unfortunately my dbua session got closed and lost VNC connection as well. Now I am trying to start the dbua it is starting from beaning again. Can you please help me with the start option from where it got stopped in unix OS.
Thanks and Regards
Hafeez
Hi Pratap Naidu,
can you please explain if is it possible to upgrade to 19c from a Oracle 11.2.04 Version that has NOT been patched with the latest Opatch, SBP – SAP Bundle patch ?
Kind regards,
Tommaso
Hello Tommaso,
As long as your source database release is 11.2.0.4 version, DBUA allow you to upgrade to 19c version. SAP didn't give any information about minimum patch on source database.
But it is always good to apply SBP before 19c upgrade,if you have old SBP.
Please check sap note 2800001 and for os requirements.
2478541
Regards
Pratap
well explained. Thnx for sharing 🙂
Oracle 19c is not supported with SDI data mining and log based logic replication
Recommendations, you should do stress tests. After migrating from 12 to 19 we have serious performance problems.
That we still haven't solved.
Hi Matias,
Please check this SAP note and see if it helps
1817553 - Checklist for performance problems in SAP Oracle Databases
Regards
Pratap
Dear Naidu,
After setting the environment variable to 19 as below
setenv ORACLE_HOME /oracle/XXX/19.0.0
setenv IHRDBMS /oracle/XXX/19.0.0
setenv OHRDBMS /oracle/XXX/19.0.0
setenv LIBPATH /usr/lib:/lib:/usr/sap/ESQ/SYS/exe/run:/oracle/XXX/19.0.0/lib
setenv PATH /oracle/XXX/19.0.0/bin:$PATH
When I am running mopatch to install the bundle patches, its showing an error as below
./mopatch.sh -v -s SAP19P_2111-70004506.ZIP
Invalid patch work directory "." specified (below Oracle Home).
Usage: mopatch [-hvdn] [-o opatch-param] [-j jre]
[-m make-utility] [-z unzip-utility]
[-s patch-source-path] [patch-work]
Please help to fix this
Hello Vinay
You have to run the command the mopatch file location
cd /oracle/XXX/19.0.0/MOPatch
>> ./mopatch.sh -v -s <<path to SAP19P_2111-70004506.ZIP location>>
Regards
Pratap
the /sap/ora_upgrade directory doesnot exist after 19c binary installation ? is it something created after SBP installation ? i understand pre and post check scripts must be run from 19c binary (TGT) not from source ...can you please explain ?
Hi Yogesh,
Yes, please apply latest available patch.. those directories will be created