If a system is being developed with 24/7 accessibility and has both batch and online programs that browse and update, how do you prevent contention issues?
The locking mechanism built into DB2 will prevent integrity problems due to contention. Of course, that does not mean that you can simply implement anything and everything without worrying about performance and availability. This is a very general question that could require a lot of space and effort to answer completely and in-depth. In general, though, you want to avoid long-running batch updates in conjunction with heavy online activity. The long-running batch work would tend to lock out the OLTP work.
Dig Deeper on IBM DB2 management
To export data from a DB2 table to a flat file, you need to run an export specifying the proper file format. The export utility exports data from a ...
Craig Mullins recommends two specific resources for learning how to create and support Binary Large Objects (BLOB) in DB2.
Craig Mullins explains various definitions of a data mart and sheds some light on the complexity of its relation to a data warehouse.