7/27/2019 195157 - Application Log Deletion of Logs

http://slidepdf.com/reader/full/195157-application-log-deletion-of-logs 1/5

17.01.2013 Page 1 of 5

SAP Note 195157 - Application log: Deletion of logs

 Note Language: English Version: 19 Validity: Valid Since 04.08.2005

Summary

Symptom 

One or several database tables of the application log contain too many

entries.

The following database tables belong to the application log:

- BALHDR (all releases)

- BALHDRP(< 4.6C)

- BALM (< 4.6C)

- BALMP (< 4.6C)

- BALC (< 4.6C)

- BALDAT (>= 4.6C)

- BAL_INDX (all releases)

Other terms

RSSLG200,

RSSLGK90,

SLG2,

application log,

log

delete,

performance

Reason and Prerequisites

The application log is a tool to collect, save and display logs.

Many different applications collect messages in the application log which

contain information or messages for the end user. The application

automatically log serves as a temporary storage for messages. The logs are

written on the database but they are not automatically deleted.

There is no general procedure for switching the application log on or off.

Some applications provide this option or they offer the option of reducing

the number of entries created. (See Notes 91519, 183960, 141244).

The expiration date of application logs

---------------------------------------------------------------------

A log usually has an expiration date, which is set by the application, that

calls the 'Application log' tool. If the application log does not set an

expiration date, the 'Application log' tool sets the expiration date as

12/31/2098 or 12/31/9999,depending on the release, which allows the logs to

stay in the system for as long as possible. The end user cannot set the

expiration date. The expiration date does not mean that logs which have

reached that date will automatically be deleted. It is used to control the

deletion of logs when you call the Deletion report. The DEL_BEFORE flag in

the BALHDR table determines whether or not the log can be deleted even

before the expiration date is reached.

DEL_BEFORE= SPACE means that the log can be deleted before the expiration

date is reached. (Default value)DEL_BEFORE='X' means that the log can only be deleted after the expiration

date.

7/27/2019 195157 - Application Log Deletion of Logs

http://slidepdf.com/reader/full/195157-application-log-deletion-of-logs 2/5

17.01.2013 Page 2 of 5

SAP Note 195157 - Application log: Deletion of logs

Solution

Deleting the logs of the application log.

Releases >= 4.6A:

=====================================================================

In Releases >= 4.6A, use Transaction SLG2.

On the selection screen you can restrict the amount of logs to be deleted:

o The 'Object' and 'Subobject' fields specify the application area in

which the logs were written (see F4 Help).

o The 'External Identification' field specifies the number which was

provided for this log by the application.

o o If you also want to delete logs which have not reached the

expiration date you must set the option "Also logs which can be

deleted before the expiration date".

Select 'Help with application' in Transaction SLG2 for further explanationof the procedure for deleting.

SLG2 is a report transaction. The corresponding report is SBAL_DELETE. At

regular intervals, this can be scheduled as a background job.

Releases < 4.6A:

=====================================================================

For Releases < 4.6A, note the following instructions:

In general, the deletion of application logs can be carried out in two

steps:

1. Report RSSLG200: Deletion of all logs which expired:

----------------------------------------------------------------------

Use report RSSLG200 to delete all logs whose expiration date is reached or

exceeded. (This report is not yet available in the standard in Release

3.0F. In this case, the report can be installed in advance; see corrections

attached to this note).

As of Release 3.1H, Report RSSLG210 is also available. This report allows

the definition of a job that runs regularly and deletes such logs.

2. Report RSSLGK90: Deleting all logs for which a deletion is allowed

before expiration:

----------------------------------------------------------------------

Sometimes, step 1 does not delete enough logs. The reason for this might be

that the expiration date of the logs is too far in the future or that no

expiration date has been defined at all (in this case, dependingon the release, the assumed expiration date is 12/31/2098 or 12/31/9999)

Use report RSSLGK90 for these logs.

When you execute this report, you can restrict the logs to be deleted in a

selection screen:

o The fields 'Object' and 'Subobject' specify the application area

which wrote the logs (see F4 help).

o The field 'External number' indicates the number which was assigned

by the application for this log.

o Field 'Log class' indicates the importance of the log.NOTE: By default, this field contains the value '4', this means

only logs with additional information. If you want to delete all

7/27/2019 195157 - Application Log Deletion of Logs

http://slidepdf.com/reader/full/195157-application-log-deletion-of-logs 3/5

7/27/2019 195157 - Application Log Deletion of Logs

http://slidepdf.com/reader/full/195157-application-log-deletion-of-logs 4/5

17.01.2013 Page 4 of 5

SAP Note 195157 - Application log: Deletion of logs

Archiving logs:

-------------------------------------------------------------------

o As of Release 6.20, it has been possible to archive logs.

The logs are archived via archiving object BC_SBAL.

The archiving programs are started via Transaction SARA (archive

administration).

Via Support Packages, the archiving of application logs has been

made available for Releases 4.6C (SAPKB46C27), 4.6D (SAPKB46D17),

and 6.10 (SAPKB61011) as well.

Header Data

Release Status: Released for Customer

Released on: 04.08.2005 13:55:45

Master Language: German

Priority: Recommendations/additional info

Category: ConsultingPrimary Component: BC-SRV-BAL Basis Application Log

 Valid Releases

Software Component Release From

Release

To

Release

and

Subsequent

SAP_APPL 30 30F 31I

SAP_APPL 40 40A 40B

SAP_APPL 45 45A 45B

SAP_BASIS 46 46A 46D XSAP_BASIS 60 610 640 X

Related Notes

Number Short Text

1774469 Report showing number of logs per application

1716420 Purge Object RMS_LBL logs render Label sets not maintainable

1009281 LAW: Runtime error CONNE_IMPORT_WRONG_COMP_TYPE

856006 Mass processing saves unnecessary logs

737696 Add. info on upgrade to SAP R/3 Enterprise 4.70 Ext. 2 SR1

706478 Preventing Basis tables from increasing considerably

637683 Add info about upgrade to SAP R/3 Enterprise Core 4.70 Ext 2

587896 Add. info on upgrade to SAP R/3 Enterprise Core 4.70 SR1

540019 Report RJBTPRLO does not work correctly

400687 Delete application log: DBIF_RSQL_INVALID_CURSOR

390062 Additional information about upgrading to 4.6C SR2

370601 Composite SAP note: APO 3.0 and 3.1 performance

365602 M/AM: Sales agent determination log - perf.

327285 Additions to upgrade to 4.6C SR1

183960 ALE: Deactivating application logs for data transfers

7/27/2019 195157 - Application Log Deletion of Logs

http://slidepdf.com/reader/full/195157-application-log-deletion-of-logs 5/5

17.01.2013 Page 5 of 5

SAP Note 195157 - Application log: Deletion of logs

Number Short Text

141244 Deactivating the application log during data transfer

138715 RSSLGK90: Too many lock entries in the database

118314 Installing the interface to a separate EH&S

91519 Deleting logs of the application log

 Attributes

Attribute Value

Transaction codes BALC

Transaction codes BALM

Transaction codes CLEAR

Transaction codes HIER

Transaction codes SARA

Transaction codes SLG2

Correction Instructions

Correcti

on

Instruct

ions

Valid

from

Valid

to

Software

Component

Typ

e

*)

Reference

Correction

Last

Changed

158903 30F 30F SAP_APPL C 16.05.2000

09:13:51

162069 31H 45B SAP_APPL C 16.05.2000

09:17:15

*) C Correction, B Preprocessing, A Postprocessing, M Undefined Work