| |
|
|
|
4 Database Kit Messages and Codes
This chapter describes the Database Kit messages and codes that may be returned by the Database Kit: It discusses:
The messages and codes described in this section are Database Kit messages and codes. The database-independent layer returns these messages and codes to an application's Database Kit modules in a Database Kit connection descriptor. Each message description in this appendix contains the message text and associated integer code, an explanation of the message, and, when the message indicates an error, one or more actions to take.
Many of the Database Kit messages returned to an application are sent in response to SQL error codes and messages returned by the relevant database server to the database-independent layer. These SQL error codes and messages are also available to an application.
For more information on error handling, see Handling Errors on page 1-52.
The application is connected to a database. See connect_information for the connection specifications.
DB ERROR: A fatal database error has occurred in the server
An error has originated in the server or the network interface that makes further operations impossible. Typically, a fatal database error terminates the connection with the database.
See your database administrator.
DB ERROR: Cannot allocate memory for connection descriptor
Not enough memory is available to create the connection descriptor for a requested connection.
Free up system memory. For more information, see your system documentation or your system administrator.
DB ERROR: Functionality not present
The requested functionality is not yet available.
DB ERROR: Insufficient memory for request
Not enough memory is available to perform the requested operation.
Adjust the parameters of DBquery to make memory usage more reasonable. For example:
- Return fewer rows.
- If you want to use a large user buffer, keep the fetch buffer small. The size of the user buffer is set with the DBquery parameter userbuf_row_limit and the size of the fetch buffer is set with the DBquery parameter rows_per_fetch.
- Adjust the value of the DBquery parameter userbuf_realloc_interval to decrease the amount of memory allocated for the user buffer when more space is required.
The request issued by the user is invalid for the current state of the database. For example:
- The user issued a connect request but is already connected.
- The value of the DBquery parameter userbuf_row_limit is not an integral multiple of rows_per_fetch.
- The number of rows allocated for DBquery is too large.
Do not issue a connect request when already connected.
Adjust the values of the DBquery parameters.
The SQL statement issued by the user is incorrectly constructed.
Correct the construction of the SQL statement.
Do not use a semicolon at the end of a SQL statement.
The user does not have the correct privileges for the database and the objects being queried therein.
After disconnecting from the database, see your database administrator to ensure that you have the correct privileges, then reconnect to the database and reissue the SQL statement.
DB ERROR: Recoverable database error
An error of unknown type occurred during processing. The error could be either a transient database error or a user error. This error aborts the operation but does not disconnect the user.
Try the action that resulted in the error again. If the error recurs, disconnect and reconnect, and try the action once again.
The default mapping performed by the database-independent layer on numeric data during a query converted floating-point data into a fixed type, resulting in an overflow error.
Use DBquery's use_floating_type_only parameter to force a mapping to floating type (see Mapping Data to Supported Database Kit Datatypes on page 1-22).
|
| |
|
|
|
Copyright © 2001 Advanced Visual Systems
Inc.
All rights reserved.