Sports Illustrated faces daily, even hourly, competition with ESPN, Yahoo Sports and others, but it has something its main rivals do not: a 53-year trove of articles and photos, most of it from an era when the magazine dominated the field of long-form sports writing and color sports photography.
Sports Illustrated has introduced the Vault, a free site within SI.com that contains all the words Sports Illustrated has ever published and many of the images, along with video and other material, in a searchable database.
DMS rebalancer is active
APAR IY48902 describes a problem which occurs when you issue an ALTER TABLESPACE command which seems to succeed–that is, there are no error messages–but in fact the operation is not performed.
A major symptom that we saw was that the db2rebal process wasn’t running even though the db2 list tablespaces show detail told us DMS rebalancer is active. Secondary symptoms were that the 4th container was not being used – the difference between usable pages and used pages is 49952 which was the size of the 4th container less 48 pages of DB2 control data)
Total pages = 343750 Useable pages = 343648 Used pages = 293696 Free pages = 0 High water mark (pages) = 293696
However, IBM do provide a utility that helped (in our case anyway). The APAR says that you need to be at DB2 V8.1 FixPak 6 – we are at FixPak 5
APAR IY48902
http://www-1.ibm.com/support/docview.wss?rs=71&context=SSEPGG&q1=IY48902&uid=swg1IY48902&loc=en_US&cs=utf-8&lang=en+en)
Utility for finding and fixing
http://www-1.ibm.com/support/docview.wss?rs=71&context=SSEPGG&q1=IY48902&uid=swg21176205&loc=en_US&cs=utf-8&lang-=en
Once you’ve run the utility in fix mode, shutdown db2 (using db2_kill if necessary) then restart db2. db2 list tablespace containers should only show the containers that existed prior to the ALTER TABLESPACE that caused the problem.
from DB2 DeveloperWorks
Data replication option
DB2 UDB includes integrated replication abilities. DB2′s implementation of replication consists of two pieces: Capture and Apply. The replication administrator designates replication sources from tables to be replicated, and then creates replication subscriptions on a target database, the secondary system, using the replication sources from the previous step as its source. The Capture process monitors the transaction logs for all changes to the replication source tables, placing any changes made to these tables into staging tables. The Apply program reads the staging tables and moves the changes to the subscription target on a timed interval.
Data replication is an asynchronous process. For a period of time either while the changed data has not yet been placed in the staging tables or while the Apply program has not replicated the changes to the target system, the two databases are out of sync. This is not necessarily a long period of time or a large amount of data but it must be considered a possibility.
Log shipping option
All database changes (inserts, updates, or deletes) are recorded in the DB2 transaction logs. Transaction logs are primarily used for crash recovery and to restore a system after a failure. As we’ve already discussed, they play a role in replication. In addition, they play a role in another high availability solution, log shipping. This HA scheme is similar to the data replication option. It requires a secondary system ready to take over in the event the primary system fails. The administrator creates this secondary system by restoring a backup of the primary system database. The backup system would be placed in a roll-forward pending state by restoring a database backup of the primary system. Transaction logs are moved from the primary system to the secondary and used to roll the database forward through the transactions. In the event of a failure the administrator stops the process of rolling forward and the database is brought online.
Like the replication option, log shipping is an asynchronous process. The secondary system is out of sync as long as there is an active log file on the primary system and there are outstanding log files that have not been applied.
Also see:
Setting Up a User Exit on DB2 UDB V8 to Archive Database Logs
The Basics of DB2 Log Shipping
Copying Your SAP/R3 System Across Platforms Using DB2 Universal Database V8 Redirected Restore