| Specifies the type of report that BMC AMI Log Master generates. The following paragraphs list and describe the reports generated by each TYPE keyword. For more information about different types of reports, such as sample reports or ordering defaults and restrictions, see Reference-of-default-Log-Master-reports. | |
|---|
| Provides information about changes in data that would complicate an UNDO or REDO action. For each change that is part of an UNDO or REDO action, the report shows information about the change and about subsequent changes that would be affected if the original change is executed. The report also supplies information about the set of affected objects and the volume of information affected by the changes. The report presents only data associated with committed transactions. To generate a Backout Integrity report, BMC AMI Log Master scans the Db2 log to the current time, even if you do not specify CURRENT as your end point. BMC AMI Log Master takes this action because the log records that you select might be affected by subsequent transactions that occur after your time frame. BMC AMI Log Master defines the current time as the last relative byte address (RBA) or log record sequence number (LRSN) that Db2 has written to the log when the BMC AMI Log Master job begins executing. BMC AMI Log Master can produce the Backout Integrity report in two formats: Detail (including field data and all URID information) or Summary (a more concise report, omitting field data and some URID information). Use the SUMMARY keyword to generate the concise version of the Backout Integrity report. BMC AMI Log Master cannot produce either version of a Backout Integrity report when the input source of your log scan is individual Db2 log files (INPUT DB2LOG). | | Provides information about ranges within the Db2 log when no activity is present for a given set of Db2 objects. The report lists only the quiet ranges common to all table spaces defined (either directly or indirectly) by your WHERE clause or filter. The optional MAXURIDS keyword enables you to list ranges when the amount of activity is below a level that you specify ('almost quiet' ranges). To generate this report, ensure that your WHERE clause or filter refers to at least one specific Db2 object (such as a table name or a column name). This action ensures that you define (either directly or indirectly) a set of table spaces that BMC AMI Log Master can search for quiet ranges. BMC AMI Log Master cannot produce a Quiet Point report when the input source for your work ID is individual Db2 log files (INPUT DB2LOG) or a logical log file generated by BMC AMI Log Master or another program (INPUT LLOG). | |
|---|
| By default, the Quiet Point report includes all quiet ranges for the specified Db2 objects (no minimum). Use this keyword to exclude shorter quiet ranges from the report. BMC AMI Log Master suppresses any quiet ranges that are shorter than the duration that you specify. Enter a minimum duration, using the time format shown in the syntax diagram. Enter any value from one microsecond to 24 hours. You must enter numeric values for hours, minutes and seconds, but microsecond values are optional. For example, to specify five seconds, enter 00.00.05 in the syntax. | | By default, the Quiet Point report includes only quiet ranges that are completely quiet (absolutely no activity for the table spaces directly or indirectly defined by your filter). By using this keyword, you can include 'almost quiet' ranges in the report. These ranges are periods within the log when the number of open transactions (units of recovery) that affect your table spaces is less than or equal to the number that you specify. Use this keyword to report on periods of high activity for your specified objects, when completely quiet ranges might not exist. The report includes both the almost quiet ranges and the completely quiet ranges. For each quiet range, the report lists the number of open transactions that are present during the range. Enter a number of open transactions between zero and thirty-two. Zero indicates that the report includes only completely quiet ranges. The default value is zero. | | You can direct BMC AMI Log Master to insert a quiesce entry into the Db2 catalog table SYSIBM.SYSCOPY for each table space defined (directly or indirectly) by the WHERE clause or filter. Specify YES to insert a quiesce record in SYSIBM.SYSCOPY using the RBA/LRSN of the latest quiet range included in the report. Specify NO to avoid inserting a quiesce record. The default value is NO. When you specify YES, BMC AMI Log Master also inserts index quiesce records into SYSIBM.SYSCOPY for any COPY YES indexes associated with the table spaces. BMC AMI Log Master records the correct quiet point registration so all recoverable objects have the proper QUIESCE entry in SYSCOPY. BMC AMI Log Master does not insert a quiesce record if: - BMC AMI Log Master finds no quiet ranges that meet your criteria
- The report includes only almost quiet ranges
If you use a report template to customize the Quiet Point report, you can direct BMC AMI Log Master to sort the quiet ranges based on duration. If you sort in ascending order, BMC AMI Log Master uses the longest quiet range in your report as the point to insert a quiesce record in SYSIBM.SYSCOPY. | | Specifies the return code (RC) with which BMC AMI Log Master will end if no quiet points are found. INFO, WARN, ERROR, SEVERE, and UNRECOV translate to RCs of 0, 4, 8, 12, and 16, respectively. You can also use a value between 0 and 4095. The default is WARN. The NOQUIETPOINTRC value determines the severity of message BMC097547. The setting of the severity code is as follows: Important NOQUIETPOINTRC must be greater than the resulting return code set during normal processing; otherwise, it will be overwritten. For example, if NOQUIETPOINTRC is set to 6 and BMC AMI Log Master encounters an unrecoverable error, BMC AMI Log Master will end with RC=16, not RC=6. | | By specifying a log mark name with the MARK option, you can direct BMC AMI Log Master to record a log mark with the RBA/LRSN associated with the quiet point. BMC AMI Log Master does not record the log mark if: - BMC AMI Log Master finds no quiet ranges that meet your criteria
- The report includes only almost quiet ranges
If you use a report template to customize the Quiet Point report, you can direct BMC AMI Log Master to sort the quiet ranges based on duration. If you sort in ascending order, BMC AMI Log Master uses the longest quiet range in your report as the point to record the log mark. | | Defines an optional, 65-character text string. Use the text description to store any comments that you want to associate with the log mark name. |
| | Provides a record of changes to data, identifying who changed the data, when it was changed, and how much data was changed. This report also gives related index and record ID (RID) information. The Audit report is similar to the report produced by the DETAIL keyword, except that the Audit report presents only changed data from updated log records, and it includes primary key information. You can also use an Audit report to show information about changes to the Db2 catalog, including changes to Db2 security. The Catalog Activity report also provides this information. The REDO keyword is valid for only Audit, Detail, or Summary reports. Use the REDO keyword only when you want a report to show you which log records would be selected for a REDO operation based on your current WHERE clause or filter. The keyword determines how BMC AMI Log Master uses your filter to select log records for the output report. For more information, see REDO. | | Provides information about changes that affect the Db2 catalog, including - The type of Db2 object that was changed
- The type of data definition language (DDL) statement that changed the object
- URID-related information about the process, program, or user that made the change (for example, authorization ID or correlation ID)
A Catalog Activity report can show all changes that affect a given object type (for example, indexes), or all changes that result from a given DDL statement type (for example, GRANT and REVOKE statements to show security changes). This report contains the same basic information that would be included if you generated a MIGRATE DDL output file with the VERBOSE keyword. Be aware of the following points as you define a Catalog Activity report: - (BMC.DB2.SPE2310) To generate a Catalog Activity report, you must set the value of the DB2CATALOG keyword to DDL.
- The Catalog Activity report uses a wide format for data. Specify a logical record length (LRECL) value of at least 132 bytes to support the data format.
- Catalog-activity-definition and Catalog-object-definition provide filter options that are helpful with the Catalog Activity report.
- ORDER-BY-definition provides the ACTVITY TYPE and OBJECT TYPE keywords to conveniently sort a Catalog Activity report.
- To obtain the information that you need, you might need to include some additional Db2 objects in your filter. For more information about filter optimization and usage, see Working-with-filters.
- When you generate a Catalog Activity report, BMC AMI Log Master can generate an output DDL file or update the Repository, but it cannot generate other forms of output in the same log scan (such as other reports or SQL). To generate other output in the same job, include an additional, separate log scan step.
| | Provides a summary of activity with the addition of column detail if the table was updated. The report maintains counts for each changed column and provides a total number of changed columns. You can use this report to assist in index tuning and to determine whether placing an index on a column would have a negative impact. The report details include: - Name
- Number
- Type
- Length
- Indexed column (Y/N)
- Frequency (the number of times a column was updated)
ORDER-BY-definition provides information about the update frequency of the table column. | | Provides information about Db2 commands that were issued within a specified period on a Db2 subsystem. Be aware of the following points as you define a Commands report: - ORDER-BY-definition provides the COMMAND keyword to conveniently sort a Commands report.
- When you generate a Commands report, BMC AMI Log Master cannot generate other forms of output in the same log scan (such as other reports or SQL). To generate other output in the same job, include an additional, separate log scan step.
| | Provides information about commit frequency for application tuning and system performance purposes. Depending on how you order the report, counts are maintained for each unit of recovery to indicate the activity volume between commit points. Use this report to determine if batch jobs are not committing changes according to standards or performance recommendations. You can also use it to determine if online transactions are performing too many operations in a given unit of work. | | Provides information about log records with either the data capture changes (DCC) or data capture none (DCN) attributes. This report provides information to help determine the impact of setting the data capture changes attribute on specific tables. BMC AMI Log Master estimates the number of bytes that would be logged if you set data capture changes on or off. | | Provides information about log records. Use this report to display log data to help diagnose application problems, or to show log data as an audit trail for applications. This report is similar to the report produced by the AUDIT keyword, except that the Detail report presents all data from update log records, and it does not include primary key information. You can also use a Detail report to show information about changes to the Db2 catalog, including changes to Db2 security. (The Catalog Activity report offers a more concise version of the same basic information. For more information, see CATALOG ACTIVITY. The REDO keyword is valid for only Audit, Detail, or Summary reports. Use the REDO keyword only when you want a report to show you which log records would be selected for a REDO operation based on your current WHERE clause or filter. The keyword determines how BMC AMI Log Master uses your filter to select log records for the output report. For more information, see REDO. | | Provides information about the volume of table space activity between image copies. For the table spaces selected (directly or indirectly) by your filter, the report shows data on all applicable image copies logged in the SYSIBM.SYSCOPY table of the Db2 catalog during your time frame. For each image copy listed, the report shows the activity (the number of insert, update, and delete actions) since the preceding image copy. Use this report to determine if a table space has too many updates between copies (which could lead to excessive recovery times) or if a table space is being copied more often than necessary. | | Provides information about transactions (units of recovery) that are not committed or aborted at the end point of your log scan, including any transactions that begin before the start point of your log scan. Use this report to identify any work that might not be represented on other product reports. Be aware of the following points regarding this report: - BMC AMI Log Master reads Db2 checkpoint records before the start point of your log scan to obtain information about the transactions that were open when the checkpoint record was created.
- The report can include open transactions that do not affect the Db2 objects selected (directly or indirectly) by your filter. BMC AMI Log Master includes these transactions because an open transaction might include activity affecting your selected objects past the end point of your log scan.
- The transactions included in the report can vary depending on whether your filter selects log records based on the unit of recovery criteria (for example, by plan name or authorization ID).
- If your filter selects based on the only unit of recovery criteria, the report includes only the open transactions selected by your filter.
- If your filter selects based on either 1) only object-specific criteria (such as table name or column name), or 2) both unit of recovery and object-specific criteria, the report includes all open transactions on the current Db2 subsystem.
- The activity counts in the report are based on the log records selected by your filter and the range of your log scan. Treat the counts as estimates of the activity associated with open transactions; do not use them as definitive data.
| | Provides information about all rollback actions performed over a specified period of time, including the frequency and number of associated transactions. Depending on how you order the report, it can present activity counts for each rolled-back transaction (in this context, transactions are considered to be the same as URIDs). The Rollback report contains only aborted transactions and cannot include committed transactions. Use this report to determine the amount of activity associated with rollback actions or to pinpoint jobs or transactions that are frequently rolled back. | | Provides information about the distribution of log records in the Db2 log. It focuses on the type, size, and distribution of log records, and not on the actual data contained in the log records. The Log Bytes report displays the following information about log records: - Counts of many log record types
- Total number of bytes used by the log records
- Percentage of space the log records use
Use the Log Bytes report for tuning purposes, to help you reduce unnecessary overhead in the log. When you generate a Log Bytes report, BMC AMI Log Master cannot include any other forms of output in the same log scan, such as other reports or SQL. To generate other forms of output for the same work ID add an additional separate log scan step. | | Provides summaries of transaction count information (the number of insert, update, and delete actions). Use this report to determine how many transactions are processed by various sort keys, or to show how much SQL would be generated by a REDO or UNDO operation on a given table space. | |
|---|
| This keyword is valid for only Audit, Detail, or Summary reports. Use this keyword only when you want a report to show you which log records would be selected for a REDO operation based on your current WHERE clause and Range definition. The keyword determines how BMC AMI Log Master selects the log records for the output report. When REDO is not specified, BMC AMI Log Master selects log records for your report that are selected by your filter and Range definition (as it does when it generates MIGRATE or UNDO SQL statements.) This value is the default and is recommended for most uses. When REDO is specified, BMC AMI Log Master selects log records for your report that are within the table spaces defined (directly or indirectly) by the filter, and within the period from the REDO recovery point to the current time. Then BMC AMI Log Master excludes the log records that are selected by your filter and Range definition. BMC AMI Log Master selects log records in this manner because it assumes that any REDO operation takes place after a recovery, and that you want to reapply all of the log records except the problem log records defined by your filter. For more information about REDO operations, see REDO. | | Use the ALL ACTIVITY keyword to generate an Object Activity Summary report. This report presents database activity (insert, update, and delete actions) from all transactions, including transactions that relate to Db2 objects that are no longer in the Db2 catalog, and transactions that are not complete within your scan range (not yet committed or aborted). With few exceptions, this version of the report presents information from all selected data management (DM) records in the Db2 log. You cannot generate an Object Activity Summary report if BMC AMI Log Master is reading log records from a logical log file previously created by BMC AMI Log Master or an application program, or if your filter selects log records based on a column’s value (for example, WHERE TABLE01.QUANTITY > 500). For more information, see Object-Activity-Summary-report. | | Use the FORMAT keyword to generate Summary report output that includes only data (no report headings, column headings, or blank lines). BMC AMI Log Master provides two different formats, both of which use character representation for all data to make it easy to move data to other platforms: - Specify CSV to generate data in the Comma Separated Value (CSV) format. Individual items of data are separated by commas.
- Specify SDF to generate data in the Standard Definition Format (SDF) format. Individual columns of data are filled with spaces so that each column has the same position and length on all lines of the output.
For either format, ensure that the logical record length (LRECL) of your report output file is long enough to contain the longest line in the report. For examples of report output in the CSV or SDF formats, see SQL-statements-versus-report-output. | | Use the INCLUDE TOTAL keyword to include subtotal and report total lines in the output. This keyword is valid only when the format of the report is CSV or SDF. By default, subtotal and report total lines are not included. |
| | Provides information about database exception (DBE) records that are logged by Db2 utilities, including MODIFY and REPAIR. These records reflect changes to table space status, data pages, deleted rows, DBD repairs, and versioning. This information can be crucial for recovery purposes because it includes data changes and other actions that cause spaces and indexes to go in and out of restricted status. When you generate a Status Changes report, BMC AMI Log Master cannot generate other forms of output in the same log scan (such as other reports or SQL). To generate other output in the same job, include an additional, separate log scan step. Consider the following when you define a Status Changes report: - ORDER-BY-definition provides the STATUS and UTILITY keywords to conveniently sort a Status Changes report.
- When BMC AMI Log Master processes a DBE record, some of the report dictionary items might not be accurately populated if the Begin UR record is logged before the start of the BMC AMI Log Master scan range. In this case, the following will be reported as UNKNOWN:
- AUTH ID
- CONNECTION ID
- CONNECTION TYPE
- CORRELATION ID
- DATA SHARING MEMBER NAME
- DATA SHARING MEMBER ID
- PLAN NAME
- SSID
|
|
