HP 3000 Manuals HP 3000 Manuals
Appendix A Error Messages
--------------------------------------------------------------
Error messages can come from many sources: the application, ALLBASE/SQL,
IMAGE/SQL, the Gupta or ODBC interfaces, or from the networking software.
Error messages are displayed by your application.
Errors from ALLBASE/SQL or IMAGE/SQL are followed by DBERR or DBWARN and
a number. Some error messages contain exclamation points (!) which are
replaced by more specific information (such as a number, file name, or
subsystem name) when the condition occurs in processing. These error
messages are documented in the ALLBASE/SQL Message Manual or in the
IMAGE/SQL Administration Guide.
Errors from the Gupta interface (numbers greater than 20000) are
documented in the ERROR.SQL file which was installed along with PC API.
The error messages below are returned by PC API to the application. Each
message is followed by a CAUSE, which gives information as to why the
warning or error occurred. This is followed by an ACTION, which gives
information on how to resolve the problem.
For all other errors, refer to the appropriate documentation or manuals.
1 MESSAGE End of Fetch.
CAUSE A FETCH has attempted to fetch beyond the end of a
result set.
ACTION None, informational only.
---------------------------------------------------------------
102 MESSAGE Select buffer is too small.
CAUSE One of the application's sqlssb function calls set
up a fetch buffer that is insufficient to hold the
data that was fetched.
ACTION Determine which select buffer is too small and
increase the size of that buffer. Checking the
fetch status code for each column selected can help
determine the column with the problem.
---------------------------------------------------------------
104 MESSAGE Attempt to fetch non-numeric data into a numeric
field.
CAUSE One of the application's sqlssb function calls set
up a fetch buffer that is defined as numeric but
the data that was fetched cannot be converted to a
numeric value.
ACTION Modify the program or data so that non-numeric data
is not attempted to be fetched into a numeric
format.
---------------------------------------------------------------
105 MESSAGE Attempt to fetch into a numeric field that is too
small.
CAUSE One of the application's sqlssb function calls set
up a fetch buffer that is defined as numeric but
the buffer provided is not large enough to hold the
numeric value.
ACTION Modify the program so the the select buffer is
large enough to accommodate the fetched value.
---------------------------------------------------------------
106 MESSAGE Application Programming Error: Data type not
supported.
CAUSE The application program is attempting to bind or
set up a select buffer and is specifying a program
that is not supported by SQLBase.
ACTION Verify that the program data type specified in the
sqlssb, sqlbnn, and sqlbnd calls are valid. Valid
program data types can be found in SQL.H file.
---------------------------------------------------------------
107 MESSAGE Application Programming Error: Long operation not
ended.
CAUSE The application program is attempting to perform a
non-long operation before ending the long operation
that is in progress.
ACTION Perform an end long operation (sqlelo) before
proceeding with any other operations.
---------------------------------------------------------------
113 MESSAGE Application Programming Error: Too many binds.
CAUSE The application program is attempting to perform a
bind operation and has exceeded the number of binds
necessary.
ACTION Correct the application program. The number of
bind function calls should equal the number of bind
variables.
---------------------------------------------------------------
114 MESSAGE Application Programming Error: Invalid bind name
or bind number.
CAUSE The application program is attempting to perform a
bind operation and it has not correctly specified
the bind name or the bind number.
ACTION Correct the application program. Verify that the
bind name pointer or bind number is correctly
specified.
---------------------------------------------------------------
115 MESSAGE Application Programming Error: Invalid program
data type.
CAUSE The application program is attempting to perform a
set select buffer (sqlssb) function call and has
specified an invalid program data type.
ACTION Correct the set select buffer (sqlssb) function
call in the application program. Verify that the
program data type is one of the program data types
defined in the file SQL.H.
---------------------------------------------------------------
116 MESSAGE Programming Error: Missing long bind before write
long.
CAUSE The application program is attempting to perform a
write long (sqlwlo) function call and no long data
has been bound.
ACTION Correct the the application program. Long data
must be bound to a write long operation before
attempting to write it with either a bind long data
by number (sqlbln) or bind long data by data name
(sqlbld) function call.
---------------------------------------------------------------
117 MESSAGE Invalid (null) parameter buffer pointer.
CAUSE The application program has performed a sqlset API
function call without providing a pointer to a
buffer, that is, the third parameter, a pointer, is
zero or null.
ACTION Correct the sqlset API function call by providing a
pointer to a buffer for the third parameter of the
sqlset function call.
---------------------------------------------------------------
119 MESSAGE Fetched data is not in a date-like or time-like
format.
CAUSE The application program is attempting to fetch data
into a buffer with a program data type of date
(SQLPDAT) and the data in the database is not
defined as a DATETIME, TIMESTAMP, DATE, or TIME
field.
ACTION Correct the set select buffer (sqlssb) function
call so the field does not ask for a program data
type of date.
---------------------------------------------------------------
126 MESSAGE Named cursor does not exist or is not open.
CAUSE The application program is attempting to execute an
SQL statement using the CURRENT OF cursorname or
ADJUSTING cursorname and the named cursor does not
exist or is not open.
ACTION Correct the application program. Check for
previous SQL return codes that may have closed or
disconnected the cursor. Correct the logic of the
application program to ensure that the specified
cursor is in fact open when this SQL statement is
executed.
---------------------------------------------------------------
128 MESSAGE Cursor name already exists or is already open.
CAUSE The application program is attempting to name a
cursor using the set cursor name (sqlscn) function
call and the specified cursor name already exists.
ACTION Correct the logic of the application program to
ensure that it does not attempt to name or open a
cursor that is already open.
---------------------------------------------------------------
131 MESSAGE Output message size is too small.
CAUSE The output message buffer is too small to hold the
current output message.
ACTION The output message buffer should never be too small
to hold the current output message as it should be
dynamically increased if necessary. Contact your
local certified technical support center for
assistance.
---------------------------------------------------------------
135 MESSAGE Invalid cursor number.
CAUSE The application program is attempting to perform a
function call and is using an invalid cursor
number. Or, the application program may be using
an old or mismatching version of a .DLL file.
ACTION Correct the application program. Verify that the
cursor is valid. To verify the cursor value, print
the value of cursor after the connect and then
before and after the function call that returned
this error. Alternately, verify that the .DLL
being used is the current version that matches the
version of the database software being used.
---------------------------------------------------------------
145 MESSAGE Out of memory at the client workstation.
CAUSE The application has run out of memory at the client
workstation.
ACTION Check available memory at the client workstation.
Attempt to make more memory available.
---------------------------------------------------------------
162 MESSAGE Invalid database name.
CAUSE The specified database name is invalid system
identifier.
ACTION A valid database identifier is a maximum of 8
characters which start with a letter followed by
letters or numbers. System identifiers include
usernames, database names, and database server
names.
---------------------------------------------------------------
184 MESSAGE Invalid server name.
CAUSE The specified database server name is not valid.
ACTION Correct the database server name. The maximum
length of a server name is 8 characters and must
begin with a letter and cannot contain special
characters.
---------------------------------------------------------------
195 MESSAGE Invalid SET parameter.
CAUSE Attempting to set a database parameter and the
specified parameter is invalid.
ACTION Verify and correct the specified parameter type.
---------------------------------------------------------------
196 MESSAGE Invalid GET parameter.
CAUSE Attempting to get a database parameter and the
specified parameter is invalid.
ACTION Verify and correct the specified parameter type.
---------------------------------------------------------------
201 MESSAGE No compiled command.
CAUSE Application program is attempting to perform a read
long (sqlrlo), write long (sqlwlo), long seek
(sqllsk), store command (sqlsto), or execute
(sqlexe) without first compiling an SQL statement.
ACTION Revise application to compile an SQL statement
prior to attempting the above operations.
---------------------------------------------------------------
202 MESSAGE Not a SELECT command.
CAUSE Trying to fetch or position within a result set
when the SQL statement is not a SELECT.
ACTION Revise application to compile a SQL SELECT
statement prior to attempting the above operations.
---------------------------------------------------------------
203 MESSAGE Command has not been executed.
CAUSE Attempting a fetch or position within a result set
without a successful SQL SELECT statement.
ACTION Revise application to compile an SQL SELECT
statement prior to attempting the above operations.
---------------------------------------------------------------
214 MESSAGE Not a long bind variable.
CAUSE Attempting a write long data column operation and
the SQL statement is not an UPDATE or INSERT
statement. Or, the column that is attempting to be
updated or inserted is not a LONG VARCHAR data
column.
ACTION Do not perform a write long data operation with an
SQL statement that is not an UPDATE or INSERT. If
the SQL statement is an UPDATE or INSERT then
verify that the column number used with the write
long data (sqlwlo) operation is associated with a
LONG VARCHAR data column in the SQL statement.
---------------------------------------------------------------
220 MESSAGE Long seek past end of long data.
CAUSE The application program is trying to position
within long data and the position specified is
beyond the end of the long data.
ACTION Modify the application program so that it does not
position beyond the end of the long data. Remember
that the position is relative to zero, i.e. the
first character is position zero. To determine the
entire length of the long data you can perform the
get long data size (sqlgls) function call.
---------------------------------------------------------------
227 MESSAGE Invalid isolation level.
CAUSE Trying to set the isolation level (sqlsil) and
specifying an invalid isolation level.
ACTION The valid isolation levels are defined in the file
SQL.H which include the following stings (or
defined constants):
"RR" (SQLILRR) - read repeatability
"CS" (SQLILCS) - cursor stability
"RO" (SQLILRO) - read only
"RL" (SQLILRL) - release lock
---------------------------------------------------------------
316 MESSAGE Column specified twice.
CAUSE Specified a column with a duplicate column name.
ACTION Do not use the column name that has already been
used.
---------------------------------------------------------------
323 MESSAGE Invalid number.
CAUSE Attempting to convert character data to numeric
data and the conversion fails.
ACTION Verify that numeric data is being provided for
conversion.
---------------------------------------------------------------
324 MESSAGE Invalid program bind variable.
CAUSE The application is attempting to use a bind
variable that was not bound with a sqlbnn or sqlbnd
function call.
ACTION Bind all bind variables with either a sqlbnn or
sqlbnd function call before attempting to execute
the statement (sqlexe).
---------------------------------------------------------------
331 MESSAGE Not enough non-null values.
CAUSE Attempting to execute an INSERT statement and there
exist columns defined as NOT NULL which have not
been provided values.
ACTION Modify the INSERT statement so that a value exists
for each column defined in the CREATE TABLE
statement as NOT NULL.
---------------------------------------------------------------
404 MESSAGE Invalid password.
CAUSE Attempting to connect to the database with a bad
password.
ACTION Use a valid database name, user name, and password.
---------------------------------------------------------------
405 MESSAGE Invalid user name.
CAUSE Trying to connect to the database with an invalid
user name.
ACTION Use a valid database name, user name, and password.
---------------------------------------------------------------
603 MESSAGE Invalid column number.
CAUSE A column has been specified by column number and
the column number specified cannot be translated to
an appropriate column name.
ACTION Specify a valid column number.
---------------------------------------------------------------
708 MESSAGE No updates with read only isolation.
CAUSE Attempting an INSERT, UPDATE, or DELETE while in
Read Only (RO) Locking Isolation Mode.
ACTION Change isolation mode setting to either Read
Repeatability (RR), Cursor Stability (CS), or
Release Lock (RL) locking isolation mode before
attempting to do an INSERT, UPDATE, or DELETE.
---------------------------------------------------------------
805 MESSAGE Insert/update of unique constrained columns with
duplicate data.
CAUSE The target table of an INSERT or UPDATE operation
is constrained (by a CREATE UNIQUE INDEX statement)
to have unique values in certain columns.
Completion of the requested INSERT or UPDATE would
result in duplicate values occurring in the row.
If a view is the object of the INSERT or UPDATE
statement, the table that defines the view is
constrained. The update might also be caused by a
DELETE operation of a parent row that cascades to a
dependent row with a delete rule of SET NULL.
ACTION Examine the definitions for any UNIQUE INDEX
indexes to determine the uniqueness constraints
imposed. For an UPDATE statement, verify that the
specified operation is consistent with the
uniqueness constraint. If this does not indicate
the error, examine the target table to determine
the cause of the problem. For an INSERT statement,
examine the target table to determine which values
violate the uniqueness constraint. If the INSERT
statement contains a subquery, match the contents
of the table addressed by the subquery and the
contents of the target table to determine the cause
of the problem. For a DELETE statement, examine
the index key columns in the table that defines the
index. These columns contain a foreign key, which
when set NULL on a cascade delete from the target
table, causes the duplicate values.
---------------------------------------------------------------
837 MESSAGE Invalid function.
CAUSE This error is only used internally by the SQLBase
system.
ACTION None.
---------------------------------------------------------------
906 MESSAGE Invalid table name.
CAUSE The table name is invalid.
ACTION Verify that the specified table name is valid.
---------------------------------------------------------------
907 MESSAGE Invalid column name.
CAUSE The column name is invalid.
ACTION Verify that the specified column names are valid.
---------------------------------------------------------------
910 MESSAGE Identifier too long.
CAUSE An identifier exceeds 18 characters.
ACTION Correct the identifier that exceeds 18 characters.
---------------------------------------------------------------
917 MESSAGE Invalid SQL statement.
CAUSE The SQL statement verb is invalid.
ACTION Verify that the first keyword is a valid SQL
statement verb.
---------------------------------------------------------------
920 MESSAGE Missing equal sign.
CAUSE An equal sign is missing in an UPDATE statement.
ACTION Correct UPDATE statement. The SET clause within an
UPDATE statement has the general form of SET
column-name = expression
---------------------------------------------------------------
922 MESSAGE Missing comma or parenthesis.
CAUSE A missing comma or parenthesis has been determined
in an INSERT statement.
ACTION Correct SQL statement.
---------------------------------------------------------------
1205 MESSAGE Bind Variable Name is too long.
CAUSE One of the bind variable names is greater than 18
characters.
ACTION Correct the bind variable name.
---------------------------------------------------------------
1703 MESSAGE Incorrect parameter length.
CAUSE The general programming interface has dispatched a
message and the parameter length is incorrect.
ACTION Check to be sure that the general programming
interface program is passing a valid message.
---------------------------------------------------------------
1801 MESSAGE System deadlock.
CAUSE The database system has determined a system
deadlock situation. A deadlock situation is an
occurrence such that two or more transactions are
in a simultaneous wait state, each one waiting for
one of the other to release a lock before it can
proceed. SQLBase detects deadlocks immediately,
that is, without waiting the duration of the
timeout period. If SQLBase detects a deadlock it
will break the deadlock by rolling back the
transaction that detected the deadlock and return
this error message to the detector. The other
transaction will continue not even knowing a
deadlock situation was determined.
ACTION Determine what transactions are becoming deadlocked
and attempt to make changes so that the deadlock
situation does not occur frequently. A COMMIT as
often as possible often helps to avoid deadlocks.
---------------------------------------------------------------
2207 MESSAGE Invalid day value.
CAUSE Specified day is not valid.
ACTION Correct the specified day.
---------------------------------------------------------------
2208 MESSAGE Invalid year value.
CAUSE Specified year is not valid.
ACTION Correct the specified year.
---------------------------------------------------------------
2209 MESSAGE Invalid month value.
CAUSE Specified month is not valid.
ACTION Correct the specified month.
---------------------------------------------------------------
2559 MESSAGE HP Allbase Server error; Double click on HP DB
Router icon.
CAUSE Backend specific error. A SQLBase equivalent error
code could not be mapped.
ACTION Call extended error processing to retrieve more
details.
---------------------------------------------------------------
2810 MESSAGE Session closed/terminated.
CAUSE This error is returned to the client computer when
the cursor is tied to a network session that no
longer exists. Once you get this error on a
cursor, subsequent tries will also yield the same
error. Other cursors sharing the same network
session will get this error also. If applications
are exiting without disconnecting all their
cursors, the database server can confuse a new
instance of an application with an old one. If the
new and old instance have the same MS Windows task
id, the database server might tell the new instance
to use a network session created by the old
instance.
ACTION Check if some other error occurred before receiving
this error. Other errors that may have gone
undetected may have caused this error. Also check
that all cursors are disconnected before
terminating each run of an application. This can
be checked by seeing if there are any session left
on the database server screen after running and
exiting each application. Check whether the
applications ever terminate in ways where sessions
are not disconnected.
---------------------------------------------------------------
2903 MESSAGE Cannot open network message file.
CAUSE Cannot open the playback file to replay the
messages.
ACTION Correctly identify the playback filename.
---------------------------------------------------------------
2907 MESSAGE Premature end of file.
CAUSE The playback program has determined that the netlog
message file has prematurely ended.
ACTION Determine why the netlog message file was
incomplete.
---------------------------------------------------------------
2910 MESSAGE Internal error.
CAUSE An unexpected internal error has been determined in
the playback program.
ACTION Contact your local certified technical support
center for assistance.
---------------------------------------------------------------
3701 MESSAGE No configuration file.
CAUSE The SQL.INI configuration file could not be found
after searching the current directory, the \SQLBASE
directory, the root directory, or the specified
operating system search PATH.
ACTION Check for the existence of the SQL.INI file in the
appropriate directory.
---------------------------------------------------------------
3703 MESSAGE Missing configuration file entry.
CAUSE Cannot find the configuration file entry [category]
in the SQL.INI configuration file.
ACTION Verify that the configuration file entry exists and
that the proper SQL.INI configuration files is
being used.
---------------------------------------------------------------
5018 MESSAGE Missing slash (e.g., user/password).
CAUSE Attempting a connect command and the forward slash
is missing or incorrect. A forward slash (/) is
expected between the user name and password.
ACTION Correct connect statement. The syntax for the
connect command is: "CONNECT databasename N
username/password" where N is the number assigned
to this connection for later reference
and username/password is optional. If
username/password is not specified then
SYSADM/SYSADM is assumed. If username/password is
specified then both are required with a forward
slash separating the two identifiers.
---------------------------------------------------------------
7005 MESSAGE Command timed-out.
CAUSE This error has the following meanings:
(1) For a CALL or (2) for ADAPTER STATUS, the
system time-out period has elapsed.
(3) For a SEND or for (4) RECEIVE, the time-out
period specified for the CALL or LISTEN has
elapsed.
(5) For a HANG UP, the time-out period has expired
for an outstanding SEND to complete.
ACTION (1) For a CALL, try again later.
(2) For an ADAPTER STATUS, make sure you are suing
a correct name.
(3)For a SEND, the session has been terminated
abnormally. Establish another session and reissue
a SEND.
(4)For a RECEIVE, reissue the command.
(5) For a HANG UP the session has been terminated
abnormally.
---------------------------------------------------------------
9291 MESSAGE Cannot listen on socket.
CAUSE This error is currently undocumented.
ACTION Contact your local certified technical support
center for assistance.
---------------------------------------------------------------
9293 MESSAGE Cannot load any communication DLLs, network may
not be installed.
CAUSE This error is currently undocumented.
ACTION None.
---------------------------------------------------------------
10402 MESSAGE Invalid cursor name.
CAUSE Attempting to name a cursor and the specified name
is missing or invalid.
ACTION Correct the command by properly specifying a valid
cursor name.
---------------------------------------------------------------
20003 MESSAGE Invalid logon !.
CAUSE The logon string in the SQL.INI file or direct
logon has incorrect syntax.
ACTION Make sure that the user and session name are
alphanumeric.
---------------------------------------------------------------
20012 MESSAGE Truncated dynamic parameter !.
CAUSE A column value has been truncated.
ACTION Make sure that the buffer is smaller than the
column definition.
---------------------------------------------------------------
20013 MESSAGE Error ! getting server error text.
CAUSE The error text could not be retrieved from the
server.
ACTION Check that the server error catalog has been
installed correctly. If so, contact your HP
Service Representative or Response Center.
---------------------------------------------------------------
20100 MESSAGE Memory error.
CAUSE An error was detected while allocating memory.
ACTION Retry the operation or try to free more memory.
---------------------------------------------------------------
20119 MESSAGE Connection list full: Too many connects.
CAUSE Exceeded maximum number of connections.
ACTION Disconnect one connection and retry.
---------------------------------------------------------------
20120 MESSAGE Cursor list full: Too many open cursors.
CAUSE Exceeded maximum number of cursors.
ACTION Close one of the cursors and retry.
---------------------------------------------------------------
20200 MESSAGE INTERNAL ERROR.
CAUSE Unknown.
ACTION Contact your HP Service Representative or Response
Center.
---------------------------------------------------------------
20307 MESSAGE Unsupported conversion. Need Roman8 or ANSI.
CAUSE An invalid conversion option was used in the
connection string.
ACTION Be sure to use the 'an' convertion option for the
ANSI character set.
---------------------------------------------------------------
20309 MESSAGE Unsupported network type.
CAUSE The connection string had an unrecognizable
datacomm type.
ACTION Check the connection string for correct syntax.
---------------------------------------------------------------
20310 MESSAGE Received packet is bigger than expected.
CAUSE The server sent more data than the client expected.
ACTION Contact your HP Service Representative or Response
Center.
---------------------------------------------------------------
20312 MESSAGE Logon error: !.
CAUSE Connection failed.
ACTION Look at the expanded error text for more
information.
---------------------------------------------------------------
20319 MESSAGE Received packet is smaller than expected.
CAUSE Client received less data from the Server than
expected.
ACTION Contact your HP Service Representative or Response
Center.
---------------------------------------------------------------
20334 MESSAGE Data communications error !.
CAUSE An error was detected during network activity.
ACTION Look at the expanded error text and refer to the
Programmer's Reference: ARPA Sockets for
MS-DOS/Windows.
---------------------------------------------------------------
20362 MESSAGE PC Sockets Error !2.
CAUSE For HP-UX, the server listener process (hpdaARPA)
has not been started.
ACTION Start the listener on the HP-UX server (as root,
hpdaARPA).
---------------------------------------------------------------
30000 MESSAGE HP Allbase Server error; Double click on HP DB
Router icon.
CAUSE Backend specific error. A SQLBase equivalent error
code could not be mapped.
ACTION Call extended error processing to retrieve more
details.
---------------------------------------------------------------
30064 MESSAGE Message Not Displayed.
CAUSE NetIPC Error. Remote protocol module aborted
connection.
ACTION Determine cause of the server failure. The server
job has started. Possibly a problem with the
DBEnvironment.
---------------------------------------------------------------
31241 MESSAGE The server node is down. (DBERR 31241)
CAUSE Unable to communicate with the server.
ACTION Reboot the system. If this does not solve the
problem record as much information as possible and
contact your HP Service Representative or Response
Center.
---------------------------------------------------------------