CWLDB0002E
Failed to update schema for component "0".
CWLDB0004W
UpdateSchema Admin task is not supported for the process type "0".
CWLDB0006E
Failed to update schema for components "0".
CWLDB0007E
Schema was updated successfully for components "0", but failed for components "1".
CWLDB0009E
Failed to update schema. This is because the SQL script "0" could not be found. Here is the error message reported by the system "1".
CWLDB0010E
Failed to update schema for component "0" to new version "1". An attempt was made to execute the SQL script "2" and that ran into an SQL error. Here is the error message reported by the system "3".
CWLDB0011E
Failed to update schema for component "0" to new version "1". An attempt was made to execute the SQL script "2" and that ran into an input/out system error. Here is the error message reported by the system "3".
CWLDB0012E
Failed to update schema. It seems the DB does not support transaction. Here is the error message reported by the system "0".
CWLDB0013E
Failed to update schema. The migration config file "0" miss. Here is the error message reported by the system "1".
CWLDB0014E
Failed to update schema. There are some syntax errors in the config file "0". Here is the error message reported by the system "1".
CWLDB0015E
Error occured while starting application "0". Here is the error message reported by the system "1".
CWLDB0016E
Common Database schema update not supported for WESB version 0.
CWLDB0017E
Common Database schema update not supported for WPS version 0.
CWLDB9012E
Creating cluster member 0 failed. Reason: 1.
CWLDB9013I
Configuring component 0 on deployment target 1.
CWLDB9014E
The configuration of component 0 failed. Reason 1.
CWLDB9015I
Deployment environment 0 is being generated.
CWLDB9016E
The generation for deployment environment 0 failed. Reason: 1. If in doubt, discard the changes and do not save the failed configuration to the master repository.
CWLDB9017W
Deployment environment 0 did not start completely. Reason: 1
CWLDB9018E
Deployment environment 0 failed to start. Reason: 1
CWLDB9019W
Deployment environment 0 did not stop completely. Reason 1
CWLDB9020E
Deployment environment 0 failed to stop. Reason 1
CWLDB9036W
Deployment environment definition 0 is not found.
CWLDB9037W
Deployment environment definition 0 has already been configured. The operation 1 cannot be executed.
CWLDB9038I
Successfully renamed the node from 0 to 1;
CWLDB9039I
Successfully renamed the deployment environment definition from 0 to 1;
CWLDB9040W
Node 0 cannot be found in deployment environment definition 1;
CWLDB9041I
The CEI destination on server 0 and node 1 will be configured with Event Infrastructure emitter factory JNDI name 2.
CWLDB9042I
The CEI destination on cluster 0 will be configured with Event Infrastructure emitter factory JNDI name 1.
CWLDB9043W
The Common Event Infrastructure server deployment target is not valid. It is a single server 0 that has no node or more than one node defined.
CWLDB9044W
Deployment environment definition 0 cannot be created because WebSphere Business Monitor does not support multiple deployment environments in a single cell.
CWLDB9045W
The 0 node cannot be renamed because it cannot be found in the 1 topologyRole.
CWLDB9046W
The 0 node cannot be removed because it cannot be found in the 1 topologyRole.
CWLDB9047W
The 0 topologyRole cannot be found in the topology.
CWLDB9048E
The 0 deployment environment cannot be exported because the 1 directory already exists. The directory cannot be overwritten because the overwrite option is set to false.
CWLDB9049E
The node cannot be added to topology deployment environment, because more than one topology is in the cell.
CWLDB9050W
The 0 role is not synchronized with the 1 deployment target.
CWLDB9051E
Updating the port 0 of cluster member 1 failed. Reason: 2.
CWLDB9051W
Deployment environment 0 is successfully generated.
CWLDB9100W
The 0 component type cannot be configured for the 1 deployment environment.
CWLDB9101E
The 0 component type cannot be used more than once for the 1 deployment target for the 2 deployment environment.
CWLDB9102E
The component "0" has a dependency on component "1" that has not yet been configured for topology "2".
CWLDB9103E
The 0 component has not been configured for the 1 deployment environment.
CWLDB9104E
The 0 component configuration of the 1 type cannot be removed because it is used by the 2 component configuration in the 3 deployment environment.
CWLDB9105E
The 0 component configuration of the 1 type cannot be removed because it is configured in the 2 deployment environment.