How To Rebuild the Derby Database for Workload Control Center r11.3 SP1

Document ID : KB000010250
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

One of the reasons why you may not be able to login to your WCC GUI or why certain WCC services (such as CA-uwccmonitoring  and CA-uwccmonitoringcollector) will not start is due to a corrupted database. 

To correct this issue, you need to export a copy of your WCC configurations and objects, rebuild your database and then import your WCC configurations and objects.

Environment:
CA Workload Control Center r11.3 SP1 using a Derby Database
Instructions:

===============

UNIX/LINUX

===============

 

Start by navigating to your $CA_WCC_INSTALL_LOCATION/bin directory

 

1. Export all views, their filters, alert policies, and jobs (if you have any to back up ) using the following command:

./wcc_monitor.sh -u username -p password -x output_file

2. Export all job status console defintions (if you have any to back up ) using the following command:

./wcc_jsc.sh -u user_name -p password -x output_file

3. Export all configurations to the file for backup using the following command:

./wcc_config.sh -u user_name -p password -x output_file

4. Stop WCC Services

./StopWCCServices.sh

5. Backup $CA_WCC_INSTALL_LOCATION/MonitorDB/wccmonitor and backup $CA_WCC_INSTALL_LOCATION/ReportsDB/reports by renaming the directories to something like wccmonitor_bkup and reports_bkup

6. Restart WCC services (this will force WCC to recreate the DB)

./StartWCCServices.sh

7. Confirm you can log into WCC (it will take a while to log into WCC because the database is being created at this time)

8. Import config backup files (if you backed up any)

./wcc_config.sh -u username -p password -i input_file

9. Add/validate/deploy AE server (if it's not done already)

10. Import monitor backup files (if you backed up any)

./wcc_monitor.sh -u username -p password -i input_file

11. Import JSC backup files (if you backed up any)

./wcc_jsc.sh -u username -p password -i input_file

 

===============

WINDOWS

===============

 

Start by navigating to your %CA_WCC_INSTALL_LOCATION%\bin directory using a command prompt window

 

1. Export all views, their filters, alert policies, and jobs (if you have any to back up ) using the following command:

wcc_monitor -u username -p password -x output_file

2. Export all job status console defintions (if you have any to back up ) using the following command:

wcc_jsc -u user_name -p password -x output_file

3. Export all configurations to the file for backup using the following command:

wcc_config -u user_name -p password -x output_file

4. Stop all WCC services

5. Backup %CA_WCC_INSTALL_LOCATION%\MonitorDB\wccmonitor and backup %CA_WCC_INSTALL_LOCATION%\ReportsDB\reports by renaming the directories to something like wccmonitor_bkup and reports_bkup

6. Restart WCC services (this will force WCC to recreate the DB)

7. Confirm you can log into WCC (it will take a while to log into WCC because the database is being created at this time)

8. Import config backup files (if you backed up any)

wcc_config -u username -p password -i input_file

9. Add/validate/deploy AE server (if it's not done already)

10. Import monitor backup files (if you backed up any)

wcc_monitor -u username -p password -i filename

11. Import JSC backup files (if you backed up any)

wcc_jsc -u username -p password -i filename