Hitachi

Hitachi Advanced Database Command Reference

6.2.1 Explanation of the specification format and options

Organization of this subsection

(1) Specification format

adbchgchunkstatus
   -u authorization-identifier
  [-p password]
  [-w chunk-ID-of-chunk-to-be-changed-to-wait-status[,chunk-ID-of-chunk-to-be-changed-to-wait-status]...]
  [-n chunk-ID-of-chunk-to-be-changed-to-normal-status[,chunk-ID-of-chunk-to-be-changed-to-normal-status]...]
   table-to-be-processed
Important

  • Make sure that you specify at least one of the -w and -n options. You can also specify both options.

  • You must specify the table to be processed as the last option that is specified.

To Page Top

(2) Explanation of options

• -u authorization-identifier

~<character string>((1 to 100 bytes))

Specifies the authorization identifier of the HADB user who executes the adbchgchunkstatus command. To execute the adbchgchunkstatus command, the user must have the following two privileges:

  • CONNECT privilege

  • CHANGE CHUNK STATUS privilege for the table to be processed

For this option, specify an authorization identifier in the range from 1 to 100 bytes. Note that the byte count (1 to 100 bytes) does not include the double quotation marks used to enclose the authorization identifier.

Important

If the character string used as the authorization identifier includes any lowercase letter or a backslash (\), make sure that you check the rules for specifying authorization identifiers. For the rules for specifying authorization identifiers, see 1.4.2 Rules for specifying authorization identifiers and passwords.

• -p password

~<character string>((1 to 255 bytes))

Specifies the password for the authorization identifier that is specified in the -u option.

Important

If the password includes a character that has a special meaning in the OS or shell, such as a double quotation mark (") or vertical bar (|), make sure that you check the rules for specifying passwords. For the rules for specifying passwords, see 1.4.2 Rules for specifying authorization identifiers and passwords.

If the adbchgchunkstatus command is executed with this option omitted, a message prompting the user to enter a password is displayed. In an environment in which a password cannot be entered from the standard input, such as when the command is executed in the background, make sure that you do not omit this option.

• -w chunk-ID-of-chunk-to-be-changed-to-wait-status[,chunk-ID-of-chunk-to-be-changed-to-wait-status]...

~<integer>((1 to 9,223,372,036,854,775,807))

Specifies the chunk IDs of the chunks whose status is to be changed to wait status. Separate multiple chunk IDs with the comma (,), or use the hyphen (-) to separate a range of chunk IDs.

  • Example 1: Placing chunks with chunk IDs 1, 3, and 5 in wait status:

    -w 1,3,5

  • Example 2: Placing chunks with chunk IDs 1 through 5 in wait status:

    -w 1-5

  • Example 3: Placing chunks with chunk IDs 1, 3, 5 through 10, and 15 in wait status:

    -w 1,3,5-10,15

If a specified chunk ID does not exist in the table to be processed or belongs to a chunk that is not in normal status, that chunk ID is ignored (only chunks whose status can be changed are processed). If there is no chunk whose status can be changed, the command results in an error.

• -n chunk-ID-of-chunk-to-be-changed-to-normal-status[,chunk-ID-of-chunk-to-be-changed-to-normal-status]...

~<integer>((1 to 9,223,372,036,854,775,807))

Specifies the chunk IDs of the chunks whose status is to be changed to normal status. Separate multiple chunk IDs with the comma (,) or use the hyphen (-) to separate a range of chunk IDs.

  • Example 1: Placing chunks with chunk IDs 1, 3, and 5 in normal status:

    -n 1,3,5

  • Example 2: Placing chunks with chunk IDs 1 through 5 in normal status:

    -n 1-5

  • Example 3: Placing chunks with chunk IDs 1, 3, 5 through 10, and 15 in normal status:

    -n 1,3,5-10,15

If a specified chunk ID does not exist in the table to be processed or belongs to a chunk that is not in wait status, that chunk ID is ignored (only chunks whose status can be changed are processed). If there is no chunk whose status can be changed, the command results in an error.

• table-to-be-processed

Specifies the name of the table for which chunk status is to be changed. Specify a multi-chunk table.

The following rules apply to specifying this information:

  • Specify in the format schema-name.table-identifier.

    If the user owns this table, the schema name can be omitted. If another HADB user owns this table, the schema name must be specified.

  • For details about the specification rules that apply when a schema name or table identifier includes any lowercase letter or backslash (\), see 1.4.3 Table name specification rules.

  • The user can specify any table for which the user has the CHANGE CHUNK STATUS privilege.

  • A single-chunk table cannot be specified.

  • A viewed table cannot be specified.

To Page Top

(3) Rules for specifying the -w and -n options

To Page Top

All Rights Reserved. Copyright (C) 2012, 2020, Hitachi, Ltd.