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 : 30-04-2017
ORA-12514

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-22604 : TDS handle already generated
  • ora-19674 : file string is already being backed up with proxy copy
  • ora-38746 : error occurred while restoring data block (file# string, block# string)
  • ora-06616 : LU6.2 Driver: Attach to LU failed
  • ora-10657 : Lob column to be shrunk does not exist
  • ora-27469 : %s is not a valid string attribute
  • ora-02452 : invalid HASHKEYS option value
  • ora-19809 : limit exceeded for recovery files
  • ora-22631 : attribute [string] is is not well-formed or does not match the type
  • ora-02750 : osnfsmmap: cannot open shared memory file ?/dbs/ftt_.dbf
  • ora-07224 : sfnfy: failed to obtain file size limit; errno = string.
  • ora-24085 : operation failed, queue string is invalid
  • ora-12950 : SYSTEM tablespace specified as default permanent tablespace
  • ora-27100 : shared memory realm already exists
  • ora-31513 : unsupported column type specified in change table
  • ora-02423 : schema name does not match schema authorization identifier
  • ora-25146 : EXTENT MANAGEMENT option already specified
  • ora-27142 : could not create new process
  • ora-01283 : Options specified is invalid
  • ora-32035 : unreferenced query name defined in WITH clause
  • ora-12461 : undefined level string for policy string
  • ora-30369 : maximum number of columns is 32
  • ora-25531 : MTTR specified is too small: string
  • ora-38101 : Invalid column in the INSERT VALUES Clause: string
  • ora-02071 : error initializing capabilities for remote database string
  • ora-33297 : (DBERR22) Analytic workspace string cannot be opened because it was last modified by an incompatible version of string.
  • ora-06258 : NETNTT: cannot allocate context area
  • ora-22338 : must specify CASCADE INCLUDING DATA when altering the final property
  • ora-07482 : snlmini: cannot create lock manager instance.
  • ora-07404 : sfareq: Timeout occurred waiting for request to complete.
  • 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.