Chapter 104 SQL/MX Messages

The messages in this chapter are generated by the HP NonStop SQL/MX subsystem. The subsystem ID displayed by these messages includes SQLMX as the subsystem name.




	NOTE: Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message that is not described in this chapter, see Chapter 15.

500

An error occurred while performing DML on the ResourceFork. CLI Error Message: detail text

Cause SQL/MX received an error on a call to a Data Manipulation Language (DML) statement, such as SELECT or INSERT.

Effect Depending on the situation, this can be a fatal error.

Recovery Use the information in the call-level interface (CLI) error message to diagnose and correct the problem.

501

An internal error occurred. Executable name: name

Process ID: process id

File name: name

Line number: number

Message: message

SQL text: SQL text

Cause SQL/MX encountered an internal error.

Effect SQL/MX is unable to process the statement. If the error occurred within an SQL/MX system process (for example, the SQL/MX compiler or SQL/MX UDR server), that process might have stopped running.

Recovery None. Report the entire event description (executable name, file name, line number, message, and SQL/MX text) to your service provider.

502

An assertion failure occurred. Executable name: name

Process ID: process id

File name: name

Line number: number

Message: message

SQL text: SQL text

Cause Internal error.

Effect SQL/MX encountered an internal error and is unable to process the statement. If the error occurred within an SQL/MX system process (for example, the SQL/MX compiler or SQL/MX UDR server), that process might have stopped running.

Recovery None. Report the entire event description (executable name, file name, line number, message, and SQL/MX text) to your service provider.

503

SQL compiler: Pass one optimization failed. A previously logged assertion failure event may contain more information about the nature of the problem.

Executable name: name Process ID: process id

Cause The SQL/MX compiler received an error at its first stage of optimization.

Effect SQL/MX is unable to prepare the statement.

Recovery Use other assertion failure events to diagnose and correct the problem.

504

SQL compiler: Optimization at pass two or higher failed. Execution will use the plan generated at pass one instead.

Executable name: name Process ID: process id

Cause The SQL/MX compiler received an error at a later stage of optimization.

Effect SQL/MX uses the plan generated by the earlier optimization step.

Recovery This is an informational message only; no corrective action is needed.

505

Automatic recompilation has occurred at runtime. Statement identifier: statement id

Module name: module name

`statement id`	is the identifier of the statement that was recompiled.
`module name`	is the name of the module where the statement belongs.

Cause A condition in the query or table caused an autorecompilation. The similarity check has failed.

Effect The control query default for automatic recompilation was set to ON, so the program was recompiled.

Recovery Determine why the similarity check failed. Check for warning messages and troubleshoot accordingly.

506

Memory assigned to a statement in close state was reclaimed due to memory pressure. This will increase the execution time when the statement is reexecuted. Subsequent reclaim of assigned memory to any statement will NOT be logged.

Free SQL/MX Memory: number bytes

Total SQL/MX Memory allocated: number bytes

Number of contexts: number

Total number of statements in all contexts: number

number

is the numeric value of the given field.

Cause This event usually is generated in a Java environment when many SQL statements are pooled across many SQL contexts. The event is written when the SQL/MX master executor is under memory pressure for the first time. Memory pressure occurs when all of the following conditions are present:

There are multiple SQL/MX segments.
The total number of memory segments allocated is more than 128 MB.
The last segment allocated is less than 128 MB, and free memory is less than half the size of the total size allocated.

Effect Memory allocated for execution of the least recently used SQL statement is deallocated to make way for new SQL statements. The performance of the SQL statement whose execution memory is deallocated is affected. SQL/MX remains functional regardless of this event.

Recovery Try to leave more virtual memory for SQL/MX, which requires you to reserve less virtual memory for Java.

507

SQL/MX scratch file I/O cannot use the following disk.

Disk Name: disk-name

Percentage of disk free space: [ percent-free-space | not applicable ]

Disk Error: low-level-disk-error

`disk-name`	is the device name of the disk.
`percent-free-space`	is the unused disk space represented as a percentage.
`low-level-disk-error`	is the disk error number.

Cause This informational message is generated when:

SQL/MX stops using a disk because the free-space threshold has fallen below the percentage specified by the SCRATCH_FREESPACE_THRSHOLD_PERCENT attribute of the SYSTEM_DEFAULTS table.
SQL/MX encounters a disk error and cannot use the disk for scratch space.

