Database Server Error 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. If error persists, contact Worldwide Customer Support. ORA-12152: TNS:unable to send break message tns could not find connect identifier Cause: Unable to send break message. Connection probably disconnected. Action: Reestablish connection. If the error tns could not resolve identifier specified oracle is persistent, turn on tracing and reexecute the operation. ORA-12153: TNS:not connected Cause: Not currently connected to a remote host. Action: Reestablish database link ora 12154 connection. ORA-12154: TNS:could not resolve the connect identifier specified Cause: 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
Error While Trying To Retrieve Text For Error Ora-12154
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: - 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 ora 12154 error in oracle 11g 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 specifying a fully qualified net service name or a full LDAP DN as the connect identifier - If you are using easy connect naming: - Verify that "EZCONNECT" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA). - Make sure the host, port and service name specified are correct. - Try enclosing the connect identifier in quote marks. See the Oracle Net Services Administrators Guide or the Oracle operating system specific g
server but either failed to contact the server or did not find a matching service name on that server. TNS or 'Transparent Network Substrate' is a transport protocol that allows Oracle sessions to communicate across a network. DB Server <=> Listener <=> Network connection ora 12154 error solution <=> Client (SQL*Net) <=> Application. In the path above, tnsping can be used to test the
Ora 12154 Tns Could Not Resolve Service Name
parts in bold and should be the first troubleshooting step. If tnsping fails, that generally indicates a problem finding the server connection - if
Ora 12154 Tns No Listener
TNSNAMES specifies an IP address, is it correct?, if it's a DNS name, is that resolving correctly? (try switching for an IP address to find out.) If tnsping succeeds, that can indicate a problem with the client configuration but could https://docs.oracle.com/cd/B19306_01/server.102/b14219/net12150.htm equally be that the connection is working as far as the listener but the database is down. Try comparing with another PC - if multiple machines are failing that usually points towards a server issue. Ora-12154 can be a tricky problem to nail down because there are many possible causes, try making a connection directly on the server or completely regenerate the TNSNAMES.ORA file on the client. ORA-12154 description: Cause: A connection to a database or other service was requested using http://ss64.com/ora/syntax-ora-12154.html 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: 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 can make it unusable. 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 specifying a fully qualified net service name or a full LDAP DN as the connect identifier Easy connect naming: - Verify that "EZCO
BI Publisher Primavera Contractor Primavera Risk Analysis Primavera Earned Value Management Primavera Portfolio Management Primavera Installation & Technical Support Product Sales F.A.Q CPM Project Management Tools Primavera Self-Support Tool P6 http://www.cpmsolutions.ca/bad-public-user-name-or-password-database-server-error-ora-12154-tnscould-not-resolve-connect-identi/ EPPM Administration Tool for Windows Client Application Cloud Publisher Project Tracker – S-Curve Tool Training Classroom Courses CPM101 - Project Management Fundamentals in Primavera P6 Web Access CPM102 - Project Management Fundamentals in Primavera P6 Windows Professional CPM106 - Advanced Topics in Primavera P6 Windows Professional CPM106A - Administration for Primavera P6 (EPPM or PPM) STO300 - Advanced Planning & ora 12154 Scheduling in Primavera P6 Windows Professional for STO Events Calendar Cancellation Policy Online Training eCPM101 Online Training for Primavera P6 EPPM eCPM102 Online Training for Primavera P6 Professional Online Training F.A.Q Training Options Virtual Training On-Site Training One-on-One Training Course Request Form Services Consulting Technical Support Contracting Hosting Our Portfolio Resources Articles and Downloads STO Navigator Articles e-Newsletter Archives Useful Links tns could not Write For Us About Us Contact Us Training Venues Accommodations Careers My Account Cart Resources News, Articles, Tutorials and More Bad public user name or password (Database server error: ORA-12154: TNS: could not resolve the connect identifier specified) April 10, 2013Jim LiNo CommentsInstallation/Admin EDIT: Oracle has addressed this issue in a previously released service pack. A user has also commented on an easier fix below. "When installing the standalone version of Primavera 6 v7 on Windows 64-bit OS, you can change the default installation directories to a path that does not include “program files (x86)” in it. The brackets around x86 are the problem with the 10g XE install. Just rename the path to “C:\Primavera” for the install and “C:\Primavera\Primavera Common” for the common files. It will work perfect after that! No need for 11g or instant client or modification of the tnsname.ora file. Regards, Clayton Richards" The fact: you installed Primavera P6 V7.0 in a standalone machine with Windows 7 64 bit operating system, and you are configuring the Oracle database connection for Primavera, then you got the error bel