Re: Dimension processing TNS Names do Not Resolve



Thanks Christophe,

I believe the issue (now resolved) had to do with the location of my TNS
file and/or the SQLNet.ORA file. I had two client installations , Oracle 9.1
and 9.2 on my machine, one of which had the TNS and SQLNet located in the
usual path to Admin, the other did not. When I copied these files over the
identical location for both, everything turned out ok.

But the suggestion below is a good idea - it would have resolved my issue
yesterday.

Thanks again,

Mark

"Christophe Niel" wrote:

I hihgly recommend that you do not use the tnsnames in your db
configuration, but instead use the full oracle string in place of the tns
name alias

your tns files should look like that :
DEV1ORA=
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost.localdomain)(PORT =
1521))
)
(CONNECT_DATA =
(SERVICE_NAME = dev1ora.devlin.com)
)
)


so in the connectring you can use "(DESCRIPTION
=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST = localhost.localdomain)(PORT =
1521)))(CONNECT_DATA=(SERVICE_NAME=dev1ora.devlin.com)))"
for the data source.

if you do this you can prevent any error in the tnsnames.ora files, NTFS
right to the file (probably your problem) or changes made by sysadmin you
don't know about.



"MarkFrank" <MarkFrank@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3E6EAF73-F9B5-42B5-9656-220E187D0406@xxxxxxxxxxxxxxxx
Hi all,

I have an Analysis Services DSV that exposes an Oracle database in the
relational view. However, when I try to process a dimension it fails
giving
me the following

Errors in the high-level relational engine. The following exception
occurred
while the managed IDbConnection interface was being used: ORA-12154:
TNS:could not resolve service name
.

I have checked my TNS_NAMES file and confirmed the entry of the server,
and
ODBC connection also tested out ok. Does anyone have any ideas of how the
DSV does show the table underneath on the Oracle server, but doesn't
process
a dimension?

Thanks,

Mark

.



Relevant Pages

  • Re: Dimension processing TNS Names do Not Resolve
    ... Great suggestion by Christophe - helped me with a completely different issue! ... I believe the issue had to do with the location of my TNS ... Oracle 9.1 ... TNS:could not resolve service name ...
    (microsoft.public.sqlserver.olap)
  • Re: Dimension processing TNS Names do Not Resolve
    ... I hihgly recommend that you do not use the tnsnames in your db configuration, but instead use the full oracle string in place of the tns name alias ... when I try to process a dimension it fails giving ... DSV does show the table underneath on the Oracle server, ...
    (microsoft.public.sqlserver.olap)
  • RE: TWO_TASK environment variable
    ... Copyright 1982, 2006, Oracle. ... ORA-12154: TNS:could not resolve the connect identifier specified ... Enter user-name: ... unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus ...
    (perl.dbi.users)
  • Re: ERROR ORA-12154 TNS: could not resolve the connect identifier specified
    ... I have a strange problem with oracle connection. ... could not resolve the connect identifier specified" ... srror on the browser. ... ociparseexpects parameter 1 to be resource, ...
    (comp.databases.oracle.misc)
  • TWO_TASK environment variable
    ... Copyright 1982, 2006, Oracle. ... ORA-12154: TNS:could not resolve the connect identifier specified ... Enter user-name: ... unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus ...
    (perl.dbi.users)