Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DBLINK access from 7.3.4 via 8.1.7 to a SQLServer Gateway.

Status
Not open for further replies.

dbtoo2001

MIS
Jun 18, 2001
415
US
I have a situation where we are still supporting Oracle Apps 10.7 on 7.3.4 (Yeah, I know!)

The application currently uses a dblink with gateway vers. 4 to MSSQL sqlserver 6.5. We have to move the sqlserver to version 2000 by the end of the year. Knowing that 7.3.4 cannot use any gateway directly to SQLServer 2000, I've setup the following:
7.3.4 has a dblink to a user in an 8.1.7 database. That user has views via dblinks and gateway vers. 8 to Sqlserver 2000.
Using sqlplus on the 7.3.4 database I can perform queries and obtain results within a second or two. However, the Oracle Application seems to hang, when the same dblink is used.
Tracing on the gateway shows that the transaction arrives. SQLNet trace does not show any errors. Any ideas on why the application appears to hang? (The testers kill their sessions after a couple of minutes, so nobody knows if it ever actually ever returns to the application - but no user is going to wait more than a minute or two anyway.) I've searched metalink, read the manuals for gateway, sqlnet, net8, etc. but haven't found any solid leads to resolve this.
This is not a supported method, but then again, it doesn't mean it can't be done.
(Don't even think about suggesting that the 7.3.4 be migrated to 8.1.7, that's been a project that was canceled twice, for various reasons. No need to mention that 7.3.4 was desupported years ago, either. )

I'm stumped on why I can get results via sqlplus but not from within the 10.7 application?

Has anyone been successful at connecting a 7.3.4 to a sqlserver 2000. (I'm trying to avoid a strip and ship of the data, the users need 'realtime' access.)

Thanks. (this was posted in dbforums too, but that site isn't available today, and there wasn't anyone taking a guess at it.)
 
I get to answer my own thread, turned out that the interim database was at 8.1.7 and not 8.1.7.4. Installing the patch fixed the problem.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top