Running consistency checks

Running consistency checks from PolicyCenter

Guidewire recommends that you view and run consistency checks from the Server Tools Consistency Checks screen in PolicyCenter. The Consistency Checks screen lists which consistency checks are available for specific tables. You can also use this page to view the results of previous consistency check runs. If there are consistency check errors, the results include SQL queries that you can use to identify records that violated the consistency check.

Running consistency checks from a command prompt

It is possible to launch database consistency checks from a command prompt. Launching consistency checks from the command prompt is useful primarily for scheduling checks to run on a regular basis. This approach to running consistency checks uses the system_tools -checkdbconsistency command option.

Running consistency checks using the -checkdbconsistency option can take a long time. If the connection times out while running this command, try the following:

  • Run consistency checks on fewer tables at a time.
  • Increase the number of worker instance threads used by the consistency check work queue.

Configure consistency checks to run at server start

It is possible to set the checker attribute in file database-config.xml to automatically trigger database consistency checks at server start.

About this task

Important: Guidewire strongly discourages the use of the checker attribute in file database-config.xml to automatically trigger database consistency checks at server start. Database consistency checks are very resource-intensive and can significantly degrade server performance. Only use the checker attribute to trigger consistency checks in a development environment that contains a very small data set. If you do use this attribute, the server log prints a message that Guidewire has deprecated the use of this attribute.

Procedure

  1. Open Guidewire Studio™ for PolicyCenter.
  2. In the Project window, expand configuration > config.
    1. Open file database-config.xml.
    2. Add a checker attribute on the <database> element and set the attribute to true.
      • <database checker="true" ...>
      By default, Guidewire omits this attribute in the base configuration and sets its value to false.
    3. Save and close file database-config.xml.
  3. Restart the application server to trigger the database consistency checks:
    • If working in a development environment, restart the QuickStart server.
    • If working in a production environment, create a new WAR or EAR file and deploy the file to the production server.