Enabling Concurrent I/O for Sybase

Description

Enabling Concurrent I/O for Sybase

Because you do not need to extend name spaces and present the files as devices, you can enable Concurrent I/O on regular files.

Before enabling Concurrent I/O, review the following:

Prerequisites

  • To use the Concurrent I/O feature, the file system must be a VxFS file system.

  • Make sure the mount point on which you plan to mount the file system exists.

  • Make sure the DBA can access the mount point.

To enable Concurrent I/O on a file system using mount with the -o cio option

  • Mount the file system using the mount command as follows:

    On AIX:

      # /usr/sbin/mount -V vxfs -o cio special /mount_point

    On HP-UX and Solaris:

      # /usr/sbin/mount -F vxfs -o cio special /mount_point

    On Linux:

      # /usr/sbin/mount -t vxfs -o cio special /mount_point

    where:

    • special is a block special device.

    • /mount_point is the directory where the file system will be mounted.

For example for Sybase, to mount a file system named /datavolon a mount point named /sybasedata:

On AIX:

  # /usr/sbin/mount -V vxfs -o cio /dev/vx/dsk/sybasedg/datavol \
/sybasedata

On HP-UX and Solaris:

  # /usr/sbin/mount -F vxfs -o cio /dev/vx/dsk/sybasedg/datavol \
/sybasedata

On Linux:

  # /usr/sbin/mount -t vxfs -o cio /dev/vx/dsk/sybasedg/datavol \
/sybasedata

The following is an example of mounting a directory (where the new SMS containers are located) to use Concurrent I/O.

To mount an SMS container named /container1 on a mount point named /mysms:

# /usr/sbin/mount -Vt namefs -o cio /datavol/mysms/container1 /mysms

See Enabling and disabling Concurrent I/O

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)