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
- Introducing Storage Foundation High Availability (SFHA) Solutions for DB2
- About the File System component
- About the Volume Manager component
- About Dynamic Multi-Pathing (DMP)
- About Cluster Server
- About Cluster Server agents
- About InfoScale Operations Manager
- Feature support for DB2 across InfoScale products
- Use cases for InfoScale products
- Overview of Storage Foundation for Databases
- Section II. Deploying DB2 with InfoScale products
- Deployment options for DB2 in a Storage Foundation environment
- DB2 deployment options in an InfoScale environment
- DB2 on a single system with Storage Foundation
- DB2 on a single system with off-host in a Storage Foundation environment
- DB2 in a highly available cluster with Storage Foundation High Availability
- DB2 in a parallel cluster with SF Cluster File System HA
- Deploying DB2 and Storage Foundation in a virtualization environment
- Deploying DB2 with Storage Foundation SmartMove and Thin Provisioning
- 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
- About the Storage Foundation for Databases (SFDB) repository
- Requirements for Storage Foundation for Databases (SFDB) tools
- Storage Foundation for Databases (SFDB) tools availability
- Configuring the Storage Foundation for Databases (SFDB) tools repository
- Updating the Storage Foundation for Databases (SFDB) repository after adding a node
- Updating the Storage Foundation for Databases (SFDB) repository after removing a node
- Removing the Storage Foundation for Databases (SFDB) 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
- How Quick I/O improves database performance
- Tasks for setting up Quick I/O in a database environment
- Preallocating space for Quick I/O files using the setext command
- Accessing regular VxFS files as Quick I/O files
- Converting DB2 containers to Quick I/O files
- About sparse files
- Displaying Quick I/O status and file attributes
- Extending a Quick I/O file
- Monitoring tablespace free space with DB2 and extending tablespace containers
- Recreating Quick I/O files after restoring a database
- Disabling Quick I/O
- Improving DB2 database performance with VxFS Concurrent I/O
- Section V. Using point-in-time copies
- Understanding point-in-time copy methods
- About point-in-time copies
- When to use point-in-time copies
- About Storage Foundation point-in-time copy technologies
- Point-in-time copy solutions supported by SFDB tools
- About snapshot modes supported by Storage Foundation for Databases (SFDB) tools
- Volume-level snapshots
- Storage Checkpoints
- Considerations for DB2 point-in-time copies
- Administering third-mirror break-off snapshots
- Administering Storage Checkpoints
- About Storage Checkpoints
- Database Storage Checkpoints for recovery
- Creating a Database Storage Checkpoint
- Deleting a Database Storage Checkpoint
- Mounting a Database Storage Checkpoint
- Unmounting a Database Storage Checkpoint
- Creating a database clone using a Database Storage Checkpoint
- Restoring database from a Database Storage Checkpoint
- Gathering data for offline-mode Database Storage Checkpoints
- 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
Displaying Quick I/O status and file attributes
You can obtain and display information about Quick I/O status and file attributes using various options of the ls command:
-al | Lists all files on a file system, including Quick I/O files and their links. |
-1L | Shows if Quick I/O was successfully installed and enabled. |
-a1L | Shows how a Quick I/O file name is resolved to that of a raw device. |
To list all files on the current file system, including Quick I/O files and their links
- Use the ls -al command with the file names:
$ ls -al filename .filename
The following example shows how to use the -a option to display the absolute path name created using qiomkfile:
$ ls -al d* .d*
For DB2:
-rw-r--r-- 1 db2inst1 db2iadm1 104890368 Oct 2 13:42 .dbfile
lrwxrwxrwx 1 db2inst1 db2iadm1 19 Oct 2 13:42 dbfile -> .dbfile::cdev:vxfs:
For Sybase:
-rw-r--r-- 1 sybase sybase 104890368 Oct 2 13:42 .dbfile
lrwxrwxrwx 1 sybase sybase 19 Oct 2 13:42 dbfile -> .dbfile::cdev:vxfs:
To determine if Quick I/O is installed and enabled for DB2
- Use the ls command as follows:
$ ls -lL filename
The following example shows how to determine if Quick I/O is installed and enabled:
$ ls -lL dbfile
where the first character, c, indicates it is a raw character device file, and the major and minor device numbers are displayed in the size field. If you see a No such file or directory message, Quick I/O did not install properly or does not have a valid InfoScale license key.
To determine if a Sybase segment has been converted to Quick I/O
- Use the ls command as follows:
$ ls -lL filename
The following example shows how to determine if Quick I/O is installed and enabled:
$ ls -lL dbfile
crw-r--r-- 1 sybase dba 45, 1 Oct 2 13:42 dbfile
To show a Quick I/O file resolved to a raw device
- Use the ls command with the file names as follows:
$ ls -alL filename .filename
The following example shows how the Quick I/O file name dbfile is resolved to that of a raw device:
$ ls -alL d* .d*
For DB2:
crw-r--r-- 1 db2inst1 db2iadm1 45, 1 Oct 2 13:42 dbfile
-rw-r--r-- 1 db2inst1 db2iadm1 104890368 Oct 2 13:42 .dbfile
For Sybase:
crw-r--r-- 1 sybase sybase 45, 1 Oct 2 13:42 dbfile
-rw-r--r-- 1 sybase sybase 104890368 Oct 2 13:42 .dbfile