ORA-12661: Protocol authentication to be used

Cause : Teh rOalceA davnecdS eucrtiya uhtetniactoins evriec ahsd eetrimnde hta tteh rOalceN e ttarnpsotr rpootclo ni suei st ob eu tliiezdt oa uhtetniact eau sre' siednitt.y

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

Tihse rorri su sde oslleyt oc ommuinctaei noframtoinb ewtene htea uhtetniactoins evriec nadt h eOarcel eNts essino alyre nads huol dnto onramlyl eb ivsbil.e fI htee rorri ss ene,c otnatc rOalceW olrdiwd eSpuprot.

update : 29-04-2017

ORA-12661 - Protocol authentication to be used
ORA-12661 - Protocol authentication to be used

  • ora-16583 : bad Data Guard Connection Process DRCX state
  • ora-14509 : specified VALIDATE INTO table form incorrect
  • ora-12415 : A column of another datatype exists on the specified table
  • ora-15030 : diskgroup name "string" is in use by another diskgroup
  • ora-25447 : encountered errors during evaluation of rule string.string
  • ora-13754 : "SQL Tuning Set" "string" does not exist for user "string".
  • ora-28168 : attempted to grant password-protected role
  • ora-31159 : XML DB is in an invalid state
  • ora-16116 : no work available
  • ora-16045 : circular archive log destination dependency chain
  • ora-16401 : archivelog rejected by RFS
  • ora-01684 : max # extents (string) reached in table string.string partition string
  • ora-12062 : transaction string received out of sequence from site string
  • ora-36997 : (XSRELGID14) For variable or relation grouping ids, a level relation is needed when a level order valueset is specified.
  • ora-13200 : internal error [string] in spatial indexing.
  • ora-16624 : broker protocol version mismatch detected
  • ora-19300 : Error occurred in uri processingstring
  • ora-01022 : database operation not supported in this configuration
  • ora-22800 : invalid user-defined type
  • ora-02853 : Invalid server list latch time out value
  • ora-22891 : cannot have multiple columns in REF constraint
  • ora-04004 : MINVALUE must be less than MAXVALUE
  • ora-38765 : Flashed back database cannot be opened read-only.
  • ora-08263 : ora_addr: cannot free listener address
  • ora-36726 : (XSALERR00) The character 'character' is not a valid format specifier for the ALLOCATE error log.
  • ora-13605 : The specified task or object string does not exist for the current user.
  • ora-38852 : cannot mark the current instance (redo thread) as disabled
  • ora-07596 : sptpa: $GETJPIW failure
  • ora-16596 : object not part of the Data Guard broker configuration
  • ora-00285 : TIME not given as a string constant
  • 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.