Home > not resolve > ociserverattach error 12154

Ociserverattach Error 12154

Oracle database via the Oracle run-time client. Technote (troubleshooting) Problem(Abstract) DataStage job ociserverattach example fails with error ORA-12154 when accessing an Oracle database via the

Ociserverattach Failed With Ora-12154

Oracle run-time client. The following are typical errors, but multiple variations exist: Error while trying ora-12154: tns:could not resolve the connect identifier specified to retrieve text for error ORA-12154 APT_OraReadOperator: connect failed. ORA-12154: TNS:could not resolve the connect identifier. ORA-12154: TNS:could not resolve service name Resolving the problem Error

Ora-12154 Tns Could Not Resolve Service Name

while trying to retrieve text for error ORA-12154 The above error means that not only did the connection to Oracle Database fail, but that Oracle was unable to retrieve the text of error message ORA-12154. This usually indicates that either the DataStage userid running the job does not have read access ora-12154 tns could not resolve the connect identifier specified windows 7 to the Oracle run-time client files, or that the environment variable ORACLE_HOME is not defined. ORA-12154: TNS:could not resolve the connect identifier. ORA-12154: TNS:could not resolve service name The above 2 errors indicate that the connection identifier or service name specified in the DataStage job (or in the ORACLE_SID environment variable or ODBC definition) was not known to either the Oracle client or the Oracle server. The connection/service identifiers known to the Oracle run-time client are defined in the tnsnames.ora file, $ORACLE_HOME/network/admin/tnsnames.ora Verify that the identifier specified for the failing Oracle connection has been defined in tnsnames.ora. If it is correctly defined, then next verify that the ORACLE_HOME environment variable is correctly defined, and that tnsnames.ora file has correct read permissions. If the above items are configured correctly, also check the listener.log on Oracle server to confirm that the service id (or the database it maps to) are known to the Oracle server

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 from the BI Server to

Error While Trying To Retrieve Text For Error Ora-12154

an Oracle database and the Oracle client returned an error. Distilling it down gives us

Ora-12154 Tns Could Not Resolve Service Name Oracle 11g

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 tns-03505 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 updated the connection pool, or connection pools You've got the correct http://www.ibm.com/support/docview.wss?uid=swg21408097 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 check all of them!). In the connection pool check the Data Source Name and make sure https://rnm1978.wordpress.com/2009/10/22/troubleshooting-obiee-and-ora-12154-tnscould-not-resolve-the-connect-identifier/ 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 in your Oracle Client so that you can see a bit more of what is going on. Add this to your $TNS_NAMES/sqlnet.ora file: trace_level_client = 10 trace_unique_client = on trace_file_client = sqlnet.trc trace_

connect identifier specified View next topic View previous topic Add To Favorites This topic has been marked "Resolved." This topic is not resolved, but there is a WORKAROUND. Post new topic   Reply to topic    DSXchange Forum Index » IBM® DataStage Enterprise Edition (Formerly Parallel Extender/PX) Author Message kishorenvkb Participant Joined: 24 Dec http://66.34.129.47/viewtopic.php?p=458910&sid=6b415d901576d140e416c8829aac37a7 2007 Posts: 54 Points: 419 Posted: Wed Oct 29, 2014 4:54 pm Reply with quote    Back to top     DataStage Release: 8x Job Type: Parallel OS: Unix Additional info: CC_OraConnection::verifyConnection Hello Gurus, I am moving from http://www.nntp.perl.org/group/perl.dbi.users/2007/12/msg32329.html one DB to another DB and I am using environment variables for server,user,password and schema. Admin updated the tnsnames.ora with the new connection. Updated the environment variables with new DB details. When I open a job and do View not resolve Data, the connector is able to connect to the new DB and is giving the desired results. But, when I compile the job and re-run the job in its entirety, I am getting the error: ConfigLvl_Ora_Load,1: [IIS-CONN-ORA-001004] The connector could not establish connection to Oracle server TEBDB01. Method: OCIServerAttach, Error code: 12,154, Error message ORA-12154: TNS:could not resolve the connect identifier specified. (CC_OraConnection::verifyConnection, file CC_OraConnection.cpp, line 4,404) Please assist. View user's profile  Send private message     PaulVL could not resolve Group memberships:Premium Members Joined: 17 Dec 2010 Posts: 960 Points: 6464 Posted: Wed Oct 29, 2014 5:07 pm Reply with quote    Back to top     Are you in a grid/cluster environment? If so, do your compute nodes also have that tns update? View user's profile  Send private message     Rate this response: 0 1 2 3 4 5 Not yet rated chulett since January 2006 Group memberships:Premium Members, Inner Circle, Server to Parallel Transition Group Joined: 12 Nov 2002 Posts: 41434 Location: Denver, CO Points: 212393 Posted: Wed Oct 29, 2014 5:08 pm Reply with quote    Back to top     So what's different between your environment and the environment of the user that runs the job? ORACLE_HOME perhaps? TNS_ADMIN? Something is. _________________-craig She got the which of the what-she-did, hid the bell with a blot, she did, But she fell in love with a hominid. Where is the which of the what-she-did? View user's profile  Send private message     Rate this response: 0 1 2 3 4 5 Not yet rated kishorenvkb Participant Joined: 24 Dec 2007 Posts: 54 Points: 419 Posted: Wed Oct 29, 2014 5:47 pm Reply with quote    Back to top     It is in the same environment. Me as the developer trying to do both. "View Data" worked. Run the job failed. View user's profile  Send privat

