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 : 25-04-2017

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

  • ora-14621 : cannot add subpartition when DEFAULT subpartition exists
  • ora-08458 : invalid format parameter
  • ora-32330 : invalid operation on online redefinition interim table "string"."string"
  • ora-02720 : osnfop: shmat failed
  • ora-06750 : TLI Driver: sync failed
  • ora-28544 : connect to agent failed, probable Net8 administration error
  • ora-38505 : invalid default value for the attribute
  • ora-16709 : standby archived log location settings conflict with flash recovery area
  • ora-16641 : failure to acquire broker configuration metadata lock
  • ora-30927 : Unable to complete execution due to failure in temporary table transformation
  • ora-06251 : NETNTT: cannot translate address file name
  • ora-09843 : soacon: Archmon unable to create named pipe.
  • ora-04064 : not executed, invalidated string
  • ora-32512 : type 'string' is unknown
  • ora-27015 : skgfcls: failed to close the file
  • ora-16602 : object must be disabled to perform this operation
  • ora-38713 : Flashback Database logging is already turned on.
  • ora-24431 : Statement does not exist in the cache
  • ora-34719 : (NLSCHARSET03) Character data loss in NTEXT/TEXT conversion
  • ora-06546 : DDL statement is executed in an illegal context
  • ora-06537 : OUT bind variable bound to an IN position
  • ora-02840 : Open of log file by client failed
  • ora-14030 : non-existent partitioning column in CREATE TABLE statement
  • ora-01207 : file is more recent than control file - old control file
  • ora-07703 : error in archive text: need '/' after device type
  • ora-31160 : max substitution group size string exceeded by "string" (string) for head element "string" (string)
  • ora-30509 : client logoff triggers cannot have AFTER type
  • ora-07456 : cannot set RESOURCE_MANAGER_PLAN when database is closed
  • ora-28334 : column is already encrypted
  • ora-16147 : standby database referenced by multiple archive log destinations
  • 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.