Serious condition messages

Messages in this category are part of the SqlMxHealthCheck verification output. They indicate that some disruptive condition exists, which is likely to cause failure of the 'mxtool fixrcb' utility and/or the Upgrade and Downgrade SQL commands.

SqlMxHealthCheck reports these messages as "SEVERE" and you must address the reported conditions before attempting a system upgrade or fallback.

Active utility operation

This message is issued when a database object has an associated DDL Lock and the associated utility operation is running.

A operation utility operation is active for object-type object-name.

: Where,
: operation is the type of the utility operation: DUP, FASTCOPY, MODIFY, and so on;
: object-type is the type of the affected database object;
: object-name is the three-part ANSI name of the affected database object.

Cause

This is an indication that a SQL/MX utility operation is active for the object.

Required action

Let the utility run to completion, then resubmit SqlMxHealthCheck for the affected catalog. The following flags may be set: Corrupt, IncompletePartBoundary, UnreclaimedFreespace. Also, one or more partitions may have the Audit flag turned off. This is acceptable while the utility is active.

NOTE:

For many forms of MODIFY, the IncompletePartBoundary and UnreclaimedFreespace remain set after the utility has completed, until required cleanup work has been performed. MODIFY can initiate this cleanup work through the use of the RECLAIM option, or the user can initiate it explicitly through FUP RELOAD.

Inactive utility operation

This message is issued when a database object has an associated DDL Lock and the associated utility operation is NOT running.

A operation utility operation was started for object-type object-name but is not actively running.

Where,

operation is the type of the utility operation: DUP, MODIFY, and so on.

A different message will be issued when the inactive utility is FASTCOPY;

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 SQL/MX utility operation has terminated abnormally.

Required action

Investigate for utility abnormal termination, then use the RECOVER command to either cancel or resume the operation, depending on the conditions. The following flags may be set: Corrupt, IncompletePartBoundary, UnreclaimedFreespace. Also, one or more partitions may have the Audit flag turned off. This is acceptable while the utility is inactive.

After successful recovery, resubmit SqlMxHealthCheck for the affected catalog to verify that no disruptive conditions exist. See the note in "Active utility operation" message.

Inactive FASTCOPY operation

This message is issued when a database object has an associated DDL Lock and the associated FASTCOPY operation is NOT running.

The state of the FASTCOPY utility operation for object-type object-name could not be determined.

: Where,
: object-type is the type of the affected database object;
: object-name is the three-part ANSI name of the affected database object.

Cause

Either the FASTCOPY utility operation has terminated abnormally or the FASTCOPY operation uses explicit index copying, and one or more of the associated FASTCOPY commands has not been issued yet.

Required action

Identify the cause. If the FASTCOPY has terminated abnormally, then use the RECOVER command to either cancel or resume the operation, depending on the conditions. Otherwise, issue the remaining FASTCOPY commands and let them run to completion.

The Corrupt flag may be set and one or more partitions may have the Audit flag turned off. This is acceptable while the FASTCOPY utility is inactive.

Subsequently, resubmit SqlMxHealthCheck for the affected catalog to verify that no disruptive conditions exist.

Corrupt flag set

This message is issued when the 'Corrupt' flag is set for a file label.

The Corrupt flag is 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 Corrupt flag is set in the file label.

Required action

This condition can be ignored if the existence of a utility operation has been reported for the affected database object, as described for the previous messages.

If no such existence has been reported, contact Hewlett Packard Enterprise support.

Partition management flag set

This message is issued when UnreclaimedFreespace or IncompletePartBoundary is set. If both flags are set, then the message is issued twice.

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

: Where,
: flag is the name of the flag. The value can be one of the following: UnreclaimedFreespace, IncompletePartBoundary;
: 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 indicated flag is set in the file label.

Required action

This condition can be ignored if the existence of a MODIFY utility operation has been reported for the affected database object, as described for previous messages.

If no such existence has been reported, use FUP LISTOPENS to verify if the required cleanup work is ongoing for the file. If no ORSERV process has the file open, then issue an FUP RELOAD for the file and let it run to completion. Use FUP STATUS to query the progress.

IMPORTANT:

Unfinished cleanup work will prevent DML access to the affected database object after a release fallback, as well as after a release upgrade from R2.3.x to R3.x.

Broken flag set

This message is issued when the 'Broken' flag is set for a file label.

The Broken flag is 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 Broken flag is set in the file label. This is an indication that there may be internal inconsistencies in the B-tree structure of the file.

Required action

Contact your Hewlett Packard Enterprise support center.

CrashLabel flag is set

This message is issued when the ‘CrashLabel’ flag is set for a file label. A file is in crash-label state if a file label operation was taking place at the time of a total system failure.

The CrashLabel 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 CrashLabel flag is set in the file label.

Required action

Contact your Hewlett Packard Enterprise support center.

TMF related flag set

This message is issued when a TMF related flag setting is detected for a file label. If more than one of the flags are set, then the message is issued more than once.

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

: Where,
: flag is the name of the flag. The value can be one of the following: RedoNeeded, UndoNeeded, RollForwardNeeded, CrashOpen, CrashLabel;
: 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 indicated flag is set in the file label. This prevents all forms of SQL access to the affected object.

Required action

Use TMF File Recovery to recover the affected partition.

Audit flag NOT set

This message is issued when a file label is not audited.

File label Guardian-file-name for object-type object-name is not audited.

: 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 file is not audited.

Required action

This condition can be ignored if the existence of a utility operation has been reported for the affected database object, as described for previous messages.

If no such existence has been reported, contact Hewlett Packard Enterprise support. Files that represent SQL/MX database objects must be audited.

Schema with incompatible version

This message is issued when a schema is not compatible on the current node.

Schema schema has schema version version1; node does not support schema versions higher than version2.

: Where,
: schema is the name of the affected schema;
: version1 is the version of schema;
: node is the three-part ANSI name of the affected database object;
: version2 is the node where the operation is executed.

Cause

The schema has a version that is higher than the highest supported schema version of the node where the operation is executed. A release fallback might have been performed without performing a metadata downgrade while the system was running on the higher release.

Required action

All the database objects defined in the schema are inaccessible. A release upgrade of the local node to a software version that supports the schema's version is required. If the problem persists, contact Hewlett Packard Enterprise support.