You must delete logs to avoid Application Log database table overflow.
You can delete logs in dialog () or in the background ( ).
You have the following options:
General selection conditions
Only calculate number The system only calculates the number of logs that can be deleted. The data is not read from the database.
Create list The system creates a list of all logs that can be deleted. You can then decide which logs to delete.
Delete immediately The system deletes all logs from the database that satisfy the selection conditions.
A log can only be deleted when it has expired (reached or passed its expiry date). However, you can delete logs before their expiry date if they have the "Delete before expiry" attribute.
Choose transaction SLG2. You go to the dialog box Application Log: Delete Obsolete Logs .
Select the appropriate radio button under Expiry Date .
Specify Selection Conditions .
Choose the relevant Options .
Choose Execute . The logs are deleted from the database.
To delete logs in the background, choose the Delete Immediately option - otherwise only the number or list of deletable logs is output.
If you want to delete logs from the database, due to storage space and runtime considerations, but still want to keep the data, you can archive the logs. A log can only be archived if it has either expired (expiration date has been reached or has passed) or if the log permits a deletion before the expiration date.
Logs are archived using archiving object BC_SBAL.
The log header data, as well as the message data itself, is stored.
The archiving programs, SBAL_ARCHIVE and SBAL_ARCHIVE_DELETE, are integrated and documented in the Archive Development Kit (ADK). For more information, see Data Archiving (CA-ARC) Data Archiving (ADK).
You start archive administration with transaction code SARA .