DB2 10.5 for Linux, UNIX, and Windows

ALTER USAGE LIST statement

The ALTER USAGE LIST statement alters the definition of a usage list.

Invocation

This statement can be embedded in an application program or issued interactively. It is an executable statement that can be dynamically prepared only if DYNAMICRULES run behavior is in effect for the package (SQLSTATE 42509).

Authorization

The privileges held by the authorization ID of the statement must include one of the following privileges:

DBADM authority
SQLADM authority

Syntax


>>-ALTER USAGE LIST--usage-list-name---------------------------->

   .--------------------------------------.   
   V  (1)                                 |   
>----------+-LIST SIZE--integer-value---+-+--------------------><
           +-WHEN FULL--+-WRAP-------+--+     
           |            '-DEACTIVATE-'  |     
           +-INACTIVE ON START DATABASE-+     
           '-ACTIVE ON START DATABASE---'

Notes:

The same clause cannot be specified more than once

Description

usage-list-name

Identifies the usage list to be altered. The usage-list-name must identify a usage list that exists at the current server (SQLSTATE 42704).

LIST SIZE integer-value

Specifies that the size of this list is integer-value entries. The minimum size that can be specified is 10 and the maximum is 5000 (SQLSTATE 428B7).

WHEN FULL

Specifies the action to perform when an active usage list becomes full.

WRAP: Specifies that the usage list wraps and replaces the oldest entries.
DEACTIVATE: Specifies that the usage list deactivates.

INACTIVE ON START DATABASE

Specifies that the usage list is not activated for monitoring whenever the database is activated. Collection must be explicitly started using the SET USAGE LIST statement.

ACTIVE ON START DATABASE

Specifies that the usage list is automatically activated for monitoring whenever the database is activated. In a partitioned database environment or DB2® pureScale® environment, the collection is automatically started whenever the database member is activated.

Notes

When changes take effect: If the current state of a usage list is active, then the alterations do not take effect when the statement is processed or when the changes are committed. The changes to the usage list take effect the next time the state of usage list is set to active. In a partitioned database environment or DB2 pureScale environment, the alterations take effect the next time the usage list at a member is activated.