| Causes | Symptoms | Countermeasures | ||
| Category 1 | Category 2 | |||
| Failure due to a descriptive error common in the TQL descriptions | If the specified column does not exist | [Error code]: 150012 [Description] (Column cannot be found) [Format] Error description below Column cannot be found Column ID cannot be found |
Check the error message and then check the column name and column ID | |
| Failure in interpretation of TQL | [Error code]: 151001 [Description] (Syntax error) |
Syntax error occurred. Check the TQL syntax. See “TQL syntax and operation functions” in “API reference” for details on the TQL syntax. | ||
| [Error code]: 151002 [Description] (Token is invalid) |
Invalid key word is detected. Check the TQL syntax. See “TQL syntax and operation functions” in “API reference” for details on the TQL syntax. | |||
| [Error code]: 151003 [Description] (Not enclosed by double quotation marks) [Format] Error description below Cannot dequote |
Double quotation mark is invalid. Check the TQL syntax. See “TQL syntax and operation functions” in “API reference” for details on the TQL syntax. | |||
| If data does not exist | [Error code]: 152009 [Description] (Array index is out of range) [Format] Error description below Index specified in the array is out of range |
Array index is invalid. Check the TQL syntax. See “Data type” in “API reference” for details on the array (complex type). | ||
Failure due to descriptive error of FROM section |
If the container name is incorrect | [Error code]: 150010 [Description] (Container name is invalid) [Format] Error description below Container name given by the API is not the same as the FROM section |
Specified container does not exist. Check the container name. | |
| Failure due to descriptive error of WHERE section | If there is a constraint violation resulting in failure in interpretation TQL | [Error code]: 150013 [Description] (* is used in the WHERE condition) [Format] Error description below * cannot be used in the WHERE condition |
* cannot be used in the WHERE condition. Check the TQL syntax. See “TQL syntax and operation functions” in “API reference” for details on the TQL syntax. | |
| If a division by 0 is attempted | [Error code]: 150016 [Description] (Division by 0) [Format] Error description below Division by 0 |
Division by 0 is not possible. Check the TQL syntax. | ||
| If there is a data type constraint violation | [Error code]: 150018 [Description] (Binary process is not supported) [Format] Error description below Binary operation is not defined |
Fellow binary operations with the specified data type cannot be executed. Review the TQL syntax. | ||
| [Error code]: 150019 [Description] (Constraint violation in column condition search) [Format] Error description below Column used in the WHERE condition is not a Boolean data type |
If a column is used individually in the WHERE condition, the column data type needs to be Boolean. Review the TQL syntax. | |||
| [Error code]: 152010 [Description] (Constraint violation in spatial search) [Format] Error description below The column specified in the spatial range condition is not a spatial data type |
Use a spatial data type column to specify the condition in searching the spatial range. Check the TQL syntax. | |||
| Failure due to descriptive error of the ORDER BY section | Failure caused by the alignment method expression | [Error code]: 151004 [Description] (Constraint violation of alignment method in ORDER BY section) [Format] Error description below Only column names are permitted in the ORDER BY section |
Check the alignment method specified in the ORDER BY section. See “Sorting of search results (ORDER BY)” under “TQL syntax and operation functions” in the “API references” for the ORDER BY section. | |
| Failure that violates operating conditions | [Error code]: 151005 [Description] (Constraint violation of operating conditions in ORDER BY section) [Format] Error description below Consolidation function and ORDER BY are being used simultaneously |
Consolidation function and ORDER BY cannot be used simultaneously. Check the TQL syntax. See “Sorting of search results (ORDER BY)” under “TQL syntax and operation functions” in the “API references” for the ORDER BY section. | ||
| Failure due to descriptive error of the function | Failure caused by function name | [Error code]: 150014 [Description] (Function cannot be found) [Format] Error description below No such function |
Check the function name. See “TQL syntax and operation functions” in “API reference” for details on the TQL syntax. | |
| If the operating conditions of the function are violated | [Error code]: 152003/152004 [Description] (Unauthorized use of special function for collection/time series containers) [Format] Error description below Selection function for collection was used on a time series container Selection function for time series container was used on a collection Consolidation function for time series container was used on a collection |
Check whether a special function for time series containers has been used on a collection. Or, check whether a special function for collections has been used on a time series container. See “TQL syntax and operation functions” in “API reference” for details on the TQL syntax. | ||
| Failure caused by the number of arguments | [Error code]: 152002/152007/152011 [Description] (Number of arguments is invalid) [Format] Error description below Number of arguments in function is invalid Argument expected to be empty is not empty in the function |
Check the argument of the function. See “TQL syntax and operation functions” in “API reference” for details on the TQL syntax. | ||
| Failure caused by the data type of the argument | [Error code]: 152002/152007/152010/152020 [Description] (Data type of argument is invalid) [Format] Error description below Data type of argument in function is invalid Interpolation target is not a column Interpolation was attempted on a column which is not a numerical value An argument which is not a column has been used |
Check the data type given in the argument of the function. See “TQL syntax and operation functions” in “API reference” for details on the TQL syntax. | ||
| Failure caused by argument value | [Error code]: 150005/152010/152012 [Description] (Value of argument is invalid) [Format] Error description below Data outside the time range has been used Coordinate value is invalid Escape text is not a single character A natural number was expected but a value less than 0 was used String cannot be converted to time format |
Data given in argument of function is incorrect. See “TQL syntax and operation functions” in “API reference” for details on the TQL syntax. | ||
| Failure due to descriptive error of the spatial data | Failure caused by the number of arguments | [Error code]: 152007/152010 [Description] (Number of arguments is invalid) [Format] Error description below Argument is required but space is blank Attempt to create a line with a single point |
Check the argument of the spatial data expression. See “TQL syntax and operation functions” in “API reference” for details on the TQL syntax. | |
| Failure caused by the data type of the argument | [Error code]: 152010 [Description] (Data type of argument is invalid) [Format] Error description below Data type of argument is invalid |
Check the type of argument of the spatial data expression. See “TQL syntax and operation functions” in “API reference” for details on the TQL syntax. | ||
| Failure to execute TQL | If memory could not be secured | [Error code]: 1001 [Description] (Error in securing memory) [Format] Error description below Memory of TQL parser cannot be secured Memory of WKT parser cannot be secured |
When raising the upper limit of the usable memory size, add /dataStore/resultSetMemoryLimit or /transaction/totalMemoryLimit to the gs_node.json file, and make the value larger than the default value (*1). If the memory size is exceeded during a search, the query can also be adjusted by restricting the number of hits so that the memory capacity used is reduced. |
|
| (*1) | ||||
| /dataStore/resultSetMemoryLimit in gs_node.json file: memory upper limit size of search result (ResultSet). Default value is 10240 MB. Unit is MB by default | ||||
| /transaction/totalMemoryLimit in gs_node.json file: upper limit size of the empty memory maintained by the transaction process memory pool. Default value is 1024 MB. Unit is MB by default | ||||
| In future, this parameter may be deleted or its name may be changed. | ||||