Database Reference
In-Depth Information
•
Domain:
In the event of a severe configuration failure of the domain in which
it is unable to start.
•
Middleware Home:
For example, to restore the entire infrastructure to a pre-
vious release after a patch has been applied.
•
Oracle Home:
For example, restoring Oracle SOA Suite
11g
to a previous
version after it has been upgraded.
•
JDK:
For example, if desiring to revert to a previous version of your JDK.
•
Oracle system files:
In the event of a bad software installation where you
wish to restore the Oracle Inventory to its original state.
In almost all cases, your Oracle SOA Suite
11g
environment must be offline to
recover. Though possible, it is dangerous to try to recover Oracle SOA Suite,
Oracle WebLogic Server, JDK, or any other component while the infrastructure
is running.
There are implications to recovering JMS data to a previous point in time. As
discussed earlier, we generally do not recommend backing up (or restoring) the
JMS file store. It can result in duplicate or lost messages. In many cases, it is
probably better to recreate the persistent stores in the event that they are acci-
dentally deleted or are in need of recovery.
Since the transaction log is accessible to all nodes of your cluster, in the event of
a server failure, the other machines should be able to process the transactions.
Even in the unlikely event of a full environment crash, the Transaction Recovery
Service gracefully handles transaction recovery once the servers are brought
up.
