InfoScale™ 9.0 Storage and Availability Management for DB2 Databases - AIX, Linux

Last Published:
Product(s): InfoScale & Storage Foundation (9.0)
Platform: AIX,Linux
  1. Section I. Storage Foundation High Availability (SFHA) management solutions for DB2 databases
    1. Overview of Storage Foundation for Databases
      1.  
        Introducing Storage Foundation High Availability (SFHA) Solutions for DB2
      2. About Veritas File System
        1.  
          About the Veritas File System intent log
        2.  
          About extents
        3.  
          About file system disk layouts
      3.  
        About Volume Manager
      4.  
        About Dynamic Multi-Pathing (DMP)
      5.  
        About Cluster Server
      6.  
        About Cluster Server agents
      7.  
        About InfoScale Operations Manager
      8.  
        Feature support for DB2 across Veritas InfoScale 9.0 products
      9.  
        Use cases for Veritas InfoScale products
  2. Section II. Deploying DB2 with InfoScale products
    1. Deployment options for DB2 in a Storage Foundation environment
      1.  
        DB2 deployment options in a Veritas InfoScale environment
      2.  
        DB2 on a single system with Storage Foundation
      3.  
        DB2 on a single system with off-host in a Storage Foundation environment
      4.  
        DB2 in a highly available cluster with Storage Foundation High Availability
      5.  
        DB2 in a parallel cluster with SF Cluster File System HA
      6.  
        Deploying DB2 and Storage Foundation in a virtualization environment
      7.  
        Deploying DB2 with Storage Foundation SmartMove and Thin Provisioning
    2. Deploying DB2 with Storage Foundation
      1.  
        Tasks for deploying DB2 databases
      2.  
        About selecting a volume layout for deploying DB2
      3. Setting up disk group for deploying DB2
        1.  
          Disk group configuration guidelines for deploying DB2
      4. Creating volumes for deploying DB2
        1.  
          Volume configuration guidelines for deploying DB2
      5. Creating VxFS file system for deploying DB2
        1.  
          File system creation guidelines for deploying DB2
      6.  
        Mounting the file system for deploying DB2
      7.  
        Installing DB2 and creating database
    3. Deploying DB2 in an off-host configuration with Storage Foundation
      1.  
        Requirements for an off-host database configuration
    4. Deploying DB2 with High Availability
      1.  
        Tasks for deploying DB2 in an HA configuration
      2.  
        Configuring VCS to make the database highly available
  3. Section III. Configuring Storage Foundation for Database (SFDB) tools
    1. Configuring and managing the Storage Foundation for Databases repository database
      1.  
        About the Storage Foundation for Databases (SFDB) repository
      2.  
        Requirements for Storage Foundation for Databases (SFDB) tools
      3.  
        Storage Foundation for Databases (SFDB) tools availability
      4. Configuring the Storage Foundation for Databases (SFDB) tools repository
        1.  
          Locations for the SFDB repository
      5.  
        Updating the Storage Foundation for Databases (SFDB) repository after adding a node
      6.  
        Updating the Storage Foundation for Databases (SFDB) repository after removing a node
      7.  
        Removing the Storage Foundation for Databases (SFDB) repository
    2. Configuring authentication for Storage Foundation for Databases (SFDB) tools
      1.  
        Configuring vxdbd for SFDB tools authentication
      2.  
        Adding nodes to a cluster that is using authentication for SFDB tools
      3.  
        Authorizing users to run SFDB commands
  4. Section IV. Improving DB2 database performance
    1. About database accelerators
      1.  
        About Arctera InfoScale™ product components database accelerators
    2. Improving database performance with Quick I/O
      1. About Quick I/O
        1.  
          How Quick I/O improves database performance
      2.  
        Tasks for setting up Quick I/O in a database environment
      3.  
        Preallocating space for Quick I/O files using the setext command
      4.  
        Accessing regular VxFS files as Quick I/O files
      5.  
        Converting DB2 containers to Quick I/O files
      6.  
        About sparse files
      7.  
        Displaying Quick I/O status and file attributes
      8.  
        Extending a Quick I/O file
      9.  
        Monitoring tablespace free space with DB2 and extending tablespace containers
      10.  
        Recreating Quick I/O files after restoring a database
      11.  
        Disabling Quick I/O
    3. Improving DB2 database performance with Veritas Concurrent I/O
      1. About Concurrent I/O
        1.  
          How Concurrent I/O works
      2. Tasks for enabling and disabling Concurrent I/O
        1.  
          Enabling Concurrent I/O for DB2
        2.  
          Disabling Concurrent I/O for DB2
  5. Section V. Using point-in-time copies
    1. Understanding point-in-time copy methods
      1.  
        About point-in-time copies
      2.  
        When to use point-in-time copies
      3.  
        About Storage Foundation point-in-time copy technologies
      4.  
        Point-in-time copy solutions supported by SFDB tools
      5.  
        About snapshot modes supported by Storage Foundation for Databases (SFDB) tools
      6. Volume-level snapshots
        1.  
          Persistent FastResync of volume snapshots
        2.  
          Data integrity in volume snapshots
        3.  
          Third-mirror break-off snapshots
      7. Storage Checkpoints
        1.  
          How Storage Checkpoints differ from snapshots
        2. How a Storage Checkpoint works
          1.  
            Copy-on-write
          2. Storage Checkpoint visibility
            1.  
              Storage Checkpoints and 64-bit inode numbers
        3.  
          About Database Rollbacks using Storage Checkpoints
        4.  
          Storage Checkpoints and Rollback process
        5.  
          Storage Checkpoint space management considerations
    2. Considerations for DB2 point-in-time copies
      1.  
        Considerations for DB2 database layouts
      2.  
        Supported DB2 configurations
    3. Administering third-mirror break-off snapshots
      1. Database FlashSnap for cloning
        1.  
          Database FlashSnap advantages
      2. Preparing hosts and storage for Database FlashSnap
        1. Setting up hosts
          1.  
            Database FlashSnap off-host configuration
        2.  
          Creating a snapshot mirror of a volume or volume set used by the database
      3.  
        Creating a clone of a database by using Database FlashSnap
      4.  
        Resynchronizing mirror volumes with primary volumes
      5.  
        Cloning a database on the secondary host
    4. Administering Storage Checkpoints
      1.  
        About Storage Checkpoints
      2. Database Storage Checkpoints for recovery
        1.  
          Advantages and limitations of Database Storage Checkpoints
      3.  
        Creating a Database Storage Checkpoint
      4.  
        Deleting a Database Storage Checkpoint
      5.  
        Mounting a Database Storage Checkpoint
      6.  
        Unmounting a Database Storage Checkpoint
      7.  
        Creating a database clone using a Database Storage Checkpoint
      8.  
        Restoring database from a Database Storage Checkpoint
      9.  
        Gathering data for offline-mode Database Storage Checkpoints
    5. Backing up and restoring with Netbackup in an SFHA environment
      1.  
        About Veritas NetBackup
      2.  
        About using Veritas NetBackup for backup and restore for DB2
      3. Using NetBackup in an SFHA Solutions product environment
        1.  
          Clustering a NetBackup Master Server
        2.  
          Backing up and recovering a VxVM volume using NetBackup
        3.  
          Recovering a VxVM volume using NetBackup
  6. Section VI. Optimizing storage costs for DB2
    1. Understanding storage tiering with SmartTier
      1. About SmartTier
        1.  
          About VxFS multi-volume file systems
        2.  
          About VxVM volume sets
        3.  
          About volume tags
        4.  
          SmartTier file management
        5.  
          SmartTier sub-file object management
      2.  
        SmartTier in a High Availability (HA) environment
    2. SmartTier use cases for DB2
      1.  
        SmartTier use cases for DB2
      2.  
        Relocating old archive logs to tier two storage using SmartTier
      3.  
        Relocating inactive tablespaces or segments to tier two storage
      4.  
        Relocating active indexes to premium storage
      5.  
        Relocating all indexes to premium storage
  7. Section VII. Storage Foundation for Databases administrative reference
    1. Storage Foundation for Databases command reference
      1.  
        vxsfadm command reference
      2. FlashSnap reference
        1.  
          FlashSnap configuration parameters
        2.  
          FlashSnap supported operations
      3. Database Storage Checkpoints reference
        1.  
          Database Storage Checkpoints configuration parameters
        2.  
          Database Storage Checkpoints supported operations
    2. Tuning for Storage Foundation for Databases
      1.  
        Additional documentation
      2. About tuning Veritas Volume Manager (VxVM)
        1.  
          About obtaining volume I/O statistics
      3. About tuning VxFS
        1. How monitoring free space works
          1.  
            About monitoring fragmentation
        2.  
          How tuning VxFS I/O parameters works
        3.  
          About tunable VxFS I/O parameters
        4.  
          About obtaining file I/O statistics using the Quick I/O interface
        5.  
          About I/O statistics data
        6.  
          About I/O statistics
      4. About tuning DB2 databases
        1.  
          DB2_USE_PAGE_CONTAINER_TAG
        2.  
          DB2_PARALLEL_IO
        3.  
          PREFETCHSIZE and EXTENTSIZE
        4.  
          INTRA_PARALLEL
        5.  
          NUM_IOCLEANERS
        6.  
          NUM_IOSERVERS
        7.  
          CHNGPGS_THRESH
        8.  
          Table scans
        9.  
          Asynchronous I/O
        10.  
          Buffer pools
        11.  
          Memory allocation
        12.  
          TEMPORARY tablespaces
        13.  
          DMS containers
        14.  
          Data, indexes, and logs
        15.  
          Database statistics
      5.  
        About tuning AIX Virtual Memory Manager
    3. Troubleshooting SFDB tools
      1. About troubleshooting Storage Foundation for Databases (SFDB) tools
        1.  
          Running scripts for engineering support analysis for SFDB tools
        2.  
          Storage Foundation for Databases (SFDB) tools log files
      2. About the vxdbd daemon
        1.  
          Starting and stopping vxdbd
        2.  
          Configuring listening port for the vxdbd daemon
        3.  
          Limiting vxdbd resource usage
        4.  
          Configuring encryption ciphers for vxdbd
      3.  
        Troubleshooting vxdbd
      4. Resources for troubleshooting SFDB tools
        1.  
          SFDB logs
        2.  
          SFDB error messages
        3.  
          SFDB repository and repository files
      5.  
        Upgrading Storage Foundation for Databases (SFDB) tools from 5.0.x to 9.0 (2184482)

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:

