Background documentationDirectory Locate this document in the navigation structure

 

When installing the database, the installation program creates a series of directories. The programs and libraries of the database system are stored in two different root directories:

The first root directory is the Independent Program Path. There is always only one Independent Program Path on each computer, on which the database software of one or more versions is installed. This path is defined in the first installation of the database software.

The second root directory is the Dependent Path. This directory is only created on the database computer when a database is created. The programs and libraries of the database core are stored in this directory. A database computer can contain any number of Dependent Path root directories of the same or different software versions. Thus every database can be operated with its own database core.

Important Directories in the Database System

Path

Contents of Directory

<independent_program_path>

Programs and libraries jointly used by all databases and applications

These always have the latest installed version of the database software.

<independent_program_path>\runtime

Runtime environment of the clients, such as JDBC, Precompiler

<dependent_path>

Installation directory of the database software

Storage location of the version-dependent server software

Any number of directories can exist together on one computer for the same version or for different versions.

All programs in these version-dependent directories are not executed directly by the user, but are called using the programs stored in the <independent_program_path>.

<independent_data_path>

Data, configuration, and run directories of databases and applications

<independent_data_path>\config

Configuration files for database parameters, data for user authorization, and so on

<independent_data_path>\wrk\<database_name>

Run Directory of the database <database_name>

<independent_data_path>\wrk\<database_name>\DIAGHISTORY

Diagnosis files (backups of the most important log files and memory dumps) which are saved by the database system after a database error

You can configure the path of this directory with the special database parameter DiagnoseHistoryPath.

<tool_application_data>

Includes log and configuration files of the database tool <tool>

<tool_user_data>

Contains the data generated with the database tool <tool> by the logged-on operating system user

During the installation of the database software, the system provides default values for the root directories, which you can adapt to your requirements. The default values provided vary because the system considers the conditions of the installation environment when creating the default values. Those conditions depend on whether SAP MaxDB software installations already exist and which paths they were stored under, whether the software is being installed within an SAP system or for a stand-alone system, and so on.

Therefore, the actual directory structures presented in the documentation are only for orientation purposes.

In the following you find overviews of the paths created during the installation under Microsoft Windows and UNIX/Linux

  • within SAP systems

  • when installing a stand-alone system

Directory Structure Within SAP Systems

Case 1: Software installation with creation of a database (server and client installation)

In SAP systems, a separate SAP MaxDB software package is installed for each database which is only used by that database. This means, for example, that for two databases of version 7.6, the SAP MaxDB software of version 7.6 is installed twice.

The complete software installation on the database computer comprises the following paths:

  • An Independent Program Path

  • A Dependent Path

  • An Independent Data Path

  • A run directory of the database

  • A path for log volume storage

  • A path for data volume storage

Default Values for the Directory Structure

Path

Default Value on Microsoft Windows

Default Value on UNIX/Linux

Independent Program Path

<drive>:\sapdb\programs

--bin

--pgm

--...

--...

/sapdb/programs

Dependent Path

<drive>:\sapdb\<database_name>\db

/sapdb/<database_name>/db

Independent Data Path

<drive>:\sapdb\data

/sapdb/data

Run directory of the database instance

<drive>:\sapdb\data\wrk\<database_name>

/var/opt/sdb/data/wrk/<database_name>

Storage of log volumes

<drive>:\sapdb\<database_name>\saplog

/var/opt/sdb/data/<database_name>/log

Storage of data volumes

<drive>:\sapdb\<database_name>\sapdata

/var/opt/sdb/data/<<database_name>/data

To ensure the downward compatibility of the database software, the database system also creates the following directories on UNIX/Linux:

Path

Contents of Directory

/var/spool/sql

Links to current directories and files

/usr/spool/sql

Links to current directories and files

Case 2: Software installation as application server (client installation)

In a pure client installation, the following paths are created:

  • An Independent Program Path

  • An Independent Data Path

Default values for the directory structure

Path

Default Value on Microsoft Windows

Default Value on UNIX/Linux

