Home | Previous Page | Next Page   Utility Reference > onutil: Check, Define, and Modify Storage Objects >

CREATE DBSLICE

Use the onutil CREATE DBSLICE command to create a set of dbspaces that are managed as a single storage object across multiple coservers.

Syntax

Read syntax diagramSkip visual syntax diagram>>-CREATE--+------+--DBSLICE--dbslice_name--FROM---------------->
           '-TEMP-'

   .-,---------------------.
   V                       |
>----| Dbslice Component |-+-----------------------------------><

Read syntax diagramSkip visual syntax diagramDbslice Component:

|--COGROUP--cogroup_name--+--------------------+---------------->
                          '-THRESHOLD--percent-'

>--+----------------------+--CHUNK------------------------------>
   '-FRAGMENTS--fragments-'

                           (1)
>--| Pathname Definition |-------| Size Component |------------->

>--+--------------------------------------+---------------------|
   |                                 (2)  |
   '-MIRROR--| Pathname Definition |------'

Notes:
  1. See Pathname Definition.
  2. See Pathname Definition.
Read syntax diagramSkip visual syntax diagramSize Component:

|--SIZE--size--+--------+---------------------------------------|
               +-KBYTES-+
               +-MBYTES-+
               '-GBYTES-'

Element Purpose Restrictions Syntax
cogroup_name The name of a cogroup or coserver in the database server The cogroup name must exist when you execute the command. Name must be unique within a database server. See Identifiers in onutil Commands.
dbslice_name The name of the dbslice to create Name must be unique within a database server. See Identifiers in onutil Commands.
fragments The approximate number of fragments each new dbspace will contain Value is between 3 and 65500 Decimal or hexidecimal integer.
percent The percentage of the total space in the dbspace which, when used, triggers an alarm. Value is between 1 and 100 Decimal or hexidecimal integer.
size The size of the initial chunk of each new dbspace Value must be greater than 0. Size must not exceed 4 gigabytes. Can specify units of kilobytes, megabytes, or gigabytes. Unsigned integer; default unit is kilobytes.

Pathname Definition

Read syntax diagramSkip visual syntax diagramPathname Definition:

|--+-| Pathname Format |-+--+----------------+------------------|
   '-"--pathname--"------'  '-OFFSET--offset-'

Read syntax diagramSkip visual syntax diagramPathname Format:

              .-----------------------------------.
              V                                   |
|--"--prefix----+-------------------------------+-+--"----------|
                +-pathname_fragment-------------+
                +-%c----------------------------+
                +-%n----------------------------+
                +-%o----------------------------+
                |                          (1)  |
                +-%f--(--first--"--last--)------+
                '-,-----------------------------'

Notes:
  1. Each item can occur only once. However, multiple items may occur in a single invocation of the command.
Element Purpose Restrictions Syntax
first The starting value of the integer to substitute for each path

When first is in the pathname, its value can be any integer that makes each generated pathname unique.

The value of first must be equal to or less than the value of last. Unsigned integer
last The ending value of the integer to substitute in each path

When last is in the pathname, its value can be any integer that makes each generated pathname unique.

The value of last must be equal to or larger than first. Unsigned integer
offset The offset, in kilobytes, into the file or raw device to reach the chunk of each dbspace Value must be greater than or equal to 0. See specifying an offset in the chapter on managing disk space in the IBM Informix: Administrator's Guide. Unsigned integer
pathname The file or raw device of the first chunk in the dbspace on each node The chunk must be a file or raw device. Use a full pathname.

The pathname can optionally contains formatting characters.

Pathname must conform to the rules specific to your operating system. See Pathname Format.
prefix The portion of the directory name that precedes the formatting character The generated directory names must correspond to directories that exist on the applicable coservers. The directory name must conform to the rules specific to your operating system.
pathname_
fragment
The portion of the generated pathname that follows the formatting characters The generated pathnames must correspond to files that exist on the applicable coservers. You can intersperse the formatting characters in between parts of the pathname. Pathname must conform to the rules specific to your operating system. See Pathname Format.
%c A formatting character that is replaced with the number of the coserver on which a dbspace is to be created

The number is the value that you specified in the COSERVER configuration parameter for this coserver.

If the number is less than 10, the number does not have a leading zero. See Generating Pathnames with Coserver Numbers.
%n A formatting character that is replaced with the host name of the node for the coserver on which a dbspace is to be created The host name is the value that you specified in the NODE configuration parameter for this coserver. See Generating Pathnames with Node Names.
%o A formatting character that is replaced with the ordinal number of a dbspace within a dbslice The ordinal numbering starts at 1. See Generating Pathnames with Dbspace Ordinal Numbers.
%r(first..last) Formatting characters that are replaced by successive integer values in the range that first and last specify You can specify the %r(first..last) formatting characters only once in a pathname format. See Generating Pathnames for Multiple Dbspaces per Coserver.

Usage

Use the onutil CREATE DBSLICE command to create groups of dbspaces that you manage as a single logical storage unit. The database server must be in online or quiescent mode when you create a dbslice.

Home | [ Top of Page | Previous Page | Next Page | Contents | Index ]