Prerequisites

  • Files you want to convert must be regular files on VxFS file systems or links that point to regular VxFS files

Usage notes

  • Converting existing database files to Quick I/O files may not be the best choice if the files are fragmented. Use the -f option to determine the fragmentation levels and choose one of two approaches: Either exclude files that are highly fragmented and do not have sufficient contiguous extents for Quick I/O use, or create new files with the qiomkfile command, rather than convert them with the qio_convertdbfiles command.

  • qio_getdbfiles skips any tablespaces that have a type of system managed space (SMS), as these tablespaces are based on a directory format and not suitable for conversion.

    The qio_getdbfiles command retrieves a list of database files and saves them in a file named mkqio.dat in the current directory.

  • Instead of using the qio_getdbfiles command, you can manually create the mkqio.dat file containing the DB2 instance filenames that you want to convert to Quick I/O files.

  • The qio_convertdbfiles command 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.

The following options are available for the qio_getdbfiles command:

-T

Lets you specify the type of database as db2. Specify this option only in environments where the type of database is ambiguous (for example, when multiple types of database environment variables, such as $ORACLE_SID, SYBASE, DSQUERY, and $DB2INSTANCE, are present on a server).

The following options are available for the qio_convertdbfiles command:

-a

Changes regular files to Quick I/O files using absolute path names. Use this option when symbolic links need to point to absolute path names (for example, at a site that uses SAP).

-h

Displays a help message.

-T

Enables you to specify the type of database as db2. Specify this option only in environments where the type of database is ambiguous (for example, when multiple types of database environment variables, such as $ORACLE_SID, SYBASE, DSQUERY, and $DB2INSTANCE are present on a server).

-u

Changes Quick I/O files back to regular files. Use this option to undo changes made by a previous run of the qio_convertdbfiles script.

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

  1. 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.

  2. 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.

  3. 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

  1. If the database is active, make it inactive by either shutting down the instance or disabling user connections.
  2. 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.