Background:

Certain error codes denote problems with TNS connections (used to connect to EPM and InfoAccess databases). This document describes some of those error messages, their causes, and potential solutions to underlying problems.

Errors:

TNS-03505: Failed to resolve name

• When it appears: User runs 'tnsping' command to verify database connectivity.
• Cause: User mistypes name of TNS connection and/or TNS connection named or formatted incorrectly in tnsnames.ora file. Example: if tnsnames.ora contains a connection entry named 'DWHP' but user types 'DHWP' at the tnsping prompt, error will appear. Can also appear if tnsnames.ora does not exist.
• Solutions: Verify presence of tnsnames.ora file. Ensure the name of the connection typed at the tnsping prompt matches the name of the connection entry in tnsnames.ora.

TNS-12545: Connect failed because target host or object does not exist

• When it appears: User runs 'tnsping' command to verify database connectivity.
• Causes: Invalid hostname in tnsnames.ora and/or local networking issues.
• Solutions: Verify basic network connectivity on local machine. Verify that the

  Host =

  entry in tnsnames.ora contains a valid hostname. If database is behind a firewall, ensure WiscVPN connectivity.

ORA-01013: User requested cancel of current operation

• When it appears: User runs query against an Oracle database in any of a variety of applications (e.g. MS Access, DBeaver, SQL Developer).
• Causes: Can appear if user prematurely cancels an SQL operation over an ODBC connection. Can also indicate a connection timeout in the event of a long or malformed query.
• Solutions: If user is not cancelling connection intentionally, disable timeout on ODBC connection. User should check query/SQL operation for errors.

ORA-01254: TNS: could not resolve the connect identifier specified

• When it appears: User attempts to configure and connect to an Oracle database.
• Causes: Malformed (incorrect or improperly formatted) connection entry in tnsnames.ora
• Solutions: Run 'tnsping' to determine which of the above two TNS- errors is applicable. Work through the corresponding solution(s). Update your TNSnames.ora file as needed (see Adding, Editing, or Replacing Your TNSnames.ora File)

ORA-12514: TNS: Listener does not currently know of service requested

• When it appears: User attempts to configure and connect to an Oracle database.
• Causes: Malformed (incorrect or improperly formatted) connection entry in tnsnames.ora
• Solutions: Run 'tnsping' to determine which of the above two TNS- errors is applicable. Work through the corresponding solution(s). Update your TNSnames.ora file as needed (see Adding, Editing, or Replacing Your TNSnames.ora File)