Effect None

Recovery This is an informational message only; no corrective action is needed.

521

The MODIFY utility operation command started on object object-name.

`operation`	is the type of operation (ADD, DROP, MOVE, REUSE, RENAME, REPARTITION, REORG) performed by the MODIFY utility.
`object`	is a table or an index.
`object-name`	is the ANSI name of the object.

Cause The MODIFY Partition Management utility finished its syntax checks and started executing.

Effect The SQL operation started.

Recovery This is an informational message only; no corrective action is needed.

522

The target partition-name created.

partition-name

is the file name of the target partition.

Cause The target partition described in this message was created offline. Offline means the target partition is not exposed to the user. This message repeats for each new target partition created.

Effect The new partition is ready to be used for MODIFY Partition Management utility operations.

Recovery This is an informational message only; no corrective action is needed.

523

All target partitions have been created. Time to create targets: interval secs.

interval

is the interval needed to create all the target partitions.

Cause All target partitions have been created.

Effect The newly created partitions can be loaded with data by the MODIFY Partition Management utility.

Recovery This is an informational message only; no corrective action is needed.

524

A data copy started using Direct Bulk I/O.

Cause The data copy using direct bulk I/O has been started.

Effect In this phase, data is taken from existing partitions and put into the newly created target partitions. A shared read lock is obtained in some cases on source partitions.

Recovery This is an informational message only; no corrective action is needed.

525

A data copy started using Unaudited Row Copy.

Cause The data copy using unaudited row copy has been started.

Effect In this phase, data is taken from existing partitions and put into the newly created target partitions. A shared read lock is obtained in some cases on source partitions.

Recovery This is an informational message only; no corrective action is needed.

526

A data copy started using Audited Row Copy.

Cause The data copy using audited row copy has been started.

Effect In this phase, data is taken from existing partitions and put into the newly created target partitions. A shared read lock is obtained in some cases on source partitions.

Recovery This is an informational message only; no corrective action is needed.

527

** Data copy status ** Time since last status: interval secs.

Data copied : units-read unit-name

`interval`	is the interval since the last message for the request was processed.
`units-read`	is a running count of the number of units read during the load phase. Units for data copy for direct bulk I/O are in bytes and for row copy, in records.
`unit-name`	is bytes for direct bulk I/O and records for row copy.

Cause The progress of the data copy operation is indicated at five-minute intervals.

Recovery This is an informational message only; no corrective action is needed.

528

Data copy completed Time since last status: interval secs.

Total data copied : units-read unit-name.

`interval`	is the interval since the last message for the request was processed.
`units-read`	is a running count of the number of units read during the load phase. Units for data copy for drect bulk I/O are in bytes and for row copy, in records.
`unit-name`	is bytes for direct bulk I/O and records for row copy.

Cause The data copy operation finished.

Effect All selected records that exist in the source partitions are coped to the new location.

Recovery This is an informational message only; no corrective action is needed.

529

Online dump is allowed for partition-name.

partition-name

is the file name of the partition that can be dumped.

Cause An online dump can be taken of the named partition. (This message is only displayed for objects that currently have online dumps.)

Effect An online dump can be taken before the SQL command is finished, which eliminates any potential data loss.

Recovery This is an informational message only; no corrective action is needed.

530

All partitions that require online dumps have been specified.

Cause All partitions affected by this operation have been identified.

Effect No more online dumps are needed.

Recovery This is an informational message only; no corrective action is needed.

531

The commit phase for the MODIFY utility operation has begun.

Cause The commit phase for the MODIFY Partition Management utility operation started.

Effect The MODIFY Partition Management utility operation now requires exclusive access to all source and target partitions.

Recovery This is an informational message only; no corrective action is needed.

532

A file lock was requested for exclusive access of partition: partition-name.

partition-name

is the file name of the partition that requires the lock.

Cause An exclusive file lock was requested for the source partition.

Effect Other applications cannot access the source partition.

Recovery This is an informational message only; no corrective action is needed.

533

All exclusive file locks have been obtained.

Cause All source partitions involved in the MODIFY Partition Management utility operation have been locked.

Effect Other applications cannot access any partition involved in the MODIFY Partition Management utility operation.

Recovery This is an informational message only; no corrective action is needed.

