ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

Cause : The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a service name for a service (usually a database service) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

- Wait a moment and try to connect a second time. - Check which services are currently known by the listener by executing: lsnrctl services - Check that the SERVICE_NAME parameter in the connect descriptor of the net service name used specifies a service known by the listener. - If an easy connect naming connect identifier was used, check that the service name specified is a service known by the listener. - Check for an event in the listener.log file.

update : 21-08-2017

ORA-12514 - TNS:listener does not currently know of service requested in connect descriptor
ORA-12514 - TNS:listener does not currently know of service requested in connect descriptor

  • ora-12918 : Invalid tablespace type for default permanent tablespace
  • ora-24308 : illegal define position
  • ora-12926 : FORCE LOGGING option already specified
  • ora-08343 : srclose: failed to close a redo server connection
  • ora-09360 : Windows 3.1 Two-Task driver unable to allocate context area
  • ora-12047 : PCT FAST REFRESH cannot be used for materialized view "string"."string"
  • ora-01361 : global name mismatch
  • ora-01784 : RECOVERABLE cannot be specified with database media recovery disabled
  • ora-13157 : Oracle error ORAstring encountered while string
  • ora-16170 : Terminal recovery may have left the database in an inconsistent state
  • ora-24020 : Internal error in DBMS_AQ_IMPORT_INTERNAL, string
  • ora-37006 : (AWLISTALL04) number writers
  • ora-36632 : (XSDUNION01) The concat dimension workspace object is not currently defined as UNIQUE.
  • ora-28043 : invalid bind credentials for DB-OID connection
  • ora-14057 : partition "string": sum of PCTUSED and PCTFREE may not exceed 100
  • ora-29896 : Length of PARAMETER string longer than string characters
  • ora-16507 : unrecognized request identifier
  • ora-01310 : requested return type not supported by the lcr_mine function
  • ora-14612 : Duplicate lob segment name string for lob column string in template
  • ora-30028 : Automatic Undo Management event for NTP testing
  • ora-30444 : rewrite terminated by the sql analyzer
  • ora-13779 : invalid load option
  • ora-30176 : invalid format code used in the format string
  • ora-24404 : connection pool does not exist
  • ora-16785 : the database is not in ARCHIVELOG mode
  • ora-07703 : error in archive text: need '/' after device type
  • ora-38723 : Invalid SCN expression.
  • ora-06957 : No SID is currently available
  • ora-31022 : Element not found
  • ora-07240 : slemrd: seek error.
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.