How To Fix DB6PM860 - Table reorganization on table &1 is already running

SAP Error Message - Details

• Message type: E = Error

• Message class: DB6PM - DB2 UDB for UNIX, Windows: Performance Monitoring

• Message number: 860

• Message text: Table reorganization on table &1 is already running

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 DB6PM860 - Table reorganization on table &1 is already running ?

  The SAP error message DB6PM860 indicates that a table reorganization process for a specific table (denoted as &1) is already in progress. This error typically occurs when a reorganization operation is attempted on a table that is currently being reorganized, which can lead to conflicts and potential data integrity issues.
  Cause:
  
  
  Concurrent Reorganization: The most common cause is that a reorganization job for the specified table is already running. This can happen if:
  
  A previous reorganization job has not completed yet.
  Multiple jobs are scheduled to run simultaneously on the same table.
  
  
  
  Long-running Processes: If the reorganization process takes longer than expected due to large data volumes or system performance issues, it may lead to this error.
  
  
  System or Job Scheduling Issues: Sometimes, job scheduling conflicts or misconfigurations can lead to attempts to reorganize the same table multiple times.
  
  
  Solution:
  
  
  Check Running Jobs: 
  
  Use transaction codes like SM37 (Job Monitoring) to check if there is an active job for the reorganization of the specified table.
  If a job is running, you may need to wait for it to complete.
  
  
  
  Cancel or Reschedule Jobs: 
  
  If you find that a job is stuck or taking too long, you may consider canceling it (if appropriate) and then rescheduling the reorganization job after ensuring that no other jobs are running on the same table.
  
  
  
  Review Job Scheduling: 
  
  Ensure that your job scheduling does not allow for overlapping reorganization jobs on the same table. This can be managed by setting appropriate job dependencies or scheduling times.
  
  
  
  Monitor System Performance: 
  
  If reorganization jobs are frequently taking too long, consider reviewing system performance and database tuning to improve the efficiency of these operations.
  
  
  
  Consult SAP Notes: 
  
  Check for any relevant SAP Notes or documentation that may provide additional insights or patches related to this error.
  
  
  
  Related Information:
  
  Reorganization Process: In SAP, table reorganization is a process that helps to optimize database performance by reclaiming space and improving access times.
  Database Administration: Regular monitoring and maintenance of database jobs are crucial for ensuring that reorganization and other database tasks do not conflict.
  Transaction Codes: Familiarize yourself with transaction codes like DB02 (Database Performance Monitor) and DB13 (Database Administration) for monitoring and managing database activities.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.