| SQL2200N | The qualifier for the table or index name is too long or it was not specified as part of the table or index name. |
Explanation: The table name or index must be fully qualified. The format is authid.name where authid must be 1 to 30 characters, table name must be 1 to 128 characters and index name must be 1 to 18 characters (bytes in a MBCS environment).
The utility stops processing.
User Response: Resubmit the command with a fully qualified name including the correct qualifier.
| SQL2203N | The tablename parameter is not valid. Either the table name is too long, only an authorization ID was specified, the table name was not specified, or the address of the name is not valid. |
Explanation: The table name is required. It must be fully qualified and in the format authid.name where authid is 1 to 30 characters and name is 1 to 128 characters (bytes in MBCS environments). The table name must be located at a valid application address.
The utility stops processing.
User Response: Resubmit the command with the correct table name.
| SQL2204N | The iname parameter is not valid. The name of the index is too long, only an authorization ID was specified, or the address of the index is not valid. |
Explanation: If an index is specified, it must be fully qualified and in the format authid.name where authid is 1 to 30 characters and name is 1 to 18 characters (bytes in MBCS environments). The index must be located at a valid application address.
The utility stops processing.
User Response: Resubmit the command with a valid index name.
| SQL2205N | The specified index is not valid. Reason code: "<reason-code>". |
Explanation: The specified index parameter is not valid for the requested operation. Following is a list of reason codes:
Federated system users: this situation can also be detected by the data source.
The utility or operation stops processing.
User Response: Resubmit the command with a valid index or without an index.
| SQL2207N | The filepath specified by the datafile parameter is not valid. |
Explanation: The datafile parameter is not any of the values that indicate the default filepath. Also the datafile parameter is not a valid non-default value. One of the following may apply:
The utility stops processing.
User Response: Resubmit the command with a valid datafile parameter.
| SQL2208N | The table space specified by the table space parameter is not valid. |
Explanation: The table space parameter does not contain a valid value. One of the following conditions may exist:
The utility stops processing.
User Response: Resubmit the command with a valid table space parameter or do not use the table space name parameter. In the latter case, the Reorganize Table utility will use the table space(s) in which the table itself resides.
| SQL2211N | The specified table does not exist. |
Explanation: The table does not exist in the database. Either the table name or the authorization ID is incorrect.
The command cannot be processed.
User Response: Resubmit the command with a valid table name.
| SQL2212N | The specified table is a view. The Reorganize Table utility cannot be run against a view. |
Explanation: The Reorganize Table utility cannot be run against a view.
The utility stops processing.
User Response: Resubmit the command with a valid table name.
| SQL2213N | The specified table space is not a system temporary table space. |
Explanation: The Reorganize Table utility requires that any table space specified is a system temporary table space. The table space name provided is not a table space defined to hold system temporary tables.
The utility stops processing.
User Response: Resubmit the command with the name of a system temporary table space or do not use the table space name parameter. In the latter case, the Reorganize Table utility will use the table space(s) in which the table itself resides.
| SQL2214N | The user does not have the authority to run the Reorganize Table utility on table "<name>". |
Explanation: The user attempted to reorganize the specified table without the appropriate authorization (either SYSADM or DBADM authority or the CONTROL privilege on the table).
The utility stops processing.
User Response: Logon as a user with the appropriate authority or privilege and resubmit the reorganize table utility command.
| SQL2215N | SQL error "<sqlcode>" occurred while committing previous work for the database. |
Explanation: The user was already connected to the database specified in the Reorganize Table command. An error occurred while committing the previous work in progress for the database.
The utility stops processing with no attempt to roll back the work or break the database connection.
User Response: Look at the SQLCODE (message number) in the message for more information. Make changes and resubmit the command.
| SQL2216N | SQL error "<sqlcode>" occurred while reorganizing a database table. |
Explanation: An error occurred during the reorganization of a database table.
The utility stops processing.
User Response: Look at the SQLCODE (message number) in the message for more information. Make changes and resubmit the command.
| SQL2217N | The page size of the system temporary table space used by the REORG utility must match the page size of the table space(s) in which the table data resides (including the LONG and/or LOB column data). |
Explanation: If the system temporary table was explicitly specified to the REORG utility then the page size of the system temporary table space used by the REORG utility must match the page size of the table space or table spaces in which the table data, including LONG and/or LOB column data, resides. One of the following has violated this restriction:
If the system temporary table space was not specified to the REORG utility then the utility was looking internally for a system temporary table space. A system temporary table space that uses the same page size as the table data either did not exist in the database or was not available at the time.
User Response: If the table being reorganized resides in a table space with a page size which is different than that of the table space in which the LONG and/or LOB data of the table resides, then a system temporary table space cannot be provided to the REORG utility. Reissue the REORG request without specifying a system temporary table space.
If a system temporary table space that uses the same page size as the table data does not exist in the database, please create a system temporary table space using a page size that matches the page size of the table data.
If a system temporary table space that uses the same page size as the table data exists in the database but was not available at the time of your command, please reissue the command when the system temporary table space is available.