Independent Program Path

<drive>:\sapdb\programs

--bin

--pgm

--...

--...

/sapdb/programs

Independent Data Path

<drive>:\sapdb\data

/sapdb/data

To ensure the downward compatibility of the database software, the database system also creates the following directories on UNIX/Linux:

Path

Contents of Directory

/var/spool/sql

Links to current directories and files

/usr/spool/sql

Links to current directories and files

Directory Structure within Stand-Alone Systems

Case 1: First installation of the database software with creation of a database

  • An Independent Program Path

  • A Dependent Path

  • An Independent Data Path

  • A run directory of the database

  • A path for log volume storage

  • A path for data volume storage

Path

Default Value on Microsoft Windows

Default Value on UNIX/Linux

Independent Program Path

<drive>:\Program Files\sdb\programs

/opt/sdb/programs

Dependent Path

<drive>:\Program Files\sdb\<database_name>

/opt/sdb/<database_name>/db

Independent Data Path

<drive>:\Documents and Settings\All Users\Application Data\sdb\data

/var/opt/sdb/data

Run directory of the database instance

<drive>:\Documents and Settings\All Users\Application Data\sdb\data\wrk\<database_name>

/var/opt/sdb/data/wrk\<database_name>

Path for log volume storage

<drive>:\Documents and Settings\All Users\Application Data\sdb\<database_name>\log

/var/opt/sdb/data/<database_name>/log

Path for data volume storage

<drive>:\Documents and Settings\All Users\Application Data\sdb\<database_name>\data

/var/opt/sdb/data/<database_name>/data

To ensure the downward compatibility of the database software, the database system also creates the following directories on UNIX/Linux:

Path

Contents of Directory

/var/spool/sql

Links to current directories and files

/usr/spool/sql

Links to current directories and files

Case 2: Creating additional databases that use this server software

The Independent Program Path and Independent Data Path have already been defined during the installation of the server software used.

When additional databases are being created, there is created one Dependent Path for each database. In addition, below the existing Independent Data Path, the path for the working directory, the path for log volume storage and the path for data volume storage are created for each database.

In a summary, the following new paths are created for each database:

  • A run directory of the database

  • A path for log volume storage

  • A path for data volume storage

Path

Default Value on Microsoft Windows

Default Value on UNIX/Linux

Run directory of the database instance

<drive>:\Documents and Settings\All Users\Application Data\sdb\data\wrk\<database_name>

/var/opt/sdb/data/wrk/<database_name>

Path for log volume storage

<drive>:\Documents and Settings\All Users\Application Data\sdb\<database_name>\log

/var/opt/sdb/data/<database_name>/log

Path for data volume storage

<drive>:\Documents and Settings\All Users\Application Data\sdb\<database_name>\data

/var/opt/sdb/data/<database_name>/data

Example Example

The databases DEMODB, TESTDB and MAXDB are all created with the same existing server software. The following path structure results under the Independent Data Path:

<drive>:\Documents and Settings

-All Users

-Application Data

-sdb

-data

-wrk

-DEMODB

-TESTDB

-MAXDB

-DEMODB

-log

-data

-TESTDB

-log

-data

-MAXDB

-log

-data

End of the example.

Case 3: First installation of the database software with the aim of creating the first database later on

  • An Independent Program Path

  • A Dependent Path

  • An Independent Data Path

Path

Default Value on Microsoft Windows

Default Value on UNIX/Linux

Independent Program Path

<drive>:\Program Files\sdb\programs

/opt/sdb/programs

Dependent Path

<drive>:\Program Files\sdb\<version>

/opt/sdb/<version>

Independent Data Path

<drive>:\Documents and Settings\All Users\Application Data\sdb\data

/var/opt/sdb/data

To ensure the downward compatibility of the database software, the database system also creates the following directories on UNIX/Linux:

Path

Contents of Directory

/var/spool/sql

Links to current directories and files

/usr/spool/sql

Links to current directories and files

More Information

Database Administration in CCMS, Properties