Enable NO FILE SYSTEM CACHING for DB2 on System z 

When your operating system is Linux™ on System z , enable the NO FILE SYSTEM CACHING option for IBM DB2 databases to improve performance.


Before you begin

Important: Enable the NO FILE SYSTEM CACHING option on an unsupported device could cause your database to become inaccessible. Ensure that you meet the requirements for creating table spaces without file system caching.


About this task

When you create DB2 databases for IBM Connections under Linux on System z, the IBM Connections database wizard and the createDb.sql script create table spaces with the FILE SYSTEM CACHING option enabled. If you are storing DB2 table spaces on devices where Direct I/O (DIO) is enabled, such as Small Computer System Interface (SCSI) disks that use Fibre Channel Protocol (FCP), you can improve database performance by enabling the NO FILE SYSTEM CACHING option.

To enable the NO FILE SYSTEM CACHING option...


Procedure

  1. Log in to the DB2 database system with the user ID of the owner of the database instance. The user ID must have privileges to create a database, a table space, tables, and indexes.

      Note: If you created multiple database instances, specify the user ID for the first instance.

  2. Enable the NO FILE SYSTEM CACHING option for the Activities table space by entering the following commands:

      CONNECT TO OPNACT

      ALTER TABLESPACE OAREGTABSPACE NO FILE SYSTEM CACHING

      CONNECT RESET

  3. Enable the NO FILE SYSTEM CACHING option for the Communities table space by entering the following commands:

      CONNECT TO SNCOMM

      ALTER TABLESPACE SNCOMMREGTABSPACE NO FILE SYSTEM CACHING

      ALTER TABLESPACE DFREGTABSPACE NO FILE SYSTEM CACHING

      CONNECT RESET

  4. Enable the NO FILE SYSTEM CACHING option for the Forums table space by entering the following commands:

      CONNECT TO FORUM

      ALTER TABLESPACE DFREGTABSPACE NO FILE SYSTEM CACHING

      CONNECT RESET

  5. Enable the NO FILE SYSTEM CACHING option for the Profiles table space by entering the following commands:

      CONNECT TO PEOPLEDB

      ALTER TABLESPACE USERSPACE4K NO FILE SYSTEM CACHING

      ALTER TABLESPACE TEMPSPACE4K NO FILE SYSTEM CACHING

      ALTER TABLESPACE USERSPACE32K NO FILE SYSTEM CACHING

      ALTER TABLESPACE TEMPSPACE32K NO FILE SYSTEM CACHING

      CONNECT RESET

  6. Close the DB2 command line processor.


Parent topic

Create databases


Related tasks


Create multiple database instances
Registering the DB2 product license key
Create a dedicated DB2 user
Create databases with the database wizard
Create databases with SQL scripts

Related reference
http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.admin.doc/doc/t0023622.htm


   

 

});