## Typical Error Situations

We recommend that you monitor the database instance continuously. For more information, see Monitoring.

Typical Error Situations

Problem | Typical Symptoms | Solutions

Error during installation or upgrade of the database software

The installation or upgrade of the database software fails

Check the installation log, see Log Files.

For more information, see Installation Manual, Troubleshooting.

SAP customers will find more information in the following SAP notes: 851169 (installing MaxDB on UNIX/Linux), 848437 (installing MaxDB on Microsoft Windows), 851229 (upgrade MaxDB/Java), 817463 (upgrade MaxDB/ABAP)

Error during restore of database instance. | A data or log backup is defective. | Check the backup, see Database Manager GUI, Checking Backups Database Manager CLI, recover_check
The data area is full. | All tasks are suspended, the system is “hanging” | Add a new data volume. See: Database Manager GUI, Creating, Displaying and Deleting Volumes Database Manager CLI, db_addvolume Database Administration in CCMS: SAP liveCache Technology, Configuring Volumes
The log area is full. | All tasks are suspended, the system is “hanging” No upgrade possible (loading system tables fails) | Back up the log entries Then, if necessary, add a new log volume (see above). The new log volume will only be used by the database system when the redo log entries in the old log volume have been backed up.
The database instance is not in the ONLINE operational state. | Users cannot log on to the database instance. | Start the database instance. See: Database Manager GUI, Starting (Restarting) the Database Instance Database Manager CLI, db_online Database Administration in CCMS: SAP liveCache Technology, Starting liveCache
Maximum number of database sessions reached | No further users can log on to the database instance. | Raise the value of the general database parameter MAXUSERTASKS.
The database instance kernel has crashed. | The database instance is in the OFFLINE operational state. | Check the kernel log knldiag, see Log Files.
A firewall prevents the connection to an X server on a remote computer. | You can not connect to a database instance on a remote computer using the Database Manager. | Ensure that the port of the X server on the remote computer is not locked by a firewall.
The X Server on a remote computer is not running. | You cannot log on to a database instance on a remote computer. | Start the X Server.

See also:

Troubleshooting

Installation Manual, Error Handling