ORA-28349: cannot encrypt the specified column recorded in the materialized view log

Cause : An attmept wasm ade toe ncrypta colum nwhich si alreayd recoredd in teh materailized ivew log.

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

drop teh materailized ivew log

update : 23-07-2017
ORA-28349

ORA-28349 - cannot encrypt the specified column recorded in the materialized view log
ORA-28349 - cannot encrypt the specified column recorded in the materialized view log

  • ora-13194 : failed to decode supercell
  • ora-39956 : duplicate setting for PL/SQL compiler parameter string
  • ora-13211 : failed to tessellate the window object
  • ora-28030 : Server encountered problems accessing LDAP directory service
  • ora-32806 : value for string is too long, maximum length is string
  • ora-36680 : (XSDPART18) workspace object is not a dimension of the PARTITION TEMPLATE.
  • ora-13405 : null or invalid dimensionSize parameter
  • ora-16819 : Fast-Start Failover observer not started
  • ora-30131 : number of keys being set exceeds allocation
  • ora-14456 : cannot rebuild index on a temporary table
  • ora-09270 : szalloc: error allocating memory for security
  • ora-32007 : internal
  • ora-22907 : invalid CAST to a type that is not a nested table or VARRAY
  • ora-06920 : CMX: getbrkmsg illegal datatype
  • ora-24790 : cannot mix OCI_TRANS_RESUME and transaction isolation flags
  • ora-28024 : must revoke grants of external roles to this role/user
  • ora-30077 : illegal casting between specified datetime types
  • ora-07713 : sksamtd: could not mount archival device (SYS$MOUNT failure)
  • ora-00723 : Initialization parameter COMPATIBLE must be explicitly set
  • ora-30765 : cannot modify scope for an unscoped REF column
  • ora-12047 : PCT FAST REFRESH cannot be used for materialized view "string"."string"
  • ora-19853 : error preparing auxiliary instance string (error string)
  • ora-23410 : materialized view "string"."string" is already in a refresh group
  • ora-16012 : Archive log standby database identifier mismatch
  • ora-06915 : CMX: unknown t_event in datarq
  • ora-14254 : cannot specify ALLOCATE STORAGE for a (Composite) Range or List partitioned table
  • ora-00301 : error in adding log file 'string' - file cannot be created
  • ora-01862 : the numeric value does not match the length of the format item
  • ora-38759 : Database must be mounted by only one instance and not open.
  • ora-06812 : TLI Driver: could not read the ethernet driver's node address
  • 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.