Changing the table_store memstore soft and hard limits
If the alerts database becomes exceptionally large, you can use a command to change the soft and hard limits.
If the alerts database becomes exceptionally large, the following message is displayed:
Region soft limit exceededThis means that the table_store memstore, where alert table data is stored, has reached its maximum size. You can use the ALTER MEMSTORE command to change the soft limit. For example, in nco_sql, enter:
ALTER MEMSTORE table_store SET SOFT LIMIT 500 M;The soft limit cannot be set to a larger size than the hard limit, which you can change using the nco_store_resize utility. This utility enables you to change the hard limit for the table_store memstore for the specified ObjectServer.
The command-line options for the nco_store_resize utility are described in the following table.
| Command-line option | Description |
|---|---|
| -help | Displays help on the command-line options and exits. |
| -messagelevel string | Specifies the message logging level. Possible values
are: debug, info, warn, error,
and fatal. The default level is error. Messages
that are logged at each level are as follows:
Tip: The value of string can
be in uppercase, lowercase, or mixed case.
|
| -messagelog string | Specifies the path to which messages are logged. The default is stderr. |
| -newhardlimit integer | Specifies the new hard limit for the memstore, in MB. The default is 500 MB. You cannot set a hard limit that is larger than the maximum memstore size. If you exceed the store size, the hard limit is truncated to the maximum permitted memstore size. The maximum permitted memstore size (in MB) for the associated platform is shown below:
|
| -server string | Specifies the name of the ObjectServer for which the memstore size will be increased. The default is NCOMS. |
| -version | Displays version information on the checkpoint verification utility and exits. |