Running a previously run DBCC

A DBCC can fail due to database consistency errors. After you have fixed the errors, you may want to rerun the DBCC to ensure all errors have been fixed. You can do this through Cloud API by including a request body with a rerunKey attribute. This attribute must be set to the Key value provided by the GET /systemtools/v1/database-consistency-checks endpoint. Note that the Key value is expressed as an integer. For more information on this endpoint, see Querying for DBCC run information.

For example, suppose you ran a DBCC that had errors. The GET /systemtools/v1/database-consistency-checks endpoint identifies the Key for this run is 21. You have fixed the errors and now want to rerun the same DBCC. The following request does this.
POST /systemtools/v1/batch-processes/DBConsistencyCheck/start

{
  "data": {
    "attributes": {
      "dbconsistencycheck": {
        "rerunKey": 21
      }
    }
  }
}

An InsuranceSuite application reruns a DBCC run only when the original DBCC run reported errors. If you provide a Key value that does not correspond to a previous run with errors, the InsuranceSuite application ignores the request.