How To Fix NSDM_MIG_CONTROL068 - Exception occurred when creating packages for aggregate &1 (p. size &2)

SAP Error Message - Details

• Message type: E = Error

• Message class: NSDM_MIG_CONTROL - Log message for migration

• Message number: 068

• Message text: Exception occurred when creating packages for aggregate &1 (p. size &2)

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 NSDM_MIG_CONTROL068 - Exception occurred when creating packages for aggregate &1 (p. size &2) ?

  The SAP error message NSDM_MIG_CONTROL068 typically occurs during the data migration process, particularly when creating packages for aggregates in the SAP system. This error can arise due to various reasons, and understanding the cause is essential for finding a solution.
  Cause:
  
  Data Volume: The size of the data being processed may exceed the limits set for the package size, leading to an exception.
  Configuration Issues: Incorrect configuration settings in the data migration or aggregation process can lead to this error.
  System Performance: Insufficient system resources (like memory or processing power) can cause failures during the package creation.
  Data Integrity Issues: Problems with the data itself, such as inconsistencies or corruption, can lead to errors during processing.
  Locking Issues: If the data being processed is locked by another transaction, it may cause the package creation to fail.
  
  Solution:
  
  Check Package Size: Review the package size settings and adjust them if necessary. Ensure that the package size is within acceptable limits for your system.
  Review Configuration: Verify the configuration settings related to data migration and aggregation. Ensure that all parameters are set correctly.
  Monitor System Resources: Check the system's performance metrics (CPU, memory, etc.) during the migration process. If resources are low, consider optimizing the system or running the migration during off-peak hours.
  Data Validation: Perform data validation checks to ensure that the data being processed is consistent and free from corruption.
  Check for Locks: Use transaction codes like SM12 to check for any locks on the data being processed. If locks are found, resolve them before retrying the migration.
  Error Logs: Review the error logs for more detailed information about the exception. This can provide insights into the specific cause of the error.
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  SM37: To check job logs and see if there are any related errors.
  ST22: To check for dumps that may provide more context on the error.
  SLG1: To view application logs that might contain additional details about the error.
  
  
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide patches and updates.
  
  
  Documentation: Review SAP documentation related to data migration and aggregation processes for best practices and troubleshooting steps.
  
  
  If the issue persists after trying the above solutions, consider reaching out to SAP support for further assistance, providing them with detailed information about the error and the steps you have already taken.