Loading

Troubleshooting Data Replication in B2C Commerce

Julkaisupäivä: Nov 19, 2025
Kuvaus

This article covers both Staging-to-Production and Staging-to-Development replication troubleshooting in B2C Commerce.

 

  • The first step is to monitor the job status of the data replication process on the Staging instance since it is the source instance. If it fails, the next step to take is to look into the staging logs for messages regarding the failure.

  • Check the staging logs on the Staging instance first. And then check the most recent staging-blade-yyyymmdd.log file. Many times a single staging log will contain several days worth of staging events in one file.

https://<staging instance name>/on/demandware.servlet/webdav/Sites/Logs 

  • Check the beginning of the replication process in the logs. It'll have a similar timestamp to the data replication task you started:
(individual tasks created in business manager)
 
[2007-01-15 21:17:12.848 GMT] ISH-CORE-2250: New replication task "1168895828901" in domain "Sites-Site" successfully created.
[2007-01-15  21:18:34.171 GMT] ISH-CORE-2250: New replication task "1168895910472"  in domain "Sites-YourStore" successfully created.
[2007-01-15  21:21:13.574 GMT]  ===================================================================================================
[2007-01-15 21:21:13.574 GMT] ReplicationPublication process created.
[2007-01-15 21:21:13.575 GMT] Start date: Mon Jan 15 21:21:12 GMT 2007
[2007-01-15 21:21:13.575 GMT] TargetSystem: Production (http://216.75.207.174:80)
[2007-01-15 21:21:13.575 GMT] Process uuid: bcvh6iaalTxJYaaacowN3YFqCG)
[2007-01-15 21:21:13.575 GMT] --------------------------------------------
 
  • From this point, scroll down through the log file and you'll see the job. Go through the steps, such as gathering stats for all tables:
[2007-01-15  21:27:06.602 GMT] ISH-CORE-2070: SQL (64ms, rows=1): begin  dbms_stats.gather_table_stats(user, 'PRODUCTOPTION_AV$1', method_opt  => 'for all indexed columns', cascade => TRUE); end;
[2007-01-15  21:27:06.654 GMT] ISH-CORE-2070: SQL (52ms, rows=1): begin  dbms_stats.gather_table_stats(user, 'PRODUCTOPTION$1', method_opt =>  'for all indexed columns', cascade => TRUE); end;
[2007-01-15  21:27:06.826 GMT] ISH-CORE-2070: SQL (171ms, rows=1): begin  dbms_stats.gather_table_stats(user, 'BUNDLEASSIGNMENT$1', method_opt  => 'for all indexed columns', cascade => TRUE); end;
[2007-01-15  21:27:06.869 GMT] ISH-CORE-2070: SQL (43ms, rows=1): begin  dbms_stats.gather_table_stats(user, 'PRODUCTOPTIONPRICE_AV$1',  method_opt => 'for all indexed columns', cascade => TRUE); end;
[2007-01-15 21:27:06.869 GMT] ISH-CORE-2067: Starting new transaction...
[2007-01-15 21:27:06.872 GMT] ISH-CORE-2069: Commit transaction.
[2007-01-15 21:27:06.882 GMT] ISH-CORE-2067: Starting new transaction..
 
  • Next you'll see the rsynch running, which gets the actual file system directories ready for copying to the target instance (Development or Production):
[2007-01-15 21:27:08.317 GMT] StagingGroup: Site specific content search index (Relative directory: search/content)
[2007-01-15  21:27:08.317 GMT] ISH-CORE-2486: Synchronize Files of unit  'Sites-YourStore-Site' in site 'Sites-YourStore-Site' to exchange  directory at '/remote/aaas/staging/stg'.
[2007-01-15 21:27:08.318  GMT] Executing command: /build/2.0.0/system/bin/synchronize.sh  /remote/aaas/aaas_stg/sharedata/sites/Sites-YourStore-Site/1/search/content/  /remote/aaas/staging/stg/Sites-YourStore-Site/search/content/ ()
[2007-01-15  21:27:08.402 GMT] rsync debug (/usr/bin/rsync -tr --delete  /remote/aaas/aaas_stg/sharedata/sites/Sites-YourStore-Site/1/search/content/  /remote/aaas/staging/stg/Sites-YourStore-Site/search/content/)
[2007-01-15  21:27:08.476 GMT] ISH-CORE-1956: Files in path 'search/content' of site  'Sites-YourStore-Site' are successfully prepared
 
  • The final step on the Staging instance should be a handoff to the target (production server). You'll see the following line in the staging log:
