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 : 30-05-2017

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

  • ora-33306 : (DBVALID03) The AW VALIDATE command cannot be used with read-only analytic workspace string.
  • ora-24181 : The type string does not exist
  • ora-14187 : partitioning method for LOCAL index is inconsistent with that of the underlying table
  • ora-03263 : cannot drop the first file of tablespace string
  • ora-14109 : partition-extended object names may only be used with tables
  • ora-31456 : error executing a procedure in the DBMS_CDC_UTILITY package
  • ora-25427 : cannot downgrade database links after database link data dictionary has been upgraded
  • ora-07415 : slpath: allocation of memory buffer failed.
  • ora-00232 : snapshot control file is nonexistent, corrupt, or unreadable
  • ora-01908 : EXISTS keyword expected
  • ora-12008 : error in materialized view refresh path
  • ora-12472 : policy string is being used
  • ora-27461 : The value for attribute string is too large.
  • ora-12056 : invalid REFRESH method
  • ora-24080 : unschedule_propagation pending for QUEUE string and DESTINATION string
  • ora-24067 : exceeded maximum number of subscribers for queue string
  • ora-29802 : missing CONTEXT keyword
  • ora-19045 : character set id specified for XMLSerialize not valid
  • ora-32637 : Self cyclic rule in sequential order MODEL
  • ora-01533 : cannot rename file 'string'; file does not belong to tablespace
  • ora-21611 : key length [string] is invalid
  • ora-14068 : TABLESPACE and TABLESPACE_NUMBER may not be both specified
  • ora-36974 : (XSRELTBL14) workspace object is not a BOOLEAN variable dimensioned by all the dimensions of the hierarchy.
  • ora-33332 : (DSSEXIST01) Use the AW command to establish a current analytic workspace. Then start your current activity again.
  • ora-07629 : smpall: $EXPREG failure
  • ora-19667 : cannot do incremental restore of datafile string
  • ora-16178 : Cannot specify remote destinations in archivelog manual mode
  • ora-26084 : direct path context already finished
  • ora-19721 : Cannot find datafile with absolute file number string in tablespace string
  • ora-02356 : The database is out of space. The load cannot continue
  • 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.