Using this utility can generate a large number of native database log entries. A large number of these entries can significantly increase the storage used by your database. You can use a variety of methods to manage transaction logging space, depending on your database type (Oracle, SQL Server, or DB2).
|
Note: |
Reclaiming logging space is a task that should be performed by a database administrator. |
The following examples show how to reclaim transaction logging space in Oracle and SQL Server.
Oracle—The following command attempts to resize the Redo log file, "EPMARedo.log," to 600k.
ALTER DATABASE DATAFILE 'F:\oradata\live\EPMARedo.log' RESIZE 600k;
SQL Server—The following command decreases the size of the data and log files in a database called "EPMA," with the goal of creating 5 percent free space within each file.
DBCC SHRINKDATABASE (EPMA, 5); GO
|
Note: |
In DB2, log file size is generally not an issue since it is overwritten if "circular logging" is enabled. If "non-circular logging" is enabled, it can be deleted when DB2 begins to use the next log file in sequence. For additional information, see your DB2 documentation. |