VxRail: Health Check Fails for op_status Test

Summary: Health check returns an event indicting that the 'operation_status' database table is too large, which causes problems when upgrading to a VxRail 7.x release.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Symptoms

VxRail Manager runs several health-checks (using VxVerify), one of which is operation_status
For VxRail 4.x, the size of the operation_status database table is checked. If it is too large, it could not then be migrated to VxRail 7.x. The individual entries are also checked to make sure that there are no empty extension values (Null or None).

For VxRail 7.0 and later versions, this test sees that the individual entries are checked to verify that there are no empty state values (Null or None).

The results of this health check and possible autocorrections are listed as a health check with one of the following results:

Test Result Result Code     Result Interpretation
Pass 0 No issues with the operation_status Database table found
Warning 1 Database operation_status table is too large.
Failure 2 NULL operation_status entries found
Critical 3 This test has no critical result.


Each test that passes will not be listed in the summary report, for ease of reading.
An example of the health-check output is shown below:

#========================#======#=========#====================================================================#==============#
|  Hostname / Category   |Status  Dell_KB |  Warnings or Failures, unless tests Passed                         ; Product S.N. |
#========================#======#=========#====================================================================#==============#
| VxRM                   | Warning 201380 | op_status: Operation_status DB too large: 4200 kB.                                |

Cause

To get the database (DB) size in VxRail 4.x, this test runs a query similar to the command below:

psql -U postgres mysticmanager -c "select pg_size_pretty (pg_relation_size('operation_status'))"

This query looks at the size of the operation_status table and compares this against this tests warning and failure thresholds. Upgrades may fail if the operation_status DB table exceeds 4 MB, contains NULL entries, or (in 7.0+) has invalid status values outside the supported list.

Resolution

Reduce oversized DB tables using the psql cleanup command, open a support case for NULL entries in 4.x, and use VxVerify -f or -fix to correct invalid entries in 7.x+. 

DB is too large:

psql -U postgres mysticmanager -c "delete from operation_status WHERE state='FAILED' OR state='COMPLETED' AND owner!='LOG_BUNDLE' AND id not like 'SBI_%';"

NULL or invalid DB entries:

For NULL entries in VxRail 4.x, open a support ticket for investigation: Contact Technical Support | Dell US 

Invalid entries in 7.x+:
Refer to: Dell VxRail: How to run the VxVerify tool

Affected Products

VxRail, VxRail Appliance Family, VxRail Appliance Series, VxRail Software
Article Properties
Article Number: 000201380
Article Type: Solution
Last Modified: 16 Mar 2026
Version:  5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.