Messages on this page are sorted by SQLCODE. Locate the appropriate code in the table below, and click the link for a full description of the message.
| SQL Code | Msg Type | Number | SQL State | Message | Possible Cause |
|---|---|---|---|---|---|
| 0L | Warning | 2000 | 00000 | No message | This code indicates that there was no error or warning. Click here for a list of possible parameters and odbc states. |
| -72L | Error | 2021 | 08W39 | "No database file specified" | The database server was started but there was no specified database file. The server is stopped. Click here for a list of possible parameters and odbc states. |
| -74L | Error | 2013 | 08W30 | "The selected database is currently inactive" | The selected database is in an inactive state. The database may be in the process of being started or shut down. Click here for a list of possible parameters and odbc states. |
| -75L | Error | 2014 | 08W29 | "Request to start/stop database denied" | You do not have permission to start or stop a database. The required permission is determined on the server command line. Click here for a list of possible parameters and odbc states. |
| -76L | Error | 2015 | 08W28 | "Request denied -- no active databases" | The server has denied your request as there are currently no running databases. Click here for a list of possible parameters and odbc states. |
| -77L | Error | 2016 | 08W27 | "Database name not unique" | The database cannot be started as its name conflicts with a previously started database. Click here for a list of possible parameters and odbc states. |
| -78L | Error | 2024 | 08W26 | "Dynamic memory exhausted" | A failure occurred when the database server was trying to allocate dynamic memory. Click here for a list of possible parameters and odbc states. |
| -79L | Error | 2017 | 08W25 | "Invalid local database option" | An invalid database option was found in the DBS (DatabaseSwitches) connection parameter. Click here for a list of possible parameters and odbc states. |
| -80L | Error | 2011 | 08W07 | "Unable to start database server" | It was not possible to start the database server. There may not be enough memory to run the database server. It may be that the executable cannot be found. Click here for a list of possible parameters and odbc states. |
| -81L | Error | 2012 | 08W08 | "Invalid database server command line" | It was not possible to start the database server because the command line was invalid. Click here for a list of possible parameters and odbc states. |
| -82L | Error | 2018 | 08W09 | "Unable to start specified database: %1" | The database server was unable to start the specified database. Check the server window messages area for more details. If the server was being autostarted, using the server -o option or manually starting the server may give more details. Click here for a list of possible parameters and odbc states. |
| -83L | Error | 2019 | 08W10 | "Specified database not found" | The database server was unable to find the specified database. The database server may be attempting to start a database file that cannot be opened or that cannot be found on the network. You may be attempting to connect to a database name that is not running. Click here for a list of possible parameters and odbc states. |
| -84L | Error | 2020 | 08W11 | "Specified database is invalid" | The database file you specified is invalid. The database server is stopped. Click here for a list of possible parameters and odbc states. |
| -85L | Error | 2022 | 08W12 | "Communication error" | There is a communication problem between the application and the server. Click here for a list of possible parameters and odbc states. |
| -86L | Error | 2025 | 08W13 | "Not enough memory to start" | The database server started, but stopped because there was not enough memory. Click here for a list of possible parameters and odbc states. |
| -87L | Error | 2026 | 08W14 | "Database name required to start server" | You did not supply a database name. A database name is required to start a database server. Click here for a list of possible parameters and odbc states. |
| -88L | Error | 2027 | 08W15 | "Client/server communications protocol version mismatch" | The connection failed because the protocol versions of the client and the server do not match. Ensure the client and server software are the same version. Click here for a list of possible parameters and odbc states. |
| -89L | Error | 2029 | 08W16 | "Database server not running in multi-user mode" | The database server was started for bulk loading (the -b option) and cannot be used as a network server. Stop the database server, and start again without -b. Click here for a list of possible parameters and odbc states. |
| -90L | Error | 2267 | WP000 | "Argument %1 of procedure '%2' cannot be NULL" | You passed a NULL value to a procedure expecting a scalar argument. For example, a Java procedure that has an 'int' argument cannot receive a NULL value. Click here for a list of possible parameters and odbc states. |
| -91L | Error | 2268 | WP001 | "Procedure '%1' terminated with unhandled exception '%2'" | A Java procedure terminated with an active exception, and this exception is reflected in SQL as an error status. Click here for a list of possible parameters and odbc states. |