ORDER BY definition

Sorts reports based on activity, in descending order. Activity in this context represents the number of database changes (insert, update, delete, or exchange actions) that have occurred against a given Db2 object.

Sorts reports based on the type of Db2 catalog activity. This criteria is valid only for a Catalog Activity report. You can also think of this syntax as sorting the report based on a type of data definition language (DDL) statement. For example, the report can group together all log records that reflect DROP statements, or ALTER statements.

Sorts reports based on authorization ID. An authorization ID is a character string used to connect to Db2; it frequently represents an individual, a work group, or a function.

Sorts reports based on the column name. The following conditions apply:

• The column name must be the last option in the order-by list.
• Either the column name or column number must be included in the order-by list, but not both.

• Column names are not qualified with the table creator and table name. Consequently, if you need to report on multiple tables, the order-by list should include Table Name, even though the table name is not required.

  Important

  This criteria is valid only for a Column Update Frequency report.

Sorts reports based on the column number. The following conditions apply:

• The column number must be the last option in the order-by list.
• Either the column name or column number must be included in the order-by list, but not both.

• Column numbers are not qualified with the table creator and table name. Consequently, if you need to report on multiple tables, the order-by list should include Table Name, even though the table name is not required.

  Important

  This criteria is valid only for a Column Update Frequency report.

Sorts reports based on a Db2 command name or a synonym that Db2 supports, such as START DATABASE (-STA DB). This criteria is valid only for a Commands report.

Sorts reports based on connection ID. A connection ID is a string identifier associated with a specific address space connection.

Sorts reports based on connection type. A connection type is a string constant representing the manner in which a unit of recovery thread is attached to Db2. For a list of possible connection type values, see CONNECTION TYPE.

Sorts reports based on correlation ID. A correlation ID is a unique string identifier for a specific Db2 thread.

Sorts reports based on the RBA/LRSN value when a Db2 object was created. Use this value to sort reports that BMC AMI Log Master produces when it runs in overtime mode. For example, in overtime mode two different instances of a table can have the same name (and possibly the same DBID or OBID). By using this value, you can separate the data from each instance of the table.

You must specify TABLE NAME or OBID as a sort criteria before you specify CREATE RBA.

Sorts reports based on database names.

Sorts reports based on database ID (DBID). A DBID is an internal identifier assigned to a database by Db2.

Sorts reports based on data set number. The data set number is the ordinal number of a given data set within a table space (usually a partitioned table space).

LUWID 

(BMC.DB2.SPE2310)

Sorts reports based on the Local Unit of Work Identifier (LUWID) and is a unique identifier that represents a group of related database operations that are treated as a single unit. These operations can include one or more SQL statements that need to be executed together, ensuring data consistency and integrity.

Sorts reports based on the member ID of a given member of a data sharing group. Use this keyword only with reports generated in a data sharing environment.

Sorts reports based on the name of a given member of a data sharing group. Use this keyword only with reports generated in a data sharing environment.

Sorts reports based on object ID (OBID). An OBID is the internal identifier that Db2 assigns to an object.

Sorts reports based on the type of Db2 object. This criteria is valid only for a Catalog Activity report. For example, the report can group together all log records that affect tables or all log records that affect indexes. Besides the commonly used objects, such as tables and columns, the object type includes other objects defined in the Db2 catalog, such as plans, packages, collections, and buffer pools.

Sorts reports based on plan name. A plan name is a character string representing an application plan, the control structure used by Db2 to process SQL statements.

Sorts reports based on the primary key of a table. The primary key of a table is a column or set of columns within a table, defined so that there is one unique primary key value for each row in the table. If you specify PRIMARY KEY, but a table has no primary key defined, BMC AMI Log Master selects a key to use. For more information, see QUALIFY.

Sorts reports based on page set ID (PSID). A PSID is an internal page set identifier assigned to a given table space by Db2.

Sorts reports based on the subsystem identifier (SSID) of a given Db2 subsystem. Use this keyword only with reports generated in a data sharing environment.

Sorts reports based on status change type.

For a description of the statuses that BMC AMI Log Master detects and reports on, see STATUS.

Sorts reports based on the names of tables selected in your WHERE clause or filter.

Sorts reports based on the names of table spaces selected in your WHERE clause or filter.

Sorts reports based on unit of recovery identifier (URID). A URID is a hexadecimal value assigned by Db2 to a recoverable sequence of operations within Db2.

Sorts reports based on Db2 utility name.

For a description of the utilities that BMC AMI Log Master detects and reports on, see UTILITY.