Explanation | WQRY0000E: An aggregation operation (e.g. SUM, AVG, etc.) appears in the mapping metadata. This is not currently supported by the EJB query engine. |
Action | WQRY0000E: This situation should never occur and indicates an internal error either in WebSphere server or the WSAD deployment tooling. Report this problem to IBM service. |
Explanation | WQRY0001E: An error occurred executing an sql statement. Token {0} indicates the failing sql statement. This only applies to the WebSphere dynamic query service. |
Action | WQRY0001E: Verify if the failing sql statement is valid for the target database. If the database schema is inconsistent with the schema used during deployment or has changed it may be necessary to redeploy the application. Otherwise report the error to IBM service. |
Explanation | WQRY0002E: A syntax error was detected in the mapping metadata generated by the WebSphere deployment tool. This error is either an error in the view implementation or the inheritance typecode predicates |
Action | WQRY0002E: This situation should never occur and indicates an internal error either in WebSphere server or the WSAD deployment tooling. Report this problem to IBM service. |
Explanation | WQRY0003E: An error occurred parsing the ejb query indicated by token {0}. |
Action | WQRY0003E: Verify the ejb query statement. If valid, report the problem to IBM service. |
Explanation | WQRY0004E: A math error occurred executing an EJB query scalar function. Token {0} indicates the scalar function name. |
Action | WQRY0004E: Correct the EJB query statement or update the CMP field values to avoid the overflow problem.. |
Explanation | WQRY0005E: A subquery used in a SELECT clause, cannot itself contain a subquery in its SELECT clause. |
Action | WQRY0005E: Correct the EJB query statement. |
Explanation | WQRY0006E: The identification variable is used in a subquery and references another identification variable indicated by token ''{0}'' in a manner that is not supported. |
Action | WQRY0006E: Correct the EJB query statement. |
Explanation | WQRY0007E: The LIKE predicate takes a single escape character. The string specified by token {0} is greater than one character in length and is not valid. |
Action | WQRY0007E: Correct the EJB query statement. |
Explanation | WQRY0008E: The Abstract Schema Name (ASN) specified in the FROM clause of the query is not defined in any of the installed applications. |
Action | WQRY0008E: Please make sure that the ASN name is correct or install the application that has the ASN name and resubmit the query. |
Explanation | WQRY0009E: The Abstract Schema Name (ASN) specified in the FROM clause of the query is defined in more than one installed applications. |
Action | WQRY0009E: Please provide the EJBHome or EJBLocalHome to uniquely identify the ASN name. Follow the sample client code for the usage of EJBHome or EJBLocalHome and resubmit the query. |
Explanation | WQRY0010E: The query expression indicated by token {0} attempts to compare two expressions which are not compatible in type. |
Action | WQRY0010E: Correct the EJB query statement. |
Explanation | WQRY0011E: The aggregate function (e.g. SUM, COUNT, etc) indicated by token {0} is used incorrectly ( such as being used in a WHERE clause ) or contains an invalid argument ( an expression that contains correlated and noncorrelated values). |
Action | WQRY0011E: Correct the EJB query statement. |
Explanation | WQRY0012E: Using the equal or not equal predicate to compare two EJBs that cannot be compared. Only EJBs that are compatible types and are from the same home can be compared. |
Action | WQRY0012E: Correct the EJB query statement. |
Explanation | WQRY0013E: A math error occurred computing the value of an AVG or SUM function. |
Action | WQRY0013E: Correct the EJB query statement or the CMP field values. |
Explanation | WQRY0014E: The identification variable ''{0}'' defined over an invalid association ''{1}'' because the schema of the association contains no persistent fields. |
Action | WQRY0014E: Check the EJB query statement or the application model. |
Explanation | WQRY0015E: EJB query does not support casting a CMP or CMR field to another type. |
Action | WQRY0015E: Correct the EJB query statement. |
Explanation | WQRY0016E: EJB query does not support casting a CMP or CMR field to another type. |
Action | WQRY0016E: Correct the EJB query statement. |
Explanation | WQRY0017E: An identification variable must be defined as an abstract schema name or as an multivalued path expression. The identification variable indicated by token ''{0}'' is defined with the path expression indicated by token ''{1}'' which ends in a single valued relationship name. |
Action | WQRY0017E: Correct the EJB query statement. |
Explanation | WQRY0018E: The mapping metadata for field indicated by token {0} cannot be accessed. |
Action | WQRY0018E: This situation should never occur and indicates an internal error either in WebSphere server or the WSAD deployment tooling. Report this problem to IBM service. |
Explanation | WQRY0019E: A field must always be used in the context of a path expression that begins with an identification variable. |
Action | WQRY0019E: Correct the EJB query statement. |
Explanation | WQRY0020E: EJB query does not support casting a CMP or CMR field to another type. |
Action | WQRY0020E: Correct the EJB query statement. |
Explanation | WQRY0021E: EJB query does not support casting a CMP or CMR field to another type. |
Action | WQRY0021E: Correct the EJB query statement. |
Explanation | WQRY0022E: Internal error. |
Action | WQRY0022E: This situation should never occur and indicates an internal error either in WebSphere server or the WSAD deployment tooling. Report this problem to IBM service. |
Explanation | WQRY0023E: When performing a grouping operation, elements of the SELECT clause must either be aggregation functions or be grouping elements. The CMP field indicated by token {0} is used in the SELECT clause and does not appear in an aggregation function but is not a grouping element. |
Action | WQRY0023E: Correct the EJB query statement. |
Explanation | WQRY0024E: The order by clause of a query statement refers to a select element by ordinal number indicated by token {0}, but no such element exists. |
Action | WQRY0024E: Correct the EJB query statement. |
Explanation | WQRY0025E: The abstract schema name indicated by token {0} is not defined. |
Action | WQRY0025E: Correct the EJB query statement. |
Explanation | WQRY0026E: Zero and negative numbers are not valid in the order by clause. To sort in descending order use the keyword DESC. |
Action | WQRY0026E: Correct the EJB query statement. |
Explanation | WQRY0027E: Attempt to navigate past the CMP or CMR field indicated by token {1} in the path expression indicated by token {0}. A path expression can only navigate through a single valued CMR field. |
Action | WQRY0027E: Correct the EJB query statement. |
Explanation | WQRY0028E: Attempt to navigate past the CMP or CMR field indicated by token {1} in a path expression. A path expression can only navigate through a single valued CMR field. |
Action | WQRY0028E: Correct the EJB query statement. |
Explanation | WQRY0029E: Overflow occurred while computing AVG aggregate function. |
Action | WQRY0029E: Correct the EJB query statement to avoid the overflow. |
Explanation | WQRY0030E: Overflow occurred while computing COUNT aggregate function. |
Action | WQRY0030E: Correct the EJB query statement to avoid the overflow. |
Explanation | WQRY0031E: Backend datastore cannot compare columns which are greater than 254 bytes or binary data |
Action | WQRY0031E: Correct the EJB query statement or the EJB mapping. |
Explanation | WQRY0032E: A number or path expression appears more than once in the order by clause. |
Action | WQRY0032E: Correct the EJB query statement. |
Explanation | WQRY0033E: A path expression appears more than once in the group by clause. |
Action | WQRY0033E: Correct the EJB query statement. |
Explanation | WQRY0034E: You cannot use DISTINCT more than once in aggregate functions in a query. |
Action | WQRY0034E: Correct the EJB query statement. |
Explanation | WQRY0035E: A distinct operation appears in the mapping metadata. This is not currently supported by the EJB query engine. |
Action | WQRY0035E: This situation should never occur and indicates an internal error either in WebSphere server or the WSAD deployment tooling. Report this problem to IBM service. |
Explanation | WQRY0036E: A CMP or CMR field with the name indicated by token ''{2}'' was used in a query statement. The bean with ASN indicated by token ''{0}'' and identification variable indicated by token ''{1}'' does not define this field. |
Action | WQRY0036E: Correct the EJB query statement. |
Explanation | WQRY0037E: The method with the name indicated by token ''{2}'' was used in a query statement. The bean with ASN indicated by token ''{0}'' and identification variable indicated by token ''{1}'' does not define this method. Use of methods in query statements is only supported in WebSphere Extended Edition. |
Action | WQRY0037E: Correct the EJB query statement. |
Explanation | WQRY0038E: Division operator can only be used on numeric types. |
Action | WQRY0038E: Correct the EJB query statement. |
Explanation | WQRY0039E: An internal error in the server runtime. |
Action | WQRY0039E: This situation should never occur and indicates an internal error in WebSphere server. Report this problem to IBM service. |
Explanation | WQRY0040E: The scalar functions EMPTY, EXISTS, IN, ALL, ANY and SOME can only be applied to CMR fields and to sub queries. |
Action | WQRY0040E: Correct the EJB query statement. |
Explanation | WQRY0041E: An unknown exception occurred during query evalution. If the query statement calls user defined methods, check that the method is not throwing an exception. Otherwise this is an internal error. |
Action | WQRY0041E: If unable to resolve problem, report this problem to IBM service. |
Explanation | WQRY0042E: The only method overloading that Query allows is for a method to have different numbers of parameters. |
Action | WQRY0042E: Correct the EJB model. |
Explanation | WQRY0043E: Greater than or equal operator can only be used with numeric, string, date-time or calendar types. Token {0} contains the expression that is incorrect. |
Action | WQRY0043E: Correct the EJB query statement. |
Explanation | WQRY0044E: Greater than operator can only be used with numeric, string, date-time or calendar types. Token {0} contains the expression that is incorrect. |
Action | WQRY0044E: Correct the EJB query statement. |
Explanation | WQRY0045E: An illegal character was used in the EJB query. The Syntax error message following the Illegal Character error message shows the location and type of the illegal character. |
Action | WQRY0045E: Check the EJB query statement for invalid characters. |
Explanation | WQRY0046E: A syntax error was detected in the mapping metadata generated by the WebSphere deployment tool. Token {0} indicates the typecode predicates and token {1} is the ASN for the failing EJBHome. |
Action | WQRY0046E: This situation should never occur and indicates an internal error either in WebSphere server or the WSAD deployment tooling. Report this problem to IBM service. |
Explanation | WQRY0047E: A path expresssion cannot navigate through a multivalued CMR field. |
Action | WQRY0047E: Correct the EJB query statement. |
Explanation | WQRY0048E: When an EJB Query is used to define a 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 CMP or single valued CMR field. |
Action | WQRY0048E: Correct the EJB query statement. |
Explanation | WQRY0049E: Inquality operator is used with an incompatible datatype. Token {0} contains the expression that is incorrect. |
Action | WQRY0049E: Correct the EJB query statement. |
Explanation | WQRY0050E: IS NULL and IS NOT NULL must be used with CMP fields or single valued CMR fields in path expresssions. |
Action | WQRY0050E: Correct the EJB query statement. |
Explanation | WQRY0051E: Less than or equal operator is used with an incompatible datatype. Token {0} contains the expression that is incorrect. |
Action | WQRY0051E: Correct the EJB query statement. |
Explanation | WQRY0052E: Less than operator is used with an incompatible datatype. Token {0} contains the expression that is incorrect. |
Action | WQRY0052E: Correct the EJB query statement. |
Explanation | WQRY0053E: MAX function is used with an incompatible datatype. Token {0} contains the expression that is incorrect. |
Action | WQRY0053E: Correct the EJB query statement. |
Explanation | WQRY0054E: The method in the EJB query differs in number or type of argument from all methods with the same name in the EJB model. |
Action | WQRY0054E: Correct the EJB query statement. |
Explanation | WQRY0055E: MINUS operator is used with an incompatible datatype. Token {0} contains the expression that is incorrect. |
Action | WQRY0055E: Correct the EJB query statement. |
Explanation | WQRY0056E: MIN function is used with an incompatible datatype. Token {0} contains the expression that is incorrect. |
Action | WQRY0056E: Correct the EJB query statement. |
Explanation | WQRY0057E: This situation should never occur. |
Action | WQRY0057E: This situation should never occur and indicates an internal error either in WebSphere server or the WSAD deployment tooling. Report this problem to IBM service. |
Explanation | WQRY0058E: Using the MEMBER OF predicate to compare an entity bean to a collection valued CMR field is invalid because the entity beans are not comparible or belong to different homes. |
Action | WQRY0058E: Correct the EJB query statement. |
Explanation | WQRY0059E: There may be a maximum of 100 select statements in the final query generated by an EJB query. |
Action | WQRY0059E: Reduce the size and number of select operations in the EJB query statement |
Explanation | WQRY0060E: A maximum of 512 quantifiers can be used in the query plan which is generated by the EJB query. |
Action | WQRY0060E: Reduce the complexity of the EJB query statement. |
Explanation | WQRY0061E: An aggregate function such as SUM cannot contain another aggregate function in the argument expression. |
Action | WQRY0061E: Correct the EJB query statement. |
Explanation | WQRY0062E: The collection aggregate operation NEST is used with an incorrect type. |
Action | WQRY0062E: This situation should never occur and indicates an internal error either in WebSphere server or the WSAD deployment tooling. Report this problem to IBM service. |
Explanation | WQRY0063E: The parameter indicated by token {0} is not defined. |
Action | WQRY0063E: Correct the EJB query statement. |
Explanation | WQRY0064E: The parameter indicated by token {0} is a cmp or cmr field. Token {1} indicates the schema used in the query. |
Action | WQRY0064E: Correct the EJB query statement. |
Explanation | WQRY0065E: The field {1} does not denote a CMR or CMP field defined by the given schema {0} |
Action | WQRY0065E: Check the EJB query statement or the schema mapping of the applicaiton model. |
Explanation | WQRY0066E: An internal metadata error. |
Action | WQRY0066E: This situation should never occur and indicates an internal error either in WebSphere server or the WSAD deployment tooling. Report this problem to IBM service. |
Explanation | WQRY0067E: Internal error. |
Action | WQRY0067E: This situation should never occur and indicates an internal error either in WebSphere server or the WSAD deployment tooling. Report this problem to IBM service. |
Explanation | WQRY0068E: Internal error. |
Action | WQRY0068E: This situation should never occur and indicates an internal error either in WebSphere server or the WSAD deployment tooling. Report this problem to IBM service. |
Explanation | WQRY0069E: A function that requires a numeric expression was used with an incorrect argument expression. Token {0} shows the function. |
Action | WQRY0069E: Correct the EJB query statement. |
Explanation | WQRY0070E: An AVG function that requires a numeric expression was used with an incorrect argument expression. |
Action | WQRY0070E: Correct the EJB query statement. |
Explanation | WQRY0071E: A query iterator became invalid because the jdbc cursor is invalid. This is probably due to an end of transaction operation. The query iterator cannot be used outside the originating transaction scope. |
Action | WQRY0071E: Correct the user program. |
Explanation | WQRY0072E: Internal error. |
Action | WQRY0072E: This situation should never occur and indicates an internal error either in WebSphere server or the WSAD deployment tooling. Report this problem to IBM service. |
Explanation | WQRY0073E: The number specified is out of the legal range for its data type |
Action | WQRY0073E: Correct the EJB query statement. |
Explanation | WQRY0074E: Internal error. |
Action | WQRY0074E: This situation should never occur and indicates an internal error either in WebSphere server or the WSAD deployment tooling. Report this problem to IBM service. |
Explanation | WQRY0075E: If the ORDER BY clause is used, the element being ordered by must appear in the SELECT clause. |
Action | WQRY0075E: Correct the EJB query statement. |
Explanation | WQRY0076E: Performing a distinct operation in an EJB query which returns object references may produce an order by on the primary key fields of the EJB. If the query contains an ORDER BY clause specified by the user, the two ordering may conflict. |
Action | WQRY0076E: Remove either the ORDER BY or the DISTINCT operation and retry the EJB query. |
Explanation | WQRY0077E: Ordering on java.sql.blob values is not supported. |
Action | WQRY0077E: Correct the EJB query statement. |
Explanation | WQRY0078E: Ordering on boolean values is not supported. |
Action | WQRY0078E: Correct the EJB query statement. |
Explanation | WQRY0079E: Ordering on java.sql.clob values is not supported. |
Action | WQRY0079E: Correct the EJB query statement. |
Explanation | WQRY0080E: Method mapping to backend data store is not currently supported. |
Action | WQRY0080E: Correct the EJB query statement. |
Explanation | WQRY0081E: Ordering is supported only for CMP values that are orderable types such as numbers, strings and date-time values. |
Action | WQRY0081E: Correct the EJB query statement. |
Explanation | WQRY0082E: PLUS operator is used with an incompatible datatype. Token {0} contains the expression that is incorrect. |
Action | WQRY0082E: Correct the EJB query statement. |
Explanation | WQRY0083E: Attempt to reference a parameter greater than the number of input parameters. The parameters are defined by the signature of the finder or select method. For WebSphere dynamic EJB query, 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 | WQRY0083E: Correct the EJB Query or the method signature. |
Explanation | WQRY0084E: When using ORDER BY with a UNION operation the ORDER BY must use integer constants to indicate CMP attributes in the EJB being queried |
Action | WQRY0084E: Correct the EJB query statement. |
Explanation | WQRY0085E: You cannot use the same Correlation Id to refer to more than one EJB instance in the same select clause. |
Action | WQRY0085E: Correct the EJB query statement. |
Explanation | WQRY0086E: 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 | WQRY0086E: Correct the EJB query statement. |
Explanation | WQRY0087E: The identification variable indicated by token {0} is used in a subquery and references another identification variable indicated by token {1} in a manner that is not supported. |
Action | WQRY0087E: Correct the EJB query statement. |
Explanation | WQRY0088E: A subquery used in a SELECT clause, cannot itself contain a subquery in its SELECT clause. |
Action | WQRY0088E: Correct the EJB query statement. |
Explanation | WQRY0089E: For example you cannot use 'select * from XyzBean' to select all of XyzBean's CMP fields. |
Action | WQRY0089E: Correct the EJB query statement. |
Explanation | WQRY0090E: In order to use 'e.*' in a subquery, the identification variable 'e' must be defined in the subquery. |
Action | WQRY0090E: Correct the EJB query statement. |
Explanation | WQRY0091E: The keyword OBJECT is used in the select clause to project the object reference associated with an identification variable. |
Action | WQRY0091E: Correct the EJB query statement. |
Explanation | WQRY0092E: The EJB query does not satisfy the syntax diagram found in the EJB Query Documentation. |
Action | WQRY0092E: Correct the EJB query statement. |
Explanation | WQRY0093E: An internal error in mapping metadata. |
Action | WQRY0093E: This situation should never occur and indicates an internal error either in WebSphere server or the WSAD deployment tooling. Report this problem to IBM service. |
Explanation | WQRY0094E: The indicated argument cannot be used with the indicated Scalar Function. |
Action | WQRY0094E: Correct the EJB query statement. |
Explanation | WQRY0095E: The actual table schema does not match the schema used to generate the mapping metadata at deployment time. |
Action | WQRY0095E: Check the actual table schema and the schema used to generate the mapping metadata at deployment time. |
Explanation | WQRY0096E: When using the IS OF TYPE predicate to test the subtype of EJBs, the subtype(s) that make the right operand of the IS OF TYPE predicate must be defined subtypes of the EJB specified by the left operand. |
Action | WQRY0096E: Correct the EJB query statement. |
Explanation | WQRY0097E: An internal error in mapping metadata. |
Action | WQRY0097E: This situation should never occur and indicates an internal error either in WebSphere server or the WSAD deployment tooling. Report this problem to IBM service. |
Explanation | WQRY0098E: An internal error in mapping metadata. |
Action | WQRY0098E: This situation should never occur and indicates an internal error either in WebSphere server or the WSAD deployment tooling. Report this problem to IBM service. |
Explanation | WQRY0099E: Multiply operator is used with an incompatible datatype. Token {0} contains the expression that is incorrect. |
Action | WQRY0099E: Correct the EJB query statement. |
Explanation | WQRY0100E: An internal error in mapping metadata. |
Action | WQRY0100E: This situation should never occur and indicates an internal error either in WebSphere server or the WSAD deployment tooling. Report this problem to IBM service. |
Explanation | WQRY0101E: An internal error in mapping metadata. |
Action | WQRY0101E: This situation should never occur and indicates an internal error either in WebSphere server or the WSAD deployment tooling. Report this problem to IBM service. |
Explanation | WQRY0102E: A subquery used with a basic predicate must only return a single value. Mutliple values were returned at runtime when the subquery was evaluated. |
Action | WQRY0102E: Correct the EJB query statement. |
Explanation | WQRY0103E: A subselect can only return a single value. |
Action | WQRY0103E: Correct the EJB query statement. |
Explanation | WQRY0104E: The sum of the second and third arguments is greater than the length of the first argument |
Action | WQRY0104E: Correct the EJB query statement. |
Explanation | WQRY0105E: An internal error in mapping metadata. |
Action | WQRY0105E: This situation should never occur and indicates an internal error either in WebSphere server or the WSAD deployment tooling. Report this problem to IBM service. |
Explanation | WQRY0106E: Inconsistent schema information regarding the given field {0} |
Action | WQRY0106E: Correct the EJB query statement or check the application model. |
Explanation | WQRY0107E: The keyword _THIS is a reserved word and cannot be used in an EJB query |
Action | WQRY0107E: Change the schema name in the deployment descriptor or the table name. |
Explanation | WQRY0108E: The field is not defined in the abstract schema as either a CMP or CMR field. Make sure that every path expression begins with an identification variable. |
Action | WQRY0108E: Correct the EJB query statement. |
Explanation | WQRY0109E: When performing a UNION operator, the SELECT statements that are operands to the UNION must contain equal number of elements in the SELECT clauses. |
Action | WQRY0109E: Correct the EJB query statement. |
Explanation | WQRY0110E: The identification variable found with a CMP or CMR field does not match the identitication variable associated with any EJB being queried |
Action | WQRY0110E: Correct the EJB query statement. |
Explanation | WQRY0111E: When performing a UNION operator, the SELECT statements that are operands to the UNION must contain type compatible elements in the SELECT clauses. |
Action | WQRY0111E: Correct the EJB query statement. |
Explanation | WQRY0112E: The correct method signature was not found in the EJB remote or local interface used. |
Action | WQRY0112E: Correct the EJB model. |
Explanation | WQRY0113E: An internal error in mapping metadata. |
Action | WQRY0113E: This situation should never occur and indicates an internal error either in WebSphere server or the WSAD deployment tooling. Report this problem to IBM service. |
Explanation | WQRY0114E: An internal error in mapping metadata. |
Action | WQRY0114E: This situation should never occur and indicates an internal error either in WebSphere server or the WSAD deployment tooling. Report this problem to IBM service. |
Explanation | WQRY0115E: An internal error in mapping metadata. |
Action | WQRY0115E: This situation should never occur and indicates an internal error either in WebSphere server or the WSAD deployment tooling. Report this problem to IBM service. |
Explanation | WQRY0116E: An internal error in mapping metadata. |
Action | WQRY0116E: This situation should never occur and indicates an internal error either in WebSphere server or the WSAD deployment tooling. Report this problem to IBM service. |
Explanation | WQRY0117E: An internal error in mapping metadata. |
Action | WQRY0117E: This situation should never occur and indicates an internal error either in WebSphere server or the WSAD deployment tooling. Report this problem to IBM service. |
Explanation | WQRY0118E: An internal error in mapping metadata. |
Action | WQRY0118E: This situation should never occur and indicates an internal error either in WebSphere server or the WSAD deployment tooling. Report this problem to IBM service. |
Explanation | WQRY0119E: The number of arguments used in the query statement is inconsistent with the definition of the function indicated by token {0}. |
Action | WQRY0119E: Correct the EJB query statement. |
Explanation | WQRY0120E: Invalid mapping of cmr field to database relational table. |
Action | WQRY0120E: Correect mapping of cmr to relational table. |
Explanation | WQRY0121E: No mapping exist for cmr field to relational database table. |
Action | WQRY0121E: Create a mapping for the cmr field. |
Explanation | WQRY0122E:The converter class used in the application schema cannot be found or instantiated or it is not a valid converter class |
Action | WQRY0122E:Add the converter class in the class path or correct the application schema. |
Explanation | WQRY0123E:Following error occured while executing dataFrom method:{0} |
Action | WQRY0123E:Converter 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 EJB query statement. |
Explanation | WQRY0124E:Following error occured while creating the input argument for dataFrom method:{0} |
Action | WQRY0124E:Correct the input value according to the converter. |
Explanation | WQRY0125E:The reutrn type from the dataFrom method is not supported by the query engine currently. |
Action | WQRY0125E:Correct the dataFrom method or use another converter. |
Explanation | WQRY0126E: Container managed relationship refers to an EJB object and object reference cannot be used in the group by clause |
Action | WQRY0126E:Correct the EJB query statement. |
Explanation | WQRY0127E:The output type of the dataFrom method is not compatible in the given expression. |
Action | WQRY0127E: Correct the EJB query statement or the converter. |
Explanation | WQRY0128E:The SELECT clause cannot contain any mutli valued CMR fields. |
Action | WQRY0128E: Correct the EJB query statement. |
Explanation | WQRY0129E: Method mapping to backend data store is not currently supported. |
Action | WQRY0129E: Correct the EJB query statement. |
Explanation | WQRY0130E: The method in the EJB query differs in number or type of argument from all methods with the same name in the EJB model. |
Action | WQRY0130E: Correct the EJB query statement. |
Explanation | WQRY0131E: Expressions with type void should not be used in EJB query. |
Action | WQRY0131E: Correct the application schema or the EJB query statement. |
Explanation | WQRY0132E:The Primary key {0} specified in the metadata at the table level and implementation does not match. |
Action | WQRY0132E: This situation should never occur and indicates an internal error in the WSAD deployment tooling. Report this problem to IBM service. |
Explanation | WQRY0133E: The EJB query that contains joins, subselects, order by, and group by cannot be run in pessimistic access intent. |
Action | WQRY0133E: Reconfigure the access intent or change the EJB query statement. |
Explanation | WQRY0134E: Ordering, Grouping or distinct is supported only for CMP fields that are of types such as numbers, strings and date-time values. |
Action | WQRY0134E: Correct the EJB query statement. |
Explanation | WQRY0135E: Cannot use group by, order by or distinct with data types like clob, blob or other long binary or character data types. |
Action | WQRY0135E: Change the EJB query statement or the mapping. |
Explanation | WQRY0136E: A {0} cannot be used as the type of a parameter. |
Action | WQRY0136E: Correct the EJB query statement with a correct parameter type. |
Explanation | WQRY0137E: A {0} cannot be used as the type of an input parameter of a method. |
Action | WQRY0137E: Correct the method with correct parameter type. |
Explanation | WQRY0138E: A {0} cannot be used as the return type of a method. |
Action | WQRY0138E: Correct the method with correct return type. |
Explanation | WQRY0150E: The specified function is not supported in EJB query |
Action | WQRY0150E: Correct the EJB query statement. |
Explanation | WQRY0151E: Trim character can only be a single character on TRIM function. |
Action | WQRY0151E: Correct the query statement. |
Explanation | WQRY0152E: The identifier must be defined before it is referenced in EJB query. |
Action | WQRY0152E: Correct the EJB query statement. |
Explanation | WQRY0153E: The identifier must be defined within a JOIN clause. |
Action | WQRY0153E: Correct the EJB query statement. |
Explanation | WQRY0154E: A path expression with an identification variable in a JOIN clause is incorrectly used. |
Action | WQRY0154E: Change the query to reference the identification variable where path expression is used. |
Explanation | WQRY0155E: Overloaded methods with the same number of input arguments are not supported. |
Action | WQRY0155E: Change the EJB query statement or the method definition. |
Explanation | WQRY1000E: Cannot execute a binary operation on two operands with incompatible types. |
Action | WQRY1000E: Correct the EJB query or the application schema. |
Explanation | WQRY1001E: Runtime evaluation error. Cannot execute a unary operation on a non-supported type. |
Action | WQRY1001E: Correct the EJB query or the application schema. |
Explanation | WQRY1002E: The allowed SQL types are TINYINT,SMALLINT,INTEGER,BIGINT,FLOAT,REAL,DOUBLE,CHAR,VARCHAR,LOB,DECIMAL,DATE,TIME,TIMESTAMP |
Action | WQRY1002E: Correct the application schema |
Explanation | WQRY1003E: Internal error encountered. |
Action | WQRY1003E: Restart your system. If the problem persists report the error to IBM service. |
Explanation | WQRY1004E: the form of the decimal constant given in the query is not a acceptable format. |
Action | WQRY1004E: Correct the decimal constant in the EJB query. |
Explanation | WQRY1005E: Date/Time arithmetic is not currently supported. |
Action | WQRY1005E: Correct the EJB query to avoid date/time arithmetics. |
Explanation | WQRY1006E: The converter class used in the application schema cannot be found or instantiated or it is not a valid converter class. |
Action | WQRY1006E: Add the converter class in the class path or correct the application schema. |
Explanation | WQRY1007E: A null return from the given converter. |
Action | WQRY1007E: Correct the converter. |
Explanation | WQRY1008E: 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 | WQRY1008E: Use the correct date/time format for literals in the EJB query. Refer to the document for supported date/time format. |
Explanation | WQRY1009E: While converting to a decimal, an overflow/underflow condition was detected. |
Action | WQRY1009E: Correct the EJB query or the application schema. |
Explanation | WQRY1010E: Cannot convert the given string to its corresponding numeric value due a non-parsable format is encountered. |
Action | WQRY1010E: Correct the string representation of the number. |
Explanation | WQRY1011E: The supported mapping for boolean type are SMALLINT, INTEGER. |
Action | WQRY1011E: correct the application schema. |
Explanation | WQRY1012E: The supported boolean value are: false = 0 , true = 1. |
Action | WQRY1012E: Correct the corresponding value stored in backend database. |
Explanation | WQRY1013E: Cannot map the inferred result type from the expression. |
Action | WQRY1013E: Correct the EJB query. |
Explanation | WQRY1014E: An error detected while attempting to retrieve a given field. |
Action | WQRY1014E: correct the given class definition or the field name |
Explanation | WQRY1015E: Cannot access or invoke the give method. |
Action | WQRY1015E: correct the application model. |
Explanation | WQRY1016E: a NULL cannot be used as the type of a parameter. |
Action | WQRY1016E: change the query method with a correct parameter type. |
Explanation | WQRY1017E: the number of parameters passed in the query engine is less than expected. |
Action | WQRY1017E: correct the number of parameter passed in. |
Explanation | WQRY1018E: an internal error found after the plan is evaluated. |
Action | WQRY1018E: restart the system, if the problem persists, report the error to IBM service team. |
Explanation | WQRY1019E: An internal error detected in plan parser. |
Action | WQRY1019E: Restart the system if the problem persists, report the error to IBM service team. |
Explanation | WQRY1020E: An error detected in attempting to access the data source. |
Action | WQRY1020E: Reset the data source.If the problem persists, report the error to IBM service team. |
Explanation | WQRY1021E: An exception occured while executing objectFrom method. |
Action | WQRY1021E: Check if the class exists and the arguments are correct. |
Explanation | WQRY1022E:An ArithmeticException occured because of division by zero. |
Action | WQRY1022E:Correct the arithmetic expression. |
Explanation | WQRY1023E:The result of the arithmetic operation is not within the range of the expected result type. |
Action | WQRY1023E:Correct the arithmetic expression. |
Explanation | WQRY1024E:The object returned by the objectFrom method of the converter [{0}] is not the same as the expected object type. |
Action | WQRY1024E:Modify the converter class or the application schema |
Explanation | WQRY1025E:The result must fall between the dates January 1, 0001 and December 31, 9999 inclusive. |
Action | WQRY1025E:Correct the expression. |
Explanation | WQRY1026E: The invoked method threw an exception. |
Action | WQRY1026E: correct the invoked method in the application model. |
Explanation | WQRY1027E: Internal error. |
Action | WQRY1027E: This situation should never occur and indicates an internal error in WebSphere server. Report this problem to IBM service. |
Explanation | WQRY1028E: Trying to create a sdo object without the primary key. |
Action | WQRY1028E: Correct the updates to the datagraph. |
Explanation | WQRY1029E: Internal error. |
Action | WQRY1029E: This situation should never occur and indicates an internal error in WebSphere server. Report this problem to IBM service. |
Explanation | WQRY1030E: Internal error. |
Action | WQRY1030E: This situation should never occur and indicates an internal error either in WebSphere server or the WSAD deployment tooling. Report this problem to IBM service. |
Explanation | WQRY1031E: Internal error. |
Action | WQRY1031E: This situation should never occur and indicates an internal error in WebSphere server. Report this problem to IBM service. |
Explanation | WQRY1032E: Internal error. |
Action | WQRY1032E: This situation should never occur and indicates an internal error in WebSphere server. Report this problem to IBM service. |
Explanation | WQRY1033E: Internal error. |
Action | WQRY1033E: This situation should never occur and indicates an internal error in WebSphere server. Report this problem to IBM service. |
Explanation | WQRY1034E: Error in initializing the mediator query {1}. |
Action | WQRY1034E: Correct the mediator query. |
Explanation | WQRY1035E: Error in executing mediator query [{1}].The input parameters for the query are [{2}]. |
Action | WQRY1035E: Correct the mediator query or EJB Schema. |
Explanation | WQRY1036E: An error occured 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 may have been changed by another user session and the update is not allowed. |
Action | WQRY1036E: Either change the updates or make appropriate change to the database based on the error. |
Explanation | WQRY1037E: Trying to create sdo objects with the same primary key. |
Action | WQRY1037E: Correct the updates to the datagraph. |
Explanation | WQRY1038E: Trying to update a field which may be the primary key or part of primary key, output of a method or output of a converter or an expression. |
Action | WRY1038E: Correct the updates to the datagraph. |
Explanation | WQRY1039E: The SDO object 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 | WQRY1039E: Generate the datagraph again by specifying the primary keys in the mediator query. To update the SDO object, include at least one of the OCC fields in your select clause. |
Explanation | WQRY1040E: Error occured while trying to create EClass defining the schema of the model query object. |
Action | WQRY1040E: Correct the error in the model query object. |
Explanation | WQRY1041E: Error occured while trying to parse the from clause. |
Action | WQRY1041E: Correct the EJB query statement. |
Explanation | WQRY1042E: Error occured while trying to create EJB Mediator. |
Action | WQRY1042E: Correct the EJB query statement. |
Explanation | WQRY1043E: A mediator adapter is supplied, however only handles partial operations for a data object. |
Action | WQRY1043E: Modify the mediator adapter and try again. |
Explanation | WQRY1044E: Cannot lookup for transaction service because the user application is a container managed bean. |
Action | WQRY1044E: Application is responsible for rolling back the transaction. |
Explanation | WQRY1045E: Cannot set roll back only for transaction service either because the status of the transaction is: javax.transaction.Status.STATUS_NO_TRANSACTION or setRollbackOnly call resulted an exception. |
Action | WQRY1045E: Application is responsible for rolling back the transaction. |
Explanation | WQRY1046E: An aggregation operation (e.g. SUM, AVG, etc.) appears in the top level query. This is not currently supported by the EJB query engine. |
Action | WQRY1046E: Correct the EJB query statement. |
Explanation | WQRY1047E: A distinct operation appears in the top level query. This is not currently supported by the EJB query engine. |
Action | WQRY1047E: Correct the EJB query statement. |
Explanation | WQRY1048E: An OCC CMP field has been changed by another user session and update to it is not allowed. |
Action | WQRY1048E: Regenerate the datagraph and try it again. |
Explanation | WQRY1049E: DataGraph based on NO_DUMMY_ROOT pattern schema can have only one instance of root sdo. |
Action | WQRY1049E: Create mediator again with ejb query array which returns single root sdo. |
Explanation | WQRY1050E: Error ocurred when trying to identify inverse relationship. |
Action | WQRY1050E: Re-deploy the application and start again. |
Explanation | WQRY1051E: Error ocurred, when trying to get collection parameter object for this ASN. |
Action | WQRY1051E: Correct collection parameter object which passed to the query engine and re-try the query again. |
Explanation | WQRY1060E: Internal error encountered. |
Action | WQRY1060E: Restart your system. If the problem persists report the error to IBM service. |
Explanation | WQRY1061E: An internal error occurred. |
Action | WQRY1061E: See the problem determination information on the WebSphere Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | WQRY1062E: The static schema for EClass {0} does not have feature {1} defined. |
Action | WQRY1062E: Redefine the static schema or the mediator query. |
Explanation | WQRY1063E: Relationship is not updatable because it is not specified in the EJBMediator query. |
Action | WQRY1063E: Cannot update the relationship in the current datagraph. To update regenerate the datagraph by specifying the relationship in the mediator query. |
Explanation | WQRY1080E: Duplcate CMP names resulting in duplicate attributes in the DataGraph. This is not allowed in queries returning SDOs. |
Action | WQRY1080E: Try rename one of the duplicates by using AS syntax. For instance, select e.name, e.depSet.name as deptName from EmpBean e. |
Explanation | WQRY1081E: Union operation is not allowed in mediator query which returns sdos. |
Action | WQRY1081E: Remove union from the query. |
Explanation | WQRY1081E: Group by or having clause is not allowed in mediator query which returns sdos. |
Action | WQRY1081E: Remove group by or having clause from the query. |
Explanation | WQRY1083E: Subquery in select clause is not allowed in mediator query which returns sdos. |
Action | WQRY1083E: Remove subquery from the select clause. |
Explanation | WQRY1084E: Data object must be retrieved for linking the relationships. |
Action | WQRY1084E: Correct the query to include the related Data Object retrieval. |
Explanation | WQRY1085E: The SELECT statements must contain equal number of elements in the SELECT clauses for queries that retrieve the same Data Object type. |
Action | WQRY1085E: Correct the EJB query statement. |
Explanation | WQRY1086E: When the same Data Objects are retrieved in mediator queries, the CMP fields in all SELECT clauses must match. |
Action | WQRY1086E: Correct the mediator query statement. |
Explanation | WQRY1087E: The select clause in mediator query must contain CMP fileds or expressions that reference CMP fields. Constant expression is not allowed. |
Action | WQRY1087E: Correct the query statement. |
Explanation | WQRY1088E: Trying to update a field which may be the primary key or part of primary key. |
Action | WRY1088E: Correct the updates to the datagraph. |
Explanation | WQRY1090E: No such abstract schema name is defined in the metadata generated by a CMP/A deploy tool |
Action | WQRY1090E: Check your application and re-deploy your application with CMP/A deploy tool. |
Explanation | WQRY1091E: The Abstract Schema Name (ASN) specified in the FROM clause of the query is not defined in any of the installed applications. |
Action | WQRY1091E: Please make sure that the ASN name is correct or install the application that has the ASN name and resubmit the query. |
Explanation | WQRY1092E: The ASN specified in the FROM clause of the query is not defined in any of the installed applications. |
Action | WQRY1092E: Please make sure that the ASN name is correct or install the application that has the ASN name and resubmit the query. |
Explanation | WQRY1093E: The ASN specified in the FROM clause of the query is not defined in any of the installed applications. |
Action | WQRY1093E: Please make sure that the ASN name is correct or install the application that has the ASN name and resubmit the query. |
Explanation | WQRY1094E: The number of method arguments does not match with the one defined in the cmp/a push-down methods list. |
Action | WQRY1094E: Correct the query or add the method to the CMP/A push-down list. |
Explanation | WQRY1095E: The ASN specified in the FROM clause of the query is not defined in any of the installed applications. |
Action | WQRY1095E: Please make sure that the ASN is correct or install the application that has the ASN name and resubmit the query. |
Explanation | WQRY1096E: Invalid access intent is defined for the {0} ASN. |
Action | WQRY1096E: Correct the accessIntent, re-install the application, and try again. |
Explanation | WQRY1097E: The ASN specified in the FROM clause of the query is not defined in any of the installed applications. |
Action | WQRY1097E: Make sure that the ASN is correct or install the application that has the ASN name and resubmit the query. |
Explanation | WQRY1098E: Foreign key for the target relationship cannot be obtained. |
Action | WQRY1098E: Correct the CMP/A push down method in the user defined push down method implementation class and redeploy with CMP/A deploy tool. |
Explanation | WQRY1099E: Method arguments for CMP/A must be either litteral or ?. |
Action | WQRY1099E: Correct the method arguments and try again. |
Explanation | WQRY1100E: Associated keys for the traget relationship cannot be obtained. |
Action | WQRY1100E: Make sure that the ASN name is correct or install the application that has the ASN name and re-deploy the application with CMP/A deploy tool. |
Explanation | WQRY1101E: The cache entry for this ASN name cannot be obtained. |
Action | WQRY1101E: Correct the CMP/A push down method in the user defined push down method implementation class and redeploy with CMP/A deploy tool. |
Explanation | WQRY1102E: The cache entry for the ASN name cannot be obtained. |
Action | WQRY1102E: Correct the CMP/A push down method in the user defined push down method implementation class and redeploy with CMP/A deploy tool. |
Explanation | WQRY1103E: Failed to invoke the finder method on the concrete bean due to the wrong finder method name or argument. |
Action | WQRY1103E: Correct the CMP/A push-down finder method and re-deploy the application with a CMP/A deploy tool. |
Explanation | WQRY1104E: Method argument type is not compatible |
Action | WQRY1104E: Correct method arguments and re-deploy the application with a CMP/A deploy tool or re-enter correct method arguments in the query and try again. |
Explanation | WQRY1105E: Failed to invoke finder method on concrete bean due to the backend error. |
Action | WQRY1105E: Correct the finder method and re-deploy the application with a CMP/A deploy tool. |
Explanation | WQRY1106E: Failed to invoke remote finder method. |
Action | WQRY1106E: Correct finder method and re-deploy the application with a CMP/A deploy tool. |
Explanation | WQRY1107E: Method does not exist in the CMP/A push-down methods list. |
Action | WQRY1107E: Define the method and re-deploy the application with a CMP/A deploy tool or re-enter the correct method in the query and try again. |
Explanation | WQRY1110E: The ASN name cannot be null. |
Action | WQRY1110E: Correct the query and try again. |
Explanation | WQRY1111E: The CMP/A finder method can be used on WBI platform for a CMP/A type query only. |
Action | WQRY1111E: Verify the installation of WBI and re-deploy the application with a CMP/A deploy tool. |
Explanation | WQRY1112E: Character can only be compared to Character or String of length 1. |
Action | WQRY1112E: Correct the EJB query statement. |