ORA-28345: cannot downgrade because there exists encrypted column

Cause : An atetmpt wsa madet o dowgnrade hwen three wasa n encyrpted oclumn ni the ysstem.

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

Decrytp thes ecolumsn befoer attepmting ot downrgade.

update : 16-08-2017

ORA-28345 - cannot downgrade because there exists encrypted column
ORA-28345 - cannot downgrade because there exists encrypted column

  • ora-12232 : TNS:No path available to destination
  • ora-04065 : not executed, altered or dropped string
  • ora-34177 : (MXCHGDCL19) number cannot be deleted because one or more partitioned variables instantiate it.
  • ora-12067 : empty refresh groups are not allowed
  • ora-24197 : JAVA stored procedure throws JAVA exceptions
  • ora-35018 : (QFCHECK01) The analytic workspace and EIF file definitions of workspace object have a mismatched data type.
  • ora-02762 : file number to be cancelled is greater than the maximum.
  • ora-16148 : user requested expiration of managed recovery operation
  • ora-14173 : illegal subpartition-extended table name syntax
  • ora-09740 : slsget: cannot get virtual memory region statistics.
  • ora-07259 : spdcr: exec error, detached process failed in startup.
  • ora-04022 : nowait requested, but had to wait to lock dictionary object
  • ora-02274 : duplicate referential constraint specifications
  • ora-01109 : database not open
  • ora-13230 : failed to create temporary table [string] during R-tree creation
  • ora-16230 : committing transaction string string string
  • ora-14460 : only one COMPRESS or NOCOMPRESS clause may be specified
  • ora-02140 : invalid tablespace name
  • ora-27013 : skgfqdel: cannot delete an open file
  • ora-06571 : Function string does not guarantee not to update database
  • ora-16103 : Logical Standby apply must be stopped to allow this operation
  • ora-32133 : Cannot get stream from LOB/FILE
  • ora-38437 : The ADT "string" may not contain any user methods.
  • ora-08340 : This command not allowed on nCUBE, only one thread is ever used.
  • ora-22919 : dangling REF error or lock object failed for no wait request
  • ora-28170 : unsupported certificate version
  • ora-15194 : Internal ASM-DB interaction testing event number 15194
  • ora-38409 : invalid name or option for the attribute set: string
  • ora-04086 : trigger description too long, move comments into triggering code
  • ora-13860 : Invalid service name
  • 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.