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 : 27-06-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-02257 : maximum number of columns exceeded
  • ora-13344 : an arcpolygon geometry has fewer than five coordinates
  • ora-30016 : undo tablespace 'string' is already in use by this instance
  • ora-32344 : cannot create a secondary materialized view with synonym as base table
  • ora-01251 : Unknown File Header Version read for file number string
  • ora-19276 : XP0005 - XPath step specifies an invalid element/attribute name: (string)
  • ora-14003 : GLOBAL clause contradicts previosly specified LOCAL clause
  • ora-40282 : invalid cost matrix
  • ora-12476 : least upper bound resulted in an invalid OS label
  • ora-38773 : cannot add data file 'string' - file already part of database
  • ora-38952 : Source database not 10.0.0.0 compatible
  • ora-12434 : invalid audit type: string
  • ora-09363 : Windows 3.1 Two-Task driver invalid context area
  • ora-01561 : failed to remove all objects in the tablespace specified
  • ora-02450 : Invalid hash option - missing keyword IS
  • ora-24034 : application string is already a subscriber for queue string
  • ora-28007 : the password cannot be reused
  • ora-16588 : no more internal buffers
  • ora-29383 : all leaves of top-plan string must be consumer groups
  • ora-01592 : error converting Version 7 rollback segment (string) to Oracle 8 format
  • ora-36976 : (XSRELGID00) The format of the GROUPINGID command is: GROUPINGID [relation1] INTO {variable | relation2 | surrogate} [USING levelrelation] [INHIERARCHY {inhvariable | valueset}] [LEVELORDER levelordervs] The source relation can be omitted only when using both surrogate gid and level order valueset.
  • ora-26519 : no memory available to allocate
  • ora-14064 : Index with Unusable partition exists on unique/primary constraint key
  • ora-01645 : previous attempt to make read write is half complete
  • ora-07401 : sptrap: cannot restore user exception handlers.
  • ora-39102 : Timeout before master process string finished initialization. Master error:
  • ora-15042 : ASM disk "string" is missing
  • ora-06602 : LU6.2 Driver: Error allocating context area
  • ora-38753 : Cannot flashback data file string; no flashback log data.
  • ora-01346 : LogMiner processed redo beyond specified reset log scn
  • 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.