Friday, March 21, 2014

Oracle DB versioning

Oracle as database is quite popular within SAP customers. It is fact for many years. The reason why customers are running their SAP system on Oracle database is that Oracle is quite stable, scalable and SAP is really optimized for Oracle. Although both companies do not like each other very much when it comes to database SAP is really taking a lot of effort to optimize their software for Oracle. Not sure how long this will be true as SAP will certainly shift its focus on their own homegrown HANA database but for time being it is valid.

Speaking of BW there are many features that are optimized for BW running on Oracle DB. You can find a lot of SAP Notes discussing those features. There are many RSADMIN parameters just for Oracle as DB. Once you want to use some of these features you may need to check first fi you have valid version of Oracle DB for which feature is valid. This here comes the tricky part. Oracle DB versioning is different from its DB’s marketing names. You can see in the particular note (e.g. 1287382) that you need Oracle DB 11g. What you see in your SAP system under menu System-> Status is that you have So is really 11g? Well version number starts with 11 but what about g?

Unfortunately I haven’t found any official material on how to match between real version number and its marketing name. But speaking very high level we can match those two as follows:

Oracle v2
Oracle v3
Oracle v4
Oracle v5
5.0.22, 5.1.17, 5.1.22
Oracle v6
Oracle8i rel 1–
Oracle8i rel 2–
Oracle8i rel 3–
Oracle9i rel 1–
Oracle9i rel 2–
Oracle Database 10g Rel 1–
Oracle Database 10g Rel 2–
Oracle Database 11g Rel 1–
Oracle Database 11g Rel 2–
Oracle Database 12c Rel 1

Source of information: Wikipedia page.

No comments: