Chapter 103 SQL/MP Messages

The messages in this chapter are sent by the Structured Query Language/Massively Parallel (SQL/MP) subsystem. Currently there are two types of messages generated by NonStop SQL/MP: those generated by the MODIFY DICTIONARY utility and those resulting from DDL operations using the WITH SHARED ACCESS option. The subsystem ID displayed by these messages includes SQL as the subsystem name.




	NOTE: Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message, see Chapter 15.

op^type command started

op^type

is the name of the operation as specified in the NAME option of the statement that started the operation.

Cause The named SQL Data Definition Language (DDL) has finished its syntax checks and has started executing.

Effect The SQL operation has started.

Recovery Informational message only; no corrective action is needed.

Target created-file created

created-file

is the name of the target partition.

Cause The target partition described in this message has been created. This message repeats for each new target partition created.

Effect The new partition is ready to be used in the SQL Data Definition Language (DDL) operation.

Recovery Informational message only; no corrective action is needed.

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

interval

is the interval since the last message for the request was processed.

Cause All target partitions have been created.

Effect The newly created partitions can be loaded with data.

Recovery Informational message only; no corrective action is needed.

Data Copy Started

Cause The data-copy operation has started.

Effect In this phase, data is taken from existing objects and put into the newly created target partitions.

Recovery Informational message only; no corrective action is needed.

** Data Copy Status ** Time since last status: interval secs Data records copied : recs-read recs

`interval`	is the interval since the last message for the request was processed.
`recs-read`	is a running count of the number of records read during the load phase (since the last status message was provided).

Cause The progress of the data-copy operation is indicated at five-minute intervals. (Some SQL Data Definition Language (DDL) requests, such as the CREATE INDEX statement, do not generate this message.)

Effect None

Recovery Informational message only; no corrective action is needed.

Data Copy Completed Time since last status: interval secs [Total records copied : recs-read recs]

`interval`	is the interval since the last message for the request was processed.
`recs-read`	is a running count of the number of records read during the load phase.

Cause The data-copy operation has finished. (Some SQL Data Definition Language (DDL) requests, such as the CREATE INDEX statement, do not generate the optional portion of the message or the total records copied.)

Effect All records that exist in the source partitions have been copied to the new location.

Recovery Informational message only; no corrective action is needed.

Online dump allowed for dump-file

dump-file

is the 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 Informational message only; no corrective action is needed.

All partitions that require online dumps have been specified

Cause All partitions that are affected by this operation have been identified.

Effect No more online dumps are needed.

Recovery Informational message only; no corrective action is needed.

Commit phase has begun

Cause The commit phase for the SQL operation has started.

Effect The SQL Data Definition Language (DDL) operation now requires exclusive access to all source and target partitions.

Recovery Informational message only; no corrective action is needed.

File lock requested for partition: source-file Time since last event interval secs

`source-file`	is the name of the partition that requires the lock.
`interval`	is the interval since the last message for the request was processed.

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

Effect Other applications cannot access the source partition.

Recovery Informational message only; no corrective action is needed.

All file locks have been obtained Time since last event interval secs

interval

is the interval since the last message for the request was processed.

Cause The source partition has been locked.

Effect Other applications cannot access any partition involved in the DDL operation.

Recovery Informational message only; no corrective action is needed.

All partition labels have been updated Time since last event interval secs

interval

is the interval since the last message for the request was processed.

Cause All partition labels affected by the operation have been updated.

Effect None

Recovery Informational message only; no corrective action is needed.

op^type command has completed

op^type

is the name of the operation as specified in the NAME option of the statement that started the operation.

Cause The Data Definition Language (DDL) request is finished.

Effect The new object is now available.

Recovery Informational message only; no corrective action is needed.

op^type command returning to caller SQLCODE returned: sqlcode Message Text: errortext

`op^type`	is the name of the operation as specified in the NAME option of the statement that started the operation.
`sqlcode`	is the SQL error that is reported as the primary SQL communications area (SQLCA) error.
`errortext`	is the error text found in the SQLCA that corresponds to the SQLCODE returned.

Cause The SQL Data Definition Language (DDL) operation has failed.

Effect All resources in use have been freed.

Recovery For more information, see the NonStop SQL/MP Messages Manual or use the ERROR command in SQLCI to determine the appropriate corrective action for the SQLCODE value. Correct the SQL error and reissue the request.

Cannot report events to collector

collector

is the name of the Event Management Service (EMS) collector that was unavailable.

Cause The specified alternate collector is not available.

Effect Messages are no longer sent to the specified alternate collector.

Recovery Check to see if the alternate collector is functioning properly.

Reporting events resumed on collector

collector

is the name of the Event Management Service (EMS) collector that was unavailable.

Cause The local primary collector received a message, but the specified alternate collector is now accepting messages.

Effect Messages for the SQL Data Definition Language (DDL) command are being processed by the specified alternate collector.

Recovery Informational message only; no corrective action is needed.

The node number old-node-number in the label-info in the file label of object-name modify-status [to new-node-number]

old-node-number

is the node number specified in the REPLACE NODE NUMBER clause of the MODIFY [DICTIONARY] LABEL command.

label-info

is the type of information stored in the file label of the object. label-info can have the following values:

catalog name base table name partition array collation array index map array

object-name

