SQL Messages 200-399
Message Code | Message Description |
---|---|
200 |
The query has invalid syntax near the keyword <<keyword>>. |
201 |
The <<function>> function cannot be used with the <<argument>> argument. |
202 |
The <<column name or data object name>> name is a keyword. Enclose table or column names that are keywords with double quotes. |
203 |
The '<<arithmetic operator>>' operator cannot be used with data types: <<data type1>>, <<data type2>>. |
204 |
The numeric result for <<result set column or alias>> is out of range and caused a decimal overflow error. |
205 |
The parameter <<parameter>> is invalid for the lastmodified function. The lastmodified function parameter must be a data object or alias referenced in the query. |
206 |
Division by 0 error encountered. |
207 |
The <<function>> function cannot be used with an argument. |
208 |
The <<function>> function requires <<number of arguments>> arguments. |
209 |
The left side of the <<expression>> expression requires a <<data type>> data type value. |
210 |
The rank function must have an 'over' clause. |
211 |
Operand data type <<datatype parameter>> is invalid for the <<function parameter>> function. |
212 |
The <<function>> function cannot be used in the WHERE clause of the query. |
213 |
The <<function>> function cannot convert data type <<data type>> to <<result data type>>. The query and the result data types must be the same. |
214 |
Unsupported datetime style number. |
215 |
UNION, INTERSECT, MINUS, EXCEPT operations must have the same number of expressions in each query. |
216 |
Each query combined in the UNION ALL operator must have the same column data types in their target lists. The query cannot combine <<first property data type>>and <<second property data type>> types for properties '<<first property>>' and '<<second property>>'. |
217 |
The locale function number of locale columns of <<expression>> is invalid. The number of locale columns must be an integer between 1 and 32. |
218 |
The <<property name>>, <<property name>> property name is ambiguous. |
219 |
The <<argument>> argument value, <<argument value>>, is invalid for the <<function>> function. |
220 |
The correlated subquery syntax is unsupported. Ensure that the properties selected in the main query are selected in the subqueries. |
221 |
The <<stored procedure name>> stored procedure is not supported. |
222 |
The value <<value>> is not a valid <<type>>. |
223 |
The <<query reference>> reference must be an aggregate expression or appear in the group by clause. |
224 |
The query results in a decimal overflow error. Please rewrite the query and check any numeric expressions or functions. |
225 |
The <<stored procedure>> stored procedure requires string arguments. Enclose the arguments used in the <<stored procedure>> stored procedure with single quotes. |
226 |
The show_value function syntax is show_value(property name, format type) requires a property reference and a string argument for the format type of 'general' or 'original'. |
227 |
The hint syntax is invalid. The syntax for the <<hint>> hint is <<hint>>= followed by one or more object names or aliases used in the query. Separate multiple object names or aliases with a / character. |
228 |
The <<hint>> hint object or alias references are invalid: <<object or alias>>, <<object or alias>>, <<object or alias>>. The <<hint>> hint requires object names or aliases referenced in the query. |
229 |
The properties referenced in the group by clause are incorrect or invalid: {property_name}. |
230 |
<<type value>> is not a defined type. |
231 |
The <<function name>> functionality is not supported. |
232 |
The query syntax is incorrect or invalid. |
233 |
Select * in common table expression with aliases is not supported. |
234 |
The hint could not be parsed. |
235 |
Function <<function>> is not supported. |
236 |
Aggregation or window function <<function>> cannot be used in group by clause. |
237 |
<<code>> is not a valid Unicode code. |
238 |
The value <<value>> cannot be cast to data type <<data type>> |
239 |
The date part <<data part>> used in <<date function>> function is invalid. |
240 |
The scalar subquery has returned multiple rows. Update the subquery to return only one row. |
241 |
All arguments in the <<function name>> function must have the same data type. The function cannot combine <<first property data type>>and <<second property data type>> types for properties '<<first property>>' and '<<second property>>'. |
242 |
One or more of the 'order by' expressions are invalid for a select distinct. The order by expressions must be included in the select clause. |
243 |
The {statement} statement is limited to one data object reference. The statement contains references to {tables} data objects. |
244 |
The query is invalid. The query result must have at least one column. |
245 |
The {statement} statement must contain a where clause. Use a where clause to specify the records to {statement}. |
246 |
The <<propertyname>> property name is ambiguous. Use aliases when one or more properties in the query exists in multiple data objects. |
247 |
The properties referenced in the update statement set clause are Infor properties and cannot be updated. Invalid property references: '<<property1>>', '<<property2>>'. |
248 |
The properties referenced in the update statement set clause are invalid. The update statement does not support the update of localized string properties. Localized string property references: <<property1>>,<<property2>>. |
249 |
The <<value>> value is invalid for the <<function>> function |
250 |
The aggregation or window function is not supported for ALL, SOME or ANY operators. |
251 |
The <<function>> function is not supported for a view, an inline view, or a common table expression. |
252 |
The recursive common table expression syntax is not supported. |
253 |
The delete statement must contain a where clause. Use a where clause to specify the records to delete. |
254 |
Compass query syntax for variation logic is invalid. Either use variation hints or variation table functions. |
255 |
The value <<value>> is out of range for the <<type>> data type and size. |
256 |
The <<table function>> table function is not supported. |
257 |
The first argument <<first parameter>> in the to_date function is invalid. The first argument must be a valid date in string format. |
258 |
Permission cannot be granted for: {permission}. |
259 |
{role} is too long. |
260 |
The {permission} permission is invalid. Supported are {supported_permissions}. |
261 |
The third argument <<third parameter>> for the infor.locale function is invalid. The third argument is optional. If used, the valid value is 'autofill'. |
262 |
The arguments in the to_date function are invalid. The first and second arguments must be strings of valid date formats. |
263 |
The <<function>> aggregation or window function is invalid in the join clause of the query. |
264 |
At least one of the arguments to {function} must be an expression that is not the NULL constant. |
265 |
The <<clause>> clause cannot be used with the <<statement type>> statement. |
266 |
The parameter '<<parameter>>' is invalid for the '<<function>>' function. The <<function>> function parameter must be a data object or alias referenced in the query. |
267 |
The {viewname} view reference is prohibited in the {statement} statement. The statement must reference an object. |
268 |
View references are prohibited in the variation handling hint or table function. The {viewname} view is not supported with this functionality |
269 |
The {viewname} view cannot be used with the {procedure} stored procedure. The stored procedure must reference an object. |
270 |
The value <<parameter>> is invalid as the first parameter for the infor.locale function. The first parameter must be a property reference. |
271 |
The number of arguments for the <<function>> function is invalid. The function arguments are the string property, number of locale values and an optional 'autofill' value. |
272 |
Wrong number of provided JDBC parameter values |
273 |
The <<function name>> function requires a minimum of <<number of arguments>> arguments. |
274 |
Unexpected parameters in the <<function>> function. All parameters must be of the same data type. |
275 |
The <<objectname>> object name is ambiguous in the from clause of the query. Use aliases to specify distinct names. |
276 |
The table <<table>> cannot be migrated as it is not active. |
277 |
Active configuration is same as Target configuration. |
278 |
Tables have wrong status for {procedure} procedure. Required status: {requiredStatus}. Actual status: {actualStatus}. |
279 |
An unsupported character is used in the second argument of the <<function name>> function. Special characters must be escaped with a \ character. |
280 |
Location specification {property} value {value} is invalid. |
281 |
Invalid trim character specified: {trimCharacter}. Trim character must be a single character |
282 |
The <<viewname>> view name is invalid. Letters A-Z in upper and lowercase, digits 0-9, and underscores are supported. |
283 |
The <<viewname>> view name is invalid. The <<reserved word>> prefix is invalid |
284 |
The <<viewname>> view name is invalid. The view name limit is 100 characters. |
285 |
The <<viewname>> view cannot be created. The name is a duplicate of an existing view or object. |
286 |
The <<viewname>> view name has not been created. View must be created before it can be altered. |
287 |
The <<viewname>> references other views. A view can only reference objects. |
288 |
The <<viewname>> view cannot be created. The <<column name or alias>> column name is invalid. The column name or alias cannot exceed 100 characters. |
289 |
The <<viewname>> view cannot be created. The <<column name or alias>> column name is invalid. The column name is a duplicate of a specified column name. |
290 |
The <<viewname>> view cannot be created. The <<column name or alias>> column name or alias uses characters that are not supported. Letters A-Z in upper and lowercase, digits 0-9, and underscores are supported. |
291 |
The <<view name>> view is invalid. Views can only be created over the "default" schema. |
292 |
Statements that attempt to query or create views over the Data Lake cannot reference more than 100 tables. |
293 |
The <<hint>> hint is not supported with Views. |
294 |
The object or view does not exist. |
295 |
The query has exceeded character limits and cannot be processed. Reduce the length of the query and please try again. |
296 |
Query failed. The <<value>> value exceeds the decimal size in Compass. The maximum size of a decimal in Compass is decimal(38,15). |
297 |
Wrong number of column aliases in CTE table |
298 |
The <<cteName>> name is a duplicate of another CTE in the query. |
299 |
Wrong CTE column alias type. |
300 |
The column <<column name>> is a duplicate within the WITH item list of CTE <<cte name>>. |
301 |
A CTE column alias contains special character(s). Enclose CTE column aliases with special characters in double quotes. |