One of the most painful experiences in the work life of a database administrator (DBA) is probably the accidental drop of a database object on a production subsystem. Most IT shops have procedures to prevent this occurrence, yet it still happens.
Data integrity is an critical feature within every DBMS, and part of integrity is keeping data in a consistent state and recoverable. It all starts in the DB2 log. Martin Hubel describes the role of the log in recovery options gives some thoughts for log management.
This week we have IBM's Florence Dubois' presentation from IDUG NA 2014 on best practices to prepare of the recovery of multiple objects. Taking regular backups is necessary but far from sufficient for anything beyond minor application recovery.
October is Backup and Recovery month. It is also the month of goblins, ghouls and scary stories. Kurt Struyf tells us that these two themes often go together. Kurt presents a horror story of what can go terribly wrong when you don't have a good backup and recovery strategy.
How many copies of your databases do you have? I’m talking about both how many test databases with test data as well as full copies of your production data. In many shops, developers are well behaved and get along nicely. They share test databases.