As many as you want.
Reuse DBC and LGC
All of the Above
GUD Workbench for DB2
RMD/ARM Recovery Management/Recover Plus
ACT CATALOG MANAGER for DB2
PSS SQL Explorer for DB2
ALM PACLOG for DB2
$B, $R, $G, $C, $U
$B, $R, $U, $G, $C
$B, $R, $G, $U, $C
That BMC DB2 recovery tools are the best of breed
That it is possible to recover lost DB2 data with only software
Hardware strategies cannot help with major disasters
It is possible to build a robust DB2 recovery strategy using only hardware technologies
It will return incorrect results
It may adversely affect the performance of existing applications
It will increase business to the extent that the company cannot cope
It will bring down DB2
Data can be stored in DB2 whilst the application still issues IMS calls to access it
People can retrain their IMS DBAs to work with something more useful, like DB2
Only minor changes need to be made to existing IMS programs
DB2 data can be moved to IMS and accessed using SQL
Migrate directly to DB2 11 CM9.
Migrate to DB2 10 CM9, then to NFM, then to DB2 11 CM.
You’re screwed. Move to Oracle.
Unload all data, install a new DB 11 subsystem, and load the data there.
They can convert a high RBA system to data sharing, but if the Delta is high enough, they will run out of LRSN.
Log files are getting really, really big.
Reordered Row Format didn’t put BMC out of business, so IBM came up with this.
Some customers write more than 256 TB of log every couple of years
As soon as they migrate to DB2 11.
After migration to NFM.
After migration to NFM, completion of DSNJCNVT utility, and reorg/rebuild of all spaces.
After running a reorg
The space is not put in REORP in DB2 11, but in AREOR, so applications can continue to access the table.
You can now alter 255 byte limit keys, instead of being limited to 40 bytes.
Altering limit keys doesn’t bring down DB2 any more.
You only have to reorg the partitions you altered now, instead of the whole tablespace.
We think LOB’s are a flash in the pan.
We were busy doing XML support for State Farm.
We have supported LOB’s for several releases. We deferred specific DB2 10 support to improve the quality of our releases.
We had higher priorities, like Binary XML and Online Schema Change.