is the name of the object specified in the MODIFY [DICTIONARY] LABEL command.

modify-status

reports the status of the MODIFY [DICTIONARY] LABEL operation. modify‑status can have the following values:

has been modified needs to be modified does not need to be modified

new-node-number

is the new node number specified in the WITH clause in the MODIFY [DICTIONARY] LABEL command.

Cause Depends on modify-status, as follows:

has been modified	A MODIFY [DICTIONARY] LABEL operation finished successfully.
needs to be modified	A MODIFY [DICTIONARY] LABEL request with the CHECKONLY option determined that `old-node-number` needs to be modified.
does not need to be modified	A MODIFY [DICTIONARY] LABEL operation determined that `old-node-number` does not need to be modified.

Effect Depends on modify-status, as follows:

has been modified	The node number is changed.
needs to be modified	The CHECKONLY option has no effect; the node number is not changed.
does not need to be modified	The command has no effect.

Recovery If modify-status indicates that an object needs to be modified, you should issue a MODIFY [DICTIONARY] LABEL command for the node number and object listed in the message, to maintain the internal consistency of the database. Otherwise, this is an informational message only; no corrective action is needed.

The node name old-node-name in each entry of the catalog table catalog-name modify-status [to new-node-name].

`old-node-name`	is the node name specified in the REPLACE NODE NUMBER clause of the MODIFY [DICTIONARY] CATALOG command.
`catalog-name`	is the system catalog name or user-defined catalog name specified in the MODIFY [DICTIONARY] CATALOG command.
`modify-status`	reports the status of the MODIFY [DICTIONARY] CATALOG operation. modify‑status can have the following values: has been modified needs to be modified does not need to be modified
`new-node-name`	is the new node name specified in the WITH clause in the MODIFY [DICTIONARY] LABEL command.

Cause Depends on modify-status, as follows:

has been modified	A MODIFY [DICTIONARY] CATALOG operation finished successfully.
needs to be modified	A MODIFY [DICTIONARY] CATALOG request with the CHECKONLY option determined that `old-node-number` needs to be modified.
does not need to be modified	A MODIFY [DICTIONARY] CATALOG operation determined that `old-node-number` does not need to be modified.

Effect Depends on modify-status, as follows:

has been modified	The node number is changed.
needs to be modified	The CHECKONLY option has no effect; the node number is not changed.
does not need to be modified	The command has no effect.

Recovery If modify-status indicates that an object needs to be modified, you should issue a MODIFY [DICTIONARY] CATALOG command for the node number and object listed in the message, to maintain the internal consistency of the database. Otherwise, this is an informational message only; no corrective action is needed.

Catalog catalog-name has been registered in the system catalog system-catalog-name.

`catalog-name`	is the name of a user-defined catalog.
`system-catalog-name`	is the name of the system catalog that contains information about the user-defined catalog.

Cause A MODIFY [DICTIONARY] REGISTER command finished successfully.

Effect The user-defined catalog is registered in the local system catalog.

Recovery Informational message only; no corrective action is needed.

Modification of node number old-node-number in the file label of object-name failed with SQL error sql-error [and FS error fs-error].

`old-node-number`	is the node number stored in the file label.
`object-name`	is the object specified in the MODIFY [DICTIONARY] LABEL command.
`sql-error`	is the NonStop SQL/MP error number associated with the error condition.
`fs-error`	is the file-system error number associated with the error condition.

Cause A MODIFY [DICTIONARY] LABEL command terminated abnormally.

Effect The node number is not changed.

Recovery Check the SQL/MP and file-system errors listed in the message and correct the error condition, then reissue the command. For a description of the file‑system error, see Appendix B, For more information about file‑system errors, including recovery actions, see the Guardian Procedure Errors and Messages Manual. For information about SQL/MP errors, use the SQLCI ERROR command or see the NonStop SQL/MP Messages Manual.

Modification of node name old-node-name in the entry of catalog table catalog-name failed with SQL error sql-error [and FS error fs-error].

`old-node-name`	is the node name stored in the catalog table.
`catalog-name`	is the system catalog name or user-defined catalog name specified in the MODIFY [DICTIONARY] CATALOG command.
`sql-error`	is the NonStop SQL/MP error number associated with the error condition.
`fs-error`	is the file-system error number associated with the error that occurred.

Cause A MODIFY [DICTIONARY] CATALOG command terminated abnormally.

Effect The node name is not changed.

Registration of catalog catalog-name into the system catalog system-catalog-name failed with SQL error sql-error [and FS error fs-error].

`catalog-name`	is the name of the user-defined catalog specified in the MODIFY [DICTIONARY] REGISTER command.
`system-catalog-name`	is the name of the system catalog to be associated with the user-defined catalog.
`sql-error`	is the SQL/MP error number associated with the error that occurred.
`fs-error`	is the file system error number associated with the error condition.

Cause A MODIFY [DICTIONARY] REGISTER command terminated abnormally.

Effect The user-defined catalog is not registered in the specified system catalog.

Recovery Check the SQL/MP and file system errors listed in the message and correct the error condition, then reissue the command. For a description of the file‑system error, see Appendix B, For more information about file‑system errors, including recovery actions, see the Guardian Procedure Errors and Messages Manual. For information about SQL/MP errors, use the SQLCI ERROR command or see the NonStop SQL/MP Messages Manual.