[2007-01-15 21:27:09.783 GMT] Staging pipeline in live system sucessfully called.
 
  • If you don’t see this success message, check for errors such as the following and follow the recommended steps:
ISH-CORE-2491:  Setting state of process with uuid='dC8KAANna1AAAAEOTN9h9md4' from  'StartingStagingProcess' to 'ErrorAcquiringEditingLocks
Ratkaisu
    If any errors are encountered, perform the following steps:
     
    1. Restart the target (PRD or DEV) followed by a restart of the staging instance via control center.

    2. Repeat failed staging process with the same parameters.

    3. If the staging log on the staging env shows no errors, go to production staging log:
      https://<production instance name>/on/demandware.servlet/webdav/Sites/Logs

      Production staging logs will start with a message like the following:
      [2007-01-15  20:29:30.321 GMT] Copy staging process with  uuid=bcFvkiaalTMxMaaaco4bVYFqBX[2007-01-15 20:29:32.347 GMT] Starting  StagingResources-Acquire@Sites-Site

      Then, depending on exactly what you are staging, you'll see the db table copy begin:
      [2007-01-15  20:30:20.296 GMT] ISH-CORE-2070: SQL (123ms, rows=1): INSERT /*+ APPEND  */ INTO CATALOG$1 dest SELECT  CATALOGDOMAINID,ID,TYPECODE,STATUS,PROXYFLAG,STARTMAINTENANCE,ENDMAINTENANCE,POSITION,UUID,OCA,DOMAINID,LASTMODIFIED  FROM CATALOG$S src WHERE src.DOMAINID NOT IN  ('bcIxgiaalXEYQaaacmKaN9rLDa')
      [2007-01-15 20:30:20.665 GMT] ISH-CORE-2070: SQL (369ms, rows=0): TRUNCATE TABLE CATALOGSITEASSIGNMENT$1 REUSE STORAGE
      [2007-01-15 20:30:20.769 GMT] ISH-CORE-2070: SQL (100ms, rows=1): INSERT /*+ APPEND */ INTO CATALOGSITEASSIGNMENT$1

    4. Then after copying, we switch from temp to source tables $2 to $1:
      [2007-01-15  20:35:43.935 GMT] ISH-CORE-2300: <dbms_output> Switching synonym  PRODUCT_AV from PRODUCT_AV$2 to PRODUCT_AV$1...
      [2007-01-15  20:35:43.935 GMT] ISH-CORE-2300: <dbms_output> Switching synonym  DELETEDPRODUCT from DELETEDPRODUCT$2 to DELETEDPRODUCT$1...
      [2007-01-15 20:35:43.935 GMT] ISH-CORE-2300: <dbms_output> Switching synonym PRODUCT from PRODUCT$2 to PRODUCT$1...
      [2007-01-15  20:35:43.935 GMT] ISH-CORE-2300: <dbms_output> Switching synonym  PRODUCTLINK from PRODUCTLINK$2 to PRODUCTLINK$1...
      [2007-01-15  20:35:43.935 GMT] ISH-CORE-2300: <dbms_output> Switching synonym  PRODUCTOPTION from PRODUCTOPTION$2 to PRODUCTOPTION$1

    5. If finished successfully, you'll see the following message at the end of the logs:
      [2007-01-15 21:31:17.434 GMT] ReplicationPublication process finished with state 'StagingProcessCompleted'.
      [2007-01-15 21:31:17.435 GMT] Process uuid: cfbcMiaalTlpoaaado7llYFqCL)
      [2007-01-15 21:31:17.435 GMT] End date: Mon Jan 15 21:31:16 GMT 2007
      [2007-01-15 21:31:17.435 GMT] =======================================
    Knowledge-artikkelin numero

    000391175

     
    Ladataan
    Salesforce Help | Article