Using a Transaction Log to Optimize Performance

When operating without a transaction log, Oracle Database SE2 must use a checkpoint at the end of every transaction. Writing these modifications consumes considerable resources, and it can degrade performance.

To enable Oracle Database SE2 to write notes that detail modifications as they occur, you can use a transaction log. Oracle Database SE2 can write the new database pages all at one time and at a time that is more efficient. Checkpoints make sure information enters the server database file and that this information is consistent and up to date.

To use a transaction log to optimize performance

Open the Server Manager command line.
For more information, see Opening the Command Line Interface for Server Manager.
Enter the following command:
```
srvrmgr> change param ClientDbTxnLog=True for comp dbxtract
```
This command sets the ClientDbTxnLog parameter to True for the Database Extract server component. Subsequent database extracts include a transaction log.