HP Neoview Messages, Руководство пользователя

Страница: 52 / 400

Recovery
To drop the constraint, you must remove the UNIQUE constraint or add an
additional NOT NULL constraint to the columns that contain UNIQUE constraints and only
one NOT NULL constraint for that column.
SQL 1276
1276 The PARTITION clause cannot be specified for an SQL/MP Table,
SQL/MP view or SQL/MX view. The partition partition-name was specified
for object table-name.
partition-name
is the partition name or number specified and
table-name
is the HP
Neoview database view name specified.
Cause
The PARTITION clause was used with a Neoview database view.
Effect The statement does not compile.
Recovery Remove the PARTITION clause and compile the statement again.
SQL 1277
1277 Unrecognized partitioning scheme for object object-name.
object-name
is the name of the SQL object (table or index).
Cause The HP Neoview database does not recognize the partitioning scheme stored in the
metadata for the named object.
Effect
The named object is considered corrupt and is inaccessible.
Recovery
Do not attempt recovery. HP support will perform recovery operations in response
to an automatically generated dial-out message about this condition. Consider running the
VERIFY operation on the named object to check for inconsistencies in the metadata with respect
to the partitioning scheme.
SQL 1278
1278 The command cannot be executed because operation is in progress
for all schemas in catalog catalog.
operation
is a schema-level operation, UPGRADE or DOWNGRADE, that uses the ALL
SCHEMAS IN CATALOG syntax.
catalog
is a catalog name that is affected by
operation.
Cause An attempt was made to execute a DDL or utility operation that affected
catalog
,
or a schema in that catalog.
Effect
The operation fails.
Recovery
Wait until
operation
is finished, then retry the failed DDL or utility operation.
SQL 1279
1279 A volatile DDL statement cannot be used on regular objects.
Cause Cannot create a volatile index on a regular nonvolatile object.
Effect None.
Recovery Either create a nonvolatile index or make sure that the base object is volatile.
SQL 1280
1280 A regular DDL statement cannot be used on volatile objects.
Cause
Cannot create a regular index on a volatile object.
Effect
None.
Recovery Either create a volatile index or make sure that the base object is not volatile.
52 Data Definition Language (DDL) Messages (1000 Through 1999)