| -b blobspace |
Names the blobspace to be
created |
Restrictions: The blobspace name
must be unique and cannot exceed 128 characters. It must begin with a letter
or underscore and must contain only letters, numbers, underscores, or the $ character.
References: For
more information, see creating a blobspace, in the chapter on managing disk
space in the IBM Informix Administrator's Guide. The syntax must conform
to the Identifier segment. For more information, see the IBM Informix Guide to SQL: Syntax. |
| -c |
Creates a dbspace,
blobspace, sbspace, or extspace
You can create up to 2047 storage spaces
of any type. |
Additional Information: After you create a storage space, you must back up both this storage
space and the root dbspace. If you create a storage space with the same name
as a deleted storage space, perform another level-0 backup to ensure that
future restores do not confuse the new storage space with the old one.
References: For more information, see creating a dbspace,
blobspace, or extspace, in the chapter on managing disk space in the IBM Informix Administrator's Guide. |
| drive |
Specifies the Windows drive to allocate as unbuffered
disk space
The format can be either \\.\<drive>, where drive is the drive letter assigned to a disk partition, or
\\.\PhysicalDrive<number>, where PhysicalDrive is a constant
value and number is the physical drive number. |
References: For information on allocating
unbuffered disk space, see allocating unbuffered disk space on Windows
in the chapter on managing disk space in the IBM Informix Administrator's Guide.
Examples:
\\.\F:
\\.\PhysicalDrive2
References: For pathname
syntax, see your operating-system documentation. |
| -g pageunit |
Specifies the blobspace
blobpage size in terms of page_unit, the number
of disk pages per blobpage |
Restrictions: Unsigned integer. Value
must be greater than 0.
References: For more information,
see blobpage size considerations, in the chapter on I/O Activity in the IBM Informix Performance Guide. |
| -m pathname
offset |
Specifies an optional pathname and offset to the chunk
that mirrors the initial chunk of the new blobspace or dbspace
Also see
the entries for -p pathname and -o offset in
this table. |
References: For more information,
see creating a dbspace or a blobspace in the chapter on managing disk space
in the IBM Informix Administrator's Guide. |
| -o offset |
Indicates, in kilobytes, the offset into the disk partition
or into the device to reach the initial chunk of the new blobspace, dbspace,
or sbspace |
Restrictions: Unsigned integer. The starting offset must
be equal to or greater than 0. The starting offset plus the chunk size cannot
exceed the maximum chunk size.
The maximum offset is 2 or 4 gigabytes, depending on the platform.
References: For more information, see allocating
raw disk space, in the chapter on managing disk space in the IBM Informix Administrator's Guide. |
| -p pathname |
Indicates the disk partition or device of the initial chunk
of the blobspace or dbspace that you are creating |
Additional Information: The chunk must be an existing unbuffered device
or buffered file. When you specify a pathname, you can use either a full pathname
or a relative pathname. However, if you use a relative pathname, it must be
relative to the directory that was the current directory when you initialized
the database server.
UNIX example (unbuffered device):
/dev/rdsk/c0t3d0s4
UNIX example (buffered device):
/ix/ids9.2/db1chunk Windows example:c:\Ifmxdata\ol_icecream\mychunk1.dat
References: For pathname syntax, see your
operating-system documentation. |
| -s size |
Indicates, in kilobytes, the size of the initial chunk
of the new blobspace or dbspace |
Restrictions: Unsigned integer. The
size must be equal to or greater than 1000 kilobytes and a multiple of the
page size. The starting offset plus the chunk size cannot exceed the maximum
chunk size.
The maximum chunk size is 2 or 4 terabytes, depending on
the platform. |
