Identifying Staging Problems

If Staging problems occur, it helps to isolate problem causes in order to formulate a speedy resolution. See Troubleshooting.
Note: This covers staging from the Staging environment to Production, but the same steps apply to any staging process running from staging to development.
  1. Monitor the job status of the data replication process on the Staging instance.
  2. If it fails, look at the staging logs for failure messages.
  3. Look at the staging logs of the Staging instance first.
  4. Look at the most recent staging log file. A single staging log often contains several days' worth of staging events in one file.
     https://staging.web.customerName.demandware.net/on/
    demandware.servlet/webdav/Sites/Logs 
    This only works with Firefox. Microsoft Internet Explorer isn't supported.
  5. Look for the beginning of the replication process in the logs. It will 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-customerName" 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] --------------------------------------------
  6. Scroll down through the log file. You will see the job go through 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..
  7. Next you will see the rsynch running which gets the actual file system directories ready for copying to the target instance
    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-customerName-Site' in site 'Sites-customerName-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-customerName-Site/1/search/content/
    /remote/aaas/staging/stg/Sites-customerName-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-customerName-Site/1/search/content/ /remote/aaas/staging/stg/Sites-customerName-Site/
    search/content/)
    [2007-01-15 21:27:08.476 GMT] ISH-CORE-1956: Files in path 'search/content' of site 'Sites-customerName-Site' are successfully prepared
  8. The final step on the Staging instance should be a handoff to the target (Production server).  You will see a the following line in the staging log.
    [2007-01-15 21:27:09.783 GMT] Staging pipeline in live system successfully called.
  9. If you don't see this success message, look 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
See Fixing Staging Problems.