Explanation | An aggregation operation (for example SUM, AVG, and so on) appears in the mapping metadata. This is not currently supported by the query engine for the enterprise Java bean (EJB). |
Action | This indicates an internal error in the Application Server or the WSAD deployment tooling. Refer to the IBM support web site for information on problem determination. |
Explanation | An error occurred executing an SQL statement. The message text indicates the SQL statement that failed. This message only applies to the WebSphere dynamic query service. |
Action | Verify that the SQL statement that is failing is valid for the target database. If the database schema is inconsistent with the schema used during deployment, or the database schema has changed, it might be necessary to redeploy the application. Otherwise, refer to the IBM support web site for information on problem determination. |
Explanation | A syntax error was detected in the mapping metadata generated by the WebSphere deployment tool. This error is in the view implementation or the inheritance typecode predicates. |
Action | This indicates an internal error in the Application Server or the WSAD deployment tooling. Refer to the IBM support web site for information on problem determination. |
Explanation | An error occurred parsing the query for the enterprise Java bean (EJB), indicated in the message text. |
Action | Verify the query statement for the EJB. If the statement is valid, refer to the IBM support web site for information on problem determination. |
Explanation | A mathematical error occurred executing a query scalar function for an enterprise Java bean (EJB). The message text indicates the name of the scalar function. |
Action | Correct the query statement for the enterprise Java bean (EJB), or update the container-managed persistence (CMP) field values to avoid the overflow problem. |
Explanation | A subquery that is used in a SELECT clause cannot contain a subquery in its own SELECT clause. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The identification variable is used in a subquery and references another identification variable, indicated in the message text, in a manner that is not supported. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The LIKE predicate takes a single escape character. The string specified in the message text is greater than one character in length and is not valid. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The Abstract Schema Name (ASN) that is specified in the FROM clause of the query is not defined in any of the installed applications. |
Action | Make sure that the ASN name is correct, or install the application that has the ASN name and submit the query again. |
Explanation | The Abstract Schema Name (ASN) that is specified in the FROM clause of the query is defined in more than one installed applications. |
Action | Provide EJBHome or EJBLocalHome to uniquely identify the ASN name and resubmit the query. Follow the sample client code for the usage of EJBHome or EJBLocalHome. |
Explanation | The query expression indicated by the token {0} attempts to compare two expressions that are not compatible in type. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The aggregate function (for example SUM, COUNT, and so on) indicated by the message text is not used correctly (such as being used in a WHERE clause), or the function contains an argument that is not valid (an expression that contains correlated and noncorrelated values). |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | You cannot use the "equal or not equal" predicate to compare two enterprise Java beans (EJBs) that cannot be compared. Only EJBs that are of compatible types and from the same home can be compared. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | A mathematical error occurred computing the value of an AVG or SUM function. |
Action | Correct the query statement for the enterprise Java bean (EJB) or the values for the container-manager persistence (CMP) field. |
Explanation | The identification variable specified is defined over an not valid association because the schema of the association contains no persistent fields. |
Action | Check the query statement for the enterprise Java bean (EJB), or check the application model. |
Explanation | The query statement for the enterprise Java bean (EJB) does not support casting a container-managed persistence (CMP) field or a container-managed relationship (CMR) field to another type. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The query statement for the enterprise Java bean (EJB) does not support casting a container-managed persistence (CMP) field or a container-managed relationship (CMR) field to another type. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | An identification variable must be defined as an Abstract Schema Name (ASN) or as a multivalued path expression. The identification variable that is indicated is defined with the path expression that is indicated in the message text, which ends in a single valued relationship name. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The mapping metadata for the field that is indicated by the message text cannot be accessed. |
Action | This indicates an internal error in the Application Server or in the WSAD deployment tooling. Refer to the IBM support web site for information on problem determination. |
Explanation | A field must always be used in the context of a path expression that begins with an identification variable. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The query statement for the enterprise Java bean (EJB) does not support casting a container-managed persistence (CMP) field or container-managed relationship (CMR) field to another type. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The query statement for the enterprise Java bean (EJB) does not support casting a container-managed persistence (CMP) field or container-managed relationship (CMR) field to another type. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | This is an internal error. |
Action | This indicates an internal error either in the Application Server or the WSAD deployment tooling. Refer to the IBM support web site for information on problem determination. |
Explanation | When performing a grouping operation, elements of the SELECT clause must either be aggregation functions or grouping elements. The container-managed persistence (CMP) field that is indicated by the token {0} is used in the SELECT clause and does not appear in an aggregation function, but the CMP field is not a grouping element. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The ORDER BY clause of a query statement refers to a select element by an ordinal number that is indicated in the message text, but no such element exists. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The Abstract Schema Name (ASN) that is indicated in the message text is not defined. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | Zero and negative numbers are not valid in the ORDER BY clause. Use the DESC keyword to sort in descending order. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The Application Server made an attempt to navigate past the container-managed persistence (CMP) or container-managed relationship (CMR) field that is indicated by token {1} in the path expression that is indicated by the token {0}. A path expression can only navigate through a single-valued CMR field. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The Application Server made an attempt to navigate past the container-managed persistence (CMP) or container-managed relationship (CMR) field that is indicated by token {1} in a path expression. A path expression can only navigate through a single-valued CMR field. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | An overflow occurred while computing the AVG aggregate function. |
Action | Correct the query statement for the enterprise Java bean (EJB) to avoid the overflow. |
Explanation | An overflow occurred while computing the COUNT aggregate function. |
Action | Correct the query statement for the enterprise Java bean (EJB) to avoid the overflow. |
Explanation | Backend data store cannot compare columns which are greater than 254 bytes or binary data. |
Action | Correct the query statement or the mapping for the enterprise Java bean (EJB). |
Explanation | A number or a path expression appears more than once in the ORDER BY clause. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | A path expression appears more than once in the GROUP BY clause. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | Do not use DISTINCT more than once in aggregate functions in a query. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | A DISTINCT operation appears in the mapping metadata. This is not currently supported by the query engine for the enterprise Java bean (EJB). |
Action | This indicates an internal error in the Application Server or the WSAD deployment tooling. Refer to the IBM support Web site for information on problem determination. |
Explanation | A container-managed persistence (CMP) field or a container-managed relationship (CMR) field with the given name was used in a query statement. The bean with the Abstract Schema Name (ASN) and the identification variable does not define this field. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The method with the given name was used in a query statement. The bean with the Abstract Schema Name (ASN) and the identification variable does not define this method. The use of methods in query statements is only supported in WebSphere Extended Edition. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The division operator can only be used on numeric types. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | An internal error occurred in the server at run time. |
Action | This error indicates an internal error in the Application Server. Refer to the IBM support Web site for information on problem determination. |
Explanation | The EMPTY, EXISTS, IN, ALL, ANY and SOME scalar functions can only be applied to container-managed relationship (CMR) fields and to subqueries. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | An unknown exception occurred during the query evalution. If the query statement calls user-defined methods, verify that the method is not throwing an exception. Otherwise, this is an internal error. |
Action | If you are unable to resolve problem, refer to the IBM support Web site for information on problem determination. |
Explanation | The only method overloading that Query allows is for a method to have different numbers of parameters. |
Action | Correct the programming model for the enterprise Java bean (EJB). |
Explanation | The "greater than or equal" operator can only be used with numeric, string, date-time or calendar types. The token {0} contains the expression that is not correct. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The "greater than" operator can only be used with numeric, string, date-time or calendar types. The token {0} contains the expression that is not correct. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | An illegal character was used in the query statement for an enterprise Java bean (EJB). The "Syntax error" message that follows the "Illegal Character" error message shows the location and the type of the illegal character. |
Action | Check the query statment for the EJB for characters that are not valid. |
Explanation | A syntax error was detected in the mapping metadata that was generated by the WebSphere deployment tool. The token {0} indicates the typecode predicates and the token {1} is the Abstract Schema Name (ASN) for the EJBHome statement that is failing. |
Action | This error indicates an internal error in the Application Server or the WSAD deployment tooling. Refer to the IBM support Web site for information on problem determination. |
Explanation | A path expresssion cannot navigate through a multi-valued contianer-managed relationship (CMR) field. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | When a query for an enterprise Java bean (EJB) is used to define FINDER or SELECT methods, the SELECT clause must contain a single element that refers to an EJB or a single-path expression that specifies a container-managed persistence (CMP) field or a single-valued container-managed relationship (CMR) field. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | An inquality operator is used with a data type that is not compatible. The message text contains the expression that is not correct. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | IS NULL and IS NOT NULL must be used in path expresssions with container-managed persistence (CMP) fields or single-valued container-managed relationship (CMR) fields. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The "less than or equal" operator is used with a data type that is not compatible. The message text contains the expression that is not correct. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The "less than or equal" operator is used with a data type that is not compatible. The message text contains the expression that is not correct. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The MAX function is used with a data type that is not compatible. The message text contains the expression that is not correct. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The method in the query statement for the enterprise Java bean (EJB) differs in number or the type of argument from all the methods with the same name that are in the programming model for the EJB. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The MINUS operator is used with a data type that is not compatible. The message text contains the expression that is not correct. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The MIN function is used with a data type that is not compatible. The message text contains the expression that is not correct. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | This error indicates an internal error in the Application Server or the WSAD deployment tooling. |
Action | Refer to the IBM support Web site for information on problem determination. |
Explanation | Using the MEMBER OF predicate to compare an entity bean to a collection-valued container-managed relationship (CMR) field is not a valid operation, because the entity beans are not comparable or belong to different homes. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | There can be a maximum of 100 select statements in the final query generated by an query statement for the enterprise Java bean (EJB). |
Action | Reduce the size and the number of SELECT operations in the query statement for the enterprise Java bean (EJB). |
Explanation | A maximum of 512 quantifiers can be used in the query plan that is generated by the query statement for the enterprise Java bean (EJB). |
Action | Reduce the complexity of the query statement for the EJB. |
Explanation | An aggregate function such as SUM cannot contain another aggregate function in the argument expression. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The collection aggregate operation NEST is used with an incorrect type. |
Action | This error indicates an internal error in the Application Server or the WSAD deployment tooling. Refer to the IBM support Web site for information on problem determination. |
Explanation | The parameter that is indicated in the message text is not defined. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The parameter that is indicated is a container-managed persistence (CMP) field or a container-managed relationship (CMR) field. The message text indicates the schema that is used in the query. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The specified field does not denote a container-managed relationship (CMR) field or a container-managed persistence (CMP) field that is defined by the given schema. |
Action | Check the query statement for the enterprise Java bean (EJB), or check the schema mapping of the application model. |
Explanation | This is an internal metadata error. |
Action | This error indicates an internal error in the Application Server or the WSAD deployment tooling. Refer to the IBM support Web site for information on problem determination. |
Explanation | This is an internal error in the Application Server or the WSAD deployment tooling. |
Action | Refer to the IBM support Web site for information on problem determination. |
Explanation | This is an internal error in the Application Server or the WSAD deployment tooling. |
Action | Refer to the IBM support Web site for information on problem determination. |
Explanation | A function that requires a numeric expression was used incorrectly with an argument expression. The message text shows the function. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | An AVG function that requires a numeric expression was used incorrectly with an argument expression. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | A query iterator is no longer valid, because the Java Database Connectivity (JDBC) cursor is not valid. This is probably due to an end-of-transaction operation. The query iterator cannot be used outside of the originating transaction scope. |
Action | Verify that the program that is running is user a valid programming model. |
Explanation | This error indicates an internal error in the Application Server or the WSAD deployment tooling. |
Action | Refer to the IBM support Web site for information on problem determination. |
Explanation | The number that is specified is out of the legal range for its data type. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | This error indicates an internal error in the Application Server or the WSAD deployment tooling. |
Action | Refer to the IBM support Web site for information on problem determination. |
Explanation | If the ORDER BY clause is used, the element that is being ordered by must appear in the SELECT clause. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | Performing a DISTINCT operation in a query statement for an enterprise Java bean (EJB) that returns object references might produce an ORDER BY on the primary key fields of the EJB. If the query statement contains an ORDER BY clause that is specified by the user, the two ordering schemas might conflict. |
Action | Remove either the ORDER BY or the DISTINCT operation, and retry the query statement for the EJB. |
Explanation | Ordering on java.sql.blob values is not supported. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | Ordering on boolean values is not supported. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | Ordering on java.sql.clob values is not supported. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | Method mapping to back-end data store is not currently supported. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | Ordering is supported only for container-managed persistence (CMP) values that are orderable types, such as numbers, strings and date-time values. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The PLUS operator is used with an data type for which it is not compatible. The message text contains the expression that is incorrect. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The program made an attempt to reference a parameter that is greater than the number of input parameters. The parameters are defined by the signature of the FINDER method or the SELECT method. For a dynamic query on an enterprise Java bean (EJB), the input parameters are passed on the exeucteQuery API. Attempting to use an input parameter whose data type is not supported by WebSphere may also result in this error. |
Action | Correct the query statement for the EJB or the method signature. |
Explanation | When using ORDER BY clause with a UNION operation, the ORDER BY clause must use integer constants to indicate the container-managed persistence (CMP) attributes in the enterprise Java bean (EJB) that is being queried. |
Action | Correct the query statement for the EJB. |
Explanation | You cannot use the same correlation ID to refer to more than one instance of an enterprise Java bean (EJB in the same select clause. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | In a query with a 'LIKE' predicate using the 'ESCAPE' keyword, the double-quote character cannot be used as the escape character for '%' or '_'. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The identification variable that is indicated in the message text is used in a subquery and references another identification variable, which is indicated in the message text, in a manner that is not supported. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | A subquery that is used in a SELECT clause cannot contain a subquery in its own SELECT clause. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | Do not use the 'select *' statement in query statements for enterprise Java beans (EJBs). For example, you cannot use 'select * from XyzBean' to select all of the container-managed persistence (CMP) fields for XyzBean. |
Action | Correct the query statement for the EJB. |
Explanation | In order to use 'e.*' in a subquery, the identification variable 'e' must be defined in the subquery. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The keyword OBJECT is used in the select clause to project the object reference that is associated with an identification variable. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The query statement for the enterprise Java bean (EJB) does not satisfy the syntax diagram that is found in the documentation for EJB queries. |
Action | Correct the query statement for the EJB. |
Explanation | There was an internal error in mapping the metadata. |
Action | This error indicates an internal error in the Application Server or the WSAD deployment tooling. Refer to the IBM support Web site for information on problem determination. |
Explanation | The specified argument cannot be used with the scalar function listed in the message text. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The table schema that is provided does not match the schema that is used to generate the mapping metadata at deployment time. |
Action | Check the table schema and the schema that is used to generate the mapping metadata at deployment time. |
Explanation | When using the IS OF TYPE predicate to test the subtype of enterprise Java beans (EJBs), the subtype(s) that make the operand on the right side of the IS OF TYPE predicate must be defined subtypes of the EJB that is specified by the left side of the operand. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | There was an internal error mapping the metadata. |
Action | This error indicates an internal error in the Application Server or the WSAD deployment tooling. Refer to the IBM support Web site for information on problem determination. |
Explanation | There was an internal error mapping the metadata. |
Action | This error indicates an internal error in the Application Server or the WSAD deployment tooling. Refer to the IBM support Web site for information on problem determination. |
Explanation | The multiply operator is used with an data type that is not compatible. The message text contains the expression that is not correct. |
Action | : Correct the query statement for the enterprise Java bean (EJB). |
Explanation | There was an internal error mapping the metadata. |
Action | This error indicates an internal error in the Application Server or the WSAD deployment tooling. Refer to the IBM support Web site for information on problem determination. |
Explanation | There was an internal error mapping the metadata. |
Action | This error indicates an internal error in the Application Server or the WSAD deployment tooling. Refer to the IBM support Web site for information on problem determination. |
Explanation | A subquery that is used with a basic predicate must only return a single value. Mutliple values were returned at run time when the subquery was evaluated. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | A subselect statement can only return a single value. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The sum of the second and third arguments is greater than the length of the first argument |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | There was an internal error mapping the metadata. |
Action | This error indicates an internal error in the Application Server or the WSAD deployment tooling. Refer to the IBM support Web site for information on problem determination. |
Explanation | There is schema information for the {0} field that is not consistent. |
Action | Correct the query statement for the EJB or check the application model. |
Explanation | The _THIS keyword is a reserved word and cannot be used in an query statement for an enterprise Java bean (EJB). |
Action | Change the schema name in the deployment descriptor or in the table name. |
Explanation | The field is not defined in the abstract schema as either a container-managed persistence (CMP) field or a container-managed relationship (CMR) field. |
Action | Correct the query statement for the enterprise Java bean (EJB). Make sure that every path expression begins with an identification variable. |
Explanation | When performing a UNION operator, the SELECT statements that are operands to the UNION must contain an equal number of elements in the SELECT clauses. |
Action | Correct the EJB query statement. |
Explanation | The identification variable that was found with container-managed persistence (CMP) field or a container-managed relationship (CMR) field does not match the identification variable that is associated with any enterprise Java bean (EJB) that is being queried. |
Action | Correct the query statement for the EJB. |
Explanation | When performing a UNION operator, the SELECT statements that are operands to the UNION must contain elements in the SELECT clauses that are of compatible type. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The correct method signature was not found in the remote or local interface that is being used for the enterprise Java bean (EJB). |
Action | Correct the programming model for the EJB. |
Explanation | There was an internal error mapping the metadata. |
Action | This error indicates an internal error in the Application Server or the WSAD deployment tooling. Refer to the IBM support Web site for information on problem determination. |
Explanation | There was an internal error mapping the metadata. |
Action | This error indicates an internal error in the Application Server or the WSAD deployment tooling. Refer to the IBM support Web site for information on problem determination. |
Explanation | There was an internal error mapping the metadata. |
Action | This error indicates an internal error in the Application Server or the WSAD deployment tooling. Refer to the IBM support Web site for information on problem determination. |
Explanation | There was an internal error mapping the metadata. |
Action | This error indicates an internal error in the Application Server or the WSAD deployment tooling. Refer to the IBM support Web site for information on problem determination. |
Explanation | There was an internal error mapping the metadata. |
Action | This error indicates an internal error in the Application Server or the WSAD deployment tooling. Refer to the IBM support Web site for information on problem determination. |
Explanation | There was an internal error mapping the metadata. |
Action | This error indicates an internal error in the Application Server or the WSAD deployment tooling. Refer to the IBM support Web site for information on problem determination. |
Explanation | The number of arguments that are used in the query statement is not consistent with the definition of the function that is indicated in the message text. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | There was mapping of container-managed relationship (CMR) field to relational table for a database that was not valid. |
Action | Correct the mapping of the CMR field to the relational table. |
Explanation | No mapping exist for the container-managed relationship (CMR) field to the relational database table. |
Action | Create a valid mapping for the CMR field. |
Explanation | The converter class that is used in the application schema cannot be found or instantiated, or the converter class is not a valid. |
Action | Add the converter class in the class path or correct the application schema. |
Explanation | The following error occurred while executing dataFrom method. |
Action | The converter that is specified in the schema needs to extend from the root class of com.ibm.vap.converters.VapAbstractConverter. Correct the implementation of dataFrom method, or correct the query statement for the enterprise Java bean (EJB). |
Explanation | The following error occurred while creating the input argument for dataFrom method. |
Action | Correct the input value according to the converter. |
Explanation | The return type from the dataFrom method is not supported by the query engine. |
Action | Correct the dataFrom method, or use another converter. |
Explanation | Container-managed relationship refers to an enterprise Java bean (EJB) object, and the object reference cannot be used in the GROUP BY clause. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The output type of the dataFrom method is not compatible in the given expression. |
Action | Correct the query statement for the enterprise Java bean (EJB) or the converter. |
Explanation | The SELECT clause cannot contain any container-managed relationship (CMR) fields that are mutli-valued. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | This method mapping to a back-end data store is not supported |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The method in the query statement for the enterprise Java bean (EJB) differs in the number or type of argument from all the methods with the same name in the EJB model. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | Expressions with the type 'void' should not be used in a query statement for an enterprise Java bean (EJB). |
Action | Correct the application schema, or correct the query statement for the EJB. |
Explanation | The Primary key that is specified in the metadata at the table level and the key that is provided at implementation time do not match. |
Action | This error indicates an internal error in the WSAD deployment tooling. Refer to the IBM support Web site for information on problem determination. |
Explanation | The query statement for the enterprise Java bean (EJB) that contains JOINS, SUBSELECTS, ORDER BY, and GROUP BY cannot be run in pessimistic access intent. |
Action | Reconfigure the access intent, or change the query statement for the EJB. |
Explanation | Ordering, grouping, or DISTINCT is supported only for container-managed persistence (CMP) fields that are of types such as numbers, strings and date-time values. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | You cannot use GROUP BY, ORDER BY, or DISTINCT with data types like clob, blob or other long binary or character data types. |
Action | Correct the query statement for the EJB or the mapping. |
Explanation | A specified type cannot be used as the type of a parameter. |
Action | Correct the query statement for the enterprise Java bean (EJB) with a correct parameter type. |
Explanation | The input argument type specified cannot be used as the type of an input parameter of a method. |
Action | Correct the method with correct parameter type. |
Explanation | The return type specified cannot be used as the return type of a method. |
Action | Correct the method with correct return type. |
Explanation | The specified function is not supported in query statements for enterprise Java beans (EJBs). |
Action | Correct the query statement for the EJB. |
Explanation | A trim character can only be a single character on TRIM function. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | The identifier must be defined before it is referenced in a query statement for an enterprise Java bean (EJB). |
Action | Correct the query statement for the EJB. |
Explanation | The identifier must be defined within a JOIN clause. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | There is a path expression with an identification variable in a JOIN clause that is not correctly used. |
Action | Change the query to reference the identification variable where path expression is used. |
Explanation | Overloaded methods with the same number of input arguments are not supported. |
Action | Correct the query statement for the EJB or the method definition. |
Explanation | The program cannot issue a binary operation on two operands with types that are not compatible. |
Action | Correct the query statement for the enterprise Java bean (EJB), or correct the application schema. |
Explanation | An evaluation error occurred at run time. The program cannot issue a unary operation on a type that is not supported. |
Action | Correct the query statement for the enterprise Java bean (EJB), or correct the application schema. |
Explanation | The following SQL types are allowed: INYINT, SMALLINT, INTEGER, BIGINT, FLOAT, REAL, DOUBLE, CHAR, VARCHAR, LOB, DECIMAL, DATE, TIME, and TIMESTAMP. |
Action | Correct the application schema. |
Explanation | An internal error was encountered. |
Action | Restart the system. If the problem persists, refer to the IBM support Web site for information on problem determination. |
Explanation | The form of the decimal constant that is given in the query is not an acceptable format. |
Action | Correct the decimal constant in the query statement for the enterprise Java bean (EJB). |
Explanation | Date/Time arithmetic is not currently supported. |
Action | Correct the query statement for the enterprise Java bean (EJB) to avoid date/time arithmetics. |
Explanation | The converter class that is used in the application schema cannot be found or instantiated, or the converter class is not valid. |
Action | Add the converter class in the class path, or correct the application schema. |
Explanation | A 'null' return was received from the converter that was specified. |
Action | Correct the converter. |
Explanation | A DATE value was supplied that is not valid. The valid format for the string representation of the DATE are: (yyyynnn), (yyyyMMdd),(yyyyMMddhhmmss),(yyyy-MM-dd-hh.mm.ss.nnnnnn),(dd.MM.yyyy). |
Action | Use the correct date/time format for literals in the query statement for the enterprise Java bean (EJB). Refer to the documentation for supported date/time formats. |
Explanation | An overflow or underflow condition was detected while converting a value to a decimal. |
Action | Correct the query statement for the enterprise Java bean (EJB), or correct the application schema. |
Explanation | The Application Server cannot convert the given string to its corresponding numeric value, because a format was encountered that is not able to be parsed. |
Action | Correct the string representation of the number. |
Explanation | The supported mapping for boolean types are SMALLINT, INTEGER. |
Action | Correct the application schema. |
Explanation | The supported boolean value are: false = 0 , true = 1. |
Action | Correct the corresponding value that is stored in back-end database. |
Explanation | The Application Server cannot map the result type that is inferred from the expression. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | An error was detected while attempting to retrieve a given field. |
Action | Correct the class definition that is given, or correct the field name. |
Explanation | The program cannot access or invoke the given method. |
Action | Correct the application model. |
Explanation | A value of NULL cannot be used as the type of a parameter. |
Action | Change the query method with a parameter type that is valid. |
Explanation | The number of parameters that was passed in the query engine is less than what was expected. |
Action | Correct the number of parameter that are passed in. |
Explanation | An internal error was found after the plan was evaluated. |
Action | Restart the system. If the problem persists, refer to the IBM support Web site for information on problem determination. |
Explanation | An internal error was detected in the plan parser. |
Action | Restart the system. If the problem persists, refer to the IBM support Web site for information on problem determination. |
Explanation | An error was detected in attempting to access the data source. |
Action | Reset the data source. If the problem persists, refer to the IBM support Web site for information on problem determination. |
Explanation | An exception occurred while executing the objectFrom method. |
Action | Verify that the class exists and that the arguments are correct. |
Explanation | An ArithmeticException occurred because of division by zero. |
Action | Correct the arithmetic expression. |
Explanation | The result of the arithmetic operation is not within the range of the result type that was expected. |
Action | Correct the arithmetic expression. |
Explanation | The object that was returned by the objectFrom method of the converter [{0}] is not the same as the object type that was expected. |
Action | Modify the converter class, or correct the application schema. |
Explanation | The result must fall between the dates January 1, 0001, and December 31, 9999, inclusively. |
Action | Correct the expression. |
Explanation | The method that was invoked threw an exception. |
Action | Correct the invoked method in the application model. |
Explanation | This is an internal error in the Application Server. |
Action | Refer to the IBM support Web site for information on problem determination. |
Explanation | There was an error trying to create a Service Data Object (SDO) without the primary key. |
Action | Correct the updates to the datagraph. |
Explanation | This is an internal error in the Application Server. |
Action | Refer to the IBM support Web site for information on problem determination. |
Explanation | This is an internal error in the Application Server. |
Action | Refer to the IBM support Web site for information on problem determination. |
Explanation | This is an internal error in the Application Server. |
Action | Refer to the IBM support Web site for information on problem determination. |
Explanation | This is an internal error in the Application Server. |
Action | Refer to the IBM support Web site for information on problem determination. |
Explanation | This is an internal error in the Application Server. |
Action | Refer to the IBM support Web site for information on problem determination. |
Explanation | There was an error in initializing the specified mediator query. |
Action | Correct the mediator query. |
Explanation | There was an error in executing the specified mediator query. The input parameters for the query are included in the message text. |
Action | Correct the mediator query or the schema for the enterprise Java bean (EJB). |
Explanation | An error occurred while trying to apply the DataGraph changes to the database. The changes have not been applied to the database. For the case of updating, one or more OCC fields might have been changed by another user session, and the update is not allowed. |
Action | Change the updates, or make the appropriate change to the database based on the error. |
Explanation | There was an error trying to create Service Data Objects (SDOs) with the same primary key. |
Action | Correct the updates to the datagraph. |
Explanation | There was an error trying to update a field that might be the primary key, part of primary key, output of a method, or output of a converter or an expression. |
Action | Correct the updates to the datagraph. |
Explanation | The Service Data Object (SDO) cannot be updated because either its primary key is not specified in the projection clause of the EJBMediator query, or at least one OCC is defined but is not projected. |
Action | Generate the DataGraph again by specifying the primary keys in the mediator query. To update the SDO, include at least one of the OCC fields in your select clause. |
Explanation | An error occurred trying to create an EClass defining the schema of the model query object. |
Action | Correct the error in the model query object. |
Explanation | Error occurred while trying to parse the FROM clause. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | An error occurred while trying to create an enterprise Java bean (EJB) mediator. |
Action | Correct the query statement for the EJB. |
Explanation | A mediator adapter is supplied, however the adapter only handles partial operations for a data object. |
Action | Modify the mediator adapter, and run the operation again. |
Explanation | The Application Server cannot perform a lookup for the transaction service because the user application is a container-managed bean. |
Action | The application is responsible for rolling back the transaction. Modify the programming model appropriately. |
Explanation | The Application Server cannot set 'roll back only' for the transaction service, because the status of the transaction is: javax.transaction.Status.STATUS_NO_TRANSACTION or the setRollbackOnly call resulted in an exception. |
Action | The application is responsible for rolling back the transaction. Modify the programming model appropriately. |
Explanation | An aggregation operation (for example SUM, AVG, and so on) appears in the top level of the query. This is not supported by the query engine for the enterprise Java bean (EJB). |
Action | Correct the query statement for the EJB. |
Explanation | A DISTINCT operation appears in the top level of the query. This is not supported by the query engine for the enterprise Java bean (EJB). |
Action | Correct the query statement for the EJB. |
Explanation | An OCC container-managed persistence (CMP) field has been changed by another user session, and an update to it is not allowed. |
Action | Regenerate the DataGraph, and run the operation again. |
Explanation | A DataGraph that is based on the NO_DUMMY_ROOT pattern schema can have only one instance of a root Service Data Object (SDO). |
Action | Create the mediator again with a query array for the enterprise Java bean (EJB) that returns a single root SDO. |
Explanation | An error occurred trying to identify an inverse relationship. |
Action | Deploy the application again, and restart the application. |
Explanation | An error occurred trying to get a collection parameter object for the Abstract Schema Name (ASN). |
Action | Correct the collection parameter object that was passed to the query engine, and run the query again. |
Explanation | An internal error occurred. |
Action | Restart your system. If the problem persists, refer to the IBM support Web site for information on problem determination. |
Explanation | An internal error occurred. |
Action | Refer to the IBM support Web site for information on problem determination. |
Explanation | The static schema for the specified EClass does not have the named feature defined. |
Action | Redefine the static schema or the mediator query. |
Explanation | The relationship is not able to be updated, because it is not specified in the EJBMediator query. |
Action | The Application Server cannot update the relationship in the current DataGraph. To update the relationship, regenerate the DataGraph by specifying the relationship in the mediator query. |
Explanation | Duplicate container-managed persistence (CMP) names, resulting in duplicate attributes, are present in the DataGraph. This is not allowed in queries that return Service Data Objects (SDOs). |
Action | Rename one of the duplicates by using the AS syntax. For instance, 'select e.name, e.depSet.name as deptName from EmpBean e'. |
Explanation | The UNION operation is not allowed in a mediator query that returns Service Data Objects (SDOs). |
Action | Remove the UNION operation from the query. |
Explanation | The GROUP BY or HAVING clauses are not allowed in a mediator query that returns Service Data Objects (SDOs). |
Action | Remove the GROUP BY or HAVING clauses from the query. |
Explanation | A subquery in a SELECT clause is not allowed in a mediator query that returns Service Data Objects (SDOs). |
Action | Remove the subquery from the SELECT clause. |
Explanation | A Data Object must be retrieved for linking the relationships. |
Action | Correct the query to include retrieval of the related Data Object. |
Explanation | The SELECT statements must contain an equal number of elements in the SELECT clauses for queries that retrieve the same type of Data Object. |
Action | Correct the query statement for the enterprise Java bean (EJB). |
Explanation | When the same Data Objects are retrieved in mediator queries, the container-managed persistence (CMP) fields in all of the SELECT clauses must match. |
Action | Correct the mediator query statement. |
Explanation | The SELECT clause in a mediator query must contain container-managed persistence (CMP) fields or expressions that reference CMP fields. A constant expression is not allowed. |
Action | Correct the query statement. |
Explanation | There was an error trying to update a field that might be the primary key or part of the primary key. |
Action | Correct the updates to the DataGraph. |
Explanation | No such Abstract Schema Name (ASN) is defined in the metadata that was generated by a CMP/A deploy tool. |
Action | Check your application, and deploy the application again with CMP/A deploy tool. |
Explanation | The Abstract Schema Name (ASN) that is specified in the FROM clause of the query is not defined in any of the installed applications. |
Action | Verify that the ASN name is correct, or install the application that has the ASN name, and submit the query again. |
Explanation | The Abstract Schema Name (ASN) that is specified in the FROM clause of the query is not defined in any of the installed applications. |
Action | Verify that the ASN name is correct, or install the application that has the ASN name, and submit the query again. |
Explanation | The Abstract Schema Name (ASN) that is specified in the FROM clause of the query is not defined in any of the installed applications. |
Action | Verify that the ASN name is correct, or install the application that has the ASN name, and submit the query again. |
Explanation | The number of method arguments does not match those that are defined in the push-down methods list of the CMP/A deployment tool. |
Action | Correct the query, or add the method to the CMP/A push-down list. |
Explanation | The Abstract Schema Name (ASN) that is specified in the FROM clause of the query is not defined in any of the installed applications. |
Action | Verify that the ASN name is correct, or install the application that has the ASN name, and submit the query again. |
Explanation | The access intent that is defined for the {0} ASN in not valid. |
Action | Correct the access intent, re-install the application, and run the program again. |
Explanation | The Abstract Schema Name (ASN) that is specified in the FROM clause of the query is not defined in any of the installed applications. |
Action | Verify that the ASN name is correct, or install the application that has the ASN name, and submit the query again. |
Explanation | The foreign key for the target relationship cannot be obtained. |
Action | Correct the CMP/A push-down method in the user-defined implementation class for the push-down method, and deploy the application again with CMP/A deployment tool. |
Explanation | The method arguments for CMP/A must be literal or ?. |
Action | Correct the method arguments, and deploy the application again with the CMP/A deployment tool. |
Explanation | The associated keys for the target relationship cannot be obtained. |
Action | Verify that the Abstract Schema Name (ASN) is correct, or install the application that has the ASN name, and deploy the application again with CMP/A deploy tool. |
Explanation | The cache entry for this Abstract Schema Name (ASN) cannot be obtained. |
Action | Correct the CMP/A push-down method that is in the user-defined implementation class for the push-down method, and deploy the application again with the CMP/A deployment tool. |
Explanation | The cache entry for this Abstract Schema Name (ASN) cannot be obtained. |
Action | Correct the CMP/A push-down method that is in the user-defined implementation class for the push-down method, and deploy the application again with the CMP/A deployment tool. |
Explanation | The Application Server failed to invoke the FINDER method on the concrete bean, because the wrong FINDER method name or argument was supplied. |
Action | Correct the CMP/A push-down FINDER method, and deploy the application again with a CMP/A deployment tool. |
Explanation | The method argument type is not compatible. |
Action | Correct the method arguments, and deploy the application again with a CMP/A deployment tool, or enter correct method arguments in the query and run the application again. |
Explanation | The Application Server failed to invoke the FINDER method on the concrete bean, because a back-end error occurred. |
Action | Correct the FINDER method, and deploy the application again with a CMP/A deployment tool. |
Explanation | The Application Server failed to invoke remote finder method. |
Action | Correct the FINDER method, and deploy the application again with a CMP/A deployment tool. |
Explanation | Method does not exist in the CMP/A push-down methods list. |
Action | Define the method, and deploy the application again with a CMP/A deployment tool, or enter the correct method in the query, and run the application again. |
Explanation | The Abstract Schema Name (ASN) cannot be null. |
Action | Correct the query, and run the application again. |
Explanation | The CMP/A FINDER method can only be used on a WebSphere Business Integration (WBI) platform for a query that is of the CMP/A type. |
Action | Verify the installation of WBI, and deploy the application again with a CMP/A deployment tool. |
Explanation | A character can only be compared to a character or a string of length 1. |
Action | Correct the query statement for the enterprise Java bean (EJB). |