2021-10-11 195157
195157 - Application log: Deletion of logs
Version 29 Type SAP Note
Language Anglais Master Language Anglais
Priority Recommendations / Additional Info Category Consulting
Release Status Released for Customer Released On 22.07.2019
Component BC-SRV-BAL ( Basis Application Log )
Please find the original document at https://launchpad.support.sap.com/#/notes/ 195157
Symptom
At least one of the database tables of the application log contains too many
entries.
The following are database tables of the application log:
- BALHDR
- BALDAT
- BAL_INDX
Other Terms
SLG2
SLGD (SLG1)
Application log
Logs
Delete, deletion
Appl. log
App log
Performance
Reason and Prerequisites
The application log is a tool for writing, saving, and displaying logs. Many
different applications write messages containing information for end users in
the application log. The application log is for the temporary storage of
messages. The logs are written to the database but are not automatically deleted
(except Cloud environment, Note 2623826 ).
There is no general procedure for activating or deactivating the application
log. Some applications offer this option individually or allow you to reduce the
number of generated entries. (See SAP Notes 91519, 183960, and 141244.)
Expiration date of application logs
Normally, a log has an expiration date ALDATE_DEL that is set by the application
that calls the application log tool. If the application does not set an
expiration date, the application log tool sets the expiration date DEC/31/2098
or DEC/31/9999 depending on the release. This means that the logs remain in the
system for as long as is possible. The expiration date cannot be set by the end
user. The expiration date does not mean that logs that have reached the
expiration date are automatically deleted. It controls the deletion of logs when
you call the deletion report SBAL_DELETE (transaction SLG2) and during archiving
(archiving object BC_SBAL). The indicator DEL_BEFORE in the table BALHDR
determines whether or not a log is allowed to be deleted or archived before the
expiration date is reached.
DEL_BEFORE = SPACE means that the log is allowed to be deleted or archived
© 2021 SAP SE or an SAP affiliate company. All rights reserved 1 of 6
2021-10-11 195157
before the expiration date is reached. This is the default value. To delete
these logs, choose the option "and logs which can be deleted before the expiry
date" in the deletion report.
DEL_BEFORE = X means that the log is only allowed to be deleted or archived once
the expiration date has been reached. The applications that created the logs in
question are responsible for the deletion or archiving of these logs if this
should be necessary (particularly if the expiration date is DEC/31/9999).
Solution
Deletion of application logs
You can make a selection of the logs to be deleted on the selection screen:
• The "Object" and "Subobject" fields denote the application area that has
written the logs (see the input help).
• The "External Identification" field specifies the number assigned to the log
by the application.
• To delete logs whose expiration date has not been reached, too, you have to
select the "and logs which can be deleted before the expiry date" checkbox.
For more information on the deletion procedure, read the application help in
transaction SLG2.
SLG2 is a report transaction. The corresponding report is SBAL_DELETE. This
report can be scheduled as a background job at regular intervals.
Remarks
• We strongly recommend regular execution of SBAL_DELETE in the background job with
suitable variant (eg: all logs that have reached their expiration date).
• If you delete a lot of logs (for example, the first time you execute the
report), we recommend that you distribute the deletion procedure to multiple
background jobs to enable parallel processing and improved resource
planning. Select the "Only calculate how many" checkbox in the deletion
report to obtain a proposal for the distribution. You can use the displayed
log number intervals as an additional selection criterion (one interval per
background job). You can also define the distribution on the basis of the
object, subobject, or creation date, for example.
Client-dependency
Note that the application log tables are client-dependent. The deletion of the
data must therefore take place in each client.
Applications that generate entries in the application log
You can use the report SBAL_OBJECT_RECORDS_COUNT (see SAP Note 1774469),
SBAL_STATISTICS (Note 2524124 - Application log Statistics ) to determine the
number of logs for each client/object/subobject or to get detailed statistics.
Alternatively, you can use transaction SE16 or TAANA to investigate the table
BALHDR (fields OBJECT and SUBOBJECT).
For the text description for the object, see the table BALOBJT (subobject in
BALSUBT) or transaction SLG0. As a rule, the application can be derived from the
name and text of the object. You can use transaction SLGD to count, display or
SLG1 to display the logs (see SAP Note 1746757). You can restrict the display to
certain objects, among other things.
Restriction of log data quantity by application
Refer to the following SAP Notes for various applications to avoid large log
© 2021 SAP SE or an SAP affiliate company. All rights reserved 2 of 6
2021-10-11 195157
volumes:
- 91519
- 183960
- 141244
Archiving logs
The archiving of logs is possible as of Release 6.20.
The logs are archived using the archiving object BC_SBAL.
You start the archiving programs using transaction SARA ("Archive
Administration").
The archiving of application logs is made available for Release 4.6C
(SAPKB46C27), 4.6D (SAPKB46D17), and 6.10 (SAPKB61011), too, by means of Support
Packages.
Software Components
Software Component Release
SAP_APPL 30F - 31I
SAP_APPL 40A - 40B
SAP_APPL 45A - 45B
SAP_BASIS 46A - 46D
SAP_BASIS 610 - 640
Correction Instructions
Software Component From To Version Changed on ID
SAP_APPL 31H 45B 1 16.05.2000 07:17:15 0000162069
SAP_APPL 30F 30F 2 16.05.2000 07:13:51 0000158903
This document refers to
SAP Note/KBA Title
91519 Deleting logs of the application log
872388 Troubleshooting Archiving and Deletion in PI
856006 Mass processing saves unnecessary logs
© 2021 SAP SE or an SAP affiliate company. All rights reserved 3 of 6
2021-10-11 195157
737696
706478 Preventing Basis tables from increasing considerably
637683
587896
540019 Report RJBTPRLO does not work correctly
440670
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
2623826 Application log: deletion of logs in SAP Cloud systems
2524124 Application log Statistics
1881405 Log entries are not deleted
183960 ALE: Deactivating application logs for data transfers
1774469 Report showing number of logs per application
1716420 Purge Object RMS_LBL logs render Label sets not maintainable
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
1009281 LAW: Runtime error CONNE_IMPORT_WRONG_COMP_TYPE
This document is referenced by
SAP
Title
Note/KBA
3039724 BALHDR and BALDAT: Application Log tables size increases [FAQ]
3037557 SBAL_DELETE report is canceled with runtime error DBSQL_INVALID_CURSOR
2936391 Dynamic variant to remove logs with SBAL_DELETE
2458005 Dump DBIF_RSQL_INVALID_RSQL/ DBSQL_TOO_MANY_OPEN_CURSOR occurs at program
© 2021 SAP SE or an SAP affiliate company. All rights reserved 4 of 6
2021-10-11 195157
SBAL_DELETE
2192622 CHARM Change Documents missing Messages data in the Application Log
2707974 Variant <Variant_name> of program SBAL_DELETE is not the current version
2622757 Error BL043 occurs when using transaction SLG2 to delete application logs
2601011 Delete errors in the Application Log - SLT
2507213 SBAL_DELETE runs too long
2386402 Error Message BL252 is issued in T-code VA88 with background processing
3025511 FRUN: EarlyWatch Alert: Expiration time for Appl Log Messages
81906 Error analysis for transactions 1KEH,1KEI,1KEJ, and 1KEK
2740654 BCS: SAPconnect Trace moved to Application Log
2623826 Application log: deletion of logs in SAP Cloud systems
2278583 SLG2 missing program documention (Shift+ F1)
2057897 Application Log: orphan records in BALDAT
1991143 Purge Object RMS_LBL logs render Label sets not maintainable
1955339 RESCIS: Error log not displayed
872388 Troubleshooting Archiving and Deletion in PI
1881405 Log entries are not deleted
706478 Preventing Basis tables from increasing considerably
1774469 Report showing number of logs per application
1716420 Purge Object RMS_LBL logs render Label sets not maintainable
1265367 Performance Analysis Checklist cProjects 4.0 / 4.5
400687 Delete application log: DBIF_RSQL_INVALID_CURSOR
856006 Mass processing saves unnecessary logs
1009281 LAW: Runtime error CONNE_IMPORT_WRONG_COMP_TYPE
390062 Additional information about upgrading to 4.6C SR2
327285 Additions to upgrade to 4.6C SR1
595856 Frame log is stored although not required
370601 Composite SAP note: APO 3.0 and 3.1 performance
118314 Installing the interface to a separate EH&S
© 2021 SAP SE or an SAP affiliate company. All rights reserved 5 of 6
2021-10-11 195157
540019 Report RJBTPRLO does not work correctly
141244 Deactivating the application log during data transfer
183960 ALE: Deactivating application logs for data transfers
91519 Deleting logs of the application log
138715 RSSLGK90: Too many lock entries in the database
365602 M/AM: Sales agent determination log - perf.
Attachments
File Name File Size Mime Type
callstack_SBAL_SVER_04.JPG 288 image/pjpeg
Terms of use | Copyright | Trademark | Legal Disclosure | Privacy
© 2021 SAP SE or an SAP affiliate company. All rights reserved 6 of 6
