| Summary | This article describes how to manage the growth and size of Orbix services' databases |
|---|---|
| Article Number | 32987 |
| Environment | Orbix 6.3 All supported platforms |
| Question/Problem Description | How to manage database size Managing the size of an Orbix database Limiting the size of an Orbix database Reducing the size of the services' databases Managing the databases' transaction logs Deleting the databases' transaction logs Archiving the databases' transaction logs |
| Clarifying Information |
The Orbix services use Berkeley databases to store persistent information. These databases consist of data files and transaction logs.
The transaction log file will grow whenever the database is accessed. By default, once a transaction log file reaches 10MB in size, a new transaction log file is created and the old file deleted. When a transaction log file does not contain any information pertaining to active transactions, it can be archived or deleted.
The above behaviour can be altered through configuration, or utilities. |
| Error Message | |
| Defect/Enhancement Number | |
| Cause | |
| Resolution | Transaction log files can be controlled through configuration and the "itadmin" utility. This allowed the user to manage the overall size of the database to some extent. For information on how to manage Orbix services' database transaction log files, please see the Orbix documentation. Orbix Administrator's Guide, Chapter 9: "Managing Orbix Service Databases", Section 3: "Managing Log File Size". Additionally, Orbix provides an itadmin command to reclaim unused space in the persistant storage used by the specified untyped notification channel: itadmin nc compact <Channel Name> |
| Workaround | |
| Notes |
Orbix 6 Product Documentation: |
| Attachment |
| Created date: | 03 July 2012 |
|---|---|
| Last Modified: | 03 August 2012 |
| Last Published: | 03 August 2012 |
| First Published date: | 03 July 2012 |
#KnowledgeDocs
#orbix.6database
#Orbix
