How to resolve snapshot mismatch error in BCC

This issue is known for ATG BCC you can get it from bellow link which says why it comes and how to resolve, may be in this article you will find some different approach to solve this.

https://forums.oracle.com/forums/thread.jspa?threadID=2338829

Please follow these bellow steps:-

1. Open <BCC Domain>/dyn/admin (i.e. http://130.29.237.176:8100/dyn/admin)

Enter credential required and click on “JDBC Browser” link

2. Click on Execute query link

3. In query box write this below query and then execute.Select * from epub_PRJ_TG_SNSHT ORDER BY to_number(SNAPSHOT_ID) DESC

You will see this below page which shows two targets (i.e. tar64 and tar66) repeatedly one target_id will be for Staging and second will be for Production, in just few next sections you will get to know how you can identify the environment’s target id.

4. Click on admin link

Enter query here

Click on it

5. Click on “Component Browser” link

6. Click on Search link and enter the name of component name (i.e. DeploymentServer) in search box and press enter.

7. Click on component link

8. Upon clicking the above component link you will get this below page which is showing snapshot id for both environment (i.e. Staging and Production).For environment you get the snapshot issue, in this page you will get UNINITIALIZED text instead of Current installed agent snapshot and Current effective snapshot.In first screen shot it says clearly in which environment snapshot mismatch error is coming.

From these below screen you can get to know which target_id is for which environment, like in this case you can easily get to know that tar66 is for Staging and tar64 is for Production.

For the environment you’re getting snapshot issue please copy SNAPSHOT_ID from ResultSet screen and paste it into the corresponding Force snapshot id entry box and click on Init button next the box.