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 : 17-08-2017

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

  • ora-23319 : parameter value string is not appropriate
  • ora-32550 : Replacement occured despite hint to the contrary
  • ora-01122 : database file string failed verification check
  • ora-03240 : User's temporary tablespace same as tablespace being migrated
  • ora-01605 : missing numbers in clause "string" of string
  • ora-25467 : table alias not specified
  • ora-32831 : timed out trying to acquire administration lock
  • ora-09241 : smsalo: error allocating SGA memory
  • ora-06559 : wrong datatype requested, string, actual datatype is string
  • ora-07418 : sfareq: Database writer got error in timing function.
  • ora-30103 : 'string' contains an illegal integer radix for 'string'
  • ora-32503 : Mapping SGA from file failed
  • ora-38951 : Target platform string not cross platform compliant
  • ora-00328 : archived log ends at change string, need later change string
  • ora-24394 : invalid mode for destroying connection pool
  • ora-24334 : no descriptor for this position
  • ora-07716 : sksachk: invalid device specification for ARCHIVE
  • ora-31112 : fail to string for string port using xdb configuration
  • ora-19720 : Error occurred when converting an OCI number into an SCN
  • ora-31070 : Invalid database user ID string
  • ora-38492 : invalid ALTER INDEX parameters clause "string"
  • ora-23470 : invalid status
  • ora-30991 : cannot use DOM to add special attribute to schema-based parent
  • ora-36767 : (XSAGGCNTMOVE05) workspace object cannot be used as an AGGCOUNT while there are permissions applied to it.
  • ora-32055 : invalid file type
  • ora-25123 : Too many components specified in the name.
  • ora-09915 : Password encryption failed.
  • ora-02287 : sequence number not allowed here
  • ora-08238 : smsfre: cannot detach from SGA
  • ora-16088 : archive log has not been completely archived
  • 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.