Home » RDBMS Server » Networking and Gateways » Not able to connect to Oracle(12c) to progress using Oracle database gateway(12c) for ODBC (Oracle12c , Oracle database gateway for ODBC 12c , Progress Version 11)
|
|
|
|
|
|
|
|
|
|
Re: Not able to connect to Oracle(12c) to progress using Oracle database gateway(12c) for ODBC [message #671824 is a reply to message #671786] |
Thu, 20 September 2018 06:47  |
 |
EdStevens
Messages: 1376 Registered: September 2013
|
Senior Member |
|
|
You posted same to my blog yesterday.
We'll deal with it here instead, as this will get more eyeballs on your issue. For the sake of the other participants, here is my response that I posted on the blog:
Quote:
Ok, I have several questions.
First, if your gateway is installed on Server 2, then you have no need of gateway related entries in the listener.ora on Server 1. Why have you created initGW_TO_PROG.ora on server 1? Why do you have a SID_DESC for GW_TO_PROG in the listener.ora on server 1? All that does is confuse the analysis of the problem.
Second, why is the listener on server 2 using port 1522 instead of the default of 1521?
Third, the error message "Unable to retrieve text of NETWORK/NCR message 65535" was particularly curious, so I googled ORA-65535 and found this:
ORA-65535: Oracle client cannot handle error code exceeding 65535. Actual error code and message follow:\n
Cause: Oracle server encountered an error whose error code exceeded 65535. Older Oracle clients (prior to version 12) cannot handle error codes larger than 65535.
Action: Actual Oracle error code and error message are a part of the error message for ORA-65535. Upgrade Oracle client to version 12 client libraries or higher.
(see https://docs.oracle.com/database/121/ERRMG/ORA-60001.htm#ERRMG-GUID-9B78A028-D760-4810-9CFC-9013FBD1FCC9).
Fourth, you state "SP2 is a DB link pointing to GW_TO_PROG service name.". No, "SP2" is not a db link, it is a stored procedure. There is a reference to a db link somewhere in the stored procedure. You've shown me all your config files but you haven't shown the actual code that initiates the call. If I were sitting next to you I'd want to see both the actual sql statement that references the db-link and the properties of the db link, as shown by 'SELECT * FROM DBA_DB_LINKS
WHERE DB_LINK = ''
The path from the sql statement making the call, to the target non-oracle database is a very clear an precise chain, as described in the article. To debug any issues, we simply follow each link in the chain. That begins with the SQL statement in your stored procedure.
Also, what version of OTG for ODBC is installed on Server2?
BTW, as of yesterday evening I relocated most of the original content of my blog to my older site edstevensdba.wordpress.com. I am close to retirement and have lost interest in maintaining the blog (and incurring the expense of self-hosting), so have moved content back to a free platform where it can remain for future reference.
|
|
|
Goto Forum:
Current Time: Sun May 04 17:21:43 CDT 2025
|