Other messages

Messages in this category are part of SqlMxHealthCheck verification output. These messages do not directly affect mxtool fixrcb or upgrade/downgrade issues. However, these messages may cause other issues after migration.

Non-existence database object owner

This message is issued if there are database objects, such as catalog, schema, table, trigger, view, sequence, and stored procedure owned by a user, but the user no longer exists on the system.

Owner userid of the object-type object-name does not exist on node.

Where,

userid is the group, user who owns the database object;

object-type is the type of the database object;

object-name is the name of the database object;

node is the name of the local node.

Cause

Owner of the database object no longer exists on the node.

Required action

If the SQL/MX version is R3.2.1, then use GIVE SCHEMA or GIVE [ CATALOG | TABLE …] to transfer object ownership to an existing user on the system. For more information about the GIVE command, see the SQL/MX Reference Manual. Contact Hewlett Packard Enterprise support if the problem persists.

Improper MXANCHOR file security for remote nodes

This message is issued if the remote nodes on which catalogs are registered contains MXANCHOR file with security (RWEP) other than ‘NCNC’.

The remote MXANCHOR file on the node node is not 'NCNC'.

Where node is the name of the remote node.

Cause

The MXANCHOR file permission is not ‘NCNC’.

Required action

Change the MXANCHOR file permission to ‘NCNC’ and retry the operation.

Catalog does not exist

This message is issued if -catalog option is specified to the SqlMxHealthCheck tool and if the catalog does not exist on the system.

The specified catalog catalog does not exist.

Where catalog is the name of the catalog.

Cause

The specified catalog does not exist on the system.

Required action

Specify an existing catalog to the SqlMxHealthCheck tool.