You may see these messages if errors are generated by the Schema
Generator.
- CWMSC0001E - An unknown exception has occurred. Exception.
- Explanation
- A general error has occurred.
- Action
- Check the error details and log files to diagnose the error.
- CWMSC0002E - A metric is defined with an invalid data type:data
type. The DDL is invalid.
- Explanation
- One of the metrics in the business measures group has an unrecognized
data type. No Schema Generator artifacts can be produced.
- Action
- Using the Business Measures editor, check
the metric with the data type indicated in the message and change it to a
valid data type.
- CWMSC0003W - An error has occurred while parsing table space properties
file. Valid table spaces, if any, will be used. Verify your table space properties
file.
- Explanation
- The table space properties file, which lists the table spaces that should
be used for table assignment during table creation, is incorrect.
- Action
- Edit the table space properties file to conform to the format described.
- CWMSC0004E - The total size of the metrics for Business Measures Group business
measures group name exceeds 32k in the State Database. You must
remove some metrics or reduce the size of some String metrics in this Business
Measures Group and rerun Schema Generator.
- Explanation
- The total size of the columns needed for a database table is larger than
32 KB. DB2® does
not support this size.
- Action
- You can remove metrics, reduce the length of string-type metrics, or both,
to reduce the total size to below 32 KB.
- CWMSC0005E - The total size of the metrics for Business Measures Group business
measures group name exceeds 32k in the Runtime Database. You must
remove some metrics or reduce the size of some String metrics in this Business
Measures Group and rerun Schema Generator.
- Explanation
- The total size of the columns needed for a database table is larger than
32 KB. DB2 does
not support this size.
- Action
- You can remove metrics, reduce the length of string-type metrics, or both,
to reduce the total size to below 32 KB.
- CWMSC0006E - The total size of the metrics for Business Measures Group business
measures group name exceeds 32k in the Fact table of the Historical
Database. You must remove some metrics or reduce the size of some String
metrics in this Business Measures Group and rerun Schema Generator.
- Explanation
- The total size of the columns needed for a database table is larger than
32 KB. DB2 does
not support this size.
- Action
- You can remove metrics, reduce the length of string-type metrics, or both,
to reduce the total size to below 32 KB.
- CWMSC0007E - The total size of the metrics for Business Measures Group business
measures group name exceeds 32 KB in a Dimension table of the Historical
Database. You must remove some metrics or reduce the size of some String
metrics in this Business Measures Group and rerun Schema Generator.
- Explanation
- The total size of the columns needed for a database table is larger than
32 KB. DB2 does
not support this size.
- Action
- You can remove metrics, reduce the length of string-type metrics, or both,
to reduce the total size to below 32 KB.
- CWMSC0008E - Target table target table name for replication
mapping is null.
- Explanation
- One of the database tables was assigned to be replicated to a target table
that does not exist.
- Action
- Contact IBM® support,
and provide it with your business measures model file.
- CWMSC0009E - Invalid parameters for table creation: DB=database
name Tablename=table name Schema=schema
name Tabletype= table type.
- Explanation
- One of the attributes of the table to be created is null or an empty string.
- Action
- Contact IBM support,
and provide it with our business measures model file.
- CWMSC0010E - Failed to lookup or create Business Measures group to map
Business Measures group business measures group name.
- Explanation
- The Schema Generator failed to perform an internal mapping while processing
the business measures model.
- Action
- Contact IBM support,
and provide it with your business measures model file.
- CWMSC0011E - No target table metadata has been found while trying to
map table <schema>.<tablename>.
- Explanation
- The Schema Generator failed to perform an internal mapping while processing
the business measures model.
- Action
- Contact IBM support,
and provide it with your business measures model file.
- CWMSC0012E - Inconsistent table mapping for table table name.
Predicate is null or zero length.
- Explanation
- The Schema Generator failed to perform an internal mapping while processing
the business measures model.
- Action
- Contact IBM support,
and provide it with your business measures model file.
- CWMSC0013E - No valid mapping has been specified for look up case for
table table name. Table mapping does not contain a source
column, lookup operation, or sqlfragment.
- Explanation
- The Schema Generator failed to perform an internal mapping while processing
the business measures model.
- Action
- Contact IBM support,
and provide it with your business measures model file.
- CWMSC0014E - No valid mapping has been specified for look up case for
table table name. Table mapping is not straight column
mapped but SQL fragment is null.
- Explanation
- The Schema Generator failed to perform an internal mapping while processing
the business measures model.
- Action
- Contact IBM support,
and provide it with your business measures model file.
- CWMSC0015E - Could not write to file for XMI saving/loading: exception.
- Explanation
- The Schema Generator could not write to the disk that is loading a business
measures model.
- Action
- Check the text of the exception, and take corrective action.
- CWMSC0016E - Could not write to file: file path.
Make sure the following directory exists and has write permissions:Exception.
- Explanation
- The Schema Generator could not create one or more of the output artifact
files.
- Action
- Verify that the target directory has write permissions, and check the
text of the exception generated to determine the problem and take corrective
action.
- CWMSC0017E - Business Measures model artifact business name with
UID XMI UIDdoes not have a physical name.
- Explanation
- One of the artifacts in the business measures model does not have an identifier
that is used to name the database objects (tables or columns).
- Action
- Contact IBM support,
and provide it with your corrupted business measures model file. Or try reexporting
your model from the Business Measures editor.
- CWMSC0018E - No dimension name found in Business Measures group business
measures group name for dimension business name.
- Explanation
- The business name of a dimension on the business measures group specified
was not found.
- Action
- Using the Business Measures editor, verify
that the dimension has a business name, and reexport the model. If the problem
persists, contact IBM support, and provide it with your business measures
model file.
- CWMSC0019E - One or more fatal errors occurred during schema generation.
No valid database scripts were produced. Check the logs for error messages.
- Explanation
- The result of the database DDL generation process is unusable.
- Action
- Check the rest of the logs and console messages to determine the root
problem.
- CWMSC0020E - The persistence type has been changed for metric business
name. You have to create a new Business Measures model and deploy
it.
- Explanation
- You are deploying an updated version of an existing business measures
model and have changed the persistence type of one of the metrics. This change
is not supported. For all unsupported changes, read the information in Change management and artifacts generation.
- Action
- To solve the problem, you can perform one of the following actions:
- Set the persistence type to its original state.
- Create a new business measures model based on the persistence type.
- Delete the metric, and create a new metric with the required persistence
type.
- CWMSC0021E - The dimension group has been changed for metric business
name. You have to create a new Business Measures model and deploy
it.
- Explanation
- You are deploying an updated version of an existing business measures
model and have changed the dimension to which a metric belongs. This change
is not supported.
- Action
- You can set the dimension group to its original state, or you can create
a new business measures model based on the dimension group.
- CWMSC0022E - The "Is dimension key" indicator been changed for metric business
name. You have to create a new Business Measures model and deploy
it.
- Explanation
- You are deploying an updated version of an existing business measures
model and have changed the “isPartOfDimensionKey” flag on a metric that is
part of a dimension. This change is not supported.
- Action
- You can set the flag back to its original value, or you can create a
new business measures model based on this flag.
- CWMSC0023E - The data type has been changed for metric business
name. You have to create a new Business Measures model and deploy
it.
- Explanation
- You are deploying an updated version of an existing business measures
model and have changed the data type of a metric. This change is not supported.
- Action
- To solve the problem, you can perform one of the following actions:
- Set the data type to its original state.
- Create a new business measures model based on this data type.
- Delete the existing metric, and create a new one with the required data
type.
- CWMSC0024E - The Business Measures Group business name status
has been modified as a Subject Area. You have to create a new Business Measures
model and deploy it.
- Explanation
- You are deploying an updated version of an existing business measures
model and have changed the “isSubjectArea” indicator. This change is not
supported.
- Action
- Set the indicator back to its original value, or create a new business
measures model based on this indicator.
- CWMSC0025E - The metric business name has been deleted
from the model but was part of a dimension key. You have to create a new Business
Measures model and deploy it.
- Explanation
- You are deploying an updated version of an existing business measures
model and have deleted a metric that was part of a dimension key on a dimension.
This change is not supported.
- Action
- Restore your model from a backup taken before the change, or create a
new business measures model based on the change and deploy it.
- CWMSC0026E - The metric business name has been added
to an existing dimension and marked as part of the dimension key. You have
to create a new Business Measures model and deploy it.
- Explanation
- You are deploying an updated version of an existing business measures
model and have added a metric that is part of a dimension key on a dimension
that already existed in the previous version. This change is not supported.
- Action
- To solve the problem, you can perform one of the following actions:
- Delete this new metric.
- Mark it as not part of the dimension key.
- Assign this metric to a new dimension group.
- Create a new business measures model based on this metric.
- CWMSC0027E - The timer business name has been toggled
between accumulating and non-accumulating. You have to create a new Business
Measures model and deploy it.
- Explanation
- A timer in the business measures model has been changed from an accumulating
type to a non-accumulating, or vice versa. This change is not supported.
- Action
- Undo the change and redeploy, or delete this timer and create a new timer
of the required type.
- CWMSC0028E - Business Measures model is invalid: the dimension business
name is invalid because it has no metrics marked as part of the
dimension key. No output is generated.
- Explanation
- A dimension group must have at least one member metric marked as part
of the dimension key. This dimension group does not meet that requirement.
- Action
- Mark at least one of the metrics in the dimension group as part of the
dimension key.
- CWMSC0029E - An error has occurred while loading the previous version
of the Business Measures model. The deployment cannot be continued: exception.
- Explanation
- The Schema Generator could not load the previous versions of this business
measures model.
- Action
- Check the error message, and take corrective action.
- CWMSC0030E - Could not connect to the Repository database to retrieve
configuration information. No artifacts will be generated.
- Explanation
- The Schema Generator could not connect to the Repository database to generate
artifacts. Or the information required for generation was not found in the
database. (See CWMSC0032E.)
- Action
- Check the error message and the rest of the log to determine the reason
that the attempt to access the Repository database was unsuccessful.
- CWMSC0031E - The dimension business name contains
a Date or Date-Time data type metric along with other metrics. Date and Data-Time
data type metrics can only be in dimensions containing a single metric.
- Explanation
- Dimension groups that contain a metric of type Date or DateTime must not
contain any other metrics (even other Date or DateTime types).
- Action
- Remove any metrics in the dimension except for the single Date or DateTime
type metric, or remove the available Date or DateTime metrics from the dimension
group.
- CWMSC0032E - The Metadata Repository does not seem to be populated correctly.
Check the DATABASE_CHARACTERISTICS table.
- Explanation
- Information needed by the Schema Generator was not found in the Repository
database.
- Action
- Look in the DATABASE_CHARACTERISTICS table in your Repository database.
If this table is empty, contact IBM Support for assistance with populating
it.
- CWMSC0033W - No Business Measures Groups were found in this Business
Measures model. Verify that you have created business measures.
- Explanation
- No artifacts were found in this business measures model. No data store
tables will be created.
- Action
- Ensure that you have created business measures in the Business Measures editor.
- CWMSC0034E - An error has occurred loading the Business Measures model
XMI file. Verify that the file file path is a valid model
XMI. Exception: exception details.
- Explanation
- The business measures model file could not be loaded by Schema Generator
because of an unknown error.
- Action
- To help solve the problem, perform one of the following actions:
- Check the text of the exception, and take corrective action if possible.
- Reexport the model.
- Contact IBM Support,
and prepare your model file.
- CWMSC0036E - Could not create foreign key relationship with null table.
Child table=table name, Parent table= table name.
- Explanation
- The Schema Generator tried to create a foreign-key relationship to a table
that does not exist.
- Action
- Contact IBM support,
and provide it with your business measures model file.
- CWMSC0037E - Could not create foreign key relationship with null table
or column. Child table= table name, Parent table= table
name, Child column= column name, Parent column=column
name.
- Explanation
- The Schema Generator tried to create a foreign-key relationship to a table
or a column that does not exist.
- Action
- Contact IBM support,
and provide it with your business measures model file.
- CWMSC0056E - An error has occurred while loading XMI file path
name from the file system: exception.
- Explanation
- The Schema Generator encountered an error while trying to load a model
file.
- Action
- Check the text of the exception, and take corrective action if possible.
- CWMSC0058W - Database DDLs have been generated with warnings. Refer
to the log files.
- Explanation
- One or more warning conditions occurred during Schema Generator artifact
generation.
- Action
- Check the console messages and log files to determine what the warnings
mean and take corrective action, if any.
- CWMSC0059E - The metric business name has a cardinality
whose value is not one. This is not valid. No DDLs are generated.
- Explanation
- A metric in the model has a multiplicity value not equal to 1. WebSphere® Business Monitor Version 6.0 only supports multiplicity
values of 1.
- Action
- Change the cardinality of the metric to 1, or contact IBM Support and
prepare your model if you cannot correct this situation
- CWMSC0060E - The Schema Generator may be already running. If this is
not the case, delete the lockfile path name. Schema generation
has not been performed.
- Explanation
- Either another user is running the Schema Generator, you have clicked
the generate button multiple times without waiting for it to complete, or
a stale lock file exists.
- Action
- Wait a few minutes, and try to run the Schema Generator again. If you
are certain another instance of Schema Generator is not running, delete the
lock file listed in the error message before you run the Schema Generator
again.
- CWMSC0061E -An error has occurred while attempting to create the Schema
Generator lockfile. Schema generation has not been performed. exception.
- Explanation
- The Schema Generator could not create the temporary lock file used to
ensure exclusive access during generation. The exception causing the error
is listed.
- Action
- Check the text of the exception, evaluate the error condition, and take
corrective action if possible.
- CWMSC0062E - The dimension business name has a too
long dimension key. Either reduce the size of some of the string metrics,
which are marked as keys in this dimension group, or clear the selection of
isPartOfDimensionKey for some metrics in this dimension.
- Explanation
- The total size of metrics making up a dimension key has exceeded 1000
bytes.
- Action
- Reduce the total size of the dimension key either by reducing the size
of the metrics making up the key or by removing some of the metrics from the
key.
- CWMSC0063E - This Business Measures model has a version number version
number which is older than the most recent deployed version version
number. Re-export the model from the Business Measures Editor and
choose a higher version number.
- Explanation
- Business measures models must be deployed in increasing version numbers.
A model with a version number equal to or greater than this model version
number has already been deployed.
- Action
- Reexport the model with a higher version number.
- CWMSC0064W - An error occurred while setting the permissions of the
Schema Generator output files.
- Explanation
- The Schema Generator sets the permissions of its output artifacts to be
world read or writable on UNIX® platforms to ensure they can be widely accessed.
In this case, the file permissions could not be set.
- Action
- Use an appropriate user (Root) to set the permissions of the output artifacts
to the required settings to allow deployment.
- CWMSC0065W - Replication Manager had warnings, returned with code return
code and message message text.
- Explanation
- The Replication Manager generation component encountered one or more warnings.
- Action
- Check the message returned by the Replication Manager, and the rest of
the administrative console and log files to determine what action to take,
if any.
- CWMSC0066E - Replication Manager had errors, returned with code return
code and message message text.
- Explanation
- The Replication Manager generation component encountered one or more failures.
- Action
- Check the message returned by the Replication Manager and the rest of
the administrative console and log files to determine what action to take,
if any. The artifact output from this invocation cannot be used.
- CWMSC0068W - One or more components of Schema Generator have reported
warning. Check the log files.
- Explanation
- One of the generation components (Schema Generator, Replication Manager, Cube
Views™) encountered one or more warnings.
- Action
- Check the administrative console and log files to determine what action
to take, if any.
- CWMSC0069E - One or more components of Schema Generator have reported
error/failure. Check the log files.
- Explanation
- One of the generation components (Schema Generator, Replication Manager, Cube
Views) encountered one or more errors.
- Action
- Check the messages returned by the Replication Manager and the rest of
the administrative console and log files to determine what action to take,
if any. Click Replication Manager messages to go to Replication Manager messages documentation.
The artifact output from this invocation cannot be used.
- CWMSC3000I - The Business Measures model is being processed and a cube
views XML, based on the Business Measures model, is being generated.
- Explanation
- This is a progress information message.
- Action
- None.
- CWMSC3001I - A cube views metadata XML, based on the Business Measures
model, has been generated.
- Explanation
- This is a progress information message.
- Action
- None.
- CWMSC3002I - The Schema Generator has detected no errors or warnings
during the cube views metadata generation.
- Explanation
- This is a progress information message.
- Action
- None.
- CWMSC3003W - The metric metric name is missing the
measureAggregationType annotation.
- Explanation
- The metric will not be included in the data mart. The metric does exist
in the model and has been identified as a measure or a measure that can be
aggregated. However, there is no defined aggregation type, such as count,
sum, maximum, or minimum, in the model.
- Action
- If you want to include this metric in the historical data, you must define
an appropriate aggregation type using the Business Measures editor.
- CWMSC3004E - An error has occurred while attempting to generate the
cube views XML file.
- Explanation
- There were problems in producing an XML file.
- Action
- Contact IBM Support.
- CWMSC3005E - An error has occurred while attempting to write the file
named file name.
- Explanation
- There were problems in producing one of the XML files.
- Action
- Contact IBM Support.
- CWMSC3006E - An error has occurred while attempting to generate the
zip file containing the Business Measures model and the cube views XML file.
- Explanation
- The Schema Generator cannot write to the directory location specified
to the Schema Generator.
- Action
- Ensure that there is a permission to write files to the directory location
that was specified.
- CWMSC3007E - An error in the Business Measures model has been detected.
The dimension group name is not found.
- Explanation
- There is a problem with the business measures model. Send the model to IBM Support
for diagnosis.
- Action
- Contact IBM Support.
- CWMSC3008E - An error in the Business Measures model has been detected.
The dimension group physical name descriptor is not found.
- Explanation
- There is a problem with the business measures model. Send the model to IBM Support
for diagnosis.
- Action
- Contact IBM Support.
- CWMSC3009E - An error in the Business Measures model has been detected.
The specified dimension group physical name isbusiness measures
group physical name.
- Explanation
- There is a problem with the business measures model. Send the model to IBM Support
for diagnosis.
- Action
- Contact IBM Support.
- CWMSC3010E - An error has occurred while attempting to write the file
named file name. Make sure the directory exists and has
write permissions.
- Explanation
- The Schema Generator cannot write the files that it produces.
- Action
- Ensure that directory exists and has write permissions.
- CWMSC3011E - An error has occurred while attempting to locate the file
named file name. Refer to the log files for errors which
may have prevented the creation of this file.
- Explanation
- The Schema Generator is attempting to produce the Monitor.zip file. There
is a problem in trying to build this file that consists of two files, the
observation model .XMI file and the cube views .XML file
- Action
- Examine the WebSphere logs
and look for any other Schema Generator messages to determine the source of
the problem. The most likely cause is a problem in generating the DB2 Cube Views .XML
file.
- CWMSC3012W - The Schema Generator has detected warnings during the cube
views metadata generation. Refer to the log files for warning messages.
- Explanation
- This is a progress information message. The business measures model likely
contains metrics that have no aggregation measures defined.
- Action
- Examine the WebSphere logs
and look for any other Schema Generator messages to determine the source of
the problem. You will likely find message number CWMSC3003W in the log files.
- CWMSC3013E - The Schema Generator has detected errors during the cube
views metadata generation. Refer to the log files for error messages.
- Explanation
- The Schema Generator cannot generate a model_cv.xml file..
- Action
- Examine the WebSphere logs,
and look for any other Schema Generator messages to determine the cause of
the problem.
- CWMSC3014E - The Dimension Hierarchy dimension hierarchy name contains
attributes with duplicate granularity level values. This model is not valid.
- Explanation
- A dimension has been modeled incorrectly within the business measures
models and needs correcting. Each metric defined to be part of a dimension
should have a unique granularity setting.
- Action
- Use the Business Measures editor to correct the business measures model.
- CWMSC3015E - No cube views metadata XML has been generated because errors
were detected in the model.
- Explanation
- The Schema Generator could not generate a model_cv.xml file.
- Action
- Examine the WebSphere logs,
and look for any other Schema Generator messages to determine the cause of
the problem.
- CWMSC3016E - An error has occurred while attempting to generate the
XML file containing db2mdapiclient import model request.
- Explanation
- The Schema Generator could not generate an XML file that contains the
import model request.
- Action
- Ensure that there is a permission to write files to the directory location
that was specified.
- CWMSC4000I - Data services component is initializing Alphablox data
sources and cubes.
- Explanation
- This is a progress information message.
- Action
- None
- CWMSC4001E - An error has occurred while attempting to create a relational
data source.
- Explanation
- The likely reason for this problem is that the Historical database is
unavailable or does not exist.
- Action
- Ensure that the Historical database does exist or is available.
- CWMSC4002E - An error has occurred while attempting to create the data
source used for cubes.
- Explanation
- The most likely reason for the problem is that the Historical database
is unavailable or does not exist.
- Action
- Ensure that the Historical database does exist or is available.
- CWMSC4003E - An error has occurred while attempting to start up an existing
cube.
- Explanation
- An error occurred while a program was creating or updating a cube using
a DB2 Alphablox administrative
API.
- Action
- Use the DB2 Alphablox administrative
console to manually create the cube. If the problem persists, contact IBM support.
- CWMSC4004E - An error has occurred while attempting to create a new
cube.
- Explanation
- An error occurred while a program was creating or updating a cube using
a DB2 Alphablox administrative
API.
- Action
- Use the DB2 Alphablox administrative
console to manually create the cube. If the problem persists, contact IBM support.
- CWMSC4005E - An AdminBlox related exception has occurred.
- Explanation
- DB2 Alphablox has been installed
incorrectly.
- Action
- Contact IBM Support.
- CWMSC4006I - Data services component has finished initializing Alphablox
data sources and cubes.
- Explanation
- This is a progress information message.
- Action
- None.
- CWMSC4007E - An error has occurred while attempting to parse the cubeviews
metadata.
- Explanation
- There was a problem in parsing the cube views .xml file that was generated.
- Action
- Contact IBM support.
- CWMSC4008E - An error has occurred while attempting to access the Repository
database.
- Explanation
- The most likely cause is a problem with a JDBC resource that was created.
- Action
- Ensure that a valid user ID and password were used for the JDBC Repository
Database. This is a WebSphere data source. Refer to the WebSphere documentation
related to data sources to resolve this problem.
- CWMSC4009E - An error has occurred while attempting to test the connection
to the relational data source.
- Explanation
- The most likely cause is incorrect data input during installation.
- Action
- Use the DB2 Alphablox administrative
console to edit the data source Historical database name and make corrections.
- Ensure that the user ID and password supplied are valid.
- Press the Test Connection button that DB2 Alphablox administrative
console supplies, to ensure that the problem is corrected.
- CWMSC4010E - An error has occurred while attempting to test the connection
to the data source used for cubes.
- Explanation
- The most likely cause is incorrect data input during installation.
- Action
- Use the DB2 Alphablox administrative
console to edit the data source Historical database name_cube and make
corrections.
- Ensure that the user ID and password supplied are valid.
- Press the Test Connection button that DB2 Alphablox administrative
console supplies to ensure that the problem is corrected.
- CWMAX3000I - The schema generation has completed successfully.
- Explanation
- A successful completion for the operation.
- Action
- None.
- CWMAX3200E - An error has occurred. Exception: exception details.
- Explanation
- A general exception has occurred.
- Action
- Check the error details and log files to diagnose the error.
- CWMAX3201E - File does not exist. File name.
- Explanation
- The current panel cannot be saved unless a correct file name is specified.
- Action
- Correct the field value to contain the name of an existing file.
- CWMAX3202E - A file input/output error has occurred. Error details.
- Explanation
- The system could not read or write to the temporary file.
- Action
- Ensure that the directory exists and the file write option is enabled.
- CWMAX3203E - The configuration value is null. Update the Configuration
tab by clicking OK or Apply.
- Explanation
- You must fill and save the contents of the Configuration tab
before you can proceed to work in any other tab.
- Action
- In the Configuration tab, click Apply to
save the current values.
- CWMAX3204E - The configuration value is null. Update the State to Runtime
Configuration tab by clicking OK or Apply.
- Explanation
- You must fill and save the contents of the Configuration tab
before you can proceed to work in any other tab.
- Action
- Return to the Configuration tab, and click Apply before
saving the values on this tab.
- CWMAX3205E - The configuration value is null. Update the Runtime to
Historical Configuration tab by clicking OK or Apply.
- Explanation
- You must fill and save the contents of the Configuration tab
before you can proceed to work in any other tab.
- Action
- Return to the Configuration tab, and click Apply before
saving the values on this tab.
- CWMAX3206E - The file file name is not found in directory
name. Please verify that the correct ZIP file is defined in the Configuration.
- Explanation
- The zipped file does not contain the correct XMI file of the business measures model.
- Action
- Ensure that the zipped file contains the correct XMI file of the business measures model.