What is the architectural benefit of keeping WebLogic Server transaction log in the database?
A.
Oracle does not allow replicating files between data centers, so keeping transaction log in
database allows for replication.
B.
Many transactions in WebLogic are database centric, so keeping log in database makes Two
Phase Commit protocol possible.
C.
It obviates the need to keep in sync two replication technologies (file and database) between
data centers. The single replication technology is used for frequently changing data.
D.
Transaction log in a file system is extremely slow so it cannot be efficiently replicated.
Explanation:
You can configure a JDBC TLOG store to persist transaction logs to a database,
which provides the following benefits:
* Leverages replication and HA characteristics of the underlying database.
* Simplifies disaster recovery by allowing the easy synchronization of the state of the database
and TLOGs.
* Improved Transaction Recovery service migration as the transaction logs to do not need to be
migrated (copied) to a new location.
* You can configure a JDBC TLOG store to persist transaction logs to a database, which allows
you to leverage replication and HA characteristics of the underlying database, simplify disaster
recovery, and improve Transaction Recovery service migration.
incorrect:
not B: Read-only, One-phase Commit Optimization requires Oracle DB 11.1.0.7.3PSU or above.