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 |
|---|---|---|---|---|---|
| -92L | Error | 2269 | WP002 | "'%1' is not a valid class file" | A file passed to the INSTALL JAVA statement was not a valid Java class file. Click here for a list of possible parameters and odbc states. |
| -93L | Error | 2273 | WW013 | "Class '%1' has no public field '%2'" | An expression referenced a field that either does not exist or is not public. Click here for a list of possible parameters and odbc states. |
| -94L | Error | 2274 | WW014 | "Invalid type for field reference" | An expression attempted to reference a field or a method of a non-Java value. Field references via . and >> are only valid when applied to Java objects. Click here for a list of possible parameters and odbc states. |
| -95L | Error | 2380 | 08W49 | "Parse error: %1" | An error occurred while parsing a connection string. Click here for a list of possible parameters and odbc states. |
| -96L | Error | 2028 | 08W23 | "Database server already running" | The database server was not able to start because a server with the same name was already running. Click here for a list of possible parameters and odbc states. |
| -97L | Error | 2031 | 08W22 | "Database page size too big: %1" | You attempted to start a database with a page size that exceeds the maximum page size of the running server. Either restart the server and include this database name on the command line, or restart the server with the required page size. Click here for a list of possible parameters and odbc states. |
| -98L | Error | 2034 | 08W21 | "Authentication violation" | You attempted to connect to a server that has been authenticated for exclusive use with a specific application. Click here for a list of possible parameters and odbc states. |
| -99L | Error | 2035 | 08W04 | "Connections to database have been disabled" | Connections to the network database server have been disabled. You will receive this error until connections have been enabled. Click here for a list of possible parameters and odbc states. |
| 100L | Warning | 2001 | 02000 | "Row not found" | You positioned a cursor beyond the beginning or past the end of the query. There is no row at that position. Click here for a list of possible parameters and odbc states. |
| -100L | Error | 2036 | 08W01 | "Database server not found" | The database server is not running, or is in the process of starting up or shutting down, or the interface library is unable to find it. Click here for a list of possible parameters and odbc states. |
| 101L | Warning | 2002 | 01004 | "Value truncated" | You may have fetched data into a host variable or SQLDA variable not large enough to receive the value. Click here for a list of possible parameters and odbc states. |
| -101L | Error | 2037 | 08003 | "Not connected to a database" | You are not connected to a database, or you executed the DISCONNECT statement and have not connected to a database again. Click here for a list of possible parameters and odbc states. |
| 102L | Warning | 2003 | 01W02 | "Using temporary table" | A temporary table has been created to satisfy the query. This warning can only occur on an OPEN statement. Click here for a list of possible parameters and odbc states. |
| -102L | Error | 2038 | 08W03 | "Database server connection limit exceeded" | You exceeded the number of computers allowed to connect to the server. If you are running the network database server, the limit is specified in your license agreement. The server may be running low on cache, and as a result it cannot accept any more database connections. The personal database server is restricted to 10 connections. Click here for a list of possible parameters and odbc states. |
| 103L | Warning | 2004 | 01W03 | "Invalid data conversion" | The database could not convert a value to the required type. The value being converted was either supplied to the database on an insert, update, or as a host bind variable, or was a value retrieved from the database into a host variable or SQLDA. Click here for a list of possible parameters and odbc states. |
| -103L | Error | 2039 | 28000 | "Invalid user ID or password" | You supplied an invalid user ID or an incorrect password. Click here for a list of possible parameters and odbc states. |
| 104L | Warning | 2005 | 01W04 | "Row has been updated since last time read" | You fetched a row from a SCROLL cursor. The row was previously fetched from the same cursor, and one or more columns in the row has been updated since the previous fetch. The column(s) updated may or may not be fetched by the cursor; this warning just indicates that the row from the table has been updated. If the cursor involves more than one table, a row from one or more of the tables has been updated. Click here for a list of possible parameters and odbc states. |
| -104L | Error | 2041 | 28W01 | "Invalid user ID or password on preprocessed module" | You specified an invalid user ID or password when a module was preprocessed. Click here for a list of possible parameters and odbc states. |
| 105L | Warning | 2006 | 01W05 | "Procedure has completed" | There are no more result sets available for this procedure. An OPEN or a RESUME statement may have caused the procedure to execute to completion. Click here for a list of possible parameters and odbc states. |
| -105L | Error | 2042 | 08001 | "Database cannot be started -- %1" | The specified database cannot be started. Either it does not exist, it is not a database, it is corrupt, or it is an older, unsupported format. Click here for a list of possible parameters and odbc states. |