SQL/MX Health Check tool messages (26000 through 26017)

This section describes the error messages that are reported by the SQL/MX Health Check tool. These error messages are not expected as part of the regular SQL/MX Health Check tool execution but may occur at runtime during verification.

These errors can be categorized as follows:

  • Errors that stop SqlMxHealthCheck execution immediately. These are sub-divided into:

    • Parameter validation errors—SQL 23004, SQL 23005, and SQL 23009. These are listed under Utility messages (20000 through 23030).

    • Fatal validation errors—SQL 26000, SQL 26001, SQL 26002, SQL 26012, SQL 26013, and SQL 26017.

  • Errors that stop current verification – The current verification is stopped but the tool continues with further verification. These messages are: SQL 26003 through SQL 26010 and SQL 26014 through SQL 26016.

SQL 26000

This error occurs when direct access to the local anchor file fails.

26000 File system error error occurred on anchor file name.

Where,

error is the Guardian file system error code;

name is the fully qualified Guardian file name of the local SQL/MX anchor file.

Cause

Access to the local anchor file failed and returned a file system error.

Effect

SqlMxHealthCheck stops without performing any verification.

Recovery

Correct the problem reported in the accompanying message, then retry the operation.

SQL 26001

This error occurs when the ANSI name in the RFork for a system schema table does not match with the expected ANSI name, as constructed from the local system name.

26001 ANSI name mismatch for the system schema table table-name. Expected ANSI name is ansi-name-1. Actual ANSI name is ansi-name-2.

Where,

table-name is the object name part of the system schema table;

ansi-name-1 is the expected 3-part ANSI name of the system schema table;

ansi-name-2 is the actual 3-part ANSI name of the system schema table.

Cause

The system was renamed after SQL/MX was initialized. The expected ANSI name is based on the current system name, the actual ANSI name is registered in the resource fork for the system schema table at SQL initialization time.

Effect

SqlMxHealthCheck stops without performing any further verification. It is not possible to access any other system table if this condition occurs.

Recovery

Either rename the system back to its original name when SQL/MX was initialized or use the mxtool goaway utility to remove all SQL/MX database files from the system, and then use the InstallSqlmx script to initialize SQL again. See the NonStop SQL/MX Reference Manual for the use of mxtool goaway, and the NonStop SQL/MX Installation and Upgrade Guide for the use of InstallSqlmx.

SQL 26002

This error occurs when SQL access to some system schema table fails during initial verification of the system schema. SqlMxHealthCheck scans through each of the system schema tables to verify that they are all readable and issues this error message if one of them is not readable.

26002 Fatal system schema verification failure.

Cause

A SQL error occurred during initial system schema verification. The actual error will be described in an accompanying message.

Effect

SqlMxHealthCheck stops without performing further verification.

Recovery

Correct the problem reported in the accompanying message, then retry the operation. If the problem persists contact Hewlett Packard Enterprise support.

SQL 26003

This error occurs when SQL access fails at the catalog level. Candidates are:

  • SCHEMATA access to fetch the list of schemas for the catalog.

  • Definition schema verification for the catalog, for example missing definition schema table.

  • Schema verification for the catalog.

  • User objects verification for each schema.

  • User views verification.

26003 A SQL error occurred during verification of catalog name.

Where name is the ANSI name of the affected catalog.

Cause

A SQL error which prevents further verification of the catalog name has occurred. The actual error will be described in an accompanying message.

Effect

Verification of the catalog name is cancelled and SqlMxHealthCheck continues with the next catalog.

Recovery

Correct the problem reported in the accompanying message, then retry the operation. If the problem persists contact your service provider.

SQL 26004

This error occurs when SQL access fails at the schema level. Candidates are:

  • Definition schema access for objects in the schema

  • Schema verification for the catalog

  • User objects verification for each schema

  • User views verification

Note this can happen during schema level verification as well as during object level verification for objects in the schema.

26004 A SQL error occurred during verification of schema name.

Where name is the two-part ANSI name of the affected schema.

Cause

