Chapter 65 ODBC/MP Server Messages

The messages in this chapter are generated by the NonStop™ ODBC Server process. The subsystem ID displayed by these messages includes ZNOS-TNM-SERVER-NAME as the subsystem name..




	NOTE: Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message that is not described in this chapter, see Chapter 15.

32002

Login incorrect: invalid user and/or password.

Cause The login included an invalid user name or password.

Effect The login fails.

Recovery Try logging in again with a valid user name and password.

32021

Internal error in LOGIN.

Cause An internal error occurred.

Effect The NonStop™ ODBC Server terminates.

Recovery Log on to the NonStop™ ODBC Server again.

32063

Cannot Trace: Invalid database name in log table table-name.

table-name

is the offending database name.

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.

32120

Cannot Trace: Log table file-name is NOT found.

file-name

is the file name for the trace log.

Cause The file name for the trace log found in ZNSPROF either does not exist as a SQL/MP table or does not have a proper mapping in the ZNUOBJ mapping table.

Effect Logging of trace output is turned off for the duration of the session.

Recovery Use NOSCOM or NOSUTIL to create the log file.

32144

Inbound buffer should be between 512 and 8192 bytes.

Cause You specified an invalid size for the inbound buffer.

Effect The statement fails.

Recovery Change the buffer size to a value between 512 and 8192 bytes.

32145

Outbound buffer size should be between 512 and 8192 bytes.

Cause You specified an invalid size for the outbound buffer.

Effect The statement fails.

Recovery Change the buffer size to a value between 512 and 8192 bytes.

32148

Invalid keyword: keyword.

keyword

is the offending keyword.

Cause You specified an invalid keyword during login.

Effect The login fails.

Recovery Check the login syntax and try logging on again.

32161

Cannot Trace: Invalid log table name log-table.

log-table

is the offending log table name.

Cause The log table name was invalid. For example, the subvolume specified might have contained invalid characters or more than eight characters.

Effect The statement fails.

Recovery Correct the log table name.

32216

variable exceeds the maximum limit of limit. Execution of this statement is stopped.

`variable`	is the name of the offending element.
`limit`	is the current maximum allowable limit.

Cause The indicated element exceeded the current maximum allowable limit.

Effect The statement does not finish. No rows are returned.

Recovery The limit is stored in the governing table. Consider specifying a different statement or changing the limit value.

32310

Error error-number opening SQLCS. Server terminating.

error-number

is the SQLCS error number being reported.

Cause A server could not open the SQLCS process.

Effect SQLCS terminates abnormally.

Recovery Check the system log to determine why SQLCS failed. error-number indicates the specific error that was encountered. error-number can have the following values:

006	Invalid pipe instance
007	Process not accepting CONTROL or SETMODE
014	The SCS process does not exist
020	Attempted to open an SCS process that has a long process ID
021	Illegal `count` specified
022	Application parameter or buffer address out of bounds
030	Unable to obtain main memory space for a link control block
031	Unable to obtain file system buffer space
032	Unable to obtain storage pool space (SYSPOOL) or extended pool space
033	I/O process is unable to obtain buffer space
034	Unable to obtain file system control block
109	Client has broken the connection
201	The SCS process has failed
233	Pipe not connected
240	Network line handler error, operation not started
241	Network error, operation not started
246	External cluster bypass error, operation terminated abnormally
248	Network line handler error, operation terminated abnormally
249	Network error, operation terminated abnormally
250	All paths to the system are down
251	Network protocol error
252	Required EXPAND class is not available
255	Net line handler flooded—too many interrupts

32311

Server no longer needed by SQLCS. Server terminating.

Cause SQLCS no longer needs a server. There are more than AVAILABLE_SERVERS servers waiting for client connection requests.

Effect The NonStop™ ODBC Server is terminated.

Recovery Informational message only; no corrective action is needed.

32312

error-number connecting to SQLCS.

error-number

is the SQLCS error number being reported.

Cause The server cannot indicate to SQLCS that it is available to service clients.

Effect SQLCS terminates abnormally.

Recovery Check the system log to determine why SQLCS failed and take action accordingly. For information about the value of error-number , see error 32310.

32313

error-number communicating with SQLCS.

error-number

is the SQLCS error number being reported.

Cause An error occurred within SQLCS software.

Effect Varies with the specific error.

Recovery Check the system log to determine if SQLCS is encountering errors. Take action accordingly. For information about the value of error-number , see error 32310.

32321

Invalid default location volume-name, using default database instead.

volume-name

is the offending volume name.

Cause The volume portion of the database identifier exceeds the maximum length.

Effect The statement fails.

Recovery Correct the volume name. A valid volume name consists of a dollar sign ($) followed by one to seven alphanumeric characters, the first of which must be a letter.

32328

User authentication error, error error-number, status status-number. Check USER_AUTHENTICATE_ procedure call for detail.

`error-number`	is the error number being reported.
`status-number`	is the status number being reported.

Cause A user authentication error occurred. See the description of the USER_AUTHENTICATE_ procedure call in the Guardian Procedure Call Reference Manual for details about interpreting this error.

Effect The request is denied.

Recovery Correct the error condition and issue the request again.

32332

Change password failed, the change password user user-name is not the same as login user login-user-name.

`user-name`	is the user ID that requested the change.
`login-user-name`	is the user ID for which the password change was requested.

Cause A change password operation failed because the user ID that requested the change was different from the user ID for which the password change was requested.

Effect The password is not changed.

Recovery Issue the request again from the user ID that is to be changed.

32333

Invalid Default Security profile-security, using Default Security of the logon user.

profile-security

is the offending security value.

Cause An invalid security value for the DEFAULT_SECURITY attribute was configured in the profile.

Effect The NonStop™ ODBC server ignores the invalid value and uses the default security of the logon user.

Recovery Correct the security value in the DEFAULT_SECURITY attribute in the profile.

32335

Account log table table-name is full.

table-name

is the name of the accounting log table.

Cause The accounting log table is full.

Effect Accounting is turned off.

Recovery Ask your system administrator to create a new accounting log table.

32337

Anonymous user logged in with password password

Cause User has loaded anonymous configuration default values and has logged in as anonymous user.

Effect Anonymous user is not allowed to perform DDL operations, passthru SQL, UTIL statements and change password statements.

Recovery Install administrative default configuration and log in as administrative user. This message is only informational. If you try any actions listed previosuly in the Effect subsection, error 32338 is returned.

32338

Anonymous user does not have sufficient privileges to execute the specified command.

Cause User has loaded anonymous configuration default values and has logged in as anonymous user.

Effect Anonymous user is not allowed to perform DDL operations, passthru SQL, UTIL statements and change password statements.

Recovery Install administrative default configuration and log in as administrative user.

32501

Startup message invalid, argument-list.

Cause An error was detected when parsing the startup message.

Effect The utility program is not started.

Recovery Use HELP command to determine correct syntax. Reissue the command with correct syntax.

32503

NOSUTIL must be SQL Compiled for invocation.

Cause The NonStop ODBC Server or the NOSUTIL process was not successfully installed.

Effect The utility program terminates abnormally.

Recovery SQL compile NOSUTIL.

32517

Unable to locate SQL System Catalog. FS Error : errnum.

Cause NonStop SQL is not installed on system, or an error occurred searching the system volumes for the file SQL.CATALOGS.

Effect The utility program aborts.

Recovery Install NonStop SQL on the system before installing the NonStop ODBC Server.