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 : 23-09-2017
ORA-25112

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

  • ora-19040 : Element string does not match expected string.
  • ora-04941 : required operating system patch needs to be applied
  • ora-17612 : Failed to discover Oracle Disk Manager library, return value string
  • ora-32638 : Non unique addressing in MODEL dimensions
  • ora-31398 : DBMS_LDAP: Shared servers are not supported.
  • ora-31482 : invalid option for non-distributed Hotlog change source
  • ora-19647 : non-zero LEVEL cannot be specified when INCREMENTAL is FALSE
  • ora-23478 : object group "string" is already mastered at string
  • ora-31073 : Resource not retrieved using path name
  • ora-25261 : JOB_QUEUE_PROCESSES must be at least 2 for AQ propagation
  • ora-30646 : schema for external table type must be SYS
  • ora-24805 : LOB type mismatch
  • ora-16151 : Managed Standby Recovery not available
  • ora-14288 : index is not partitioned by Composite Range method
  • ora-06004 : NETASY: dialogue file open failure
  • ora-02192 : PCTINCREASE not allowed for rollback segment storage clauses
  • ora-31509 : publication does not exist
  • ora-06515 : PL/SQL: unhandled exception string
  • ora-09845 : soacon: Archmon unable to open named pipe.
  • ora-07274 : spdcr: access error, access to oracle denied.
  • ora-38904 : DML error logging is not supported for LOB column "string"
  • ora-00221 : error on write to control file
  • ora-37082 : Invalid percent
  • ora-24501 : invalid UTF16 string passed in
  • ora-28009 : connection as SYS should be as SYSDBA or SYSOPER
  • ora-36993 : (XSRELGID10) OBJECT workspace object must be a VARIABLE, RELATION, or a numeric SURROGATE DIMENSION based on the level dimension workspace object.
  • ora-24852 : protocol error during statement execution
  • ora-04932 : increment or adjust of sequence number failed
  • ora-12825 : explicit degree of parallelism must be specified here
  • ora-12315 : database link type is invalid for the ALTER DATABASE statement
  • 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.