KFAA50207-E

The specification of the option file specified in the aa....aa is invalid.

aa....aa: Executed command name

• adbchgchunkstatus command

bb....bb: Option argument specifying the option file

• -m option

cc....cc:

Value specified for the option argument^#1

dd....dd:

Row number^{#3, #4}

ee....ee:

Operand name^#4

ff....ff:

Option argument of the operand^{#2, #3, #4}

gg....gg:

Value specified for the option argument of the operand^{#2, #3, #4, #5, #6}

hh....hh:

Cause of the error

#1:

Up to 512 bytes are displayed.

#2:

If the output of hh....hh is No. 15 in the table of corrective actions, * is displayed.

#3:

If the output of hh....hh is No. 16 in the table of corrective actions, * is displayed.

#4:

If the output of hh....hh is No. 17 in the table of corrective actions, * is displayed.

#5:

If a comma-separated list is specified, only the arguments where the error occurred will be displayed.

For example, the -w option displays the chunk ID of the chunk to be changed to the wait status where the error occurred, and the -n option displays the chunk ID of the chunk to be changed to the normal status where the error occurred.

#6:

If the output of hh....hh is No. 7 to 14 in the table of corrective actions, the table name is displayed in the format of "schema-name.table-identifier".

Enclosing characters are not displayed. In addition, lowercase alphabetic characters not surrounded by enclosing characters are displayed in uppercase alphabetic characters.

S:

Terminates processing.

Action:

Review the specification of the option file specified in the -m option of the adbchgchunkstatus command according to the following table. Then, re-execute the adbchgchunkstatus command.

No.	Information output to ee....ee	Information output to ff....ff	Information output to hh....hh	Error causes and corrective actions
1	adbchunkstatus	-w or -n	An invalid character was specified.	Characters that cannot be used or that are grammatically incorrect are specified. Example of incorrect specification: -w 1-2-3 Example of correct specification: -w 1-3
2			The specified value is outside the valid range.	A value that is outside the specification chunk ID range was specified. Specify a value from 1 to 9,223,372,036,854,775,807 for the chunk ID.
3			The value on the right side is equal to or less than the value on the left side.	When a range of chunk IDs is specified, the value-to-the-left-of-the-hyphen is equal to or greater than the value-to-the-right-of-the-hyphen. Correct the specification so that the value-to-the-left-of-the-hyphen is less than the value-to-the-right-of-the-hyphen. Example of incorrect specification: -w 5-2 Example of correct specification: -w 2-5
4			The specified value exceeds the maximum value that can be specified.	The maximum number of specified chunk IDs exceeds 29,999. Reduce the number of chunk IDs to 29,999 or fewer.
5		-t	The option is not specified.	No option is specified. Specify the table to be processed.
6			The invalid table name is specified.	The specification format of the specified table name is invalid. Specify the table name in the format "schema-name"."table-identifier". If the user owns the table, the schema name can be omitted.
7			The specified table does not exist.	The specified table does not exist. Specify an existing table.
8			The HADB user who executed the command does not have the CHANGE CHUNK STATUS privilege for the specified table.	The HADB user who executed the command does not have CHANGE CHUNK STATUS privilege for the specified table. Grant CHANGE CHUNK STATUS privilege to the HADB user executing the command. For details about how to grant CHANGE CHUNK STATUS privilege, see Granting access privileges to an HADB user in the HADB Setup and Operation Guide. However, if the schema of the specified table is different from the authorization identifier of the HADB user who executed the command, the specified table itself may not exist.
9			The specified table is not a base table.	The specified table is not a base table. Specify a base table.
10			The specified table is not a multi-chunk table.	The adbchgchunkstatus command could not be executed because the specified table is a single-chunk table.
11			The specified table is an archivable multi-chunk table.	The adbchgchunkstatus command could not be executed because the specified table is an archivable multi-chunk table.
12			The adbimport command was stopped for the specified table.	The table for which the execution of the adbimport command was interrupted is specified. Re-execute the adbimport command and then specify the table. For details, see Handling abnormal termination of the adbimport command in the HADB Command Reference.
13			The adbidxrebuild command was stopped for the specified table.	The table for which the execution of the adbidxrebuild command was interrupted is specified. Re-execute the adbidxrebuild command and then specify the table. For details, see Handling abnormal termination of the adbidxrebuild command in the HADB Command Reference.
14			The same table is already specified.	The same table is already specified. The same table cannot be specified more than once. Therefore, specifications for the same table should be specified with a single adbchunkstatus operand.
15		*	Neither the -w option nor the -n option is specified.	Neither the -w option nor the -n option is specified. Make sure to specify one or both.
16			The specified number of adbchunkstatus items exceeds 32.	The specified number of adbchunkstatus operands exceeds 32. Limit the number of specified adbchunkstatus operands to 32 or less.
17	*	*	Analysis of the file ended with an error.	Failed to analyze the option file. Check the error messages that were output before this message, and eliminate the cause of the error.