SHRLEVEL
SHRLEVEL REFERENCE
SHRLEVEL REFERENCE is the default and allows read-only access by other programs to the target space during the rebuild process.
SHRLEVEL CHANGE
SHRLEVEL CHANGE allows read-write application access to Db2 table space and index space objects during the rebuild process.
Performing an online rebuild index by specifying SHRLEVEL CHANGE offers the following benefits:
- Allows full access to Db2 data during most of the rebuild
- Delivers significantly improved data availability by greatly reducing the outage for the Db2 objects
- Operates in a non-destructive manner, which allows you to make the objects available without having to recover in the event of a failure
Option | Description | ||||||||
|---|---|---|---|---|---|---|---|---|---|
MAXRO integer | Specifies the maximum number of seconds that BMC AMI Recover spends applying log records for the last iteration of log processing. integer can be any positive integer (0 or greater). During the iteration, applications have read-only access. The actual runtime of the last iteration might exceed the specified value for MAXRO integer. Specifying a small positive value reduces the length of the period of read-only access, but it might increase the time for REBUILD INDEX to complete. If you specify a very large positive value, the second iteration of log processing will probably be the last iteration. The default value is the value of the lock timeout system parameter IRLMRWT. It is used if MAXRO is not specified or you specify the value as 0. | ||||||||
LONGLOG | Specifies the action to take if BMC AMI Recover determines that a longlog condition exists. A longlog condition exists when BMC AMI Recover determines over a period of time that the Db2 subsystem is generating log records for the objects that you are rebuilding faster than BMC AMI Recover is applying the records. After detecting that a longlog condition exists, BMC AMI Recover sends an action write-to-operator (WTO) notification and continues to apply the log records until the delay interval specified on the DELAY option expires. If the longlog condition still exists, BMC AMI Recover takes the action that you specify with one of the following options.
| ||||||||
DELAY | Specifies the number of seconds that should elapse from the time BMC AMI Recover detects a longlog condition until it performs the action specified by the LONGLOG option If the longlog condition no longer exists at the end of the time period specified by DELAY, the timer is reset. When BMC AMI Recover detects the next longlog condition, it restarts the timer by using the original DELAY value. The value must be a positive integer (0 or greater). The default value is 1200. | ||||||||
DRAIN_WAIT integer | Specifies the number of seconds that REBUILD INDEX should to wait when draining the table space or index. The specified time is the aggregate time for objects that are to be checked. integer can be any integer from 0 to 1800. If you do not specify DRAIN_WAIT or if you specify a value of 0, BMC AMI Recover uses the value of the lock timeout subsystem parameter IRLMRWT. | ||||||||
RETRY integer | Specifies the maximum number of retries that REBUILD INDEX should attempt. integer can be any integer from 0 to 255. REBUILD INDEX uses 1 as the default if you do not specify a value. | ||||||||
RETRY_DELAY integer | Specifies the minimum number of seconds between retries. integer can be any integer from 1 to 1800. If you do not specify RETRY_DELAY, REBUILD INDEX uses the DRAIN_WAIT value x RETRY value. |