Schema Mismatch Error After Upgrading to PGP Universal Server 3.2.x

Products

• Symantec Products

Issue/Introduction

Schema mismatch reported in logs after upgrading PGP Universal server to version 3.2.0 or higher.

 

Cause

This is generally caused by a failed or missed migration during an upgrade. In some cases the migration could have been from a previous upgrade.

 

Resolution

Please open a case with Symantec Technical Support to fix this issue.  To fix this issue, you will need SSH access to the server. WinSCP or SCP are also needed as some file transfers will be used during the process. If you do not have SSH access to your server, you can follow the related article below to set that up.