534

All partition labels have been updated.

Cause All partition labels affected by the operation were updated.

Effect None

Recovery This is an informational message only; no corrective action is needed.

535

A FUP RELOAD operation has been started to delete data from source partition partition-name.

partition-name

is the file name of the partition from which data is deleted.

Cause The MODIFY Partition Management utility issued a request to the FUP RELOAD utility asynchronously to delete records from the source partition that were copied to the new location.

Effect All selected records that were copied to the new location will be deleted from the source partition by the FUP RELOAD utility.

Recovery This is an informational message only; no corrective action is needed.

536

Row Hiding is turned on for partition-name.

partition-name

is the file name of the partition on which Row Hiding is turned on.

Cause Row Hiding is turned on so that only one copy of a given row is visible to the user during the MODIFY Partition Management utility operation.

Effect Only one copy of a given row is visible to the user.

Recovery This is an informational message only; no corrective action is needed.

537

The MODIFY utility operation command has completed on object object-name.

`operation`	is the type of operation (ADD, DROP, MOVE, REUSE, RENAME, REPARTITION, REORG) performed by the MODIFY utility.
`object-name`	is the ANSI name of the object.
`object`	is a table or an index.

Cause The MODIFY utility request is finished.

Effect The new table or index is now available.

Recovery This is an informational message only; no corrective action is needed.

538

The MODIFY utility operation command returning to caller. SQLCODE returned: sqlcode. Message Text: error-text.

`operation`	is the type of operation (ADD, DROP, MOVE, REUSE, RENAME, REPARTITION, REORG) performed by the MODIFY utility.
`sqlcode`	is the error code of the first error that is reported in the diagnostics area of SQL/MX.
`error-text`	describes the error, which is returned in the diagnostics area of SQL/MX. The MODIFY utility can report up to a maximum of five errors.

Cause The MODIFY utility operation has failed.

Effect All resources in use have been freed.

Recovery See the SQL/MX Messages Manual to determine the appropriate recovery for the SQLCODE value. Correct the SQL error and reissue the request.

539

SQL/MX audit fix-up process initialized. Time to perform initialization: interval secs.

interval

is the interval since the last status message for a given audit fix-up process servicing the request.

Cause The audit fix-up process has been initialized.

Effect The audit fix-up process is ready to accept fix-up requests.

Recovery Informational message only; no corrective action is needed.

540

** SQL/MX audit fix-up process status ** Time since last status : interval secs.

Distance to audit EOF : aud-distance-to-eof kbytes.

Records read : aud^recs^read recs.

Records queued for redo : aud^recs^redo recs.

Read rate : aud^read^rate bytes/sec.

Redo queueing rate : {+|-} aud^redo^rate bytes/sec.

Progress rate : {+|-} aud^prog^rate bytes/sec.

`interval`	is the interval since the last message for the request was processed.
`aud-distance-to-eof`	is a computed amount of audit information, logically merged from one or more audit files, determined to be necessary for the fix-up operation.
`aud`^`recs`^`read`	is a running total of the number of audit records read during the audit fix-up operation.
`aud`^`recs`^`redo`	is a running total of the number of audit records redone during the audit fix-up operation.
`aud`^`read`^`rate`	is the rate, in bytes per second, at which audit information was generated in the audit trails since the last status report.
`aud`^`redo`^`rate`	is the rate, in bytes per second, at which audit information was redone during the last reporting period.
`aud`^`prog`^`rate`	is the rate, in bytes per second, at which an operation is approaching the logical (merged) audit end-of-file (EOF) during the last reporting period. This number can be negative and is always negative during the load phase of an operation. A negative number means that the audit trail is being created faster than the fix-up process can use it. The number might not be available for the first few status reports, in which case it is represented as a question mark (?).

Cause The progress of the audit fix-up operation is indicated at five-minute intervals.

Effect None

Recovery Informational message only; no corrective action is needed. Use this information to predict when the operation will finish.

541

SQL/MX audit fix-up process aud-num started.

aud-num

is the ordinal position of an audit fix-up request. Several audit fix-up requests can be made through the execution of an operation that uses WITH SHARED ACCESS. There are always at least two requests.

Cause An audit fix-up application request was made.

Effect The audit fix-up process has started.

Recovery Informational message only; no corrective action is needed.

