Increases server startup parameters while the database remains online.

Syntax

proutil db-name -C increaseto  [ -B n ][ -B2 n ] [ -L n ] [ -Mn n ]
                  [ -Mxs n ] [ -aibufs n ] [ -bibufs n ]  [ -cdcsize n ] [ -ecsize n ]
                  [ -n n ] [ -omsize n ] [ -pica n ] [ -mtpmsize n ]  [ -secsize n ]
                  [ -indexrangesize n ] [ -lobrangesize n ] [ -tablerangesize n ] 
                  [ -userindexrangesize n ] [ -userlobrangesize n ] [ -usertablerangesize n ]
                  [ -clstmtCacheAllocationFactor n ]

Parameters

db-name
Specifies the name of the database to be updated.
-B
Specifies the new value for the number of blocks in the primary buffer pool.
-B2
Specifies the new value for the number of blocks in the alternate buffer pool.
-L
Specifies the new limit of the record locking table.
-Mn
Limits the number of remote user servers that can be started by the broker process.
-Mxs
Specifies the size of the shared-memory overflow, in kilobytes.
-aibufs
Specifies the new number of after-image buffers.
-bibufs
Specifies the new number of before-image buffers.
-cdcsize
Specifies the size of the CDC secondary cache. In single-user mode, the primary cache is not used, and its entire size is allocated to the secondary cache. In multi-user mode, 75 percent of the cache size is allocated to the primary and the remainder to the secondary cache. However, for values smaller than 400, the size is split evenly between the two caches. INCREASETO modifies the size of only the secondary cache.
-ecsize
Specifies the size of the secondary encryption cache. At startup, if the database is enabled for transparent data encryption (TDE), two encryption caches are allocated: a primary cache and a secondary cache, each with a number of entries specified by this startup parameter. If your database is not enabled for TDE, only the secondary cache is allocated. INCREASETO modifies the size of only the secondary cache.
-n
Specifies the number of users.
-omsize
Specifies the number entries in the secondary storage object cache. At startup, primary and secondary storage object cache are allocated, each with the number of entries specified by this startup parameter. INCREASETO modifies the size of only the secondary cache.
-pica
Specifies the size of the database service communications area.
Note: If the database is not enabled for replication, INCREASETO prompts whether you want to continue with the increase operation.
-mtpmsize
Specifies the number of entries in the multi-tenancy partition cache. At startup, a primary and secondary multi-tenancy partition cache are allocated, each with the number of entries specified by this startup parameter. INCREASETO modifies the size of only the secondary cache.
-secsize
Specifies the size of the secondary security cache. At startup, if the database is enabled for authentication through use of the OpenEdge Authentication Gateway, two security caches are allocated: a primary cache and a secondary cache, each with a number of entries specified by this startup parameter. INCREASETO modifies the size of only the secondary cache.
-indexrangesize
Specifies the number of rows maintained in the _IndexStat VST.
-lobrangesize
Specifies the number of rows maintained in the _LobStat VST.
-tablerangesize
Specifies the number of rows maintained in the _TableStat VST.
-userindexrangesize
Specifies the number of rows maintained in the_UserIndexStat VST.
-userlobrangesize
Specifies the number of rows maintained in the _UserLobStat VST.
-usertablerangesize
Specifies the number of rows maintained in the_UserTableStat VST.
-clstmtAllocationFactor
Specifies the number of connections you want to account for when reserving shared memory.

INCREASETO enables the identified startup parameters to be increased while the database is online improving database resiliency by minimizing planned downtime exclusively for changes to startup parameters. The improved database resiliency provides a robust, high availability mechanism that allows you to modify commonly used database resources while the database is online.

Notes

  • You can update any number of parameters with a single INCREASETO command. For example:

    proutil db-name -C increaseto -B 10240 -L 20480 -bibufs 360 -aibufs 500
  • If a value specified to increase to is less than the current value, an error is reported and the current value is not changed.
  • Only one instance of INCREASETO can connect to an online database at a time.
  • The parameters specified using INCREASETO are restricted by the currently supported limits. For example, the maximum increase for the number of blocks in the database buffer is limited to 1,000,000,000 for 64-bit platforms. See Database Startup Parameters in Manage the OpenEdge Database for more information on range and limits of -B, -L, -bibufs, -aibufs, -Mxs, -B2, -cdcsize, -n, -omsize, -pica, -mtpmsize, -secsize, -indexrangesize, -tablerangesize, -lobrangesize, -userindexrangesize, -usertablerangesize, and -userlobrangesize.
  • You must have security privileges on the directly connected database to use INCREASETO.
  • All users directly connected to the database must have privileges to read any new shared-memory segments created by INCREASETO. If a user does not have access, INCREASETO prompts you to disconnect the under-privileged users or abort the INCREASETO.
  • All utilities that wait for screen input (PROMON, DBUTIL, PROUTIL, and REPLMON) check for shared memory connection requirements every two seconds. Self-service clients check the interval defined by -dbnotifytime, which, if not specified, defaults to 30 seconds. These asynchronous checks provide the ability such that an INCREASETO operation for database utilities does not have to wait for the utility to exit screen input or disconnect from the database before continuing. An INCREASETO operation for self-service clients need not wait for the client to attach to new shared memory segments, before continuing.