This file is overwritten when a new request is sent to a third-party backup tool.
Information about backups of the database that are created using third-party backup tools. 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. Information on loading the system tables for the databaseīackup history of the database, includes backup IDs, external backup IDs, and error messages General log file for all DBM servers that are located on the database computer You can display the data path using the dbm_getpath DBM command:įor more information, see Database Manager CLI, dbm_getpath. Log file of the DBM server of the current installation, containing all administration commands sent to the DBM serverĮxamples: information about adding data and log volumes or database parameter changes Information and history of backup templates of the database If no backups have yet been executed or the backup history was interrupted, HISTLOST is displayed.įor information from third-party backup tools, see the respective documentation. 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.īackup history of the database: contains all backup and restore actions To change the location of the file, use the support database parameter RTEDumpFileName. Note that on Unix, no dump file is written if the database crashes due to a Unix signal.
In case of an emergency datatabase shutdown, the global memory of the database is dumped into this file (in binary format). To change the location of the file, use the database parameter KernelDumpFileName, see Support Database Parameters. Last kernel log file (before the last restart)Ĭlassic form of the current database kernel log fileĭepending on your system, this file may become very large. See also the special database parameter MaxKernelMessageArchiveSize 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. See also Special Database Parameters KernelMessageFileSize and KernelMessageHistor圜ountĮrror messages and start messages of the kernel since installation If the database crashes, a stack back trace is written. These messages will be overwritten cyclically. The second part of the file contains the messages that the database writes during operation. Of the kernel log file is copied to the Database Messages (Old) file. These messages are not be overwritten until the next database start, when the old version
#Sap installation log file location software#
The first part of the file contains messages of the database start into the operational state ADMIN: information about the software version, important paths and the current values of the database parameters. This file is written in a pseudo-XML format.
Run directory of the database (see Run Directory).Ĭurrent kernel log file of the database, containing all kernel messages (error messages, warnings, and information)
0 kommentar(er)
