5.1 Interpreting Gateway Error Messages
The gateway architecture consists of different components and any component may detect and report an error condition while processing SQL statements that refer to one or more DRDA database tables.
This means that errors can be complex, involving error codes and supporting data from multiple components. In all cases, however, the application ultimately receives a single error code or a return code.
As most gateway messages exceed the 70 character message area in the Oracle SQL Communications Area (SQLCA), the programmatic interfaces and Oracle Call Interfaces, that you use to access data through the gateway should use SQLGLM or OERHMS to view the entire text of messages. Refer to the programmer's guide to the Oracle precompilers for additional information about SQLGLM, and refer to the Oracle C++ Call Interface Programmer's Guide for additional information about OERHMS.
Errors encountered when using the gateway can originate from the following sources:
- Errors detected by the Oracle database
- Errors detected by the gateway
- Errors detected in the DRDA software, either on the client or server side
- Communication errors
- Errors detected by the server database
- Errors Detected by the Gateway
Errors detected by the Oracle database are reported back to the application or tool with the standardORA
type message. - Errors Detected in the DRDA Software
Errors detected in the DRDA gateway, on the client or server side, are usually reported with errorORA-28500
, followed by a gateway-specific expanded error message. - Errors Detected by the DRDA Server
Errors detected by the DRDA server are reported with anORA-28500
followed by a gateway-specific expanded error message.
Parent topic: Error Messages, Diagnosis, and Reporting
5.1.1 Errors Detected by the Gateway
Errors detected by the Oracle database are reported back to the application or tool with the standard ORA
type message.
Refer to Oracle Database Error Messages for descriptions of these errors. For example, the following error occurs when an undefined database link name is specified:
ORA-02019: connection description for remote database not found
Errors in the ORA-9100
to ORA-9199
range are reserved for the generic gateway layer (components of the gateway that are not specific to DRDA). Messages in this range are documented in Oracle Database Error Messages.
Parent topic: Interpreting Gateway Error Messages
5.1.2 Errors Detected in the DRDA Software
Errors detected in the DRDA gateway, on the client or server side, are usually reported with error ORA-28500
, followed by a gateway-specific expanded error message.
There are two return codes reported in the expanded message:
drc
specifies DRDA-specific errors.grc
specifies generic gateway errors detected in the DRDA layer. These errors are documented in the Oracle Database Error Messages.
Note:
Error codeORA‐28500
was error code ORA‐09100
prior to gateway version 8. Error code ORA‐28501
was listed as ORA‐09101
prior to gateway version 8.
The values in parentheses that follow the drc
values are used for debugging by Oracle Support Services. The errp
field indicates the program (client or server) that detected the error. If present, errmc
lists any error tokens.
For example, the following error message is returned when the database name specified with the DRDA_REMOTE_NAME
parameter in the initsid.ora
file is not defined at the DRDA server:
ORA-28500: connection from ORACLE to non-Oracle system returned the message:
Parent topic: Interpreting Gateway Error Messages
5.1.3 Errors Detected by the DRDA Server
Errors detected by the DRDA server are reported with an ORA-28500
followed by a gateway-specific expanded error message.
Refer to IBM documentation for the specific database being used. Also refer to Mapped Errorsfor some SQL errors that get translated.
Note:
Error codeORA‐28500
was error code ORA‐09100
prior to gateway version 8. Error code ORA‐28501
was listed as ORA‐09101
prior to gateway version 8.
For example, the following error message indicates that the DRDA server did not find the DB2 database name specified in the HS_FDS_CONNECT_INFO
parameter in the initSID.ora
file:
ORA-28500: connection from ORACLE to a non-Oracle system returned this message: [Oracle][ODBC DB2 Wire Protocol driver]Remote Database Not Found: UNKNOWN
Parent topic: Interpreting Gateway Error Messages