Veritas Storage Foundation 5.1 SP1 Advanced Features Administrator"s Guide (5900-1503, April 2011)

To extend a Quick I/O file

If required, ensure the underlying storage device is large enough to contain

a larger VxFS file system (see the vxassist(1M) manual page for more

information), and resize the VxFS file system using fsadm command:

Extend the Quick I/O file using the qiomkfile command:

$ /opt/VRTS/bin/qiomkfile -e extend_amount /mount_point/filename

$ /opt/VRTS/bin/qiomkfile -r newsize /mount_point/filename

An example to show how to grow VxFS file system:

/db01 to 500MB and extend the tbs1_cont001 Quick I/O file by 20MB:

$ /opt/VRTS/bin/qiomkfile -e 20M /db01/tbs1_cont001

# /opt/VRTS/bin/fsadm -b 500M /db01

An example to show how to grow VxFS file system:

/db01 to 500MB and resize the tbs1_cont001 Quick I/O file to 300MB:

$ /opt/VRTS/bin/qiomkfile -r 300M /db01/tbs1_cont001

# /opt/VRTS/bin/fsadm -b 500M /db01

Monitoring tablespace free space with DB2 and

extending tablespace containers

DB2 does not automatically make use of extended DMS files. When tablespace

space needs to be extended, a number of DB2 commands must be run. Unlike raw

devices, a Database Administrator can easily extend Quick I/O files online. Using

this method, a Database Administrator can monitor the free space available in

the DB2 tablespaces and use the qiomkfile command to grow the Quick I/O files

online as needed (typically when the file is about 80 to 90% full). This method

does not require you to lock out unused disk space for Quick I/O files. The free

space on the file system is available for use by other applications.

Before extending tablespaces, make sure the following conditions have been met:

■ Log on as the DB2 instance owner.Prerequisites

Improving DB2 performance with Veritas Quick I/O

Monitoring tablespace free space with DB2 and extending tablespace containers