Skip to end of metadata
Go to start of metadata

Problems during installation, upgrade or migration

This page provides information about the installation, upgrade and migration tools.


Problems with SAPinst and SAPup/SUM
Problems with R3SETUP or LCSETUP
Drop database
Further information

Problems with SAPinst and SAPup/SUM

The SAPinst installation protocol files are located here:

Unix: /tmp/sapinst_instdir
Microsoft Windows: <drive>:\Program Files\sapinst_instdir
Check the content of file sapinst_dev.log (detailed information) or sapinst.log.

Depending on the tool which is used for upgrade the protocol files are located in the following directories:
Unix: /usr/sap/<SID>/upg/abap/log
Unix: /usr/sap/<SID>/SUM/abap/log
Microsoft Windows: <drive>:\usr\sap\<SID>\SUM\abap\log

The dev_*.log protocol files could be helpful as well for error analysis. You'll find these files for example in /usr/sap/<SID>/SUM/abap/<SID>/DVEBMGS<SYS>/work

back to top

Problems with R3SETUP or LCSETUP

In the installation directory you can find several template and protocol files of the installation. In file <TEMPLATE>.log you can find information about the step in which the error occured and what kind of an error it was (<TEMPLATE>: e.g. DBUPDATE or LCINST)
In file <TEMPLATE>.R3S or <TEMPLATE>.TPL all steps of the migration/installation are listed - sorted alphabetically. The step in which the error occured is marked with STATUS=ERROR. There you can see e.g. which command should have been executed and with which options.
In file XCMDOUT.log you can get detailed information about the problem if it occured when a database tool was used (e.g. during command dbmcli -d <database_name> -u <dbm_operator>,<password> db_state).
In case of a database error you should check the SAP MaxDB log files.

back to top


These tools are used to install or update the SAP MaxDB software.
SDBINST installs/updates the database software only.
SDBUPD is used for an 'database update'. This means that you specify a database and then

  • it is checked if the update is allowed for this database,
  • this database is stopped,
  • the new software is installed,
  • the database is started and
  • the system tables are loaded.

SDBSETUP is available as of version 7.6. It is a GUI which allows software installations as well as database updates. It is also possible to uninstall SAP MaxDB software using SDBSETUP.

SDBINST and SDBUPD provide helpful information at the command prompt (in the shell). If this information is not sufficient, the protocol file MaxDB*<date><time>.LOG in directory <independent_data_path>/wrk should be checked. This protocol file can also be viewed in SDBSETUP.

As of SAP MaxDB version 7.8 (isolated installation) the protocol files are located in <GlobalDataPath>/wrk
SDBINST: SDBINSTMsg<number>.log
SDBUPD: SDBUPDMsg<number>.log

With each start of SDBUPD/SDBINST a new log file is created.

Installations or Updates in the Command Line
Overview of SDBINST options

Known Problem on Microsoft Windows 64 Bit:

2382619 - SDBINST/SDBSETUP stops working on Microsoft Windows

back to top

Drop databse

To be able to drop a database, this database has to be in operational state OFFLINE. You can use Databse Studio to drop the database (Administration Tasks -> Delete Database). Alternatively you can use the following DBM command:
dbmcli -d <database_name> -u <dbm_operator>,<password> db_drop [WITHOUTFILES]

back to top


If you need to uninstall SAP MaxDB software, you should always use SDBUNINST to make sure that all software and all registrations are removed. SDBUNINST must be run as root user (or administrator). Before you can uninstall the SAP MaxDB software you have to make sure that no database exists anymore which uses this software.

The database installation consists of several installation packages which can be listed with the following command:
sdbuninst -l


PCR 7301 /sapdb/programs valid
PCR 7401 /sapdb/programs valid
PCR 7240 /sapdb/programs valid
PCR 7402 /sapdb/programs valid
Server Utilities /sapdb/programs 64 bit valid
PCR 7250 /sapdb/programs valid
Database Kernel /sapdb/ZW6/db 64 bit valid
Database Kernel /sapdb/LW6/db valid
Base /sapdb/programs 64 bit valid
PCR 7300 /sapdb/programs valid
APO COM /sapdb/ZW6/db/sap 3.0A.34 64 bit valid

The PCR packages contain different precompiler runtime versions. These are needed by the SAP application servers.
Package Server Utilities contains e.g. the X server.
APO COM (only used for liveCache) is the installation of the LCA routines.
Package Database Kernel contains the database kernel software.
Base contains information about the complete installation.
Using sdbuninst -all all components based on Base are deleted. If you don't want to remove all SAP MaxDB software, you should specify the package which should be deleted.


sdbuninst -package "Database Kernel"

As there might be several software installations on one server, you are asked which specific installation of a package should be deleted. All installations are listed and you have to enter the number of the installation to be removed.


0: Database Kernel in /sapdb/ZW6/db 64 bit
1: Database Kernel in /sapdb/LW6/db
2: none

A complete description of the uninstall possibilities can be found in the installation manual.

In versions < 7.4.02 SDBUNINST did not exist. If a newer version of SAP MaxDB is running on the same server, you can use SDBUNINST of this version to uninstall the old software. If you don't have any SDBUNINST on this server, please follow the instructions of note 412466.
In case an uninstallation was not performed correctly on a Microsoft Windows server, registry information might still exist after you deleted the software. In this case please check note 572836.

back to top

Further information

Documentation about installations and upgrades can be found here.
You can use the Guide Finder for SAP NetWeaver and ABAP Platform.

Note 498036 contains further information about SAP MaxDB software updates.

Detailed information about SDBINST, SDBUPD and SDBSETUP can be found in the installation manual.

back to top