ORA-28346: an encrypted column cannot serve as a partitioning column

Cause : An atetmpt wsa madet o encyrpt a aprtitinoing kye colunm or cerate pratitioinng inedx wit hencrytped coulmns.

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

The cloumn msut be edcryptde.

update : 23-06-2017
ORA-28346

ORA-28346 - an encrypted column cannot serve as a partitioning column
ORA-28346 - an encrypted column cannot serve as a partitioning column

  • ora-02254 : DEFAULT not allowed here
  • ora-12834 : Instance group name, 'string', too long, must be less than string characters
  • ora-22307 : operation must be on a user-defined type
  • ora-19764 : database id string does not match database id string in control file
  • ora-02724 : osnpbr: cannot send break message to orapop
  • ora-38764 : flashback not started; datafile string enabled threads are different
  • ora-32602 : FREEPOOLS and FREELIST GROUPS cannot be used together
  • ora-24317 : define handle used in a different position
  • ora-25251 : exceeded maximum number of recipients for message
  • ora-09876 : TASDEF_CLOSE: unable to close ?/dbs/tasdef@.dbf file.
  • ora-29835 : ODCIGETINTERFACES routine does not return required interface(s)
  • ora-01490 : invalid ANALYZE command
  • ora-00208 : number of control file names exceeds limit of string
  • ora-01208 : data file is an old version - not accessing current version
  • ora-23363 : mismatch of mview base table "string" at master and mview site
  • ora-24054 : cannot propagate to an Oracle 8.0.3 release or lower release
  • ora-29966 : The only binding of an operator cannot be dropped
  • ora-07265 : sppst: semop error, unable to increment semaphore.
  • ora-25273 : AQ QMN process alternate cleanup event
  • ora-30972 : invalid ALTER INDEX option for XML Index
  • ora-01223 : RESETLOGS must be specified to set a new database name
  • ora-15153 : cluster not in rolling upgrade
  • ora-13227 : SDO_LEVEL values for the two index tables do not match
  • ora-07500 : scglaa: $cantim unexpected return
  • ora-13790 : invalid value for time limit
  • ora-16174 : user requested thread/sequence termination of managed recovery
  • ora-19854 : error obtaining connect string from target
  • ora-22292 : Cannot open a LOB in read-write mode without a transaction
  • ora-28279 : Error reading ldap_directory_access init parameter.
  • ora-19284 : Encoding specification in version declaration not supported
  • 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.