Home » RDBMS Server » Networking and Gateways » how to set orale Gateways 11g for mssql
how to set orale Gateways 11g for mssql [message #444386] Sun, 21 February 2010 06:02 Go to next message
daizhicun
Messages: 6
Registered: February 2010
Location: china
Junior Member

I want connect mssql in oracle by orale Gateways 11g

my environment:
windows Wista
oracle 11.1.0.7.0
Oracle Database Gateways 11.1.0.7.0
SQL SEVER2008

these softs in one computer.


my steps :

1. set initdg4mssql.ora

http://www.daizhicun.com/dmx/pic/initdg4mssql.jpg

2.set listener.ora

http://www.daizhicun.com/dmx/pic/listener.jpg



3. set tnsnames.ora

http://www.daizhicun.com/dmx/pic/tnsnames.jpg

4.start lsnrctl

http://www.daizhicun.com/dmx/pic/lsnrctlstart.jpg

5.use SYSTEM/ORACLE@DZCDB
logined. create dblink and test.
but it's error. i want to know where is the error.
http://www.daizhicun.com/dmx/pic/dblink.jpg

[Updated on: Sun, 21 February 2010 06:12] by Moderator

Report message to a moderator

Re: how to set orale Gateways 11g for mssql [message #444812 is a reply to message #444386] Wed, 24 February 2010 05:39 Go to previous message
tahpush
Messages: 961
Registered: August 2006
Location: Stockholm/Sweden
Senior Member

Quote:
ORA-12154: TNS:could not resolve the connect identifier specified
Cause: A connection to a database or other service was requested using a connect identifier, and the connect identifier specified could not be resolved into a connect descriptor using one of the naming methods configured. For example, if the type of connect identifier used was a net service name then the net service name could not be found in a naming method repository, or the repository could not be located or reached.
Action: - If you are using local naming (TNSNAMES.ORA file):

- Make sure that "TNSNAMES" is listed as one of the values of the NAMES.DIRECTORY_PATH parameter in the Oracle Net profile (SQLNET.ORA)

- Verify that a TNSNAMES.ORA file exists and is in the proper directory and is accessible.

- Check that the net service name used as the connect identifier exists in the TNSNAMES.ORA file.

- Make sure there are no syntax errors anywhere in the TNSNAMES.ORA file. Look for unmatched parentheses or stray characters. Errors in a TNSNAMES.ORA file may make it unusable.

- If you are using directory naming:

- Verify that "LDAP" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).

- Verify that the LDAP directory server is up and that it is accessible.

- Verify that the net service name or database name used as the connect identifier is configured in the directory.

- Verify that the default context being used is correct by specifying a fully qualified net service name or a full LDAP DN as the connect identifier

- If you are using easy connect naming:

- Verify that "EZCONNECT" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).

- Make sure the host, port and service name specified are correct.

- Try enclosing the connect identifier in quote marks. See the Oracle Net Services Administrators Guide or the Oracle operating system specific guide for more information on naming.
Previous Topic: ora-01033: Oracle initialization or shutdown in progress
Next Topic: ORA-01741: illegal zero-length identifier for DBlink
Goto Forum:
  


Current Time: Sun Nov 23 07:25:18 CST 2014

Total time taken to generate the page: 0.08605 seconds