Below information was taken from SAP Note 562863 – FAQ: Logon mechanisms. The following database users exist in the SAP environment:
| Database User | Description |
|---|---|
| • SAPR3 • SAP[sid] • SAP[xyz] • SAPSR3 | The SAPR3 / SAP[sid] / SAP[xyz] / SAPSR3 user is the owner of all R/3 objects. The work processes log on to the database with this user. The SAPR3 user was always used for older R/3 releases. However since several R/3 systems may be present in the same database within MCOD with current releases – you can replace the SAPR3 user with a system-specific SAP[sid] user here. You can define this during the installation. To avoid confusion during homogeneous system copies as of 4.7 SR1 you can use an SID independent username – SAP[xyz] with "SAP" followed by any three characters (see Note 617444). In the meantime the system proposes the username SAPSR3 by default – irrespective of the SID that the system actually uses. |
| • SAPR3SHD • SAP[sid]SHD • SAP[xyz]SHD • SAPSR3SHD | This user is used temporarily within an SAP shadow upgrade. This user is not required during normal system operation. |
| • SYSTEM | The SYSTEM user is created during the Oracle installation as standard and has extensive authorizations. Some of the objects in the system tablespace belong to this user. |
| • SYS | The SYS user is also created during Oracle installation and also has extensive authorizations. Most of the objects in the system tablespace belong to this user. |
| • OPS$[sid]ADM • OPS$SAPSERVICE[sid] | The OPS$ users are taken from R/3 and used to set up the connection to the R/3 database and to execute sapdba and BR tools and are created as part of the R/3 installation. |
| • INTERNAL | CONNECT INTERNAL is a mechanism that you can use to log onto the database without a password. Therefore strictly speaking – INTERNAL is not a user. As of Oracle 9 – CONNECT INTERNAL is no longer available – instead only the "/ AS SYSDBA" and "/ AS SYSOPER" connects are available. |
| • OUTLN | Stored Outlines are managed in the OUTLN user. If this user is missing – ORA-18008 may occur. See Note 722376 which contains further information. |
| • DBSNMP | The DBSNMP user may be created by Oracle but does not play a role in the R/3 environment. |
| • CTXSYS | The CTXSYS user is only used in conjunction with Oracle and has no role in the R/3 environment. This user is only required if you use Requisite/BugsEye. SAP[sid]DB |
| • TSMSYS | The TSMSYS user is an Oracle-internal user (Transparent Session Migration) that is automatically created as of 10g but that is of no importance in the SAP environment. |
| • DIP | The DIP user is an Oracle-internal user (Directory Integration Provisioning) that is automatically created as of 10g but that is of no importance in the SAP environment. |
| • ORACLE_OCM | The ORACLE_OCM user is required for the Oracle Configuration Manager (see Note 974781) which is not used in the SAP environment and therefore is not critical. |
| • APPQOSSYS | The APPQOSSYS user is required for saving and administering the Quality of Service data. This user is irrelevant in the SAP environment. |
| • SAP[sid]DB • SAP[xyz]DB • SAPSR3DB | SAP[sid]DB / SAP[xyz]DB or SAPSR3DB is the equivalent to SAPR3 / SAP[sid] / SAP[xyz] / SAPSR3 in the J2EE environment as of Release 6.30. |
| • SAPPCD | In the EP environment the SAPPCD user is owner of the objects of the Portal Content Directories (PCD). |
| • SAPWCM | In the EP environment the SAPWCM user is owner of Content Management objects. |
| • SYSMAN • MGMT_VIEW | These users are used in conjunction with Oracle Enterprise Manager. For more information about SYSMAN see Note 1635210. |
| • DVSYS • DVF • SECADMIN • SECACCTMGR • SAPACCTMGR • BRTDBA • SUPPORT_DBA | These users are used if you use the Database Vault (see Note 1503634). |
