Veritas Storage Foundation 5.1 SP1 Advanced Features Administrator"s Guide (5900-1503, April 2011)

In the example, 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 accessible to 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
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
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.
Symbolic links are recommended because they provide easy file system
management and location transparency of database files. However, the drawback
Improving Sybase performance with Veritas Quick I/O
Accessing regular VxFS files as Quick I/O files
62