D (Database) Errors
PLBWIN Only
The following are DATABASE errors that are trapped using the DBFAIL TRAP. Additional error information may be obtained by using the DBERROR statement. Failure to trap these errors will result in a runtime error message and program termination. For 5xx series subcodes, see the table in the I errors section.
|
Code |
Description |
|
D201 |
Unable to connect to remote database. Extended error codes for MySQL connections are: |
|
|
1045: Access denied. |
|
|
2001: Failed to create a Linux socket. |
|
|
2002: Failed to connect to the local MySQL server. |
|
|
2003: Failed to connect to the MySQL server. |
|
|
2004: Failed to create an IP socket. |
|
|
2005: Failed to find the IP address for the hostname. |
|
|
2007: A protocol mismatch resulted from attempting to connect to a server with a client library that uses a different protocol version. This can happen if you use a very old client library to connect to a new server that wasn't started with the --old-protocol option. |
|
|
2008: Out of memory. |
|
|
2013: If connect_timeout is specified and it took longer than the specified number of seconds to connect to the server or if the server died while executing the initialization command. |
|
D202 |
Error occurred while executing DBSEND. One possible cause of this error is buffer overflow. |
|
D203 |
Unable to execute query. Extended error codes for MySQL connections are: |
|
|
2000: An unknown error occurred. |
|
|
2006: The MySQL server has gone away. |
|
|
2013: The connection to the server was lost during the query. |
|
|
2014: Commands were executed in an improper order. |
|
D204 |
Problem occurred while retrieving the next row from the remote database |
|
D205 |
An operation is being performed on a DBFILE file object that has not had a successful DBCONNECT performed on it (the DBFILE is still closed). |
|
D207 |
Unable to retrieve state of query. |
|
D208 |
Unable to halt query. |
|
D209 |
Unable to convert item during DBFETCH. The subcode value is a variable count from one to N for the fetch variable that encountered the conversion problem. |
|
D210 |
No more memory. |
|
D211 |
A column type is being used that is not supported by Windows ODBC operations. The valid column types that are supported can be found in the note (8.) description for the DBFETCH instruction. |
|
D212 |
Error getting the result. |
|
D213 |
Error on a DBTRANSACTION. |
|
D214 |
Error on a DBPREPARE. |
|
D215 |
Problem occurred while retrieving the previous row from the remote database. |
|
D216 |
Already under a transaction. |
|
D217 |
No transaction in process. |
|
D218 |
Error when disconnecting. |
|
D220 |
No driver entry or dll |
|
D221 |
Bad driver version. |
|
D222 |
Unsupported statement. |
|
D223 |
Unable to open a statement. |
|
D224 |
Bad cursor type. |
See Also: PL/B Errors
![]() |