Question : DB2 V9.5 database size problem!

Hi.

It is DB2 V9.5. Windows Server 2003. I issued the "create database mydb" statement in the DB2 command window and it was allocated 2Gb on disk!
I tested this case on 2 different systems (actually both are VMs) - result is the same it ia always allocating 2Gb for any new database.

Why empty database takes to much space?
Are there any options to decrease allocated space?

I need a lot of empty databases - about 60-100 databases on same computer. It is a build procedure environment - it creating database for every customer project specific build process, initializing tables, objects and so on, but all tables are empty because the only structure of database required during building process, it is not filled with data at all.

Another thing - we have a number of VM (virtual machines) used as test environments and it seems like we have to essentially increase disk sizes for new VM with DB2 V9.5... :-\ which is bad. So, are there any options to decrease disk allocation size for newly created db?...

It was perfectly works on DB2 V7.x and V8.x - empty databases took only 4-5 Mb on disk, but seems with DB2 V9.x it was essentially changed and it is the cause of problems. :-\

Regards,
Dmitry.
Code Snippet: 
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:

The code using to create new database
 
  DB2 CREATE DATABASE %Database% AUTOMATIC STORAGE NO USING CODESET UTF-8 TERRITORY US 
  DB2 CREATE BUFFERPOOL %BufferPool% ALL NODES SIZE 200 PAGESIZE 8192 
  DB2 CREATE REGULAR TABLESPACE %TableSpace% PAGESIZE 8192 MANAGED BY SYSTEM USING ('%db2container%') EXTENTSIZE 256 PREFETCHSIZE 32 BUFFERPOOL %BufferPool%
 
Is it looks ok?
Can you recomment anything other? Any hints on this?
 
Note: in particular 2Gb disk space allocated by 1st command here, by this:
  DB2 CREATE DATABASE %Database% AUTOMATIC STORAGE NO USING CODESET UTF-8 TERRITORY US 
That is why I'm wondering about such strange behaviour...
Open in New Window Select All

Answer : DB2 V9.5 database size problem!

Sorry, my apologizes to IBM guys. I was not right about this case with DB2.
I found the problem  there was additional db initialization script started which did not write any info into log file, so it looked like it hang on DB2 CREATE DATABASE %Database% while in real it did hang on DB2 update DB CFG for %Database% using LOGFILSIZ    16000.

So, 2GB is = DbPageSize * LOGFILSIZ * LOGPRIMARY = 4096 * 16000 * 32 =~ 2GB.

So, case closed.

PS.
Hm... seems not too many experts are here if got only 1 recommendation related to absolutely to different area. :-\ Maybe it not costs that money...
Random Solutions  
 
programming4us programming4us