This content has been marked as final. Show 3 replies
1 person found this helpful
976592 wrote:Is the MSSql Server instance 32 or 64-bit? (I think it should say from properties on the db server/top node, in Product name.)
My main problem is that I am trying to install the option for one of my clients that is using Windows Server Standard with SQL SERVER 2008.
In SSMS, Server objects, Linked servers, Providers. Is OraOLEDB.Oracle listed?
2: How to get rid of where 10g added "Provider for OLE DB" on my personal computer now that 10g is uninstalled?Possibly it will be "overridden" if you install another instance of the provider, e.g. from a 11g Database product. Only one OraOLEDB may exist on the machine.
But to clean out the installation completely you probably need to do a system restore or re-install.
Check out ODAC packages with Xcopy deployment option, based on Instant client. That's about as lightweight a install of OLE DB you'll get.
It is 32 bit, but I loaded the 64-bit SSIS wizard and it was there, thank you for pointing that out!!
Now I am getting a new error... when I test the connection I get "Test connection failed because of an error in initializing provider. ORA-12154: TNS:could not resolve the connect identifier specified.
I checked the tnsnames.ora file to get the service name KFXXXXXXXX and got the username/password from the client but it is still not connecting to the database.
As the message says, the name for the connect descriptor could not be resolved (or found). Possibly wrong name given, wrong tnsnames.ora or bad tnsnames.ora file.
Try leaving out the use of tnsnames, by using the format 'hostname:port/service_name' instead where you enter connection name. E.g localhost:1521/xe. Leaving out the port number if std port 1521 is used is possible, e.g. localhost/xe instead.