Metadata upgrade/downgrade specific conditions
Messages in this category are part of the SqlMxHealthCheck verification output. They indicate that some condition exists which might prevent metadata Upgrade or Downgrade. Such conditions are perfectly acceptable in a regular production state, but might cause unexpected delays when metadata Upgrade/Downgrade is required.
SqlMxHealthCheck reports these messages as "MINOR" and you must address the reported conditions before attempting a metadata upgrade or downgrade.
View reference to system schema table
This message is issued when a user view references the ALL_UIDS table, and the target version specified to SqlMxHealthCheck is 3000 or greater.
View
view-name references system schema table ALL_UIDS.
Cause
The view references the ALL_UIDS system schema table which will be removed when the metadata for the system catalog is upgraded to version 3000 or higher.
Required action
The presence of the view will prevent a metadata upgrade to 3000 or higher for the system catalog. Remove the view before such a metadata upgrade. Save SHOWDDL output for the view before removing it. Since the ALL_UIDS table is removed entirely as a result of the metadata upgrade, the view cannot be recreated "as is".
If no metadata upgrade is planned, then no action is required.
View reference to table in the system security schema
This message is issued when a user view references a table in the SYSTEM_SECURITY_SCHEMA in the system catalog, and the target version specified to SqlMxHealthCheck is less than 3100.
View
view-name references system schema table
table-name.
-
Where,
-
view-name is the three-part ANSI name of the affected view;
-
table-name is the three-part ANSI name of the referenced table in the system security schema.
Cause
The view references the named system security schema table which will be removed when the metadata for the system catalog is downgraded to a version lower than 3100.
Required action
The presence of the view will prevent a metadata downgrade to 3000 or lower for the system catalog. Remove the view before such a metadata downgrade. It is recommended to save SHOWDDL output for the view before removing it, since the system security schema is removed entirely as a result of the metadata downgrade, the view cannot be recreated 'as is'.
View reference to definition schema table
This message is issued when a user view references a table in some definition schema.
View
view-name references definition schema table
table-name.
-
Where,
-
view-name is the three-part ANSI name of the affected view;
-
table-name is the three-part ANSI name of the referenced definition schema table.
Cause
The view references the named definition schema table which is replaced when metadata is upgraded or downgraded.
Required action
The presence of the view will prevent a metadata upgrade or downgrade. The view must be removed before such an operation. Save SHOWDDL output for the view before removing it. The view cannot be recreated exactly "as is" after a metadata upgrade or downgrade since the definition schema name changes, but changing the version part of the definition schema name in the view definition must be straightforward.
View reference to UMD table
-
The schema version of the affected schema is 1200 and the target version is 3000 or higher.
-
The schema version of the affected schema is 3000 or higher and the target version is 1200.
View
view-name user metadata table
table-name.
-
Where,
-
view-name is the three-part ANSI name of the affected view;
-
table-name is the three-part ANSI name of the referenced UMD table.
Cause
The view references the named UMD table which will be replaced when metadata is upgraded or downgraded between version 1200 and a higher version.
Required action
The presence of the view will prevent a metadata upgrade or downgrade. The view must be removed before such an operation. Save SHOWDDL output for the view before removing it. The view can be re-created exactly "as is" after a metadata upgrade from version 1200 to version 3000 or higher. Also, in many cases it can be recreated exactly "as is" after a downgrade to version 1200. But, if the view references the HISTOGRAM_FREQ_VALS table or if it references one of the columns in the HISTOGRAMS or HISTOGRAM_INTERVALS table that is not present in version 1200, then the view must be rewritten.
Database objects using new features
This message is issued if there are database objects that use any new features that are not compatible on the specified target version.
The
object-type object-name has object feature version
version1 which is not supported on the specified target version
version2.
-
Where,
-
object-type is the type of the affected database object;
-
object-name is the three-part ANSI name of the affected database object;
-
version1 is the object feature version of the affected database object;
-
version2 is the specified target version.
Cause
The database object uses new features that are not supported on the target version.
Required action
-
Use the FEATURE_VERSION_INFO function to obtain the name and the object type of the database objects that uses new features. Such database objects prevent a downgrade operation.
-
Convert each database object that uses the new features to a corresponding copy object without the new feature. For copy objects, you create a copy of the original object without the new feature, to retain the data.
-
Drop the original objects with the incompatible feature version before executing the downgrade command.
Schema with incompatible version
This message is issued when a schema is not compatible on the specified target version.
Schema
schema has schema version
version1 which is not compatible on the specified target version
version2.
-
Where,
-
schema is the name of the affected schema;
-
version1 is the schema version of the affected schema;
-
version2 is the specified target version.
Cause
The schema is not compatible after the system is downgraded to the specified target version.
Required action
Perform metadata downgrade before attempting fallback if the database contains schemas with schema version higher than the fallback (target) version. For more information on
Downgrade SQL command, see
SQL/MX Installation and Upgrade Guide.
Schema level privileges exist on a schema
This message is issued when there are user granted schema level privileges on a schema. The target version specified to SqlMxHealthCheck is 3400 or lower.
Schema level privileges exist for schema schema-name.
-
Where,
-
schema-name is the ANSI name of the affected schema.
Cause
The schema is granted schema level privileges by the owner or security administrator. These privileges are not compatible after the system is downgraded to the specified target SQL/MX version.
Required action
Revoke all the schema level privileges granted on the reported schema before attempting fallback. For more information on revoking schema level privileges from a schema, refer to SQL/MX 3.5 Release Technical Update.
DML/DDL privileges granted to a privilege group on a schema or object
This message is issued when there are user granted schema level or object level privileges to a privilege group. The target version specified to SqlMxHealthCheck is 3400 or lower.
Privileges on object-type, object-name have been granted to privilege group privilege-group.
-
Where,
-
object-type is either schema, table, view, sequence, or stored procedure.
-
object-name is the ANSI name of an affected object.
-
privilege-group is the name of a privilege group to which privilege has been granted.
Cause
There are schema level or object level DDL/DML privileges granted to a privilege group. They are not compatible after the system is downgraded to the specified target SQL/MX version.
Required action
Revoke all the schema level or object level privileges granted on the reported object to the privilege group before attempting to fallback. For more information on revoking schema level privileges from a schema, refer to SQL/MX 3.5 Release Technical Update.