--- schema_version: "1" id: 415415187f048ce42bb6c0235c866d7952454ec53a23d9086ef978cac68c1532 title: Troubleshooting Replication in B2C Commerce collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/cc/264-0-0/b2c_troubleshooting_replication.md canonical_url: https://help.salesforce.com/s/articleView?id=cc.b2c_troubleshooting_replication.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: d9d8c82c6a88daf94ed9e8bb567df4e197ae332fb284f0f4aafec323fdc58e93 description: These tips can help you troubleshoot some common replication issues. products: - Commerce - B2C Commerce release: "264" --- # Troubleshooting Replication in B2C Commerce These tips can help you troubleshoot some common replication issues. ## Monitoring Replication Status To check the status of a replication process, click App Launcher ![App Launcher](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/cc/b2c_merchandiser_administrator/images/appLauncher.png), and then select **Administration** | **Replication** | **Code Replication** or **Administration** | **Replication** | **Data Replication** and find it in the list. . ## Replication Logs The replication process records log files on both the source and target systems, separately from the regular error logs. They exist in https://instance\_address/on/demandware.servlet/webdav/Sites/Logs/, with filenames like staging-blade\_name\-appserver-yyyymmdd.log To view the log files in Business Manager, click App Launcher ![App Launcher](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/cc/b2c_merchandiser_administrator/images/appLauncher.png), and then select **Administration** | **Site Development** | **Development Setup** | **Log Files**. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-cc-b2c_merchandiser_administrator-264-0-0-production-enus/ea76f372-6cfa-42a6-8e7c-05c6df7abed8/images/icon_note.png) Note All the log file names contain "staging", regardless of the instance type. ## Hung Replication Some database transactions, especially those involving catalog data, can take a while to complete depending on the amount of data involved. If the replication remains in the running state for longer than expected, check whether it’s hung. - Open the most recent replication log on the staging instance. - Check whether it contains the line "Staging pipeline in live system successfully called." If it doesn't, there’s a problem. - Check whether it includes an entry that a state is set to "ErrorAcquiringEditingLocks." If so, it’s possible that resource locks from a previous replication process weren’t released, which can hang the replication. - Open the most recent replication log on the target instance, and scroll to the end. - Refresh the view a few times to determine whether new entries are being added. If no new entries appear after a while, the replication can be hung. - Check whether it includes an entry that a state is set to ErrorAcquiringLivelocks. If so, it’s possible that resource locks from a previous replication process weren’t released, which can hang the replication. - If the last log entry is a database action (for example, INSERT or ALTER INDEX), check earlier logs. Examine how long that action usually takes and what log entries usually follow it. - If the last log entry starts with Rsync, the delay can be due to a large number of changed static content files. Files that have been moved to a different folder are included, even if their content is the same. If the Rsync is stuck, contact Support to check its status. - If the log shows the state ErrorLiveStagingProcessKilled, the replication is probably hung due to a concurrent deployment or instance restart. - If either log contains a line with something similar to "resource busy and acquire with NOWAIT specified," open a ticket with Support. In the ticket, provide the troubleshooting steps that you’ve attempted. - If the replication process shows completed on the target instance but is still waiting or in progress on staging, check the staging instance. It can have been down when the replication finished. Restart the staging instance, and check the status again. If you determine that the replication is hung, use Control Center to restart the staging instance. To verify that the hung replication has stopped, confirm that its status on the staging instance is Failed. When it has stopped, rerun the replication. If the replication hangs again, try restarting the target instance, then restarting the source instance, then rerunning the replication. However, restarting the target instance disrupts all running jobs, returns errors for all storefront requests, and clears all caches. Restart a production instance only as a last resort. If the replication still hangs, open a Support ticket and provide the troubleshooting steps that you’ve attempted. ## Post-Replication Issues If you encounter a problem after a data replication operation, take the following steps. - Examine the replication logs on the staging and target instances for error messages. Look for entries that include "failed" or "ORA-". These messages can help determine the problem. - If the replication logs don’t provide helpful data, check the error logs. - To isolate the replication task that caused the problem, run tests with and without each task. - If replication of multiple objects fails, try replicating individual objects to narrow the cause. - If a scheduled replication didn’t run, try to run it manually.