542

SQL/MX audit fix-up process aud-num completed. Duration: interval secs.

`aud-num`	is the ordinal position of an audit fix-up request.
`interval`	is the interval since the last message for the request was processed.

Cause An audit fix-up application request is finished.

Effect The audit fix-up process has received a request and responded to it.

Recovery Informational message only; no corrective action is needed.

543

SQL/MX audit fix-up process terminated.

Cause The audit fix-up function is finished.

Effect The audit fix-up process stops.

Recovery Informational message only; no corrective action is needed.

551

The POPULATE INDEX for index, index-name : Started.

index-name

is the ANSI name of the index.

Cause The POPULATE INDEX utility finished its initialization stage and started executing.

Effect The SQL operation started.

Recovery This is an informational message only; no corrective action is needed.

552

The POPULATE INDEX for index, index-name : Ended.

index-name

is the ANSI name of the index.

Cause The POPULATE INDEX utility finished executing.

Effect The SQL operation ended.

Recovery This is an informational message only; no corrective action is needed.

553

The POPULATE INDEX command failed. SQLCODE returned: sql-code.

MessageText: error-text

`sql-code`	is the error code of the first error that is reported in the diagnostics area of NonStop SQL/MX.
`error-text`	describes the error found. This information is reported in the diagnostics area of NonStop SQL/MX.

Cause The POPULATE INDEX utility operation failed.

Effect The index has not been populated.

Recovery To determine the appropriate recovery for the SQLCODE value, see the NonStop SQL/MX Messages Manual. Correct the SQL error and reissue the request.

554

The POPULATE INDEX for index, index-name : Commit Phase Started.

index-name

is the ANSI name of the index.

Cause The commit phase for the POPULATE INDEX utility operation began.

Effect The SQL operation is in progress.

Recovery This is an informational message only; no corrective action is needed.

555

The POPULATE INDEX for index, index-name : Entering Recovery Mode.

index-name

is the ANSI name of the index.

Cause The POPULATE INDEX utility encountered an error and is attempting to recover the object.

Effect The POPULATE INDEX utility failed.

Recovery This is an informational message only; further messages will be issued by the POPULATE INDEX utility.

556

The POPULATE INDEX for index, index-name : Audit Compress Attribute Altered.

index-name

is the ANSI name of the index.

Cause The POPULATE INDEX utility altered the Audit Compress attribute of the index.

Effect The POPULATE INDEX utility is executing.

Recovery This is an informational message only; no corrective action is needed.

557

The POPULATE INDEX for index, index-name : MAXEXTENTS Attribute Altered.

index-name

is the ANSI name of the index.

Cause The POPULATE INDEX utility altered the MAXEXTENTS attribute of the index.

Effect The POPULATE INDEX utility is executing in initialize phase.

Recovery This is an informational message only; no corrective action is needed.

558

The POPULATE INDEX for index, index-name : Commit Phase Ended.

index-name

is the ANSI name of the index.

Cause The commit phase for the POPULATE INDEX utility operation ended.

Effect The POPULATE INDEX utility operation is in progress.

Recovery This is an informational message only; no corrective action is needed.

561

The operation has started

operation

is the normalized operation text that the user entered.

Cause The actual processing of the operation started. No errors were detected during the initialization phase. If operation begins with RECOVER, a recovery of a previous operation started.

Effect The affected schemas have been marked as having an upgrade or downgrade in progress. No DDL or utility operation can create, alter, or drop objects in the affected schemas.

Recovery This informational message is issued only to the primary event collector ($0) on the segment where the command was executed. No corrective action is needed. If you want this event and other upgrade and downgrade events distributed to other segments in the network, configure forwarding distributors.

562

The operation has completed

operation

is the normalized operation text that the user entered.

Cause The operation completed successfully. The affected schemas are no longer marked as having an upgrade or downgrade in progress.

Effect DDL or utility operations can again create, alter, and drop objects in the affected schemas.

Recovery Informational message only; no corrective action is needed.

563

Schema schema has been upgraded from version source to version target

`schema`	is the ANSI name of the affected schema.
`source`	is the version of the `schema` before the upgrade.
`target`	is the version of the `schema` after the upgrade.

Cause The mentioned schema was upgraded to the target version as part of an UPGRADE command.

