Oracle ATG — How to correct projects in unknown state in BCC/CA ?

AZ-5 switch at Chrenobyl nuclear power plant — the safety cut-off button employed in 1986 at Chernobyl.

Note: This article was originally published by me here — https://atgkid.blogspot.com/2011/10/how-to-correct-projects-in-unknown.html

Moving above article to medium and adding more details on top of it.

Often deployments will fail due to some reason and even if we use halt deployment, critical reset, cancel/resume button sometimes ATG fails to revert the project to previous state. And because of JVM crash or normal bounce of BCC instance, currently deploying projects will go to unknown state, follow below steps to correct such type of projects.

If BCC instance is bounced while deploying a project to staging

we can get back the project previous state so that we can start from Author state

Invalidate below repository caches
/atg/epub/PublishingRepository/
/atg/epub/version/VersionManagerRepository/

If BCC instance is bounced while deploying a project to production

we can get back the project previous state so that we can redeploy to
production.

Invalidate only /atg/epub/PublishingRepository/

Completely delete a project

To give all conflicting projects

To give all conflicting projects for a particular asset.

For example to find all conflicting projects of category asset cat3484800002

If a deployment is stuck either in staging or production

Invalidate below repository caches
/atg/epub/PublishingRepository/

To know project deployment duration

Finding all the items which got modified in ATG CA Project

Software Engineer, Learner, Developer, Prokopton

Software Engineer, Learner, Developer, Prokopton