Licensed Materials - Property of IBM (C)Copyright IBM Corporation 2004, 2005. All Rights Reserved US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. The specified relational database management system is not supported.
Database: rdbms_name
Version: rdbms_version

See message.

Reconfigure the common event infrastructure data source to use a supported relational database management system.

The relational database management system reported the following error.
Data source resource reference: data_source
SQL state: sql_state
Vendor code: vendor_code
Message: message

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.

Refer to the appropriate relational database documentation for information about the SQL state, the vendor code, and the error message.

The mapping of a Common Base Event element or attribute to database tables and columns cannot be found.
Attribute: attribute_name

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.

Install the event database again.

The data store is connecting to the specified relational database management system.
Database: rdbms_name
Version: rdbms_version The maximum purge transaction size purge_threshold has been exceeded. The purge operation has been stopped, the transaction has been rolled back, and no events have been purged.

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.

To reduce the number of events to be purged in a single transaction, do one or all of the following actions:

Add additional filters to the purge event selector expression.
Set the maximum purge transaction size to a lower value.

The query threshold query_threshold has been exceeded. The query operation has been stopped and no events have been returned.

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.

To reduce the number of events to be returned, do one or more of the following actions:

Add additional filters to the event selector expression for the query.
Specify the maximum number of events to be returned.
If you have sufficient system resources, increase the query threshold value.

An event with the global instance identifier, global_id , already exists in the database. The event was not stored in the database.
Existing event: old_event
New event: new_event

Each event instance must have a unique global instance identifier.

Create the event with a unique global instance identifier.

The WebSphere Application Server connection pooling system returned a database connection that is no longer valid.
Data source resource reference: data_source

See message.

Try the operation again.

A database connection could not be obtained from the connection pool after maximum_retries attempts to obtain a connection.
Data source resource reference: data_source

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.

Do one or more of the following actions:

Reconfigure the data source, increasing the maximum number of connections. This option improves performance and event throughput.
Reconfigure the data source, increasing the connection time out value.
In the data store profile, increase the number of retries.

The maxCacheEntries configuration parameter must be greater than or equal to minimum_cache_entries. However, maximum_cache_entries was specified. The maxCacheEntries value has been set to new_cache_entries .

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.

In the data store profile, set the maxCacheEntries value to zero (0) or greater.

The data store cannot find the resource reference in JNDI.
Resource reference: resource_reference_name

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.

In the WebSphere Administrative Console, reconfigure the specified resource reference to a valid JNDI resource.

The attribute or element name specified in the event selector expression expression is not supported.

See message.

Specify an event selector expression that contains only attributes and elements that are supported.

The predicate expression specified in the event selector expression, expression, is not valid, and it could not be translated to a valid SQL expression.

The most likely cause of this problem is specifying only a constant value as the predicate in an expression.

Specify an event selector expression with a valid predicate expression.

The function function used in the event selector expression, expression, has an argument that is not valid. 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.
Argument: argument

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.

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.

CommonBaseEvent[starts-with(@msg,'My message')]

No arguments were specified for a function used in the event selector expression.
Event selector expression: expression
Function: function

You must specify one argument for this function.

Specify one argument for the function.

The function used in the event selector expression is not supported.
Event selector expression: expression
Function: function

See message.

Specify an event selector expression that uses a supported function.

The XPath expression type specified in the event selector expression is not supported.
Expression type: expression_type
Event selector expression: expression

These are the expression types that are supported for this release:

Constant
```
1,2,'thisString'
```
Location Path
```
CommonBaseEvent[@severity=10]
```
Operation
```
@severity+10=20
```
Function
```
contains(@msg)
```

Specify an XPath expression that uses a supported expression type.

The event selector expression expression is not valid. The event selector parsing tool returned the following message: message

These are the are possible reasons for this exception:

