Preparing a DB2 database with DBADM authority

This topic describes how to prepare a DB2 database when you have database administration authority (DBADM).

Before you begin

This creation and setup of a DB2 database assumes that the user who is preparing the Jazz database has DBADM authority over the database, and that the database, tablespace storage, and appropriate storage configurations is created by a SYSADM user. The following configuration parameters and tablespace options are recommendations and the settings are for a fully automated installation.

About this task

The Jazz database consists of tables that contain fixed length strings, variable length strings up to 1000 bytes, integers, time stamps, and blobs. Most of these database objects are small, but they can be up to a maximum of 1 GB in length. Stored procedures or UDFs are not used. The Jazz Team Server database consists of two tablespaces, one of the type Large that holds most of the tables and indexes, and the other one of type User Temporary for temp tables.

Procedure

As a SYSADM user, create a database with 8192 pages and UTF-8 code set. In general, managing storage manually and pre-allocating disk space for the two Jazz tablespaces in DMS mode gives the best performance on a single disk system. This might not be entirely applicable to your environment and you should setup the tablespaces for optimal performance. The following parameters are the database configuration parameters that are changed in the fully automated installation:
```
LOGPRIMARY 20
LOGSECOND 20
APP_CTL_HEAP_SZ 10000
APPLHEAPSZ 10000
BUFFPAGE 16384
LOGFILSIZ 4096
DBHEAP 8192
```
Create two tablespaces. The first one is of type Large and is used to hold the bulk of the Jazz data, and the second one is a user temporary tablespace.
Add the names of these two tablespace to the teamserver.properties file so the Repository Tools application can correctly install the Jazz database tables. The following is an example of a Large tablespace. Note that this is only an example and the Large tablespace should be created with settings appropriate to your environment.
```
CREATE LARGE TABLESPACE JAZZDATA MANAGED BY DATABASE USING (file '' 250000) DROPPED TABLE RECOVERY OFF AUTORESIZE YES
```
The following is an example of a user temporary space:
```
CREATE USER TEMPORARY TABLESPACE JAZZTMPSPACE MANAGED BY DATABASE USING (file '' 2500) AUTORESIZE YES
```
Create a user or grant an existing user DBADM authority over the database you created in step 1. Ensure that the DBADM user has permission to perform the following tasks:
- Create and drop tables.
- Select, insert, delete, and update those tables.
- Run statistics on the tables.
- Create a deadlock monitor for Jazz.
- Use the user temporary tablespace that was created in step 2.

As the DBADM user, add the following parameters to the teamserver.properties file before running repotools -createTables with the correct substitutions for the tablespace names and the user name. If no tablespace names are given, the install uses the default names, JAZZDATA and JAZZTMPSPACE.

com.ibm.team.repository.db.db2.automatic.setup=false
com.ibm.team.repository.db.vendor=DB2
com.ibm.team.repository.db.db2.temp.tablespace.name=<temp tablespace name>
com.ibm.team.repository.db.db2.data.tablespace.name=<data tablespace name>
com.ibm.team.repository.db.jdbc.location=//localhost:50000/JAZZ:user=<user name>;password={password};

Run repotools -createTables.
Tip: You can also assign a user without DBADM authority to serve as the Jazz database user. To do this, after the database tables have been created, grant this user read and write privileges to all Jazz database tables and use of the user temporary tablespace.