Kontakt

Ansicht
Dokumentation

ABENDDIC_DATABASE_TABLES_PROTOCOL - DDIC DATABASE TABLES PROTOCOL

ABENDDIC_DATABASE_TABLES_PROTOCOL - DDIC DATABASE TABLES PROTOCOL

PERFORM Short Reference   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

- Logging Database Tables

If logging is activated, any changes to table entries in are logged in the log table DBTABLOG. This also requires the profile parameter rec/client to be set accordingly. This profile parameter can have the following values:

  • ALL
Logging is client-independent.
  • clnt1, clnt2, ...
Changes are logged only in the specified clients clnt1, clnt2, ...
  • OFF
No logging.

The logs can be evaluated using the transaction Table History (transaction SCU3). Logging is independent of updates.

If a table row has more than 16000 bytes, logging is not possible for the table. The lengths of fields with the built-in types STRING, RAWSTRING, LCHR, LRAW, and GEOM_EWKB are counted completely here.

Notes

  • If logging is activated, access to the DDIC database table slows down accordingly. If logging is activated for many DDIC database tables, lock situations can occur for the log table.
  • No data can be written to a DDIC database table with enabled logging using the statement INSERT with subquery.
  • The documented method IS_LOGGING_ON of the system class CL_DBI_UTILITIES can be used to check whether logging is currently switched on for a DDIC database table.





BAL_S_LOG - Application Log: Log header data   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 2257 Date: 20240426 Time: 114851     sap01-206 ( 41 ms )