What is the architectural benefit of keeping WebLogic Server transaction log in the database?

Question

Options

• AOracle does not allow replicating files between data centers, so keeping transaction log in
• BMany transactions in WebLogic are database centric, so keeping log in database makes Two
• CIt obviates the need to keep in sync two replication technologies (file and database) between data
• DTransaction log in a file system is extremely slow so it cannot be efficiently replicated.

• A
  4% (1)
• B
  24% (6)
• C
  56% (14)
• D
  16% (4)

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 * 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. Not B: Readonly, Onephase Commit Optimization requires Oracle DB 11.1.0.7.3 PSU or above.

No community discussion yet for this question.