How To Fix SDRB034 - Setting was saved but is not supported by database

SAP Error Message - Details

• Message type: E = Error

• Message class: SDRB - Document Relationship Browser

• Message number: 034

• Message text: Setting was saved but is not supported by database

What causes this issue?

The saved settings are ignored because the database does not support
data aging.

System Response

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

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SDRB034 - Setting was saved but is not supported by database ?

  The SAP error message SDRB034: "Setting was saved but is not supported by database" typically occurs when there is a mismatch between the settings or configurations in the SAP system and what the underlying database can support. This can happen for various reasons, including:
  Causes:
  
  Database Compatibility: The settings you are trying to save may not be compatible with the version or type of database you are using (e.g., Oracle, SQL Server, HANA).
  Configuration Issues: There may be configuration settings in the SAP system that are not supported by the database, such as certain data types or features.
  Version Mismatch: The SAP application version may not be fully compatible with the database version, leading to unsupported settings.
  Custom Development: If there are custom developments or enhancements in the system, they may introduce settings that the database cannot handle.
  
  Solutions:
  
  Check Database Compatibility: Verify that the settings you are trying to save are supported by your database version. Consult the SAP documentation for compatibility matrices.
  Review Configuration Settings: Go through the configuration settings in the SAP system to ensure they align with what the database can support. This may involve checking data types, field lengths, and other parameters.
  Update Database or SAP Version: If there is a version mismatch, consider updating either the SAP application or the database to a version that is compatible with the settings you are trying to save.
  Consult SAP Notes: Search for relevant SAP Notes that may address this specific error. SAP Notes often provide fixes or workarounds for known issues.
  Check for Custom Code: If there are custom developments, review the code to ensure it does not introduce unsupported settings. You may need to modify or remove certain customizations.
  Contact SAP Support: If the issue persists, consider reaching out to SAP Support for assistance. They can provide more specific guidance based on your system configuration and the error message.
  
  Related Information:
  
  SAP Documentation: Always refer to the official SAP documentation for your specific version and database type for detailed compatibility information.
  SAP Community: The SAP Community forums can be a valuable resource for finding similar issues and solutions shared by other users.
  System Logs: Check the system logs (transaction codes like SLG1) for additional error messages or warnings that may provide more context about the issue.
  
  By following these steps, you should be able to identify the cause of the error and implement a suitable solution.