-876   object-type CANNOT BE CREATED OR ALTERED, REASON reason-code

The object in the SQL statement cannot be created or altered.

object-type

The type of object that could not be created or altered:

TYPE 1 INDEX

The object that the SQL statement attempted to create is a type 1 index.

INDEX

The object that the SQL statement attempted to create is an index.

TABLE

The object that the SQL statement attempted to create or alter is a table.

TABLESPACE

The object that the SQL statement attempted to alter is a table space.

reason-code

A value that indicates the reason for the failure.

TABLE DEFINED AS ASCII

The underlying table is defined as ASCII. Only type 2 indexes are supported for ASCII tables.

PIECESIZE IS NOT VALID

PIECESIZE is only valid for non-partitioned indexes.

COLUMN NAME IN EBCDIC EXCEEDS 18 BYTES, OR THE CONVERSION FROM UNICODE TO EBCDIC FAILED

The table that is being created or altered has an edit procedure that is defined with row attribute sensitivity, a field procedure, or a validation procedure. In these cases, the column name in EBCDIC cannot exceed 18 EBCDIC bytes in length, or the conversion of a column name from UNICODE to EBCDIC failed.

BASE TABLESPACE IS LOG YES, LOB TABLESPACE IS LOG NO

A spatial index cannot be created because the following table spaces have the indicated attributes:

• The table space that contains base table has the LOG YES (or LOGGED) attribute.
• The LOB table space that stores the LOB column has the LOG NO (or NOT LOGGED) attribute.

CONTAINS A SPATIAL COLUMN

The LOG YES attribute of a LOB table space cannot be altered to LOG NO if an index depends on the LOB column.

The LOG NO attribute of a table space cannot be altered to LOG YES if it contains a table with an index that depends on a LOB column of the table.

6

The value of the PREVENT_NEW_IXCTRL_PART subsystem parameter disallowed the creation of an index-controlled partitioned table.