You want to configure WebLogic server transactions to be recoverable when a nonclustered
managed server crashes, even if that crash is caused by an unrecoverable hardware failure. You
want to run the managed server on different hardware, and have it recover the transactions that
were in-progress at the time of the crash.
You also want to use the default store for transaction logs.
Which statement is true?
A.
Thisscenarioisnotpossible .YoumustusetheJDBCstore to recover transactions from a crashed
server.
B.
This scenario is not possible. You must use clustered managedservers to recover transactions
from a crashed server.
C.
This scenario is common , and so the default configuration of the default store works.
D.
Beforethe crash ,you need to update the path to the default store for the managed server. The
path should be to some shared storage location.
E.
After the crash,obtain a copy of the managed server’s defaultstorefrom the
administrationserver. Move it to the samerelative locationon the new hardware before starting the
managedserverthere.
D is correct
Answer : D
Explanation :
The default persistent store can only be a file store. Therefore, a JDBC store cannot be used as a default persistent store.
file-based stores [[must be configured on a shared disk]] that is available to the migratable target servers in the cluster.
Both a file store and a JDBC store can survive a process crash or hardware power failure without losing any committed updates. Uncommitted updates may be retained or lost, but in no case will a transaction be left partially complete after a crash.
Source : http://docs.oracle.com/cd/E24329_01/web.1211/e24432/store.htm#CNFGD228
Sorry, my last comment is about clustered.
The good answer is E
Explanation : For non-clustered servers, you can only move the entire server to a new system
Source : http://docs.oracle.com/cd/E24329_01/web.1211/e24377/trxman.htm#WLJTA178
Details : http://docs.oracle.com/cd/E24329_01/web.1211/e24377/trxman.htm#WLJTA180
To recover transactions for a failed server, follow these steps:
– Move (or make available) the persistent store DAT file (which contains all transaction log records) from the failed server to a new server.
-Set the path for the default persistent store with the path to the data file. See Setting the Path for the Default Persistent Store.
– Start the new server. The Transaction Recovery Service searches all transaction log files for incomplete transactions and completes them as described in Transaction Recovery Service Actions After a Crash.
E claims that managed server’s default store can be obtained from *Admin server*. Is it somehow possible? If not then D looks better to me, even for non-cluster setup.
E
Letter E
http://docs.oracle.com/cd/E24329_01/web.1211/e24377/trxman.htm#WLJTA180
D, no doubt:
When moving transaction log records after a server failure, make all transaction log records available on the new machine before starting the server there. Otherwise, transactions in the process of being committed at the time of a crash might not be resolved correctly, resulting in application data inconsistencies. Accomplish this by storing persistent store data files on a dual-ported disk available to both machines. As in the case of a planned migration, update the default file store directory attribute with the new path before starting the server if the pathname is different on the new machine.
http://docs.oracle.com/cd/E24329_01/web.1211/e24377/trxman.htm#WLJTA180
E inply to recover tlog from adminserver, i don’t think it is possible
“even if that crash is caused by an unrecoverable hardware failure” I think it is D