The DB2 log is far more than an important part of DB2′s recovery strategy. It is also a gold mine for a variety of other significant purposes.
Database administration, application development, and maintenance programmers may use the DB2 log to repair the results of incorrect program executions, wrongly scheduled jobs or user errors. In many cases standard recovery based on image-copies is inappropriate – because it resets too much – actually specific repairs to the data are required, using log information.
Auditors and administrators may analyze the DB2 log to keep track of data access and data modifications, to document unauthorized or suspicious usage, and to set up standard procedures for data collection and examination.
Database administrators look at the log to analyze update frequencies and idle times, to identify inefficiently working programs, programs violating coding standards or to find quiet points where recovery activities can attach themselves.
And data centers more and more use log records to continuously propagate data changes to other environments, which is much more affordable and easier to handle than using conventional data propagation mechanisms.
But as getting to the gold always may be a problem, getting to the log records requires the right tool. Understanding the log records’ format is the least it can do. More importantly, it needs to be really useful. For example, seamless and robust data propagation has to be mastered, even in data sharing environments. Seamless operation is also a challenge for auditing activities, and comfortably setting the operation’s scope, automating data collection, maintaining the collected information, housing the entire auditing process within an integrated solution, is also very important. Furthermore a considerable flexibility is required regarding the output of the log analysis, which might be SQL, a text report, a CSV file, or a loadable format for various target platforms.
To learn more about all those considerations, have a closer look at the different areas of our website’s log analysis and tracking section.