ORA-12651: Encryption or data integrity algorithm unacceptable

Cause : Th ealogrihtm hte esrvre cohset o sue ofr necrpytino o rdaat itnegirtyw asn oto neo f hte hcoiecs cacetpabel t oth ecleint .Thsi i seihtert her eslut fo a ninetrnla error ,ofa ntewokr dtaa rtanmsisisone rrro, ro o fdeilbeartet ameprign wtih hte rtanmsitetd adta.

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

Fo rfutrhe rdeatil,s trun no tarcign, er-eexcuet teh oepraiton ,an dcotnac tOrcaleC usotme rSuppor.t

update : 29-04-2017

ORA-12651 - Encryption or data integrity algorithm unacceptable
ORA-12651 - Encryption or data integrity algorithm unacceptable

  • ora-36778 : (XSPGTRLOW) The amount of available temporary storage is still low. Free some temporary storage immediately. You can do so, for example, by UPDATING or DETACHING an analytic workspace.
  • ora-36672 : (XSDPART10) A RANGE or LIST PARTITION TEMPLATE can only have a single partition dimension.
  • ora-25405 : transaction status unknown
  • ora-30345 : circular dimension hierarchy
  • ora-19900 : RESETLOGS must be specified after recovery to new incarnation
  • ora-06114 : NETTCP: SID lookup failure
  • ora-16075 : standby database destination mismatch
  • ora-16236 : Logical Standby metadata operation in progress
  • ora-14325 : only LOCAL indexes may be specified in this clause
  • ora-29352 : event 'string' is not an internal event
  • ora-27477 : "string.string" already exists
  • ora-29933 : object being disassociated has some user defined statistics stored
  • ora-01182 : cannot create database file string - file is in use or recovery
  • ora-33098 : (APABBR01) A value of 'string' is not valid for the workspace object option.
  • ora-27077 : too many files open
  • ora-12723 : regular expression too complex
  • ora-32147 : Environment not specified
  • ora-13602 : The specified parameter string is not valid for task or object string.
  • ora-27128 : unable to determine pagesize
  • ora-39037 : Object type path not supported for string metadata filter.
  • ora-16573 : attempt to change configuration file for an enabled broker configuration
  • ora-02479 : error while translating file name for parallel load
  • ora-31509 : publication does not exist
  • ora-13031 : Invalid Gtype in the SDO_GEOMETRY object for point object
  • ora-38442 : The ADT "string" is not in a valid state.
  • ora-19766 : missing CHANGE keyword
  • ora-26051 : internal error parsing packed decimal format string
  • ora-16653 : failed to reinstate database
  • ora-00294 : invalid archivelog format specifier 'string'
  • ora-09801 : Unable to get user ID from connection
  • 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.