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 : 28-07-2017
ORA-37118

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

  • ora-36258 : (XSAGINFO00) When the AGGMAPINFO function is called, workspace object must be an AGGMAP.
  • ora-36401 : (XSSPROPOTYPE) Property string may only be applied to objects of type string.
  • ora-16555 : the Data Guard database is not active
  • ora-30926 : unable to get a stable set of rows in the source tables
  • ora-32739 : Hang analysis aborted due to failed heap re-grow
  • ora-06313 : IPA: Shared memory failed to initialise
  • ora-13613 : The requested operation is not supported for this advisor object.
  • ora-32741 : Hang analysis already going on
  • ora-06105 : NETTCP: remote host is unknown
  • ora-13211 : failed to tessellate the window object
  • ora-13226 : interface not supported without a spatial index
  • ora-19375 : no CREATE TABLE privilege on schema "string"
  • ora-26534 : collision: tranID number ignored and purged
  • ora-38473 : cannot drop a type used for Expression Filter attribute set
  • ora-06504 : PL/SQL: Return types of Result Set variables or query do not match
  • ora-26503 : internal RepAPI operation failure on object string.string
  • ora-31010 : XML element index string exceeds maximum insertion index string
  • ora-31614 : routine string received this error from string: string
  • ora-15127 : ASM file name 'string' cannot use templates
  • ora-29308 : view TS_PITR_CHECK failure
  • ora-36802 : (XSTBLFUNC01) The OLAP_TABLE function must contain a DATAMAP that executes a FETCH command or a LIMITMAP.
  • ora-12451 : label not designated as USER or DATA
  • ora-32500 : Dirname 'string' cannot exceed 'number' characters
  • ora-26671 : maximum number of STREAMS processes exceeded
  • ora-14500 : LOCAL option not valid without partition name
  • ora-24373 : invalid length specified for statement
  • ora-36400 : (XSSPROP02) workspace object is not a valid variable name.
  • ora-16044 : destination string attribute cannot be specified at session level
  • ora-07205 : slgtd: time error, unable to obtain time.
  • ora-39012 : Client detached before the job started.
  • 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.