Database Error Code 12154 Ora 12154
Contents |
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. database link ora 12154 If error persists, contact Worldwide Customer Support. ORA-12152: TNS:unable to send break
Ora 12154 Error In Oracle 11g
message Cause: Unable to send break message. Connection probably disconnected. Action: Reestablish connection. If the error is persistent, ora 12154 error solution turn on tracing and reexecute the operation. ORA-12153: TNS:not connected Cause: Not currently connected to a remote host. Action: Reestablish connection. ORA-12154: TNS:could not resolve the connect identifier specified Cause: error while trying to retrieve text for error ora-12154 A connection to a database or other service was requested using a connect identifier, and the connect identifier specified could not be resolved into a connect descriptor using one of the naming methods configured. For example, if the type of connect identifier used was a net service name then the net service name could not be found in a naming
Ora 12154 Tns Could Not Resolve Service Name
method repository, or the repository could not be located or reached. Action: - If you are using local naming (TNSNAMES.ORA file): - Make sure that "TNSNAMES" is listed as one of the values of the NAMES.DIRECTORY_PATH parameter in the Oracle Net profile (SQLNET.ORA) - Verify that a TNSNAMES.ORA file exists and is in the proper directory and is accessible. - Check that the net service name used as the connect identifier exists in the TNSNAMES.ORA file. - Make sure there are no syntax errors anywhere in the TNSNAMES.ORA file. Look for unmatched parentheses or stray characters. Errors in a TNSNAMES.ORA file may make it unusable. - If you are using directory naming: - Verify that "LDAP" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA). - Verify that the LDAP directory server is up and that it is accessible. - Verify that the net service name or database name used as the connect identifier is configured in the directory. - Verify that the default context being used is correct by s
SQL TuningSecurityOracle UNIXOracle LinuxMonitoringRemote supportRemote plansRemote servicesApplication Server ApplicationsOracle FormsOracle PortalApp UpgradesSQL ServerOracle ConceptsSoftware SupportRemote Support Development Implementation Consulting StaffConsulting PricesHelp Wanted! Oracle PostersOracle Books Oracle Scripts Ion Excel-DB Don Burleson Blog
ora 12154 tns no listener ORA-12154: TNS could not resolve service name tips ora 12154 tns could not resolve service name oracle 9i Question: I need help with this error: ORA-12154: TNS: could not resolve service name.Answer: The ORA-12154 is a very common error,Ora 12154 Tns Could Not Resolve The Connect Identifier Specified Xe
always related to your local copy of the tnsnames.ora file, your listener configuration and your database name aliases. Make sure that your listener is listening for the same service name that you are using. Your https://docs.oracle.com/cd/B19306_01/server.102/b14219/net12150.htm service name might have an alias, so check for global (world) entries and local entries. Check: $ORACLE_HOME/network/admin/tnsnames.ora Check your global_name setting with this SQL: select * from global_name; The query value should match your init.ora parms for db_name and db_domain, You can change the global_name with an ALTER DATABASE command, as follows: alter database rename global_name to xxx; Also see these notes on configuring your tnsnames.ora file and troubleshooting network http://www.dba-oracle.com/t_ora_12154_tns_resolve_service_name.htm errors. Rampant author Steve Callan notes this on the ORA-12154 error: "One of the most common errors related to improper configuration is the "ORA-12154: TNS: could not resolve service name" error. It is not uncommon for new users of Oracle to spend hours upon hours trying to figure out what their mistake is when ORA-12154 appears." The oerr utility notes this on the ORA-12154 error:: $oerr ora 12154 ORA-12154: TNS:could not resolve the connect identifier specifiedCause: A connection to a database or other service was requested using a connect identifier, and the connect identifier specified could not be resolved into a connect descriptor using one of the naming methods configured. For example, if the type of connect identifier used was a net service name then the net service name could not be found in a naming method repository, or the repository could not be located or reached. Action: The following actions may be appropriate: If you are using local naming (tnsnames.ora file): Make sure that TNSNAMES is listed as one of the values of the names.directory_path parameter in the sqlnet.ora Oracle Net profile. Verify that a tnsnames.ora file exists and is in the proper directory and is accessible. Check that the net service name used as the connect identifie
open a published workbook that is connected to an Oracle database, where http://kb.tableau.com/articles/issue/error-ora-12154-connecting-to-oracle-not-using-tnsnames-ora-file all three connection parameters (Server, Service, and Port) were configured during the initial connection, the following error might occur: Oracle database error 12154: ORA-12154: TNS:could not resolve the connect identifier specified When you try to connect to the same Oracle database using the service name from TNSNames.ora file in the Server parameter and ora 12154 leaving the other two parameters blank, the connection is successful. EnvironmentTableau ServerTableau DesktopOracle ResolutionOption 1: Work with your Oracle database administrator to allow the HOSTNAME connection type for the Oracle client on the computer running Tableau Desktop or Tableau Server. Option 2: The following workaround may allow the HOSTNAME connection type: On the computer running ora 12154 tns Tableau Desktop or Tableau Server, find the sqlnet.ora file. The folder containing the file should be specified in the TNS_ADMIN variable and should also contain the TNSNames.ora file. For more information, see "Set the TNS_Admin environment variable" in Setting an Oracle Connection to Use TNSNames.ora and Sqlnet.ora at Oracle FAQ's. Note: If this folder does not contain a sqlnet.ora file, create a sqlnet.ora file.In the sqlnet.ora file, amend the NAMES.DIRECTORY_PATH line to say the following or add the following line to the sqlnet.ora file: NAMES.DIRECTORY_PATH= (LDAP, TNSNAMES, HOSTNAME) Note: If this issue occurs in a Tableau Server distributed environment, perform the above steps on all computers in the Tableau Server installation. CauseThe sqlnet.ora file is not allowing the Oracle driver to look for the database using all three connection parameters. Did this article resolve the issue? Thank you for providing your feedback on the effectiveness of the article. Click here to return to our Support page. Open new Case Open a new cas