Category: Architecture

5

Architecting High-Availability and Disaster Recovery Solutions with DB2

NOTE: Please do not attempt to architect a high-availability solution without a DB2 expert involved. There are many questions and answers needed beyond those here to make the best decision and ask all the tough questions. High Availability vs. Disaster Recovery High Availability and Disaster Recovery often have different goals and priorities. High Availability can be considered the ability to...

1

DB2 Basics: Filesystems for DB2 on Unix and Linux Systems

DB2 doesn’t have any defaults for filesystems because that is an OS-level thing. However, there are a few sanity checks and some recommeded separation when installing DB2 on Linux and UNIX operating systems. These are my best practices for installations, in general terms. Software Location The default location for installing the DB2 code in /opt/ibm/db2/V10.5 (replacing V10.5 with whatever version)....

ibm-blu 1

A Deeper Dive into DB2 BLU

I started out with a DB2 Basics entry on BLU. That starts with the most basic concepts. In this post, I’d like to delve into some of the details of BLU and talk about when BLU is beneficial and when it may be detrimental and why. BLU Workloads If you’re considering BLU consider first that it is not for all...

2

DB2 Basics: Aliases

My blog entries covering the DB2 Basics continue to be my most popular blog entries. This is probably because they appeal to a wider audience – even non-DBAs are interested in them and I continue to rank highly in Google search results. My blog entry on how to catalog a DB2 database gets a ridiculous 50 page views per day,...

1

DB2 Basics: Storage Groups

What is a Storage Group? A storage group is a layer of abstraction between the data in your database and disk. It is only used with Automatic Storage Tablespaces (AST). It allows us to group tablespaces together to live in similar places. Storage groups were first introduced in a roundabout way with automatic storage databases in DB2 8.2. These databases...

9

Redesigning Tablespaces in an Existing Database

Like many applications, WebSphere Commerce puts all tables in USERSPACE1 unless they need larger page sizes. This actually works just fine for smaller and midrange implementations, but we have about one build a year that requires something else – either because of standards that client DBAs adhere to or because they actually are busy enough for I/O and separate buffer...

2

DB2 Naming Standards

Last week, I read this article by Craig Mullins: http://www.sswug.org/articlesection/default.aspx?TargetID=70585. Go read it, this blog entry will still be here when you get back. I have to say that in large part, I agree. I don’t like having differing naming standards for tables and views. And certainly not for aliases. I do like to have a naming standard for constraints...

7

DB2 LUW – What is a Page?

The logical view of a database consists of the standard objects in any RDBMS – Tables, Indexes, etc. There are a number of layers of abstraction between this and the physical hardware level, both in the OS and within DB2. Setting the Page Size The smallest unit of I/O that DB2 can handle is a page. By default, the default...