43.2.1 Explanation of the specification format and options

(a) When the specification format of the -c option is invalid

The following table lists the message IDs that are displayed when the specification format of the -c option is invalid, and describes the possible errors. If any of these errors occurs, correct the error, and then re-execute the adbunarchivechunk command.

Legend:

∆: Space

(b) When an invalid chunk ID is specified in the -c option

The following table lists the message IDs that are displayed when an invalid chunk ID is specified in the -c option, and describes the possible errors. If an error occurs, correct the error, and then re-execute the adbunarchivechunk command.

Note:

For details about how to search for the IDs of chunks existing in the table to be processed, see -c in (2) Explanation of options.

(a) Specifying ranges of dates

Use dates to specify a range of chunks to be unarchived.

Format

-r {YYYY-MM-DD|YYYY/MM/DD}-{YYYY-MM-DD|YYYY/MM/DD}

Connect the minimum value (date specification) and maximum value (date specification) by using a hyphen (-). There must be no spaces between the minimum value and the hyphen (-), or between the maximum value and the hyphen (-).

Explanation

YYYY: Year (0001-9999)

MM: Month (01-12)

DD: Day (01 to the last day of the month specified in MM)

Specification example

Specification example 1: -r 2016/01/01-2016/12/31

Specification example 2: -r 2016-01-01-2016-12-31

Specify each date in either of the following formats: YYYY-MM-DD or YYYY/MM/DD (delimit YYYY, MM, and DD using forward slashes (/) or hyphens (-)).

In the case of specification example 1, 2016/01/01 and 2016/12/31 are treated as date specifications.

In the case of specification example 2, 2016-01-01 and 2016-12-31 are treated as date specifications.

The rules for specifying ranges of dates are as follows:

• If there are not enough digits in the values you want to specify in YYYY, MM, or DD, pad the left side of the value with zeros (0).

• The data types in the archive range column for which you can specify a date range are as follows:

  • DATE

  • TIMESTAMP

• Only dates can be specified in a date range specification. If the data type in the archive range column is TIMESTAMP, specified values are treated as if the time has been omitted. Therefore, the start time and end time in a specified value are corrected as shown in the following table. As a result, all chunks containing data in the specified date range are subject to unarchiving.

  Table 43‒4: Correction of the start time and end time

  No.	Number of digits in the fractional seconds defined in the TIMESTAMP-type column	Start time	End time
  1	0	0 hours 0 minutes 0 seconds	23 hours 59 minutes 59 seconds
  2	3	0 hours 0 minutes 0.000 seconds	23 hours 59 minutes 59.999 seconds
  3	6	0 hours 0 minutes 0.000000 seconds	23 hours 59 minutes 59.999999 seconds
  4	9	0 hours 0 minutes 0.000000000 seconds	23 hours 59 minutes 59.999999999 seconds
  5	12	0 hours 0 minutes 0.000000000000 seconds	23 hours 59 minutes 59.999999999999 seconds

• The following table lists the message IDs that are displayed when the specified date range is invalid, and describes possible errors. If any of these errors occurs, correct the error, and then re-execute the adbunarchivechunk command.

  Table 43‒5: Message IDs that are displayed when the specified date range is invalid, and possible errors

  No.	Message ID that is displayed	Possible error	Example of invalid specification	Example of corrected specification
  1	KFAA50225-E	Too many digits in the date Not enough digits in the date	-r 2015/7/1-2015/008/031	-r 2015/07/01-2015/08/31
  2		A date outside the range is specified.	-r 2015/01/01-2015/06/31	-r 2015/01/01-2015/06/30
  3	KFAA90002-E KFAA96840-I	The range specification format is invalid.	Specification example -r 2015/01/11∆-∆2015/7/31 Explanation Because there is a space between the date specification and the hyphen (-), the shell erroneously uses spaces to delimit the option arguments.	-r 2015/01/11-2015/07/31

  Legend:

  ∆: Space

(b) Specifying ranges of times

Use times to specify a range of chunks to be unarchived.

Format

-r hh:mm:ss[.[nn...n]]-hh:mm:ss[.[nn...n]]

Connect the minimum value (time specification) and maximum value (time specification) by using a hyphen (-). There must be no spaces between the minimum value and the hyphen (-), or between the maximum value and the hyphen (-).

