Day-to-Day Operation
instructing the table administration program, rmstbladm, to remove old entries. Before
running rmstbladm, archive any data you want to keep as described in Section 9.4.4.
Remove old entries as follows:
# rmstbladm -c
rmstbladm clears out all entries that are older than a specified lifetime. The lifetime for
job data and the lifetime for statistical data are specified in the attributes table (see
Section 10.2.3).
Failure to clear old entries can cause problems as described at the end of this section.
See Section 9.4.3 for details about the accounting statistics table which also grows over
time.
A cron job can be set up to clear out the tables. In the following example, this task is
performed at 2 a.m. each weekday morning.
0 2 * * 1-5 /usr/bin/rmstbladm -c
Troubleshooting
If the tables are not cleared out on a regular basis, the database continues to grow until
the performance of RMS is affected. Indications that this is happening include the
following:
• The database server, msqld, uses more memory.
• The table join operations performed by rinfo take longer.
• Queries acting on large tables may exceed normal user memory limits.
• rmstbladm takes a long time to clear out old entries or may fail, although insert
operations succeed and the tables continue to grow.
The point at which memory limits are exceeded varies with the number of nodes in the
machine and the amount of memory on the rmshost node. To check that the size of the
database is within operating limits, enter the following query:
$ rmsquery; "select * from node_stats" > /tmp/stats.sql
If this fails, follow these steps to recover from the problem:
1. Log in to the rmshost node as root and stop the database server, as follows:
# /sbin/init.d/msqld stop
MSQL: service stopped
9-8 Setting up RMS