The onutil SET REPACK_THREAD_MAX Command

A new onutil command can reset the value of the REPACK_THREAD_MAX parameter at run time. It has this syntax:

>>-onutil--SET REPACK_THREAD_MAX--value------------------------->
 
>--+---------------------+-------------------------------------><
   +-COSERVER-+-number-+-+
   |          '-name---' |
   +-PERSISTENT----------+
   '-PROPAGATE-----------'
 

Here value is an unsigned integer in the range from 0 to 2,147,483,647.

If the optional PERSISTENT keyword is omitted, the value that onutil specifies for REPACK_THREAD_MAX is in effect until the session ends, or until another onutil SET REPACK_THREAD_MAX command specifies a new value.

The DBSA can set the value to zero to interrupt all active repack threads.

Unless the PERSISTENT keyword is included in the command, values set by this command are lost when the database server is restarted, and the value of REPACK_THREAD_MAX reverts to what the configuration file specifies or defaults to. If the DBSA specifies the PERSISTENT keyword, then the specified value remains in effect when the server is restarted, and persists until another onutil SET REPACK_THREAD_MAX command specifies a new value.