Nqserror 17001 Oracle Error Code 12154
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 Oracle database. The error is simply OBIEE reporting that it tried to connect could not connect to oracle database in obiee 11g from the BI Server to an Oracle database and the Oracle client returned an
Nqserror 17014 In Obiee 11g
error. Distilling it down gives us this error: ORA-12154: TNS:could not resolve the connect identifier specified at OCI call OCIServerAttach. This
Nqserror 17014 Could Not Connect To Oracle Database Obiee 12c
generally means one of three things: You've got the correct 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
Obiee 11g Tnsnames Ora Location
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 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 error codes: opr4onwy:u9im8tac:oi2dl65p 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 to validate it: $tnsping ORCL TNS Ping Utility for HPUX: Version 10.2.0.1.0 - Production on 22-OCT-2009 12:38:33 Copyright (c) 1997, 2005, Oracle. All rights reserved. Used parameter files: /app/oracle/product/10.2.0/network/admin/sqlnet.ora Used TNSNAMES adapter to resolve the alias Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = myoracleserver)(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = ORCL))) OK (0 msec) If you think you've eliminated these three possibilities then the next step would be to enable tracing i
Check Error Console Dashboard Database Display Error Enterprise Manager Mobile Model Check Error nQSError OBIEE 11.1.1.7 Oracle Error Code Performance Presentation Server Error Properties Queries Repository Server XML edit CONTACT Name *Email *Message *VerificationPlease enter nqserror 43113 any two digits *Example: 12This box is for spam protection - please leave oracle oci it blank: RECENT Add a message to the Sign In page The primary key of the logical level is not tnsping unique Invalid identifier at OCI call OCIStmtExecute (2) Cannot read property ‘getAttribute' of null Change "signing-in-failed" message on Sign In screen Tagscatalog manager column selector connection pool consistency check content delete dimension entry error https://rnm1978.wordpress.com/2009/10/22/troubleshooting-obiee-and-ora-12154-tnscould-not-resolve-the-connect-identifier/ Error No. 39008 hostname HTML identifier instanceconfig.xml key level locked LOV Managed server Node manager nQSError: 10058 nQSError: 15001 nQSError: 17001 nQSError: 17010 nQSError: 17014 nQSError: 43093 nQSError: 43113 nQSError: 43119 OBIEE ORA-00942 Oracle BI processes physical column prompt prompts replace repository rpd runcat.sh Sign In tnsnames.ora user warning webcat Weblogic server xml TNS:could not resolve the connect identifier specified at OCI call OCIServerAttach When you get http://www.obiee247.com/tnscould-not-resolve-the-connect-identifier-specified-at-oci-call-ociserverattach/ the error message ("TNS:could not resolve the connect identifier specified at OCI call OCIServerAttach") State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS [nQSError: 43119] Query Failed: [nQSError: 17001] Oracle Error code: 12154, message: ORA-12154: TNS:could not resolve the connect identifier specified at OCI call OCIServerAttach. [nQSError: 17014] Could not connect to Oracle database. (HY000) the Data Source Name that is used in the connectionpool of the physical database that is used to show the report, is not found in the tnsnames.ora file. This is how you can fix it; log in to the server go to the directory where the tnsnames.ora file is located cd $FMW_HOME/Oracle_BI/network/admin create a copy of tnsnames.ora cp tnsnames.ora tnsnames.ora[_orig] edit the file, for example with vi-editor vi tnsnames.ora insert the entry save the tnsnames.ora :wq The error message will not be displayed anymore. Tweet Posted on 6 March 201527 September 2016Author BerryCategories Display Error, nQSError, OBIEE 11.1.1.7, ServerTags entry, nQSError: 10058, nQSError: 17001, nQSError: 17014, nQSError: 43113, nQSError: 43119, ORA-12154, tnsnames.ora Post navigation Previous Previous post: Replace (All Column Values) text in promptNext Next post: Internal error: No matching table for expr Proudly po
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 - 10g 3.2 - 11g 4 - Connect identifier 4.1 http://gerardnico.com/wiki/dat/obiee/oci - Net Service Name 4.2 - Easy Connect Method 4.3 - Connect Descriptor 5 - Support 5.1 - ORA-12154: TNS:could not resolve the connect identifier 5.2 - ODBC limitations 6 - Documentation / Reference 1 - About OCI stands http://allappsdba.blogspot.com/2013/05/obiee-11g-client-admin-tool-connection.html for Oracle Call Interface (OCI). It's an Call Level Interface API (such as ODBC and JDBC but specific to Oracle) that lets you develop application and access an Oracle Database. 2 - Articles Related OBIEE - Connection PoolOBIEE obiee 11g 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 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 could not connect 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 If the TNS_ADMIN environment variable is not set then the ORACLE_HOME variable must be set, and the configuration files are expected to be in the $ORACLE_HOME/network/admin directory. In 11g, it's then Oracle_BI_HOME/network/admin. 4.2 - Easy Connect Method A SQL Connect URL such as //database_host[:port]/service_name 4.3 - Connect Descriptor You can also enter a connect descriptor. ( DESCRIPTION= ( ADDRESS=(PROTOCOL=tcp)(HOST=oracle11gr2.gerardnico.local)(PORT=1521) ) ( CONNECT_DATA=(SERVICE_NAME=ORCL) ) ) 5
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 do