ORA-28366: invalid database encryption operation

Cause : The command for database encryption contained improper spelling or syntax.

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

Verify the spelling and syntax and execute the command again.

update : 19-08-2017
ORA-28366

ORA-28366 - invalid database encryption operation
ORA-28366 - invalid database encryption operation

  • ora-36210 : (XSAGOP05R) In AGGMAP workspace object, you can only specify the REMOPERATOR string with the PROPORTIONAL, EVEN, or HEVEN operators, not string.
  • ora-16079 : standby archival not enabled
  • ora-14522 : Partition-level default tablespace string block size [string] for string string does not match existing string block size [string]
  • ora-02347 : cannot grant privileges on columns of an object table
  • ora-39148 : unable to import data into pre-existing queue table string. Table_exists_action of string being ignored for this table
  • ora-01984 : invalid auditing option for procedures/packages/functions
  • ora-30552 : The package/procedure/function cannot be changed
  • ora-31488 : cannot support change set string in this configuration
  • ora-32803 : value for string cannot be altered
  • ora-00960 : ambiguous column naming in select list
  • ora-00271 : there are no logs that need archiving
  • ora-24272 : initialization value must be either F or T
  • ora-01650 : unable to extend rollback segment string by string in tablespace string
  • ora-12469 : no user levels found for user string and policy string
  • ora-08194 : Flashback Table operation is not allowed on materialized views
  • ora-36184 : (XSAGGR10) You do not have sufficient permissions for the variable workspace object.
  • ora-13403 : invalid rasterDataTable specification: string
  • ora-19361 : ONLINE option not allowed with this type of index
  • ora-13376 : invalid type name specified for layer_gtype parameter
  • ora-07680 : sou2os: another call to Oracle currently executing
  • ora-38705 : Expected block size string does not match string in log header.
  • ora-28275 : Multiple mappings for user nickname to LDAP distinguished name exist.
  • ora-12504 : TNS:listener was not given the SID in CONNECT_DATA
  • ora-22161 : type code [string] is not valid
  • ora-14267 : cannot specify PARALLEL clause when adding a (Composite) Range partition
  • ora-21526 : initialization failed
  • ora-31215 : DBMS_LDAP: PL/SQL - Invalid LDAP mod value.
  • ora-36924 : (XSVPMVTOPART05) workspace object is not in a COMPOSITE.
  • ora-24806 : LOB form mismatch
  • ora-00371 : not enough shared pool memory, should be atleast string bytes
  • 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.