Previous Topic: IPv6 Database Issues

Next Topic: DB2 JDBC Issues


DB2 Database Issues

ReportCenter supports the Legacy and Universal DB2 for z/OS JDBC drivers. You do not need to change or upgrade drivers. If you are using the Legacy driver, you can continue to do so.

Review the information in DB2 Administration. If you have monitored the performance of your current production database, this information can help you assess whether any of the suggestions can benefit your environment.

In particular, migration is an ideal time to review the database size and whether all the data stored justifies the space it takes. You can delete unwanted data and prevent it from being sent to ReportCenter in the future.

Review the space usage of your tablespace data sets. For large fact tables, you can redefine these data sets to fit all the data into one primary extent.

Review your buffer pool allocations. You can create a dedicated buffer pool for ReportCenter.

If you have not previously done so, verify that SQL Dynamic Statement Caching is enabled on the DB2 subsystem where the ReportCenter database runs.

You can get ReportCenter to use your current production database by performing the following steps:

Specify the current schema name in the DB2 section of the REPORTCENTER parameter group.

Use the same DB2 JDBC properties file, which points to the current DB2 subsystem.