SQL/MP Messages Manual

SQL Catalog Manager Messages (1000 to 1999)
HP NonStop SQL/MP Messages Manual427720-006
3-96
SQL 1630
Cause. For certain alter requests, a special “in-place” split operation is executed. After
an “in-place” split has completed, extra space exists in the file that needs to be
reclaimed. A FUP RELOAD operation reclaims this space and allows it to be reused. In
other cases, a failed Alter “merge” request may need to delete data in the target
partition. After the data is deleted, a FUP RELOAD is required to reclaim this space.
Effect. None.
Recovery. Run FUP RELOAD to reclaim space.
SQL 1631
Cause. The requested ALTER operation moves data into an already existing file
partition. Because the target already exists, EXTENT values and FORMAT cannot be
changed. Because we allow concurrent SQL DML activity on the file, the data copy
operation cannot support DSLACK, ISLACK, SLACK or FORMAT parameters.
Effect. None. Informational message.
Recovery. Do not specify EXTENT, DSLACK, ISLACK, SLACK, or FORMAT values
as part of the operation.
SQL 1632
Cause. The CATALOG clause was specified in the ALTER command but the name did
not match the actual catalog where the target partition exists.
Effect. The statement fails.
Recovery. Either specify the correct CATALOG name or do not use the CATALOG
clause. For existing target partitions, SQLCAT determines the correct catalog to use. It
is unnecessary to specify the CATALOG clause.
1630 The requested ALTER request has completed either
successfully or unsuccessfully, please run FUP RELOAD on
value to reclaim any freespace.
1631 The current version of ALTER TABLE or ALTER INDEX does
not support the specification of EXTENT, DSLACK, ISLACK,
SLACK or FORMAT attributes. These attribute specifications
have been ignored.
1632 Catalog name-1 specified in the CATALOG clause does not
match catalog name-2 where the target partition resides.