CMS Application - Execute - Fatal Error - Snapshot already in progress or processing

Description

On running the analysis/snapshot,it shows the following error

Snapshot is already in progress

Observed in CAST AIP

Observed on RDBMS

Step by Step Scenario

1. Run the Snapshot/Analysis
2. Check the error:Snapshot already in progress or is already processing

Action Plan

1. The full error is normally one of the following:

   1. Invalid Snapshots: A snapshot computation is already in progress on this central site. The dashboard service is locked. Cannot define and compute a new snapshot.
   2. Error: Cannot generate Snapshot. Snapshot is already processing

2. When getting this error, do the following:

   1. Synchronize the central base for your application using as shown below so that you can see the unfinished Snapshots.
      1. Go to Execute Tab in CMS and double click on the Central service configured for the Application:
         1. 
      2. Double click the Central, now synchronize the Central db and check for the snapshots available and see if you were able to find the latest snapshot that was run:
         1. 
      3. If it’s there, then delete it from CMS and launch a new snapshot.

3. An alternative approach would be to run the following query to purge the snapshot on the appropriate snapshot in process to stop it:

   1. set search_path=;

   2. select dss_purge_snapshot(-1);

      1. The snapshot normally has a snapshot_status of -1, but in some cases, it could have a snapshot_status of 1.  When this occurs, then run the following instead:
         1. select dss_purge_snapshot(1);

4. If this doesn’t work, an alternative approach is to do the following:

   1. In pgAdmin,run the following query

Set search_path=<central_basename>   SELECT snapshot_id FROM dss_snapshots WHERE snapshot_status = -1

   2. Check that the result of the query returns -1 as status.
   3. If there is no other snapshots in progress on the database, then run the below query

      ```java
UPDATE dss_snapshots 
SET    snapshot_status=2 
WHERE  snapshot_id=<snapshot_id>

4. Now connect to CAST-MS and run the snapshot.
5. There may be some cases where instead of a snapshot_status of -1, the snapshot_status is 1, so the steps above should be done for snapshot_status of 1 instead of -1.
6. If  the problem you are facing does not match any case listed in this page, contact CAST Technical Support with the following relevant input.

Impact on Analysis Results and Dashboard

Notes/comments

Related Pages

Ticket # 1637, 22672