--- title: SQL++ Error Codes description: The following table lists all of the SQL++ error codes, their error message, and some tips to resolve them. pubDate: 2026-08-17T09:53:44.266Z antora: editUrl: https://github.com/couchbaselabs/docs-devex/edit/capella/modules/n1ql/pages/n1ql-language-reference/n1ql-error-codes.adoc xref: xref:cloud:n1ql:n1ql-language-reference/n1ql-error-codes.adoc[] --- [Consult the llms.txt file for a full list of contents](/llms.txt) [View original HTML](/cloud/n1ql/n1ql-language-reference/n1ql-error-codes.html) # SQL++ Error Codes > The following table lists all of the SQL++ error codes, their error message, and some tips to resolve them. ## [](#1xx-codes-shell)1xx Codes (shell) These errors are related to the shell. | ICode | Error Message | Description | | ----- | ---------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 100 | A connection was refused. | **Reason** A connection the cbq-shell was trying to make was refused by the remote partner. **User Action** Verify the connection URL and try again. | | 101 | Unsupported protocol scheme «scheme» | **Reason** The protocol scheme in the cbq-shell connection URL is not supported. **User Action** Correct the URL ensuring only a supported scheme is used. Schemes: http, https, couchbase, couchbases | | 102 | No such host «host» | **Reason** The noted host could not be found by the cbq-shell. **User Action** Correct the host in the connection URL and try again. | | 103 | No host in request URL | **Reason** The cbq-shell connection URL does not contain a host name or IP address. **User Action** Correct the the connection URL and try again. | | 104 | Unknown port «port» | | | 105 | No route to host | | | 106 | Network is unreachable. | | | 107 | Not connected to any cluster. Use \\CONNECT command. | **Reason** A connection in the cbq-shell has not been attempted or has failed. **User Action** Issue the connect command to connect to a server. | | 108 | Failed to open a connection to the server endpoint. | **User Action** Review the details of the error reported. Contact support. | | 109 | Invalid input URL «url» | **Reason** 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. **User Action** Correct the URL and retry. | | 116 | Error during file read «details» | **Reason** The cbq-shell input commands file could not be read. The cbq-shell command history file could not be read. **User Action** Review the details reported and take corrective action. | | 117 | Error during file write «details» | **Reason** The cbq-shell command history file could not be written to. **User Action** Review the details reported and take corrective action. | | 118 | Unable to open file «file» | **Reason** 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. **User Action** Review the details reported and take corrective action. | | 119 | Unable to close file «file» | | | 121 | Invalid password | **Reason** 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. **User Action** Enter only a valid password at the prompt. review the details reported and take corrective action. | | 122 | Invalid username. | **Reason** The cbq-shell command line flags include the password but not the user name. **User Action** Pass both user and password on the cbq-shell command line. | | 123 | Username missing in -credentials/-c option. | **Reason** The username could not be found in the credentials cbq-shell option value. **User Action** Correct the value and retry. | | 124 | Invalid format for credentials. Separate username and password with a colon (':'). | **Reason** The credentials cbq-shell option value was not in the correct format. **User Action** Correct the value and retry. | | 136 | Command does not exist. | **Reason** The command entered at the cbq-shell prompt was invalid. The cbq-shell help command could not find the command specified. **User Action** Correct the command and retry. | | 137 | Parameter does not exist | **Reason** An attempt was made access a parameter that doesn't exist via cbq-shell commands. **User Action** Verify the parameter is correctly named and the sequence of commands means it is defined when expected. | | 138 | Too many input arguments to command. | **Reason** A cbq-shell command was attempted but too many arguments were supplied. **User Action** Consult the command help facility, correct the command and retry. | | 139 | Too few input arguments to command. | **Reason** A cbq-shell command was attempted with insufficient arguments. **User Action** Consult the command help facility, correct the command and retry. | | 140 | Stack empty. | **Reason** The cbq-shell value stack was empty and an attempt to pop or set a value was attempted. **User Action** Contact support. | | 141 | Alias does not exist «alias» | **Reason** An attempt was made to list cbq-shell command aliases and no aliases exist. | | 142 | Error when running in batch mode for Analytics. Incorrect input value | **Reason** The cbq-shell batch command line option was set to an invalid value. **User Action** Correct the command line option and retry. | | 143 | Cannot write to string buffer. | **Reason** Operating in batch mode, cbq-shell failed to write the command to the batch file. **User Action** Review the details reported and take corrective action. | | 170 | Operation timed out. Check query service url | | | 171 | Retired. | | | 172 | An error occurred writing data in JSON format. | **User Action** Contact support. | | 173 | An error occurred reading data in JSON format. | **User Action** Contact support. | | 174 | An error occurred in the Query driver. | **User Action** Review the reported error. Contact support. | | 175 | Error with io Writer. | **Reason** The cbq-shell was trying to write output and encountered an error. **User Action** Review the details reported and take corrective action. | | 176 | Unbalanced quotes in the input. | **Reason** The cbq-shell echo contained an unequal number of double quotation marks. **User Action** Correct the command and retry. | | 177 | Retired. | | | 178 | Place input argument URL at the end, after input flags. | **Reason** The cbq-shell connection URL was not passed as the engine argument and was not the last argument. **User Action** Pass the connection URL using the engine argument flag or as the final argument on the command line. | | 179 | Input Argument format is invalid. | **Reason** The argument to a cbq-shell command was not a supported format. The value specified for a cbq-shell predefined value was not valid. **User Action** Correct the argument or value type. | | 180 | Query APIs cannot be initialized from Cluster Map. | **Reason** The cbq-shell failed to obtain the cluster map from the server. **User Action** Review the connection URL is correct and still valid. | | 181 | Invalid argument. | **Reason** An invalid argument was supplied to the cbq-shell redirect command. **User Action** Consult the command help facility, correct the command and retry. | | 182 | Terminal set-up failed (check not legacy console) | **Reason** cbq-shell failed to initialise the terminal for vi emulation mode. **User Action** (Windows) Ensure cbq-shell is not being run in a legacy console window. Don't use cbq-shell's vi emulation mode. | | 183 | Invalid protocol. Mixed protocols are not permitted in engine list. | **Reason** Multiple endpoints were listed in the cbq-shell connection URL with differing protocols. **User Action** Ensure all endpoints listed are using the same protocol. | | 199 | A non-specific error occurred in the cbq-shell. | **User Action** Contact support. | ## [](#1xxx-codes-services)1xxx Codes (services) These errors are related to the services. | ICode | Error Message | Description | | ----- | ------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 1000 | The server or request is read-only and cannot accept this write statement. | **Reason** 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. **User Action** 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. | | 1010 | Unsupported http method:«METHOD» | **Reason** The service endpoint supports only GET & POST HTTP methods. All other HTTP methods are not supported. **User Action** Use a supported method to submit requests. | | 1020 | «feature» «value» not implemented | **Reason** The noted feature and value combination is reserved but is not implemented. **User Action** Use only supported feature and value combinations. | | 1030 | Unknown «parameter» value: «value» | **Reason** The value supplied for the noted parameter is unknown. **User Action** Ensure the value supplied is a supported value in the required format for the request parameter noted. | | 1040 | Error processing «message» | **Reason** 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. **User Action** Where the error is derived from user controlled data, correct the data. See [Note](#note-1040). | | 1050 | No «parameter» value | **Reason** A value was not supplied for the required parameter. **User Action** 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. | | 1060 | Multiple values for «parameters» | **Reason** Multiple values have been supplied for a parameter or two mutually exclusive parameters are both enabled. **User Action** Ensure all request parameters including named statement parameters, are unique and supplied only once. Ensure mutually exclusive parameters are not simultaneously enabled. | | 1065 | Unrecognized parameter in request: «parameter» | **Reason** An unknown request parameter was received. **User Action** Pass only valid request parameters. Check parameter names for typographical errors. | | 1070 | «feature» has to be of type «expected» | **Reason** The value supplied for «feature» was not of the expected type. **User Action** Correct the value and re-submit the request. | | 1080 | Timeout «duration» exceeded | **Reason** The specified request time-out was reached. **User Action** Check the statement is correctly constructed and using the expected plan. Revise the time-out upward to accommodate the statement. | | 1090 | «parameter» = «value» is invalid. «message» | **Reason** The named parameter's value was invalid for the reason noted in the message. **User Action** Set the parameter to a valid value for the request. | | 1100 | Invalid JSON in results | **Reason** An error occurred whilst writing results to the output stream. **User Action** Please contact support. | | 1110 | forbidden character (\\\\ or \\") in client\_context\_id | **Reason** The request parameter client\_context\_id contains one or more of the noted invalid characters. **User Action** Revise the value for client\_context\_id. | | 1120 | Unsupported media type: «mediaType» | **Reason** The HTTP request header field ˝Accept˝ was not set to a supported value. **User Action** Change the header field to ˝\*/\*˝, ˝application/json˝ or ˝application/xml˝. | | 1130 | Request «id» is not a http request | **Reason** The request identified by «id» does not exist. | | 1140 | Array «scan\_entry» should be of length 2 | **Reason** An invalid scan vector array element was found. **User Action** Correct the scan vector. | | 1150 | Bad sequence number «seqno». Expected an unsigned 64-bit integer. | **Reason** An entry in the scan vector contained a sequence number that was not an unsigned 64-bit integer. | | 1155 | Bad UUID «vbucket\_uuid». Expected a string. | **Reason** An entry in the scan vector contained a v-bucket UUID that was not a string value. | | 1160 | Failed to decode nil value. | **Reason** A request requiring a body did not include one. **User Action** Resubmit a valid request. | | 1170 | Unsupported method «method» | **Reason** The HTTP request method noted is not supported by the endpoint. | | 1180 | Indicates the service on the node is in the process of shutting down. | **Reason** A topology change was in the process of removing the node. | | 1181 | Indicates the service on the node has been shut down and is waiting to be terminated. | **Reason** A topology change was in the process of removing the node. | | 1182 | Service cannot handle requests | **Reason** A ping request has determined the service was not healthy. **User Action** Examine the diagnostic logs to ascertain the reason for this state. Contact support. | | 1191 | User has more requests running than allowed | **Reason** Currently unused. | | 1192 | User has exceeded request rate limit | **Reason** Currently unused. | | 1193 | User has exceeded input network traffic limit | **Reason** Currently unused. | | 1194 | User has exceeded results size limit | **Reason** Currently unused. | | 1195 | Request execution aborted as the number of errors raised has reached the maximum permitted. | **Reason** The number of errors raised has reached the limit. **User Action** Consult the errors to ensure the statement is operating as expected. Revise the ˝error\_limit˝ request parameter as necessary. | | 1196 | Request has been declined with «reason» | **Reason** The request breached a limit for the tenant. | | 1197 | Request does not have a valid tenant | | | 1198 | Request is not authorized for tenant «tenant» | | | 1199 | Request rejected due to limiting or throttling. «retry» | **User Action** Retry the request in accordance with «retry». | | 1200 | Tenant not found «tenant» | | | 1201 | Request queue full | **Reason** The request queue has reached its limit **User Action** Verify the server is processing requests. | | 1202 | Client disconnected | **Reason** The server aborts servicing a request when it detects the client has closed its connection. | | 1203 | Slow/stalled client write timed out | **Reason** 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. **User Action** Check the application is reading response stream fast enough to avoid blocking writes. | | 1204 | request halted: free memory below «threshold»% of available memory | **Reason** The request was halted by admission control due to low available memory. | > [!NOTE] > Error 1040 > > The Query Service REST API returns this error if you specify request parameters as form data and include an unescaped semicolon (;) in a statement. ## [](#2xxx-codes-admin)2xxx Codes (admin) These errors are related to the admin. | ICode | Error Message | Description | | ----- | -------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 2000 | Error connecting to «what» | **Reason** The server encountered an error when establishing a connection to «what». **User Action** Contact support. | | 2001 | Error accounting manager: «reason». | **Reason** «reason» prevented correct start-up of the service statistics monitor. **User Action** Contact support | | 2010 | Invalid «component» URL: «URL» | **Reason** An invalid URL was encountered for the noted component. **User Action** Contact support. | | 2020 | Error in JSON decoding | **User Action** Contact support. | | 2030 | Error in JSON encoding | **User Action** Contact support. | | 2031 | Unknown setting: «setting» | **Reason** An unknown setting was supplied in a request to the settings rest endpoint. **User Action** Provide only valid settings in the request. | | 2032 | Incorrect value «value» for setting: «name» | **Reason** The value provided for the noted setting was not of the correct type. **User Action** Correct the value and re-submit the request. | | 2040 | Error retrieving cluster «message» | **User Action** Contact support. | | 2050 | Error adding cluster «message» | **User Action** Contact support. | | 2060 | Error removing cluster «message» | **User Action** Contact support. | | 2070 | Error retrieving node «message» | **User Action** Contact support. | | 2080 | No such node «message» | **User Action** Contact support | | 2090 | Error adding node «message» | **User Action** Contact support | | 2100 | Error removing node «message» | **User Action** Contact support | | 2110 | Error creating metric «message» | | | 2120 | Error authorizing against cluster «message» | **Reason** Request received without suitable credentials. Failure to authenticate with given credentials. Authenticated user lacks required privileges. **User Action** Review the embedded «message» information for more detail on why the operation failed. | | 2130 | The admin endpoint encountered an error. | **User Action** Contact support | | 2140 | server is not ssl enabled | **Reason** An attempt has been made to update the SSL certificate but the server does not have SSL enabled. **User Action** Review the server configuration. | | 2150 | Not a proper creds JSON array of user/pass structures: «creds» | | | 2160 | Completed requests qualifier already set: «qualifier» | **User Action** Define a different qualifier or update the existing one. Refer to the ˝logging qualifiers section of the documentation. | | 2170 | Completed requests qualifier unknown: «qualifier» | **Reason** An attempt was made to add a qualifier that is not a known. **User Action** Check the qualifier specified is valid. Refer to the ˝logging qualifiers section of the documentation. | | 2180 | Completed requests qualifier not set: «qualifier» | **Reason** An attempt was made to access a qualifier that was not set. **User Action** Ensure the intended qualifier has been set. | | 2190 | Non-unique completed requests qualifier «qualifier» cannot be updated | **Reason** A attempt was made to update a qualifier that isn't unique. **User Action** Only attempt to update unique qualifiers. Non-unique qualifiers may only be added/removed. | | 2200 | Completed requests qualifier «qualifier» cannot accept argument «value» | **Reason** The data type of the «value» was incompatible with the qualifier. **User Action** Correct the value for the qualifier and re-submit the request. | | 2201 | Completed requests maximum plan size («size») is invalid. | | | 2210 | Invalid service port: «port» | **User Action** Contact support. | | 2220 | Error getting request body | **Reason** A prepareds endpoint PUT request was received but the body was empty or could not be read. **User Action** contact support | | 2230 | FFDC invocation failed. | **Reason** An error occurred with a manual First Failure Data Capture (FFDC) invocation. **User Action** Wait until the specified reported minimum time before attempting a further invocation. | | 2240 | Error accessing log | **Reason** A request was made to the diagnostic log endpoint and there was a error accessing the file. **User Action** Ensure the diagnostic log file being accessed exists for the duration of the request. | | 2500 | Failed to start workload reporting | **Reason** An error occurred when starting request capture for workload reporting. **User Action** Review the error and correct any configuration issues. | | 2501 | Invalid value «value» for workload setting «setting» | **Reason** The value provided for the setting is invalid. **User Action** Consult the documentation for the valid values for the workload settings. Review the configuration and correct the value. | | 2502 | Error processing workload configuration | **Reason** The value provided for AWR configuration is invalid. **User Action** Review the configuration and correct the value. The value must be a valid object or a string encoding a valid JSON object. | | 2503 | Error distributing workload settings | **Reason** An error occurred distributing the workload settings to other Query nodes. **User Action** Contact support. | | 2504 | Warning during AWR operation. | **Reason** An AWR operation encountered a condition that needs attention. **User Action** Check the error message for recommended actions. Or consult the documentation for guidance. | | 2505 | Workload reporting is not supported in Community Edition. It is an enterprise level feature. | **Reason** An Workload reporting related operation was attempted on a Community Edition Couchbase cluster. **User Action** Consult the documentation for the feature you are trying to use. | ## [](#3xxx-codes-parse)3xxx Codes (parse) These errors are related to the parsing. | ICode | Error Message | Description | | ----- | ------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 3000 | Indicates a syntax error occurred during statement parsing. | **User Action** 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. See [Note](#note-3000). | | 3005 | Details the location in the statement text of errors encountered during parsing. | | | 3006 | invalid escape sequence | **Reason** 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. **User Action** Valid escape sequences are: \\b, \\f, \\n, \\r, \\t, \\/, \\\\, \\", \\\`, \\u#### (where #### is a Unicode symbol number in hexadecimal). | | 3007 | invalid string | **Reason** An opening quotation mark defining a string was encountered without any further characters. **User Action** Correctly delimit all string values in statements. | | 3008 | missing closing quote | **User Action** Contact support. | | 3009 | unescaped embedded quote | **User Action** Contact support. | | 3080 | Ambiguous reference to field «field» | **Reason** 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 ... **User Action** Fully qualify references when the potential for ambiguity exists. e.g. SELECT b.a FROM b,c WHERE ... | | 3081 | Duplicate variable: «identifier» already in the scope «context» | **Reason** There was a non-unique binding name in a LET or WITH clause. **User Action** Use unique names for all bindings in a statement. | | 3082 | Formalizer internal error: «details» | **Reason** A statement included a correlated reference that was not permitted. **User Action** If encountered with a existing prepared statement, re-prepare the statement. Contact support. | | 3083 | Invalid input. | **Reason** Invalid input was submitted, either a statement or expression, depending on context. **User Action** Submit only valid SQL++ statements or expressions. | | 3100 | A semantic error is present in the statement. | **Reason** The statement includes portions that violate semantic constraints. **User Action** The cause will contain more detail on the violation; revise the statement and re-submit. | | 3101 | Semantic error: «what» | **Reason** An internal error occurred during semantics check for the query. **User Action** Contact support. | | 3110 | «op» on «alias» cannot have join hint (USE HASH or USE NL) | **Reason** Join type hints are only supported for ANSI join and nest operations. **User Action** Review the statement and revise the operation or omit the hints. | | 3120 | «operation» on «alias» cannot have USE KEYS. | **Reason** USE KEYS is not supported in this context. | | 3130 | «operation» on «alias» cannot have USE INDEX. | **Reason** USE INDEX is not supported in this context. | | 3150 | MERGE with ON KEY clause cannot have document key specification in INSERT action. | **Reason** 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',{})\] **User Action** Refer to the documentation for lookup merge statements. | | 3160 | MERGE with ON clause must have document key specification in INSERT action | **Reason** 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 ({})\] **User Action** Refer to the documentation for ANSI merge statements. | | 3170 | MERGE is missing source. | | | 3180 | MERGE with ON KEY clause cannot have USE INDEX hint specified on target. | **Reason** 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 ({})\] **User Action** Refer to the documentation for lookup merge statements. | | 3190 | MERGE with ON KEY clause cannot have join hint specified on source. | **Reason** The USE INDEX hint is not supported with lookup merge statement source. **User Action** Refer to the documentation for lookup merge statements. | | 3200 | Cannot mix «op1» on «alias1» with «op2» on «alias2». | **Reason** 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. **User Action** Revise the statement to use only one type of operation. | | 3220 | «name» window function «clause» «reason» | **Reason** A violation of the window function semantic restrictions was present in the statement. **User Action** Revise the statement to remove the violation. | | 3230 | «feature» is an enterprise level feature. | **Reason** An attempt was made to use the noted feature that is only available in the Enterprise Edition of the product. **User Action** Consult the documentation for the feature you're trying to use. | | 3250 | Advise supports SELECT, MERGE, UPDATE and DELETE statements only. | **Reason** An attempt was made to run advise on an unsupported statement. **User Action** Refer to the documentation for ADVISE. | | 3255 | Advisor function is only allowed in projection clause | **Reason** An attempt was made to use the ADVISOR() function out side of a select statement's projection. **User Action** Refer to the documentation for ADVISE. | | 3256 | FROM clause is not allowed when Advisor function is present in projection clause. | **Reason** An attempt was made to use the advisor function on the results from a keyspace fetch. **User Action** Refer to the documentation for ADVISE. | | 3260 | «what» is only supported in Developer Preview Mode. | | | 3261 | «type» term must have USE KEYS | **Reason** A keyspace in the statement was not an explicit path and there was no USE KEYS clause. **User Action** Revise the statement to include an explicit path or a USE KEYS clause as appropriate. | | 3262 | «type» term should not have USE INDEX | **Reason** A keyspace in the statement was not an explicit path and there was a USE INDEX clause. **User Action** Revise the statement to include an explicit path or remove the USE INDEX clause as appropriate. | | 3270 | UPDATE STATISTICS (ANALYZE) supports GSI indexes only for INDEX option. | **Reason** An attempt was made to run UPDATE STATISTICS for a non-GSI index. **User Action** Do not run UPDATE STATISTICS on a non-GSI index. | | 3271 | INDEX ALL option for UPDATE STATISTICS (ANALYZE) can only be used for a collection. | **Reason** A statistics update was attempted using the INDEX ALL clause on a bucket. **User Action** Do not run UPDATE STATISTICS with INDEX ALL on buckets. | | 3272 | UPDATE STATISTICS of 'self' is not allowed | **Reason** A statistics update was attempted on an index expression including ˝self˝. **User Action** Revise the index expression to not include ˝self˝. Refer to the documentation for UPDATE STATISTICS. | | 3280 | «index key expression» is not indexable | **Reason** An expression in the index definition was not indexable (e.g. a constant). **User Action** Revise the definition to include only indexable expressions. | | 3281 | «message» «location» MISSING attribute not allowed (Only allowed with gsi leading key). | **Reason** 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. | | 3282 | Attributes are not allowed on «details» «location» of flatten\_keys. | **Reason** Attributes specified for FLATTEN\_KEYS. **User Action** Revise the statement to remove the attributes on the FLATTEN\_KEYS() expression. NOTE: Arguments passed to FLATTEN\_KEYS() may have attributes. | | 3283 | «flatten keys expression» «location» is not allowed in this context | **Reason** FLATTEN\_KEYS specified outside of CREATE INDEX or UPDATE STATISTICS or was surrounded by a function. **User Action** Refer to the documentation for flatten keys. | | 3284 | ALL/DISTINCT is not allowed in «expression» «location» | **Reason** ALL and/or DISTINCT used in an invalid location. **User Action** Revise the statement. | | 3285 | Index of «expression» «location» is not allowed as a index key | **Reason** An attempt to use SELF as an index key was made. **User Action** Remove SELF from the the index definition. | | 3286 | PRIMARY INDEX is not allowed using FTS | **Reason** FTS was specified as the index provider for a primary index. | | 3290 | Join hint (USE HASH or USE NL) cannot be specified on the first from term «term» | **Reason** A join hint was specified on the first term of a join. **User Action** Revise the statement to remove the hint on the first join term. | | 3291 | «what» «expression» is not a valid constant, named, positional or function parameter. | **Reason** The ORDER BY direction or NULLS position was not a valid constant, named, positional or function parameter. **User Action** Revise the ORDER BY direction or NULLS position to be a valid constant, named, positional or function parameter. | | 3300 | recursive\_with semantics: «cause» | **Reason** The statement specifies restricted syntax in a recursive common table expression definition. **User Action** Revise the statement removing the restricted syntax. | | 3301 | Anchor Clause cannot have recursive reference in FROM Expression : «alias» | **Reason** 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 **User Action** Correct the recursive common table expression definition. | | 3302 | Recursive reference «alias» must not appear more than once in the FROM clause | **Reason** 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 **User Action** Revise the statement removing the duplicate reference. | | 3303 | Invalid config option «option» | **Reason** 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 **User Action** Refer to the documentation for permitted options. | | 3304 | recursive\_with\_unsupported: «reason» | **Reason** 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. **User Action** Revise the statement to remove the unsupported reference. | | 3305 | Recursive WITH «alias» limited to «limit» documents as no explicit document count limit or memory quota set | **Reason** 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. **User Action** 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. | | 3306 | Recursive WITH «alias» stopped at «depth» level as no explicit level limit or memory quota set | **Reason** 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. **User Action** 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. | | 3307 | Cycle fields validation failed for with term: «alias» | **Reason** The expression specified in the cycle clause is not an identifier or path term. **User Action** Revise statement removing or modifying the invalid cycle clause expression. | | 3400 | Semantic error in query with vector search function: <>. | **Reason** A vector search function cannot be used together with certain features of a query, e.g. GROUP BY clause or Window function. **User Action** Revise the statement to remove the offending features of the query. | | 3401 | Invalid index attributes specified for index key <> in CREATE INDEX statement. | **Reason** Cannot mix index attribute VECTOR with <> for index key <> in CREATE INDEX statement. **User Action** Revise the statement to remove the offending index attribute. | | 3402 | Multiple VECTOR index key specified in CREATE INDEX statement for index <>. | **Reason** Only a single index key with VECTOR attribute is supported in CREATE INDEX statement. **User Action** Revise the statement to include only a single index key with VECTOR attribute. | | 3403 | Multiple index keys specified in CREATE VECTOR INDEX statement for index <>. | **Reason** Only a single index key (with VECTOR attribute) is supported in CREATE VECTOR INDEX statement. **User Action** Revise the statement to include only a single index key (with VECTOR attribute). | | 3404 | No index key with VECTOR attribute specified in CREATE VECTOR INDEX statement for index <>. | **Reason** An index key with VECTOR attribute must be included in CREATE VECTOR INDEX statement. **User Action** Revise the statement to include an index key with VECTOR attribute. | | 3405 | Vector function (<>) in ORDER BY clause must use a constant for <