Database Reference
In-Depth Information
Transaction logs
Transaction logs
store information about committed transactions, coordinated
by the Oracle WebLogic Server, that may not have been completed. The trans-
action logs provide Oracle WebLogic Server with a mechanism to recover from
system crashes or network failures.
It is recommended to configure the default persistent store of the transaction
logs to a directory on highly available and shared storage. This is typically a re-
quirement for multinode installations of Oracle SOA Suite
11g
anyway. To identi-
fy where this directory is, log in to the Oracle WebLogic Server Administration
Console, navigate to
Environment
|
Servers
|
soa_server1
|
Configuration
|
Services
, and observe the value of
Directory
.
Unfortunately, transaction logs can only be stored in the default store and must
be file-based. Thus, the backup behavior is similar to that of JMS file-based
persistent stores. Oracle WebLogic 12c, however, allows transaction logs to be
stored in a JDBC store, but Oracle SOA Suite is not yet released for that version.
Since transaction logs are based on file-based persistent
stores, do not delete or restore them. It may result in data in-
consistency.
The recommendation, therefore, is to ensure that the transaction logs reside in
fully redundant shared storage accessible to all nodes of the cluster, and guaran-
tee its availability. Backing up the transaction logs is suggested, but there are im-
plications regarding message loss and message duplication should you choose
to restore them.
