ODBC Server Messages Manual

NonStop™ ODBC Server Messages
NonStop ODBC Server Messages Manual—429394.001
1-15
Messages Displayed on the Workstation
Recovery. If the table or view does not exist, correct the statement to reference an
existing table or view. If the table or view exists but for some reason is not registered in
the mapping tables, you can execute the REFRESH statement.
32063
Cause. The specified database name is invalid, does not exist, or is not customized. If
the database is customized and you get this error, the database entry could be missing
from the NonStop™ ODBC Server mapping tables.
Effect. The statement fails.
Recovery. If the database name is invalid, correct it. If the database does not exist,
create it using the CREATE DATABASE statement. If the database exists but is not
customized, execute the USERCAT INSTALL statement. If the database exists and is
customized but for some reason is missing from the mapping tables, execute the
REFRESH statement against the system catalog.
32064
Cause. An internal error occurred while processing a batch.
Effect. The batch fails.
Recovery. Retry the batch. If it fails again, contact your service provider.
32065
Cause. An internal error occurred while processing a statement.
Effect. The statement fails and the NonStop™ ODBC Server terminates.
Recovery. Contact your service provider.
32066
Cause. A CREATE VIEW statement specified an unsupported DISTINCT or ORDER
BY clause.
Effect. The statement fails.
Recovery. Remove the DISTINCT or ORDER BY clause from the CREATE VIEW
statement.
Invalid object name: database-name.
Process batch error.
Fatal error: Invalid statement type.
A clause-type clause is not allowed in a view.