SAP Note 1915323 Oracle Vs Orasid User
SAP Note 1915323 Oracle Vs Orasid User
Symptom
New User Concept 'Oracle Standard' for SAP NetWeaver Standard Installations
Starting with Oracle Database 12c Release 1 (12.1) SAP supports the user concept 'Oracle Standard' with a
separate Oracle software owner ‘oracle’ also for SAP NetWeaver standard installations with Oracle single
instance on file system (SI/FS). This is the same user concept that is used for SAP NetWeaver installations
on Oracle RAC, Oracle ASM and Oracle Engineered Systems.
Starting with Oracle Database 12c Release 1 (12.1), user concept 'SAP Classic', the classic user concept for
SAP NetWeaver installations with 'ora<dbsid>' as Oracle software owner and database administrator, is
deprecated. It can be desupported in the future. For SAP NetWeaver standard installations with a non-CDB
database of release 12.1.0.2, 12.2.0.1, 18c or 19c, 'SAP Classic' is still supported.
User concept 'SAP Classic' is only supported for Oracle databases with the non-CDB database architecture.
'SAP Classic' is not supported for CDB databases (see SAP Note 2336881).
NEWS
June
INFO: User concept 'SAP Classic' is supported for SAP NetWeaver standard installations (SI/FS)
27,
with Oracle Database 19c (non-CDB only).
2019
October
INFO: User concept 'SAP Classic' is supported for SAP NetWeaver standard installations (SI/FS)
29,
with Oracle Database 18c (non-CDB only).
2018
March INFO: User concept 'SAP Classic' is supported for SAP NetWeaver standard installations (SI/FS)
7, 2017 with Oracle Database 12c (12.2.0.1) (non-CDB only).
March INFO: User concept 'SAP Classic' is supported for SAP NetWeaver standard installations (SI/FS)
7, 2017 with Oracle Database 12c (12.1.0.2) (non-CDB only).
October
A new version of SAP guide "Upgrade to Oracle Database 12c Release 1 (12.1): UNIX" is
22,
available that describes the upgrade procedure for user concept 'SAP Classic'.
2015
August In order to give SAP customers more time to migrate their existing SAP installations with Oracle
13, single instance on file system (SI/FS) to the new user concept ‘Oracle Standard’ with software
2015 Owner ‘oracle’ the decision has been made that the classical user concept ‘SAP Classic’ with
Other Terms
Solution
Starting Oracle Database 12c SAP supports two user concepts for SAP NetWeaver standard installations
with an single instance database on file system (SI/FS):
In user concept ‘SAP Classic’ there is one OS user ‘ora<dbsid>’ that is used for installation of Oracle
database software and for administration of database <DBSID>.
‘ora<dbsid>’
'ora<dbsid>' is software owner and database administrator for database <DBSID>. You log on as ora<dbsid>
to install new Oracle homes or apply patches into existing Oracle homes. You also log on as ora<dbsid> for
daily database administration tasks. Whenever you log on as ora<dbsid> the environment for database
The user home directory is '/oracle/<DBSID>' for SAP installations with Oracle releases 11.2 and before.
Starting 12.1 the user home directory was changed to '/home/ora<dbsid>' (reason: avoid OUI warning 'INS-
32008', see SAP Note 1523171).
As a result, we have the old 'SAP Classic' user concept with software owner 'ora<dbsid>',
ORACLE_BASE=/oracle and HOME=/oracle/<DBSID>. And we have an up-to-date, modern 'SAP Classic'
user concept with software owner 'ora<dbsid>', ORACLE_BASE=/oracle/<DBSID> and
HOME=/home/ora<dbsid>.
By default, 'ora<dbsid>' is a member of the OS groups 'dba' and 'oper'. As a member of these groups,
ora<dbsid> is allowed to connect to the database instance via OS authentication '/ as sysdba' or '/ as
sysoper'.
Every database <DBSID> has its own software owner 'ora<dbsid>' and its own Oracle home.
1. Multiple databases on the same database server can not share the same Oracle home. Using a shared
Oracle home is only possible with user concept 'Oracle Standard'.
2. OS user ora<dbsid> can connect to another database on the same database server other than
<DBSID> using OS authentication if the corresponding Oracle homes were installed with the same
OSDBA/OSOPER groups.
3. The administration tasks ‘Software installation’ and ‘Database administration’ are performed by the
same OS user.
The following table shows OS users and their corresponding OS groups and roles.
User concept 'Oracle Standard' is used by SAP since Oracle Release 11.2 for SAP installations with Oracle
RAC, Oracle ASM and also on Oracle Engineered Systems. Starting Oracle Release 12.1 this user concept
is now also supported for SAP installations with an Oracle single instance database on file system.
OS User 'oracle'
‘oracle’ is the Oracle software owner for all Oracle databases on a database server. You log on as ‘oracle’ to
install Oracle software, to apply patches into existing Oracle homes or to install or clone new Oracle homes.
This user has no environment variables for ORACLE_HOME or ORACLE_SID for a specific database set by
default. This user should be used for software management tasks only.
OS User 'ora<dbsid>'
'ora<dbsid>' is database administrator dedicated for database <DBSID>. You also log on as ora<dbsid> for
daily database administration tasks. Whenever you log on as ora<dbsid> the environment for database
<DBSID> is already set (PATH, ORACLE_SID, DB_SID, ORACLE_HOME, LD_LIBRARY_PATH).
By default, 'ora<dbsid>' is a member of the OS groups 'dba' and 'oper'. As a member of these groups,
ora<dbsid> is allowed to connect to the database instance via OS authentication '/ as sysdba' or '/ as
sysoper'.
Every database <DBSID> has its own database administrator user ‘ora<dbsid>’.
1. OS user ora<dbsid> can connect to another database on the same database server other than
<DBSID> using OS authentication if the corresponsing Oracle homes were installed with the same
OSDBA/OSOPER groups.
2. All database files or all databases are owned by software owner ‘oracle’.
3. All database instance processes belong to software owner ‘oracle’.
1. Unified user concept for SAP on Oracle SI/FS, SAP on Oracle RAC, SAP on Oracle ASM and SAP on
Oracle Engineered Systems.
2. Multiple databases on the same database server can share the same Oracle home.
3. Allows to separate responsibility for Oracle software administration from responsibility for Oracle
database administration (security)
The following table shows OS users and their corresponding OS groups and roles.
Recommendation
User concept 'SAP Classic' is deprecated. It can be desupported in the future (see above). 'Oracle Standard'
is the default user concept for new SAP installations.
For SAP installations with Oracle Database 12c Release 1 (12.1.0.2) and higher SAP SWPM supports both
user concepts 'Oracle Standard' and 'SAP Classic'. For support of 'SAP Classic' SWPM SP09 or higher is
required.
When you upgrade your SAP database to a new database version (12c or higher), you can decide to stay
with user concept 'SAP Classic', or you can decide to migrate to user concept 'Oracle Standard'. The
corresponding SAP Guide describes both alternatives.
You can stay with user concept 'SAP Classic' while you upgrade your database to release 12.1 or higher.
You can migrate from 'SAP Classic' to user concept 'Oracle Standard' at any time later after the upgrade.
In order to use 'Oracle Standard' as user concept, you migrate the software owner from 'ora<dbsid>' to
'oracle' before you upgrade the database. The procedure consists of the following steps:
The complete procedure how you can migrate to user concept 'Oracle Standard' is described in SAP Note
1915317.
SAP
Title
Note/KBA
Transformation of an existing SAP Oracle database into an SAP Oracle pluggable database running
2335850
in an Oracle Multitenant database container (CDB)