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
Accessing regular VxFS files as Quick I/O files
You can access regular VxFS files as Quick I/O files using the ::cdev:vxfs: name extension.
While symbolic links are recommended because they provide easy file system management and location transparency of database files, the drawback of using symbolic links is that you must manage two sets of files (for instance, during database backup and restore).
Usage notes |
|
To access an existing regular file as a Quick I/O file on a VxFS file system
- Access the VxFS file system mount point containing the regular files:
$ cd /mount_point
- Create the symbolic link:
$ mv filename .filename $ ln -s .filename::cdev:vxfs: filename
This example shows how to access the VxFS file dbfile as a Quick I/O file:
$ cd /db01 $ mv dbfile .dbfile $ ln -s .dbfile::cdev:vxfs: dbfile
This example shows how to confirm the symbolic link was created:
$ ls -lo .dbfile dbfile
For DB2:
-rw-r--r-- 1 db2inst1 104890368 Oct 2 13:42 .dbfile
lrwxrwxrwx 1 db2inst1 19 Oct 2 13:42 dbfile -> .dbfile::vxcdev:vxfs:
For Sybase:
$ ls -lo .dbfile dbfile
-rw-r--r-- 1 sybase 104890368 Oct 2 13:42 .dbfile
lrwxrwxrwx 1 sybase 19 Oct 2 13:42 dbfile -> .dbfile::cdev:vxfs: