Log Master recovery tasks
Log Master provides functionality that enables you to perform transaction-level recoveries (undo and redo transactions), recover dropped objects, and discover quiet points for point-in-time recovery.
Identification and analysis of problem transactions
By analyzing activity reflected in the DB2 log, Log Master identifies problem transactions and generates SQL statements to back them out.
Good transactions (including those that apply to the same rows as the problem transactions) are not affected. Your database tables remain online throughout the backout process. For more information, see Backing out problem transactions.
Automated dropped objects recovery
An automated drop recovery work ID creates several forms of output that enable Log Master, working with a recover utility, to recover DB2 objects that have been dropped from the DB2 catalog.
Log Master can also create JCL to execute the different types of output in the right order to accomplish the recovery. For more information, see Recovering dropped objects.
Generation of DDL statements or objects
Log Master enables you to generate data definition language (DDL) files for migration or to reverse unwanted changes (UNDO DDL). You can process DB2 catalog log records within the log scan step and specify DDL as output. For more information about generating DDL, see DDL output files.
Optionally, you can include DDL objects in an output logical log file. DDL objects represent the DDL activity selected by your filter, but are not the same as the DDL statements that Log Master generates. A DDL object can represent multiple DDL statements, and a DDL statement can represent multiple insert, update, or delete actions against tables in the DB2 catalog. The DDL objects in a logical log file can be interpreted as input by Log Master or by the High-speed Apply Engine that is distributed with Log Master.
Analysis of quiet points
Log Master can analyze the log for a given time frame to determine log ranges during which no transactions were in process for a set of table spaces. Use this information to select start and end points as you recover from problem transactions (possibly with a conventional recovery and REDO SQL).
Optionally, you can specify a minimum duration to exclude shorter quiet ranges from the report. When you specify a duration, Log Master suppresses any quiet ranges that are shorter than the time value you specify. Use the option to exclude quiet ranges that represent only momentary pauses between parts of an overall 'logical' transaction. By excluding shorter ranges, you can concentrate on times when there is truly no activity for your table spaces. For more information, see Quiet Point report.