Information Messages

Messages in this category are part of SqlMxHealthCheck verification output. These messages are for information only and does not have any impact on ‘mxtool fixrcb’ utility and/or Upgrade and Downgrade SQL commands. These messages do not require any actions to be performed.

Start and completion of database objects verification

The following message is displayed when a particular category verification is started. This message is displayed only once per category during the verification.

Verification of category started.

Where category is the category of database objects that are verified.

Cause

The verification of the following category of database objects is started:

  • Catalogs

  • Schemas

  • User objects under the schema

  • Views

  • Catalog registrations

  • Remote MXANCHOR files

  • Definition schema tables

The following message is displayed when a particular category verification ends. This message is displayed only once per category during the verification.

Verification of category ended.

Where category is the category of database objects that are verified.

Cause

The verification of the following category of database objects ends:

  • Catalogs

  • Schemas

  • User objects under the schema

  • Views

  • Catalog registrations

  • Remote MXANCHOR files

  • Definition schema tables

The following message is displayed when a particular database object verification is started. This message is repeated for each database object. If –logl option is warn, then this message is not displayed.

Verification of object-type object-name started.

Where,

object-type is the type of the database object that is verified;

object-name is the ANSI name of the database object.

Cause

The verification of the following specific type of database object is started:

  • Catalog

  • Schema

  • Table

  • Index

  • Trigger temporary table

  • Stored procedure

  • Sequence

  • View

The following message is displayed when a particular database object verification is completed successfully. This message is repeated for each database object. If –logl option is warn, then this message is not displayed.

Verification of object-type object-name completed successfully.

Where,

object-type is the type of the database object that is verified;

object-name is the name of the database object.

Cause

The verification of the following specific type of database object is completed successfully:

  • Catalog

  • Schema

  • Table

  • Index

  • Trigger temporary table

  • Stored procedure

  • Sequence

  • View

The following message is displayed when a particular database object verification is completed with minor conditions. This message is repeated for each database object. If –logl option is warn, then this message is not displayed.

Verification of object-type object-name completed with minor conditions.

Where,

object-type is the type of the database object that is verified;

object-name is the name of the database object.

Cause

The verification of the following specific type of database object is completed with minor conditions:

  • Catalog

  • Schema

  • Table

  • Index

  • Trigger temporary table

  • Stored procedure

  • Sequence

  • View

The following message is displayed when a particular database object verification is completed with severe conditions. This message is repeated for each database object. If -logl option is warn, then this message is not displayed.

Verification of object-type object-name completed with severe conditions.

Where,

object-type is the type of the database object that is verified;

object-name is the name of the database object.

Cause

The verification of the following specific type of database object is completed with severe conditions:

  • Catalog

  • Schema

  • Table

  • Index

  • Trigger temporary table

  • Stored procedure

  • Sequence

  • View

Catalog with no user schemas

This message is issued if there are no schemas in a catalog.

Catalog catalog has no schemas.

Where catalog is the ANSI name of the catalog.

Cause

The catalog that is verified has no schemas.

No remote catalog registrations

This message is issued if there are no catalogs registered on a remote node.

No catalog(s) are registered on a remote node.

Cause

There are no catalogs that are registered on a remote node. This message is displayed if no catalogs on the local node are registered remotely and no remote catalogs are registered on the local node.

Audit Compress flag not set

This message is issued when the 'AuditCompress' flag is not set for a file label. The AuditCompress flag only indicates the mode of producing audit-checkpoint messages. The AuditCompress flag not set does not cause any issue.

The AuditCompress flag is not set in file label Guardian-file-name for object-type object-name.

Where,

Guardian-file-name is the fully qualified Guardian file name of the affected file label;

object-type is the type of the affected database object;

object-name is the three-part ANSI name of the affected database object.

Cause

The AuditCompress flag is not set in the file label.

ClearOnPurge flag is set

This message is issued when the ‘ClearOnPurge’ flag is set for a file label. The ‘ClearOnPurge’ flag set does not cause any issues for mxtool fixrcb and/or Upgrade and Downgrade SQL commands. If you drop a table or index that has the ClearOnPurge flag set, the disk process physically deletes the file data from the disk and then deletes the table or index.

The ClearOnPurge flag is set in the file label Guardian-file-name for object-type object-name.

Where,

Guardian-file-name is the fully qualified Guardian file name of the affected file label;

object-type is the type of the affected database object;

object-name is the three-part ANSI name of the affected database object.

Cause

The ClearOnPurge flag is set in the file label.