Executor messages (8000 through 8999)

SQL 8001

8001 An internal executor error occurred.

Cause

NonStop SQL/MX has received an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8002

8002 The current nowaited operation is not complete.

Cause

A nowait CLI operation was started.

Effect

The operation is not complete.

Recovery

Ignore this message if the SQL/MX statement completes successfully. Otherwise, an internal error occurred, and you should contact your service provider.

SQL 8003

8003 The descriptor is locked by another nowaited operation.

Cause

The descriptor is still being used by another nowait CLI operation.

Effect

The new descriptor is locked.

Recovery

None. Contact your service provider.

SQL 8004

8004 Trying to open a statement or cursor that is not in the closed state.

Cause

You attempted to open a statement or cursor that is not in the closed state. It must be in the closed state to be opened.

Effect

The operation fails.

Recovery

Close the cursor before trying to open it.

SQL 8005

8005 Trying to fetch from a cursor that is not in the open state.

Cause

You attempted to fetch from a cursor that is not open.

Effect

The operation fails.

Recovery

Open the cursor before trying to fetch.

SQL 8006

8006 The stream timed out, but the cursor is still open.

Cause

A cursor is still open although its stream timed out.

Effect

The operation fails.

Recovery

Close the cursor before trying to open it.

SQL 8007

8007 The operation has been canceled.

Cause

You pressed the break key.

Effect

The operation stops.

Recovery

None.

SQL 8008

8008 Catalog name name is not valid.

Where,

name is the name of the catalog.

Cause

You specified an invalid catalog name.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 8009

8009 Schema name name is not valid.

Where,

name is the name of the schema.

Cause

You specified an invalid schema name.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 8010

8010 Default catalog name: name1. Default schema name: name2.

Where,

catalog name1 is the name of the catalog;

schema name2 is the name of the schema.

Cause

NonStop SQL/MX displays the default catalog and schema names.

Effect

None.

Recovery

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

SQL 8011

8011 SELECT statement inside compound (BEGIN ... END) statement returns more than one row.

Cause

You specified a SELECT statement inside a compound statement that returns more than one row.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 8012

8012 Encoding of CONTROL QUERY DEFAULTs: encoding.

Cause

NonStop SQL/MX displays an internal CONTROL QUERY DEFAULT encoding.

Effect

None.

Recovery

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

SQL 8013

8013 You are trying to update or delete from a cursor that is not in the fetched state.

Cause

You are trying to update or delete from a cursor that is not in the fetched state.

Effect

The operation fails.

Recovery

Fetch the cursor and resubmit.

SQL 8014

8014 A SELECT statement within compound statement did not return any row.

Cause

You specified a SELECT statement inside a compound statement that did not return any rows.

Effect

None.

Recovery

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

SQL 8015

8015 Aborting transaction because a compound statement performed an update operation followed by a SELECT statement that did not return any row.

Cause

You performed an UPDATE, DELETE, or INSERT operation as part of a compound statement before a SELECT statement. The SELECT statement did not return any rows.

Effect

The transaction is aborted, and the update is rolled back.

Recovery

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

SQL 8016

8016 An attempt was made to access name which has a system version that is incompatible with the version of the accessing software.

Cause

You attempted to access a system version that is incompatible with the version of the accessing software.

Effect

The operation fails.

Recovery

The system you are trying to access must be on a system version that is compatible with your accessing software. Upgrade that system.

SQL 8017

8017 Explain information is not available for this query.

Cause

The explain default has been turned off for this query.

Effect

NonStop SQL/MX is not able to display explain information.

Recovery

Turn the explain default on for this query.

SQL 8018

8018 Partition name1 of table name2 could not be accessed due to file system error number. It is skipped because the default SKIP_UNAVAILABLE_PARTITION was set.

Where,

name1 is the name of the partition;

name2 is the name of the table;

number is the file system error returned.

Cause

Attempt to open partition name1 of the table name2 failed, returning the file system error code number.

Effect

None

Recovery

See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.

SQL 8019

8019 Explain plan data retrieval error, numeric field NULL or truncated.

Cause

A NULL or truncated value is received instead of a numeric value.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8022

8022 Stored row count is invalid for table name.

Cause

The row count maintained by the disk process for one or more partitions of the table name is invalid because of the following reasons:

• The table is created by an SQL release before R3.0.

• The table is created by an SQL DUP operation.

• The table is reorganized.

Effect

The operation fails.

Recovery

In the SQL/MX R3.0, the only way to reset the row count is to delete all the rows from the table. Alternatively, the INSERT…SELECT statements can be used to move the data from the table with the invalid row count to another table. The target table will then have a valid row count although the row count for the source table will remain invalid.

SQL 8100

8100 Define name does not exist.

Cause

You attempted to reference a define that does not exist.

Effect

The operation fails.

Recovery

Define the item, or use the correct define name.

SQL 8101

8101 The operation is prevented by check constraint name1 on table name2.

Where,

constraint name1 is the name of the constraint;

table name2 is the name of the table.

Cause

You attempted to perform an operation on table name1 that is prevented by check constraint name2.

Effect

The operation fails.

Recovery

Change the data you are attempting to enter to be consistent with the constraint.

SQL 8102

8102 The operation is prevented by a unique constraint.

Cause

You attempted to perform an operation that is prevented by a unique constraint.

Effect

NonStop SQL/MX could not perform the operation.

Recovery

Make the data you enter unique to be consistent with the constraint.

SQL 8103

8103 The operation is prevented by referential integrity constraint name1on table name2.

Where,

name1 is the name of the constraint;

name2 is the name of the table.

Cause

You attempted to perform an operation on table name1 that is prevented by referential integrity constraint name2.

Effect

The operation fails.

Recovery

Change the data you are attempting to enter to be consistent with the constraint. The data must exist in another table. For example, if you are trying to enter a department number for an employee, the department number must exist in a department number table.

SQL 8104

8104 The operation is prevented by the check on view name1cascaded from the check option on name2.

Where,

view name1 is the name of the view;

name2 is the name of the table.

Cause

You attempted to perform an operation on table name1. The operation has been prevented by the check on view name2, cascaded from the check option on the table.

Effect

The operation fails.

Recovery

Change the view properties, if appropriate.

SQL 8105

8105 The operation is prevented by the check option on view name.

Where,

name is the name of the view.

Cause

You attempted to perform an operation on table name that is prevented by the check option on view name.

Effect

The operation fails.

Recovery

Insert into the base table rather than this view.

SQL 8106

8106 The last row fetched by this cursor was updated or deleted between the FETCH and UPDATE/DELETE...WHERE CURRENT... of statements.

Cause

The last row fetched by the cursor was updated or deleted between the FETCH and UPDATE/DELETE...WHERE CURRENT statements and is no longer available.

Effect

The UPDATE/DELETE WHERE CURRENT statement is invalid.

Recovery

Perform another FETCH then an UPDATE/DELETE.

SQL 8107

8107 Self-referencing INSERT statement without blocking operator is not allowed with AUTOCOMMIT OFF.

Cause

A self-referencing INSERT is executed in a transaction when AUTOCOMMIT is set to OFF and the compiler has chosen the DP2 Locks method.

Effect

The INSERT operation fails and no rows are inserted.

Recovery

Ensure that the compiler chooses the Blocking Plan Operator method by setting the CQD, BLOCK_TO_PREVENT_HALLOWEEN to ON.

SQL 8109

Default name is not a valid default.

name

is the default name to set.

Cause

The SET SESSION DEFAULT command specified an invalid default.

Effect

The operation fails.

Recovery

Set the correct attribute value.

SQL 8111

