SQL/MX 3.1 Messages Manual (H06.23+, J06.12+)

Data Definition Language (DDL) Messages (1000
through 1999)
HP NonStop SQL/MX Release 3.1 Messages Manual—663849-001
3-50
Cause. An OSS file system error occurred when you attempted to save a table DDL.
Possible reasons are:

The directory /usr/tandem/sqlmx/ddl did not exist or could not be created.

The system did not have write access to /usr/tandem/sqlmx/ddl.

Insufficient OSS file space was available.
Effect. The table is not dropped.
Recovery. Either correct the file system problem and drop the table or perform a
SHOWDDL on the existing table, capture the output, set.
SAVE_DROPPED_TABLE_DDL to “OFF,” and drop the table.
SQL 1233
Where catalog-name is the name of the SQL/MX catalog.
Cause. You attempted to create a schema in the system catalog.
Effect. The operation fails.
Recovery. Choose a different catalog name and reissue the CREATE statement.
SQL 1234
Where object-name is the name of the SQL/MP object.
Cause. An ALTER SQL/MP ALIAS command specified the same SQL/MP database
object as was previously mapped.
Effect. The operation succeeds. This is a warning message only.
Recovery. None.
SQL 1235
Cause. A CREATE or ALTER statement specified an invalid combination of EXTENT
sizes and MAXEXTENTS.
Effect. The operation fails.
1233 Creating schema in SQL/MX system catalog catalog-name is
prohibited.
1234 SQL/MP object object-name is the same as previous
mapping.
1235 An invalid combination of EXTENT sizes and MAXEXTENTS
was specified for table or index table-name.