Creating a Database Device

Create new database devices.

  1. In the left pane of the Administration Console, expand ASE Servers > Space Management > Devices.
  2. Click Database Devices.
  3. Click the drop-down arrow and select New.
  4. Select the server in which to create the database device.
  5. (Optional) For a cluster environment, click Create this as a private database device, then select the instance on which to create the private device.
    Private devices are used only by local user temporary databases. For the Cluster Edition, you can use block devices to manage the storage needs of temporary data in the cluster. These devices are added as private devices and can be used only by local user temporary databases. See Using Temporary Databases in the Clusters User Guide for more information.
  6. On the Device Name and Path screen, enter:
    • Device name – the logical device name used in the create database and alter database commands.
    • Device path – the physical device name, usually in the form of a full path for the new file, or in UNIX, a raw device partition. If you do not specify a device path, this field is filled with the device name along with a .dat file extension.
  7. On the Advanced Options screen, specify:
    • The device size, in megabytes
    • The device number – a unique number that identifies this device on the server. A default device number is provided.
    • Starting address – the virtual starting address, or the offset, for the server to begin using the database device. Defines the starting address for this device, and is a virtual offset in 2KB blocks. The default is 0. See Other optional parameters for disk init in the System Administration Guide for information about vstart.
    • Skip initialization of device – select to speed up the resizing of the device.
  8. Select a write option:
    • Data sync – ensures that writes to the database device occur on the physical storage medium. This allows the server to recover data from the device when a system failure occurs.
    • Direct IO – transfers the data directly to disk, bypassing the operating system's buffer cache.
    • Cached IO – turns off the data sync option, and any writes to the database device are buffered into the file system. During system failures, the server does not recover any data that has not been updated to the physical medium.
  9. (Optional) On the Mirroring screen, you can click Mirror the database device and specify the path for the duplicate device.
    Note: If the server is not configured to enable disk mirroring, the options for the Mirroring page are unavailable.