Veritas InfoScale™ 7.4 Solutions Guide - Solaris

To create a DB2 container as a Quick I/O file using qiomkfile

1. Create a Quick I/O-capable file using the qiomkfile command:

   # /opt/VRTS/bin/qiomkfile  -s file_size /mount_point/filename

   For example, to show how to create a 100MB Quick I/O-capable file named dbfile on the VxFS file system /db01 using a relative path name:

   # /opt/VRTS/bin/qiomkfile -s 100m /db01/dbfile
   # ls -al
   -rw-r--r--			1 db2inst1		db2iadm1 104857600		Oct 2 13:42		.dbfile
   lrwxrwxrwx			1 db2inst1		db2iadm1				    19		Oct 2 13:42			dbfile -> \
   .dbfile::cdev:vxfs:

2. Create tablespace containers using this file with the following SQL statements:

   $ db2 connect to database
   $ db2 create tablespace tbsname managed by database using \
   ( DEVICE /mount_point/filename size )
   $ db2 terminate

   In the example from 1, qiomkfile creates a regular file named /db01/dbfile, which has the real space allocated. Then, qiomkfile creates a symbolic link named /db01/dbfile. This symbolic link is a relative link to the Quick I/O interface for /db01/.dbfile, that is, to the .dbfile::cdev:vxfs: file. The symbolic link allows .dbfile to be accessed by any database or application using its Quick I/O interface.

   We can then add the file to the DB2 database PROD:

   $ db2 connect to PROD
   $ db2 create tablespace NEWTBS managed by database using \
   ( DEVICE '/db01/dbfile' 100m )
   $ db2 terminate

To create a Sybase database file as a Quick I/O file using qiomkfile

1. Create a database file using the qiomkfile command:

   # /opt/VRTS/bin/qiomkfile -s file_size /mount_point/filename

   For example, to show how to create a 100MB database file named dbfile on the VxFS file system /db01 using a relative path name:

   # /opt/VRTS/bin/qiomkfile -s 100m /db01/dbfile
   $ ls -al
   -rw-r--r--			1 sybase			sybase 		104857600			Oct 2 13:42				.dbfile
   lrwxrwxrwx			1 sybase			sybase 			      19	  Oct 2 13:42				dbfile -> \
   .dbfile::cdev:vxfs:

2. Add a device to the Sybase dataserver device pool for the Quick I/O file using the disk init command:

   $ isql -Usa -Psa_password -Sdataserver_name
   > disk init
   > name="device_name",
   > physname="/mount_point/filename",
   > vdevno="device_number",
   > size=51200
   > go
   > alter database production on new_device=file_size 
   > go

   The size is in 2K units. The Enterprise Reference manual contains more information on the disk init command.

   In the example from 1, qiomkfile creates a regular file named /db01/.dbfile, which has the real space allocated. Then, qiomkfile creates a symbolic link named /db01/dbfile. The symbolic link is a relative link to the Quick I/O interface for /db01/.dbfile, that is, to the .dbfile::cdev:vxfs: file. The symbolic link allows .dbfile to be accessed by any database or application using its Quick I/O interface.

   The device size is a multiple of 2K pages. In the example, 51200 times 2K pages is 104857600 bytes. The qiomkfile command must use this size.

   An example to show how to add a 100MB Quick I/O file named dbfile to the list of devices used by database production, using the disk init command:

   $ isql -Usa -Psa_password -Sdataserver_name
   > disk init
   > name="new_device",
   > physname="/db01/dbfile",
   > vdevno="device_number",
   > size=51200
   > go
   > alter database production on new_device=100
   > go

   See the Sybase Adaptive Server Enterprise Reference Manual.

3. Use the file to create a new segment or add to an existing segment.

   To add a new segment:

   $ isql -Usa -Psa_password -Sdataserver_name
   > sp_addsegment new_segment, db_name, device_name
   > go

   To extend a segment:

   $ isql -Usa -Psa_password -Sdataserver_name
   > sp_extendsegment segment_name, db_name, device_name
   > go

   An example to show how to create a new segment, named segment2, for device dbfile on database production:

   $ isql -Usa_password -Sdataserver_name
   > sp_addsegment segment2, production, dbfile
   > go

   An example to show how to extend a segment, named segment1, for device dbfile on database production:

   $ isql -Usa_password -Sdataserver_name
   > sp_extendsegment segment1, production, dbfile
   > go

   See the Sybase Adaptive Server Enterprise Reference Manual.