Error Messages¶
Error Message Severities¶
The error message severities are:
TRACE
INFO
DEBUG
WARNING
ERROR
FATAL
Comparative to severities in PostgreSQL,
TRACE, INFO and WARNING are equivalent to PSQL INFO.
DEBUG is equivalent to PSQL DEBUG.
ERROR is equivalent to PSQL ERROR.
FATAL is equivalent to PSQL FATAL.
TRACE and DEBUG are used to get helpful output for debugging. INFO provides potentially helpful, but non-critical information about internal operation. WARNING is similar to INFO, but highlights potentially dangerous or undesirable, though non-critical, behavior. ERROR messages report disruptive but recoverable states. Note that ERRORs encountered while parsing or executing a query will cause it to fail. FATAL messages indicate disruptive, unrecoverable states and cause the program to immediately exit, closing any open network connection.
Octo or ROcto Errors¶
Octo or ROcto Errors are of the form
ERR_<error>
orINFO_<error>
orWARN_<error>
. These errors can occur in eitherocto
orrocto
. The errors are detailed below, in alphabetical order. Occurrences of "xxx" indicate portions of the error message text that vary depending on the details of the particular error.
Error messages also include line numbers to indicate where in the query input the error occurred. Two line numbers are included: 1. The line number where the query is located within the full input string, relative to the start of the input or beginning of the input file 2. The line number where the syntax error occurred within the query itself, relative to the start of the query
For example, given an empty database, if a file with the following contents is passed to octo
:
UPDATE myTable
SET id = 3, name = "Orion"
WHERE breed = "Black Lab";
UPDATE myTable
SET name = (SELECT name FROM tableOfDogs WHERE breed = "Black lab");
Then the following error messages will be issued:
[ERROR]: ERR_UNKNOWN_TABLE: Unknown table: MYTABLE
LINE 1:1: UPDATE myTable
^^^^^^^
[ERROR]: ERR_UNKNOWN_TABLE: Unknown table: TABLEOFDOGS
LINE 5:2: ... name = (SELECT name FROM tableOfDogs WHERE breed = "Black lab"...
^^^^^^^^^^^
Note that the first query specifies line numbers 1:1
, indicating that the syntax error is on the first line of the file and the first line of the query itself.
In contrast, the second query specifies line numbers 4:2
, indicating that the syntax error occurred on the fourth line of the file and the second line of the query itself.
ERR_AGGREGATE_FUNCTION_CHECK¶
Text: Aggregate functions are not allowed in CHECK constraints
Description/Action: This error is generated when aggregate functions are used in a CHECK constraint, which is not allowed. PSQL Error Code: 42803
ERR_AGGREGATE_FUNCTION_JOIN¶
Text: Aggregate functions are not allowed in JOIN conditions
Description/Action: This error is generated when aggregate functions are used in JOIN conditions, which is not allowed. PSQL Error Code: 42803
ERR_AGGREGATE_FUNCTION_NESTED¶
Text: Aggregate function calls cannot be nested
Description/Action: This error is generated when aggregate function calls are nested, which is not allowed. PSQL Error Code: 42803
ERR_AGGREGATE_FUNCTION_UPDATE¶
Text: Aggregate functions are not allowed in UPDATE
Description/Action: This error is generated when aggregate functions are used in the SET clause of an UPDATE command, which is not allowed. PSQL Error Code: 42803
ERR_AGGREGATE_FUNCTION_WHERE¶
Text: Aggregate functions are not allowed in WHERE
Description/Action: This error is generated when aggregate functions are used in WHERE, which is not allowed. PSQL Error Code: 42803
ERR_AMBIGUOUS_COLUMN_NAME¶
Text: Ambiguous column name "xxx": qualify name for safe execution
Description/Action: This error is generated when two or more columns from different tables of the same name are given in a single query without qualifying them with their respective table names. PSQL Error Code: 42702
ERR_AS_MORE_COLUMNS¶
Text: Table name "xxx" has xxx columns available but xxx columns specified
Description/Action: This error is generated when the
AS
keyword specifies a list of column names that is more than the available number of columns. PSQL Error Code: 42P10
ERR_AUTO_UPGRADE¶
Text: Cannot auto upgrade binary table/function definitions. Please manually upgrade.
Description/Action: Whenever a newer build of Octo is installed in an environment, any internal Octo artifacts that are incompatible with the newer build are automatically regenerated. This includes the binary representation of table definitions (CREATE TABLE queries) and function definitions (CREATE FUNCTION queries). If the previous Octo build in use is prior to r1.0.0, this automatic regeneration is not possible. The ERR_AUTO_UPGRADE error is issued in that case. The manual workaround is to drop/recreate all tables and functions (using CREATE TABLE, CREATE FUNCTION, DROP TABLE and/or DROP FUNCTION commands) in the environment. PSQL Error Code: F0000
ERR_AUTO_UPGRADE_DB_HIGHER_FMT¶
Text: Cannot auto upgrade as DB has data in higher format. Please delete data or manually upgrade.
Description/Action: Whenever a build of Octo is installed in an environment, any internal Octo artifacts that are incompatible with the build are automatically regenerated. This includes the binary representation of table definitions (CREATE TABLE queries) and function definitions (CREATE FUNCTION queries). If the previous Octo build was of higher version than the current and if artifacts of higher build was stored in the DB then auto upgrade with an older build is not possible. In such a case this error is issued. Please contact your Octo support channel for how to recover from this situation. PSQL Error Code: F0000
ERR_BAD_CONFIG¶
Text: Bad config setting in xxx: xxx
Description/Action: This error occurs when invalid configuration settings are used or a syntax error is detected in the configuration file. PSQL Error Code: F0000
ERR_BAD_ZROUTINES¶
Text: Error no valid source directory found in octo_zroutines config or $zroutines ISV
Description/Action: This error indicates that no valid source directory was found in octo_zroutines config or in $zroutines ISV. PSQL Error Code: F0000
ERR_BUFFER_TOO_SMALL¶
Text: xxx buffer too small
Description/Action: This error indicates that the buffer used to store output plans is too small for the query. PSQL Error Code: 22000
INFO_CALLING_M_ROUTINE¶
Text: Calling M routine: xxx
Description/Action: This message is generated when M routines are called. PSQL Error Code: 00000
ERR_CANNOT_CREATE_FUNCTION¶
Text: Function "xxx" already exists with same argument types
Description/Action: This error indicates an attempt to create an already existing function. PSQL Error Code: 42723
ERR_CANNOT_CREATE_TABLE¶
Text: Table or View "xxx" already exists
Description/Action: This error indicates an attempt to create an already existing table. PSQL Error Code: 42P07
ERR_CANNOT_CREATE_VIEW¶
Text: View or Table "xxx" already exists
Description/Action: This error indicates an attempt to create an already existing view. PSQL Error Code: 42P07
ERR_CANNOT_DROP_FUNCTION¶
Text: Cannot DROP function xxx: no function defined with given name and parameter types
Description/Action: This error indicates an attempt to drop a non-existent function. PSQL Error Code: 42883
ERR_CANNOT_DROP_TABLE¶
Text: Cannot DROP table "xxx" as it does not exist
Description/Action: This error indicates an attempt to drop a non-existent table. PSQL Error Code: 42P01
ERR_CANNOT_DROP_VIEW¶
Text: Cannot DROP view "xxx" as it does not exist
Description/Action: This error indicates an attempt to drop a non-existent view. PSQL Error Code: 42P01
ERR_CASE_BRANCH_TYPE_MISMATCH¶
Text: CASE branch type mismatch: left xxx, right xxx
Description/Action: This error is generated when there is a type mismatch between branches in a
CASE
statement. PSQL Error Code: 42804
ERR_CASE_VALUE_TYPE_MISMATCH¶
Text: WHEN argument is of type xxx but is used in a context that expects a xxx type
Description/Action: This error is generated when there is a type mismatch between
CASE value
andWHEN condition
type inCASE
statement. PSQL Error Code: 42804
ERR_FORMAT_NOT_ALLOWED_WITH_CAST¶
Text: Date/time format cannot be specified for cast operation
Description/Action: This error is generated when
fileman
,horolog
,zhorolog
orzut
is specificed as format in a cast operation (example:::date(fileman)
). This is not allowed. Make use of date/time conversion functions if such conversion is needed. Refer to Functions <https://docs.yottadb.com/Octo/grammar.html#date-time-functions> for the list of conversion functions available. Refer to CAST operation <https://docs.yottadb.com/Octo/grammar.html#operations-and-allowed-operand-types> for the list of valid cast operation available with date/time values. Refer to PSQL Error Code: 42846
ERR_CHECK_CONSTRAINT_VIOLATION¶
Text: New row for table xxx violates CHECK constraint xxx
Description/Action: This error is generated when the
UPDATE
orINSERT INTO
command tries to add a row that violates aCHECK
constraint defined on the table. The name of the table, the name of the constraint along with the column values of the violating row are included in the error detail. PSQL Error Code: 23514
ERR_CIRCULAR_EXTRACT_DEFINITION¶
Text: Definition for EXTRACT column "xxx" contains circular dependency starting from EXTRACT column "xxx"
Description/Action: This error is generated when a CREATE TABLE
statement contains an code:EXTRACT column definition that references another EXTRACT
column that is the same as the referring column or eventually references the referring column, creating a circular dependency. Resolve this error by revising at least one of the EXTRACT
columns to not reference the other. PSQL Error Code: 42P10
INFO_CLIENT_CONNECTED¶
Text: Client connected
Description/Action: This message lets the user know that a client connected successfully. PSQL Error Code: 00000
ERR_COMMON_COLUMN¶
Text: Common column name "xxx" appears more than once in xxx side of NATURAL JOIN
Description/Action: This message is emitted when a user attempts a
NATURAL JOIN
using a table containing multiple columns of the same name, introducing an ambiguity into the join. PSQL Error Code: 42702
ERR_CONFIG_IO_FAILURE¶
Text: File I/O error reading config setting 'xxx' in config: xxx
Description/Action: This error indicates that a config file setting is unreadable. This typically occurs when a configuration file is not formatted correctly. PSQL Error Code: 58030
INFO_CURPLAN¶
Text: LOGICAL_PLAN xxx follows xxx
Description/Action: This message is a textual representation of the current logical plan. PSQL Error Code: 00000
INFO_CURSOR¶
Text: Generating SQL for cursor xxx
Description/Action: This message indicates that SQL instructions are being generated for the given cursor. PSQL Error Code: 00000
ERR_DATABASE_FILES_OOS¶
Text: Generated routines and database seem to be out of sync
Description/Action: This error indicates that the generated routines and the database are not synchronized. PSQL Error Code: XX000
ERR_DATE_TIME_RESULT_OUT_OF_RANGE¶
Text: Result of operation exceeds date/time allowed range of values
Description/Action: This error indicates that the date/time value result of an operation exceeds the allowed range. PSQL Error Code: 22008
ERR_DDL_LITERAL¶
Text: Invalid literal in DDL specification: only xxx literals accepted for this keyword.
Description/Action: This error is emitted when a literal of an invalid type is used in a DDL keyword specification. PSQL Error Code: 42601
ERR_DOLLAR_SYNTAX¶
Text: Prepared statement dollar syntax (e.g. $1, $2, etc.) only supported in Rocto using the Extended Query Protocol
Description/Action: This error indicates that user has tried to use a dollar symbol ($) in Octo. Prepared statement dollar syntax is only supported in Rocto using the PostgreSQL Extended Query Protocol. PSQL Error Code: 42601
ERR_DROP_FUNCTION_DEPENDS¶
Text: Cannot DROP function xxx because other objects (xxx "xxx" on table "xxx") depend on it
Description/Action: This error indicates an attempt to drop a function that is still being relied upon by at least one CHECK constraint in a table. This function cannot be removed until all tables whose CHECK constraints rely on this function are dropped. PSQL Error Code: 2BP01
ERR_DROP_FUNCTION_DEPENDS_ON_VIEW¶
Text: Cannot DROP function xxx because view "xxx" depends on it
Description/Action: This error indicates an attempt to drop a function that is still being relied upon by at least one View. This function cannot be removed until all views which rely on this function are dropped. PSQL Error Code: 2BP01
ERR_DROP_TABLE_DEPENDS_ON_VIEW¶
Text: Cannot Drop table "xxx" because view "xxx" depends on it
Description/Action: This error indicates an attempt to drop a table that is still being relied upon by at least one View. This table cannot be removed until all views which rely on this function are dropped. PSQL Error Code: 2BP01
ERR_DROP_VIEW_DEPENDS_ON_VIEW¶
Text: Cannot Drop view "xxx" because view "xxx" depends on it
Description/Action: This error indicates an attempt to drop a view that is still being relied upon by at least one View. This view cannot be removed until all views which rely on this view are dropped. PSQL Error Code: 2BP01
ERR_DUPLICATE_COLUMN¶
Text: Column "xxx" specified more than once
Description/Action: This error is generated when the
CREATE TABLE
orINSERT INTO
command specifies more than one column with the same column name. Additionally, this error is generated if aCREATE TABLE
command specifies no columns with thePRIMARY KEY
orKEY NUM
keywords and specifies at least one column with the special name%YO_KEYCOL
which would then collide with the name of the hidden primary key column that Octo internally creates. PSQL Error Code: 42701
ERR_DUPLICATE_CONSTRAINT¶
Text: Constraint name "xxx" already exists
Description/Action: This error is generated when a
CREATE TABLE
specifies multiple constraints with the same name. Every constraint within a table must have a uniquely specified name. PSQL Error Code: 42710
ERR_DUPLICATE_KEY_VALUE¶
Text: Duplicate Key Value violates UNIQUE constraint xxx
Description/Action: This error is generated when the
UPDATE
orINSERT INTO
command tries to add a row that violates aUNIQUE
constraint defined on the table. The name of the constraint along with the affected list of columns and their corresponding values are included in the error detail. PSQL Error Code: 23505
ERR_DUPLICATE_PRIMARY_KEY_CONSTRAINT¶
Text: PRIMARY KEY constraint name "xxx" already exists in table "xxx"
Description/Action: This error is generated when a
CREATE TABLE
specifies a PRIMARY KEY constraint with a name that conflicts with the PRIMARY KEY constraint name of an already existing table. The user specified PRIMARY KEY constraint name needs to be unique across all tables in Octo. PSQL Error Code: 42710
INFO_ENTERING_FUNCTION¶
Text: Entering xxx
Description/Action: This message is generated when a function is entered. PSQL Error Code: 00000
INFO_ENV_VAR¶
Text: # xxx='xxx'
Description/Action: This message reports the current value of a YottaDB environment variable. PSQL Error Code: 00000
INFO_EXECUTION_DONE¶
Text: SQL query/command execution complete
Description/Action: This message indicates that query execution is complete for the current SQL query/command. The actual query/command executed can be found from the preceding INFO_PARSING_DONE message. PSQL Error Code: 00000
ERR_EXTRACT_CANNOT_BE_KEY_COLUMN¶
Text: Column "xxx" cannot be a computed/extract column and key column at same time
Description/Action: This error is generated when a column that is defined with an
EXTRACT
keyword in aCREATE TABLE
command is also defined as a key column (using thePRIMARY KEY
orKEY NUM
constraint/keyword). An EXTRACT type of column is a Computed column. A computed column cannot be a key column. PSQL Error Code: 42P10
ERR_EXTRACT_TYPE_MISMATCH¶
Text: EXTRACT column of type xxx, but function call returns type xxx
Description/Action: This error is generated when there is a type mismatch between the type of an
EXTRACT
column and the return type of the function call it references. This error may be resolved by defining the column with same type as the return type of the function specified for theEXTRACT
column. PSQL Error Code: 42804
ERR_FAILED_TO_OPTIMIZE_PLAN¶
Text: Failed to optimize logical plan
Description/Action: This error is generated when Octo fails to optimize a logical plan for a given SQL query. PSQL Error Code: XX000
ERR_FAILED_TO_PARSE_SCHEMA¶
Text: Failed to parse schema from table xxx
Description/Action: This error is generated when a table fails to parse a schema. PSQL Error Code: XX000
ERR_FAILED_TO_RETRIEVE_ENVIRONMENT_VARIABLE¶
Text: Failed to retrieve value of environment variable: 'xxx'
Description/Action: This error is generated when Octo fails to retrieve the value of an environment variable. PSQL Error Code: F0000
ERR_FEATURE_NOT_IMPLEMENTED¶
Text: Feature not implemented: xxx
Description/Action: This error indicates an attempt to use a feature that is yet to be implemented. PSQL Error Code: 0A000
ERR_FILE_NOT_FOUND¶
Text: Error opening input file: xxx
Description/Action: This error is generated when Octo tries to read from a file that is non-existent. PSQL Error Code: 58030
ERR_FUNCTION_NOT_UNIQUE¶
Text: Function 'xxx(xxx)' not unique. Parameter(s) may require explicit type cast(s)
Description/Action: A SQL function was called with one or more
NULL
arguments and the call signature matched more than one function definition (as defined by aCREATE FUNCTION
command) with the same name. Consequently, Octo cannot determine which function definition to use to call the SQL function. To resolve the ambiguity and target a specific function definition, use an explicit type cast on the ambiguous argument(s).
INFO_FUNCTION_ALREADY_EXISTS¶
Text: Function xxx already exists, skipping
Description/Action: This message lets the user know that Octo is skipping the action since the specified function already exists. PSQL Error Code: 42723
INFO_FUNCTION_DOES_NOT_EXIST¶
Text: Function xxx does not exist, skipping
Description/Action: This message lets the user know that Octo is skipping the action since the specified function does not exist. PSQL Error Code: 00000
INFO_FUNCTION_SEARCH¶
Text: Searching for function xxx
Description/Action: This message lets the user know that Octo is looking up the given function. PSQL Error Code: 00000
ERR_GENERATING_TEMPORARY_TABLE¶
Text: Generating temporary table: xxx
Description/Action: This error is generated during temporary table generation. PSQL Error Code: XX000
INFO_GENERATING_XREF¶
Text: Generating helper cross reference M file [xxx] for table [xxx] and column [xxx]
Description/Action: This message indicates that a cross reference is being generated for the given table and column as an optimization. PSQL Error Code: XX000
ERR_GLOBAL_KEY_COLS_ORDER¶
Text: GLOBAL keyword does not specify the KEY columns in the right order
Description/Action: This error is generated when a
GLOBAL
keyword in aCREATE TABLE
command specifies key columns (using thekeys()
syntax) in the wrong order. For example, if a table has primary key columnscol1
andcol2
in that order, theGLOBAL
keyword should specify a global reference where some subscriptkeys(""col1"")
is followed by a later subscript (not necessarily the immediately next subscript)keys(""col2"")
. PSQL Error Code: 42P10
ERR_GLOBAL_MISSING_KEY_COLS¶
Text: GLOBAL keyword does not specify all KEY column(s)
Description/Action: This error is generated when a
GLOBAL
keyword in aCREATE TABLE
command does not specify all key columns (using thekeys()
syntax). For example, if a table has a primary key columncol1
, theGLOBAL
keyword should specify a global reference where one subscript iskeys(""col1"")
). PSQL Error Code: 42P10
ERR_GROUP_BY_INVALID_USAGE¶
Text: Invalid GROUP BY. Only column number, column name and expressions are valid in GROUP BY (not constants or references to subqueries or aggregate function)
Description/Action: This error is generated when values referring to subqueries or aggregate functions are used in
GROUP BY
. Please use only valid column number, column name, expressions and constants. PSQL Error Code: 42803
ERR_GROUP_BY_OR_AGGREGATE_FUNCTION¶
Text: Column 'xxx' must appear in the GROUP BY clause or be used in an aggregate function
Description/Action: This error is generated when a column is
SELECT
ed, but does not appear in aGROUP BY
clause or isn't used in an aggregate function. PSQL Error Code: 42803
ERR_GROUP_BY_POSITION_INVALID¶
Text: GROUP BY position xxxxxx is not in select list
Description/Action: This error is generated when the column number of
SELECT
column list referenced inGROUP BY
is incorrect. PSQL Error Code: 42P10
ERR_GROUP_BY_POSITION_NOT_INTEGER¶
Text: Non integer constant xxxxxx in GROUP BY
Description/Action: Description/Action: This error is generated when the GROUP BY position is a non-integer. PSQL Error Code: 42601
ERR_GROUP_BY_SUB_QUERY¶
Text: Subqueries are not supported in GROUP BY
Description/Action: This error is generated when a subquery is present in
GROUP BY
. PSQL Error Code: 42803
ERR_KEYS_NEEDS_A_KEY_COLUMN¶
Text: Column "xxx" specified using keys() in EXTRACT/GLOBAL keyword is not a KEY column
Description/Action: This error is generated when a
keys()
usage as part of aEXTRACT
orGLOBAL
keyword in aCREATE TABLE
command specifies a column name that is not a key column in the table. If the column is a non-key column, usevalues()
instead. If the column should be a key column, specify thePRIMARY KEY
constraint/keyword as part of that column definition in the sameCREATE TABLE
command. PSQL Error Code: 42P10
ERR_IDENT_LENGTH¶
Text: xxx length xxx exceeds max (xxx)
Description/Action: This error indicates that a query attempted to use an identifier (such as a table name) that is longer than the maximum length allowed. PSQL Error Code: 22P02
ERR_INIT_SCANNER¶
Text: Error initializing the scanner
Description/Action: This message indicates an error in initializing the scanner used to parse provided input. Please contact your YottaDB support channel. PSQL Error Code: XX000
ERR_INSERT_ON_GENERATED_ALWAYS_IDENTITY¶
Text: Cannot INSERT into GENERATED ALWAYS identity column "xxx". Use OVERRIDING SYSTEM VALUE to override.
Description/Action: This error is generated when the
INSERT INTO
command is done on an ALWAYS GENERATED identity column. SeeOVERRIDING SYSTEM VALUE
in IDENTITY to know how to override this check. PSQL Error Code: 428C9
ERR_INSERT_TOO_MANY_COLUMNS¶
Text: INSERT has more target columns than expressions
Description/Action: This error is generated when the
INSERT INTO
command specifies more columns in the comma-separated list of columns (corresponding to the target table) than the number of expression columns in the source query. PSQL Error Code: 42601
ERR_INSERT_TOO_MANY_EXPRESSIONS¶
Text: INSERT has more expressions than target columns
Description/Action: This error is generated when the
INSERT INTO
command specifies more expression columns in the source query than the number of comma-separated columns specified for the target table (if a comma-separated list of target columns is specified) or the number of columns of the target table (if no comma-separated list of target columns is specified). PSQL Error Code: 42601
ERR_INSERT_TYPE_MISMATCH¶
Text: Column "xxx" is of type xxx but expression is of type xxx
Description/Action: This error is generated when the
INSERT INTO
command specifies a target column whose type is different from the corresponding source column expression. PSQL Error Code: 42804
ERR_INVALID_BOOLEAN_SYNTAX¶
Text: Invalid input syntax for type boolean: 'xxx' is not a valid boolean value
Description/Action: This error is generated when the user attempts to assign a non-boolean value to a boolean variable. PSQL Error Code: 22P02
ERR_INVALID_CLI_OPTION¶
Text: Invalid value specified for option xxx
Description/Action: This error is issued when a user attempts to use an unacceptable command line option value. PSQL Error Code: 22P02
ERR_INVALID_CONSTRAINT_EXPRESSION¶
Text: xxx expressions not accepted within CHECK constraints
Description/Action: This error is issued when a user attempts to use an unacceptable expression in a
CHECK
constraint. PSQL Error Code: 22P02
ERR_INVALID_DATE_TIME_VALUE¶
Text: "xxx" is invalid for type "xxx", format "xxx" and datestyle "xxx"
Description/Action: This error is issued when a date/time value is outside the range of valid values(RANGE <https://docs.yottadb.com/Octo/grammar.html#range>) or is syntactically incorrect for the given date/time type and format, or if value doesn't match the format specified in datestyle(INPUT AND OUTPUT TEXT FORMAT VALUE <https://docs.yottadb.com/Octo/grammar.html#input-and-output-text-format-value>), or when an in-exact fileman date is having either year as zero or when month is zero and day is non zero(NOTE <https://docs.yottadb.com/Octo/grammar.html#note>). PSQL Error Code: 22007
ERR_INVALID_DATE_TIME_TYPE_FORMAT¶
Text: The given type and format is invalid
Description/Action: This error is issued when a time/time with time zone type is specified to have fileman format or when time/time with time zone/timestamp with time zone type is specified to have zut format. This is invalid. PSQL Error Code: 22007
ERR_INVALID_DATESTYLE_VALUE¶
Text: DATESTYLE value "xxx" is invalid
Description/Action: This error is issued when the value given to set DATESTYLE is incorrect. See INPUT AND OUTPUT TEXT FORMAT VALUE <https://docs.yottadb.com/Octo/grammar.html#input-and-output-text-format-value> for more details. PSQL Error Code: 22023
ERR_INVALID_DROP¶
Text: Dropping "xxx" is disallowed as it is a system object
Description/Action: This error is issued when a user attempts to drop a table/function/view which is defined in octo-seed.sql. This is not allowed. PSQL Error Code: 42601
ERR_INVALID_ESCAPE_PATTERN¶
Text: Cannot end pattern with escape character: xxx
Description/Action: This error is issued when a user attempts to use an invalid escape pattern in a regular expression. PSQL Error Code: 22025
ERR_INVALID_INPUT_SYNTAX¶
Text: Invalid input syntax : Expecting type NUMERIC or INTEGER : Actual type xxx
Description/Action: This error is issued when a user attempts to use a unary '+' or '-' on a field of non-numeric type. PSQL Error Code: 22P02
ERR_INVALID_INTEGER_SYNTAX¶
Text: Invalid input syntax for type integer: 'xxx'
Description/Action: This error indicates that an integer was expected in this context, but a non-integer value was specified. PSQL Error Code: 22P02
ERR_INVALID_NUMERIC_SYNTAX¶
Text: Invalid input syntax for type numeric: 'xxx'
Description/Action: This error indicates that an numeric was expected in this context, but a non-numeric value was specified. PSQL Error Code: 22P02
ERR_INVALID_KEYWORD_CHAR¶
Text: Integer value xxx given for xxx character is not a valid ASCII (0-127) character
Description/Action: This error is issued when a user attempts to use an invalid character as part of a
DELIM
specfication. Accepted values range from zero(0) to 127 (ASCII). PSQL Error Code: 42601
ERR_INVALID_NUMBER¶
Text: xxx: invalid number of xxx: xxx is out of range (min: xxx, max: xxx)
Description/Action: This error indicates that there is an invalid number of items of the given type. PSQL Error Code: 22003
ERR_PARSE_FAILED¶
Text: xxx
Description/Action: This error indicates that the parser reached an invalid state when parsing the given query. The printed text specifies which token specifically caused the failure. Fix the query syntax and try again. PSQL Error Code: 42601
ERR_INVALID_READ_SIZE¶
Text: Read size xxx out of range
Description/Action: This error indicates an internal code attempt to read beyond a buffer's allocated range. Please contact your YottaDB support channel. PSQL Error Code: 22003
ERR_INVALID_RUNTIME_PARAMETER¶
Text: Unrecognized runtime configuration parameter "xxx"
Description/Action: This error indicates an attempt to access a run-time configuration parameter that does not exist. For a full list of accepted run-time parameters and related information, issue the following query: SELECT * FROM pg_settings. PSQL Error Code: 22023
ERR_INVALID_TYPE¶
Text: Type xxx does not exist
Description/Action: This error is generated when a user attempts to use a type that doesn't exist. PSQL Error Code: 42704
ERR_INVALID_WRITE_SIZE¶
Text: Write size xxx out of range
Description/Action: This error indicates an internal code attempt to write beyond a buffer's allocated range. Please contact your YottaDB support channel. PSQL Error Code: 22003
ERR_JOIN_ALIAS_DUPLICATE¶
Text: table name "xxx" specified more than once
Description/Action: This error is generated when a table name has been specified more than once. PSQL Error Code: 42712
INFO_LEAVING_FUNCTION¶
Text: LEAVING xxx
Description/Action: This message is generated when the flow of control is leaving a function and is used for debugging. PSQL Error Code: 00000
ERR_LIBCALL¶
Text: Library call failed: xxx
Description/Action: This error is generated when a library call fails. PSQL Error Code: 58000
ERR_LIBCALL_WITH_ARG¶
Text: Library call xxx failed with argument 'xxx'
Description/Action: This error is generated when a library call fails, and provides additional information about the arguments passed to it. PSQL Error Code: 58000
ERR_LIBSSL_ERROR¶
Text: Error in libssl/libcrypt
Description/Action: This error is generated when there is a problem with libssl/libcrypt. PSQL Error Code: XX000
ERR_LINE_TOO_LONG¶
Text: Input line too long
Description/Action: This error is generated if the input line is too long. PSQL Error Code: 22026
ERR_LITERAL_MAX_LEN¶
Text: Literal value exceeds max length (xxx bytes)
Description/Action: This error indicates that a query was issued containing a literal value that exceeds the maximum length in bytes allowed for any literal value. PSQL Error Code: 22003
INFO_LOADED_CONFIG¶
Text: Loaded config from xxx
Description/Action: This message is generated when a configuration file has been loaded. PSQL Error Code: 00000
INFO_M_PLAN¶
Text: Generating M file [xxx] (to execute SQL query)
Description/Action: This message notifies the user that an M plan is being generated for the given cursor. PSQL Error Code: 00000
INFO_MEM_REALLOCATION¶
Text: Memory xxx for variable xxx
Description/Action: This message is generated when memory for a particular variable is reallocated. PSQL Error Code: 00000
ERR_MEMORY_USAGE¶
Text: Failed to retrieve memory usage at process exit
Description/Action: This message indicates a failure to determine how much memory is in use at Octo process exit. PSQL Error Code: 58000
INFO_MEMORY_USAGE¶
Text: Memory usage at process exit: xxx Kb
Description/Action: This message reports how much memory is in use at Octo process exit. PSQL Error Code: 00000
ERR_MIDENT_LENGTH¶
Text: Length xxx too large for M identifier (max length xxx)
Description/Action: This error indicates that the length for an M identifier has been exceeded. PSQL Error Code: 22003
ERR_MISSING_FROM_ENTRY¶
Text: Missing FROM-clause entry for table : xxx
Description/Action: This error indicates that there is no entry for the given table in a FROM clause. PSQL Error Code: 42P01
ERR_MISSING_KEY¶
Text: Missing key xxx in table xxx; max key was xxx
Description/Action: This error indicates that the schema for the table lacks the correct number of keys, and that it needs to be corrected. PSQL Error Code: 42704
ERR_MISTYPED_FUNCTION¶
Text: Function xxx cannot be invoked with a parameter of type xxx
Description/Action: This error indicates that a function was passed an argument whose type does not match that defined for the given parameter. PSQL Error Code: 42883
ERR_MISTYPED_FUNCTION_TABLE_ASTERISK¶
Text: Aggregate function xxx cannot be invoked with a parameter of type xxx
Description/Action: This error indicates that the aggregate function xxx was passed a parameter of type
table.*
which is unsupported. PSQL Error Code: 42883
ERR_MULTIPLE_VALUES_PROVIDED¶
Text: Multiple values provided for xxx; undefined behavior
Description/Action: This error indicates that multiple values have been provided for a particular parameter. PSQL Error Code: 42P08
ERR_MULTIPLE_ZERO_KEYS¶
Text: Multiple xxx keys found for table xxx
Description/Action: This error indicates that the table has multiple
KEY NUM
elements with the same number, and that the source schema needs to be corrected. PSQL Error Code: 42P08
ERR_NEGATIVE_SUBSTRING_LENGTH¶
Text: negative substring length not allowed
Description/Action: This error is generated when the
substring()
function is invoked with a negative length (3rd parameter). PSQL Error Code: 22011
ERR_NOT_OPERATION_TYPE_MISMATCH¶
Text: xxx type operand is incorrect for NOT operation. Need a boolean operand.
Description/Action: This error is generated when
NOT
operation is applied on a non boolean operand. PSQL Error Code: 42804
ERR_NON_INTEGER_IDENTITY¶
Text: Only integer columns can be an identity column
Description/Action: This error is generated when a non
INTEGER
column is made as an identity inCREATE TABLE
command. PSQL Error Code: 22023
ERR_NULL_COL_VALUE¶
Text: NULL value in column xxx violates NOT NULL constraint
Description/Action: This error is generated when the
UPDATE
orINSERT INTO
command tries to add a row that violates aNOT NULL
constraint defined on the table. The affected primary key column name is included in the error detail. PSQL Error Code: 23502
ERR_NULL_SUBS_DISABLED¶
Text: Null subscripts must be enabled for proper operation. Please set '-null_subscripts=always' for all regions containing Octo global variables.
Description/Action: This error indicates that Null Subscripts have been turned off. However, they must be enabled for proper operation. Set '-null_subscripts=always' for all regions containing Octo global variables. PSQL Error Code: F0000
ERR_NUMERIC_SCALE¶
Text: Numeric scale xxx must be between zero(0) and precision xxx
Description/Action: This error indicates that the SCALE value in a NUMERIC(PRECISION,SCALE) specification cannot be greater than the PRECISION value. PSQL Error Code: 22023
ERR_NUMERIC_OVERFLOW¶
Text: Numeric field overflow; A field with precision xxx, scale xxx must round to an absolute value less than 10^xxx
Description/Action: This error indicates that the integer portion of a value that is being type cast to NUMERIC(PRECISION,SCALE) cannot be longer than PRECISION-SCALE (i.e. PRECISION minus SCALE) decimal digits. PSQL Error Code: 22003
ERR_AUTO_SEED_LOAD¶
Text: Failed to load internal tables and functions
Description/Action: This error indicates that the auto load of internal tables and function have failed. Examine the preceding messages for more error detail. Fix the cause of that error and rerun the command that produced the ERR_AUTO_SEED_LOAD error. PSQL Error Code: XX000
ERR_ORDER_BY_POSITION_INVALID¶
Text: ORDER BY position xxxxxx is not in select list
Description/Action: This error is generated when the column number of the
SELECT
column list referenced inORDER BY
is incorrect. PSQL Error Code: 42P10
ERR_ORDER_BY_POSITION_NOT_INTEGER¶
Text: Non integer constant xxxxxx in ORDER BY
Description/Action: This error is generated when the ORDER BY position is a non-integer. PSQL Error Code: 42601
ERR_ORDER_BY_SELECT_DISTINCT¶
Text: For SELECT DISTINCT, ORDER BY expressions must appear in select list
Description/Action: This error is generated when the
ORDER BY
expression is attempted outside of the select list when using theDISTINCT
quantifier. PSQL Error Code: 42P10
INFO_OCTO_STARTED¶
Text: Octo started
Description/Action: This message indicates that an Octo process has begun execution. PSQL Error Code: 00000
ERR_PARM_CANNOT_BE_CHANGED¶
Text: Runtime parameter "xxx" cannot be changed
Description/Action: This message indicates an attempt to modify a read-only runtime parameter. PSQL Error Code: 55P02
ERR_PARSING_COMMAND¶
Text: Error parsing statement: xxx
Description/Action: This message indicates that there is an error in parsing the statement or command. PSQL Error Code: XX000
ERR_PARSING_CONFIG¶
Text: Error parsing config (xxx): line xxx: xxx
Description/Action: This error is generated when there is an error parsing the configuration file. PSQL Error Code: F0000
INFO_PARSING_DONE¶
Text: Parsing done for SQL command [xxx]
Description/Action: This message indicates that parsing is complete for the given SQL statement or command. PSQL Error Code: 00000
ERR_PERCENT_IN_EXTRINSIC_FUNCTION_NAME¶
Text: '%%' is only allowed at the beginning of an M label or routine name.
Description/Action: This error is generated when a user attempts to map a SQL function to an improperly formatted M extrinsic function name. PSQL Error Code: 42601
ERR_PLAN_HASH_FAILED¶
Text: Failed to generate plan filename hash
Description/Action: This error is generated when Octo fails to generate the filename hash for the plan. PSQL Error Code: XX000
ERR_PLAN_NOT_GENERATED¶
Text: Failed to generate xxx plan
This error is generated when Octo fails to generate the plan for the given SQL query or command. PSQL Code: XX000
ERR_PLAN_NOT_WELL_FORMED¶
Text: Plan produced by optimizer appears incorrect
Description/Action: This error is generated when the plan produced by the optimizer is incorrect. Please contact your YottaDB support channel. PSQL Error Code: XX000
ERR_PLAN_OWNER¶
Text: Problem resolving owner for deferred plan; undefined behavior
Description/Action: This error is indicates an internal error in resolving query subplans. Please contact your YottaDB support channel. PSQL Error Code: XX000
ERR_PRIMARY_KEY_NOT_FOUND¶
Text: No primary key specified when creating table "xxx". Please consult the documentation for more information.
Description/Action: This error is generated when a table was created without specifying a primary key. PSQL Error Code: 42601
INFO_PROCESSING_MESSAGE_TYPE¶
Text: Processing message type xxx
Description/Action: This debug message indicates that a PostgreSQL wire protocol message of a particular type is being processed. PSQL Error Code: 00000
WARN_FEATURE_NOT_IMPLEMENTED¶
Text: Feature not implemented but some of its usages are allowed: xxx
Description/Action: This warning message indicates a feature is used that is yet to be fully implemented. Some of its usages are being allowed to enable the working of a few clients that is why the query didn't issue an error but instead a warning was logged. Refer to the message or Grammar <https://docs.yottadb.com/Octo/grammar.html> section for more details on the usages that are allowed. PSQL Error Code: 0A000
WARN_READLINE_LOAD_FAIL¶
Text: Failed to load history file xxx (check your file name and permissions)
Description/Action: This warning message says that history couldn't be read from the specific file. This is due to a bad file name or a file on which you don't have permissions. Fix this by specifying the correct history file in octo.conf. If you are sure that the file is correct, then check the permissions on the file to make sure you can write it to. Hint: starting Octo with -v gives you information on where the history file is stored.
WARN_READLINE_SAVE_FAIL¶
Text: Failed to save history file xxx (check your file name and permissions)
Description/Action: See WARN_READLINE_LOAD_FAIL. This is the same error but occurs on save.
INFO_READLINE_NOTIFY_HIST_COUNT¶
Text: History limited to xxx entries
Description/Action: This is an informational message to tell you how many entries in history will be saved when you exit Octo.
INFO_READLINE_NOTIFY_HIST_STIFLED¶
Text: History stifled to xxx entries
Description/Action: This is an informational message to tell you that due to an INPUTRC setting of
history-size
, the runtime storage list for Octo is limited to the number of entries set byhistory-size
. We do not recommend using this setting with Octo. If you need it with other applications, make sure to guard the setting in the INPUTRC so that it does not apply to application "Octo". See Readline Documentation for more information.
INFO_READLINE_NOTIFY_HIST_LOCATION¶
Text: History located at xxx
Description/Action: This is an informational message to tell you where your history will be stored. This can be helpful if you need to know why your history didn't load, or why a certain history file is not writable.
INFO_READLINE_NOTIFY_LOAD¶
Text: Reading history
Description/Action: Purely informational message to say that we are about to read the history.
INFO_READLINE_NOTIFY_LOAD_COUNT¶
Text: Reading xxx history entries
Description/Action: Purely informational message to say how many entries we read from history.
INFO_READLINE_NOTIFY_SAVE¶
Text: Saving history
Description/Action: Purely informational message to say that we are about to save the history.
INFO_READLINE_NOTIFY_SAVE_COUNT¶
Text: Saving xxx additional history entries
Description/Action: Purely informational message to say how many entries we will save to history.
ERR_READONLY_DISALLOWED¶
Text: READONLY keyword in CREATE TABLE is disallowed due to an incompatible keyword
Description/Action: This error is generated when a CREATE TABLE command specifies the table type to be READONLY but also specifies another keyword that is incompatible with READONLY. Specifying a CHECK or a UNIQUE constraint is the only way to create an incompatibility currently. Such constraints are only supported with READWRITE type tables. So changing the table type to be READWRITE will fix the error. PSQL Error Code: 42601
ERR_READONLY_AND_READWRITE_DISALLOWED¶
Text: CREATE TABLE specifies keywords that make it incompatible with both READONLY and READWRITE keywords
Description/Action: This error is generated when a CREATE TABLE command does not explicitly specify the table type as READONLY or READWRITE (the only two possible types) but specifies keyword(s) that make it incompatible with READONLY and keyword(s) that make it incompatible with READWRITE. See ERR_READONLY_DISALLOWED and/or ERR_READWRITE_DISALLOWED message description for potential causes of the incompatibility. Decide which type the table needs to be, specify that keyword explicitly and remove the keywords that are incompatible with this type from the CREATE TABLE command. PSQL Error Code: 42601
ERR_READWRITE_DISALLOWED¶
Text: READWRITE keyword in CREATE TABLE is disallowed due to an incompatible keyword
Description/Action: This error is generated when a CREATE TABLE command specifies the table type to be READWRITE but also specifies another keyword that is incompatible with READWRITE. A table level GLOBAL keyword is compatible if it specifies just an unsubscripted M global name followed by subscripts that only correspond to primary key columns (using the
keys(...)
syntax). Otherwise it is considered incompatible. A column level PIECE keyword is compatible if it is specified for a non-key column and the piece number matches the number of this non-key column (starting from one(1) from the leftmost non-key column in the CREATE TABLE command). Otherwise it is considered incompatible. A column level EXTRACT, GLOBAL, DELIM, START, STARTINCLUDE or END keyword is considered incompatible. There is one exception to this rule and that is a table with only one non-key column that also has a column levelDELIM ""
specified. This is considered compatible. This error is also generated in some cases when a CREATE TABLE command does not specify the table type to be READWRITE or READONLY but specifies a keyword that is incompatible with READWRITE and a default table type of READWRITE is assumed. In such cases, explicitly specifying the table type as READONLY would fix the error. PSQL Error Code: 42601
INFO_READ_MESSAGE¶
Text: Read message of type xxx and length xxx
Description/Action: This debug message indicates that a PostgreSQL wire protocol message of the specified format was read from the wire. PSQL Error Code: 00000
INFO_RECORDING_ENV_VARS¶
Text: # Recording pertinent ydb_* env var values at process startup
Description/Action: This message notes that various YDB environment variable values are being recorded at startup . PSQL Error Code: 00000
INFO_RETURNING_FAILURE¶
Text: Returning failure from xxx
Description/Action: This debug message indicates that the given function exited due to an error. PSQL Error Code: 00000
INFO_REUSE_M_PLAN¶
Text: Using already generated M file [xxx] (to execute SQL query)
Description/Action: This message indicates that an M plan has already been generated for the current SQL query and will be used instead of creating a new one. PSQL Error Code: 00000
SELECT_STAR_NO_TABLES¶
Text: SELECT * with no tables specified is not valid
Description/Action: This error indicates that a user attempted to select all rows without specifying a table to select them from. PSQL Error Code: 42601
INFO_SEND_MESSAGE¶
Text: Sending message of type xxx and length xxx
Description/Action: This debug message indicates that a PostgreSQL wire protocol message of the specified format was written to the wire. PSQL Error Code: 00000
ERR_SETOPER_NUMCOLS_MISMATCH¶
Text: Each xxx query must have same number of columns
Description/Action: This error is generated when the two operands of a SET operation do not have the same number of columns. PSQL Error Code: 42804
ERR_SETOPER_TYPE_MISMATCH¶
Text: xxx types xxx and xxx cannot be matched
Description/Action: This error is generated when the two operands of a SET operation are of different types. PSQL Error Code: 42601
ERR_SUBQUERY_ONE_COLUMN¶
Text: Subquery must return only one column
Description/Action: This error is generated when a subquery must return only one column. PSQL Error Code: 42601
ERR_SUBQUERY_CHECK¶
Text: Cannot use subquery in CHECK constraint
Description/Action: This error is generated when a subquery is used in a CHECK constraint, which is not allowed. PSQL Error Code: 0A000
ERR_SUBQUERY_MULTIPLE_ROWS¶
Text: More than one row returned by a subquery used as an expression
Description/Action: This error is generated when more than one row is returned by a subquery that is used as an expression. PSQL Error Code: 21000
ERR_SYSCALL¶
Text: System call failed: xxx, return xxx (xxx)
Description/Action: This error is generated when a system call has failed. PSQL Error Code: 58000
ERR_SYSCALL_WITH_ARG¶
Text: System call failed: xxx, return xxx (xxx): args: xxx
Description/Action: This error is generated when a system call fails, and provides additional information about the arguments passed to it. PSQL Error Code: 58000
INFO_TABLE_ALREADY_EXISTS¶
Text: Table "xxx" already exists, skipping
Description/Action: This message lets the user know that Octo is skipping the action since the specified table already exists. PSQL Error Code: 42P07
ERR_TABLE_ASTERISK_COLUMN_COUNT_MISMATCH¶
Text: Table asterisk column count mismatch: left xxx, right xxx
Description/Action: This error is generated when the comparison between two
table.*
usages cannot be made as their number of columns do not match. PSQL Error Code: 42804
ERR_TABLE_ASTERISK_COLUMN_TYPE_MISMATCH¶
Text: Table asterisk column type mismatch: left xxx, right xxx
Description/Action: This error is generated when the comparison between two
table.*
usages cannot be made as their column types do not match. PSQL Error Code: 42804
ERR_TABLE_ASTERISK_SCALAR_COMPARISON¶
Text: Table asterisk cannot be compared against column reference
Description/Action: This error is generated when the comparison is done between a
table.*
and regular column reference, as its an invalid usage. PSQL Error Code: 42804
ERR_TABLE_DEFINITION_TOO_LONG¶
Text: Table definition for xxx too long; max size is xxx, table length is xxx
Description/Action: This error is generated when the table definition is too long. PSQL Error Code: 42P16
INFO_TABLE_DOES_NOT_EXIST¶
Text: Table "xxx" does not exist, skipping
Description/Action: This message lets the user know that Octo is skipping the action since the specified table does not exist. PSQL Error Code: 00000
INFO_VIEW_DOES_NOT_EXIST¶
Text: View "xxx" does not exist, skipping
Description/Action: This message lets the user know that Octo is skipping the action since the specified view does not exist. PSQL Error Code: 00000
ERR_TABLE_KEY_NUM¶
Text: CREATE TABLE for table "xxx" cannot use table-level PRIMARY KEY constraint and KEY NUM at same time
Description/Action: This error is generated when a
CREATE TABLE
command specifies a table-levelPRIMARY KEY
constraint (i.e. a PRIMARY KEY keyword followed by a parenthesized list of column names) and aKEY NUM
keywords in the same command. To specify multiple key columns in the table, use only a table-levelPRIMARY KEY
constraint. No need for any KEY NUM keywords (which are still supported only for historical reasons). PSQL Error Code: 42P10
ERR_TABLE_MULTIPLE_IDENTITY¶
Text: Multiple identity specified for column "xxx" of table "xxx"
Description/Action: This error is generated when a
CREATE TABLE
command specifies more than one column levelIDENTITY
specifications. PSQL Error Code: 42601
ERR_TABLE_MULTIPLE_PRIMARY_KEYS¶
Text: Multiple primary keys for table "xxx" are not allowed
Description/Action: This error is generated when a
CREATE TABLE
command specifies more than one column level or table levelPRIMARY KEY
constraint. PSQL Error Code: 42P10
ERR_TABLE_MUST_HAVE_A_VISIBLE_COLUMN¶
Text: Table "xxx" must have at least one visible column
Description/Action: This error is generated when a
CREATE TABLE
command does not specify any user visible columns (possible for example if the command only specifies table levelCHECK
constraint). PSQL Error Code: 42P10
ERR_TABLE_MUST_HAVE_A_NON_EXTRACT_COLUMN¶
Text: Table "xxx" must have at least one non-EXTRACT column
Description/Action: This error is generated when all columns specified in a
CREATE TABLE
command have theEXTRACT
keyword. Such a table would have all of its columns be computed columns. A table should have at least one non-computed column. PSQL Error Code: 42P10
ERR_TABLE_READONLY¶
Text: xxx not allowed on READONLY table "xxx". Only allowed on READWRITE tables.
Description/Action: Queries that modify tables (e.g. INSERT INTO, DELETE, ALTER etc.) are not allowed on tables that have been created as READONLY. They are only allowed on READWRITE tables. PSQL Error Code: 42601
INFO_TABLE_OR_VIEW_SEARCH¶
Text: Searching for table or view xxx
Description/Action: This message lets the user know that Octo is looking up the given table or a view. PSQL Error Code: 00000
ERR_TABLE_UNKNOWN_COLUMN_NAME¶
Text: Column "xxx" of table "xxx" does not exist
Description/Action: This error is generated when the specified column name is not a valid column in the specified table. PSQL Error Code: 42703
INFO_TEXT_REPRESENTATION¶
Text: xxx
Description/Action: This message prints the text representation of a DDL specification. PSQL Error Code: 00000
ERR_TOO_MANY_DELIM_CHARS¶
Text: Too many characters specified for DELIM specification (got: xxx, max: xxx)
Description/Action: This message indicates an attempt to specify more characters in a DELIM specification than is supported within an Octo DDL. PSQL Error Code: 22003
ERR_TOO_MANY_FUNCTION_ARGUMENTS¶
Text: Too many arguments passed for function xxx (max: xxx)
Description/Action: This error indicates an attempt to create a function with more arguments than the maximum allowed. PSQL Error Code: 22003
ERR_TOO_MANY_SELECT_KEYCOLS¶
Text: Too many key columns specified in SELECT query (got: xxx, max: xxx)
Description/Action: This message indicates an attempt to specify too many key columns in a SELECT query. For every table specified in the FROM/JOIN list of a SELECT query, the number of key columns is summed up and if the sum is more than 256, this error is issued. PSQL Error Code: 54001
ERR_TOO_MANY_TABLE_KEYCOLS¶
Text: Too many key columns specified in CREATE TABLE of xxx (got: xxx, max: xxx)
Description/Action: This message indicates an attempt to specify too many key columns in a CREATE TABLE command. The maximum number of key columns allowed in one table is 256. PSQL Error Code: 54001
ERR_TYPE_CAST¶
Text: Cannot cast type xxx to type xxx
Description/Action: This error is generated when a type cast operation is attempted on a
table.*
typed value. No type cast operations are allowed on that type. PSQL Error Code: 42846
ERR_TYPE_MISMATCH¶
Text: Type mismatch: left xxx, right xxx
Description/Action: This error is generated when there is a type mismatch between parameters. PSQL Error Code: 42804
ERR_TYPE_NOT_COMPATIBLE¶
Text: Type xxx not compatible for xxx
Description/Action: This error is generated when a type is not compatible with a parameter. PSQL Error Code: 42883
ERR_UNGROUPED_OUTER_QUERY_COLUMN¶
Text: subquery uses ungrouped column xxx from outer query
Description/Action: This error is generated when an un-grouped outer query column is used in inner query. PSQL Error Code: 42803
ERR_UNKNOWN_COLUMN_NAME¶
Text: Unknown column: xxx
Description/Action: This error is generated when the column referenced does not exist or is unknown. Note that column names are case sensitive (stored internally in upper case if not specified as a double-quoted identifier) and so if these are specified inside
keys()
orvalues()
specifications in aEXTRACT
keyword or aGLOBAL
keyword (both column-level and table-level keywords) of aCREATE TABLE
command, it is important that the case match. PSQL Error Code: 42703
ERR_UNKNOWN_FUNCTION¶
Text: No function xxx defined with given parameter types (xxx)
Description/Action: This error is generated when the function referenced does not exist or is unknown. PSQL Error Code: 42883
ERR_UNKNOWN_FUNCTION_EMULATION¶
Text: No xxx-parameter function xxx() defined for the current database emulation mode (xxx)
Description/Action: This error is generated when there is no function defined with the given number of arguments for the currently active database emulation mode. PSQL Error Code: 42883
ERR_UNKNOWN_KEYWORD_STATE¶
Text: Unknown state reached; please contact your Octo support channel
Description/Action: This error indicates an unknown keyword state was reached. Please contact your YottaDB support channel. PSQL Error Code: XX000
ERR_UNKNOWN_MESSAGE_TYPE¶
Text: Unknown message type from frontend: xxx
Description/Action: This error is generated when an unknown message type was received from a remote client. Please contact your YottaDB support channel. PSQL Error Code: 08P01
ERR_UNKNOWN_TABLE¶
Text: Unknown table: xxx
Description/Action: This error is generated when the table referenced does not exist or is unknown. PSQL Error Code: 42P01
ERR_UPDATE_OF_GENERATED_ALWAYS_IDENTITY¶
Text: Updating a GENERATED ALWAYS IDENTITY column "xxx" to a non-DEFAULT value is invalid.
Description/Action: This error is genererated when a GENERATED ALWAYS AS IDENTITY column is being updated with a non-DEFAULT value. This is invalid. PSQL Error Code: 428C9
ERR_VALUES_LENGTH¶
Text: VALUES lists must all be the same length
Description/Action: This error is generated when a VALUES keyword specifies a list of rows where at least one row does not have the same number of columns as the other rows. PSQL Error Code: 42601
ERR_VALUES_NEEDS_A_NON_KEY_COLUMN¶
Text: Column "xxx" specified using values() in EXTRACT/GLOBAL keyword is a KEY column
Description/Action: This error is generated when a
values()
usage as part of anEXTRACT
keyword in aCREATE TABLE
command specifies a column name that is a key column in the table. If the column is a key column, usekeys()
instead. If the column should be a non-key column, make sure thePRIMARY KEY
constraint/keyword is not specified as part of that column definition in the sameCREATE TABLE
command. PSQL Error Code: 42P10
ERR_VALUES_NOT_ALLOWED_IN_GLOBAL¶
Text: values() usage not allowed in GLOBAL keyword (only keys() usage allowed)
Description/Action: This error is generated when a
values()
is used as part of aGLOBAL
keyword in aCREATE TABLE
command. Only key columns should be specified in theGLOBAL
keyword and they should use thekeys()
syntax, not thevalues()
syntax. PSQL Error Code: 42P10
ERR_VALUES_NOT_ALLOWED_IN_START_END¶
Text: values() usage not allowed in START/END keywords (only keys() usage allowed)
Description/Action: This error is generated when a
values()
is used as part of aSTART
orEND
keyword in aCREATE TABLE
command. Only key columns should be specified in those keywords and they should use thekeys()
syntax, not thevalues()
syntax. PSQL Error Code: 42P10
ERR_VARCHAR_TOO_LONG¶
Text: Value too long for type VARCHAR(xxx)
Description/Action: This error indicates that the specified value is more than xxx characters long and hence cannot fit in the VARCHAR(xxx) type. Specify a value which is less than or equal to xxx characters long. PSQL Error Code: 22001
ERR_VIEW_MORE_COLUMN_NAMES¶
Text: View specifies more column names than the number of columns defined
Description/Action: This error indicates that create view specifies more column names than the number of columns present in the view definition. PSQL Error Code: 42601
ERR_VIEW_OPERATION_NOT_SUPPORTED¶
Text: xxx operation on a view is not implemented
Description/Action: This error indicates that the operation being performed is not supported. PSQL Error Code: 0A000
ERR_WRONG_TYPE¶
Text: "xxx" is not a xxx
Description/Action: This error indicates that the query is executed on a wrong type of object. Second argument specifies the type of object required for the executed query. PSQL Error Code: 42809
ERR_YOTTADB¶
Text: YottaDB error: xxx
Description/Action: Octo encountered an error generated by YottaDB. Consult the Administration and Operations Guide or the Messages and Recovery Procedures Manual for more information.
ERR_ZERO_LENGTH_IDENT¶
Text: Zero-length identifier
Description/Action: Octo encountered an attempt to use the empty string as a SQL identifier, e.g. a table or column name. This error may be resolved by only referencing identifiers containing at least one character. PSQL Error Code: 22003
Rocto Specific Errors¶
Rocto Specific Errors are of the form
ERR_ROCTO_<error>
orINFO_ROCTO_<error>
. These errors can occur only inrocto
. The errors are detailed below, in alphabetical order. Occurrences of "xxx" indicate portions of the error message text that vary depending on the details of the particular error.
INFO_AUTH_SUCCESS¶
Text: xxx: user successfully authenticated
Description/Action: This message indicates that the Rocto user has been successfully authenticated. PSQL Error Code: 00000
ERR_ROCTO_BAD_ADDRESS¶
Text: Bad listen address: xxx
Description/Action: This error is issued when Rocto fails to correctly initialize a listening socket. PSQL Error Code: 08000
ERR_ROCTO_BAD_PASSWORD¶
Text: xxx: password doesn't match stored value
This message indicates that the password entered does not match the stored value. PSQL Code Error: 28P01
ERR_ROCTO_BAD_TIMESTAMP¶
Text: handle_cancel_request: PID timestamp doesn't match stored value
Description/Action: This message indicates that a Cancel Request was attempted using a timestamp that doesn't match that of the target PID. Timestamps are checked to ensure that only the client who spawned a Rocto process can cancel queries running in that process. This error is not disclosed to the client to prevent information leakage about active Rocto processes. PSQL Error Code: 28000
ERR_ROCTO_BIND_PARAMETER_DECODE_FAILURE¶
Text: Failed to decode binary bind parameter
Description/Action: This error indicates that Rocto failed to decode a bind parameter from a binary format. PSQL Error Code: XX000
ERR_ROCTO_BIND_TO_UNKNOWN_QUERY¶
Text: Bind to unknown query attempted
Description/Action: This error indicates that the user has attempted to bind parameter values to a non-existent prepared statement. PSQL Error Code: 08P01
INFO_ROCTO_CHILD_STATE_UPDATED¶
Text: Process xxx switched to state xxx
Description/Action: This message indicates that the Rocto child process state has been updated. PSQL Error Code: 00000
INFO_ROCTO_CLEAN_DISCONNECT¶
Text: connection closed cleanly
Description/Action: This message indicates that a Rocto connection has been closed cleanly. PSQL Error Code: 00000
ERR_ROCTO_COLUMN_VALUE¶
Text: xxx: failed to extract column value xxx from row
Description/Action: This error indicates that Rocto failed to retrieve the column value from the row. PSQL Error Code: XX000
ERR_ROCTO_COMMAND_TAG¶
Text: Failed to identify command tag
Description/Action: This error indicates that Rocto failed to identify the command tag. PSQL Error Code: XX000
ERR_ROCTO_DB_LOOKUP¶
Text: xxx: failed to retrieve xxx from database
Description/Action: This error is generated when Rocto has failed to retrieve the data from the database. PSQL Error Code: XX000
ERR_ROCTO_HASH_CONVERSION¶
Text: xxx: failed convert xxx hash to xxx
Description/Action: This error is generated when Rocto has failed to perform hash conversion. PSQL Error Code: XX000
ERR_ROCTO_INVALID_INT_VALUE¶
Text: xxx: invalid xxx value xxx: must be xxx
Description/Action: This error indicates that Rocto received an invalid integer value in a PostgreSQL wire protocol message. PSQL Error Code: 22003
ERR_ROCTO_INVALID_ITEM_VALUE¶
Text: xxx: invalid item value xxx: must be xxx
Description/Action: This error indicates that Rocto received an invalid value for the 'item' field of a message of the specified PostgreSQL wire protocol message type. PSQL Error Code: 22000
ERR_ROCTO_INVALID_MESSAGE_TYPE¶
Text: xxx: invalid type 'xxx': must be 'xxx'
Description/Action: This error indicates that an invalid PostgreSQL wire protocol message type was used. PSQL Error Code: 08P01
ERR_ROCTO_INVALID_NUMBER_BIND_PARAMETERS¶
Text: xxx: invalid number of parameters: expected xxx got xxx
Description/Action: This error indicates that an invalid number of parameters have been provided for a Bind message. PSQL Error Code: 22003
ERR_ROCTO_INVALID_NUMBER_COLUMN_FORMAT_CODES¶
Text: xxx: invalid number of column format codes specified for portal xxx: expected xxx got xxx)
Description/Action: This error occurs when a client requests a different number of output column formats than the number of columns to be returned. PSQL Error Code: 22P02
ERR_ROCTO_INVALID_FORMAT_CODE¶
Text: Bind: invalid xxx format code xxx: must be zero (text) or one (binary)
Description/Action: This error indicates multiple invalid integer values were provided via a PostgreSQL wire protocol message. PSQL Error Code: 22003
ERR_ROCTO_INVALID_VERSION¶
Text: xxx: invalid version xxx: must be xxx
Description/Action: This error indicates an invalid version has been given as input. PSQL Error Code: 08P01
ERR_ROCTO_MISSING_DATA¶
Text: xxx: missing xxx
Description/Action: This error indicates that there is missing data. PSQL Error Code: 22000
ERR_ROCTO_MISSING_NULL¶
Text: xxx: xxx missing null terminator
Description/Action: This error indicates that a value within a wire protocol message sent by a remote client is missing a null terminator. PSQL Error Code: 22024
ERR_ROCTO_MISSING_USERNAME¶
Text: xxx: startup message missing username
Description/Action: This error indicates that a client attempted to initiate remote connection without specifying a username. PSQL Error Code: 08P01
ERR_ROCTO_NONEXISTENT_KEY¶
Text: handle_cancel_request: received non-existent secret key
Description/Action: This error is generated when there is an invalid authorization specification or a non-existent secret key. PSQL Error Code: 28000
ERR_ROCTO_NO_SCHEMA¶
Text: Rocto is not allowed to make schema changes without startup flag –allowschemachanges
Description/Action: This error indicates that Rocto is not allowed to make schema changes without the startup flag set to
--allowschemachanges
. PSQL Error Code: XX000
ERR_ROCTO_NOSCHEMA_USER¶
Text: Cannot modify schema: user 'xxx' not allowed to change schema
Description/Action: This error indicates that a user attempted to change a schema using
CREATE
orDROP
, but lacks permission to do so. To give a user permission to modify schemas, recreate the user usingydboctoAdmin
with the--allowschemachanges
option. PSQL Error Code: 42601
ERR_ROCTO_PARAMETER_COUNT¶
Text: Failed to count number of parameters in prepared statement
Description/Action: This error indicates that Rocto failed to count the number of parameters provided in the prepared statement. PSQL Error Code: XX000
ERR_ROCTO_PASSWORD_TYPE¶
Text: xxx: expected xxx encrypted password
Description/Action: This error indicates that Rocto received a password encrypted in an unexpected format. PSQL Error Code: 28000
ERR_ROCTO_PERMISSIONS_LOOKUP_FAILED¶
Text: Server failed to lookup user permissions. Valid permissions not defined for user 'xxx'
Description/Action: Indicates that a rocto server was unable to determine access permissions for the user indicated. This may occur because the user does not exist, or because permissions were not defined for that user. Accordingly, the user should be created and/or permissions set for that user. PSQL Error Code: 28000
ERR_ROCTO_QUERY_CANCELED¶
Text: canceling statement due to user request
Description/Action: This error indicates a query was successfully cancelled via a CancelRequest message. PSQL Error Code: 57014
ERR_ROCTO_QUERY_TOO_LONG¶
Text: Query length xxx exceeded maximum size (xxx)
Description/Action: This error indicates that the query length exceeded maximum size. PSQL Error Code: 08P01
ERR_ROCTO_READ_FAILED¶
Text: read failure: xxx
Description/Action: This error is generated when Rocto fails to read data from a remote connection. PSQL Error Code: 08000
ERR_ROCTO_READONLY_MODE¶
Text: Cannot modify table: rocto started in read-only mode
Description/Action: This error is generated when a user attempts to modify a table using an INSERT, UPDATE, or DELETE statement, but Rocto was not started with the
--readwrite
option. PSQL Error Code: 42601
ERR_ROCTO_READONLY_USER¶
Text: Cannot modify table: user 'xxx' has read-only permissions
Description/Action: This error is generated when a user attempts to modify a table using an INSERT, UPDATE, or DELETE statement, but does not have "readwrite" permissions. To give a user these permissions, recreate the user using
ydboctoAdmin
with the--readwrite
option. PSQL Error Code: 42601
ERR_ROCTO_READ_TOO_LARGE¶
Text: Read size xxx greater than buffer size xxx
Description/Action: This error indicates that a PostgreSQL wire protocol message exceeded the maximum size of messages which can be read by Rocto. Please contact your YottaDB support channel. PSQL Error Code: 22000
INFO_ROCTO_PARAMETER_DESCRIPTION_SENT¶
Text: sent ParameterDescription for prepared statement 'xxx'
Description/Action: This message indicates that a Rocto ParameterDescription message has been sent for a prepared statement. PSQL Error Code: 00000
INFO_ROCTO_PARAMETER_STATUS_SENT¶
Text: sent ParameterStatus with parameter 'xxx' set to 'xxx'
Description/Action: This message indicates that Rocto recorded the value of a database parameter set by a SET statement, and has notified the client using a ParameterStatus message as part of the PostgreSQL wire protocol startup procedure. PSQL Error Code: 00000
INFO_ROCTO_ROW_DESCRIPTION_SENT¶
Text: sent RowDescription for xxx: 'xxx'
Description/Action: This message indicates that a Rocto RowDescription message has been sent. PSQL Error Code: 00000
INFO_ROCTO_SERVER_FORKED¶
Text: rocto server process forked with pid xxx
Description/Action: This message is generated to show the Rocto server fork that is running, along with its PID. PSQL Error Code: 00000
INFO_ROCTO_STARTED¶
Text: rocto started on port xxx
Description/Action: This message indicates a successful start of Rocto on the given port. PSQL Error Code: 00000
ERR_ROCTO_SECRET_KEY_MISMATCH¶
Text: handle_cancel_request: secret key/PID pair doesn't match stored value
Description/Action: This error indicates that the secret key/PID pair doesn't match that of the client sending a CancelRequest. PSQL Error Code: 28000
ERR_ROCTO_SEND_FAILED¶
Text: failed to send message of type 'xxx'
Description/Action: This error indicates that Rocto failed to send a message of a specific type to a remote client. PSQL Error Code: 08000
ERR_ROCTO_SESSION_LOOKUP¶
Text: xxx: failed to retrieve xxx from session info
This error indicates that Rocto has failed to retrieve the relevant session data for a given client. PSQL Code: XX000
ERR_ROCTO_TLS_ACCEPT¶
Text: ydb_tls_accept: xxx
Description/Action: This error indicates that there is an issue with TLS acceptance. PSQL Error Code: XX000
ERR_ROCTO_TLS_CONNECTION¶
Text: ydb_tls_get_conn_info: xxx
Description/Action: This error indicates that there is an issue with the TLS connection process. PSQL Error Code: XX000
ERR_ROCTO_TLS_INIT¶
Text: ydb_tls_init: xxx
Description/Action: This error indicates that there is an issue with TLS initialization. PSQL Error Code: XX000
ERR_ROCTO_TLS_READ_FAILED¶
Text: ydbcrypt: read failed: xxx
Description/Action: This error indicates that an attempt to read from a TLS socket has failed. PSQL Error Code: XX000
ERR_ROCTO_TLS_REQUIRED¶
Text: Server requires all connections to be TLS encrypted. Please re-connect using a client with TLS/SSL enabled.
Description/Action: This error indicates that the server requires all network connections to use TLS encryption, but the client attempted to initiate an unencrypted connection. PSQL Error Code: 08P01
ERR_ROCTO_TLS_SOCKET¶
Text: ydb_tls_socket: xxx
Description/Action: This error indicates that there is an issue with the TLS socket. PSQL Error Code: XX000
ERR_ROCTO_TLS_UNKNOWN¶
Text: ydbcrypt: unknown error: xxx
Description/Action: This error indicates that an unknown TLS error has taken place. PSQL Error Code: XX000
ERR_ROCTO_TLS_UNNAMED¶
Text: Unnamed failure in ydb_tls_accept: xxx (tls_errno: xxx)
Description/Action: This error indicates that an unnamed TLS error has occurred in the TLS initialization process (accepting a new connection). PSQL Error Code: XX000
ERR_ROCTO_TLS_WANT_READ¶
Text: ydbcrypt: unprocessed read data
Description/Action: This error indicates that there is data remaining to be read from a TLS socket. PSQL Error Code: XX000
ERR_ROCTO_TLS_WANT_WRITE¶
Text: ydbcrypt: unprocessed write data
Description/Action: This error indicates that there is data remaining to be written to a TLS socket. PSQL Error Code: XX000
ERR_ROCTO_TLS_WRITE_FAILED¶
Text: ydbcrypt: write failed: xxx
Description/Action: This error indicates that an attempt to write to a TLS socket has failed. PSQL Error Code: XX000
ERR_ROCTO_TOO_FEW_VALUES¶
Text: xxx: too few xxx
Description/Action: This error indicates that a PostgreSQL wire protocol message is missing one or more fields. PSQL Error Code: 22003
ERR_ROCTO_TOO_MANY_VALUES¶
Text: xxx: too many xxx
Description/Action: This error indicates that a PostgreSQL wire protocol message was submitted with too many fields. PSQL Error Code: 22003
ERR_ROCTO_TRAILING_CHARS¶
Text: xxx: message has trailing characters
Description/Action: The error indicates that a PostgreSQL wire protocol message has trailing characters. PSQL Error Code: 08P01
ERR_ROCTO_UNSUPPORTED_BIND_PARAMETER¶
Text: Unsupported bind parameter type received
Description/Action: This error indicates that Rocto has received a request to bind a value of an unsupported data type to a prepared statement. PSQL Error Code: XX000
ERR_ROCTO_USER_LOOKUP¶
Text: xxx: failed to retrieve xxx for user xxx from database
Description/Action: This error indicates that a client has attempted to log in to Rocto as a non-existent user. PSQL Error Code: 28000
PostgreSQL Error Codes Used¶
Octo uses a few PostgreSQL Error Codes.
List of PostgreSQL error codes defined and used in Octo:
Error Code
Condition Name
Class 00 — Successful Completion
00000
successful_completion
Class 08 — Connection Exception
08P01
protocol_violation
Class 26 — Invalid SQL Statement Name
26000
invalid_sql_statement_name
Class 42 — Syntax Error or Access Rule Violation
42601
syntax_error