A predicate bracket is not closed. For example, CommonBaseEvent[@severity='10 is missing a closing bracket, and it should be specified as CommonBaseEvent[@severity='10'].
A function has the wrong number of arguments. For example, the starts-with and the contains function require two arguments.
A quote on a string constant is not closed. For example, CommonBaseEvent[@severity='10] is missing a closing quote, and it should be specified as CommonBaseEvent[@severity='10'].
An open parenthesis is not closed. For example, CommonBaseEvent[(@severity+10=20] is missing a closing parentheses, and it should be specified as CommonBaseEvent[(@severity+10)=20].
A string constant that is not contained by quotes. For example, CommonBaseEvent[@creationTime=2003-12-31T12:00:00Z] is missing quotes around the date time sting, and it should be specified as CommonBaseEvent[@creationTime='2003-12-31T12:00:00Z'].

Specify a valid event selector expression.

The event selector expression expression is not valid. The CommonBaseEvent element does not have an associated predicate.

See message.

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]

The function function used in the event selector expression, expression, is specified with an incorrect number of arguments. The function should be specified with number_of_arguments arguments.

See message.

Specify the function with a valid number of arguments.

The arithmetic operation contains an operand that is not a numeric value.
Operation: operation

Only numeric operands are supported for the following arithmetic operators: +, -, *, div, mod, <, >, <=, >=

Specify two numeric values for this operation.

The following example shows a valid event selector expression using the addition operation.

CommonBaseEvent[@severity = 10 + 1]

The operation contains operands that are not compatible.
Operation: operation

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.

Specify operands with compatible types.

The following example shows a valid event selector expression using the equality operation.

CommonBaseEvent[@severity = '10']

Because the string value 10 can be converted to the numeric value 10, the operation is valid and the types are compatible.

An error occurred when writing the CommonBaseEvent any element to the database. The operation was stopped.
Event: event

See message.

An error occurred when reading the CommonBaseEvent any element from the database. The operation was stopped.
Global instance identifier: global_id

See message.

An error occurred when writing a CommonBaseEvent extended data element that has a hexBinary data type to the database. The operation was stopped.
Event: event

See message.

An error occurred when reading a CommonBaseEvent extended data element that has a hexBinary data type from the database. The operation was stopped.
Global instance identifier: global_id

See message.

The configuration value for connection retries, connection_retries_old_value, is not valid. The value has been changed to connection_retries_new_value.

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.

In the data store profile, set the connection retries value to 0 or greater.

The configuration value for query threshold, query_threshold_old_value, is not valid. The value has been changed to query_threshold_new_value.

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.

In the data store profile, set the query threshold value to 1 or greater.

The maximum purge transaction size, purge_threshold_old_value, is not valid. The value has been changed to purge_threshold_new_value.

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.

In the data store profile, set the maximum purge transaction size to 1 or greater.

The operator used in the the event selector expression operation operation is not supported.

These are the supported event selector expression operators:

+,-,*, div, mod
=, !=, <, >, <=, >=
and, or

Specify an event selector expression operation that uses a supported operator.

The implementation class that supports the configured relational database system cannot be loaded.
Implementation class name: class_name
Relational database name: rdbms_name
Database version: rdbms_version

See message.

Ensure that the specified implementation class is in the CLASSPATH.

The relational database management system reported the following error.
Data source resource reference: data_source
Database product: rdbms_name
Database version: rdbms_version
SQL state: sql_state
Vendor code: vendor_code
Message: message

Refer to the appropriate relational database documentation for information about the SQL state, the vendor code, and the error message.

The values element is referenced in the specified event selector expression, expression, without specifying a corresponding extended data element type.

When the values element is specified in an event selector expression, a corresponding event selector type must also be specified.

Identify the event selector type of the values element specified in the event selector expression using the and operator.

A valid event selector expression referencing the values element looks similar to the following example.

CommonBaseEvent[extendedDataElements[values=1 and @type='intArray' ]]

The and operation on the values element and the type attribute expressions must be located within a predicate expression of an extendedDataElements element.

The XPath pattern-matching character character that is used in the specified event selector expression, expression, is not supported.

The XPath pattern-matching characters are not supported.

Specify the XPath expression without using a XPath pattern-matching character.

The type attribute used in the event selector expression, expression, conflicts with another type attribute that has already been specified.

Extended data element type attributes cannot be specified in conjunction with one another using the and operator.

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.

CommonBaseEvent[extendedDataElements[values=1 and @type='intArray' and @type='float']]

This expression is correctly rewritten as follows:

CommonBaseEvent[extendedDataElements[values=1 and @type='intArray'] and extendedDataElements[@type='float']]

The event selector expression, expression, was specified with stacked predicates. Stacked predicates are not supported.

See message.

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.

CommonBaseEvent[@severity=10][@priority=10]

This expression is correctly rewritten as follows:

CommonBaseEvent[@severity=10 and @priority=10]

The parameter value function_parameter specified for the function xpath_function in the event selector expression expression does not match any known extended data element types.

See message.

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.

CommonBaseEvent[extendedDataElements[starts-with(@type,'int')]]

The current bucket is being changed from bucket old_bucket to bucket new_bucket. The value property_value for the property property_name cannot be converted to an integer. The default value of default_value is used.

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.

The value property_value for the property property_name is greater than the maximum allowed value of maximum_value. The default_value default value is used.

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.

The value property_value for the property property_name is less than the minimum allowed value of minimum_value. The default value default_value is used.

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.

The property property_name cannot be found. The default value default_value is used. A fast purge is in progress. Only the active bucket is accessed. The active bucket is active_bucket. Querying the database for the event with the global_id ID in the search_bucket bucket. The bucket is bypassed because the fast purge is in progress. The severity attribute for the event with the global instance ID of global_id cannot be set to new_severity_value because it is already set to old_severity_value.

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.

Events cannot be inserted into the bucket_number bucket because it is not active. The events are inserted into the active bucket. The active bucket is active_bucket. The event with the global instance ID of global_id cannot be updated because it does not exist in the database.

An event update request specified an event that no longer exists in the database. This might occur if an event purge was performed.

The current active bucket cannot be changed from bucket active_bucket to bucket new_bucket because bucket new_bucket still contains event data.

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.

The event database is configured to only use one bucket. The current active bucket cannot be changed.

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.

Number of buckets: number_buckets
Current bucket: active_bucket
Bucket check interval (seconds): bucket_check_interval The database schema is not compatible with the default data store. The database schema version is actual_schema_version. the required version is required_schema_version.

See message.

The database schema version is actual_schema_version. The parent location path parent_location_xpath in the event update request for event with global instance ID global_id does not refer to any extended data element instances in the event. The event update request cannot be performed.

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.

Database table table_name does not exist for schema schema_name. The default data store is unable to start.
Data source resource reference: data_source

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.

The user ID used to connect to the database at run time must be the same as the user ID that was used to create the database. Change the connection information in the data source so that the correct user ID is specified.

Database table table_name does not exist. The default data store is unable to start.
Data source resource reference: data_source

Metadata table table_name in schema schema_name is empty. The default data store is unable to start.
Data source resource reference: data_source

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.

Run the ins_metadata script to create the required metadata table. This script is used to populate the metadata table when the event database is created, and it can safely be run multiple times.

Metadata table table_name is empty. The default data store is unable to start.
Data source resource reference: data_source

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.

Run the ins_metadata script to create the required metadata table. This script is used to populate the metadata table when the event database is created, and it can safely be run multiple times.