8111 The specified value attribute value for DEFAULTS attribute attribute name is not valid value.

value

specifies the range to enter the correct attribute value.

Cause

You specified a default attribute value that is invalid.

Effect

The operation fails.

Recovery

Set the correct attribute value.

SQL 8140

8140 The statement was canceled, to test cancel processing. File name at line number.

Where,

name is the name of the file;

number is the line number.

Cause

You set an environmental variable to test cancel processing.

Effect

The statement was canceled.

Recovery

Execute the statement again after first resetting the environmental variable.

SQL 8141

8141 An error was artificially injected, to test error handling. File name at line number.

Cause

You set an environmental variable to test error handling.

Effect

The operation fails.

Recovery

Recompile and re-execute the statement, after first resetting the environmental variable.

SQL 8300

8300 Late name resolution failed for type object.

Where,

type is the type of the affected object, such as table;

object is the fully qualified ANSI name of the affected object.

Cause

Late name resolution failed for the affected object.

Effect

The operation fails. This message will be accompanied by one or more other messages detailing the reason for the failure.

Recovery

Correct the error, as reported in the accompanying messages, and resubmit.

SQL 8301

8301 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 an SQL/MX anchor file.

Cause

Access to the specified anchor file failed and returned a Guardian file system error code.

Effect

Late name resolution fails.

Recovery

Correct the error and resubmit.

SQL 8302

8302 All partitions of type object are unavailable.

Where,

type is the type of the affected object, such as table;

object is the fully qualified ANSI name of the affected object.

Cause

Late name resolution could not resolve the ANSI name to an available partition.

Effect

The operation fails.

Recovery

Determine why none of the partitions were available, then correct the error and resubmit.

SQL 8303

8303 Anchor file name contains invalid data.

Where,

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

Cause

The named anchor file contains invalid data.

Effect

NonStop SQL/MX uses data from the anchor file to locate the system schema tables on a node. Without a valid anchor file, it is not possible to compile or execute queries that use SQL/MX metadata on the anchor file's Expand node.

Recovery

None. This is a fatal error. Contact your service provider.

SQL 8350

8350 Character set set1 and set2 are not assignment compatible.

Where,

set1 and set2 are the character sets of two character types.

Cause

The two character sets are different. As a result, an assignment between the two character types cannot be made.

Effect

The operation fails.

Recovery

Determine why the two character types have different character sets and make them agree (for example, properly declare the character set of the host variable or use the SQL function TRANSLATE).

SQL 8400

8400 Define name1 should have a name2 class attribute.

Cause

The CLASS attribute of the DEFINE is not correct. For example, the CLASS attribute for an MP table name DEFINE should be MAP, not SORT.

Effect

The operation fails.

Recovery

Use a correct CLASS attribute as specified in the SQL/MX Programming Manual for C and COBOL.

SQL 8401

8401 21000 A row subquery or SELECT...INTO statement cannot return more than one row.

Cause

The table or tables had more than one row that satisfied the query. Only one row is allowed.

Effect

The operation fails.

Recovery

Determine if the statement or the data is incorrect. If the data is incorrect, correct the data. If the INTO clause is incorrect, use a cursor to select and fetch the data. Use an INTO clause only when you expect one row to satisfy the SELECT statement. If the subquery is incorrect, rewrite the SELECT query.

SQL 8402

8402 22001 A string overflow occurred during the evaluation of a character expression. Conversion of Source Type: source-data-type(internal-type) Source Value:string-value to Target Type: target-data-type(internal-type).

Where,

source-data-type(internal-type) is the character string data type (and an internal representation of the data type) of the column to which the SQL statement refers;

string-value is the character string literal that you specified in the SQL statement;

target-data-type(internal-type) is the character string data type (and an internal representation of the data type) to which the character string is being converted.

Cause

If the SQLSTATE is 22001, this is an error. You attempted to use a character expression whose length caused a string overflow.

If the SQLSTATE is 01004, this is a warning. You attempted to use a character expression whose length caused a string overflow.

Effect

If this is an error, the operation fails. If this is a warning, your string is truncated.

Recovery

Do not attempt recovery. Contact your service provider.

SQL 8403

8403 The length argument of function SUBSTRING cannot be less than zero or greater than source string length.

Cause

You specified a SUBSTRING function with an invalid length argument: less than zero or greater than the source string length.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 8404

8404 The trim character argument of function TRIM must be one character in length.

Cause

You specified a TRIM function with an invalid trim character argument, which must be one character in length.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 8405

8405 The operand of function CONVERTTIMESTAMP is out of range.

Cause

You attempted to reference the operand of a CONVERTTIMESTAMP function that is out of range.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 8407

8407 The operand of function JULIANTIMESTAMP is out of range.

Cause

A statement attempted to reference the operand of a JULIANTIMESTAMP function that is out of range.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 8409

8409 The escape character argument of a LIKE predicate must be one character in length.

Cause

You specified a LIKE predicate with an invalid escape character argument, which must be one character in length.

Effect

The operation fails.

Recovery

Check your input data and resubmit.

SQL 8410

8410 An escape character in a LIKE pattern must be followed by another escape character, an underscore, or a percent character.

Cause

You specified a LIKE pattern whose syntax is incorrect. An escape character in a LIKE pattern must be followed by another escape character, an underscore, or a percent character.

Effect

The operation fails.

Recovery

Check your input data and resubmit.

SQL 8411

8411 A numeric overflow occurred during an arithmetic computation or data conversion.

Cause

A computation has resulted in an item that overflows its field.

Effect

The operation fails.

Recovery

Do not attempt recovery. Contact your service provider.

SQL 8412

8412 An input character host variable is missing its null terminator.

Cause

You specified an input character host variable that is missing its null terminator.

Effect

The operation fails.

Recovery

Check your input data and resubmit.

SQL 8413

8413 The string argument contains characters that cannot be converted.

Cause

You provided a string argument for conversion that contains characters that cannot be converted.

Effect

The operation fails.

Recovery

Check your input data and resubmit.

SQL 8414

8414 The attempted conversion is not supported on this platform.

Cause

You attempted to perform a conversion that is not supported on this platform.

Effect

The operation fails.

Recovery

None.

SQL 8415

8415 The provided DATE, TIME or TIMESTAMP is not valid and cannot be converted.

Cause

You provided an invalid DATE, TIME, or TIMESTAMP, which could not be converted.

Effect

The operation fails.

Recovery

Check your data and resubmit.

SQL 8416

8416 A datetime expression evaluated to an invalid datetime value.

Cause

Invalid datetime expression.

Effect

The operation fails.

Recovery

Correct the expression and resubmit the statement.

SQL 8417

8417 An error occurred during the evaluation of a USER function.

Cause

NonStop SQL/MX has received an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8418

8418 The USER function is not supported on this platform.

Cause

You attempted to perform the USER function, which is not supported on this platform.

Effect

The operation fails.

Recovery

None.

SQL 8419

8419 An arithmetic expression attempted a division by zero.

Cause

An expression attempted to divide by zero, which is invalid.

Effect

The operation fails.

Recovery

Do not attempt recovery. Contact your service provider.

SQL 8420

8420 Missing indicator parameter for a NULL value.

Cause

You specified a NULL value that is missing an indicator parameter.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 8421

8421 NULL cannot be assigned to a NOT NULL column.

Cause

You assigned NULL to a column for which NOT NULL was specified.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 8422

8422 The provided INTERVAL is not valid and cannot be converted.

Cause

You provided an INTERVAL that is not valid and that could not be converted.

Effect

The operation fails.

Recovery

Check your input and resubmit.

SQL 8423

8423 The provided field number is not valid.

