ORA-37118: The OLAP API library was not preloaded.

Cause : In shared-server mode, the OLAP API library should be loaded during process initialization to ensure that the C++ virtual table addresses are identical in all shared-server processes. The OLAP API session was executing in a process in which the library had not been loaded.

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

Set option _XSOLAPI_LOAD_AT_PROCESS_START to SHARED_SERVER or ALWAYS, restart the instance, and try again.

update : 27-04-2017
ORA-37118

ORA-37118 - The OLAP API library was not preloaded.
ORA-37118 - The OLAP API library was not preloaded.

  • ora-19271 : XP0051 - invalid atomic type definition
  • ora-07255 : spini: cannot set up signal handler.
  • ora-23466 : flavor requires missing object "string"."string"
  • ora-36650 : (XSDUNION10) Concat dimension workspace object cannot be changed to UNIQUE. Leaves workspace object and workspace object share the value number.
  • ora-15053 : diskgroup "string" contains existing files
  • ora-27300 : OS system dependent operation:string failed with status: string
  • ora-01628 : max # extents (string) reached for rollback segment string
  • ora-29367 : object string does not exist
  • ora-01974 : Illegal archive option
  • ora-13431 : GeoRaster metadata rasterType error
  • ora-13766 : A ranking measure is required.
  • ora-24758 : not attached to the requested transaction
  • ora-07233 : slemcw: invalid file handle, seals do not match.
  • ora-06265 : NETNTT: break protocol error
  • ora-31025 : Invalid document element
  • ora-23343 : no match for specified conflict resolution information
  • ora-13338 : failure in reversing LRS polygon/collection geometry
  • ora-36845 : (XSLMGEN15) Owner is greater than 30 bytes
  • ora-07501 : scgtoa: $deq unexpected return
  • ora-07700 : sksarch: interrupt received
  • ora-32034 : unsupported use of WITH clause
  • ora-07626 : smsget: sga already mapped
  • ora-07252 : spcre: semget error, could not allocate semaphores.
  • ora-16199 : Terminal recovery failed to recover to a consistent point
  • ora-07588 : spdcr: $GETJPIW get image name failure
  • ora-12495 : cannot disable an enabled level, category, or release category
  • ora-02264 : name already used by an existing constraint
  • ora-12535 : TNS:operation timed out
  • ora-34840 : (OPCREATE01) The string option must be declared with datatype string.
  • ora-03206 : maximum file size of (string) blocks in AUTOEXTEND clause is out of range
  • 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.