ORA-12648: Encryption or data integrity algorithm list empty

Cause : An Oracle Advanced Security list-of-algorithms parameter was empty, e.g. "()".

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

Change the list to contain the name of at least one installed algorithm, or remove the list entirely if every installed algorithm is acceptable.

update : 24-07-2017

ORA-12648 - Encryption or data integrity algorithm list empty
ORA-12648 - Encryption or data integrity algorithm list empty

  • ora-00293 : control file out of sync with redo log
  • ora-38442 : The ADT "string" is not in a valid state.
  • ora-31422 : owner schema string does not exist
  • ora-16508 : channel handle not initialized
  • ora-02853 : Invalid server list latch time out value
  • ora-29252 : collection does not contain elements at index locations in call to dbms_sql.bind_array
  • ora-00225 : expected size string of control file differs from actual size string
  • ora-37023 : (XSMLTUPD01) Object workspace object cannot be updated without dimension workspace object.
  • ora-29342 : user string does not exist in the database
  • ora-01983 : invalid auditing option for DEFAULT
  • ora-39126 : Worker unexpected fatal error in string [string] string
  • ora-08323 : scnmin: close of bias lock failed
  • ora-30953 : XML minoccurs value (string) violated
  • ora-06810 : TLI Driver: could not set the IPX ethernet SAP at init
  • ora-00051 : timeout occurred while waiting for a resource
  • ora-38505 : invalid default value for the attribute
  • ora-15182 : ASMLIB [string] version mismatch, ORACLE version [string]
  • ora-24396 : invalid attribute set in server handle
  • ora-32613 : not a MODEL cell
  • ora-03261 : the tablespace string has only one file
  • ora-06602 : LU6.2 Driver: Error allocating context area
  • ora-23474 : definition of "string"."string" has changed since generation of replication support
  • ora-33911 : (MAKEDCL29) You cannot define a string in analytic workspace string because it has not been upgraded to version string.
  • ora-36168 : (XSMXAGGR10) COUNTVAR variable workspace object must have the same dimensionality as workspace object
  • ora-36162 : (XSMXAGGR05) COUNTVAR variable workspace object must be of type INTEGER, not string.
  • ora-29819 : cannot associate default values with columns
  • ora-02314 : illegal use of type constructor
  • ora-04068 : existing state of packagesstringstringstring has been discarded
  • ora-15082 : ASM failed to communicate with database instance
  • ora-16628 : the broker protection mode is inconsistent with the database setting
  • 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.