Effect The UPGRADE command might be active when this event is issued. However, the schema version was changed for schema.

Recovery Informational message only; no corrective action is needed.

564

Schema schema has been downgraded from version source to version target

`schema`	is the ANSI name of the affected schema.
`source`	is the version of the `schema` before the downgrade.
`target`	is the version of the `schema` after the downgrade.

Cause The mentioned schema was downgraded to the target version as part of a DOWNGRADE command.

Effect The DOWNGRADE command might be active when this event is issued. However, the schema version was changed for schema.

Recovery Informational message only; no corrective action is needed.

565

Schema schema will be upgraded from version source to version target

`schema`	is the ANSI name of the affected schema.
`source`	is the version of the `schema` before the upgrade.
`target`	is the target version of the upgrade.

Cause The mentioned schema will be upgraded to the target version as part of an UPGRADE command.

Effect The catalog is identified by previous event 561. Event 565 is issued before the actual upgrade, but event 563 is issued after the schema is actually upgraded.

Recovery Informational message only; no corrective action is needed.

566

Schema schema will be downgraded from version source to version target

`schema`	is the ANSI name of the affected schema.
`source`	is the version of the `schema` before the downgrade.
`target`	is the target version of the downgrade.

Cause The mentioned schema will be downgraded to the target version as part of a DOWNGRADE command. The catalog is identified by previous event 561.

Effect Event 566 is issued before the actual downgrade, but 564 is issued after the schema is actually downgraded.

Recovery Informational message; no corrective action is needed.

567

Creating version target definition schema for catalog catalog

`target`	is the target version of an upgrade or downgrade operation.
`catalog`	is the ANSI name of a catalog that is affected by an upgrade or downgrade operation.

Cause A definition schema of version target for catalog catalog is required to run an upgrade or downgrade operation. target is the target version of that operation.

Effect None.

Recovery Informational message; no corrective action is needed.

568

Upgrading version source metadata to version target for affected schemas in catalog catalog

`source`	is one of the source versions of an upgrade operation.
`target`	is the target version of an upgrade operation.
`catalog`	is the ANSI name of a catalog that is affected by an upgrade operation.

Cause The metadata copy phase of an upgrade operation begins for affected schemas of version source in catalog catalog.

Effect None.

Recovery Informational message; no corrective action is needed.

569

Downgrading version source metadata to version target for affected schemas in catalog catalog

`source`	is one of the source versions of a downgrade operation.
`target`	is the target version of a downgrade operation.
`catalog`	is the ANSI name of a catalog that is affected by a downgrade operation.

Cause The metadata copy phase of a downgrade operation begins for affected schemas of version source in catalog catalog.

Effect None.

Recovery Informational message; no corrective action is needed.

570

Set schema version to target for schema

`target`	is either the target version of an upgrade or downgrade operation or the source version of a RECOVER ... CANCEL of an upgrade or downgrade operation.
`schema`	is the ANSI name of a schema that is affected by an upgrade or downgrade operation.

Cause Either the cut-over phase of an upgrade or downgrade operation or a RECOVER ... CANCEL operation updated the schema version of schema.

Effect None.

Recovery Informational message; no corrective action is needed.

571

Updating file labels for affected schemas in catalog catalog

catalog

is the ANSI name of a catalog that is affected by an upgrade or downgrade operation.

Cause The update file labels phase of an upgrade or downgrade operation begins for affected schemas in catalog catalog.

Effect None.

Recovery Informational message; no corrective action is needed.

572

Remove version version metadata for affected schemas in catalog catalog

`version`	is either the source version of an upgrade or downgrade operation or the target version of a RECOVER ... CANCEL operation.
`catalog`	is the ANSI name of a catalog that is affected by an upgrade or downgrade operation.

Cause Either the metadata removal phase of an upgrade or downgrade operation or a RECOVER ... CANCEL operation begins for affected schemas in catalog catalog.

Effect None.

Recovery Informational message; no corrective action is needed.

573

Remove definition-schema

definition-schema

is either a definition schema that became empty because of an upgrade or downgrade operation or the target version of a RECOVER ... CANCEL operation.

Cause Either the final phase of an upgrade or downgrade operation or a RECOVER ... CANCEL operation determined that definition-schema became empty.

Effect None.

Recovery Informational message; no corrective action is needed.

574

Canceling original command operation

