Database maintenance
WebSphere® Business Monitor databases
require regular maintenance. Some DB2® tools can help you in enhancing the
use and performance of the databases.
The recommended tools are:
- Configuration Advisor.
- DB2 Web
Health Center, which assists database administrators (DBAs) by alerting them
to potential problems and providing recommendations to resolve problems. DBAs
can monitor an instance remotely using the Web Health Center and view alert
details and make recommendations.
- REORG and REORGCHK commands. REORG eliminates overflow rows and reclaims
space from deleted rows of tables and indexes. This tool is useful if there
have been a large number of deletions, updates, or inserts. REORGCHK updates
the statistics that are used by the DB2 optimizer tool. This tool is useful
when the statistical information of the database tables are not up to date
due to database updates.
- RUNSTATS command, It gathers statistics about databases objects. These
statistics can be used during data retrieval to choose the path in accessing
data. Therefore the DB2 will have the information it needs to choose the
most efficient access path. Databases performance will be poor until an administrator
runs the DBA RUNSTATS command against all of the tables in all of the databases
after some data has been allowed to accumulate in each of the databases. Example:
RUNSTATS ON TABLE tablename WITH DISTRIBUTION AND DETAILED INDEXES ALL
Note: The tablename must be fully qualified with the schema name.
After
the running the command. Run DB2 rebind command: db2rbind <database_alias> -l logfile all
The
performance affects Monitor Server event processing performance as well as
Replication performance. In addition the default Pruning interval set in
replication's RMPRUNECTL table should be defaulted to 0 instead of the current
1440 seconds (or 24 hours).
For more information on DB2 maintenance utilities, refer to IBM
® DB2 documentation.
Backing up databases and recovering them from deployment errors is also
part of database maintenance.
- Database backup
You should back up Repository, State, Runtime and Historical databases before you run any new WebSphere Business Monitor Database Definition Language (DDL) scripts, whether they deploy a new model obchodních ukazatelů or update an existing one.
- Recovery after deployment errors
If you encounter an error while deploying replication artifacts. You have to undo the actions performed within the deployment of a single model obchodních ukazatelů to undo the changes.