Deployment issues

During the different deployment scenarios of WebSphere® Business Monitor databases artifacts, errors may occur. The following are the proposed solutions for each error.

During deployment of the generated database artifacts problems can arise that are a result of
Table 1. Deployment errors
Problem Solution
Table space assigned to a table does not seem to exist.
  • Make sure the table spaces defined in the table-space properties file exist with the characteristics described.
  • Either create the missing table space, with the appropriate characteristics and rerun the DDLs, or update the table-space properties file to match the table spaces that are defined, and then regenerate the schema.
Table space assigned to table is too small to hold the table.
  • Make sure the table spaces defined in the table-space properties file exist with the characteristics described.
  • Either fix and rerun, or just edit the DDL manually to correct the table-space assignment.
Tables already exist in the database.

Assuming this DDL has not been run previously, there are two possible causes of this problem.

  • The DDL scripts were generated with the option Ignore Previous Deployments selected. The Schema Generator generates new table-creation statements, rather than altering existing tables. This option should only be used when you are trying to create your database tables initially; that is, when you have dropped your existing database tables. If you know you have existing database tables and want to retain them, rerun the Schema Generator without the Ignore Previous Deployments option selected, and then rerun the resulting DDL scripts.
  • The other cause is that at some point a version of this business measures model has been removed and the Delete and keep for reporting option was not selected. If a version of an business measures model is deleted and the keep for reporting option is not selected, then the Schema Generator cannot continue to manage changes in the supporting database tables for this business measures model. There are two options at this point.
    • Branch off and create a new business measures model based on the current one, and deploy it as a new business measures model with a new set of tables. You can manually migrate the data from the existing set of tables into the new tables.
    • Manually drop the existing database tables that support this business measures model, using the provided mapping files as a guide. Once the tables have been dropped, rerun the Schema Generator with the Ignore Previous Deployments option. The resulting DDL scripts will create a fresh set of tables that will support this latest version of the business measures model.
Note: Unless you manually back up the data from the old tables before you drop them and then migrate the data into the newly created tables, you will not have a reporting history for any processes that ran on the old versions of the business measures model.

is not recommended to use the delete option instead of the delete and keep for reporting option when you are removing the model, unless you have no intention of deploying a new version of this business measures model at some point in the future.

Table space is too small. (Although the table space initially assigned to this table was sufficient for the column size, subsequent metrics that were added to the table have pushed it beyond the page size of the current table space.) You will need to back up this table, drop it, and then re-create it, assigning it to a larger table space. The backed-up data should then be loaded into the new table. Once the current table is re-created in a larger table space, you will be able to run the latest DDL scripts that will add the necessary columns.
For various reasons, you may want begin again with your database tables. For example, you may have a number of metrics that you no longer want, which are still in your database tables because they existed in previous business measures model versions. The simplest way is to rename the project in WebSphere Business Modeler. The business measures model will be treated as a new mode, and new, unique tables will be created in the database.
Note: In this case, no history information from previous process instances will be available.
If you want to view the history information, copy the data from the original database tables into the newly created tables. The column names will not match, but the data types will be matching. You can use the mapping files (generated with the DDL scripts) or database column comments to identify which column corresponds with which metric and which table corresponds with which process.
Note: Some columns from the original tables will not have corresponding columns in the new tables if those metrics no longer exist in the latest version of your business measures model.

Copyright IBM Corporation 2005. All Rights Reserved.