operation

is the normalized operation text that the user entered.

Cause A RECOVER ... CANCEL was issued for the operation.

Effect None.

Recovery Informational message; no corrective action is needed.

575

Resuming original command operation

operation

is the normalized operation text that the user entered.

Cause A RECOVER ... RESUME request was issued for the operation.

Effect None.

Recovery Informational message; no corrective action is needed.

576

The upgrade of schema schema from version source to version target will be canceled

`schema`	is the ANSI name of the affected schema.
`source`	is the version of the `schema` before the upgrade.
`target`	is the target version of the upgrade.

Cause A RECOVER ... CANCEL operation was issued for an original upgrade operation.

Effect The version of the affected schema is set back to the value it had before the upgrade.

Recovery Informational message; no corrective action is needed.

577

The downgrade of schema schema from version source to version target will be canceled

`schema`	is the ANSI name of the affected schema.
`source`	is the version of the `schema` before the downgrade.
`target`	is the target version of the downgrade.

Cause A RECOVER ... CANCEL operation was issued for an original downgrade operation.

Effect The version of the affected schema is set back to the value it had before the downgrade.

Recovery Informational message; no corrective action is needed.

578

The upgrade of schema schema from version source to version target was canceled

`schema`	is the ANSI name of the affected schema.
`source`	is the version of the `schema` before the upgrade.
`target`	is the target version of the upgrade.

Cause A RECOVER ... CANCEL operation was issued for an original upgrade operation.

Effect The version of the affected schema is set back to the value it had before the upgrade.

Recovery Informational message; no corrective action is needed.

579

The downgrade of schema schema from version source to version target was canceled

`schema`	is the ANSI name of the affected schema.
`source`	is the version of the `schema` before the downgrade.
`target`	is the target version of the downgrade.

Cause A RECOVER ... CANCEL operation was issued for an original downgrade operation.

Effect The version of the affected schema is set back to the value it had before the downgrade.

Recovery Informational message; no corrective action is needed.

580

Upgrade of version source metadata to version target for affected schemas in catalog catalog is not required

`source`	is one of the source versions of an upgrade operation.
`target`	is the target version of an upgrade operation.
`catalog`	is the ANSI name of a catalog that is affected by an upgrade operation.

Cause (1) When issued as part of a RECOVER ... CANCEL of an original downgrade operation, the original processing terminated before touching the original source version metadata. (2) When issued as part of a RECOVER ... RESUME of an original upgrade operation, the original processing terminated after the upgrade of the original source version metadata was complete.

Effect None.

Recovery Informational message; no corrective action is needed. If Cause 2, the resume processing does not need to do anything.

581

Downgrade of version source metadata to version target for affected schemas in catalog catalog is not required

`source`	is one of the source versions of a downgrade operation.
`target`	is the target version of a downgrade operation.
`catalog`	is the ANSI name of a catalog that is affected by a downgrade operation.

Cause (1) When issued as part of a RECOVER ... CANCEL of an original upgrade operation, the original processing terminated before the original source version metadata was removed. (2) When issued as part of a RECOVER ... RESUME of an original downgrade operation, the original processing terminated after the copy of the source version metadata was complete.

Effect None.

Recovery Informational message; no corrective action is needed. If Cause 2, the resume processing does not need to do anything.

582

Set schema version to target for schema is not required.

`target`	is either the target version of a RECOVER ... RESUME of an upgrade or downgrade operation or the source version of a RECOVER ... CANCEL of an upgrade or downgrade operation.
`schema`	is the ANSI name of a schema that is affected by an upgrade or downgrade operation.

Cause (1) When issued as part of a RECOVER ... CANCEL of an original operation, the original processing terminated before the schema version was set to the target version. Therefore, there is nothing to recover. (2) When issued as part of a RECOVER ... RESUME of an original operation, the original processing terminated after the schema version was set to the target version.

Effect None.

Recovery Informational message; no corrective action is needed. If Cause 2, the resume processing does not need to do anything.

583

Update file labels for affected schemas in catalog catalog is not required

catalog

is the ANSI name of a catalog that is affected by an upgrade or downgrade operation.

Cause (1) When issued as part of a RECOVER ... CANCEL of an original operation, the original processing terminated before any file labels were updated. (2) When issued as part of a RECOVER ... RESUME of an original operation, the original processing terminated after all file labels were updated.

