Database Reference
In-Depth Information
CHAPTER 20
Database Configuration and Administration Using SAP
BRTOOLS
SAP uses a set of naming conventions for different database components, such as ta-
blespaces, datafiles, and Oracle Database-related file systems. SAPinst also sets environ-
mental variables, creates operating system and database user accounts, and creates configura-
tion files as a part of the standard SAP installation. It is important to stick to the standard
SAP naming conventions, as proper functioning of BRTOOLS will depend on such usage.
The first half of this chapter will discuss the naming conventions, operating system (OS) and
database user accounts, configuration files used by Oracle in SAP environments, and work
process login and password control mechanisms, and the second half of the chapter will dis-
cuss the Oracle Database administration activities using BRTOOLS.
Naming Conventions for Tablespaces
The SAP default installation uses the classic Oracle Database tablespace naming conventions
to separate the data and index tablespaces in older versions. With the advances in hard disk
and memory technologies, these classic conventions have been changed as of SAP Web AS
6.10.
Table 20-1
lists the tablespace naming conventions and a brief description of the pur-
pose of the tablespace. In the new naming conventions, the entire SAP ABAP stack is in one
tablespace PSAP<SCHEMA-ID> for ABAP systems and PSAP<SCHEMA-ID>DB for Java
systems. New features in Oracle Database, such as system managed automatic segment space
management, UNDO tablespaces, locally managed SYSTEM tablespace, and default tempor-
ary tablespaces, use the new tablespace format by default. Tablespaces SYSTEM,
PSAPUNDO, and PSAPTEMP are locally managed upon creating, but with uniform extent
size.
