CA Directory Database File Defragmentation
Article ID: 388195
Updated On:
Products
Issue/Introduction
CA Directory database file defragmentation is a concept that re-surfaced after the introduction of the "set dxgrid-db-tuning = 34;" starting CA Directory 14.1/sp5 to address the performance issues sometimes occur when CA Directory is used as a session store. The concept is not new, nevertheless. The idea is that reduced data defragmentation assists in improving the processing of add, modify, and delete requests that by-design are slower. Generally, when the dxgrid-db-tuning is set to work, it does a good job to keep up the online defragmentation job. However, under certain extreme conditions, you may decide to do it offline.
In addition, there have been scenarios where people have experienced issues with regard to the ever increasing "Reclaimable Bytes" due to how the applications are designed to work and eventually caused issues to the CA Directory data DSAs. When this happens, we may start seeing the type of
** ALARM **: 60% of datastore in use
appears in the alarm log even though the size of the database file can actually keep up with the real data growth.
Environment
Release 14.1
Component: CA Directory
Resolution
CA Directory utilites the memory mapped file to gain the permission boost. For a normal no-downtime operation, the same steps are performed on each of the multi-write servers one server at a time:
- Select a Data DSA to perform the database file defragmentation
- Wait for at least one of its peer multi-wrie Data DSAs to start serving data.
- stop the Data DSA
dxserver stop DSAName
- dxdumpdb to dump the data to an LDIF file
dxdumpdb -f LDIFFileName DSAName
- dxloadb to reload the LDIF data fro the LDIF file
dxloaddb DSAName LDIFFileName
- re-start the Data DSA
dxserver start DSAName
Additional Information
Please see the following documentation links for additional information:
Feedback
