It might happen that due to oversight during GPCC upgrade , GPCC symbolic links not updated on all the hosts to the actively running GPCC version on all hosts instead its pointing to the different GPCC(old prior version from which it was upgraded) version.
Note - This might not show any issues with functioning of GPCC as the old and upgraded versions are compatible to be work without issues but should not be kept like that instead needs to be updated to the installed active single GPCC version on all hosts of cluster.
All Greenplum Database versions.
All Greenplum Command Center (GPCC) versions.
It might be oversight during the upgrade that only the symbolic links are updated on the Master(5.x,6.x)/Coordinator(7.x) host leading to this issue.
Note - Please make sure gpadmin must have write access to /usr/local directory or another directory where GPCC is installed.
If somehow only root have access, use root to udpate the links.
1. Stop GPCC if already running.
2. Remove the existing symbolic link for /usr/local/greenplum-cc:
gpssh -f <hostfile> 'sudo unlink /usr/local/greenplum-cc'
3. Create a new symbolic link from /usr/local/greenplum-cc to the new version directory:
gpssh -f <hostfile> 'sudo ln -s /usr/local/greenplum-cc-<version> /usr/local/greenplum-cc'