ORA-28602: statement not permitted on tables containing bitmap indexes

Cause : table has bitmap indexes and user is minimizing or nominimizing records_per_block

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

drop all bitmap indexes before changing records_per_block

update : 26-06-2017
ORA-28602

ORA-28602 - statement not permitted on tables containing bitmap indexes
ORA-28602 - statement not permitted on tables containing bitmap indexes

  • ora-29339 : tablespace block size string does not match configured block sizes
  • ora-00302 : limit of string logs exceeded
  • ora-31073 : Resource not retrieved using path name
  • ora-32020 : SID=* clause needed to modify this parameter
  • ora-25959 : join index must be of the bitmap type
  • ora-16012 : Archive log standby database identifier mismatch
  • ora-00380 : cannot specify db_stringk_cache_size since stringK is the standard block size
  • ora-24039 : Queue string not created in queue table for multiple consumers
  • ora-37145 : (XSTTS_PLAT) Cannot transport analytic workspace across platforms.
  • ora-13123 : invalid name specified
  • ora-02241 : must of form EXTENTS (FILE BLOCK SIZE , ...)
  • ora-36848 : (XSLMGEN18) Dimension string.string!string is missing a COLUMNNAME property value
  • ora-12221 : TNS:illegal ADDRESS parameters
  • ora-01987 : client os username is too long
  • ora-19006 : XMLType TYPE storage option not appropriate for storage type
  • ora-19656 : cannot backup, copy, or delete online log string
  • ora-02794 : Client unable to get key for shared memory
  • ora-30772 : opaque types do not have default constructors
  • ora-16656 : higher DRC UID sequence number detected
  • ora-31435 : an error occurred during the purge operation
  • ora-12402 : invalid format string: string
  • ora-16553 : the Data Guard broker process (DMON) failed to shutdown
  • ora-24363 : measurements in characters illegal here
  • ora-13010 : an invalid number of arguments has been specified
  • ora-01456 : may not perform insert/delete/update operation inside a READ ONLY transaction
  • ora-15162 : cluster in rolling downgrade
  • ora-14043 : only one partition may be added
  • ora-22807 : cannot resolve to a scalar type or a collection type
  • ora-31607 : function string is inconsistent with transform.
  • ora-28232 : invalid input length for obfuscation toolkit
  • 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.