Skip Navigation Links | |
Exit Print View | |
Oracle Directory Server Enterprise Edition Administration Guide 11g Release 1 (11.1.1.5.0) |
Part I Directory Server Administration
2. Directory Server Instances and Suffixes
Quick Procedure for Creating Server Instances and Suffixes
Creating and Deleting a Directory Server Instance
To Create a Directory Server Instance
To Delete a Directory Server Instance
Starting, Stopping, and Restarting a Directory Server Instance
To Start, Stop, and Restart Directory Server
To List All the Running Instances
Disabling or Enabling a Suffix
To Disable then Enable a Suffix
Setting Referrals and Making a Suffix Read-Only
To Set Referrals to Make a Suffix Read-Only
Importing Data From an LDIF File
To Load Sample Data in Directory Server Instance
Adding, Modifying, and Deleting Entries in Bulk
To Add, Modify and Delete Entries in Bulk
3. Directory Server Configuration
6. Directory Server Access Control
7. Directory Server Password Policy
8. Directory Server Backup and Restore
9. Directory Server Groups, Roles, and CoS
10. Directory Server Replication
13. Directory Server Attribute Value Uniqueness
15. Directory Server Monitoring
Part II Directory Proxy Server Administration
16. Directory Proxy Server Tools
17. Directory Proxy Server Instances
19. Directory Proxy Server Certificates
20. Directory Proxy Server Load Balancing and Client Affinity
21. Directory Proxy Server Distribution
22. Directory Proxy Server Virtualization
23. Virtual Data Transformations
24. Connections Between Directory Proxy Server and Back-End LDAP Servers
25. Connections Between Clients and Directory Proxy Server
26. Directory Proxy Server Client Authentication
27. Directory Proxy Server Logging
28. Directory Proxy Server Monitoring and Alerts
Part III Directory Service Control Center Administration
Directory Server 11g Release 1 (11.1.1.5.0) supports the compaction of suffixes offline. Online compaction is not supported in this release. If storage space is available, compacting a suffix reduces the size of the database by reorganizing the database keys, and returns the storage space to the filesystem, if possible. Compacting a suffix also reduces the disk footprint. Since application data is not processed and based on the way the database keys are managed, it is not guaranteed that the storage space can be reclaimed. Nevertheless database size will not grow.
Before You Begin
Be sure you have sufficient disk space.
Compacting a suffix requires free disk space equal to at least twice the size of the largest suffix to be compacted. The free disk space is needed for temporary files. For example, to compact the following three suffixes :
o=suffix1 : 300 Gb o=suffix2 : 170 Gb o=suffix3 : 633 Gb
The server requires at least 633 * 2, or 1266 Gb, of free disk space.
Stop the server and back up your database before performing this task.
$ dsadm repack instance-path suffix-dn
All .db3 files related to the specified suffix are compacted.
If you run this command with the -b option, you can specify a backend database name, instead of a suffix DN. At least one suffix, or one backend must be specified.
For more information, see the dsadm(1M)man page.