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

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

  • ora-15090 : handle string is not a valid descriptor
  • ora-16951 : Too many bind variables supplied for this SQL statement.
  • ora-26002 : Table string has index defined upon it.
  • ora-14079 : illegal option for a partition marked Index Unusable
  • ora-01267 : Failure getting date/time
  • ora-06003 : NETASY: port write failure
  • ora-01661 : tablespace 'string' is already temporary
  • ora-16622 : two or more broker database objects resolve to one physical database
  • ora-29861 : domain index is marked LOADING/FAILED/UNUSABLE
  • ora-00394 : online log reused while attempting to archive it
  • ora-39710 : only connect AS SYSDBA is allowed when OPEN in UPGRADE mode
  • ora-12914 : Cannot migrate tablespace to dictionary managed type
  • ora-03275 : duplicate DEALLOCATE option specification
  • ora-29883 : cannot create a domain index on column expressions
  • ora-01161 : database name string in file header does not match given name of string
  • ora-22878 : duplicate LOB partition or subpartition specified
  • ora-10936 : trace name context forever
  • ora-29277 : invalid SMTP operation
  • ora-37031 : (XSMLTMAINT02) You cannot DELETE values of dimension workspace object in MULTI mode.
  • ora-32334 : cannot create prebuilt materialized view on a table already referenced by a MV
  • ora-12680 : Native services disabled but required
  • ora-32100 : operation invalid on transient object
  • ora-27250 : OS system call failure
  • ora-30928 : Connect by filtering phase runs out of temp tablespace
  • ora-16260 : Waiting to replace partial or corrupt logfile (thread# string, sequence# string)
  • ora-26685 : cannot apply transactions from multiple sources
  • ora-29358 : resource plan string does not exist
  • ora-24128 : partition name specified for a non-partitioned object
  • ora-38776 : cannot begin flashback generation - flash recovery area is disabled
  • ora-26520 : internal memory failure
  • 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.