A SQL error which prevents further verification of schema name has occurred. The actual error will be described in an accompanying message.

Effect

Verification of schema name is cancelled and SqlMxHealthCheck continues with the next schema.

Recovery

Correct the problem reported in the accompanying message, then retry the operation. If the problem persists contact your service provider.

SQL 26005

This error occurs when SQL access fails at the object level. Candidates are:

  • Definition schema access for the object

  • User objects verification for each schema

  • User views verification

This message can be reported for all types of objects, whenever their verification happens. For example, tables, indexes, views, triggers, and so on.

26005 A SQL error occurred during verification of object-type name.

Where,

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

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

Cause

A SQL error occurred while fetching metadata for the affected database object. The actual error will be described in an accompanying message.

Effect

Verification of the affected database object is cancelled and SqlMxHealthCheck continues with the next object.

Recovery

Correct the problem reported in the accompanying message, then retry the operation. If the problem persists contact your service provider.

SQL 26006

This error occurs when a Guardian file system error occurs at the file label level. Candidates are:

  • Partition verification for an object with physical data, for example a table or an index.

  • View label verification for a view.

  • Procedure label verification for a stored procedure.

This message can be reported for all types of objects, whenever their verification happens. For example, tables, indexes, views, triggers, sequence, and so on.

26006 A Guardian file system error error occurred during verification of file label guardian-file-name for object-type name.

Where,

error is a Guardian file system error code;

guardian-file-name is the fully qualified Guardian file name of a label that is related to the affected database object;

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

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

Cause

Guardian file system error error occurred while verifying file label guardian-file-name.

Effect

Verification of the affected file label is cancelled and SqlMxHealthCheck continues with the next file label.

Recovery

Correct the problem, then retry the operation. If the problem persists contact your service provider.

SQL 26007

This error occurs when SQL access fails during remote catalog reference verification.

26007 A SQL error occurred during remote reference verification for catalog name.

Where name is the ANSI name of the affected catalog.

Cause

A SQL error occurred during verification of the remote catalog. The actual error will be described in an accompanying message.

Effect

Verification of remote references is cancelled for the affected catalog and SqlMxHealthCheck continues with the next catalog.

Recovery

Correct the problem reported in the accompanying message, then retry the operation. If the problem persists contact your service provider.

SQL 26008

This error occurs when direct access to a remote anchor file fails.

26008 File system error error occurred on anchor file name during remote reference verification for catalog catalog.

Where,

error is the Guardian file system error code;

name is the fully qualified Guardian file name of a remote SQL/MX anchor file;

catalog is the ANSI name of the affected catalog.

Cause

Access to the remote anchor file failed and returned a file system error.

Effect

The remote reference for the affected catalog cannot be verified on the affected system, SqlMxHealthCheck continues to verify remote references for the catalog, if any.

Recovery

Correct the problem reported in the accompanying message, then retry the operation.

SQL 26009

This error occurs when a SQL access fails. Candidates are:

  • Verification of remote catalog registrations

  • Verification of catalogs

  • Verification of schemas

  • Verification of schema objects

  • Verification of views

26009 A SQL error occurred during verification of object-type. SQL error detail: error-text.

Where,

object-type is one of the following:

  • Remote catalog registrations

  • Catalogs

  • Schemas

  • Schema objects

  • Views

error-text is the actual error text message.

Cause

A SQL error occurred which prevents further verification of an object-type. The actual error will be described in an accompanying message.

Effect

Verification of object is cancelled. SqlMxHealthCheck continues further verification.

Recovery

Correct the problem reported in the accompanying message, then retry the operation. If the problem persists, contact Hewlett Packard Enterprise support.

SQL 26010

This error occurs when a SQL access fails. Candidates are:

  • Verification of schemas

  • Verification of remote catalog registrations

26010 A SQL error occurred during verification of operation for object-type object-name. SQL error detail: error-text.

Where,

operation is registration or verification of schemas;

object-type is catalog for registration and schema verification operations;

object-name is the name of the catalog object;

error-text is the detailed error message text.

