Problem |
See message. |
Problem |
The SQL state is the standard JDBC error code for the reported problem. The vendor code is the database vendor specific error code. The message parameter is the localized error message that is returned by the relational database management system. |
Problem |
The data store stores metadata information in its database. This metadata information specifies how Common Base Event elements and attributes map to tables and columns in the database. Either an error occurred during the installation of the event database or the metadata table information is corrupted. |
Problem |
An event purge operation attempted to delete a large number of events. Because this action can adversely affect system performance and event throughput, the purge operation was stopped. |
User response |
To reduce the number of events to be purged in a single transaction, do one or all of the following actions: |
Problem |
An event query attempted to return a very large number of events. Because this action can adversely affect system performance and event throughput, the query operation was stopped. |
User response |
To reduce the number of events to be returned, do one or more of the following actions: |
Problem |
Each event instance must have a unique global instance identifier. |
User response |
Create the event with a unique global instance identifier. |
Problem |
See message. |
User response |
Try the operation again. |
Problem |
The WebSphere Application Server connection pooling system was not able to return a database connection using the current configuration of the connection pool and the configured number of retries. |
Problem |
The maxCacheEntries configuration parameter specifies how many translated event selector expressions can be cached by the data store. Caching translated event selector expressions improves the performance of the event query and the event purge because event selector expressions in the cache do not need to be parsed and translated to SQL. When the maxCacheEntries parameter is set to zero (0), no translated event selector expressions are cached. Therefore, each event selector expression specified in a call to the event query and the event purge methods must be parsed and translated to a valid SQL expression. |
Problem |
The data store uses resource references to obtain the data source that is used to obtain connections to the database and for the object that contains the configuration for the data store. The resource reference information specified during installation is not valid. For example, a JNDI name that is not valid was specified for the resource reference. If the specified resource reference name is java:comp/env/DefaultDataStoreProfileReference, the data store cannot access its configuration data. If the specified resource reference name is java:comp/env/EventDataSourceReference, the data store cannot access its data source. If the specified resource reference name is java:comp/env/ejb/DataStoreHelperEJB, the data store cannot access the data store helper enterprise java bean. |
Problem |
See message. |
User response |
Specify an event selector expression that contains only attributes and elements that are supported. |
Problem |
The most likely cause of this problem is specifying only a constant value as the predicate in an expression. |
User response |
Specify an event selector expression with a valid predicate expression. |
Problem |
The first argument of the function must either be a string constant or a location path that can be translated to a column in the event data store. The second argument of the function must be a string constant. The SQL equivalent to this function, the LIKE function, requires that the first argument be either a table column or a string constant and the second argument be a string constant. |
User response |
Specify a string constant or a location path that maps to a table column in the event database for the first argument of the function used in the event selector expression. Specify a string constant for the second argument of the function that is used in the event selector expression. This example shows a valid event selector expression using the starts-with function. |
Problem |
You must specify one argument for this function. |
User response |
Specify one argument for the function. |
Problem |
See message. |
Problem |
These are the expression types that are supported for this release: |
User response |
Specify an XPath expression that uses a supported expression type. |
Problem |
These are the are possible reasons for this exception: |
User response |
Specify a valid event selector expression. |
Problem |
See message. |
User response |
Specify an event selector expression with one predicate associated with the CommonBaseEvent element. For example, the following event selector expression returns a SQL expression that selects all events from the event database. For example, CommonBaseEvent[@globalInstanceId] |
Problem |
See message. |
User response |
Specify the function with a valid number of arguments. |
Problem |
Only numeric operands are supported for the following arithmetic operators: +, -, *, div, mod, <, >, <=, >= |
User response |
Specify two numeric values for this operation. The following example shows a valid event selector expression using the addition operation. |
Problem |
The most likely cause of this problem is using a numeric value for one operand and a string value that cannot be converted to a numeric value for the other operand. |
User response |
Specify operands with compatible types. The following example shows a valid event selector expression using the equality operation. Because the string value 10 can be converted to the numeric value 10, the operation is valid and the types are compatible. |
Problem |
See message. |
Problem |
See message. |
Problem |
See message. |
Problem |
See message. |
Problem |
The connection retries configuration setting specifies the number of times the data store attempts to obtain a database connection from the connection pool. If a connection cannot be obtained in the specified number of retries, the data store throws an exception. A value of 0 specifies that the data store does not retry the operation. |
Problem |
The query threshold configuration setting specifies the maximum number of events that can be returned by the queryEvents methods. This value must be 1 or greater. |
Problem |
The maximum purge transaction size configuration setting specifies the maximum number of events that can be deleted in a single purgeEvents call. This value must be 1 or greater. |
Problem |
These are the supported event selector expression operators: |
User response |
Specify an event selector expression operation that uses a supported operator. |
Problem |
See message. |
Problem |
The SQL state is the standard JDBC error code for the reported problem. The vendor code is the database vendor specific error code. The message parameter is the localized error message that is returned by the relational database management system. |
Problem |
When the values element is specified in an event selector expression, a corresponding event selector type must also be specified. |
User response |
Identify the event selector type of the values element specified in the event selector expression using the operator. A valid event selector expression referencing the values element looks similar to the following example. The operation on the values element and the type attribute expressions must be located within a predicate expression of an extendedDataElements element. |
Problem |
The XPath pattern-matching characters are not supported. |
User response |
Specify the XPath expression without using a XPath pattern-matching character. |
Problem |
Extended data element type attributes cannot be specified in conjunction with one another using the operator. |
User response |
Specify the event selector expression without using two extended data element type attributes that are conflicting. For example, the following event selector expression is not valid because the type attributes are conflicting. This expression is correctly rewritten as follows: |
Problem |
See message. |
User response |
Specify the event selector expression without using stacked predicates. For example, the following event selector expression is not valid because there are multiple predicates on the CommonBaseEvent element. This expression is correctly rewritten as follows: |
Problem |
See message. |
User response |
Specify a value for the function that matches at least one extended data element type. For example, the following event selector expression is valid because the starts-with function matches the int and intArray extended data element types. |
Problem |
The specified property value is being read from the cei_t_properties table. The value stored in the property_value column, which is a string, cannot be converted to an integer value. The contents of the cei_t_properties table can be reset to the default values by running the ins_metadata script. |
Problem |
The specified property value is being read from the cei_t_properties table. The value stored in the property_value column, which is a string, can be converted to an integer value, but the value is larger than the maximum allowed value. The contents of the cei_t_properties table can be reset to the default values by running the ins_metadata script. |
Problem |
The specified property value is being read from the cei_t_properties table. The value stored in the property_value column, which is a string, is converted to an integer value, but the value is smaller than the minimum allowed value. The contents of the cei_t_properties table are reset to the default values by running the ins_metadata script. |
Problem |
The CommonBaseEvent schema does not allow the severity attribute to be changed once it is set. An event update request was submitted that attempted to set the severity attribute on an event that already had a severity value. The calling application should be changed so that it does not attempt to set the severity attribute on the specified event. |
Problem |
An event update request specified an event that no longer exists in the database. This might occur if an event purge was performed. |
Problem |
All of the events in the inactive bucket must be purged before the active bucket can be switched. Use the fast purge to purge all the events in the inactive bucket. |
Problem |
The event database only contains one set of tables, a bucket, to store event data. Therefore, there is only an active bucket. The eventbucket.jacl script cannot be used to change the active bucket. |
Problem |
See message. |
Problem |
The Xpath expression for the parent extended data element is a valid Xpath expression and it does not refer to any existing extended data element instances. The calling application needs to be changed so that the Xpath expression refers to at least one extended data element in the event. |
Problem |
A required database table could not be found using the fully qualified SQL table name, which includes the user ID used to connect to the database. This indicates that a different user ID was used to create the event database, resulting in a different fully qualified table name. |
Problem |
A required database table could not be found using the fully qualified SQL table name, which includes the user ID used to connect to the database. This indicates that a different user ID was used to create the event database, resulting in a different fully qualified table name. |
Problem |
The specified metadata table maps Common Base Event elements and attributes to database tables and columns. This metadata is required for the default data store to operate. |
Problem |
The specified metadata table maps Common Base Event elements and attributes to database tables and columns. This metadata is required for the default data store to operate. |