Cause

You specified a field number that is not valid.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 8424

8424 Function name is not yet supported.

Where,

name is the name of the function.

Cause

You attempted to perform function name, which is not supported.

Effect

The operation fails.

Recovery

None.

SQL 8425

8425 NULL cannot be assigned to a DEFAULT NULL NOT NULL column.

Cause

You attempted to assign a null value to a column that is defined as NOT NULL.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit, without a null value.

SQL 8427

8427 detail text

Cause

A sort error occurred. The error returned appears as detail text.

Effect

The operation fails.

Recovery

To diagnose and correct the problem, use the information in the sort error.

SQL 8428

8428 The argument to function name is not valid.

Where,

name is the name of the function.

Cause

You specified an invalid argument for the function name.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 8429

8429 The preceding error actually occurred in function name.

Cause

NonStop SQL/MX detected an error in the function name. Errors will appear before this one that refer to low-level computations that this function uses.

Effect

The operation fails.

Recovery

Correct the function and resubmit.

SQL 8432

8432 A negative value cannot be converted to an unsigned numeric datatype string.

Cause

An attempt was made to assign a negative value to an unsigned column.

Effect

The assignment fails.

Recovery

You cannot assign negative values to unsigned variables or columns. Check the value being assigned and retry the operation.

SQL 8433

8433 Invalid char-set character encountered in function.

Where,

char-set is the name of the character set (SJIS or UTF8);

function is the function name.

Cause

The table or the statement has invalid SJIS or UTF8 characters.

Effect

The operation fails.

Recovery

Remove the invalid characters from the table or the statement, and resubmit.

SQL 8445

8445 Error occurred while processing the format node.

Cause

The value specified was not processed for the given format specification.

Effect

The operation fails.

Recovery

Correct the value and resubmit the statement.

SQL 8447

8447 An internal error occurred in SQL/MX executor while evaluating IFNULL/ ISNULL/ NVL expression.

Cause

An internal error occurred while evaluating a IFNULL/ISNULL/NVL expression.

Effect

The operation fails.

Recovery

Correct the value and resubmit the statement.See Contacting your service provider.

SQL 8490

8490 An internal error occurred while evaluating a Datetime arithmetic expression.

Cause

An internal error occurred while evaluating a DATETIME expression.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8451

8451 None of the CPUs configured using CQD 'CPU_LIST_FOR_ESP_PLACEMENT' are available at runtime.

Cause

None of the configured CPUs were available at the time of ESP creation or reuse.

Effect

The operation fails.

Recovery

Reload the CPUs and retry the operation.

SQL 8500

8500 Key values specified in the INSERT clause of a MERGE statement must be the same as those specified in the ON clause.

Cause

You specified different values for key columns of the target table in the ON clause and the INSERT clause of the MERGE statement.

Effect

Application outage.

Recovery

Specify same values for the key columns of the target table in the ON clause and the INSERT clause and resubmit the MERGE statement.

SQL 8501

8501 The USING clause subquery in a MERGE statement cannot return more than one matching row.

Cause

For the specified ON condition, more than one matching row was returned by the USING clause.

Effect

The operation fails.

Recovery

Modify the ON condition or the USING subquery and resubmit the statement.

SQL 8551

8551 Error NSK err was returned by the file system on object-name.

Where,

NSK err is the NonStop Kernel error returned;

object-name is the name of the object.

Cause

The file system returned error NSK err on object-name.

Effect

The operation fails.

Recovery

See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.

SQL 8552

8552 Error num was returned by the file system while fetching the version of the system name.

Where,

num is the error number returned;

name is the name of the system.

Cause

The file system returned error num.

Effect

The operation fails.

Recovery

See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.

SQL 8553

8553 Stream overflow; subscription rate has fallen too far behind publishing rate.

Cause

The table used by the streaming cursor has overflowed.

Effect

The cursor or statement is closed.

Recovery

Reopen the statement or cursor and resume subscribing. For more details, see "Run-Time Limits on Streams" in SQL/MX Queueing and Publish/Subscribe Services.

SQL 8555

8555 An internal error occurred in the SQL/MX executor in the disk process.

Cause

An SQL/MX procedure in the disk process detected an internal error.

Effect

The operation fails. An EMS event message for event number 5127 from the Disk subsystem has been generated to supply further diagnostic information. See the Operator Messages Manual for information on retrieving EMS event messages.

Recovery

None. Contact your service provider.

SQL 8570

8570 SQL/MX could not allocate sufficient memory to build query.

Cause

The system does not have enough memory to build the query.

Effect

The operation fails.

Recovery

Try to reduce the system's load by entering fewer statements. You can try restarting NonStop SQL/MX. If this does not correct the problem, contact your service provider.

SQL 8571

8571 SQL/MX could not allocate sufficient memory to execute query.

Cause

The system does not have enough memory to execute the query.

Effect

The operation fails.

Recovery

Try to reduce the system's load by entering fewer statements. You can try restarting NonStop SQL/MX. If this does not correct the problem, contact your service provider.

SQL 8572

8572 The statement has incurred a fatal error and must be deallocated.

Cause

NonStop SQL/MX has received an internal error.

Effect

The operation fails.

Recovery

Re-execute the statement and resubmit it. If this does not correct the problem, stop and restart NonStop SQL/MX.

SQL 8573

8573 The user does not have user-level privilege on object name.

Where,

user-level is the user privilege.

name is the ANSI name of the object.

Cause

You attempted to perform an operation on object name for which you do not have a sufficient privilege level.

Effect

The operation fails.

Recovery

None. Ask the system administrator to change your privilege level, if appropriate.

SQL 8574

8574 An OPEN was blown away on table name.

Where,

name is the name of the table.

Cause

While you had table name open, another operation such as DDL changed that table.

Effect

The table is no longer open. You will see this message if NonStop SQL/MX was unable to recompile your statement.

Recovery

Reopen the table and start again.

SQL 8575

8575 Timestamp mismatch on table name.

Where,

name is the name of the table.

Cause

Table name has been changed, and NonStop SQL/MX was not able to recompile this statement.

Effect

The operation fails.

Recovery

Verify what has changed in the file and recompile this program.

SQL 8576

8576 Statement was recompiled.

Cause

NonStop SQL/MX recompiled the statement.

Effect

The operation fails.

Recovery

Recompile the program.

SQL 8577

8577 Table, index or view name was not found.

Where,

name is the name of the object.

Cause

NonStop SQL/MX could not find the object name.

Effect

The operation fails.

Recovery

Verify the location of the object and resubmit.

SQL 8578

8578 Similarity check passed.

Cause

The similarity check passed.

Effect

None.

Recovery

Informational message only; no corrective action is needed.

SQL 8579

8579 Similarity check failed: reason

Where,

reason specifies the failed criteria.

Cause

Similarity Check failed.

Effect

The operation fails.

Recovery

Use the reason to diagnose and correct the problem. For more information, see the Similarity Check criteria in the SQL/MX Programming Manual for C and COBOL.

SQL 8580

8580 No partitions of table name could be accessed. File system error number was returned.

Where,

name is the name of the specified table;

number is the error code returned.

Cause

Attempts to open any partition of table name failed, returning file system error code number.

Effect

The operation fails.

Recovery

See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.

SQL 8581

8581 The in-memory Join operation could not complete due to insufficient memory.

Cause

Insufficient memory was available to perform the join operation.

Effect

The operation fails.

Recovery

Contact Hewlett Packard Enterprise support for assistance in recompiling the query with Unique In-Memory Hash Joins turned off (control query default UNIQUE_HASH_JOINS 'OFF'), and re-execute.

