Greenplum Command Center (GPCC) reports: column "memory_quota" does not exist

Products

• VMware Tanzu Greenplum
• Pivotal Data Suite Non Production Edition
• VMware Tanzu Data Suite
• VMware Tanzu Data Suite
• Greenplum

Issue/Introduction

After upgrading to Greenplum Database (GPDB) to 7.x, GPCC can start reporting the error:

column "memory_quota" does not exist

 

Cause

This is caused by the definition of the table gp_toolkit.gp_resgroup_config. The column name "memory_limit" has been renamed to "memory_quota".

gpperfmon=# \d  gp_toolkit.gp_resgroup_config
          View "gp_toolkit.gp_resgroup_config"
     Column      | Type | Collation | Nullable | Default
-----------------+------+-----------+----------+---------
 groupid         | oid  |           |          |
 groupname       | name |           |          |
 concurrency     | text | C         |          |
 cpu_max_percent | text | C         |          |
 cpu_weight      | text | C         |          |
 cpuset          | text | C         |          |
 memory_limit    | text | C         |          |
 min_cost        | text | C         |          |
 io_limit        | text | C         |          |

Resolution

Fix

• Ensure GPDB is 7.1.1 or above
• Connect to each database in the cluster and run:

SELECT * FROM pg_extension;
ALTER EXTENSION gp_toolkit UPDATE;

The version of the extension should be 1.6 or above.