ORA-25122: Only LOCAL bitmap indexes are permitted on partitioned tables

Cause : A nattepmtw a smdaet oc raet eag lboa lbtimpa nidxe no apratoinde atbel.

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

ceraet alcoa lbtimpa nidxe niseta.d

update : 27-06-2017

ORA-25122 - Only LOCAL bitmap indexes are permitted on partitioned tables
ORA-25122 - Only LOCAL bitmap indexes are permitted on partitioned tables

  • ora-09719 : osncui: invalid handle.
  • ora-16417 : Activation occurred after recovery from standby redo log files; a full database backup is required
  • ora-23541 : tables do not match tables used while defining the redefinition
  • ora-23470 : invalid status
  • ora-06421 : NETCMN: Error detected in the read-in data
  • ora-23619 : non-Oracle system error: string
  • ora-22890 : cannot specify name for REF column constraint
  • ora-14158 : too many subpartition descriptions
  • ora-02725 : osnpbr: cannot send break signal
  • ora-00213 : cannot reuse control file; old file size string, string required
  • ora-33447 : (ESDREAD16) Discarding compiled code for workspace object because workspace object and workspace object, which were partition-dependent when the code was compiled, are now not partition-dependent.
  • ora-32163 : Method called on Invalid Environment type
  • ora-36814 : (XSTBLFUNC07) The datatype of the column used in the ROW2CELL clause of a LIMITMAP must be RAW(16).
  • ora-24507 : invalid combination of character set ids
  • ora-06711 : TLI Driver: error on bind
  • ora-08310 : sllfop: Bad value for recsize
  • ora-19601 : output file is string string (string)
  • ora-37182 : you may only specify one dimension to partition
  • ora-38717 : Invalid DUMP FLASHBACK option.
  • ora-16012 : Archive log standby database identifier mismatch
  • ora-39139 : Data Pump does not support XMLSchema objects. string will be skipped.
  • ora-31635 : unable to establish job resource synchronization
  • ora-24340 : cannot support more than 255 columns
  • ora-02007 : can't use ALLOCATE or DEALLOCATE options with REBUILD
  • ora-22279 : cannot perform operation with LOB buffering enabled
  • ora-28542 : Error in reading HS init file
  • ora-38477 : attribute set cannot be derived from an evolved type or a subtype.
  • ora-29396 : cannot switch group to string
  • ora-29268 : HTTP client error string
  • ora-23315 : repcatlog version or request string is not supported by version string
  • 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.