Cause

A SQL error occurred which prevents verification of schemas for a catalog or registration of catalog failed. The actual error will be described in an accompanying message.

Effect

Verification of object fails. SqlMxHealthCheck continues further verification.

Recovery

Correct the problem reported in the accompanying message, then retry the operation. If the problem persists, contact Hewlett Packard Enterprise support.

SQL 26012

This error occurs if there is a problem loading the JDBC/MX Type 2 driver.

26012 Could not load the JDBC/MX driver: error.

Where error is an error returned when JDBC/MX Type 2 driver is loaded.

Cause

An error occurred while loading the JDBC/MX Type 2 driver.

Effect

SqlMxHealthCheck tool stops immediately.

Recovery

Before launching the SqlMxHealthCheck tool, ensure that the CLASSPATH environment variable includes the jdbcMx.jar file and _RLD_LIB_PATH environment variable is set to the directory that contains the libJdbcMx.so JDBC/MX DLL file in your environment.

SQL 26013

This error occurs if the required value for the specified argument is missing.

26013 Required value is missing for the argument: argument.

Where argument is the command-line argument to the SqlMxHealthCheck tool.

Cause

The required value for the specified command-line argument is missing.

Effect

The operation fails.

Recovery

Provide a valid value for the argument and retry the operation.

SQL 26014

This error occurs if the specified path for the log file is not valid or the user does not have required access permissions on the specified log file.

26014 An error occurred while accessing the log file log-file. Error detail: error. The messages will be logged to the console.

Where,

log-file is the full path of the file to which the output of the SqlMxHealthCheck tool is logged;

error is the actual error that had occurred while accessing the specified log file.

Cause

An error occurred while creating or accessing the specified log file.

Effect

The output of the SqlMxHealthCheck tool is logged to the console.

Recovery

Correct the problem reported and retry the operation.

SQL 26015

This error occurs if there is a SQL access error during system schema verification.

26015 A SQL error occurred during verification of system schema. SQL error detail: error.

Where error is the actual SQL error occurred.

Cause

A SQL error occurred which prevents further processing of the SqlMxHealthCheck tool.

Effect

Verification of the system schema fails and the SqlMxHealthCheck tool stops.

Recovery

Correct the problem reported and retry the operation. If the problem persists, contact Hewlett Packard Enterprise support.

SQL 26016

This error occurs if there is a file system error during verification of the existence of the owner of a database object.

26016 File system error error occurred during owner existence verification for object-type object-name.

Where,

error is a file system error;

object-type is the type of the database object;

object-name is the name of the database object.

Cause

A file system error occurred during verification of the object owner.

Effect

Verification of an object owner fails.

Recovery

Correct the problem reported, then retry the operation. If the problem persists, contact Hewlett Packard Enterprise support.

SQL 26017

This error occurs if there is a file system error while retrieving the system metadata location.

26017 File system error error occurred on anchor file while retrieving the system metadata location.

Where error is a file system error.

Cause

A file system error occurred on the MX anchor file while retrieving the system metadata location.

Effect

The SqlMxHealthCheck tool cannot proceed further and stops immediately.

Recovery

Correct the problem reported, then retry the operation. If the problem persists, contact Hewlett Packard Enterprise support.

SQL 26018

This error occurs while fetching system schema version.

26018 SQL error error occurred while fetching system schema version. SQL error detail: error-detail.

Where,

error is the SQL error code.

error-detail is message for an occurred error.

Cause

A SQL error occurred while fetching system schema version.

Effect

Fetching of system schema version fails.

Recovery

Correct the error reported and retry the operation. If the problem persists, contact your service provider.

SQL 26019

This error occurs while fetching privilege groups on the system.

26019 SQL error error occurred while fetching privilege groups. SQL error detail: error-detail..

Where,

error is the SQL error code.

error-detail is message for an occurred error.

Cause

A SQL error occurred while fetching privilege groups.

Effect

Fetching of privilege groups on the system fails.

Recovery

Correct the reported error and retry the operation. If the problem persists, contact your service provider.