connect identifier specified Message ID: 8E3D502A002DA04FADBDED4CB4D94D3A04A916CF@phxmail02.phx.ndchealth.com Hello All, I am confused as to why I am getting this error message. I am trying to connect to two different Oracle instances within one program run. The two Oracle instances are different in versions. inst1 is 9.2 while inst2 is 10.2. I am able to connect to the first instance without problems, but the instance yields "ORA-12154" error. However, when I reverse the connection order by connecting the inst2 with 10.2 version first, then connecting to the inst1 with 9.2 version, there is no error. I hope someone can shed some lite. Here is the code: #!/usr/bin/perl use DBI; $ENV{'ORACLE_HOME'} = "/opt/app/oracle/product/9.2"; $ENV{'PATH'} = "/opt/app/oracle/product/9.2/bin:/usr/ccs/bin:/opt/studio9/SUNWspro/bin: /opt/app/oracle/product/10.2/bin:/opt/CA/Shar edComponents/dmscript/bin:/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/lo cal/bin:/opt/app/oracle/product/8.1.7.4/bin:/usr/local/bin:/ usr/local/apps/common/devl/bin:/usr/lbin:/usr/ccs/bin:/usr/xpg4/bin:/opt /pkware:/opt/RICHPse/bin:/opt/RICHPse/examples:/opt/sas82:/o pt/sas82/sasexe:/opt/Navisphere/bin:/opt/fileport/bin:/opt/syncsort/bin: /usr/bin:/usr/openwin/bin:/opt/SUNWspro/bin:/opt/mfcobol/cob ol/bin:/opt/starsql/bin:/opt/uni/bin:/opt/uni/scripts:/etc:/opt/emc/EMCp ower/bin/sparcv9:/etc/emc/bin:/usr/local/nz/bin/:."; my $dbh_inst1 = DBI->connect("dbi:Oracle:inst1", "schema", "password", { RaiseError => 1, PrintError => 1}); $ENV{'ORACLE_HOME'} = "/opt/app/oracle/product/10.2"; $ENV{'PATH'} = "/opt/app/oracle/product/10.2/bin:/opt/app/oracle/product/9.2/bin:/usr/c cs/bin:/opt/studio9/SUNWspro/bin:/opt/CA/Shar edComponents/dmscript/bin:/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/lo cal/bin:/opt/app/oracle/product/8.1.7.4/bin:/usr/local/bin:/ usr/local/apps/common/devl/bin:/usr/lbin:/usr/ccs/bin:/usr/xpg4/bin:/opt /pkware:/opt/RICHPse/bin:/opt/RICHPse/examples:/opt/sas82:/o pt/sas82/sasexe:/opt/Navisphere/bin:/opt/fileport/bin:/opt/syncsort/bin: /usr/bin:/usr/openwin/bin:/opt/SUNWspro/bin:/opt/mfcobol/cob ol/bin:/opt/starsql/bin:/opt/uni/bin:/opt/uni/scripts:/etc:/opt/emc/EMCp ower/bin/sparcv9:/etc/emc/bin:/usr/local/nz/bin/:."; my $dbh_inst2 = DBI->connect("dbi:Oracle:i

 

Related content

could not resolve placeholder spring error

could not resolve placeholder spring error p here for a quick spring could not resolve placeholder in string value overview of the site Help Center Detailed answers to any questions spring could not resolve placeholder default value you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Spring Cannot Resolve Placeholder Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a Could Not Resolve Placeholder Jdbc Driverclassname

ora-12154 error in initializing provider

Ora- Error In Initializing Provider p up Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home Data Warehousing Integration error ora- tns could not resolve the connect identifier specified Services ORA- Error when attempting to configure ORA- Error when attempting to Ora- Tns Could Not Resolve The Connect Identifier Specified Windows configure Oracle OLE DB COnnection Rate Topic Display Mode Topic Options Author Message Welsh CorgiWelsh Corgi Posted Thursday July ora- tns could not resolve service name PM SSCertifiable Group General Forum Members Last Login Monday October AM Points Visits It has been three years since

ora-12154 error in ssis

Ora- Error In Ssis p HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by Error Ora- Tns could Not Resolve The Connect Identifier Specified SSIS Can't connect to Oracle SQL Server SQL Server Integration ora- tns could not resolve the connect identifier specified windows Services Question Sign in to vote I have a -Vista machine I am using Ora- Tns Could Not Resolve Service Name SQL Server R I have created a SSIS project Under the Connection Manager I am trying to connect to a remote Oracle server

oracle support a server connection error occurred

Oracle Support A Server Connection Error Occurred p TNS received bad packet type from network layer Cause Internal error Action Not normally visible to the user For further details turn on tracing and reexecute the operation If error persists contact Worldwide Customer Support ORA- TNS unable to send ora- tns could not resolve the connect identifier specified break message Cause Unable to send break message Connection probably disconnected Action Reestablish connection If ora- tns could not resolve the connect identifier specified windows the error is persistent turn on tracing and reexecute the operation ORA- TNS not connected Cause Not currently

ora-12514 tns listener cannot resolve service name error

Ora- Tns Listener Cannot Resolve Service Name Error p TNS received bad packet type from network layer Cause Internal error Action Not normally visible to the user For further details turn on tracing and reexecute the operation If error persists contact Worldwide Customer Support ORA- TNS unable to send break message Cause Unable to ora- tns could not resolve service name send break message Connection probably disconnected Action Reestablish connection If the error is persistent turn Ora- Tns Could Not Resolve The Connect Identifier Specified Windows on tracing and reexecute the operation ORA- TNS not connected Cause Not currently connected