HP NonStop SQL/MX Messages Manual page 508

Table of Contents

Advertisement

Utility Messages (20000 through 23099)
Effect. The operation fails.
Recovery. Verify the catalog name and resubmit.
SQL 20118
20118 Schema schema name does not exist or cannot be
accessed.
Where schema name is the name of the schema associated with the table to be
purged.
Cause. You specified a schema name that does not exist or could not be accessed.
Effect. The operation fails.
Recovery. Verify the schema name and resubmit.
SQL 20119
20119 Table table name does not exist or cannot be accessed.
Where table name is the name of the table to be purged.
Cause. You specified a table name that does not exist or could not be accessed.
Effect. The operation fails.
Recovery. Verify the table name and resubmit.
SQL 20120
20120 Partition does not exist or cannot be accessed.
Cause. You specified a partition that does not exist or could not be accessed.
Effect. The operation fails.
Recovery. Verify the partition name and resubmit.
SQL 20121
20121 Partition is not the last in a table that is not key-
sequenced. PURGEDATA cannot be performed.
Cause. The table being purged has multiple partitions and is not key-sequenced. This
type of table is not supported.
Effect. The operation fails.
Recovery. None. This is an internal error. Contact your service provider.
HP NonStop SQL/MX Messages Manual—640324-001
18 -32

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Nonstop sql/mx 3.0

Table of Contents