Corrupt Repository

Documentation for OAS Repository Corruption and Recovery

February 5, 2013

Authored for Middleware Team

So let’s talk corrupt repository, there are several things that could go wrong with the repository. I will address a few of them for lessons learned here in this document. We will start with the main five causes:

 User error (damaging or deleting crucial files in $ORACLE_HOME/)

 Hardware failure (memory errors, disk corruption, power supply issues)

 Operating system failure (filesystem bugs, kernel crashes, cross-platform compatibility issues)

 Tool error (third-party tools inadvertently damaging .hg/ state)

 Tercurial failure (bugs in hg causing data corruption - very rare)

I’m going to say in this case we have a little bit User error mixed with Operating system failure and Tool error. We have to do our due diligence to clean up directories when deploys fail and deploy properly with the tools given. There are some instances where deploys are changed on the fly or we have file system bugs and cross-platform compatibility issues. When these instances occur we have to be the gatekeepers of the information and hone in on our SOP’s to alleviate these occurrences. So here is a scenario, let’s say you have a Deploy scheduled for today. In this case we will use ER Web Apps for an example.

When deploying application to prod or non-prod we usually deploy from the container under applications as shown below.

Figure 1

First we choose the container that we want to work within. The example shown is the ER container. Then we choose Applications. This will take us to our deployment screen.

Figure 2

Here we have the Deployment screen showing the application that we want to Un-deploy first (Shown in Figure 3).

Figure 3

Figure 3

In this scenario we choose un-deploy. Let’s say we get an exception error while un-deploying. What should be our next step? First we read our exception carefully and see what it says. Then we want to...