Explanation

hh:: Hours (00-23)

mm: Minutes (00-59)

ss: Seconds (00-59)

.: Decimal point

nn...n: Fractional seconds (n is 0-9)

Specification example

Specification example 1: -r 00:00:00-12:59:59

Specification example 2: -r 00:00:00.000-12:59:59.999

The hh, mm, and ss values of each time are delimited using colons (:).

When specifying fractional seconds, connect the ss and nn...n values by using a decimal point (.).

In the case of specification example 1, 00:00:00 and 12:59:59 are treated as time specifications.

In the case of specification example 2, 00:00:00.000 and 12:59:59.999 are treated as time specifications.

The rules for specifying ranges of times are as follows:

• If there are not enough digits in the values you want to specify in hh, mm, or ss, pad the left side of the value with zeros (0).

• The data type in the archive range column for which you can specify a time range is as follows:

  • TIME

• If the fractional seconds have more digits than the fractional seconds defined in the TIME-type column, the excess digits are truncated.

• If fractional seconds are omitted, the start time and end time are corrected to reflect the number of digits in the fractional seconds defined in the TIME-type column. The following table lists details about how this correction is made.

  Table 43‒6: Correction of the start time and end time when fractional seconds are omitted

  No.	Number of digits in the fractional seconds defined in the TIME-type column	Start time	End time
  1	3	.000 seconds	.999 seconds
  2	6	.000000 seconds	.999999 seconds
  3	9	.000000000 seconds	.999999999 seconds
  4	12	.000000000000 seconds	.999999999999 seconds

• For details about comparing the minimum and maximum values for time specifications, see Comparing datetime data in Data types that can be compared in Data types that can be converted, assigned, and compared in the manual HADB SQL Reference.

• The following table lists the message IDs that are displayed when the specified time range is invalid, and describes possible errors. If any of these errors occurs, correct the error, and then re-execute the adbunarchivechunk command.

  Table 43‒7: Message IDs that are displayed when the specified time range is invalid, and possible errors

  No.	Message ID that is displayed	Possible error	Example of invalid specification	Example of corrected specification
  1	KFAA50225-E	Too many digits in the time Not enough digits in the time	-r 0:0:0-012:59:59	-r 00:00:00-12:59:59
  2		A time outside the range is specified.	-r 00:00:00-12:60:00	-r 00:00:00-12:59:59
  3	KFAA90002-E KFAA96840-I	The range specification format is invalid.	Specification example -r 00:00:00∆-∆12:59:59 Explanation Because there is a space between the time specification and the hyphen (-), the shell erroneously uses spaces to delimit the option arguments.	-r 00:00:00-12:59:59

  Legend:

  ∆: Space

(c) Specifying ranges of time stamps

Use time stamps to specify a range of chunks to be unarchived.

Format

-r '{YYYY-MM-DD|YYYY/MM/DD}∆hh:mm:ss[.[nn...n]]'
    -'{YYYY-MM-DD|YYYY/MM/DD}∆hh:mm:ss[.[nn...n]]'

Connect the minimum value (time stamp specification) and maximum value (time stamp specification) by using a hyphen (-). There must be no spaces between the minimum value and the hyphen (-), or between the maximum value and the hyphen (-).

Explanation

YYYY: Year (0001-9999)

MM: Month (01-12)

DD: Day (01 to the last day of the month specified in MM)

∆: Halfwidth space or tab

hh:: Hours (00-23)

mm: Minutes (00-59)

ss: Seconds (00-59)

.: Decimal point

nn...n: Fractional seconds (n is 0-9)

Specification example

Specification example 1: -r '2016/01/01 00:00:00'-'2016/12/31 12:59:59'

Specification example 2: -r '2016/01/01 00:00:00.000'-'2016/12/31 12:59:59.999'

Connect the date and time of each specified time stamp by using a halfwidth space, and enclose entire date or time values in single quotation marks ('). When specifying dates, use either of the following formats: YYYY-MM-DD or YYYY/MM/DD (delimit YYYY, MM, and DD using forward slashes (/) or hyphens (-)). When specifying times, delimit the hh, mm, and ss values by using colons (:). When specifying fractional seconds, connect the ss and nn...n values by using a decimal point (.).

In the case of specification example 1, 2016/01/01 00:00:00 and 2016/12/31 12:59:59 are treated as time stamp specifications.

In the case of specification example 2, 2016/01/01 00:00:00.000 and 2016/12/31 12:59:59.999 are treated as time stamp specifications.

The rules for specifying ranges of time stamps are as follows:

• If there are not enough digits in the values you want to specify in YYYY, MM, DD, hh, mm, or ss, pad the left side of the value with zeros (0).

• The data type in the archive range column for which you can specify a time stamp range is as follows:

  • TIMESTAMP

• If the fractional seconds have more digits than the fractional seconds defined in the TIMESTAMP-type column, the excess digits are truncated.

• If fractional seconds are omitted, the start time and end time are corrected to reflect the number of digits in the fractional seconds defined in the TIMESTAMP-type column. The following table lists details about how this correction is made.

  Table 43‒8: Correction of the start time and end time when fractional seconds are omitted

  No.	Number of digits in the fractional seconds defined in the TIMESTAMP-type column	Start time	End time
  1	3	.000 seconds	.999 seconds
  2	6	.000000 seconds	.999999 seconds
  3	9	.000000000 seconds	.999999999 seconds
  4	12	.000000000000 seconds	.999999999999 seconds

• For details about comparing the minimum and maximum values for time stamp specifications, see Comparing datetime data in Data types that can be compared in Data types that can be converted, assigned, and compared in the manual HADB SQL Reference.

• The following table lists the message IDs that are displayed when the specified time stamp range is invalid, and describes possible errors. If any of these errors occurs, correct the error, and then re-execute the adbunarchivechunk command.

  Table 43‒9: Message IDs that are displayed when the specified time stamp range is invalid, and possible errors

  No.	Message ID that is displayed	Possible error	Example of invalid specification	Example of corrected specification
  1	KFAA50225-E	Too many digits in the time stamp Not enough digits in the time stamp	-r '2015/7/1∆00:00:00'-'2015/008/031∆12:59:59'	-r '2015/07/01∆00:00:00'-'2015/08/31∆12:59:59'
  2		A time stamp outside the range is specified.	-r '2015/01/01∆00:00:00'-'2015/06/31∆12:60:00'	-r '2015/01/01∆00:00:00'-'2015/06/30∆12:59:59'
  3	KFAA90002-E KFAA96840-I	The range specification format is invalid.	Specification example -r '2016/04/01∆00:00:00'∆-∆'2016/06/30∆12:59:59' Explanation Because there is a space between the time stamp specification and the hyphen (-), the shell erroneously uses spaces to delimit the option arguments.	-r '2016/04/01∆00:00:00'-'2016/06/30∆12:59:59'
  4			Specification example -r 2016/04/01∆00:00:00-2016/06/30∆12:59:59 Explanation Because the time stamp specification is not enclosed in single quotation marks ('), the shell sees the space between the date and time values, and erroneously uses spaces to delimit the option arguments.

  Legend:

  ∆: Space

(d) Specifying ranges of fixed-length character strings

Use fixed-length character strings to specify a range of chunks to be unarchived.

Format

-r a...a-a...a

Connect the minimum value (fixed-length character string specification) and maximum value (fixed-length character string specification) by using a hyphen (-). There must be no spaces between the minimum value and the hyphen (-), or between the maximum value and the hyphen (-).

Explanation

a...a: String of one or more characters

Specification example

-r 20160101-20161231

20160101 and 20161231 are treated as fixed-length character string specifications.

The rules for specifying ranges of fixed-length character strings are as follows:

• Specify a fixed-length character string of one or more characters.

• Fixed-length character string specifications are case sensitive.

• The data type in the archive range column for which you can specify a fixed-length character string range is as follows:

  • CHARACTER

• If the fixed-length character string includes a character that has a special meaning in the OS or shell, such as a double quotation mark (") or vertical bar (|), specify the escape character (\) immediately before that character. Alternatively, enclose the entire fixed-length character string in single quotation marks (').

  Specification example

  Specification example 1: -r a\|c-def

  Specification example 2: -r 'a|c'-def

  In both examples, a|c and def are treated as fixed-length character string specifications.

• If a character string is enclosed in double quotation marks (") and then the entire string is enclosed in single quotation marks ('), both the character string and the double quotation marks (") are treated as a fixed-length character string.

  Specification example

  -r '"abc"'-def

  "abc" and def are treated as fixed-length character string specifications.

• If you specify a fixed-length character string that includes any hyphens (-), enclose the entire fixed-length character string in single quotation marks ('). This is to differentiate hyphens (-) in the specification from hyphens used to separate the minimum and maximum values.

  Specification example

  • When enclosing a specification in \' (backslashes and single quotation marks)

    -r \'a-c\'-def

  • When first enclosing a specification in single quotation marks ('), and then enclosing the entire string in double quotation marks (")

    -r "'a-c'"-def

  In both examples, a-c and def are treated as fixed-length character string specifications.

  In addition, even if a specified fixed-length character string does not include any hyphens (-), if you enclose the specification in single quotation marks ('), the enclosed value is treated as the fixed-length character string specification, with the single quotation marks (') omitted.

  Specification example

  • When enclosing a specification in \' (backslashes and single quotation marks)

    -r \'abc\'-def

    abc and def are treated as fixed-length character string specifications.

• If a specified fixed-length character string includes any single quotation marks ('), specify two single quotation marks (') in succession to express one single quotation mark (').

  Specification example

  • When specifying two \' (backslashes and single quotation marks)

    -r a\'\'c-def

  • When enclosing a specification that includes a single quotation mark ('), in double quotation marks (")

    -r "a''c"-def

  In both examples, a'c and def are treated as fixed-length character string specifications.

• For details about comparing the minimum and maximum values for fixed-length character string specifications, see Comparing character string data in Data types that can be compared in Data types that can be converted, assigned, and compared in the manual HADB SQL Reference.

• The following table lists the message IDs that are displayed when the specified fixed-length character string range is invalid, and describes possible errors. If any of these errors occurs, correct the error, and then re-execute the adbunarchivechunk command.

  Table 43‒10: Message IDs that are displayed when the specified fixed-length character string range is invalid, and possible errors

  No.	Message ID that is displayed	Possible error	Example of invalid specification	Example of corrected specification
  1	KFAA50225-E	The fixed-length character string specification includes multiple hyphens (-) that are used to separate the minimum and maximum values.	-r a-c-def -r 'a-c-def'	-r \'a-c\'-def
  2	KFAA90002-E KFAA96840-I	The range specification format is invalid.	Specification example -r abc∆-∆def Explanation Because there is a space between the fixed-length character string specification and the hyphen (-), the shell erroneously uses spaces to delimit the option arguments.	-r abc-def

  Legend:

  ∆: Space

(e) Specifying ranges of decimal numbers

Use decimal numbers to specify a range of chunks to be unarchived.

Format

-r [{+|-}]{a...a[.[b...b]]|.b...b}
    -[{+|-}]{a...a[.[b...b]]|.b...b}

Connect the minimum value (decimal specification) and maximum value (decimal specification) by using a hyphen (-). There must be no spaces between the minimum value and the hyphen (-), or between the maximum value and the hyphen (-).

Explanation

+, -: Signs (the "+" sign can be omitted)

a...a: Integer part (a is 0-9)

.: Decimal point

b...b: Fractional part (b is 0-9)

Examples of specifying DECIMAL(5,2)

Specification example 1: -r -100-100

Specification example 2: -r -100.00-+100.00

-100.00 and +100.00 are treated as decimal specifications.

The rules for specifying ranges of decimal numbers are as follows:

• Either the integer part or the fractional part must be specified. If there is no fractional part, the decimal point can be omitted.

• The data type in the archive range column for which you can specify a decimal range is as follows:

  • DECIMAL

• If the fractional parts have more digits than the fractional parts defined in the DECIMAL-type column, the excess digits are truncated.

• The following table lists the message IDs that are displayed when the specified decimal range is invalid, and describes possible errors. If any of these errors occurs, correct the error, and then re-execute the adbunarchivechunk command.

  Table 43‒11: Message IDs that are displayed when the specified decimal range is invalid, and possible errors

  No.	Message ID that is displayed	Possible error	Example of invalid specification	Example of corrected specification
  1	KFAA50225-E	A numerical value has been specified that cannot be used with the data type in the archive range column.	Specification example -r 0-123456789012345678901234567890123456789 Explanation A decimal specification contains 39 digits.	Specification example -r 0-12345678901234567890123456789012345678 Explanation Specify a decimal using 38 digits.
  2	KFAA90002-E KFAA96840-I	The range specification format is invalid.	Specification example -r 0∆-∆1 Explanation Because there is a space between the decimal specification and the hyphen (-), the shell erroneously uses spaces to delimit the option arguments.	-r 0-1

  Legend:

  ∆: Space

(f) Specifying ranges of integers

Use integers to specify a range of chunks to be unarchived.

Format

-r [{+|-}]a...a-[{+|-}]a...a

Connect the minimum value (integer specification) and maximum value (integer specification) by using a hyphen (-). There must be no spaces between the minimum value and the hyphen (-), or between the maximum value and the hyphen (-).

Explanation

+, -: Signs (the "+" sign can be omitted)

a...a: Numerical value (a is 0-9)

Specification example

Specification example 1: -r -100-100

Specification example 2: -r -100-+100

-100 and +100 are treated as integer specifications.

The rules for specifying ranges of integers are as follows:

• The data types in the archive range column for which you can specify an integer range are as follows:

  • INTEGER

  • SMALLINT

• The following table lists the message IDs that are displayed when the specified integer range is invalid, and describes possible errors. If any of these errors occurs, correct the error, and then re-execute the adbunarchivechunk command.

  Table 43‒12: Message IDs that are displayed when the specified integer range is invalid, and possible errors

  No.	Message ID that is displayed	Possible error	Example of invalid specification	Example of corrected specification
  1	KFAA50225-E	A numerical value has been specified that cannot be used with the data type in the archive range column.	In the case of INTEGER -r 0-9223372036854775808 In the case of SMALLINT -r 0-2147483648	In the case of INTEGER -r 0-9223372036854775807 In the case of SMALLINT -r 0-2147483647
  2	KFAA90002-E KFAA96840-I	The range specification format is invalid.	Specification example -r 0∆-∆1 Explanation Because there is a space between the integer specification and the hyphen (-), the shell erroneously uses spaces to delimit the option arguments.	-r 0-1

  Legend:

  ∆: Space

(g) Specifying ranges of floating point numbers

Use floating point numbers to specify a range of chunks to be unarchived.

Format

-r [{+|-}]{a...a[.[b...b]]|.b...b}[{E|e}[{+|-}]c...c]
    - [{+|-}]{a...a[.[b...b]]|.b...b}[{E|e}[{+|-}]c...c]

Connect the minimum value (floating point specification) and maximum value (floating point specification) by using a hyphen (-). There must be no spaces between the minimum value and the hyphen (-), or between the maximum value and the hyphen (-).

Explanation

+, -: Signs (the "+" sign can be omitted)

a...a: Integer part of the mantissa (a is 0-9)

.: Decimal point

b...b: Fractional part of the mantissa (b is 0-9)

E, e: Floating-point numeric literal

c...c: Exponent (c is 0-9)

Figure 43‒5: Example of specifying a floating point range by using the -r option

In the case of specification example 1, -100 and 100 are treated as floating point specifications.

In the case of specification example 2, -1.0E2 and +1.0E2 are treated as floating point specifications.

In the case of specification example 3, -100 and 1.0E+2 are treated as floating point specifications.

The rules for specifying ranges of floating point numbers are as follows:

• The data type in the archive range column for which you can specify a floating point range is as follows:

  • DOUBLE PRECISION

• The following table lists the message IDs that are displayed when the specified floating point range is invalid, and describes possible errors. If any of these errors occurs, correct the error, and then re-execute the adbunarchivechunk command.

  Table 43‒13: Message IDs that are displayed when the specified floating point range is invalid, and possible errors

  No.	Message ID that is displayed	Possible error	Example of invalid specification	Example of corrected specification
  1	KFAA50225-E	The number of specifiable characters is exceeded.	Specification example -r 0-123...(omitted)...789 Explanation A floating point specification contains 510 characters.	Specification example -r 0-123...(omitted)...78 Explanation Specify a floating point specification using 509 characters.
  2	KFAA90002-E KFAA96840-I	The range specification format is invalid.	Specification example -r 0∆-∆1 Explanation Because there is a space between the floating point specification and the hyphen (-), the shell erroneously uses spaces to delimit the option arguments.	-r 0-1

  Legend:

  ∆: Space