SQL 8584

8584 Query timed out while waiting for release work reply from ESPs.

Cause

Application abends with a time-out error on a select query with multiple “esp_exchange” nodes in its plan is executed.

Effect

Application outage.

Recovery

< control query default ATTEMPT_ESP_PARALLELISM 'OFF';>

SQL 8598

8598 View view-name was not found or was dropped and recreated.

Where,

view--name is the name of the view.

Cause

An attempt was made to access a view that no longer exists.

Effect

The query fails.

Recovery

Verify that the view exists and is accessible, and retry the operation.

SQL 8601

8601 Error returned from file system while locking/unlocking.

Cause

The file system received an error while locking or unlocking.

Effect

The operation fails.

Recovery

If errors accompany this one, use them to diagnose and correct the problem.

SQL 8602

8602 The file system reported error number on a lock/unlock operation.

Where,

number is the error number.

Cause

The file system received process control procedure error number while performing a locking or unlocking operation.

Effect

The operation fails.

Recovery

Use the process control procedure error to diagnose and correct the problem.

See Process control procedure errors.

SQL 8603

8603 Trying to begin a transaction that has already been started.

Cause

You attempted to begin a transaction that has already been started.

Effect

The operation fails.

Recovery

Correct the syntax so that the transaction is started only once, and resubmit.

SQL 8604

8604 Transaction subsystem name returned error number while starting a transaction.

Where,

name is the subsystem name;

number is the error number.

Cause

Transaction subsystem name has returned error numberwhile starting a transaction.

Effect

The operation fails.

Recovery

See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.

SQL 8605

8605 Committing a transaction which has not started.

Cause

You attempted to commit a transaction that has not been started.

Effect

The operation fails.

Recovery

Correct the syntax so that the transaction is started before it is committed, and resubmit.

SQL 8606

8606 Transaction subsystem name returned error number on a commit transaction.

Where,

name is the name of the subsystem;

number is the error number.

Cause

Transaction subsystem name has returned error number while committing a transaction.

Effect

The operation fails.

Recovery

See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.

SQL 8607

8607 Rolling back a transaction that has not started.

Cause

You attempted to roll back a transaction that has not started.

Effect

The operation fails.

Recovery

Correct the syntax so that the sequence of events is correct, and resubmit.

SQL 8608

8608 Transaction subsystem name returned error number on rollback transaction.

Where,

name is the name of the subsystem;

number is the error number.

Cause

Transaction subsystem name has returned error number while rolling back a transaction.

Effect

The operation fails.

Recovery

See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.

SQL 8609

8609 Waited rollback performed without starting a transaction.

Cause

You attempted to perform a waited rollback on a transaction that has not started.

Effect

The operation fails.

Recovery

Correct the syntax so that the sequence of events is correct, and resubmit.

SQL 8610

8610 Transaction subsystem name reported error number on a waited rollback transaction.

Where,

name is the name of the subsystem;

number is the error number.

Cause

Transaction subsystem name has returned error number while performing a waited rollback transaction.

Effect

The operation fails.

Recovery

See the Guardian Procedure Errors and Messages Manual to diagnose and correct the problem.

SQL 8612

8612 Transaction mode cannot be set if the transaction is already running.

Cause

You attempted to set the transaction mode, but the transaction is already running.

Effect

The operation fails.

Recovery

Abort and restart the transaction if you must change its mode.

SQL 8613

8613 SQL cannot commit or rollback a transaction that was started by application.

Cause

An application started a transaction outside of NonStop SQL/MX that NonStop SQL/MX could not commit or rollback.

Effect

The operation fails.

Recovery

The application that started the transaction must perform a commit or rollback. NonStop SQL/MX must start any transactions it will later commit or rollback.

SQL 8614

8614 SQL cannot begin a transaction when multiple contexts exist.

Cause

NonStop SQL/MX cannot start a transaction when multiple contexts are present.

Effect

The transaction is unable to start.

Recovery

None. Contact your service provider.

SQL 8615

8615 A user-defined transaction has been started. Multi commit operation cannot be performed.

Cause

A multi commit statement is issued in a transaction started explicitly by the user.

Effect

The statement fails.

Recovery

End the transaction and issue the multi commit statement, or use a regular DELETE statement inside a user-started transaction.

SQL 8690

8690 An invalid character value encountered in TRANSLATE function.

Cause

The source contains a character that cannot be translated to the target.

Effect

The operation fails.

Recovery

Make sure that the source data is clean and translatable and resubmit.

SQL 8700

8700 An assertion failure or out-of-memory condition occurred during parallel execution.

Cause

An ESP encountered an error during a query.

Effect

The query fails.

Recovery

Use the EMS event log information in the event generated by this failure to diagnose and correct the problem. You might need to allocate page file space or memory. If this does not correct the problem, contact your service provider.

SQL 8710

8710 Error num returned by Measure when attempting to update SQL counters.

Where,

num is the error number returned.

Cause

Measure encountered an error while attempting to update SQL/MX counters.

Effect

Measure fails to update the SQL/MX counters.

Recovery

Use the error in the message to diagnose and correct the problem.

SQL 8750

8750 A module cannot be unloaded when a transaction is in progress. End the transaction and retry the operation.

Cause

The UNLOAD MODULE command is executed in the context of an active transaction.

Effect

The module is not unloaded. The resources allocated to the module are not released.

Recovery

Retry the UNLOAD MODULE command after ending the transaction by committing or aborting it.

SQL 8751

8751 System module files cannot be unloaded.

Cause

The module-name specified in the UNLOAD MODULE command refers to a system module file.

Effect

None.

Recovery

Change the module-name to refer to the correct user module and retry the operation.

SQL 8801

8801 Descriptor allocation failed because the descriptor already exists in the current context.

Cause

This is an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8802

8802 Statement allocation failed because the statement already exists in the current context.

Cause

This is an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8803

8803 The provided input descriptor does not exist in the current context.

Cause

This is an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8804

8804 The provided input statement does not exist in the current context.

Cause

This is an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8805

8805 Trying to action a descriptor that is not allocated with AllocDesc() call.

Cause

This is an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8806

8806 Trying to action a statement that is not allocated with AllocStmt() call.

Cause

This is an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8807

8807 Trying to allocate more than value entries for a descriptor.

Cause

This is an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8808

8808 Module file name contains corrupted or invalid data.

Where,

name is the name of the file.

Cause

NonStop SQL/MX has detected corrupted or invalid data in the module file name.

Effect

NonStop SQL/MX could not execute the file.

Recovery

Recompile the .mdf file, using the MXCMP compiler, to create a valid module file. For more information, see the subsection "Understanding and Avoiding Some Common Run-time Errors" in the SQL/MX Programming Manual for C and COBOL.

SQL 8809

8809 Open of the module file name failed with error number.

Where,

name is the name of the file;

number is the error number returned.

Cause

NonStop SQL/MX was unable to open module file name.

Effect

The operation fails.

Recovery

Check the location of the module file and retry the operation. For more information on this error, see the subsection "Understanding and Avoiding Some Common Run-time Errors" in the SQL/MX Programming Manual for C and COBOL.

SQL 8811

8811 Trying to close a statement that is either not in the open state or has not reached EOF.

Cause

This is an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8812

8812 Trying to execute a statement that is not in the closed state.

Cause

This is an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8813

8813 Trying to fetch from a statement that is in the closed state.

Cause

This is an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8814

8814 The transaction mode at run time (value) differs from that specified at compile time (value).

Cause

This is an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8815

8815 An internal error occurred while building the TCB tree when executing the statement.

Cause

This is an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8816

8816 An internal error occurred while executing the TCB tree.

Cause

This is an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8817

8817 An internal error occurred while fetching from the TCB tree.

Cause

This is an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8818

8818 An internal error occurred in root_tdb describe.

Cause

This is an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8819

8819 Begin transaction failed while preparing the statement.

Cause

This is an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8820

8820 Transaction commit failed while closing the statement.

Cause

This is an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8821

8821 Rollback transaction failed during the process of fetching the statement.

Cause

This is an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8822

8822 The statement was not prepared.

Cause

This is an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8823

8823 An internal error occurred: IO requests are waiting for description message in the IpcMessageStream.

Where,

description is the description message.

Cause

I/O requests are waiting for messages shown in message description from the IpcMessage Stream.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8824

8824 The input module_id does not have a module name.

Cause

A module name was not passed into the module ID structure that was passed in.

Effect

The operation fails.

Recovery

Make sure that a module name is passed into the module ID structure.

SQL 8825

8825 Module is already added into the current context.

Cause

This is an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8826

8826 The module could not be added.

Cause

This is an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8827

8827 The request name could not be sent.

Where,

name is the name of the request.

Cause

NonStop SQL/MX was unable to send request name.

Effect

The operation fails.

Recovery

Use the errors that accompany this one to diagnose and correct the problem.

SQL 8828

8828 Out-of-memory condition occurred while creating the name.

Cause

NonStop SQL/MX ran out of memory while creating the internal structure name.

Effect

The operation fails.

Recovery

Increase NonStop SQL/MX's memory and resubmit.

SQL 8829

8829 Trying to set descriptor item for an entry that is either invalid or greater than the maximum entry count for that descriptor.

Cause

This is an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8830

8830 There is no current context.

Cause

This is an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8831

8831 Either no current context or the module to which the statement belongs is not added to the current context.

Cause

This is an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8832

8832 Transaction has not been started.

Cause

A transaction has not been started.

Effect

The operation fails.

Recovery

Verify that the transaction has been started or start it if it has not been.

SQL 8833

8833 The input parameter is an invalid SQL transaction command.

Cause

This is an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8834

8834 The SQL installation directory could not be found. Operating system error number.

Where,

number is the error number.

Cause

NonStop SQL/MX was unable to find the SQL/MX installation directory and received an operating system error number.

Effect

The operation fails.

Recovery

Locate the SQL/MX installation directory, correct your syntax, and resubmit.

SQL 8835

8835 Invalid SQL descriptor information requested.

Cause

The descriptor item requested from the descriptor area or being set in the descriptor area is not valid.

Effect

The operation fails.

Recovery

Make sure that the syntax is correct and that a valid descriptor item is being retrieved or set.

SQL 8836

8836 Application specified an invalid update column for cursor.

Cause

There is an error in the program that this code is embedded in. The build might not have completed correctly.

Effect

The operation fails.

Recovery

Verify that the build was successful and resubmit.

SQL 8837

8837 Authorization failure: Error number1 with status number2 was returned by proc-call.

Where,

number1 is the file-system error returned by proc-call;

number2 is the status code returned by proc-call;

proc-call is the name of the file-system procedure call returning the error.

Cause

The value of the user ID is not valid.

Effect

The operation fails.

Recovery

Ensure that the user ID of the form group id][name, user id][user name, password is valid and exists on the current system. If the problem persists, contact your service provider.

SQL 8838

8838 Unable to receive reply from MXCMP, possibly caused by internal errors when compiling SQL statements, processing DDL statements, or executing the builtin stored procedures.

Cause

NonStop SQL/MX did not receive a reply it expected from MXCMP.

Effect

The operation fails.

Recovery

Verify that MXCMP is running.

SQL 8839

8839 Transaction was aborted.

Cause

A transaction failed during processing of an SQL/MX statement. NonStop SQL/MX might have aborted an AUTOCOMMIT transaction, or a transaction was aborted for some other reason (audit trail full, autoabort time limit reached, and so on).

Effect

The operation fails.

Recovery

Check the application event log for a detailed entry about this situation.

SQL 8840

8840 Object name provided to CLI is not valid.

Cause

The object named provided to CLI is invalid.

Effect

The operation fails.

Recovery

Correct the object name and resubmit.

SQL 8841

8841 User application committed or aborted a transaction started by SQL. This transaction needs to be committed or aborted by calling SQL COMMIT or ROLLBACK WORK.

Cause

NonStop SQL/MX started a transaction that was committed or aborted by an embedded program, rather than by NonStop SQL/MX.

Effect

The operation fails.

Recovery

Commit or abort the transaction by calling SQL COMMIT or ROLLBACKWORK.

SQL 8842

8842 The cursor, name, referenced by this statement is not found or is not updatable.

Where,

name is the name of the cursor.

Cause

There is an error in the program that this code is embedded in. The build might not have completed successfully.

Effect

The operation fails.

Recovery

Verify that the build was successful and resubmit.

SQL 8843

8843 Trying to retrieve an item, value, that is out of range.

Where,

value is the entry number of the item.

Cause

The item number of the requested descriptor item or the item number of the descriptor item being set is out of range. The value must be less than the maximum number of occurrences specified when the descriptor area was allocated.

Effect

The operation fails.

Recovery

Specify a valid number between 1 and the maximum allocated item count of the descriptor.

SQL 8844

8844 A transaction started by SQL that was committed or aborted by user application from outside of SQL, has now been cleaned up.

Cause

After NonStop SQL/MX started a transaction that was committed or aborted by an embedded program, rather than from NonStop SQL/MX, you used SQL COMMIT or ROLLBACKWORK to finish the transaction.

Effect

None.

Recovery

Informational message only; no corrective action is needed.

SQL 8845

8845 An internal error occurred: root_tcb is null.

Cause

This is an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8846

8846 An empty SQL statement was passed in.

Cause

The SQL source statement passed to the compiler to do the prepare was empty.

Effect

The operation fails.

Recovery

You must pass in a valid SQL source statement.

SQL 8847

8847 An error occurred while trying to retrieve SQL/MP metadata information.

Cause

NonStop SQL/MX received an error while trying to retrieve SQL/MP metadata information.

Effect

The operation fails.

Recovery

Use the errors that accompany this one to diagnose and correct the problem, and resubmit.

SQL 8848

8848 Cancel on DDL statements or stored procedures is not supported.

Cause

You attempted to enter a break while running DDL statements or internal table-valued functions.

Effect

The operation fails.

Recovery

None.

SQL 8850

8850 The table specified in this cursor update or delete statement is different than the table specified in the declare cursor statement.

Cause

The table specified in the update or DELETE statement is not the same as the one specified in the declare cursor statement, as is required.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 8851

8851 A CLI Parameter bound check error occurred.

Cause

NonStop SQL/MX received a CLI parameter bound check error.

Effect

The operation fails.

Recovery

Rebuild the module file and resubmit.

SQL 8852

8852 Holdable cursors are supported for only streaming cursors and embedded update/delete cursors.

Cause

You attempted to use a holdable cursor in a situation where it is not supported.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 8853

8853 Specified attribute definition is not valid.

Cause

You specified an invalid attribute definition.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 8854

8854 Specified attribute value is not valid.

Cause

You specified an invalid attribute value.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 8855

8855 Statement attribute cannot be set now.

Cause

You attempted to set a statement attribute after a statement was compiled. The attribute must be set before compilation.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 8856

8856 Specified attribute value is not valid. INPUT_ARRAY_MAXSIZE must be positive.

Cause

You specified an invalid attribute value. INPUT_ARRAY_MAXSIZE must be positive.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 8858

8858 The value (value) is not a valid SQL identifier.

Cause

You attempted to reference an invalid SQL identifier, displayed in the message.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 8859

8859 There are pending insert, delete, or update operations.

Cause

The current operation failed because there is a pending INSERT, DELETE, or UPDATE operation.

Effect

The operation fails.

Recovery

Complete the outstanding operation and try again.

SQL 8860

8860 Module file name has an obsolete module header.

Where,

name is the file name.

Cause

The module file name has an obsolete module header.

Effect

The operation fails.

Recovery

Rebuild the module file and resubmit.

SQL 8861

8861 Module file name has an obsolete descriptor location table header.

Where,

name is the file name.

Cause

The module file name has an obsolete table header.

Effect

The operation fails.

Recovery

Rebuild the module file and resubmit.

SQL 8862

8862 Module file name has an obsolete descriptor location table entry.

Where,

name is the file name.

Cause

The module file name has an obsolete descriptor location table entry.

Effect

The operation fails.

Recovery

Rebuild the module file and resubmit.

SQL 8863

8863 Module file name has an obsolete descriptor header.

Where,

name is the file name.

Cause

The module file name has an obsolete descriptor header.

Effect

The operation fails.

Recovery

Rebuild the module file and resubmit.

SQL 8864

8864 Module file name has an obsolete descriptor entry.

Where,

name is the file name.

Cause

The module file name has an obsolete descriptor entry.

Effect

The operation fails.

Recovery

Rebuild the module file and resubmit.

SQL 8865

8865 Module file name has an obsolete procedure location table header.

Where,

name is the file name.

Cause

The module file name has an obsolete procedure location table header.

Effect

The operation fails.

Recovery

Rebuild the module file and resubmit.

SQL 8866

8866 Module file name has an obsolete procedure location table entry.

Where,

name is the file name.

Cause

The module file name has an obsolete procedure location table entry.

Effect

The operation fails.

Recovery

Rebuild the module file and resubmit.

SQL 8867

8867 An error while reading from file name.

Where,

name is the file name.

Cause

NonStop SQL/MX encountered an error while reading the module file name.

Effect

The operation fails.

Recovery

Rebuild the module file and resubmit.

SQL 8868

8868 SQL cannot create a new context when current transaction is implicitly started by SQL.

Cause

The application did not start its own transaction. Multiple contexts are not allowed when the transaction is started by NonStop SQL/MX.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8869

8869 The specified file number in not a QFO, or the file number is not internally associated with a QFO object (CLI internal error).

Cause

The file number does not refer to a quasi file object (QFO).

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8870

8870 The current statement is not associated with any QFO.

Cause

No quasi file object (QFO) file number is associated with the current statement.

Effect

The current operation fails.

Recovery

None. Contact your service provider.

SQL 8871

8871 The NOWAIT tag is not specified in the statement-id.

Cause

A nowait tag was not specified.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8872

8872 New operations cannot be executed while another NOWAIT operation is pending.

Cause

Only one nowait operation at a time is allowed on an SQL/MX statement.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8873

8873 The current statement is already associated with a QFO.

Cause

An existing quasi file object (QFO) is already associated with the current statement.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8874

8874 An error in an insert, update or delete statement caused that statement to be rolled back but statement rollback failed.

Cause

DP2 limits on savepoints is exceeded.

Effect

The operation fails.

Recovery

None.

SQL 8875

8875 An error in an insert, update or delete statement caused that statement to be rolled back without aborting the transaction.

Cause

An insert, update, or delete statement was rolled back because of an error, and the associated transaction was not aborted. The autocommit mode was off for the transaction.

Effect

The work done by the statement is rolled back. Other statements that are part of the transaction are not impacted. The transaction is still active.

Recovery

This is a warning message. Check the additional diagnostics messages, correct the cause, and resubmit the statement.

SQL 8877

8877 A transaction is needed to run this query, one is not already started, and the automatic starting of transactions has been disabled.

Cause

A statement was run that requires a transaction. There is no existing transaction and the transaction attribute AUTOBEGIN is set to OFF.

Effect

The statement fails to run.

Recovery

Either start a transaction or set transaction attribute AUTOBEGIN to ON and rerun the statement.

SQL 8878

8878 Transaction has been doomed. The user should explicitly

Cause

The CONTROL QUERY DEFAULT value for DOOM_USERTRANSACTION is ON, and NonStop SQL/MX encountered an unrecoverable error.

Effect

The transaction is in a doomed state. Users are unable to continue work on this transaction.

Recovery

Use the ROLLBACK WORK statement to undo the transaction explicitly.

SQL 8879

8879 The buffer to return the Query ID is too small.

Cause

Effect

The CLI call fails and the query ID is not returned.

Recovery

Perform the CLI call again with a buffer size large enough to hold the query ID. The len_of_item output parameter from the first CLI call contains the actual size of the buffer required to return the query ID.

SQL 8880

8880 CLI applications are not allowed to remove the current context.

Cause

A CLI application attempted to delete the current CLI context.

Effect

The context is not removed.

Recovery

None. Contact your service provider.

SQL 8881

8881 The specified CLI context handle could not be found.

Cause

A CLI application specified a context handle that does not exist.

Effect

The specified operation on the context is not performed.

Recovery

None.

SQL 8882

8882 Containing SQL is not permitted.

Cause

A stored procedure registered with the NO SQL attribute attempted to access NonStop SQL/MX.

Effect

The corresponding SQL request is rejected.

Recovery

Either change the definition of the stored procedure to allow SQL access, or determine why the stored procedure contains SQL/MX statements that might be called while the stored procedure is executing.

SQL 8883

8883 URD violation checking is currently disabled.

Cause

The server failed to enable UDR violation checking prior to issuing an SQL/MX CLI function call to check or clear the UDR violation flags.

Effect

The operation fails.

Recovery

This is an internal error in the SQL/MX UDR server. Contact your service provider.

SQL 8884

8884 Prohibited SQL statement attempted.

Cause

A stored procedure attempted to execute a transaction-related SQL/MX statement.

Effect

The transaction-related SQL/MX statement is blocked, and the CALL statement fails.

Recovery

Remove the transaction-related statements in the stored procedure and retry the SQL/MX statement.

SQL 8887

8887 The provided buffer to retrieve generated code is either null or not big enough.

Cause

The caller did not provide a buffer with enough capacity to store the generated code.

Effect

The operation fails.

Recovery

Retry the operation after allocating enough buffer size in the calling routine.

SQL 8889

8889 The provided buffer to retrieve Result Set proxy syntax is either null or not big enough.

Cause

The NonStop SQL/MX call-level interface (CLI) function was unable to provide a proxy syntax for a stored procedure result set because the provided target buffer is either null or not large enough.

Effect

The operation fails.

Recovery

Make the CLI call again and use a buffer large enough to hold the proxy syntax. Consider using the len_of_item output parameter from the first CLI call to obtain the actual size of the buffer needed to return the proxy syntax.

SQL 8890

8890 The SQL compiler failed to initialize properly. Query results may differ from what is expected, due to different compiler defaults.

Cause

The SQL/MX compiler failed to initialize correctly.

Effect

Query results might be affected.

Recovery

Stop SQL/MX and restart it.

SQL 8891

8891 Non-ASCII character host variable type was specified for name field.

Where,

name is the name of the field.

Cause

The host variable type for the field name must be ASCII.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 8892

8892 Buffer to return SQL/MP metadata information is too small.

Cause

The buffer where SQL/MP metadata will be returned is too small.

Effect

The operation fails.

Recovery

Define the buffer with a larger size and resubmit.

SQL 8893

8893 The statement argument count does not match the descriptor entry count.

Cause

You specified a statement whose argument count does not match the descriptor entry count.

Effect

The operation fails.

Recovery

Correct the syntax and resubmit.

SQL 8894

8894 Argument argument-name of CLI function function-name is reserved for future use and must be set to string when calling the function.

Cause

A value that was passed into an SQL/MX CLI function containing a reserved parameter was not the value expected by NonStop SQL/MX.

Effect

The CLI function fails.

Recovery

None. Contact your service provider.

SQL 8895

8895 The character set name for the descriptor item SQLDESC_CHAR_SET is not valid.

Cause

You specified an invalid character set name for the SQLDESC_CHAR_SET descriptor.

Effect

The SET DESCRIPTOR fails.

Recovery

Specify a valid character set name and resubmit.

SQL 8896

8896 The character set name1 of a host variable does not match name2 of the corresponding descriptor item (entry number).

Cause

The character set of a character host variable does not match the descriptor item.

Effect

The operation fails.

Recovery

Change the character set declaration of the host variable so that the character set name matches the descriptor item.

SQL 8897

8897 RPC exception occurred in CLI request from non-trusted shadow client to trusted shadow server.

Cause

This is an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8898

8898 An internal error occurred in CLI.

Cause

This is an internal error.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8900

8900 Only ISO88591 and UCS2 host variables can be used to retrieve SQL error or warning messages.

Cause

Host variable used to retrieve error message is not ISO88591 or UCS2 data type.

Effect

The error message cannot be retrieved.

Recovery

Define host variable as either UCS2 or ISO88591 data type.

SQL 8901

8901 The MXUDR server for this statement is no longer running. The statement will be assigned a new MXUDR server if it is executed again.

Cause

During execution of an SQL/MX statement, an attempt was made to contact a nonexistent SQL/MX UDR server.

Effect

The operation fails.

Recovery

Retry the SQL/MX statement.

SQL 8902

8902 An internal error occurred: MXUDR returned a UDR handle that is not valid.

Cause

The SQL/MX UDR server generated an improperly formatted identifier when NonStop SQL/MX was executing a stored procedure.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8903

8903 An attempt was made by SQL/MX to kill the MXUDR server for this statement (process name). PROCESS_STOP_ returned value.

Where,

process name is the name of an SQL/MX UDR server process.

Cause

NonStop SQL/MX received an interrupt signal, possibly caused by an MXCI user pressing Ctrl-C while the SQL/MX UDR server was executing a stored procedure.

Effect

The operation fails, and if PROCESS_STOP_ was successful (as indicated by a return value of 0), the SQL/MX UDR server is stopped.

Recovery

The SQL/MX statement will acquire a new SQL/MX UDR server if it is executed again. If the MXCI user was attempting to halt a long-running stored procedure, investigate to determine whether problems within the stored procedure might be causing the delay.

SQL 8904

8904 SQL/MX did not receive a reply from MXUDR, possibly caused by internal errors while executing user-defined routines.

Cause

During execution of an SQL/MX statement, NonStop SQL/MX did not receive an expected reply from the SQL/MX UDR server.

Effect

The operation fails.

Recovery

Verify that the SQL/MX UDR server is running. If not, the SQL/MX statement will acquire a new SQL/MX UDR server when it is next executed.

SQL 8905

Cause

You attempted to execute a query that uses a User Defined Function for which the user executing the query does not have the EXECUTE privilege.

Effect

The operation fails.

Recovery

You must GRANT the user EXECUTE privilege on the User Defined Function and retry the query.

SQL 8906

8906 An invalid or corrupt MXUDR reply could not be processed, possibly due to memory corruption in MXUDR while executing user-defined routines or an internal error in SQL/MX.

Cause

During execution of an SQL/MX statement, the SQL/MX executor received a message from the SQL/MX UDR server that was unreadable in some way. Either the message was corrupted by the SQL/MX UDR server, or an internal error occurred within the SQL/MX executor.

Effect

The operation fails.

Recovery

If you have linked a native method library into the SQL/MX UDR server, determine whether code in that library could be causing the problem. Otherwise, contact your service provider.

SQL 8907

8907 Procedure procedure-name is registered to return result sets and stored procedure result sets are not yet supported.

Where,

procedure-name is the ANSI name of a stored procedure.

Cause

You are running an SQL/MX version that does not support stored procedure result sets and attempted to compile a CALL statement for a stored procedure that returns result sets. This message indicates that a downgrade has been performed without removing stored procedures that return result sets.

Effect

The SQL/MX statement is not compiled.

Recovery

Migrate to an SQL/MX version that supports stored procedure result sets.

SQL 8909

8909 The request to allocate a stored procedure result set failed because the provided input statement is not a CALL statement.

Cause

A call-level interface (CLI) application attempted to allocate a stored procedure result set but the specified input statement is not a CALL statement. The stored procedure result sets cannot be allocated from statements other than CALL statements.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8912

8912 The request to allocate a stored procedure result set failed. An unexpected internal error was encountered.

Cause

An internal error was detected within the SQL/MX executor during allocation of a stored procedure result set.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8913

8913 The PREPARE operation is not allowed on a stored procedure result set.

Cause

A CLI application attempted to dynamically prepare an SQL statement, and the statement identifier is associated with a stored procedure result set.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8914

8914 An attempt to open a stored procedure result set failed because multiple open operations on the same result set are not allowed.

Cause

A CLI application attempted to open a stored procedure result set cursor that was previously opened.

Effect

The operation fails.

Recovery

None. Contact your service provider.

SQL 8915

8915 An attempt to access a stored procedure result set at position index failed because there is no result set currently available at that position.

Where,

index is an integer specifying a position in the ordered set of result sets returned from a CALL statement.

Cause

A CLI application attempted to access a stored procedure result set at position index, but the number of result sets returned from the CALL statement was less than index.

Effect

The operation fails.

Recovery

None. Contact the GMCSC and report this condition.

SQL 8916

8916 The request to allocate a stored procedure result set at position index failed because the position is out of range. Valid positions range from one up to the maximum number of result sets that can be returned from the specified CALL statement, which in this case is max-result-sets.

Where,

index is an integer specifying a position in the ordered set of result sets returned from a CALL statement;

max-result-sets is the maximum number of result sets that can be returned from the associated CALL statement.

Cause

A call-level interface (CLI) application specified an invalid index in a request to bind a stored procedure result set to a specific result set index. A valid index ranges from 1 to the maximum number of result sets that can be returned from the CALL statement.

Effect

The operation fails.

Recovery

None. Contact GMCSC and report this condition.

SQL 8917

8917 The request to allocate a stored procedure result set at position index failed because a result set at position index already exists.

Where,

index is an integer specifying a position in the ordered set of result sets returned from a CALL statement.

Cause

A call-level interface (CLI) application attempted to bind multiple stored procedure result set statements to the same result set index.

Effect

The operation fails.

Recovery

None. Contact GMCSC and report this condition.

SQL 8918

The Runtime Statistics infrastructure is not running or restarted on CPU n. Unable to return Runtime Statistics.

Where,

n is the CPU number.

Cause

The user issues a command to retrieve runtime statistics, however the runtime statistics infrastructure (the SSCP and SSMP processes) is not running or restarted on the CPU.

Effect

Runtime statistics information is not retrieved, and the command fails.

Recovery

If RTS subsystem is not running, start the RTS subsystem. Restart the SQL/MX Connectivity Service or SQL/MX client to ensure that RTS is enabled.

SQL 8919

Unable to retrieve Runtime Statistics for invalid query ID qid.

Where,

qid is the query ID.

Cause

The runtime statistics command contains a query ID that is not in a valid format. Or, the display statistics command contains a query ID that is not in a valid format. The system is unable to parse the input query ID to retrieve the node-number (and thus the node-name) and CPU number.

Effect

Runtime statistics information is not retrieved, and the command fails.

Recovery

Issue the command with a valid query ID.

SQL 8920

Invalid CPU or PID passed in. Unable to retrieve Runtime Statistics.

Cause

The DISPLAY STATISTICS FOR CPU <cpu> or a DISPLAY STATISTICS FOR PID <pid> command contains an invalid CPU or PID.

Effect

Runtime statistics information is not retrieved, and the command fails.

Recovery

Issue the command with valid values for the CPU or PID.

SQL 8921

Cause

The DISPLAY STATISTICS FOR CPU or PID or QID command timed out, since SQL/MX is unable to obtain the statistics from RTS components within the specified timeout period.

Effect

Runtime statistics information is not retrieved, and the command fails.

Recovery

Increase the timeout period using SET SESSION DEFAULT RTS_TIMEOUT n command. If the problem persists, check if all RTS processes are running or the system is busy.

SQL 8922

Cause

The DISPLAY STATISTICS FOR CPU or PID or QID command failed to obtain statistics from all CPUs.

Effect

The runtime statistics information returned may be devoid of statistics from one or more CPUs. If the CPU is involved in the query, the statistics may not be accurate.

Recovery

Reissue the command. If the problem persists, contact your service provider.

SQL 8923

Cause

The query ID does not exist or the statistics information for the given query ID is freed.

Effect

Runtime statistics information is not retrieved for the input query ID.

Recovery

Reissue the command with an existing query ID or issue the command in time before the statistics information is freed.

SQL 8924

8924 Merged Runtime Statistics is null.

Cause

The CLI call SQLCLI_GetStatisticsItems() tries to retrieve the runtime statistics information. The runtime statistics information is not available in current SQL context.

Effect

The CLI call fails and the runtime statistics information is not retrieved.

Recovery

Retry the CLI call.

SQL 8925

8925 The given query ID is not matching the query ID in the merged runtime statistics.

Cause

The CLI call SQLCLI_GetStatisticsItems() tries to retrieve the runtime statistics information for the given query ID. The query ID does not match the ID stored in current SQL context.

Effect

The CLI call fails and the runtime statistics information is not retrieved.

Recovery

Check the query ID and retry the CLI call.

SQL 8926

8926 The given SQLSTATS_DESC_STATS_TYPE is not found in the merged runtime statistics.

Cause

The CLI call SQLCLI_GetStatisticsItems() tries to retrieve the runtime statistics information with specified SQLSTATS_DESC_STATS_TYPE in SQLSTATS_ITEM.stats_type. The SQLSTATS_DESC_STATS_TYPE is not found in the merged runtime statistics.

Effect

The CLI call fails and the runtime statistics information for the SQLSTATS_DESC_STATS_TYPE is not retrieved.

Recovery

Check the SQLSTATS_DESC_STATS_TYPE passed in SQLSTATS_ITEM.stats_type and retry the CLI call.

SQL 8927

8927 The given SQLSTATS_ITEM_ID is not valid for the given SQLSTATS_DESC_STATS_TYPE.

Cause

The CLI call SQLCLI_GetStatisticsItems() tries to retrieve the runtime statistics information with the specified SQLSTATS_ITEM_ID in SQLSTATS_ITEM.statsItem_id and SQLSTATS_DESC_STATS_TYPE in SQLSTATS_ITEM.stats_type. The specified SQLSTATS_ITEM_ID is not found in the merged runtime statistics.

Effect

The CLI call fails and the runtime statistics information for the SQLSTATS_ITEM_ID is not retrieved.

Recovery

Check the SQLSTATS_ITEM_ID passed in SQLSTATS_ITEM. statsItem_id and SQLSTATS_DESC_STATS_TYPE passed in SQLSTATS_ITEM.stats_type and retry the CLI call.

SQL 8928

8928 The length of the input array SQLSTATS_DESC is not sufficient for the merged runtime statistics.

Cause

The CLI call SQL_EXEC_GetStatistics2() tries to retrieve the runtime statistics description, however, the buffer sqlstats_desc is not large enough to hold all the SQL statistics description. max_stats_desc specifies the size of sqlstats_desc. When this error is returned, The no_returned_stats_desc (if not NULL) contains the actual number of the SQLSTATS_DESC.

Effect

The CLI call fails and the SQL statistics description is not retrieved.

Recovery

Retry the CLI call with a buffer large enough to hold all SQLSTATS_DESC. To determine the buffer size required to return all the SQLSTATS_DESC, refer to the no_returned_stats_desc output parameter from the previous CLI call SQL_EXEC_GetStatistics2().

SQL 8934

8934 The MAXVALUE for the sequence generator has been exceeded

Cause

The internal sequence generator table has reached either the maximum value for IDENTITY column data type or the MAXVALUE.

Effect

The operation fails.

Recovery

There is no recovery when IDENTITY column data type maximum is reached. If MAXVALUE is reached, define a new MAXVALUE using ALTER TABLE ALTER COLUMN statement, and resubmit the statement.

SQL 8935

8935 The sequence generator update failed, see additional diagnostics for failure details.

Cause

The update to the internal sequence generator table failed.

Effect

The operation fails.

Recovery

Additional error codes are returned for the update failure. Proceed with the recovery procedures recommended for these additional error codes.

SQL 8936

8936 seq-name.CURRVAL is not initialized in the current session.

Where,

seq-name is the ANSI name of the sequence generator.

Cause

The CURRVAL pseudo column for a sequence generator cannot be accessed unless the NEXTVAL pseudo column for that sequence generator is successfully accessed at least once in the same query or session.

Effect

The statement fails.

Recovery

Execute a statement that accesses NEXTVAL in the same session.

SQL 8970

8970 Duplicate format elements for format-string.

Where,

format-string is the datetime component.

Cause

A component of datetime (day, month, year, hour, minute, or second) is repeated in the format string.

Effect

The operation fails.

Recovery

Ensure each component of datetime occurs only once in the format and value strings and retry the operation.

SQL 8971

8971 function-name internal error for reason.

Where,

reason is additional information about the internal error.

Cause

An internal error occurred while executing the function code.

Effect

The operation fails.

Recovery

None. Contact your service provider.

See Contacting your service provider.

SQL 8972

8972 Invalid value value-string for reason.

Where,

value-string is the invalid value string argument.

reason is the format string argument.

Cause

The specified value for a datetime format element does not match the valid range of values for that format element.

Effect

The operation fails.

Recovery

Specify a value that matches the format element and retry the operation.

SQL 8973

8973 Value string value does not match with format format-string.

Where,

value is the value string argument.

format-string is the format string argument.

Cause

The value string does not match the format string specified as an argument to the datetime function. Some of the individual elements in the value and format strings may match but the strings do not match. One reason for the error is when the format string ends before the value string or conversely.

Effect

The operation fails.

Recovery

Specify the correct value string that matches with the format string and retry the operation.

SQL 8974

8974 Arguments for function-name must be of character type.

Cause

Either the value string or the format string argument is not of the character data type.

Effect

The operation fails.

Recovery

Ensure that both arguments to the function are of the character data type and retry the operation.

SQL 8975

8975 Unable to allocate memory.

Cause

Execution of the function encountered an error while trying to allocate memory probably due to memory pressure on the system.

Effect

The operation fails.

Recovery

Check memory pressure on the system and retry the operation when memory load is less. If problem persists, contact your service provider.

See Contacting your service provider.