The size, in number of cache entries, of the primary and secondary security caches.
For best performance, you should set Security cache size (-secsize) large enough that all your existing records fit in the primary cache. Pick the value for –secsize based on available shared memory and the size of the _sec-authentication-domain table. Each entry consumes approximately 450 bytes. For example, if –secsize is 512, roughly 512 * 450 = 0.25 Mb is allocated for the primary cache, and also the secondary cache, for a total of 0.5 Mb. If memory is not an issue, pick a value close the number of records in _sec-authentication-domain.
If you set the value between 1 and 12, it is automatically increased to 13.
You can set Security cache size (-secsize) to 0 (zero) if you never intend to enable use of the security cache on your database.
For use with the OpenEdge Authentication Gateway only, use Security Cache Size (-secsize) to specify the size (in number of security cache entries) of the security cache. The security cache holds fields from the _sec-authentication-domain and _Tenant-Name tables in memory, eliminating the need to read those values from the database during connection validation.
At startup, if your database is currently enabled for authentication through use of the OpenEdge Authentication Gateway, two security caches are allocated, a primary cache and a secondary cache.
Existing fields are cached in the primary security cache and are preloaded by a broker. After instantiation, no new entries are ever added to the primary cache. If the primary cache is filled, remaining entries are inserted into the secondary cache. All new entries are automatically cached in the secondary cache. During normal database activity, fifty percent (50%) of the cache entries must be evictable. If the number of fixed cache entries is more than 50% of all entries, new entries cannot be added to the cache and creation of a new _sec-authentication-domain record fails. If this occurs, an informational message is written to the database log file, as shown:
Please increase security cache size using database startup parameter -secsize.
Cannot perform this operations because the database security cache is too small.
