Raw Partition Overview

Data files for tablespaces can be stored on a file system or on raw partitions. A raw partition is a portion of a physical disk that is accessed at the lowest possible level.

Input/output (I/O) to a raw partition offers approximately a 5% to 10% performance improvement over I/O to a partition with a file system on it.

• About Physical Disk
  A physical disk represents the entire disk and points to the following:
• About Logical Partition
  Logical partitions point to drives other than \Device\Harddiskx\Partition0.
• About Physical Disk and Logical Partition Considerations
  Consider the following when deciding which raw partition to use:
• About Compatibility Issues
  You can create logical partitions, but define physical disk convention names for them. For example:

About Physical Disk

A physical disk represents the entire disk and points to the following:

\Device\Harddiskx\Partition0

Symbolic link name \\.\PhysicalDrivex is automatically defined by Windows for every hard disk in the computer. For example, a computer with three hard disks have the following symbolic links:

\\.\PhysicalDrive0 
\\.\PhysicalDrive1 
\\.\PhysicalDrive2 

Internally, these names expand to the following:

\\.\PhysicalDrive0 =\Device\Harddisk0\Partition0 
\\.\PhysicalDrive1 =\Device\Harddisk1\Partition0 
\\.\PhysicalDrive2 =\Device\Harddisk2\Partition0 

Partition0 is special, because it represents the entire physical disk regardless of any partitioning scheme on that disk. Windows writes a signature on the first block of all disks it recognizes. To avoid overwriting that block, Oracle Database skips the first block of a physical raw partition that is used for an Oracle Database data file.

Note:

Although you can use physical disks, Oracle recommends that you use logical partitions.

About Logical Partition

Logical partitions point to drives other than \Device\Harddiskx\Partition0.

They are initially assigned names with drive letters (\\.\drive_letter:) and typically re-assigned symbolic link names (\\.\symbolic link name). For example, \\.\D: may be assigned a symbolic link name of \\.\ACCOUNTING_1. Regardless of whether a drive letter or symbolic link name is used, logical partitions are defined to represent a specific partition in a disk rather than the entire disk. Internally, these names can expand to:

\\.\D:= \Device\Harddisk2\Partition1 
\\.\ACCOUNTING_1= \Device\Harddisk3\Partition2 

Note:

Oracle Database does not skip the first block of a logical raw partition used for an Oracle Database data file.

About Physical Disk and Logical Partition Considerations

Consider the following when deciding which raw partition to use:

• Physical disks are automatically defined by Windows to represent the entire disk, and must never be defined by the user.

• Logical partitions must be defined by the user to represent a specific partition in a disk. These partitions must be logical partitions or drives contained in an extended partition. They must never be defined as Partition0.

• Using an entire disk (Partition0) for an Oracle Database data file and using a partition that occupies the entire disk for an Oracle Database data file are not the same thing. Even when a partition occupies the entire disk, there is still a small space on the disk that is not part of the partition.

• If you are using an entire disk for an Oracle Database data file (Partition0), then use the predefined physical raw names that Windows provides.

• If you are using a specific partition and it occupies the entire disk, then use a logical partition.

• If you are using a specific partition created with Windows disk-management tools, then define and use a symbolic link name rather than a logical partition number (even if it occupies the entire disk).

Note:

For both physical and logical raw conventions, use OCOPY to transfer the contents of a raw partition to a standard file system for backup purposes.

About Compatibility Issues

You can create logical partitions, but define physical disk convention names for them. For example:

\\.\PhysicalDriveACCOUNTING_1 = \Device\Harddisk2\Partition1 
\\.\PhysicalDriveACCOUNTING_2 = \Device\Harddisk3\Partition1 

Oracle Database then handles data files using the physical disk convention even though it really is a logical partition. This does not cause any data corruption or loss as long as you continue to use physical disk naming conventions. Oracle recommends that you convert to the logical partition at your earliest convenience.

You can also create logical names representing Partition0, but this is definitely not recommended. For example:

\\.\ACCOUNTING_1 = \Device\Harddisk1\Partition0 

This poses severe problems, because Disk Management typically writes a signature into the first block of every disk, and consequently may overwrite a portion of the data file header. It can also cause data loss. Never use Partition0 with the logical partition convention.

Physical and logical partition conventions are not compatible with one another because of the extra block that is skipped for physical raw conventions. This also means you cannot simply use OCOPY to copy from a physical disk to a logical partition, because contents of these partitions are incompatible.

To convert from a physical convention to a logical convention, you must:

1. Perform a full database export to a (local) file system.

2. Create logical partitions and define logical names for these partitions.

3. Recreate the database by using the new logical partitions.

4. Perform the full database import to the newly-created database.

If your database installation uses physical disk conventions with logical partitions, Oracle recommends converting to the logical partition conventions at your earliest convenience, using the preceding steps.

See Also:

Your operating system documentation for information about creating extended and logical partitions