Oracle Error Code 12154 Obiee
Contents |
Error code: 12154, message: ORA-12154: TNS:could not resolve the connect identifier specified at OCI call OCIServerAttach. [nQSError: 17014] Could not connect to could not connect to oracle database in obiee 11g Oracle database. The error is simply OBIEE reporting that it tried
Nqserror 17014 In Obiee 11g
to connect from the BI Server to an Oracle database and the Oracle client returned an error. Distilling obiee 11g tnsnames ora location it down gives us this error: ORA-12154: TNS:could not resolve the connect identifier specified at OCI call OCIServerAttach. This generally means one of three things: You've got the correct nqserror 17014 could not connect to oracle database obiee 12c Data Source Name (DSN) in your connection pool configuration, but not in your tnsnames.ora file You've got the correct DSN in your tnsnames.ora but you've not updated the connection pool, or connection pools You've got the correct DSN in your connection pool and tnsnames.ora, but have multiple tnsnames.ora files and OBIEE is using a different one from the one
Error Codes: Opr4onwy:u9im8tac:oi2dl65p
you've got the correct DSN in. To check your connection pool, open the RPD in Adminstration tool and go to the Physical Layer. Expand the Database, and double-click on the Connection Pool (if you're not sure which one, then check all of them!). In the connection pool check the Data Source Name and make sure it matches to what you have in your tnsnames.ora file: To check your tnsnames.ora, first locate it. This ties in with the third point on my list too. Be aware that you may have several copies of this file, so make sure you're opening the correct one. I've not done extensive testing of this but until proven otherwise I would assume that OBIEE uses the tnsnames.ora in $ORACLE_HOME/network/admin/ $ORACLE_HOME should be set in [OracleBI]/setup/user.sh or your user profile. Note that it's the home for the connectivity (usually client), not necessarily your DB. Once you've located the correct tnsnames.ora file check that it has a valid entry for the DSN in your connection pool. You should use the tnsping utility t
Intelligence (OBIEE/Siebel Analytics) OBIEE 10G/11G - Oracle Call Interface (OCI) configuration OBIEE 10G/11G - Oracle Call Interface (OCI) configuration Table of Contents 1 - About 2 - Articles Related 3 - Prerequisites 3.1 nqserror 43113 - 10g 3.2 - 11g 4 - Connect identifier 4.1 - Net Service oracle oci Name 4.2 - Easy Connect Method 4.3 - Connect Descriptor 5 - Support 5.1 - ORA-12154: TNS:could not resolve the
Tnsping
connect identifier 5.2 - ODBC limitations 6 - Documentation / Reference 1 - About OCI stands for Oracle Call Interface (OCI). It's an Call Level Interface API (such as ODBC and JDBC but https://rnm1978.wordpress.com/2009/10/22/troubleshooting-obiee-and-ora-12154-tnscould-not-resolve-the-connect-identifier/ specific to Oracle) that lets you develop application and access an Oracle Database. 2 - Articles Related OBIEE - Connection PoolOBIEE 10G/11G - Event Pooling table (Event Table) to purge the cache after ETL processOBIEE - Physical LayerOBIEE - Data Source (Oracle Analytics Adapter) 3 - Prerequisites 3.1 - 10g To use it you have to install it on the BI Server machine through an Oracle Client http://gerardnico.com/wiki/dat/obiee/oci installation (for instance an Oracle Database, an Oracle Client or an Oracle Instant). This installations will provide you the oci.dll file which is the OCI binary. And the directory of this binary must be located in the path environment variable of the user who start the BI Server (for a remote server import) or the Administration tool for a local import. 3.2 - 11g The OCI dll are shipped with the installation. cd /u01/app/oracle/product/fmw/Oracle_BI1/lib ls -l *oci* -rwxr-x--- 1 oracle oinstall 117051 Oct 14 17:12 libnmeoci.so -rw-r----- 1 oracle oinstall 0 Apr 28 2011 libnmeoci.so.0 4 - Connect identifier To configure OCI, you have to provide in the connection pool of the physical layer three parameters: the call interface. You must choose OCI. The data source name The user name and password In the data source name, you have to enter a connect identifier that can be one of the following naming methods. 4.1 - Net Service Name A Net Service Name (TnsName). This descriptor must be defined in the tnsnames.ora file. OCI localized this file with the help of the TNS_ADMIN environment variable. In 11g locally, you must set this environment variable in the file bi-init
With Error: "ORA-12504 or ORA-12154″ February 21, 2012 OBIEE Architect Leave a comment Applies to Business Intelligence Suite Enterprise Edition http://obiee-blog.info/tag/connection-pool/ - Version: 11.1.1.3.0 [1905] to 11.1.1.5.0 [1308] [Release: 11g to 11g] Symptoms After upgrading to Oracle Business Intelligence Enterprise Edition (OBIEE) 10g to OBIEE 11g, when viewing a dashboard or http://allappsdba.blogspot.com/2013/05/obiee-11g-client-admin-tool-connection.html creating a new analysis in Answers, the following error occurs: State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message obiee 11g returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 17001] Oracle Error code: 12504, message: ORA-12504: TNS:listener was not given the SERVICE_NAME in CONNECT_DATA at OCI call OCIServerAttach. [nQSError: 17014] Could not connect to Oracle database. (HY000) Or you might get the error: [2010-11-16T06:02:38.000+00:00] [OracleBIServerComponent] [ERROR:1] [] [] [ecid: 004_ILDmfHpFw000jzwkno0002Xk0000qx] [tid: 4f353960] [nQSError: 17014] Could not could not connect connect to Oracle database. [[ [nQSError: 17001] Oracle Error code: 12154, message: ORA-12154: TNS:could not resolve the connect identifier specified at OCI call OCIServerAttach. [nQSError: 43093] An error occurred while processing the EXECUTE PHYSICAL statement. [nQSError: 43113] Message returned from OBIS. It looks like all the database connections have been broken. Another symptom that may occur is that the BI Server does not start up and you get the following error in the nqserver.log: [ecid: 00hxwa3cUNZ4aq_S9Q2FSx0001SO000000] [tid: 814] [36007] Loading repository E:\obiee11g\instances\instance2\bifoundation\OracleBIServerComponent\coreapplication_obis1\repository\11rpd.rpd. [2011-01-06T20:20:52.000+00:00] [OracleBIServerComponent] [ERROR:1] [] [] [ecid: 00hxwa3cUNZ4aq_S9Q2FSx0001SO000000] [tid: 19b4] [nQSError: 17014] Could not connect to Oracle database. [[[nQSError: 17001] Oracle Error code: 12154, message: ORA-12154: TNS:could not resolve the connect identifier specifiedat OCI call OCILogon. Changes Upgraded from OBIEE 10g to OBIEE 11g. Cause In OBIEE versions prior to 11g, it uses the database client home tnsnames.ora file to resolve the tnsname. But OBIEE 11g uses the tnsnames.ora file installed within its installation home. The path is [middleware
in India. With rich experience In Oracle E-Business, Oracle Database, Oracle Application Express (APEX), Oracle J Developer, Oracle OBIEE and E-Business Suite DOYENSYS Knowledge Portal We Welcome you to visit our DOYENSYS KNOWLEDGE PORTAL : Doyensys Knowledge Portal Thursday, May 9, 2013 OBIEE 11g Client Admin Tool Connection To Datasource In Offline Mode Fails With Error "The Connection Has Failed" OBIEE 11g Client Admin Tool Connection To Datasource In Offline Mode Fails With Error "The Connection Has Failed" Created a new repository (RPD) using the Oracle Business Intelligence Enterprise Edition (OBIEE) Admin Tool. When trying to import data in offline mode, the following error occurs with both ODBC and OCI connection: ErrorThe Connection has failed. You may also notice all or some of the following errors in NQSAdminTool.log: [2011-02-07T11:26:19.000+00:00] [OracleBIServerComponent] [nQSError: 17003] Oracle gateway error: OCIEnvNlsCreate or OCIEnvInit failed to initialize environment. Please check your Oracle Client installation and make sure the correct version of OCI libraries are in the library path....[2011-02-08T15:42:58.000+00:00] [nQSError: 17014] Could not connect to Oracle database. [[[nQSError: 17001] Oracle Error code: 12154, message: ORA-12154: TNS:could not resolve the connect identifier specifiedat OCI call OCIServerAttach...]][2011-02-08T15:46:08.000+00:00] [nQSError: 17014] Could not connect to Oracle database. [[[nQSError: 17001] Oracle Error code: 12705, message: ORA-12705: Cannot access NLS data files or invalid environment specified at OCI call OCISessionBegin... The issue is not reproducible while in Online mode. This issue would be due to Multiple Oracle Homes exist which can cause confusion to the OBIEE Admin Tool for where to reference OCI libraries, NLS and the tnsnames.ora entries. Additional configuration steps are required to ensure the desired files are used. To prevent this error, you need to complete the following configuration tasks: NOTE: In all cases, the OBIEE Admin Tool should be started by using the Start -> Programs -> Oracle Business Intelligence -> Administration Tool menu item and not by double-clicking the RPD file itself. Starting the Admin Tool via the menu item is required t