Makes a partition available to Replication Server. A partition can be a disk partition or an operating system file.
create partition logical_name on 'physical_name' with size size [starting at vstart]
A name for the partition. The name must conform to the rules for identifiers. The name is also used in the drop partition and alter partition commands.
The full specification of the partition. This name must be enclosed in single quotation marks.
The size, in megabytes, of the partition. Maximum size possible is 1TB.
Specifies the number of megabytes (vstart) to offset from the beginning of the partition.
Adds a 20MB partition named P1 on the device named /dev/rsd0a:
create partition P1 on '/dev/rsd0a' with size 20
Adds a 20MB partition named P1 on the device named /dev/rsd0a. Since an offset of 1MB is specified, however, the total usable partition space available to Replication Server is 19MB:
create partition P1 on '/dev/rsd0a' with size 20 starting at 1
Replication Server uses partitions for stable message queues. The message queues hold data until it is sent to its destination.
Increasing the available disk space in partitions allows Replication Server to support more routes and database connections and to continue to queue messages during longer failures.
The maximum size for a partition is 1TB, which is approximately 1,000,000MB.
Disk partitions must not be mounted for use by the operating system and should not be used for any other purpose, such as for swap space or an Adaptive Server disk device.
Allocate the entire partition to Replication Server. If you allocate part of a partition for Replication Server, you cannot use the remainder for any other purpose. If you use the starting at vstart clause, the partition space available to Replication Server is what is left after you subtract the offset size from the total partition size.
The starting at vstart clause makes space available at the beginning of the partition for disk mirroring information.
You can use operating system files for partitions. However, the operating system buffers file I/O, so you may not be able to recover stable queues completely following a failure. Therefore, you should only use files for partitions in a test environment—unless your operating system does not support physical disk partitions.
If you use an operating system file, you must create it before executing create partition. On UNIX platforms, you can create the file with the touch command. The file can be zero bytes in length; the create partition command extends the file to the specified size.
The “sybase” user should own the disk partition or operating system file and must have read and write permissions on it. Users other than “sybase” should not have write or read permission on the partition.
create partition requires “sa” permission.
