Overview of a baseline report

You can generate a baseline report to track what has been captured for a specific baseline.

Related topics

Generating-a-baseline-report

Taking-a-snapshot-of-a-database-environment

The report includes general information about the baseline, DDL and commented-out GRANT statements for each object, and the unload data set names that are associated with a recoverable baseline.

Example of ALUIN input stream for a baseline report

SSID DEBA
REPORTTYPE BASELINE
OBJECTS (RDACRJ.BL02)

The REPORTTYPE keyword specifies that you want to create a baseline report. The OBJECTS keyword specifies to use the baseline named RDAMAF.IBMSAMPDB.

You can manually insert the new TERMINATOR keyword into the ALUIN input stream to change the character that separates SQL DDL statements. The value for the TERMINATOR keyword can be any character except a blank, comma (,), double quotation mark ('), single quotation mark ('), left parenthesis [(], right parenthesis [)], or an underscore (_).

If the TERMINATOR keyword is not specified, and if the DDL contains a CREATE TRIGGER or ALTER TRIGGER SQL statement and the trigger text includes a semicolon, the Baseline Report component inserts the --#SET TERMINATOR control statement into the report and uses the pound sign as the SQL statement terminator or separator. Like the value for the TERMINATOR keyword, the value for the --#SET TERMINATOR statement can be any character except a blank, comma, double quotation mark, single quotation mark, left parenthesis, right parenthesis, or an underscore. If the trigger text does not include a semicolon, the Baseline Report component uses a semicolon as the terminator or separator.

The report contains the following information:

  • Baseline header information
    • Baseline name
    • Name of the profile that was used to create the baseline
    • Timestamp of when the baseline was created
    • Baseline status
    • Whether the baseline can be used for a full recovery
    • DDL baseline (the data set name that contained the DDL or worklist)
    • Whether the baseline is designated as protected from deletion
    • Baseline type
    • Counts of the objects and authorizations in the baseline
    • The version of BMC AMI Change Manager for Db2 that was used at the time that you took the baseline and at the time that you generated the baseline report
    • The version of Db2 on which Change Manager was running at the time that you generated the baseline report
    • A list of the maintenance that was applied to the version of the product at the time that you generated the baseline report

  • Executable SQL DDL statements (in SPUFI format) for objects that are stored in the baseline

    When you generate a baseline report for native stored procedures and advanced triggers, the product includes -SQLP commands to preserve the syntax format. If you attempt to use a baseline report that includes -SQLP commands as input in IBM SPUFI or BMC AMI Catalog Manager for Db2, the process will fail.

    Objects that are implicitly defined are commented out.

    Warning

    The DDL statements are in order by object type and object name (for example, table, synonym, alias, and view). As a result, they might not be in the correct order to execute without generating an error. That is, if an alias or synonym references a view, the product might generate an error because the view statement occurs after the alias or synonym statement.

  • Data set information that is associated with a full-recovery catalog baseline (table names, data set names, record identifiers, and source type for an XML or LOB file reference)

  • SQL GRANT statements that indicate the authorizations for the objects that are stored in the baseline

    Important

    The SQL GRANT statements are in order by object type and object name and are commented out.

This section contains the following topic:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*