Effect None.

Recovery Informational message; no corrective action is needed. If Cause 2, the resume processing does not need to do anything.

584

Remove version version metadata for affected schemas in catalog catalog is not required

`version`	is either the source version of an upgrade or downgrade operation or the target version of a RECOVER ... CANCEL operation.
`catalog`	is the ANSI name of a catalog that is affected by an upgrade or downgrade operation.

Cause (1) When issued as part of a RECOVER ... CANCEL of an original operation, the original processing terminated before the copying of source metadata started. (2) When issued as part of a RECOVER ... RESUME of an original operation, the original processing terminated after the target version metadata was removed.

Effect None.

Recovery Informational message; no corrective action is needed. If Cause 2, the resume processing does not need to do anything.

585

The upgrade of schema schema from version source to version target is complete

`schema`	is the ANSI name of the affected schema.
`source`	is the version of the `schema` before the upgrade.
`target`	is the target version of the upgrade.

Cause A RECOVER ... RESUME operation was issued for an upgrade operation.

Effect The original processing terminated after the named schema was fully upgraded.

Recovery Informational message; no corrective action is needed.

586

The downgrade of schema schema from version source to version target is complete

`schema`	is the ANSI name of the affected schema.
`source`	is the version of the `schema` before the downgrade.
`target`	is the target version of the downgrade.

Cause A RECOVER ... RESUME operation was issued for a downgrade operation.

Effect The original processing terminated after the named schema was fully downgraded.

Recovery Informational message; no corrective action is needed.

587

The upgrade of schema schema from version source to version target was never started

`schema`	is the ANSI name of the affected schema.
`source`	is the version of the `schema` before the upgrade.
`target`	is the target version of the upgrade.

Cause A RECOVER ... CANCEL operation was issued for an upgrade operation.

Effect The original processing terminated before the named schema was affected.

Recovery Informational message; no corrective action is needed.

588

The downgrade of schema schema from version source to version target was never started

`schema`	is the ANSI name of the affected schema.
`source`	is the version of the `schema` before the downgrade.
`target`	is the target version of the downgrade.

Cause A RECOVER ... CANCEL operation was issued for a downgrade operation.

Effect The original processing terminated before the named schema was affected.

Recovery Informational message; no corrective action is needed.

701

ZMXBRDLL: An internal error occurred.

Executable Name: name

Process Name: name

File Name: number

Message: message

message

is the actual text of the message. Depending on the context, message may be:

SEGMENT_DEALLOCATE_ failed with error = error-number and error detail = error-detail-number in API-name.
The version of BR2 and ZMXBRDLL does not match. The BR2 version is version-no and the ZMXBRDLL version is version-no.
ZMXBRDLL was not able to allocate an extended memory segment. SEGMENT_ALLOCATE_ returned error error-number, error detail error-detail-number.
MXAGENT process could not be created - Operating system error error-number, TPC error error-number, TPC error detail error-detail-number. See Guardian system procedure PROCESS_SPAWN_ for details.
MXAGENT process connect failed with error = error-number.
MXAGENT process communication error, sendAndReceive failed with error error-number in API-name.
Request structure version mismatch error in API-name.
Reply structure version mismatch error in API-name.

Cause An internal error encountered during ZMXBRDLL.

Effect Due to an internal error in the ZMXBRDLL process the backup/restore operation was not performed by BR2.

Recovery None. If the error persists, contact your service provider and provide all relevant information:

Event descriptions (executable name, process name, file name, line number and message)
Details from the message or messages generated

Most of the error messages are related to incompatible version of BR2 (T0744) and MxAgent (T1057) being used or MXAGENT file not found or MXAGENT process abended, etc.

702

MXAGENT: An internal error occurred.

Executable Name: name

Process Name: name

File Name: name

Line Number: number

Message: message

message

is the actual text of the message. Depending on the context, the message can be:

MXAGENT process cannot share the segment id with the parent process, SEGMENT_ALLOCATE_ failed with error error-number
Parent process’ pin cannot be identified by MXAGENT Process, PROCESSHANDLE_DECOMPOSE_ failed with error error-number

Cause An internal error encountered during MXAGENT process.

Effect Due to an internal error in the MXAGENT process the backup/restore operation was not performed by BR2.

