How To Fix /CFG/UI_BCW090 - Migration is still running; changes are not allowed.

SAP Error Message - Details

• Message type: E = Error

• Message class: /CFG/UI_BCW -

• Message number: 090

• Message text: Migration is still running; changes are not allowed.

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 /CFG/UI_BCW090 - Migration is still running; changes are not allowed. ?

  The SAP error message /CFG/UI_BCW090 Migration is still running; changes are not allowed typically occurs when there is an ongoing migration process in the system, and the system is preventing any changes to ensure data integrity during this process. This error is often seen in the context of system migrations, upgrades, or when using the SAP Business Configuration (BC) tools.
  Cause:
  
  Ongoing Migration Process: The most common cause is that a migration process is currently active. This could be due to a system upgrade, data migration, or configuration changes that are being applied.
  Locking Mechanism: SAP uses a locking mechanism to prevent changes while a migration is in progress to avoid inconsistencies in the data.
  Long-running Processes: Sometimes, the migration process may take longer than expected due to data volume or system performance issues.
  
  Solution:
  
  
  Check Migration Status: 
  
  Use transaction codes like SM37 to check for any background jobs related to migration that might be running. Look for jobs with a status of "Running" or "Scheduled."
  If you find a job that is stuck or taking too long, you may need to investigate further or consult with your Basis team.
  
  
  
  Wait for Completion: 
  
  If a migration job is running, the simplest solution is to wait for it to complete. Once the migration is finished, the system should allow changes again.
  
  
  
  Cancel or Restart Migration: 
  
  If the migration process is stuck and not progressing, you may need to cancel the job. This should be done with caution and ideally under the guidance of your Basis team or SAP support, as it may lead to data inconsistencies.
  
  
  
  Check for Locks: 
  
  Use transaction SM12 to check for any locks that might be preventing changes. If you find locks that are no longer needed, you can delete them, but ensure that you understand the implications of doing so.
  
  
  
  Consult Documentation: 
  
  Review any relevant SAP notes or documentation related to the migration process you are performing. There may be specific instructions or known issues that could help resolve the situation.
  
  
  
  Contact SAP Support: 
  
  If the issue persists and you cannot determine the cause or resolution, consider reaching out to SAP support for assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SM37 (Job Monitoring), SM12 (Lock Entries), and ST22 (Dump Analysis) for troubleshooting.
  SAP Notes: Check the SAP Support Portal for any notes related to the specific migration process you are using, as there may be updates or patches that address known issues.
  System Logs: Review system logs for any errors or warnings that may provide additional context about the migration process.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.