IBM Tivoli Monitoring, Version 6.3

Increasing the size of your database (DB2 for Linux, UNIX, and Windows only)

DB2 for Linux, UNIX, and Windows Workgroup Edition has a default table size limit of 64 GB with a page size of 4 KB. To increase the capacity of your DB2 for Linux, UNIX, and Windows database, you can create a new table space, IBMDEFAULTGROUP, and choose a larger page size (up to 32 KB). This increases the capacity of the database up to 512 GB per table.

About this task

The following example creates the IBMDEFAULTGROUP table space with a page size of 16 K. This increases the table size capacity to 256 GB.
CREATE REGULAR TABLESPACE IBMDEFAULTGROUP IN DATABASE PARTITION GROUP IBMCATGROUP 
PAGESIZE 16384 MANAGED BY DATABASE
	 USING (FILE 'E:\DB2\NODE0000\SQL00001\IBMDEFAULTGROUP.001'1500000)
	 EXTENTSIZE 32
	 PREFETCHSIZE AUTOMATIC
	 BUFFERPOOL IBM16KBP
	 OVERHEAD 12.670000
	 TRANSFERRATE 0.180000 
	 DROPPED TABLE RECOVERY ON

If 512 GB of space per table is not enough for your environment, move to DB2 for Linux, UNIX, and Windows Enterprise Edition and using physical or logical partitioning.

The following steps outline the process for using database partitioning with DB2 for Linux, UNIX, and Windows Enterprise Edition:

Procedure

  1. Add a new database partition to the DB2 for Linux, UNIX, and Windows instance by running the db2ncrt command.
  2. Use the ALTER TABLE statement to add a partitioning key to the tables that you want to partition. For example:
    ALTER TABLE "CANDLE "."NT_System"     ADD PARTITIONING KEY ("Server_Name") 
         USING HASHING
  3. Use the ALTER DATABASE PARTITION GROUP statement to assign the new partition to the database partition group. You can do this either from the command-line or from the DB2® Control Center.
  4. Redistribute the data in the database partition group, using the Redistribute Data Wizard in the DB2 Control Center.

What to do next

For additional information about database partitioning, see the following DB2 for Linux, UNIX, and Windows sources:

For additional database performance and tuning information, see the IBM Tivoli Monitoring Administrator's Guide.



Feedback