27.04.2013 Views

SAP Basis

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

ADM100 Lesson: Appendix - Database Logs<br />

• User processes<br />

• System error messages<br />

The log is run as a circular memory file that is overwritten as soon as it<br />

reaches a certain size. A new log file is created after every start of the<br />

database system. A backup copy of the old log (knldiag.old) iscreated<br />

before a restart of the database system.<br />

All error and warning messages concerning the database system are<br />

recorded in the error log (knldiag.err), including the messages for the<br />

system start and stop.<br />

MS SQL Server<br />

Figure 26: MS SQL Server<br />

The MS SQL Server logs all significant events such as starting<br />

and stopping the database and error messages in the file<br />

:\MSSql7\Log\Errlog. A new error log file is written at every<br />

start of the MS SQL server. Multiple versions of these error log files are<br />

stored as Errlog.1, Errlog.2, and so on. The oldest available version is<br />

stored as Errlog.6. AteveryrestartoftheSQLserver,theoldestfileis<br />

overwritten. If a serious database problem occurs, you should backup the<br />

oldest file before the restart, so that this information is not lost.<br />

TheseerrorlogfilescanbedisplayedintheEnterpriseManager.<br />

Messages of the “SQLServerAgent” service that is required for backups are<br />

also logged in the above directory in the file Sqlagent.out. Thelastsix<br />

versions of this log are also retained.<br />

2003/Q3 © 2003 <strong>SAP</strong> AG. All rights reserved. 79

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!