How To Fix DHCDC_CORE035 - Subscriber logging table for application table &1 has too many records

SAP Error Message - Details

• Message type: E = Error

• Message class: DHCDC_CORE -

• Message number: 035

• Message text: Subscriber logging table for application table &1 has too many records

What causes this issue?

The subscriber logging table for application table &V1& has too many
records (&V2&). Possible causes include:
+,,One or more subscribers have not retrieved captured changes, so the
subscriber logging table cannot be properly cleaned up.

System Response

If the logging table continues to grow and reaches the configured
records limit, then the system will delete captured changes for inactive
subscribers.

How to fix this error?

Check whether the subscribers are active and running correctly, and that
the remote system is running correctly.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message DHCDC_CORE035 - Subscriber logging table for application table &1 has too many records ?

  The SAP error message DHCDC_CORE035 indicates that the subscriber logging table for a specific application table has exceeded the maximum number of records allowed. This can occur in systems that utilize the Data Hub or similar data replication technologies, where subscriber logging is used to track changes to application tables.
  Cause:
  
  High Volume of Changes: The application table is experiencing a high volume of changes, leading to an accumulation of records in the subscriber logging table.
  Retention Policy: The retention policy for the logging table may not be configured correctly, allowing too many records to accumulate without being purged.
  Configuration Issues: There may be misconfigurations in the data replication settings that prevent the proper management of the logging table.
  
  Solution:
  
  Purge Old Records: Implement a process to regularly purge old records from the subscriber logging table. This can often be done through a scheduled job or a manual cleanup process.
  Adjust Retention Settings: Review and adjust the retention settings for the logging table to ensure that it only retains records for a necessary period.
  Monitor Changes: Set up monitoring to track the volume of changes to the application table and the growth of the logging table. This can help in identifying trends and potential issues before they lead to errors.
  Increase Capacity: If the volume of changes is expected to remain high, consider increasing the capacity of the logging table, if possible, or optimizing the data replication process to reduce the number of records generated.
  Review Configuration: Check the configuration settings for the data replication and subscriber logging to ensure they are set up correctly and efficiently.
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like SLG1 (Application Log) to check for logs related to the error and DB02 to monitor database performance and table sizes.
  SAP Notes: Look for relevant SAP Notes that may provide additional guidance or patches related to this error.
  Documentation: Review SAP documentation on data replication and subscriber logging for best practices and configuration guidelines.
  
  If the issue persists after implementing these solutions, it may be beneficial to consult with SAP support or your system administrator for further assistance.