System limit alerts

Some system limits are instrumented by the IBM i operating system to send messages to QSYSOPR when a threshold value has been reached.

Once each day the following limits are checked against their alerting level. If the level is exceeded, a message is sent to the QSYSOPR message queue. Since these limits will prevent database activity from continuing if they are reached, you should take action to get the object's percent used for the limit below the alerting level. Reducing data by archiving it is one example of an action that could be taken.

Table 1. System limits that send alerting messages
Limit ID	Limit description	Maximum	Alerting Level	Alerting Cadence
15000	Maximum number of all rows in a partition	4,294,967,288	Greater than 90%	Once per day
15003	Maximum size of a table	1,869,169,767,219	Greater than 90%	Once per day
15104	Maximum number of variable-length segments	65,533	Greater than 90%	Once per day
15400	Maximum *MAX4GB Index Size	4,294,967,296	Greater than 90%	Once per day
15401	Maximum *MAX1TB Index Size	1,869,166,411,776	Greater than 90%	Once per day
15403	Maximum Encoded Vector Index Size	2,199,023,255,552	Greater than 90%	Once per day

The QSYSOPR message is formatted like this:

MYLIB/MYTABLE *FILE HAS CONSUMED MORE THAN 90% OF THE LIMIT: 
15000-MAXIMUM NUMBER OF ALL ROWS (4008420999 OF 4294967288=93.33%). 
REFER TO ibm.biz/DB2foriAlerts FOR MORE DETAIL.