
Integrity Advanced Server Installation Guide
48
Chapter 7
Maintaining Integrity Advanced Server
Once you have installed and configured the Integrity Advanced Server you must
periodically perform maintenance tasks to ensure optimum performance.
Monitor your database tablespace
Periodically check that you have sufficient free tablespace in your database. Databases
can fill up quickly if you have:
large numbers of client packages
large numbers of users
Update your database statistics
When using Oracle 9i, IBM DB2 8.2,
or Microsoft SQL Server 2000, you should
periodically update your database statistics. Doing this will help your databases to work
more efficiently, improving performance.
Optimize query performance
Some report queries may run for a long time, especially when filtering over a long time
span. You should periodically run commands to optimize your query performance.
Optimizing query performance for DB2
Run the DB2 RUNSTATS command on the reporting tables and indexes on a regular
basis. In some circumstances, queries may time out and errors will appear in the logs.
If this occurs increase the amount of time for TCP/IP timeouts to keep connections
alive longer.
Optimizing query performance for Oracle 9i
Run the ANALYZE command on a regular basis to ensure optimal query performance.
If you see the error ‘
ORA-01555: snapshot too old
’ in the Integrity logs, increase the
size or number of rollback segments.
Monitor your disk space
Closely monitor the Integrity Advanced Server disk space usage. Integrity and
Apache logs can consume a lot of disk space on the Integrity Advanced Server.
Integrity Advanced Server will fail to respond to Integrity clients and/or not work
as expected if there are no free disk space. You should monitor the disk usage, and