InfoScale™ 9.0 Storage and Availability Management for DB2 Databases - AIX, Linux
- Section I. Storage Foundation High Availability (SFHA) management solutions for DB2 databases
- Overview of Storage Foundation for Databases
- About Veritas File System
- Overview of Storage Foundation for Databases
- Section II. Deploying DB2 with InfoScale products
- Deployment options for DB2 in a Storage Foundation environment
- Deploying DB2 with Storage Foundation
- Deploying DB2 in an off-host configuration with Storage Foundation
- Deploying DB2 with High Availability
- Deployment options for DB2 in a Storage Foundation environment
- Section III. Configuring Storage Foundation for Database (SFDB) tools
- Configuring and managing the Storage Foundation for Databases repository database
- Configuring the Storage Foundation for Databases (SFDB) tools repository
- Configuring authentication for Storage Foundation for Databases (SFDB) tools
- Configuring and managing the Storage Foundation for Databases repository database
- Section IV. Improving DB2 database performance
- About database accelerators
- Improving database performance with Quick I/O
- About Quick I/O
- Improving DB2 database performance with Veritas Concurrent I/O
- Section V. Using point-in-time copies
- Understanding point-in-time copy methods
- Volume-level snapshots
- Storage Checkpoints
- Considerations for DB2 point-in-time copies
- Administering third-mirror break-off snapshots
- Administering Storage Checkpoints
- Database Storage Checkpoints for recovery
- Backing up and restoring with Netbackup in an SFHA environment
- Understanding point-in-time copy methods
- Section VI. Optimizing storage costs for DB2
- Section VII. Storage Foundation for Databases administrative reference
- Storage Foundation for Databases command reference
- Tuning for Storage Foundation for Databases
- Troubleshooting SFDB tools
Converting DB2 containers to Quick I/O files
Special commands available in the /opt/VRTS/bin directory are provided to assist you in converting an existing database to use Quick I/O. You can use the qio_getdbfiles command to extract a list of file names from the database system tables and the qio_convertdbfiles command to convert this list of database files to use Quick I/O.
Before converting database files to Ouick I/O files, the following conditions must be met:
The following options are available for the qio_getdbfiles command:
The following options are available for the qio_convertdbfiles command:
To extract a list of DB2 containers to convert
- With the database instance up and running, run the qio_getdbfiles command from a directory for which you have write permission:
$ cd /extract_directory
$ export DB2DATABASE=database_name
$ /opt/VRTS/bin/qio_getdbfiles
The qio_getdbfiles command extracts the list file names from the database system tables and stores the file names and their size in bytes in a file called mkqio.dat under the current directory.
Note:
Alternatively, you can manually create the mkqio.dat file containing the DB2 database container names that you want to convert to use Quick I/O. You can also manually edit the mkqio.dat file generated by qio_getdbfiles, and remove files that you do not want to convert to Quick I/O files.
Note:
To run the qio_getdbfiles command, you must have permission to access the database and permission to write to the /extract_directory.
The mkqio.dat list file should look similar to the following:
/data11r1/VRTS11r1/redo01.log 52428800 /data11r1/VRTS11r1/redo02.log 52428800 /data11r1/VRTS11r1/redo03.log 52428800 /data11r1/VRTS11r1/sysaux01.dbf 632553472 /data11r1/VRTS11r1/system01.dbf 754974720 /data11r1/VRTS11r1/undotbs01.dbf 47185920 /data11r1/VRTS11r1/users01.dbf 5242880 /data11r1/nqio1.dbf 104857600
To convert the DB2 database files to Quick I/O files
- Make the database inactive by either shutting down the instance or disabling user connections.
Warning:
Running the qio_convertdbfiles command while the database is up and running can cause severe problems with your database, including loss of data and corruption.
- Run the qio_convertdbfiles command from the directory containing the mkqio.dat file:
$ cd /extract_directory
$ export DB2DATABASE=database_name
$ /opt/VRTS/bin/qio_convertdbfiles
The list of files in the mkqio.dat file is displayed. For example:
file1 --> .file1::cdev:vxfs: file2 --> .file2::cdev:vxfs: file3 --> .file3::cdev:vxfs: file4 --> .file4::cdev:vxfs: file5 --> .file5::cdev:vxfs:
Run the qio_convertdbfiles command (with no options specified) to rename the file filename to .filename and creates a symbolic link to .filename with the Quick I/O extension. By default, the symbolic link uses a relative path name.
The qio_convertdbfiles script exits and prints an error message if any of the database files are not on a VxFS file system. If this happens, you must remove any non-VxFS files from the mkqio.dat file before running the qio_convertdbfiles command again.
- Make the database active again.
You can now access these database files using the Quick I/O interface.
To undo the previous run of qio_convertdbfiles and change Quick I/O files back to regular VxFS files
- If the database is active, make it inactive by either shutting down the instance or disabling user connections.
- Run the following command from the directory containing the mkqio.dat file:
$ cd /extract_directory
$ export DB2DATABASE=database_name
$ /opt/VRTS/bin/qio_convertdbfiles -u
The list of Quick I/O files in the mkqio.dat file is displayed. For example:
.file1::cdev:vxfs: --> file1 .file2::cdev:vxfs: --> file2 .file3::cdev:vxfs: --> file3 .file4::cdev:vxfs: --> file4 .file5::cdev:vxfs: --> file5
The qio_convertdbfiles command with the undo option (-u) specified renames the files from <.filename> to <filename> and undoes the symbolic link to .filename that was created along with the Quick I/O files.