Estou recebendo esse erro quando tento acessar o oracle via Visual Studio 2008, pelo componente SQLDataSource, o engraçado é se eu fizer a conexão via código, consigo acessar normalmente, também consigo acesso pelo PL/SQL e SQL*Plus.
Instalei o Oracle 11g Release 2 ODAC 11.2.0.1.2 with Oracle Developer Tools for Visual Studio (o mais recente).
alguém poderia me ajudar?
Erro Ora-12154
-
- Rank: Analista Sênior
- Mensagens: 164
- Registrado em: Sex, 22 Ago 2008 12:28 pm
- Localização: SP
ORA-12154 TNS:could not resolve service name Oracle version: 8i
Cause: The service name specified is not defined correctly in the TNSNAMES.ORA file.
Action: Make the following checks and correct the error:
- Verify that a TNSNAMES.ORA file exists and is in the proper place and accessible. See
the operating system specific manual for details on the required name and location.
- Check to see that the service name exists in one of the TNSNAMES.ORA files and add it
if necessary.
- Make sure there are no syntax errors anywhere in the file. Particularly look for
unmatched parentheses or stray characters. Any error in a TNSNAMES.ORA file makes it
unusable. See Chapter 4 in the SQL*Net V2 Administrator's Guide. If possible, regenerate
the configuration files using the Oracle Network Manager.
ORA-12154 TNS:could not resolve the connect identifier specified Oracle version: 10g
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.
Retidado de :
http://www.ora-error.com/error.php
Att,
DIego Monteiro
-
- Rank: Analista Sênior
- Mensagens: 164
- Registrado em: Sex, 22 Ago 2008 12:28 pm
- Localização: SP
Você tem instalado vários ORACLE_HOME na máquina?
Isso pode acontecer devido a vários clientes instalados, ou seja, uma aplicação um Oracle_HOME e outra aplição usa a outra instalação como HOME. Se for isso você tem que copiar o TNS completo para a outra HOME.
Att,
Diego Monteiro
Isso pode acontecer devido a vários clientes instalados, ou seja, uma aplicação um Oracle_HOME e outra aplição usa a outra instalação como HOME. Se for isso você tem que copiar o TNS completo para a outra HOME.
Att,
Diego Monteiro
-
- Informação
-
Quem está online
Usuários navegando neste fórum: Nenhum usuário registrado e 6 visitantes