Oracle Analytics Cloud and Server

Home› Oracle Analytics› Oracle Analytics Forums› Oracle Analytics Cloud and Server› Oracle Analytics Cloud and Server

Categories

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

Direct Database Request results in ORA-12154: TNS:could not resolve the connect identifier specified

Received Response
44
Views
15
Comments
3240307
3240307 Rank 4 - Community Specialist
edited Aug 13, 2024 6:05PM in Oracle Analytics Cloud and Server

We are trying to create a test analysis using Direct Database Request and keep running into this error. We have checked the database details, the connection pool seems to be correct (Import Metadata works flawlessly) but when we use the same connection pool for the DDBR, it errors out with the above error.

Any pointers in where the issue could be?

OBIEE 11.1.1.9.0

Oracle 12.1.0.2 on Exadata

«1

Answers

  • Joel
    Joel Rank 8 - Analytics Strategist

    If you import your table into physical layer for test purposes, can you update the table count or select from it?

  • 3240307
    3240307 Rank 4 - Community Specialist

    Yes I can, I can do both.

  • Joel
    Joel Rank 8 - Analytics Strategist

    How do you reference your connection pool in you DDR? Do you qualify it with the database name as defined in the physical layer?

    for example:

    "database name"."connection pool"

  • 3240307
    3240307 Rank 4 - Community Specialist

    No, never had to do that before. Just use the name of the connection pool. You think that would help? With the quotes?

  • 3240307
    3240307 Rank 4 - Community Specialist

    Just tried it, same error.

  • 3310714
    3310714 Rank 6 - Analytics Lead

    Are you running the Analysis and Import from the same workstation?   How about your SID, does it need to be fully qualified?  Orcl.abc.com instead of Orcl?

  • 3240307
    3240307 Rank 4 - Community Specialist

    Yes I am, but how does that matter? When you ask if my SID "needs" to be fully qualified, how does that create the difference in behavior I'm talking about? I have tried both though and the error is the same.

  • 3310714
    3310714 Rank 6 - Analytics Lead

    The error message says it can't resolve the connect identifier.  If it was another workstation getting this error, maybe they don't have the drivers installed.  But since you're running from the same PC, that's not it. 

    I'd noticed before in my network, i had to use a fully qualified SID and server name.  otherwise OBI doesn't connect to the DB.

    can you supply screenshots?

  • 3240307
    3240307 Rank 4 - Community Specialist

    It is only 1 application server so I'm still unsure as to how a "workstation" will make a difference. The server that hosts the application (OBIEE) has the drivera/client installed. I unfortunately cannot provide screenshots beyond what I've mentioned already. I can post logs etc though if you'd like anything in particular.

  • 3310714
    3310714 Rank 6 - Analytics Lead

    How are you defining your data source, using tnsnames.ora ((DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=server.domain.com)(PORT=your_port)))(CONNECT_DATA=(SID = your_db))))

    or

    easyconnect (server:port/sid)?

    have you tried both?