- If there is any concern or doubt about executing the below steps without assistance, please do not hesitate to open a new support case to request assistance.
- None of the below processes require the MySql service to be stopped or restarted.
- Before starting to fix the database, shut down all CA Performance Manager services to prevent DB access during the fix process. See KB article kb000032043 for instructions on stopping and starting these services.
After shutting down the four CA Performance Manager services, but leaving the MySql service running, the first step is to determine how extensive the problem is. To do so:
- Log into the CA Performance Manager server at the command line as the root user
- Change directories to the /opt/CA/MySql/bin directory.
- Run the following command to begin the repair of the tables: mysqlcheck -uroot -pnetqos --repair --all-databases
- Run the following command to list the status of all tables in all databases present: mysqlcheck --all-databases
When the "mysqlcheck --all-databases" command is run and all tables are returned as OK, the corruption has been resolved. It is now safe to restart the four CA Performance Manager services. After this the web UI and log in should work. If it does not, please open a new support case for further investigation and resolution.