ATG BCC SnapShot Issue

SnapShot are maintained against the each deployment server. A Successful deployment is treated as Snapshot. Snapshot issue occurs during following scenarios.
1. Previous deployment wasn't successful
2. No installed snapshots found against server (DB Change).

Its rare scenario when Site is live. 

Screen of admin console looks during snapshot issue.



To resolve the Above Issue, try the following steps. Following case explains for Staging(Preview) server.

1. Query the following in Publishing Database.

select epub_target.display_name as "Target",
epub_prj_tg_snsht.snapshot_id as "Snapshot",
epub_project.display_name as "Project" from
epub_target, epub_project, epub_prj_tg_snsht
where
epub_prj_tg_snsht.project_id in
(select project_id from epub_project where
workspace is not null and
checked_in = '1'
) and
epub_target.target_id = epub_prj_tg_snsht.target_id and
epub_prj_tg_snsht.project_id = epub_project.project_id
order by epub_project.checkin_date desc;

2. Fetch the recent snapshot for the corresponding server(Staging or Production)



3.  Initialise the same in Deployment Server from dyn/admin of Publishing.

http://<publishing server IP address>:<Pub-port>/dyn/admin/nucleus/atg/epub/DeploymentServer/)



4. Similar steps, if the snapshot issue occurs for Production server.

 

Read More