Oracle Error Code 12154 Message Ora-12154
Contents |
CommunityOracle User Group CommunityTopliners CommunityOTN Speaker BureauJava CommunityError: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on and reload this page. nqserror 17014 could not connect to oracle database Please enter a title. You can not post a blank message. Please
Could Not Connect To Oracle Database In Obiee 11g
type your message and try again. More discussions in Business Intelligence Suite Enterprise Edition All PlacesBusiness IntelligenceBusiness Intelligence nqserror 17001 in obiee 11g FoundationBusiness Intelligence Suite Enterprise Edition This discussion is archived 1 Reply Latest reply on Dec 22, 2011 3:08 AM by Dpka Unable to view data on dashboards OBIEE 11G message: nqserror 17014 in obiee 11g ORA-12154: TNS: user1153604 Dec 21, 2011 8:55 PM I am receiving this error on the dashboard of a newly installed OBIEE 11.1.0.5: State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 17001] Oracle Error code: 12154, message: ORA-12154: TNS:could not resolve the connect identifier specified at OCI
Obiee 11g Tnsnames Ora Location
call OCIServerAttach. [nQSError: 17014] Could not connect to Oracle database. (HY000) I have read many articles but still I am faced with this issue. This is what i have done so far: 1. I can TNSPING my database 2. I have tried to connect with username and password via sqlplas with no issues 3. copied my tnsnames.ora from $ORACLE_HOME/network/admin to ORACLE_BI1/network/admin Dir 4. edited user.sh to point my TNS_ADMIN=$ORACLE_HOME/Network/admin 5. restarted all services weblogic/coreapplication(biserver) and still I am getting the same error. My environment is Linux x64 Help really appreciated. I have the same question Show 0 Likes(0) 1372Views Tags: none (add) 11gContent tagged with 11g, callContent tagged with call, obieeContent tagged with obiee, ociContent tagged with oci, tnsContent tagged with tns This content has been marked as final. Show 1 reply 1. Re: Unable to view data on dashboards OBIEE 11G message: ORA-12154: TNS: Dpka Dec 22, 2011 3:08 AM (in response to user1153604) Hi User, Check this, https://cn.forums.oracle.com/forums/thread.jspa?threadID=2276845&start=0&tstart=0 Rgds, Dpka Like Show 0 Likes(0) Actions Actions About Oracle Technology Network (OTN)My Oracle Support Community (MOSC
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 ora-12154: tns:could not resolve the connect identifier specified any two digits *Example: 12This box is for spam protection - please leave it nqserror 17014 could not connect to oracle database obiee 12c blank: RECENT Add a message to the Sign In page The primary key of the logical level is not unique
Tns-03505
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://community.oracle.com/thread/2326696 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 the error http://www.obiee247.com/tnscould-not-resolve-the-connect-identifier-specified-at-oci-call-ociserverattach/ 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 powered by Wor
while creating a linked server to Oracle ★★★★★★★★★★★★★★★ SnehadeepJune 30, 201028 Share 0 0 This is one of the most common errors https://blogs.msdn.microsoft.com/dataaccesstechnologies/2010/06/30/ora-12154-tns-could-not-resolve-the-connect-identifier-specified-error-while-creating-a-linked-server-to-oracle/ while creating linked server to Oracle database. Today I will http://gerardnico.com/wiki/dat/obiee/oci discuss the reason for this error and possible resolutions.
Full error message: OLE DB provider "MSDAORA" for linked server "LINKED_ORA" returned message "ORA-12154: TNS:could not resolve the connect identifier specified". Msg 7303, Level 16, State 1, Line 1 Cannot initialize could not the data source object of OLE DB provider "MSDAORA" for linked server "LINKED_ORA". First of all make sure you have reviewed the following Microsoft KB article that has a lot of good information on troubleshooting Oracle linked server issues. How to set up and troubleshoot a linked server to an Oracle database in could not connect SQL Server http://support.microsoft.com/kb/280106 Also make sure you have installed Oracle Client on the SQL server. If the SQL server is 64 bit then we need to install 64 bit Oracle provider. You can also create linked server using Oracle ODBC driver together with Microsoft OLE DB provider for ODBC. Once again on a 64 bit SQL server you need to install the 64-Bit OLEDB Provider for ODBC (MSDASQL) and 64 bit Oracle ODBC drivers. However 64-Bit OLEDB Provider for ODBC (MSDASQL) is already there in Windows Vista/Windows Server 2008 and later OS. This particular error message is a very general error message and can happen for quite a number of reasons. For general understanding of the error, you can review oracle documentation like this http://ora-12154.ora-code.com/ In SQL Server Linked Server, it could indicate a few things (not limited to)– 1. SQL Server (and oracle net libraries) is not able to get the TNS alias from tnsnames.ora file.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 - 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 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 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 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 (TnsNa