As described in What are the databases used by the management applications?, there are 2 schemas that, while separate, must be updated at the same time and remain in sync with the WGS and GUI interfaces.
When you install a management application for the first time, the tables are created at a specific schema level (for example, 20). This is checked by the software to ensure it matches the expected version.
Subsequent upgrading to a newer version requires the table structures to be updated. For example, if there is a new data element to be stored, this will require new columns to be added in one or more tables in nastel_apwmq. Similarly, when a new configuration setting is added, these have to be saved in tables in nastel_permv3. These changes are referred to as upgrades. The upgrades start at the next level and may consist of several upgrades to get to the new level (21-25). There are multiple upgrade scripts because smaller incremental changes are more reliable and are easier to diagnose should something go wrong. The recommended approach is to use the SQL maintenance tool, nsqjdbcmk, which automatically determines what scripts are required. Manually applying the changes requires applying each upgrade script to achieve the same result. The nastel_apwmq and nastel_permv3 schemas have their own upgrade scripts.
it is very important to take a backup before starting the upgrade should any issues arise. Due to the nature of database changes, there is no way to back them out.
Note, only the schemas shown in blue are usable by the product, the intermediate levels shown in gray are transitional only.
The schema is reported in several places but Enterprise Manager provides a summary of both schema levels and any other errors that may be reported.
This example shows an incomplete upgrade. The software was expecting 37 but found the last completed upgrade was 36. See this related article, What are the databases used by the management applications?.