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 : 24-06-2017

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

  • ora-28546 : connection initialization failed, probable Net8 admin error
  • ora-12922 : concurrent ALTER DATABASE [NO] FORCE LOGGING command is running
  • ora-37157 : MDX syntax error was found in MDX query string but error text was missing
  • ora-22862 : specified object identifier doesn't match existing object identifier
  • ora-02031 : no ROWID for fixed tables or for external-organized tables
  • ora-09818 : Number is too large
  • ora-06743 : TLI Driver: cannot alloc t_bind
  • ora-16520 : unable to allocate resource id
  • ora-28111 : insufficient privilege to evaluate policy predicate
  • ora-01113 : file string needs media recovery
  • ora-16714 : the value of property string is inconsistent with the database setting
  • ora-36700 : (XSRELTBL04) Dimension workspace object cannot be qualified more than once.
  • ora-24908 : invalid recipient presentation attribute
  • ora-03112 : a server linked as single-task cannot use SQL*Net
  • ora-07581 : spstp: cannot derive SID from unexpected process name
  • ora-30376 : prevent sharing of a parsed query of an explain rewrite session
  • ora-01644 : tablespace 'string' is already read only
  • ora-27019 : tape filename length exceeds limit (SBTOPMXF)
  • ora-15076 : Emulating I/O errors on the OSM disk
  • ora-23616 : Failure in executing block string for script string
  • ora-12696 : Double Encryption Turned On, login disallowed
  • ora-37023 : (XSMLTUPD01) Object workspace object cannot be updated without dimension workspace object.
  • ora-39951 : incomplete values specified for PL/SQL warning settings
  • ora-26672 : timeout occurred while stopping STREAMS process string
  • ora-09702 : sem_acquire: cannot acquire latch semaphore
  • ora-38420 : invalid stored attribute sub-expression: string
  • ora-39132 : object type "string"."string" already exists with different hashcode
  • ora-16747 : logical standby database guard could not be turned on
  • ora-19753 : error writing to change tracking file
  • ora-21710 : argument is expecting a valid memory address of an object
  • 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.