Sap database log files

You need the file ID of the log file. Note that file IDs are case-sensitive. Kernel Logs. File Name. File ID. Current kernel log of the database instance. Contains all kernel messages error messages, warnings and information. Run directory of the database instance. Detailed current kernel log of the database instance. You can use the Database Manager to display more information about the messages. Pseudo XML file. Error messages and start messages of the kernel since installation.

Last kernel log before the last restart. General Log Files. History of the database parameters. Text version of the database trace. Memory dump after a database crash. Only for Microsoft Windows. Memory dump after database kernel crash for postmortem debugging. This file contains database error messages only. The content of this file is not overwritten cyclically. This file contains the data of the database trace.

In case of an emergency shutdown the global memory of the database is dumped into file knldump. The size of this file is approx. The corresponding fdirectory run directory by default needs to be large enough to store this file.

The development team might need to analyse the knldump to find the cause of an emergency shutdown. It is not necessary to send this knldump to the support teams.

In case of a database crash you can see in file rtedump which tasks were active in the database at the time of the crash. The timestamp is the time of this database restart - not of the crash.

The default is 2. The files are cyclically synchronized. In the case of a database crash, the current content of the memory segments is synchronized with the memory mapped files. For more information check SAP note: Backup history, includes backup IDs, external backup IDs and error messages. If a backup tool successfully executed a backup but could not determine the backup ID, it enters the backup as failed in the backup history. X Server Messages. X Server Messages Old.

The system overwrites this log file each time Database Studio is started and saves the old log file as dbstudio. Further Database Analyzer Log Files. Loader Log File.

Loader Transformation History. History of all start, stop and initialization actions of SAP liveCache. The system appends the information in the lcinit. Glossary , Directory. Log Files The database system, database tools and interfaces write information and error messages to log files. If the database crashes, a stack back trace is written.

This file is not overwritten cyclically. If you are analyzing database problems and the Database Messages and Database Messages Old files do not contain the relevant information anymore, check the Database Errors file.

Database Messages Old. Database Messages Classic. Depending on your system, this file may become very large. In case of an emergency datatabase shutdown, the global memory of the database is dumped into this file in binary format. Note that on Unix, no dump file is written if the database crashes due to a Unix signal. Runtime Environment Dump.

In case of an emergency database shutdown, this file contains the tasks that were active in the database at the time of the emergency shutdown. Database Parameter History. To change the name and location of this file, use the support database parameter KernelTraceFile , see Support Database Parameters. Database Trace Readable.

Text version of the database trace available after a database trace has been created. Installation Log File. Depending on which program you have used to install, update or uninstall the software:. Event Dispatcher Configuration. You can also configure another name using the EventFileName support database parameter.

For information from third-party backup tools, see the respective documentation. Backup Templates.