Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 657
  • Last Modified:

ODBC Error when connecting from Oracle to SQL Server 2005

I have an application and when data in a table is updated a trigger is executed and sends information from oracle to sql server 2005.  This was working correctly and all of a sudden I began seeing the following error message:

Detail Message=java.sql.SQLException: ORA-28500: connection from ORACLE to a non-Oracle system returned this message: [Generic Connectivity Using ODBC][S1000] [9013]General error in nvITrans_BeginT - rc = -1. Please refer to the log file for details. ORA-02063: preceding 2 lines from KANCARD

I'm not sure why this error occurred or how to correct it.  Help is greatly appreciated as this is in our production environment.
0
algoma
Asked:
algoma
  • 2
1 Solution
 
Geert GOracle dbaCommented:
oracle is trying to login on the sql server with a user
1: which doesn't exist anymore on the sql server
or
2: of which the password has changed on the sql server
0
 
FaherCommented:
kindly first check database link (from Oracle to sql server ).
check tns service alias using tnsping command.

If there is any issue with databas link then recreate database link from oracle to sql server

create database link ODBC connect to "sa" identified by "pencil" using 'hsodbc'.

If you encase the login and password in double quotes and the tnsnames reference in single quotes, then the connection between Oracle and MSSQL works perfectly.
0
 
algomaAuthor Commented:
>>oracle is trying to login on the sql server with a user
>>1: which doesn't exist anymore on the sql server
>>or
>>2: of which the password has changed on the sql server

The user and password does still exist as I was able to log in to SQL Server Mgmt Studio with it.


>>kindly first check database link (from Oracle to sql server ).
>>check tns service alias using tnsping command.

Prior to seeing this message I did drop the link and recreate the link which seemed to "fix" the problem.  I still have no idea what caused the problem and more importantly I have no idea when this problem is going to take us down again.  I know I can work around this problem by setting something up to schedule the link to be dropped and created at some given interval but I really would like to understand why this is happening and how to prevent/handle it rather than just blindly recreating the link.
0
 
algomaAuthor Commented:
The reason I accepting my own comment as the solution is because my comment was the correct solution.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now