ORA-12516: TNS:listener could not find available handler with matching protocol stack

Cause : Noen o fth eknwon nad vaaialbl esevric ehadnlesr fro teh gvienS ERIVCEN_AM Esuppor tth ecleints' portoocl tsac:k tarnsoprt ,sessio,n adn persetnatoin rpotcool.s

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

Chcek ot mkae usret ha tth esevric ehadnlesr (.eg.d isaptcehrs )fo rth egievn ESRVCIE_ANMEa rer egsiteerd iwtht hel isetne,r aer accepitngc onenctoins ,an dthta tehy rae rpoprelyc onifguerd ot spupotr teh dseirde portoocls.

update : 20-07-2017

ORA-12516 - TNS:listener could not find available handler with matching protocol stack
ORA-12516 - TNS:listener could not find available handler with matching protocol stack

  • ora-19692 : missing creation stamp on piece string
  • ora-00324 : log file 'string' translated name 'string' too long, string characters exceeds string limit
  • ora-26764 : invalid parameter "string" for local capture "string"
  • ora-01286 : start interval required
  • ora-10862 : resolve default queue owner to current user in enqueue/dequeue
  • ora-12354 : secondary object being dropped
  • ora-06302 : IPA: Cannot connect to remote host
  • ora-30946 : XML Schema Evolution warning: temporary tables not cleaned up
  • ora-01946 : DEFAULT TABLESPACE already specified
  • ora-27014 : skgfqpini: translation error while expanding SS_UDMPDIR
  • ora-02767 : Less than one request descriptor was allocated per server
  • ora-08104 : this index object string is being online built or rebuilt
  • ora-26761 : Standby Redo Logs not available for real time mining
  • ora-10948 : trace name context forever
  • ora-00081 : address range [string, string) is not readable
  • ora-15097 : cannot SHUTDOWN ASM instance with connected RDBMS instance
  • ora-38458 : invalid operation "string" for XPATH_FILTER_PARAMETERS
  • ora-25145 : allocation policy already specified
  • ora-25505 : the system is not in quiesced state
  • ora-34897 : (PPMONTHS01) Blank lines are not allowed in the MONTHNAMES option.
  • ora-27474 : cannot give both an argument name and an argument position
  • ora-30564 : Index maintainence clause not allowed for ADD partition to RANGE partitioned tables
  • ora-00152 : current session does not match requested session
  • ora-38439 : invalid operation "string"
  • ora-13703 : The snapshot pair [string, string] for database_id string and instance_id string are not found in the current repository.
  • ora-01200 : actual file size of string is smaller than correct size of string blocks
  • ora-31108 : Action failed as resource string is locked
  • ora-22615 : attribute is not a collection
  • ora-16092 : dependent archive log destination is not active
  • ora-15128 : ASM file name 'string' exceeds maximum length string
  • 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.