Recovery None. If the error persists, contact your service provider and provide all relevant information:

Event descriptions (executable name, process name, file name, line number, and message)
Details from the message or messages generated

1154

Partition Overlay Support (POS) could not create object‑type object-name, as the table size is too big to fit on the system.

`object-type`	is the type of the object.
`object-name`	is the ANSI name of the object.

Cause SQL could not create the object as the requested table size is bigger than the total amount of disk space available on the system.

Effect No SQL operation failed.

Recovery Check that the table size requested is big enough to fit on the system, then retry the statement.

1158

A subsystem problem occurred on the system. Resource Name: name Problem Description: description

`name`	is the name of the system resource experiencing the problem. The name is the value of ZOSM-TKN-RESOURCE-NAME, which is a string token to describe the resource that has the problem. The string token contains a comma-separated list of all the subject tokens from the original event.
`description`	is the description of the problem. The description is the value of ZOSM‑TKN‑SPECIFIC-PROBLEM, which is a string token to describe the problem. The string token contains the event text message from the original event.

Cause Varies; see Recovery.

Effect Varies.

Recovery If the problem description does not provide adequate recovery information, locate the resource in the OSM Service Connection and look for alarm details or problem attribute values for more information.

15514

Change password broadcast failed, error class error-class, error error-detail, user user-name

error-class

The error classes are:

Error Class	Error Detail Source and Description
2	Safeguard Error— Error detail contains a Safeguard error number.
3	File System Error—Error detail contains a Guardian file system error number.
4	Internal Error—Error detail contains a Security Process (NSP) error number.
5	Process Information Error—Error detail contains a Process Information error number.
6	SPI Error—Error detail contains a Subsystem Programmatic Interface (SPI) error number.

error-detail

The error detail provided by the subsystem identified by error-class. For error-detail of Error Class 4, Internal Error, see Cause.

user-name

The user name of the user who initiated the password change request.

Cause For all error classes except 4, Internal Error, error-detail contains an error number specific to the subsystem. For error class 4, Internal Error, see the error detail information in this table.

Error Detail	Description
10000	Generic Exception—A general exception occurred.
10001	Backup Communication Failure—The primary process was unable to communicate with the backup process.
10002	Checkpoint Too Big—The primary process attempted to send a checkpoint message greater than the maximum I/O size.
10003	Error Getting Primary Info—An error occurred on an attempt to get process information about the primary process.
10004	Exceeded Recovery Limit—The primary process was unable to restart the backup.
10005	Inconsistent Object Maps—An internal consistency check failed.
10006	Memory Allocation Failure—The NSP was unable to obtain the memory necessary to continue operation.
10007	NULL Pointer—An attempt was made to use a pointer that was not initialized.
10008	Receive Failure—An unexpected I/O error occurred on $RECEIVE.
10009	Unable To Obtain Primary CPU—A failure occurred on an attempt to retrieve the number of the primary CPU.
10010	Unexpected System Error—An unexpected error was returned from a call to a system procedure.
10011	Unknown Exception—An exception occurred, but the type of the exception could not be obtained.
10012	Unnamed Process—An attempt was made to start the NSP as an unnamed process.
10013	Unrecognized Pair Info—An unexpected value was encountered on an attempt to obtain process pair information.
20000	Invalid Object Type—An attempt was made to create an object of unknown type.
20001	Invalid Process State—An attempt was made to enter an invalid state in the NSP state machine.
20002	Invalid Request Type—The NSP received a request of invalid type.
20003	Parameter Error—The NSP received a request in which one or more of the parameters were incorrect.
20004	Request too Short—The NSP received a request that was too short to contain any known operation.
20005	Unable to Get Segment Info—The NSP encountered an unexpected error on an attempt to obtain information on the system segments.
20006	Unhandled Request Version—The NSP was unable to handle the version of the request received.
20007	Unable to Get User Info—The NSP was unable get the information for the userid for which the password change was requested.

Effect The password for user user-name will not be the same across all segments of the system. Therefore, the old password might work on some segments and the new password might work on other segments (the system is inconsistent).

Recovery Contact the security administrator for the customer and have the customer use DB Admin to assign a new password to the user-name. The newly assigned password should be different from the old password and the new password specified in the password change request. Either of these passwords might be rejected on some segments if password history is set.