How To Fix CODAC_ODH_MESSAGES003 - Memory size for Obsolete Table &1 and Table &2 could not be calculated

SAP Error Message - Details

• Message type: E = Error

• Message class: CODAC_ODH_MESSAGES - Message class to capture Obsolete Data Handling messages

• Message number: 003

• Message text: Memory size for Obsolete Table &1 and Table &2 could not be calculated

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message CODAC_ODH_MESSAGES003 - Memory size for Obsolete Table &1 and Table &2 could not be calculated ?

  The SAP error message "CODAC_ODH_MESSAGES003 Memory size for Obsolete Table &1 and Table &2 could not be calculated" typically indicates an issue related to the calculation of memory size for obsolete tables in the SAP system. This error can arise in various contexts, often related to data management, archiving, or system performance.
  Cause:
  
  Obsolete Tables: The error suggests that the system is trying to calculate memory size for tables that are considered obsolete. This could be due to data that has been archived or deleted but still has references in the system.
  Database Issues: There may be inconsistencies or corruption in the database that prevent the system from accessing the necessary metadata for the tables.
  Configuration Issues: Incorrect configuration settings in the SAP system related to data management or archiving could lead to this error.
  System Performance: If the system is under heavy load or if there are resource constraints, it may fail to perform the necessary calculations.
  
  Solution:
  
  Check Table Status: Verify the status of the tables mentioned in the error message. Ensure that they are indeed obsolete and that there are no lingering references to them in the system.
  Database Consistency Check: Run a consistency check on the database to identify and resolve any issues. This can often be done using transaction codes like DB02 or DBACOCKPIT.
  Update Statistics: Ensure that the database statistics are up to date. This can help the system better manage memory and optimize performance.
  Review Configuration: Check the configuration settings related to data management and archiving. Ensure that they are set correctly and that there are no conflicts.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error. There may be patches or updates available that resolve the issue.
  Consult Documentation: Review the SAP documentation related to the specific module or functionality that is generating the error for additional troubleshooting steps.
  Contact SAP Support: If the issue persists after trying the above solutions, consider reaching out to SAP Support for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE11 (Data Dictionary), SE14 (Database Utility), and SM37 (Job Monitoring) to help diagnose the issue.
  Performance Monitoring: Use tools like ST03N (Workload Analysis) and ST22 (Dump Analysis) to monitor system performance and identify any related issues.
  Archiving Strategy: Review your archiving strategy to ensure that obsolete data is being handled correctly and that the system is not trying to access unnecessary tables.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.