You may see these messages if errors are generated by the Replication
Manager.
- CWMRM0000E - No message text has been found for the message identifier message
identifier.
- Explanation
- A message without message text was issued.
- Action
- Report the message number to IBM® Support.
- CWMRM0001E - An invalid parameter parameter name with
value parameter value has been detected in method or constructor method
name.
- Explanation
- The program detected an incorrect parameter and stopped processing. The
cause may be incorrect input values, like configuration settings.
- Action
- Contact IBM Support.
- CWMRM0002E - No Business Measures model has been passed to Replication
Manager.
- Explanation
- The Schema Generator invokes the Replication Manager component that generates
the Data Movement Service setup artifacts. You have not provided all the required
information so generation cannot proceed.
- Action
- If the Schema Generator displayed any error messages before this one,
resolve the problem and retry the generation. If there are no prior error
messages, contact IBM Support.
- CWMRM0003E - No configuration information has been passed to Replication
Manager.
- Explanation
- The Schema Generator invokes the Replication Manager component that generates
the Data Movement Service setup artifacts. You have not provided all the required
information so generation cannot proceed.
- Action
- If the Schema Generator displayed any error messages before this one,
resolve the problem and retry the generation. If there are no prior error
messages, contact IBM Support.
- CWMRM0004E - No table space configuration information has been passed
to Replication Manager.
- Explanation
- The Schema Generator invokes the Replication Manager component that generates
the Data Movement Service setup artifacts. You have not provided all the required
information so generation cannot proceed.
- Action
- If the Schema Generator displayed any error messages before this one,
resolve the problem and retry the generation. If there are no prior error
messages, contact IBM Support.
- CWMRM0005E - Replication Manager failed to process model business
measures model name due to a fatal error.
- Explanation
- An error occurred when the Replication Manager attempted to process the
model.
- Action
- Inspect the log file for any previous error messages that describe the
exact error condition. If the error was caused by a mistake in configuration
or an incorrect business measures model, then resolve the problem and retry
the generation. If the problem is not resolved, contact IBM Support. Do
not attempt to deploy any artifacts that may have been placed into the output
directory by the Schema Generator component or the Replication Manager component.
- CWMRM0009W - Replication Manager has finished processing, but generated
one or more warnings. Database setup artifacts have been created.
- Explanation
- At least one warning message has been issued by the Replication Manager
while processing the deployment artifact generation. Depending on the nature
of the warning, the generated artifacts may or may not be valid.
- Action
- Inspect the log file carefully for any warning messages before this message.
Warnings may have been caused by incorrect or missing configuration options
(leading to the use of default values), business-measures-model-related issues
(such as restrictions not enforced by the Business Measures editor),
or other recoverable conditions. Do not deploy the generated artifacts until
you know whether the reason for the warning does not affect the validity of
the generated artifacts. If necessary and possible, try to resolve the cause
and redo the generation. Contact IBM Support if you are unsure of how to
proceed.
- CWMRM0010W - Replication Manager has finished processing, but generated
one or more warnings. No database setup artifacts have been created.
- Explanation
- At least one warning message has been issued by the Replication Manager
while processing the deployment artifact generation. This warning indicates
that no deployment artifacts have been generated. The cause may or may not
be the reason that no artifacts were generated.
- Action
- Inspect the log file carefully for any warning messages before to this
message. Warnings may have been caused by incorrect or missing configuration
options (leading to the use of default values), business-measures-model-related
issues (such as restrictions not enforced by the Business Measures editor),
or other recoverable conditions. The cause of the warning may be unrelated
to the fact that no artifacts were generated. For example, no artifacts might
have been generated because no significant changes were found for the model.
Contact IBM Support
if you are unsure of how to proceed.
- CWMRM0011E - Replication Manager has failed during processing. No
database setup artifacts have been created.
- Explanation
- An error occurred while the Replication Manager was generating deployment
artifacts. The error may or may not be the reason that no deployment artifacts
were created.
- Action
- Inspect the log file for any error and warning messages before this message.
If the problem was caused by an incorrect configuration, an environment setup
problem, or a constraint that has not been enforced by the Schema Generator
or the Business Measures editor, resolve the
problem if possible and redo the generation. Contact IBM Support if you cannot resolve the problem.
Never deploy any artifacts generated by the Schema Generator if the Replication
Manager reports any errors.
- CWMRM0016E - A fatal error has occurred while processing model business
measures model name.
- Explanation
- An unrecoverable error occurred while the Replication Manager was generating
deployment artifacts. The log file contains additional information on the
cause of the error.
- Action
- Inspect the log file for any error and warning messages before this message.
If the problem was caused by an incorect configuration, an environment setup
problem, or a constraint that has not been enforced by the Schema Generator
or the Business Measures editor, resolve the
problem if possible and redo the generation. Contact IBM Support if you cannot resolve the problem.
- CWMRM0026E - A negative Business Measures model version number was
passed to Replication Manager.
- Explanation
- A version number is assigned to each business measures model to indicate
changes. The version number is either 0 (the first time a model is processed)
or greater, but never negative. The Schema Generator instructed the Replication
Manager to treat the current model as a version with an incorrect (negative)
number.
- Action
- Inspect the log file for any Schema Generator error and warning messages
before this message. If the problem was caused by an incorrect configuration,
an environment setup problem, or a user error, resolve the problem if possible
and redo the generation. Contact IBM Support if you cannot resolve the problem.
- CWMRM0800E - Loading of Replication Manager model from file file
name has generated fatal errors: error message.
- Explanation
- The Replication Manager saves internal information about business measures
models in the file system. Loading of a file containing such information failed.
- Action
- Contact IBM Support.
- CWMRM0801W - Loading of Replication Manager model from file file
name has generated warnings: warning message.
- Explanation
- The Replication Manager saves internal information about business measures
models in the file system. Loading of a file containing such information generated
warnings.
- Action
- Contact IBM Support.
- CWMRM0803E - A fatal error has occurred while loading Replication Manager
model from file file name.
- Explanation
- The Replication Manager saves internal information about business measures
models in the file system. An error occurred while a file containing such
information was being loaded. This message is followed by additional information
about the error.
- Action
- Contact IBM Support.
- CWMRM0805E - A fatal error occurred while saving Replication Manager
output model business measures model name to file file name.
- Explanation
- The Replication Manager saves internal information about business measures
models in the file system. An error occurred while a file containing such
information was being loaded. This message is followed by additional information
about the error.
- Action
- If the problem was caused by insufficient disk space or privileges, make
the necessary corrections. Otherwise, contact IBM Support.
- CWMRM0806E - A fatal error has occurred while saving Replication Manager
input model business measures model name to file file name.
- Explanation
- The Replication Manager saves internal information about business measures
models in the file system. An error occurred while a file containing such
information was being saved. This message is followed by additional information
about the error.
- Action
- If the problem was caused by insufficient disk space or privileges, make
the necessary corrections. Otherwise, contact IBM Support.
- CWMRM0808E - A fatal error has occurred while trying to copy Replication
Manager input model business measures model name.
- Explanation
- The Replication Manager saves internal information about business measures
models in the file system. An error occurred while copying such a file. This
message is followed by additional information about the error.
- Action
- If the problem was caused by insufficient disk space or privileges, make
the necessary changes. Otherwise contact IBM Support.
- CWMRM0809E - A Replication Manager metadata repository corruption has
been detected. Entry invalid repository entry text is not valid.
- Explanation
- The Replication Manager detected incorrect metadata in its repository
either while loading or storing it.
- Action
- Contact IBM Support.
- CWMRM0810E - A fatal error has occurred while saving the Replication
Manager repository: error message.
- Explanation
- The Replication Manager detected incorrect metadata when trying to save
its repository content.
- Action
- Contact IBM Support.
- CWMRM0811E - A fatal error has occurred while saving the Replication
Manager repository. See previous log entry for details.
- Explanation
- The Replication Manager detected incorrect metadata when trying to save
its repository content.
- Action
- The log file contains at least one more error entry before this one indicating
the cause of the problem. Contact IBM Support.
- CWMRM0812E - An attempt has been made to store an incomplete or invalid
Replication Manager metadata repository entry for Business Measure model business
measures model.
- Explanation
- The Replication Manager detected incorrect metadata when trying to save
its repository content.
- Action
- Contact IBM Support.
- CWMRM0813E - Unable to save Replication Manager model because no metadata
directory has been defined.
- Explanation
- The Replication Manager could not determine where to store its metadata
information in the file system.
- Action
- Make sure the installation completed successfully. If no setup errors
were reported, contact IBM Support.
- CWMRM0814E - A fatal error has occurred while loading the Replication
Manager repository: error message.
- Explanation
- The Replication Manager could not load its metadata from the file system
because of the indicated error.
- Action
- Contact IBM Support.
- CWMRM0815E - A Replication Manager metadata repository corruption
has been detected. Key invalid repository key is not valid.
- Explanation
- While metadata information was being loaded from the file system, a potential
corruption was detected. Schema generation will not be performed until the
metadata information has been corrected manually.
- Action
- Contact IBM Support.
- CWMRM0816E - A Replication Manager metadata repository corruption has
been detected. Key repository key refers to an invalid file named invalid
file name.
- Explanation
- While metadata information was being loaded from or stored into the file
system, a potential corruption was detected. The identified piece of metadata
references a file that does not exist or is a directory. Schema generation
will not be performed until the metadata information has been corrected manually.
- Action
- Contact IBM Support.
- CWMRM0817E - The loading of Replication Manager metadata repository
has been cancelled.
- Explanation
- A metadata corruption has been detected while the repository was being
loaded into memory. The log contains one or more CWMRM0818E messages that
indicate the model for which corrupted entries have been encountered. Schema
generation will not be performed until the metadata information has been corrected
manually.
- Action
- Contact IBM Support.
- CWMRM0818E - A Replication Manager metadata repository corruption has
been detected for model business measures model name.
- Explanation
- A metadata corruption for the indicated model has been detected while
the repository was being loaded into memory. Schema generation will not be
performed until the metadata information has been corrected manually.
- Action
- Contact IBM Support.
- CWMRM0819W - Replication Manager repository information repository
key=repository value is not associated with a model. The information will
be discarded.
- Explanation
- A potentially incomplete piece of metadata has been detected while the
repository was being loaded into memory. Because it cannot be associated with
any business measures model, it will be discarded. This condition is a warning
and does not cause schema generation to stop.
- Action
- No immediate action is necessary.
- CWMRM0820E - A Replication Manager metadata repository corruption has
been detected. Models business measures model name and business
measures model name share the same logical repository identifier unique
repository identifier.
- Explanation
- A unique internal identifier is assigned internally to each business
measures model. While the repository information was being loaded from the
file system, two model entries with identical identifiers were read. No schema
generation will be performed until the metadata information has been corrected
manually.
- Action
- Contact IBM Support.
- CWMRM0821E - A Replication Manager metadata repository corruption has
been detected. Model business measures model name has been assigned
to repository identifier unique repository identifier and unique
repository identifier.
- Explanation
- A unique internal identifier is assigned internally to each business measures
model. While the repository information was being loaded from the file system,
it was discovered that two identifiers were assigned to the same model. No
schema generation will be performed until the metadata information has been
corrected manually.
- Action
- Contact IBM Support.
- CWMRM0900E - The initialization of Replication Manager has failed. The
installation directory directory name does not exist.
- Explanation
- Upon startup, the Replication Manager validates that some of its mandatory
files are present in the installation directory. The Schema Generator notifies
the Replication Manager where these files should be located in the file system.
The specified directory does not exist or is not a directory.
- Action
- Make sure the installation completed successfully.
- CWMRM0901E - The initialization of Replication Manager has failed.
The template archive file named JAR file name could not be located
in directory directory name.
- Explanation
- Upon startup, the Replication Manager validates that some of its mandatory
files are present in the installation directory. The specified Java™ archive
does not exist.
- Action
- Make sure the installation completed successfully.
- CWMRM0902E - The initialization of Replication Manager has failed.
Configuration file named config file name could not be located in directory directory
name.
- Explanation
- Upon startup, the Replication Manager validates that some of its mandatory
files are present in the installation directory. The specified Java archive
does not exist.
- Action
- Make sure the installation completed successfully.
- CWMRM0903E - The initialization of Replication Manager has failed. Unable
to create Replication Manager metadata directory directory name.
- Explanation
- Upon startup, the Replication Manager validates that its metadata directory
exists. If it does not, an attempt will be made to create it. This error will
be raised if the directory cannot be created.
- Action
- Make sure that the user ID running the Schema Generator utilities has
write access privileges in the installation directory.
- CWMRM0904E - The initialization of Replication Manager has failed. Unable
to create Replication Manager work directory directory name.
- Explanation
- Upon startup, the Replication Manager validates that its work directory
exists. If it does not, an attempt will be made to create it. This error will
be raised if the directory cannot be created.
- Action
- Make sure that the user ID running the Schema Generator utilities has
write access privileges in the parent directory of the directory name and
that no file with an identical name already exists.
- CWMRM0905E - The initialization of Replication Manager has failed due
to the following error: error message
- Explanation
- An error occurred during Replication Manager initialization.
- Action
- The most common initialization problems are identified by their own messages.
A problem has occurred that is not covered by any of the specific messages.
Contact IBM Support.
- CWMRM1002E - Failure creating/cloning model object of type internal
data type name.
- Explanation
- The Replication Manager maintains internal models that represent the business
measures models for which deployment artifacts are to be created. The creation
of an internal model object failed.
- Action
- A potential cause could be the lack of available memory. Make sure you
have enough resources allocated.
- CWMRM1005E - A fatal error has occurred while updating model business
measures model. Error message.
- Explanation
- An error occurred while the Replication Manager was building or updating
its internal model. The error is described by error message.
- Action
- There are a number of potential error conditions. Contact IBM Support.
- CWMRM1006E - A fatal error has occurred while creating core model objects
for model business measures model. Error message
- Explanation
- An error occurred while the Replication Manager was creating its internal
base model. The error is described by error message.
- Action
- There are a number of potential error conditions. Contact IBM Support.
- CWMRM1010E - A constraint violation has been detected in input model.
Table table name in database database name does not contain
any columns.
- Explanation
- Based on the business measures model, the Schema Generator creates logical
database-table definitions. A table definition does not contain any columns,
a condition not allowed in relational databases.
- Action
- Contact IBM Support.
There may be a problem with how the business measures model is mapped onto
database structures.
- CWMRM1011E - A constraint violation has been detected in input model.
Table table name in database database name contains multiple
columns named column name.
- Explanation
- Based on the business measures model, the Schema Generator creates logical
database-table definitions. A table definition contains two columns with identical
names. Identical column names are not allowed in relational databases.
- Action
- Contact IBM Support.
There may be a problem with how the business measures model is mapped onto
database structures.
- CWMRM1013E - A fatal error has occurred during the creation of Capture
model objects for service Data Movement Service name. Error message.
- Explanation
- The Replication Manager maintains internal models that represent the business
measures models for which deployment artifacts are to be created. The creation
of an internal model object representing a Capture component instance failed.
The Error message gives more information about the failure.
- Action
- Contact IBM Support.
- CWMRM1014E - A fatal error has occurred during the creation of Apply
model objects for service Data Movement Service name. Error message.
- Explanation
- The Replication Manager maintains internal models that represent the business
measures models for which deployment artifacts are to be created. The creation
of an internal model object representing an Apply component instance failed.
Details can be found in the error message.
- Action
- Contact IBM Support.
- CWMRM1015E - A fatal error has occurred during the creation of a subscription
set model object associated with Apply Apply component instance name. Error
message.
- Explanation
- The Replication Manager maintains internal models that represent the business
measures models for which deployment artifacts are to be created. The creation
of an internal model object representing an Apply component instance failed.
Details can be found in the error message.
- Action
- Contact IBM Support.
- CWMRM1016E - A fatal error has occurred during the creation of an Apply
related model object associated with table database table name and
Subscription Set subscription set name. Error message
- Explanation
- The Replication Manager maintains internal models that represent the business
measures models for which deployment artifacts are to be created. The creation
of an internal model object representing a database table to which changes
are to be applied failed. Details can be found in the error message.
- Action
- Contact IBM Support.
- CWMRM1017E - Invalid model has been detected during ETL setup. Multiple
source table mappings have been detected for table database table name in
database database name. This is not allowed in the current release.
- Explanation
- A table in the Runtime and Historical database can only be populated using
a single source table during ETL processing. The Schema Generator created
a logical model that violates this constraint.
- Action
- Contact IBM Support.
There may be a problem with how the business measures model is mapped onto
database structures.
- CWMRM1018E - Invalid model has been detected during ETL setup. The mapping
information for table database table name in database database name is
ambiguous.
- Explanation
- The Schema Generator created a logical model that contains ambiguous information
about how table data is mapped to another table data.
- Action
- Contact IBM Support.
There may be a problem with how the business measures model is mapped onto
database structures.
- CWMRM1019W - The data type data type name of source column column
name in table database table name in database database name does
not match data type data type name of target column column name in
table database table name in database database name. This may
cause failures during ETL processing.
- Explanation
- Tables in the Runtime and Historical database contain data that is derived
from data in the State or Runtime database. There may be a problem if the
data types or length between source database (State or Runtime) and target
database (Runtime or Historical) are different. For example, a character column
in the source database may be longer than the related character column in
the target database. In this scenario, data may be truncated.
- Action
- Modify your measures definitions in your business measures model to avoid
problems.
- CWMRM1020E - A failure has occurred while loading table space properties.
Database tables cannot be assigned to table spaces.
- Explanation
- During schema generation, database tables are assigned to table spaces,
based on a configuration file containing the mappings of table type to table
space names. If configuration-file load errors were ignored, all tables would
be assigned to the same databases default table space, seriously affecting
performance. Raising this error prevents this problem.
- Action
- Verify that the table-space configuration file that you specified has
a valid structure, and then rerun schema generation.
- CWMRM1021E - Invalid model has been detected during ETL setup. The mapping
information for table database table name in database database name is
inconsistent.
- Explanation
- A table in the Runtime and Historical database can only be populated using
a single source table during ETL processing. The Schema Generator created
a logical model that violates this constraint because of inconsistent mapping
information.
- Action
- Contact IBM Support.
- CWMRM1022E - Invalid model has been detected during ETL setup. Table database
table name in database database name does not contain any metrics.
- Explanation
- Each database table for which replication needs to be set up must contain
at least one metric. The Schema Generator created a logical model that violates
this constraint. The most likely cause is the business measures input model.
- Action
- Make sure that your business measures model is valid.
- CWMRM1023E - Invalid model has been detected during ETL setup. No valid
source table mapping could be found for table database table name
in database database name. The join predicate is missing.
- Explanation
- To populate tables in the Runtime and Historical databases, the ETL process
determines where to obtain the source data from and how to map it. A mandatory
piece of information is missing in the logical input model created by the
Schema Generator.
- Action
- Contact IBM Support.
- CWMRM1024E - Invalid model has been detected during ETL setup. No valid
source table mapping could be found for table database table name in
database database name. The SQL fragment is missing.
- Explanation
- To populate tables in the Runtime and Historical databases, the ETL process
determines where to obtain the source data from and how to map it. A mandatory
piece of information is missing in the logical input model created by the
Schema Generator.
- Action
- Contact IBM Support.
- CWMRM1025E - Invalid model has been detected during ETL setup. No source
table mapping could be found for table database table name in database database
name.
- Explanation
- To populate tables in the Runtime and Historical databases, the ETL process
determines where to obtain the source data from and how to map it. A mandatory
piece of information is missing in the logical input model that was created
by the Schema Generator.
- Action
- Contact IBM Support.
- CWMRM1300E - A fatal error has occurred while processing Apply related
model updates for tables located in database database name. The Active
Business Measures Group identifier is internal business measures group
name and updates have been processed for Service Data Movement Service
name.
- Explanation
- An error occurred while an Apply component instance for the indicated
business measures group was being created or updated in the internal model.
- Action
- Contact IBM Support.
- CWMRM1301E - Model inconsistency has been detected during Apply setup.
A duplicate entry for table database table name has been found for
Apply named Apply component instance name and Subscription Set named Subscription
Set name.
- Explanation
- An error occurred while an Apply component instance for the indicated
business measures group was being created or updated in the internal model.
- Action
- Contact IBM Support.
- CWMRM1302E - Model inconsistency has been detected during Apply setup.
No entry for table database table name has been found for Apply named Apply
component instance name and Subscription Set named Subscription Set
name.
- Explanation
- An error occurred while an Apply component instance for the indicated
business measures group was being created or updated in the internal model.
- Action
- Contact IBM Support.
- CWMRM1600E- A fatal error has occurred while processing Capture related
model updates for tables located in database database name. The Active
Business Measures Group identifier is internal business measures group
name and updates have been processed for ServiceData Movement Service
name.
- Explanation
- An error occurred while a Capture component instance for the indicated
business measures group was being created or updated in the internal model.
- Action
- Contact IBM Support.
- CWMRM1601E - Model inconsistency has been detected during Capture setup.
A duplicate entry for table database table name has been found for
Capture named Capture component instance name.
- Explanation
- An error occurred while a Capture component instance for the indicated
business measures group was being created or updated in the internal model.
- Action
- Contact IBM Support.
- CWMRM1901E - A fatal error has occurred while processing ETL related
model updates for tables located in database database name. The Active
Business Measures Group identifier is internal business measures group
name and updates have been processed for Service Data Movement Service
name.
- Explanation
- An error occurred while an ETL component instance for the indicated business
measures group was being created or updated in the internal model.
- Action
- Contact IBM Support.
- CWMRM1903E - Invalid model has been detected during ETL setup. Source
table database table name in database database name is not a
valid ETL source table for table database table name in database database
name.
- Explanation
- An error occurred while an ETL component instance for the indicated business
measures group was being created or updated in the internal model. The named
source table is not associated with a business measures group.
- Action
- Contact IBM Support.
- CWMRM1904E - Model inconsistency has been detected during ETL setup.
Changes to table database table name in database database name are
not being applied.
- Explanation
- While an ETL component instance for the indicated business measures group
was being created or updated in the internal model, it was detected that no
Apply component instance has been assigned to the named table. An ETL component
instance can only be created or updated if a table has been previously assigned
to an Apply component instance.
- Action
- Contact IBM Support.
- CWMRM1905E - Model inconsistency has been detected during ETL setup.
No Apply information for table database table name in database database
name has been found.
- Explanation
- No information could be found in the internal model that associates the
named table with an Apply component instance. An ETL component instance can
only be created or updated if a table has been previously assigned to an Apply
component instance.
- Action
- Contact IBM Support.
- CWMRM1906E - A fatal error has occurred during ETL setup for table database
table name located in database database name.
- Explanation
- An error occurred while an ETL component instance for the indicated business
measures group was being created or updated in the internal model.
- Action
- Contact IBM Support.
- CWMRM1907E - Invalid model has been detected during ETL setup. Table database
table name in database database name is declared as being of type logical
table type, which is not supported.
- Explanation
- Internally, tables are assigned a type, like dimension table or fact table.
A table has been labeled by the Schema Generator as an unsupported logical
table type.
- Action
- Contact IBM Support.
- CWMRM2201E - Model inconsistency has been detected during Prune setup.
A duplicate prune entry for table database table name has been found
for Service Data Movement Service name.
- Explanation
- While a Source Life Cycle component instance that is associated with table database
table name was being created, it was detected that another Life Cycle
component instance was already been assigned to this table.
- Action
- Contact IBM Support.
- CWMRM2202E - Invalid model has been detected during Prune setup. Table database
table name in database database name does not contain any pruning
information.
- Explanation
- While a Source Life Cycle component instance that is associated with table database
table name was being created, it was detected that the named source table
is not associated with a business measures group.
- Action
- Contact IBM Support.
- CWMRM2203E - Model inconsistency has been detected during Prune setup.
Table database table name has not yet been assigned to a Capture process
in database database name.
- Explanation
- No information could be found in the internal model that associates the
named table with a Capture component instance. A Source Life Cycle component
instance can only be created or updated if a table has been previously assigned
to a Capture component instance.
- Action
- Contact IBM Support.
- CWMRM2204E - Model inconsistency has been detected during Prune setup.
No Capture related information could be found for table database table
name being processed by Capture Capture component instance name.
- Explanation
- No information could be found in the internal model that associates the
named table with a Capture component instance. A Source Life Cycle component
instance can only be created or updated if a table has been previously assigned
to a Capture component instance.
- Action
- Contact IBM Support.
- CWMRM2205E - A fatal error has occurred while processing pruning-related
model updates for tables located in database database name. . The Active
Business Measures Group identifier is internal business measures group
name and updates have been processed for ServiceData Movement Service
name.
- Explanation
- An error occurred while a Source Life Cycle instance for the indicated
business measures group was being created or updated in the internal model.
- Action
- Contact IBM Support.
- CWMRM2206E - A fatal error has occurred during pruning setup for table
database table name located in database database name.
- Explanation
- An error occurred while a Source Life Cycle instance for the indicated
business measures group was being created or updated in the internal model.
- Action
- Contact IBM Support.
- CWMRM4003E - A fatal error has occurred while loading task definitions
from file file name.
- Explanation
- Changes that the user makes to business measures models are mapped to
database artifacts using task definitions. Each task results in the creation
of one or more artifact files that need to be deployed onto the database system.
The task definition file does not exist, or one or more of its task definitions
are incorrect.
- Action
- Make sure the file exists in the indicated directory and that no application
initialization errors have been reported previously.
- CWMRM4005E - Execution of generator class Java class name has failed.
- Explanation
- During schema generation, Java template classes generate artifact
files that set up the data movement services for a business measures model.
If, during execution of such a generator class, a problem occurs, this error
is raised and generation is stopped.
- Action
- Contact IBM Support.
- CWMRM4006E - Unable to execute sub task task name because no
matching generator class has been defined for source database type database
type identifier and target database type database type identifier.
- Explanation
- Changes to the business measures model or the creation of a new business
measures model are internally mapped to tasks and subtasks, which are then
executed using one or more generator classes. The Schema Generator classes
currently only support DB2® UDB as a source database (State or Runtime) and target
database (Runtime or Historical).
- Action
- Default generator classes are packaged in a Java archive named: monReplicationManager_templates.jar.
Make sure this file exists in a subdirectory called rm in your installation
directory.
- CWMRM4007E - Unable to execute sub task task name because generator
class Java class name does not contain valid metadata.
- Explanation
- Changes to the business measures model or the creation of a new business
measures model are internally mapped to tasks and subtasks, which are then
executed using one or more generator classes. Each generator class contains
metadata describing its purpose and configuration. A generator class did not
contain the necessary information to make it usable.
- Action
- Contact IBM Support.
- CWMRM4008E - Execution of task task name was aborted because
execution of its source sub task task name has failed.
- Explanation
- Changes to the business measures model or the creation of a new business
measures model are internally mapped to tasks and subtasks, which are then
executed using one or more generator classes. For the Data Movement Service
from the State database to Runtime database, the State database is referred
to as the source database and the Runtime database as the target database.
For the Data Movement Service from the Runtime database to Historical database,
the Runtime database is referred to as the source database and the Historical
database as the target database. A subtask can be associated with either a
source database or a target database, and is therefore called either a source
subtask or a target subtask. This error indicates a generator class failed
during execution, and processing of a task stopped.
- Action
- Contact IBM Support.
- CWMRM4009E - Execution of task task name has been aborted because
execution of its target sub task task name failed.
- Explanation
- Changes to the business measures model or the creation of a new business
measures model are internally mapped to tasks and subtasks, which are then
executed using one or more generator classes. For the Data Movement Service
from the State database to Runtime database, the State database is referred
to as the source database and the Runtime database as the target database.
For the Data Movement Service from the Runtime database to Historical database,
the Runtime database is referred to as the source database and the Historical
database as the target database. A subtask can be associated with either a
source database or a target database, and is therefore called either a source
sub task or a target sub task. This error indicates a generator class failed
during execution, and processing of a task stopped.
- Action
- Contact IBM Support.
- CWMRM4010E - Task task name has failed during execution.
- Explanation
- Changes that are made by the user to business measures models are mapped
to database artifacts using task definitions. A task has failed. Information
about the cause can be found in error messages (like CWMRM4005E) that were
logged prior to this message.
- Action
- Contact IBM Support.
- CWMRM4012E - No task definition can be found for task task name.
- Explanation
- Changes that are made by the user to business measures models are mapped
to database artifacts using task definitions. If no task definition exists
for the indicated task name, no artifacts can be created and processing is
stopped.
- Action
- Contact IBM Support.
- CWMRM4015E - Class Java class name does not appear to be
a valid generator class. Error message.
- Explanation
- Changes to the business measures model or the creation of a new business
measures model are internally mapped to tasks and subtasks, which are then
executed using one or more generator classes. Generator classes are registered
and validated dynamically. If a generator class fails validation, this error
is raised and additional information displayed in error message.
- Action
- Your installation may be corrupted. Contact IBM Support.
- CWMRM4016E - A fatal error has occurred while analyzing generator classes
in archive Java archive file name. Error message.
- Explanation
- Changes to the business measures model or the creation of a new business
measures model are internally mapped to tasks and subtasks, which are then
executed using one or more generator classes. Generator classes are defined
in a JAR archive that is loaded, and its content is validated. If an error
occurred that is not specific to a generator class, this error is raised.
- Action
- Your installation may be corrupted. Contact IBM Support.
- CWMRM4017E - Number of invalid Java classes classes that are contained
in archive file name do not appear to be valid generator classes. Check
previous log entries.
- Explanation
- Changes to the business measures model or the creation of a new business
measures model are internally mapped to tasks and subtasks, which are then
executed using one or more generator classes. Generator classes are defined
in a JAR archive that is loaded, and its content is validated. If at least
one of the classes failed validation, this error is displayed. One or more
CWMRM4015E messages with additional details precede this message in the log
file.
- Action
- Your installation may be corrupted. Contact IBM Support.
- CWMRM4018E - Registration of template generator class Java class
name has failed. Generator class Java class name has already been assigned
to sub task task name.
- Explanation
- Changes to the business measures model or the creation of a new business
measures model are internally mapped to tasks and subtasks, which are then
executed using one or more generator classes. If more than one generator class
is assigned to a subtask, this error is raised.
- Action
- Your installation may be corrupted. Contact IBM Support.
- CWMRM4019E - No generator class has been assigned to sub task task
name.
- Explanation
- Changes to the business measures model or the creation of a new business
measures model are internally mapped to tasks and subtasks, which are then
executed using one or more generator classes. If no generator class is assigned
to a subtask, this error is raised.
- Action
- Your installation may be corrupted. Contact IBM Support.
- CWMRM4020E - A fatal error has occurred during instantiation of generator
class Java class name. Error message
- Explanation
- Changes to the business measures model or the creation of a new business
measures model are internally mapped to tasks and subtasks, which are then
executed using one or more generator classes. An error message contains additional
information on the reason the Java class name could not be loaded.
- Action
- Your installation may be corrupted, or sufficient system resources are
not available. Contact IBM Support.
- CWMRM4021E - A fatal error has occurred while processing generator
class Java class name. Error message
- Explanation
- Changes to the business measures model or the creation of a new business
measures model are internally mapped to tasks and subtasks, which are then
executed using one or more generator classes. Generator classes are registered
and validated dynamically. If a generator class fails validation, this error
is raised, and additional information displayed in error message.
- Action
- Your installation may be corrupted. Contact IBM Support.
- CWMRM5001E - The DeploymentConsumer constructor has been called with
a null argument.
- Explanation
- During deployment in the State, Runtime, and Historical databases, multiple
utilities are used to process the generated artifacts. An attempt was made
to register a new utility without sufficient information. This message is
conceptually identical to CWMRM0001E..
- Action
- Contact IBM Support.
- CWMRM5002W - Warning: The method getDeploymentConsumer could not find
a consumer for the consumer type of consumer identifier and the platform
identified by the number internal platform identifier.
- Explanation
- During deployment in the State, Runtime, and Historical databases, multiple
utilities are used to process the generated artifacts. An artifact has been
generated for which no processing utility has been registered. Processing
fails.
- Action
- Contact IBM Support.
- CWMRM5005E - A fatal error has occurred while setting up packaging environment
for service Data Movement Service name. Error message
- Explanation
- Artifact files that have been generated are packaged into compressed archives: DS_State_setup,
DS_Runtime_setup and DS_Datamart_setup. Each one of the archives
contains a master setup script that will be used during deployment to configure
the necessary database objects. A problem, identified by the error message,
has occurred during preparation for archive creation.
- Action
- Contact IBM Support.
- CWMRM5006E - A fatal error has occurred while packaging artifacts for
service Data Movement Service. Error message
- Explanation
- Artifact files that have been generated are packaged into compressed archives: DS_State_setup, DS_Runtime_setup and DS_Datamart_setup. Each one of the archives contains a master setup script that will be used
during deployment to configure the necessary database objects. An error occurred
during packaging. Specific details about the error can be found in the error
message.
- Action
- Contact IBM Support.
- CWMRM5009E - A fatal error has occurred while packaging artifacts for
sub task task name. Error message
- Explanation
- Artifact files that have been generated are packaged into compressed archives: DS_State_setup, DS_Runtime_setup and DS_Datamart_setup. Each one of the archives contains a master setup script that will be used
during deployment to configure the necessary database objects. An error occurred
during packaging of artifacts related to the subtask. Specific details about
the error can be found in the error message.
- Action
- Contact IBM Support.
- CWMRM5010E - A fatal error has occurred while packaging artifacts for
task task name. Error message
- Explanation
- Artifact files that have been generated are packaged into compressed archives: DS_State_setup, DS_Runtime_setup and DS_Datamart_setup. Each one of the archives contains a master setup script that will be used
during deployment to configure the necessary database objects. An error occurred
during packaging of artifacts related to the task. This message is not displayed
if CWMRM5009E has already been issued. Specific details about the error can
be found in the error message.
- Action
- Contact IBM Support.
- CWMRM5012W - The optional deployment file file name could not
be found during deployment setup.
- Explanation
- Artifact files that have been generated are packaged into compressed archives: DS_State_setup, DS_Runtime_setup and DS_Datamart_setup. Each one of the archives contains a master setup script that will be used
during deployment to configure the necessary database objects. Each one of
the archives contains support files that are specific to the platform where
the deployment will occur. If one of these files cannot be located during
packaging, this warning is displayed. Two password-masking libraries for AIX® (libAIX32GetPassword.so)
and Microsoft® Windows® (Win32GetPassword.ddl)
are considered optional during artifact packaging. If they are not present
during deployment, any password information that is entered will not be masked.
See error messages CWMRM9000W and CWMRM9001W.
- Action
- You only need to take action if the file reported as missing is relevant
to the platform where deployment will occur. For example, if deployment for
State, Runtime, and Historical databases will be performed on AIX, Win32GetPassword.ddl
is not required, and you can ignore this warning. Launchpad stores optional
deployment files in the installation directory under rm\lib. Your installation
may not have completed successfully if this warning is displayed. Check with
your administrator.
- CWMRM9000W - The program was unable to load the password masking library
due to the following error: error message.
- Explanation
- During deployment, a user may be prompted to enter password information.
The information entered is usually not displayed. However, if this warning
is issued, it means that a problem occurred that prevents the utility from
masking the user input. The Schema Generator uses a native library called
Win32GetPassword.dll (Windows) or libAIX32GetPassword.so (AIX)
to capture password input. This library is located in each one of the compressed
ZIP or JAR files that are created during schema generation.
- Action
- Make sure that the libraries are present during deployment. If the error
message indicates that the library could not be found, update the correct
environment variable to point to the directory where the library is located.
- CWMRM9001W - Passwords will be shown in clear text as the user types
them.
- Explanation
- This warning is displayed together with message CWMRM9000W to notify the
user that sensitive information is about to be echoed by the console.
- Action
- You can stop the utility and investigate why the library that captures
password input could not be loaded.
- CWMRM9004E - Unable to create directory directory name because
of the following error: error message.
- Explanation
- During deployment, the temporary files are created in a temporary directory.
An attempt to create a directory failed because of the indicated error.
- Action
- Make sure your user ID has the proper permissions to create a directory
in the current working directory (where you started the utility).
- CWMRM9005E - Unable to create directory directory name because
a file with the same name already exists.
- Explanation
- An attempt to create a directory failed because a directory with the same
name already exists.
- Action
- If possible, remove the directory.
- CWMRM9018E - A fatal error has occurred while cleaning up: error
message.
- Explanation
- During Schema Generator deployment, the RMSecurityWrapper utility encountered
a problem while performing maintenance tasks. These tasks include, for example,
the removal of temporary files. The stated error prevented the utility from
performing a cleanup task successfully.
- Action
- Contact IBM Support.
- CWMRM9022E - An error occurred: error message.
- Explanation
- During Schema Generator deployment, the RMSecurityWrapper utility encountered
a problem for which no error handling or recovery has been defined.
- Action
- Contact IBM Support.
- CWMRM9023E - Incorrect program invocation. Command command name requires
an argument.
- Explanation
- During Schema Generator deployment, the RMSecurityWrapper utility is used
to perform a certain set of predefined tasks. The utility has been invoked
with incomplete parameters.
- Action
- Your classpath environment variable may be pointing to a location that
contains an older version of this utility. By default, a copy is included
in each ZIP and JAR archive that is created during schema generation. Make
sure that, during deployment, you are using the version of the utility that
is included in the archive.
- CWMRM9024E - Incorrect program invocation. File file name is
not of a supported type.
- Explanation
- A file of an unsupported type was passed as a parameter to the RMSecurityWrapper
utility.
- Action
- Your classpath environment variable might be pointing to a location that
contains an older version of this utility. By default, a copy is included
in each ZIP and JAR archive that is created during schema generation. Make
sure that, during deployment, you are using the version of the utility that
is included in the archive.
- CWMRM9025E - No security information could be located. No user credentials
will be added
- Explanation
- During Data Movement Service deployment, the user is given the option
to specify alternative user credentials to use when connecting to the State,
Runtime, and Historical databases. The alternative user credentials cannot
be retrieved by the RMSecurityWrapper utility.
- Action
- Locate the deployment log file. (It is named after the deployment script
that was executed and is located in the current working directory.) Check
this log file for any prior error messages indicating that a problem occurred
while saving the user credentials. If no errors were logged, check whether
a file named dbaccess.key exists in the current working directory.
If it does, remove it, and retry running the deployment script.
- CWMRM9026E - A fatal error has occurred during encryption: error
message.
- Explanation
- By default, the current user's credentials are being used during deployment
to connect to the State, Runtime, and Historical databases. A user can optionally
specify alternative credentials that are encrypted and used instead of the
current credentials. A problem occurred during encryption.
- Action
- Contact IBM Support.
- CWMRM9027E - A fatal error has occurred during decryption: error
message.
- Explanation
- By default, the current user's credentials are used during deployment
to connect to the State, Runtime, and Historical databases. A user can optionally
specify alternative credentials, which are encrypted and used instead of the
current credentials. A problem occurred during decryption of previously encrypted
information.
- Action
- Contact IBM Support.
- CWMRM9028E - Incorrect program invocation. "directory name" does
not exist or is not a directory.
- Explanation
- The deployment script dynamically retrieves setup files from a predefined
directory location. The setup script expected to find its support files in
directory name that does not exist or is not a directory.
- Action
- Make sure that you have extracted all files from the deployment ZIP (or
JAR) archive successfully. If no problems occurred during extraction, make
sure that you are invoking the deployment script from the current working
directory.
- CWMRM9030E - No patterns are defined for file "file type".
- Explanation
- The deployment script dynamically replaces default user credentials in
its template files with user credentials that you entered during deployment.
A file type was found that has not been defined to perform the replacement.
- Action
- The deployment scripts invoke the RMSecurityWrapper utility to handle
user credential-related tasks. Your classpath environment variable may be
pointing to a location that contains an older version of the RMSecurityWrapper
utility. By default, a copy is included in each ZIP and JAR archive that is
created during schema generation. Make sure that you are using the utility
version that is included in the archive.
- CWMRM9031E - File "file name" was not found.
- Explanation
- RMSecurityWrapper could not find the indicated file.
- Action
- Make sure that you have extracted all files from the deployment ZIP (or
JAR) archive successfully.
- CWMRM9032E - An error occurred during processing of file "file name"
: error message.
- Explanation
- RMSecurityWrapper encountered a problem while processing a file name.
- Action
- Contact IBM Support.
- CWMRM9033E - Incorrect program invocation. Command "command identifier"
is not supported.
- Explanation
- RMSecurityWrapper was invoked by a deployment script with an unsupported
command parameter.
- Action
- The deployment scripts invoke the RMSecurityWrapper utility to handle
user credential- related tasks. Your classpath environment variable may be
pointing to a location that contains an older version of the RMSecurityWrapper
utility. By default, a copy is included in each ZIP and JAR archive that is
created during schema generation. Make sure that you are using the utility
version that is included in the archive.
- CWMRM9035E - Incorrect program invocation. "file name" does
not exist or is not a file.
- Explanation
- A deployment script invoked RMSecurityWrapper and specified an incorrect
file name as a parameter. Deployment is stopped.
- Action
- Make sure that you have extracted all files from the deployment ZIP (or
JAR) archive successfully.
- CWMRM9036E - Your environment is not configured properly to run the DB2 Replication
setup tool. Class Java class name was not found.
- Explanation
- During deployment, a Java-based DB2 replication utility named ASNCLP was
used to create the necessary database objects. The Java class was not found, and deployment
is stopped.
- Action
- During initialization, the deployment scripts attempt to automatically
detect the location from where com.ibm.db2.tools.repl.replapis.cmdline.Asnclp.class can
be loaded. Verify that the JAR archive db2replapis.jar exists in your DB2 installation
subdirectory named "tools".