Re: Dimension processing TNS Names do Not Resolve
- From: "Christophe Niel" <Christophe.Niel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 18 Dec 2007 12:35:27 +0100
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
.
- Follow-Ups:
- Re: Dimension processing TNS Names do Not Resolve
- From: MarkFrank
- Re: Dimension processing TNS Names do Not Resolve
- Prev by Date: Re: Lazy Aggregation - Dropping Aggregations and Indexes Problem
- Next by Date: Re: One Fact or Two?
- Previous by thread: How to work with a time dimension
- Next by thread: Re: Dimension processing TNS Names do Not Resolve
- Index(es):
Relevant Pages
|
