ODBC Server Messages Manual

NonStop™ ODBC Server Messages
NonStop ODBC Server Messages Manual429394.001
1-61
Messages Displayed on the Workstation
32575
Cause. Performing an INSERT received an SQLCODE of 0, indicating the object
already exists.
Effect. The command fails.
Recovery. The command can be retried with a corrected object name if it was not a
fatal NonStop™ SQL/MP error.
32576
Cause. A MODIFY or REMOVE did not find a named object.
Effect. The command fails.
Recovery. Retry the command with a different NOS user name, Guardian user name,
profile name, or database name.
32577
Cause. A logical name has already been assigned to the Guardian user id, NOS does
not allow more than one logical NOS user to map the same guardian id..
Effect. The command fails.
Recovery. Change the mapping for one of the user id’s to ensure that two logical
ODBC user names do not refer to the same guardian id.
32579
Cause. Either the qualified procedure name was not found or a NonStop™ SQL/MP
error occurred.
Effect. The command fails.
Recovery. The command can be retried with a corrected set of values.
Object object-type object-username already exists.
Object object-type object-username not found.
*** ERROR occurred. Guardian user id userid is already
mapped. Only one logical name can be mapped to one Guardian
id.
Column definition (column-1) column-2 for ADD PROCEDURE
invalid.