It is suggested to check the AC database for problems rather than rebuilding them regularly. This is suggested because although a rebuild is a good thing, other outside factors can cause serious problems if something disrupts the rebuild process. Some things which could happen are:
Please see the below commands which might be used to create an AC database check script.
Note: These are only example commands to run an AC DB check and verify the success/failure of the check. You or your Services team will need to be responsible for creating the script and ensuring it works properly.
mkdir C:\ACCheck cd c:\ACCheck dbmgr -backup . dbmgr -u -all seos_odf.dat | find "succ" > ACCheck.log dbmgr -u -all seos_cdf.dat | find "succ" >> ACCheck.log dbmgr -u -all seos_pdf.dat | find "succ" >> ACCheck.log dbmgr -u -all seos_pvf.dat | find "succ" >> ACCheck.log
So in the example above the ACCheck.log will show 8 lines of success messages like below if the AC DB was ok.
Index Check Completed succ = four times Free Index Check Completed succ = four times
If there are less than 8 lines someone should look into the AC DB Consistency or run a full AC database index rebuild.
If you think it might be inconsistent then run the whole check process again and ensure that they are consistent results.
If you need to rebuild the AC database indexes move onto the steps below;
dbmgr -u -build seos_odf.dat dbmgr -u -build seos_cdf.dat dbmgr -u -build seos_pdf.dat dbmgr -u -build seos_pvf.dat
Check the output for success.
Note: you may see deleted records noted in the live AC database index rebuild which is normal.
As Always, If you have any questions or concerns with the technical information provided in this document, please contact CA Support.