Procedure documentationTroubleshooting Locate this document in the navigation structure


  1. Check if one of the typical error situations (listed below) applies.

    Typical Error Situations

    Error Situation

    Typical Symptoms


    More Information

    Error during installation or upgrade of the database software

    The installation or upgrade of the database software fails.

    Check the installation log file.

    The database is not in the ONLINE operational state.

    Users cannot log on to the database.

    Start the database.

    Error during data or log backup

    A data carrier is not available.

    Make the data carrier available.


    Error during restore of a database

    A data or log backup is damaged.

    Check the backup.

    The data area is full.

    All tasks are suspended, the system comes to a stand-still.

    Add a new data volume.

    The log area is full.

    All tasks are suspended, the system comes to a stand-still.

    No upgrade is possible (the system tables cannot be loaded).

    Back up the redo log entries.

    Then, if necessary, add a new log volume.

    Caution Caution

    Adding a new log volume will not immediately reduce the filling level of the log area. The system will only use the new log volume after you have carried out a log backup.

    End of the caution.

    Database Studio,

    Database Manager CLI,

    Database Administration in CCMS, Monitoring the Log Area

    Maximum number of database sessions reached

    No further users can log on to the database.

    Raise the value of the general database parameterMaxUserTasks.

    General Database Parameters

    The database kernel has crashed.

    The database is in the OFFLINE operational state.

    Check the kernel log file.

    A firewall prevents the connection to the relevant SAP MaxDB X server (database communication server) on a remote computer.

    You cannot connect to a database on a remote computer.

    Ensure that the port of the relevant SAP MaxDB X server on the remote computer is not locked by a firewall.

    Global Listener and X Servers

    The relevant SAP MaxDB X server on a remote computer is not running.

    You cannot log on to a database on a remote computer.

    Start the relevant SAP MaxDB X server.

    Global Listener and X Servers, Starting the Global Listener and/or Installation-Specific X Servers

    Inconsistent database structure

    -9053: Data page corrupted

    -9023: Illegal entrypos

    -9003: Illegal entrylength

    -9006: Illegal keylength

    -9041: Index not accessible

    Check the database structures and correct the error(s).

    Database error in an SAP system

    A database problem occurs in an SAP system that uses the SAP MaxDB database or SAP liveCache technology.

    Analyze the problem.

    Database Administration in CCMS, Performance

      The database is slow.

      Carry out a performance analysis

      Analyzing Database Performance

      Error message

      The system displays an error message.

      The Messages documentation explains (error and information) messages from the database system and recommends how you can react to them. The messages are sorted by error number.

      Messages documentation

      Miscellaneous errors

      Your system is not behaving as expected.

      Check whether your database configuration still complies with the current recommendations for your system.

      Checking the Database Configuration

    • Open the Database Errors log file and check whether there are any error messages for your database.

      More information:

    • If you cannot find a solution to your problem, save the Database Messages log file of your database to a local text file.

      The Database Messages file is the main database log file, which contains all database kernel messages (error messages, warnings, and information). The beginning of the file contains information about the software version, important paths and the current values of the database parameters. The end of the file contains the latest database actions.

    • Proceed as follows.

      • If you are an SAP Customer

        If you are an SAP customer, perform a SAP notes search on the SAP service marketplace at (login required). The component for SAP MaxDB is BC-DB-SDB*.

        If you cannot find any SAP note describing your problem, open a support message with a detailed problem description and attach the Database Messages file. More information: Getting Support

      • If you are not an SAP Customer

        Search the SAP MaxDB wiki at

        Search the SAP MaxDB forum in the SAP Community Network (SCN) at

        If you cannot find an answer to your problem, post a new question to the forum with a detailed problem description and information about your system setup (for example from the Database Messages file).

    More Information

    You can follow the status of general software problems submitted to SAP using the PTS system. More information: Tracking Problem Messages in PTS