ORA-25112: maximum number of BITMAP index columns is 30

Cause : Too amn yclounmsw eer pseicfeidf o rteh nidxe.

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

Ceraet na nidxe no efwre oclmun.s

update : 22-07-2017
ORA-25112

ORA-25112 - maximum number of BITMAP index columns is 30
ORA-25112 - maximum number of BITMAP index columns is 30

  • ora-13265 : geometry identifier column string in table string is not of type NUMBER
  • ora-29515 : exit called from Java code with status string
  • ora-19100 : PASSING or RETURNING keyword expected
  • ora-32408 : materialized view log on "string"."string" already has new values
  • ora-16080 : invalid LogMiner session string for APPLY
  • ora-02227 : invalid cluster name
  • ora-31001 : Invalid resource handle or path name "string"
  • ora-39178 : cannot perform estimate on metadata only jobs
  • ora-19651 : cannot apply offline-range record to datafile string: SCN mismatch
  • ora-16728 : consistency check for property string found string error
  • ora-27057 : cannot perform async I/O to file
  • ora-01108 : file string is in backup or media recovery
  • ora-01754 : a table may contain only one column of type LONG
  • ora-15107 : missing or invalid ASM disk name
  • ora-27123 : unable to attach to shared memory segment
  • ora-13251 : duplicate entry string in metadata table
  • ora-10921 : Cannot drop tablespace belonging to default temporary tablespace group
  • ora-13043 : failed to read metadata from the _SDOLAYER table
  • ora-02808 : Allocation of memory of open files array failed.
  • ora-28102 : policy does not exist
  • ora-23608 : invalid resolution column "string"
  • ora-19380 : invalid plan filter
  • ora-27485 : argument string already exists at a different position
  • ora-27050 : function called with invalid FIB/IOV structure
  • ora-09821 : Numeric label is not valid
  • ora-19812 : cannot use string without DB_RECOVERY_FILE_DEST
  • ora-01573 : shutting down instance, no further change allowed
  • ora-07641 : smscre: Unable to use the system pagefile for the SGA
  • ora-01955 : DEFAULT ROLE 'string' not granted to user
  • ora-09826 : SCLIN: cannot initialize atomic latch.
  • 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.