ORA-37112: OLAP API requires Oracle 9.2 or later

Cause : Thev ersoin o ftheO LAPA PI ajr flies htat oyu uesd rqeuirse Orcale evrsino 9. 2or alter.

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

Ensrue taht teh UR Lwit hwhihc th eJDB Cconenctino wa sopeend i scorerct.I f teh RDMBS isntanec isr unnnig i ncomaptibliitym odef or averison lodert han9 .2,i t msut b eupgardedt o a tleats 9..20.00. tob e uesd wtih tihs vresio nof hte OALP AIP.

update : 29-06-2017
ORA-37112

ORA-37112 - OLAP API requires Oracle 9.2 or later
ORA-37112 - OLAP API requires Oracle 9.2 or later

  • ora-02442 : Cannot drop nonexistent unique key
  • ora-39057 : invalid worker request string for string jobs.
  • ora-01692 : unable to extend lob segment string.string partition string by string in tablespace string
  • ora-39771 : stream must be loaded before its handle is freed
  • ora-16721 : unable to set LOG_ARCHIVE_DEST_n initialization parameters
  • ora-22800 : invalid user-defined type
  • ora-30936 : Maximum number (string) of 'string' XML node elements exceeded
  • ora-13364 : layer dimensionality does not match geometry dimensions
  • ora-26065 : check constraint cannot reference column, string, in direct path load
  • ora-15182 : ASMLIB [string] version mismatch, ORACLE version [string]
  • ora-19764 : database id string does not match database id string in control file
  • ora-31070 : Invalid database user ID string
  • ora-28579 : network error during callback from external procedure agent
  • ora-01557 : rollback segment extents must be at least string blocks
  • ora-19766 : missing CHANGE keyword
  • ora-12485 : new effective label not within effective clearance
  • ora-26094 : stream format error: input column overflow
  • ora-38726 : Flashback database logging is not on.
  • ora-13361 : not enough sub-elements within a compound ETYPE
  • ora-01551 : extended rollback segment, pinned blocks released
  • ora-35020 : (QFCHECK02) The analytic workspace and EIF file definitions of workspace object have mismatched dimensioning.
  • ora-40226 : model upgrade/downgrade must be performed by SYS
  • ora-14642 : Bitmap index mismatch for tables in ALTER TABLE EXCHANGE PARTITION
  • ora-30772 : opaque types do not have default constructors
  • ora-29292 : file rename operation failed
  • ora-01592 : error converting Version 7 rollback segment (string) to Oracle 8 format
  • ora-36275 : (XSCGMDLAGG13) string is not a valid workspace object.
  • ora-16622 : two or more broker database objects resolve to one physical database
  • ora-26506 : null global context
  • ora-25202 : invalid value NULL, string should be non-NULL
  • 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.