Oracle Schemas Not Visible In OBIEE 11g Metadata Import Wizard And Admin Tool Log Shows Error: "[nQSError: 93001] ...Cannot load library, oracore11.dll..."

(Doc ID 1475489.1)

Last updated on OCTOBER 12, 2016

Applies to:

Business Intelligence Server Administrator - Version 11.1.1.6.0 and later
Oracle Exalytics Software - Version 1.0.0.0.0 and later
Information in this document applies to any platform.

Symptoms

Using Oracle Business Intelligence Enterprise Edition (OBIEE) Admin Tool 11.1.1.6+  (or 11.1.1.7+) in an Exalytics environment and created connection pool and database object for an Exadata database.
Then connected to OBIEE Admin Tool in offline mode and started the Metadata Import Wizard to import data from the Exadata database.
All schema objects were checked in step 2 (View, tables, indexes, etc.) of the wizard.
In step 3, the Exadata database shows on the left side, of the wizard window, but there are no schemas displayed and the import cannot proceed (see image below):

No errors are displayed in the OBIEE Admin Tool, but the NQSAdminTool log file (i.e. "OBIEERPD_NQSAdminTool.log") on the client machine shows error:

]]
[2012-07-09T23:21:24.000+00:00] [OracleBIServerComponent] [NOTIFICATION:1] [] [] [ecid: ] [tid: 1464]  [16020] Metadata Database Type:  [[
Data Source Name: (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = exadata-server)(PORT = 1521))) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = exadata_DB)))
Data Source Type: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64b
]]
[2012-07-09T23:21:30.000+00:00] [OracleBIServerComponent] [ERROR:1] [] [] [ecid: ] [tid: 1464]  [nQSError: 93001] Can not load library, oracore11.dll, due to, The specified module could not be found. [[
.
The specified module could not be found.

 

This problem may occur in any environment that includes OBIEE 11.1.1.6+ or OBIEE 11.1.1.7+.  It may occur in OBIEE environments associated with Oracle Exalytics, or standalone OBIEE installations.
Problem is not limited to Exadata data sources.  Problem may occur in any OBIEE environment where 32-bit and 64-bit applications may both be installed on the same environment.

 

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms