SQL++ Error Codes

A connection the cbq-shell was trying to make was refused by the remote partner.

Verify the connection URL and try again.

The protocol scheme in the cbq-shell connection URL is not supported.

Correct the URL ensuring only a supported scheme is used. Schemes: http, https, couchbase, couchbases

The noted host could not be found by the cbq-shell.

Correct the host in the connection URL and try again.

The cbq-shell connection URL does not contain a host name or IP address.

Correct the the connection URL and try again.

A connection in the cbq-shell has not been attempted or has failed.

Issue the connect command to connect to a server.

Review the details of the error reported.

Contact support.

The URL could not be properly parsed.

The URL contains an invalid host.

The URL contains an invalid port.

A port number was specified with couchbase:// or couchbases:// protocol scheme in the URL.

Correct the URL and retry.

The cbq-shell input commands file could not be read.

The cbq-shell command history file could not be read.

Review the details reported and take corrective action.

The cbq-shell command history file could not be written to.

Review the details reported and take corrective action.

The cbq-shell input commands file could not be opened.

The size of the cbq-shell input stream could not be determined.

The the cbq-shell input stream was empty.

The cbq-shell command history file could not be opened.

Review the details reported and take corrective action.

An empty password was entered at the cbq-shell password prompt.

A password entered at the cbq-shell prompt contains invalid characters.

An error occurred reading from the terminal for the cbq-shell password prompt.

Enter only a valid password at the prompt.

review the details reported and take corrective action.

The cbq-shell command line flags include the password but not the user name.

Pass both user and password on the cbq-shell command line.

The username could not be found in the credentials cbq-shell option value.

Correct the value and retry.

The credentials cbq-shell option value was not in the correct format.

Correct the value and retry.

The command entered at the cbq-shell prompt was invalid.

The cbq-shell help command could not find the command specified.

Correct the command and retry.

An attempt was made access a parameter that doesn't exist via cbq-shell commands.

Verify the parameter is correctly named and the sequence of commands means it is defined when expected.

A cbq-shell command was attempted but too many arguments were supplied.

Consult the command help facility, correct the command and retry.

A cbq-shell command was attempted with insufficient arguments.

Consult the command help facility, correct the command and retry.

The cbq-shell value stack was empty and an attempt to pop or set a value was attempted.

Contact support.

An attempt was made to list cbq-shell command aliases and no aliases exist.

The cbq-shell batch command line option was set to an invalid value.

Correct the command line option and retry.

Operating in batch mode, cbq-shell failed to write the command to the batch file.

Review the details reported and take corrective action.

Contact support.

Contact support.

Review the reported error.

Contact support.

The cbq-shell was trying to write output and encountered an error.

Review the details reported and take corrective action.

The cbq-shell echo contained an unequal number of double quotation marks.

Correct the command and retry.

The cbq-shell connection URL was not passed as the engine argument and was not the last argument.

Pass the connection URL using the engine argument flag or as the final argument on the command line.

The argument to a cbq-shell command was not a supported format.

The value specified for a cbq-shell predefined value was not valid.

Correct the argument or value type.

The cbq-shell failed to obtain the cluster map from the server.

Review the connection URL is correct and still valid.

An invalid argument was supplied to the cbq-shell redirect command.

Consult the command help facility, correct the command and retry.

cbq-shell failed to initialise the terminal for vi emulation mode.

(Windows) Ensure cbq-shell is not being run in a legacy console window.

Don't use cbq-shell's vi emulation mode.

Multiple endpoints were listed in the cbq-shell connection URL with differing protocols.

Ensure all endpoints listed are using the same protocol.

Contact support.

A request was submitted using the GET method and attempted a statement that modifies data.

A request was received with the ˝readonly˝ parameter set to true and attempted a statement that modifies data.

A PREPARE statement preparing a statement that modifies data was received and the ˝auto_execute˝ was set to true.

Use POST to submit write statements and ensure the ˝readonly˝ request parameter is not set or is set to false.

Ensure ˝auto_execute˝ is false when ˝readonly˝ is true (or when using the GET method) and preparing statements that modify data.

The service endpoint supports only GET & POST HTTP methods. All other HTTP methods are not supported.

Use a supported method to submit requests.

The noted feature and value combination is reserved but is not implemented.

Use only supported feature and value combinations.

The value supplied for the noted parameter is unknown.

Ensure the value supplied is a supported value in the required format for the request parameter noted.

There was an error in processing as detailed in the message. e.g. a non-numeric string value passed as the value for a request parameter that is expected to be numeric.

Where the error is derived from user controlled data, correct the data.

A value was not supplied for the required parameter.

Provide valid values for all required parameters. e.g. ensure a user and password are supplied for all requests and a scan_vector is supplied for requests using AT_PLUS consistency level.

Multiple values have been supplied for a parameter or two mutually exclusive parameters are both enabled.

Ensure all request parameters including named statement parameters, are unique and supplied only once.

Ensure mutually exclusive parameters are not simultaneously enabled.

An unknown request parameter was received.

Pass only valid request parameters.

Check parameter names for typographical errors.

The value supplied for «feature» was not of the expected type.

Correct the value and re-submit the request.

The specified request time-out was reached.

Check the statement is correctly constructed and using the expected plan.

Revise the time-out upward to accommodate the statement.

The named parameter's value was invalid for the reason noted in the message.

Set the parameter to a valid value for the request.

An error occurred whilst writing results to the output stream.

Please contact support.

The request parameter client_context_id contains one or more of the noted invalid characters.

Revise the value for client_context_id.

The HTTP request header field ˝Accept˝ was not set to a supported value.

Change the header field to ˝*/*˝, ˝application/json˝ or ˝application/xml˝.

The request identified by «id» does not exist.

An invalid scan vector array element was found.

Correct the scan vector.

An entry in the scan vector contained a sequence number that was not an unsigned 64-bit integer.

An entry in the scan vector contained a v-bucket UUID that was not a string value.

A request requiring a body did not include one.

Resubmit a valid request.

The HTTP request method noted is not supported by the endpoint.

A topology change was in the process of removing the node.

A topology change was in the process of removing the node.

A ping request has determined the service was not healthy.

Examine the diagnostic logs to ascertain the reason for this state.

Contact support.

Currently unused.

Currently unused.

Currently unused.

Currently unused.

The number of errors raised has reached the limit.

Consult the errors to ensure the statement is operating as expected.

Revise the ˝error_limit˝ request parameter as necessary.

The request breached a limit for the tenant.

Retry the request in accordance with «retry».

The request queue has reached its limit

Verify the server is processing requests.

The server aborts servicing a request when it detects the client has closed its connection.

A write to the request output stream timed out. Individual writes that make up the response must not block indefinitely, which typically occurs when the client isn't reading the response stream.

Check the application is reading response stream fast enough to avoid blocking writes.

The request was halted by admission control due to low available memory.

The server encountered an error when establishing a connection to «what».

Contact support.

«reason» prevented correct start-up of the service statistics monitor.

Contact support

An invalid URL was encountered for the noted component.

Contact support.

Contact support.

Contact support.

An unknown setting was supplied in a request to the settings rest endpoint.

Provide only valid settings in the request.

The value provided for the noted setting was not of the correct type.

Correct the value and re-submit the request.

Contact support.

Contact support.

Contact support.

Contact support.

Contact support

Contact support

Contact support

Request received without suitable credentials.

Failure to authenticate with given credentials.

Authenticated user lacks required privileges.

Review the embedded «message» information for more detail on why the operation failed.

Contact support

An attempt has been made to update the SSL certificate but the server does not have SSL enabled.

Review the server configuration.

Define a different qualifier or update the existing one.

Refer to the ˝logging qualifiers section of the documentation.

An attempt was made to add a qualifier that is not a known.

Check the qualifier specified is valid.

Refer to the ˝logging qualifiers section of the documentation.

An attempt was made to access a qualifier that was not set.

Ensure the intended qualifier has been set.

A attempt was made to update a qualifier that isn't unique.

Only attempt to update unique qualifiers. Non-unique qualifiers may only be added/removed.

The data type of the «value» was incompatible with the qualifier.

Correct the value for the qualifier and re-submit the request.

Contact support.

A prepareds endpoint PUT request was received but the body was empty or could not be read.

contact support

An error occurred with a manual First Failure Data Capture (FFDC) invocation.

Wait until the specified reported minimum time before attempting a further invocation.

A request was made to the diagnostic log endpoint and there was a error accessing the file.

Ensure the diagnostic log file being accessed exists for the duration of the request.

An error occurred when starting request capture for workload reporting.

Review the error and correct any configuration issues.

The value provided for the setting is invalid.

Consult the documentation for the valid values for the workload settings. Review the configuration and correct the value.

The value provided for AWR configuration is invalid.

Review the configuration and correct the value.

The value must be a valid object or a string encoding a valid JSON object.

An error occurred distributing the workload settings to other Query nodes.

Contact support.

An AWR operation encountered a condition that needs attention.

Check the error message for recommended actions. Or consult the documentation for guidance.

An Workload reporting related operation was attempted on a Community Edition Couchbase cluster.

Consult the documentation for the feature you are trying to use.

Correct the syntax and re-submit the request. Look for incorrectly spelled keywords, use of reserved words as identifiers, incorrect or omitted punctuation and delimiters or invalid grammar.

If using the cbq-shell, the \syntax command may help with grammar issues.

An invalid escape sequence was encountered whilst parsing a string value. Escape sequences are introduced with a backslash (Reverse Solidus, U+005C) and literal backslashes must be escaped.

Valid escape sequences are: \b, \f, \n, \r, \t, \/, \\, \", \`, \u#### (where #### is a Unicode symbol number in hexadecimal).

An opening quotation mark defining a string was encountered without any further characters.

Correctly delimit all string values in statements.

Contact support.

Contact support.

A field reference in the statement was not fully qualified and there were multiple keyspaces it could have referred to. e.g. SELECT a FROM b, c WHERE ...

Fully qualify references when the potential for ambiguity exists. e.g. SELECT b.a FROM b,c WHERE ...

There was a non-unique binding name in a LET or WITH clause.

Use unique names for all bindings in a statement.

A statement included a correlated reference that was not permitted.

If encountered with a existing prepared statement, re-prepare the statement.

Contact support.

Invalid input was submitted, either a statement or expression, depending on context.

Submit only valid SQL++ statements or expressions.

The statement includes portions that violate semantic constraints.

The cause will contain more detail on the violation; revise the statement and re-submit.

An internal error occurred during semantics check for the query.

Contact support.

Join type hints are only supported for ANSI join and nest operations.

Review the statement and revise the operation or omit the hints.

USE KEYS is not supported in this context.

USE INDEX is not supported in this context.

A lookup merge statement specified a document key. e.g. MERGE INTO default USING [{},{} AS source ON KEY 'aaa' WHEN NOT MATCHED THEN INSERT ('key',{})]

Refer to the documentation for lookup merge statements.

An ANSI merge statement did not include the document key specification. e.g. MERGE INTO default USING [{},{} AS source ON default.id IS VALUED WHEN NOT MATCHED THEN INSERT ({})]

Refer to the documentation for ANSI merge statements.

The USE INDEX hint is not supported with lookup merge statement targets. e.g. MERGE INTO default USE INDEX (ix) USING [{},{} AS source ON KEY 'aaa' WHEN NOT MATCHED THEN INSERT ({})]

Refer to the documentation for lookup merge statements.

The USE INDEX hint is not supported with lookup merge statement source.

Refer to the documentation for lookup merge statements.

Mixing ANSI and non-ANSI joins. e.g. SELECT * FROM default d1 JOIN default d2 ON d1.id = d2.id JOIN default d3 ON KEYS 'aaa'

Mixing ANSI and non-ANSI NEST statements.

Revise the statement to use only one type of operation.

A violation of the window function semantic restrictions was present in the statement.

Revise the statement to remove the violation.

An attempt was made to use the noted feature that is only available in the Enterprise Edition of the product.

Consult the documentation for the feature you're trying to use.

An attempt was made to run advise on an unsupported statement.

Refer to the documentation for ADVISE.

An attempt was made to use the ADVISOR() function out side of a select statement's projection.

Refer to the documentation for ADVISE.

An attempt was made to use the advisor function on the results from a keyspace fetch.

Refer to the documentation for ADVISE.

A keyspace in the statement was not an explicit path and there was no USE KEYS clause.

Revise the statement to include an explicit path or a USE KEYS clause as appropriate.

A keyspace in the statement was not an explicit path and there was a USE INDEX clause.

Revise the statement to include an explicit path or remove the USE INDEX clause as appropriate.

An attempt was made to run UPDATE STATISTICS for a non-GSI index.

Do not run UPDATE STATISTICS on a non-GSI index.

A statistics update was attempted using the INDEX ALL clause on a bucket.

Do not run UPDATE STATISTICS with INDEX ALL on buckets.

A statistics update was attempted on an index expression including ˝self˝.

Revise the index expression to not include ˝self˝.

Refer to the documentation for UPDATE STATISTICS.

An expression in the index definition was not indexable (e.g. a constant).

Revise the definition to include only indexable expressions.

An attempt was made to create a GSI index and INCLUDE MISSING was specified for a non-leading key.

An attempt was made to create a non-GSI index and INCLUDE MISSING was specified.

An attempt was made to create an index using FLATTEN_KEYS, and INCLUDE MISSING was specified for an argument other than the initial argument.

Attributes specified for FLATTEN_KEYS.

Revise the statement to remove the attributes on the FLATTEN_KEYS() expression.

NOTE: Arguments passed to FLATTEN_KEYS() may have attributes.

FLATTEN_KEYS specified outside of CREATE INDEX or UPDATE STATISTICS or was surrounded by a function.

Refer to the documentation for flatten keys.

ALL and/or DISTINCT used in an invalid location.

Revise the statement.

An attempt to use SELF as an index key was made.

Remove SELF from the the index definition.

FTS was specified as the index provider for a primary index.

A join hint was specified on the first term of a join.

Revise the statement to remove the hint on the first join term.

The ORDER BY direction or NULLS position was not a valid constant, named, positional or function parameter.

Revise the ORDER BY direction or NULLS position to be a valid constant, named, positional or function parameter.

The statement specifies restricted syntax in a recursive common table expression definition.

Revise the statement removing the restricted syntax.

The statement includes a recursive common table expression that references itself in the first branch of the defining UNION. e.g. WITH RECURSIVE rcte AS (SELECT * FROM rcte UNION SELECT * FROM rcte) SELECT 1

Correct the recursive common table expression definition.

The statement includes a recursive common table expression that references itself more than once in the recursive branch of the defining UNION. e.g. WITH RECURSIVE rcte AS (SELECT * FROM default UNION SELECT * FROM rcte, rcte) SELECT 1

Revise the statement removing the duplicate reference.

The statement includes a recursive common table expression with an OPTIONS clause object containing an invalid option. e.g. WITH RECURSIVE rcte AS (SELECT * FROM default UNION SELECT * FROM rcte) OPTIONS {'bad':1} SELECT 1

Refer to the documentation for permitted options.

A recursive common table expression was specified in a NEST clause.

A recursive common table expression was specified in an UNNEST clause.

A recursive common table expression was specified in an OUTER JOIN clause.

Revise the statement to remove the unsupported reference.

The request without a memory quota set contained a recursive common table expression without an explicit document limit that produced more results than the implicit limit and was stopped.

Review the statement and its control of the recursion. Use a memory quota to guard against runaway recursion or specify an explicit document limit for the common table expression.

The request without a memory quota set contained a recursive common table expression without an explicit level limit exceeded the implicit limit and was stopped.

Review the statement and its control of the recursion. Use a memory quota to guard against runaway recursion or specify an explicit level limit for the common table expression.

The expression specified in the cycle clause is not an identifier or path term.

Revise statement removing or modifying the invalid cycle clause expression.

A vector search function cannot be used together with certain features of a query, e.g. GROUP BY clause or Window function.

Revise the statement to remove the offending features of the query.

Cannot mix index attribute VECTOR with <<attr>> for index key <<key>> in CREATE INDEX statement.

Revise the statement to remove the offending index attribute.

Only a single index key with VECTOR attribute is supported in CREATE INDEX statement.

Revise the statement to include only a single index key with VECTOR attribute.

Only a single index key (with VECTOR attribute) is supported in CREATE VECTOR INDEX statement.

Revise the statement to include only a single index key (with VECTOR attribute).

An index key with VECTOR attribute must be included in CREATE VECTOR INDEX statement.

Revise the statement to include an index key with VECTOR attribute.

A vector function (<<term>>) in ORDER BY clause uses a non-constant for specifying <<option>>.

Revise the statement to use a constant for the order option.

A vector function (<<term>>) in ORDER BY clause uses an invalid option <<option>>.

Revise the statement to use only ASC and NULLS LAST order options.

An array index key with VECTOR attribute is specified using DISTINCT in CREATE INDEX statement.

Revise the statement to remove DISTINCT in array index key with VECTOR attribute.

An index key (<<name>>) with VECTOR attribute is specified as an object construct or array construct in CREATE INDEX statement.

Revise the statement to not use a constant construct in index key with VECTOR attribute.

Contact support.

A parsing error occurred when re-preparing a statement.

There was an error building the plan when re-preparing a statement.

There was an error storing the re-prepared plan in the cache.

Prepare the statement under a new name.

Contact support.

The planVersion in the encoded plan exceeds the plan version supported by the current server: 800

Upgrade the server to a version that supports the planVersion specified in the encoded plan.

The mismatch triggered a re-prepare; verify that the re-prepared plan uses the expected indexes.

Keyspace, scope or index referenced in the plan is missing or has changed since the plan was generated.

Index is no longer online or does not exist.

Keyspace UUID has changed, indicating recreation.

Ensure that all referenced keyspaces, scopes, buckets, and indexes still exist and are online.

Failure in verification led to a re-prepare; inspect the re-prepared plan.If it appears sub-optimal, force prepare the statement after making the required changes.

The statement includes an unnamed FROM term.

Revise the statement aliasing terms that are unnamed (i.e. non-keyspace path terms).

The statement defines the alias multiple times for different elements.

Revise the statement to ensure aliases are unique.

The statement contains a duplicate reference to the noted alias in a FROM expression.

Revise the statement to ensure alias references are unique.

The statement contains an index join FOR clause referencing an unknown alias.

Revise the statement correcting the alias.

A correlated sub-query was specified but a suitable index on the keyspace was not available to support it.

Create the necessary index.

Check the expected index is online.

A primary scan supporting a correlated sub-query returned more keys than permitted.

Create an appropriate secondary index to support the sub-query.

The prepared statement referenced in the request doesn't exist.

Verify that a valid prepared statement name is specified.

A request with a non-character string ˝prepared˝ parameter value was received.

Automatic execution (auto_execute) failed to produce a prepared statement.

Inter-node prepared statement distribution failed.

Ensure a valid value is passed for ˝prepared˝.

Contact support.

A prepared statement with the same name was already defined.

Use a unique name for each prepared statement.

Delete unwanted prepared statements.

The ˝encoded_plan˝ parameter received for a prepared statement didn't match the cached plan for the statement.

Different nodes had a plan of the same name but their plans differed.

Resubmit the request and the cached plan will be used.

Contact support.

The name in an encoded plan doesn't match the prepared statement's name.

Correct the request if passing an encoded plan.

Delete the entry from the prepareds cache.

Contact support.

The query context in an encoded plan doesn't match the prepared statement's query context.

Correct the request if passing an encoded plan.

Delete the entry from the prepareds cache.

Contact support.

Don't use predefined names for prepared statements. Predefined names have a double underscore ('__') prefix and include: '__get','__insert','__upsert','__update' and '__delete'.

There was no available index to support the index join or NEST on the noted term.

Create an appropriate secondary index to support the join or NEST statement.

An expression term in a from clause specifies USE KEYS or USE INDEX. e.g. SELECT * FROM (SELECT * FROM default) a USE KEYS['key']

Revise the statement removing the invalid clauses or expression term.

No active Index service nodes were found in this cluster.

Ensure the Index service is defined and operational in the cluster before attempting index operations.

The statement was attempting to scan the keyspace but there was no index available to support the scan.

Create a appropriate index to support the scan.

A statement was attempting to scan a keyspace using a primary index however the index was not online.

Check the state of the index and build it if necessary.

Create a appropriate index to support the scan.

The statement contained grouping and an expression in the projection referenced a value that was not a grouping key or an aggregate. e.g. SELECT a FROM b GROUP BY c

Revise the statement to use only grouping keys or aggregates in the projection.

An attempt was made to create an index with a name that already exists.

Verify that existing index has the desired definition.

Use unique index names.

A statement with multiple FROM terms includes meta-data function without a qualifying argument.

Add the term qualification argument to the meta-data function.

The GSI indexer doesn't support descending key ordering.

An internal error occurred whilst generating the query plan.

Contact support.

An ALTER INDEX statement was attempted but is not supported by the indexer.

Drop and re-create to alter an index.

The statement contains an ANSI JOIN with the noted alias and no index exists to support it.

The statement contains an ANSI NEST with the noted alias and no index exists to support it.

Create a appropriate index to support the operation.

The statement includes an index partitioning clause that isn't supported by the indexer.

An attempt was made to define an index with a duplicate name.

An attempt was made to manage an index that was not defined.

An operation the user lacked necessary permissions for was attempted on an index.

An internal error occurred in the GSI sub-component.

Review the reported error for more detail on why the operation failed and possible user actions.

Review the error details for possible user actions. GSI will typically handle this condition and retry the operation automatically when appropriate. The state of index build operations can be monitored via the GSI endpoint or system:indexes collection.

GSI was unable to write to a temporary file for the request as the configured temporary disk space limit was reached.

Check the settings indicated permit sufficient space for the operation.

Review active statements and their temporary space requirements.

Query uses Search() as predicate with KNN, but there is no matching FTS index

Create appropriate FTS index

The server was operating in ˝serverless˝ mode and the request attempted to pass an encoded plan for execution.

Submit the statement text for planning and execution.

Contact support.

A key in a USE KEYS clause was not a string. e.g. SELECT * FROM default USE KEYS[123;]

Correct the key in the statement.

Clustering was unable to add a Query service node due to the detailed incompatibility.

A sub-component such as GSI may be reporting an error.

An internal error occurred.

If reported by a sub-component, review the error details for appropriate actions.

Contact support

The server encountered an internal error that resulted in a panic which halted request processing.

Contact support

Contact support

The request has a USING clause and provides parameters.

The request has a USING clause that includes a non-static value.

Either provide parameters or use a USING clause.

Use only static value in a USING clause.

A projection EXCLUDE clause in the statement contains a string reference that cannot be parsed.

Revise the statement to use only valid expressions in projection EXCLUDE clauses.

An order by operation was unable to spill to disk as the temporary space quota was hit.

A group by operation was unable to spill to disk as the temporary space quota was hit.

An ordered sequential scan was unable to spill to disk as the temporary space quota was hit.

Review the Query service temporary space quota setting meets with requirements.

Review statements to reduce the amount of data sorted and grouped.

Create a primary index to support ordered document key operations.

The INSERT operation was using a sequential scan exhausted the space reserved to exclude new keys.

The space reserved to record keys processed by the UPSERT statement was exhausted.

Divide the statement into portions that don't exceed the key validation space.

Create a suitable secondary index to support the statement.

An attempt was made to access a URL outside of the configured list.

An attempt was made to access a restricted URL using the CURL() function.

An attempt was made to access an invalid URL.

The CURL() function failed to complete within the specified time limit.

An invalid option was passed to the CURL() function.

The CURL() function failed to access the URL for the reason noted.

Check the server configuration permits access to the URL.

Don't attempt to access restricted URLs.

Ensure the URL is correctly formed with a valid, supported scheme.

Ensure the time limit specified is suitable for the URL response time.

Refer to the documentation for valid options.

Depending on the error, contact your administrator or support.

A nested statement was stopped when the nesting statement stopped.

Verify it is expected that the nesting statement was stopped.

The noted error occurred during the evaluation of the indicated item.

Review the indicated error and it's actions.

The SQL++ abort() function was called in the statement. e.g. SELECT abort('An example cause')

Contact support

The statement failed to build a query plan for an embedded query.

An internal error occurred writing the plan as JSON.

Contact support.

Contact support.

Ensure date values are in the range -9999-01-01 12:00:00.000000000 UTC to 9999-12-31 09:59:59.999000000 UTC.

Correct the date format specification.

A date function converting a string to a date encountered an invalid element in the string, such as a numeric month outside the range 1-12.

Correct the date string value.

A date function converting a string to a date failed to parse the input string according to the format.

Correct the date string value.

A date function operating on elements in a date value was given an invalid date component.

Correct the date component specified.

A date function manipulating a component of a date value was provided a non-integer number.

Correct the argument to the date function.

A date function argument was not of the correct type.

Correct the argument to the date function.

A date value or function argument includes an unknown or invalid timezone.

Correct the timezone in the date value or function argument. Absolute offsets are recommended in place of time zone names.

Contact support.

An expression in an EXCLUDE clause was invalid.

An expression in an argument to OBJECT_REMOVE_FIELDS() was invalid.

Revise the statement providing valid a expression.

An expression in an EXCLUDE clause is not supported.

An expression in an argument to OBJECT_REMOVE_FIELDS() is not supported.

Revise the statement providing valid a expression.

An ARRAY_RANGE() call exceeds the permitted limit for the number of elements produced.

An ARRAY_REPEAT() call exceeds the permitted limit for the number of elements produced.

A REPEAT() call exceeds the permitted limit for the resulting string's size.

A DATE_RANGE_STR() call exceeds the permitted limit for the number of values produced.

A DATE_RANGE_MILLIS() call exceeds the permitted limit for the number of values produced.

Revise the function arguments to produce results within the permitted limit.

An arithmetic operation dividing by zero was encountered during the statement evaluation.

If required, revise the statement as necessary to avoid such operations.

Contact support.

Contact support.

Contact support.

The statement includes an INSERT operation with a non-string key value. e.g. INSERT INTO default VALUES(1,{'the':'value'})

Revise the statement to ensure keys are always string values.

The statement includes an INSERT operation with a non-OBJECT options value. e.g. INSERT INTO default VALUES('the_key',{'the':'value'},null)

Revise the statement to ensure insert options are always provided as an object value or omitted if unneeded.

Contact support.

The UPSERT statement was trying to modify the same key multiple times. e.g. UPSERT INTO default VALUES ('key0',{}),('key0',{})

Revise the statement to ensure that keys are unique.

Contact support.

The statement includes an UPSERT operation with a non-string key value. e.g. UPSERT INTO default VALUES(1,{'the':'value'})

Revise the statement to ensure keys are always string values.

Contact support.

Contact support.

Contact support.

Contact support.

Contact support.

An attempt was made to update a field that doesn't support updating or to set an unsupported value for the field.

Revise statement to not update the field.

Contact support.

The request parameter ˝scan_vector˝ was specified for the request which references multiple keyspaces.

Use the ˝scan_vectors˝ request parameter with statements referring to multiple keyspaces.

The determination of dynamic privileges required by the request failed.

Revise the request to ensure all keyspace references can be resolved enabling dynamic authorisation to proceed.

The determination of transaction privileges required by the request failed.

Verify the user is permitted to run transaction statements.

A role grant or revoke statement referred to a user that didn't exist.

A user alter or drop statement referred to a user that didn't exist.

Verify the user referenced in the statement exists prior to executing the statement.

A create user command was attempted but the user specified already existed.

Revise the statement if intending to create a different user.

A create user statement creating a ˝local˝ domain user did not specify the password attribute.

A create or alter user statement for a ˝remote˝ domain user specified the password attribute.

Specify the password when creating ˝local˝ domain users.

Do not specify the password when creating or altering ˝remote˝ domain users.

A create group command was attempted but the group specified already existed.

Revise the statement if intending to create a different group.

A group role grant or revoke statement specified a group that was not defined.

A group alter or drop statement specified a group that was not defined.

A create or alter user statement specified a group that was not defined.

Ensure the group exists before attempting role operations.

Ensure the group exists before attempting to alter or drop it.

Ensure the group exists before assigning to a user.

A create group statement did not specify any roles.

Specify at least one role when creating a group.

A create user statement did not specify any attributes.

An alter user statement did not specify any attributes.

A create group statement did not specify any attributes.

An alter group statement did not specify any attributes.

Specify at least one attribute when creating users or groups.

A role in a grant or revoke statement requires qualification with a keyspace.

A role in a group create or alter statement requires qualification with a keyspace.

Revise the statement to provide the necessary keyspace qualification.

An attempt was made to specify a scope role as a collection role.

Correct the role qualification in the statement.

A keyspace qualification has been provided for a role that isn't qualified by keyspace in a grant or revoke role statement.

A keyspace qualification has been provided for a role that isn't qualified by keyspace in a group create or alter statement.

Remove the qualification from the role that isn't qualified by keyspace.

A keyspace qualification provided in a grant or revoke role statement was invalid.

A keyspace qualification provided in a group create or alter statement was invalid.

Revise the statement to provide a valid keyspace qualification.

The scope provided to qualify ˝scope_admin˝ role in a grant or revoke statement was not valid.

Revise the statement to provide a valid scope qualification.

The bucket provided to qualify a role in a grant or revoke statement was not valid.

Revise the statement to provide a valid bucket qualification.

An invalid role was provided in a grant or revoke role statement.

An invalid role was provided in a group create or alter statement.

Revise the statement to provide a valid role.

An attempt was made to revoke a role from a user or group that was not held by the user or group.

The user has had all roles revoked.

The group has had all roles revoked.

Contact support.

Contact support.

During a merge statement a key was detected multiple times in update and/or delete operations.

Contact support.

The INSERT action of the MERGE statement had previously inserted the noted key. e.g. MERGE INTO default USING [{},{} AS source ON default.id IS VALUED WHEN NOT MATCHED THEN INSERT ('key',{}) ;]

Revise the statement logic to ensure only unique keys are produced.

An expression in the window aggregate did not evaluate to a number.

The window order clause evaluation failed.

The window partitioning clause evaluation failed.

Contact support.

Contact support.

The results from an advisor session are not valid.

Repeat the session.

Contact support.

Contact support.

Contact support.

The index definition includes missing values for the leading key and this feature is not supported by the indexer.

Revise the index definition to not include missing leading key values.

Contact support.

The cost of an index scan could not be calculated as the index was not in memory.

Statistics for the index could not be updated as it was not in memory.

Re-submit the request.

Contact support.

The system bucket N1QL_CBO_STATS does not exist and could not be created.

Manually create the bucket and re-submit the request.

Contact support.

An index name in the index build statement was not a string value compliant with index naming requirements.

An index name in the update statistics statement was not a string value compliant with index naming requirements.

Revise the statement to provide a valid index name.

The index specified in an index build statement does not exist.

The index specified in an update statistics statement does not exist.

Revise the statement to provide a valid index name.

Contact support

A nested loop join using a primary scan produced more than 1000 documents. This limit is imposed for resource usage and performance considerations as the inner leg of such a join may be executed repeatedly.

Limit the number of documents accessed in this manner or create an appropriate secondary index to support the join.

An invalid parameter (query vector) is specified for vector function: <<msg>>.

Revise the vector function to use a proper parameter (query vector).

An invalid parameter (probes) is specified for vector function: <<msg>>.

Revise the vector function to use a proper parameter (probes).

An invalid parameter (rerank) is specified for vector function: <<msg>>.

Revise the vector function to use a proper parameter (rerank).

Limit and/or Offset specified as query parameters have values that exceeded maximum allowed values for vector index.

Specify Limit/Offset as constants and re-submit the query.

Use values that do not exceed the maximum allowed value and re-submit the query.

An invalid parameter (TopNScan) is specified for vector function: <<msg>>.

Revise the vector function to use a proper parameter (TopNScan).

The tracked memory required for the request exceeded the quota set for it.

Review the statement execution plan for efficiency.

Review the volume of data the statement is expected to process and the operations used.

Increase the memory quota if appropriate.

Contact support.

The indicated action was attempted a number of times without success.

If the associated error indicates an infrastructure issue, verify all cluster resources are accessible, available and online.

Contact support.

A key in a USE KEYS clause was not found.

If necessary, revise the keys listed.

A node level memory quota was in effect and while trying to execute the request the limit was reached

Verify the memory requirements of the request, possibly setting a request memory quota.

Retry the request with less concurrent activity.

An error occurred reconstructing a value data spilled temporarily to disk during the request processing.

Contact support.

An error occurred reconstructing a value data spilled temporarily to disk during the request processing.

Contact support.

The request processing requires date be temporarily spilled to disk and the temporary file creation failed.

Review the Query service temporary data directory and validate the filesystem is in good order with sufficient space to support the node's temporary data requirements.

Review the request memory quota, if in effect, and increase it if appropriate to avoid spilling.

Contact support.

An error occurred reading data spilled temporarily to disk during the request processing.

Contact support.

An error occurred writing data temporarily to disk during the request processing.

Contact support.

An error occurred accessing the file used for data temporarily spilled to disk during the request processing.

Contact support.

The operation is attempting to use more files for temporarily spilling data to disk than is permitted.

Increase your request memory quota.

Contact support.

The feature is not implemented in this edition.

Authorisation for the user failed with the indicated error.

Ensure the request is using the correct credentials and the user holds the permissions necessary for the request.

An attempt was made to drop the named function but it did not exist.

Ensure the function exists before attempting to drop it.

An attempt was made to create a function with a name that was already defined.

Use the OR REPLACE clause if the intention is to redefine the function.

Change the function name to be unique.

Contact support.

Revise the statement to include the correct number of arguments to the function.

The namespace in the function name was invalid.

The scope in the function name did not exist.

The function name had an incorrect number of components.

Revise the statement providing a valid function name.

Contact support.

Contact support.

The cluster's feature control flags disable the type of functions.

Problems with initialising the environment to run functions of the type prevent them being enabled.

Restrictions in the cluster deployment model disable the type of functions.

The error noted occurred whilst executing the function.

Review the error for possible user actions and revise the statement and/or function as appropriate.

Contact support.

Function execution reached the maximum permitted number of nested calls and was halted.

Review your function code to ensure you don't have excess recursion.

Review your functions, flattening where possible so as to not exceed the limit.

The path specified in a Javascript function creation statement was invalid.

Revise the statement providing a path valid for Javascript libraries.

An error occurred loading the body of a Javascript function.

Review the error referenced for appropriate actions.

Contact support.

Contact support.

A bucket path was expected but the provided information did not resolve to a two part path.

A scope path was expected but the provided information did not resolve to a three part path.

A collection path was expected but the provided information did not resolve to a four part path.

A keyspace path was expected but the provided information did not resolve to a two or four part path.

Review the request's ˝query_context˝ setting.

Revise the statement to provide a correct path.

The request's ˝query_context˝ contains the noted error.

The request's ˝query_context˝ contains too many parts.

Correct the ˝query_context˝ value and try the request again.

Contact support.

Contact support.

The process responsible for synchronising changes to the bucket in the node encountered more failures than the maximum tolerated.

The bucket was dropped outside of the node and the synchronisation endpoint was no longer available.

If the bucket was dropped this error is expected.

Contact support.

The process responsible for synchronising changes to the bucket was unable to find a healthy node on which to find the bucket.

Contact support.

The process responsible for synchronising changes to the bucket encountered an error reading the information stream from the orchestrator.

Contact support.

The process responsible for synchronising changes to the bucket failed to connect to the orchestrator.

Contact support.

The process responsible for synchronising changes to the bucket failed to connect to the orchestrator.

Contact support.

Contact support.

The process responsible for synchronising changes to the bucket in the node was unable to find the orchestrator endpoint for the bucket.

The bucket was dropped outside of the node and the synchronisation endpoint was no longer available.

If the bucket was dropped this error is expected.

Contact support.

An advisor function call was made with the action as ˝stop˝ and an unknown session specified.

Verify the correct session is specified when stopping an index advisor session.

An advisor function call was made with an invalid value for the ˝action˝ field.

Refer to the documentation for valid values to pass to the advisor function.

An advisor function call was made with an object argument that was missing the ˝action˝ field.

Refer to the documentation for valid arguments to pass to the advisor function.

An advisor function call was made with invalid arguments.

Refer to the documentation for valid arguments to pass to the advisor function.

An invalid metric specification (<<metric>>) is used in vector function <<name>>.

Revise the vector function to use a supported metric specification.

An invalid field specification (<<field>>) is used in vector function <<name>>.

Revise the vector function to use a valid field specification.

An invalid dimension specification (<<dimension>>) is used in IsVector() function.

Revise the function parameter to use an integer for dimension specification.

An invalid argument (<<msg>>) is used in IsVector() function.

Revise the function parameter to use a supported argument.

Contact support.

A reference was made to a keyspace that doesn't exist in the system namespace.

Refer to the documentation for valid keyspaces in the system namespace.

Contact support.

Contact support.

Contact support.

An attempt was made to delete an unknown request from completed requests.

Contact support.

An operation on a remote node failed as detailed.

Contact support.

Contact support.

Contact support.

The request attempted to access the contents of a restricted access system keyspace and the user was not permitted to see all data.

Ensure the request is run as a user with the correct privileges.

Contact support.

Contact support.

Contact support.

On start-up the Query service was unable to connect to the authorisation service.

Contact support.

Contact support.

A keyspace referenced in the statement did not exist.

Check all expected keyspaces have been created and are correctly referenced in the statement.

Contact support.

Contact support.

An error occurred retrieving documents from the data service.

Review the error detailed for possible user actions.

Contact support.

An attempt was made to update a document but it was concurrently updated by another request.

Review concurrent document update logic and retry the operation as appropriate.

A request to the data service to delete a key failed.

Contact support.

An attempt was made to access a bucket of an an unsupported type through the Query service.

Migrate all buckets to currently supported types.

The maximum time for a primary index scan was reached before producing any keys.

Review the state and performance of the indexing nodes in the cluster.

Contact support.

An attempt was made to alter or drop an index that didn't exist.

Check the index exists before attempting to alter or drop it.

Check for a concurrent deletion of the index.

An attempt to retrieve a document using the random document interface failed.

Contact support.

The authorisation service was not initialised but is required by the datastore.

Contact support.

Contact support.

An attempt was made to alter or drop a bucket that did not exist.

Review the statement and ensure buckets exist beforehand.

Contact support.

An error was encountered acquiring the bucket statistics from the data service.

Contact support.

Contact support.

Creation of the N1QL_SYSTEM_BUCKET used for storing statistics for query planning failed.

Review the error detailed for possible user actions.

Contact support.

An attempt was made to create a scope with a name that already existed.

Review the statement and ensure scope names are unique within the bucket.

An attempt was made to create a scope with a name that did not exist.

Review the statement and ensure scopes exist beforehand.

Invalid options were passed in a CREATE COLLECTION statement.

An invalid value was passed for the ˝maxTTL˝ option in a CREATE COLLECTION statement.

Revise the statement to provide a valid options.

An attempt was made to drop a collection that did not exist.

Review the statement and ensure collections exist beforehand.