OBIEE Administration Tool – Import Metadata shows no schemas

May 24th, 2012 by

Importing Metadata with the Administration Tool

The client-only install of the OBIEE 11g Administration Tool is installed with a set of OCI libraries. This means that it can support basic Oracle Database interaction, without the need for a full Oracle Client installation on the machine. For example, you can update row counts in the Physical layer of the RPD of tables that are on Oracle.

Unfortunately, the supplied OCI libraries are not complete, which leads to a rather tricky problem to diagnose. When you use the Import Metadata operation (either from the File menu, or context menu on an existing Connection Pool), the step (“Select Metadata objects”) which ought to show the schemas just shows a stub, and no schemas.

No schemas shown in Select Metadata Objects / Import Metadata

No error is shown by the Administration Tool, giving the erroneous impression that there just aren’t any schemas in the database.

Missing OCI library

The Administration Tool writes a log, which by default is in the following rather long path: C:\Program Files\Oracle Business Intelligence Enterprise Edition Plus Client\oraclebi\orainst\diagnostics\logs\OracleBIServerComponent\coreapplication\Administrator_NQSAdminTool.log

If you examine the log, you’ll see this error:

[2011-12-16T15:10:12.000+00:00] [OracleBIServerComponent] [ERROR:1] [] [] [ecid: ] [tid: 8b4]  [nQSError: 93001] Can not load library, oracore11.dll, due to, The specified module could not be found. [[
The specified module could not be found.


The key bit in this is “Can not load library, oracore11.dll“. This is the library which is missing and on which there is a dependency. The library isn’t provided by InstantClient, so you must install the full Oracle Client.


Installing the Oracle Client

Download the Oracle Client from the Oracle Website. The link is currently this, but may change. In this instance I downloaded “Oracle Database 11g Release 2 Client ( for Microsoft Windows (32-bit)” (all 600MB+ of it).


Unzip the installer and run setup.exe. If you want as minimal an installation as possible, then select the custom installation, and choose just the “Oracle Call Interface (OCI)” option.

Oracle Client installer - OCI libraries

Once you’ve installed the Full Client, restart the AdminTool and the Import Metadata function will now work.


Footnote – tnsnames.ora

Don’t forget that if you don’t install the full Oracle Client and use the OCI functionality provided by the OBIEE installation alone, you will need to configure your tnsnames.ora file in C:\Program Files\Oracle Business Intelligence Enterprise Edition Plus Client\oraclebi\orahome\network\admin\tnsnames.ora. The exception is if you are using Easy Connect DSNs (dbserver:port/sid) in your RPD rather than TNS entries (orcl etc)

Footnote – troubleshooting library issues

Microsoft’s SysInternals suite includes the program ProcMon. You can point this at a running process and see what it’s up to in terms of file access, DLLs, and networking. It is great for detecting things like:

  • Which files a process writes to (eg where is a user preference stored)
  • Check which PATHs are being searched for an executable / library
  • Which tnsnames.ora is being picked up
  • What network connections are being made, or failing
  • Registry key access

When you run ProcMon you’ll realise how much is going on in the background of your Windows machine – there’ll be screenful upon screenful of output. To focus on the target of your analysis, use the Include Process option to just show AdminTool.exe:

Include AdminTool in procmon traces

You can then see things like it searching for the oracore11.dll which it is missing:

oracore11.dll missing

The next entry shows the log file being updated, giving you the path if you didn’t know it already:

AdminTool log file

Tags: , , , ,


  1. Manish Says:

    Thanks for this info. I am facing a different issue. In Offline mode, my OCI connection pool connects just fine i.e. Import metadata shows the database objects. As soon as I deploy the RPD, in online mode, Import Metadata immediately gives an error “The connection has failed”.

    Any idea why this is the case? I am using the Oracle VM for SampleApp for OBIEE



  2. Robin Moffatt Says:

    @Manish, Check the AdminServer.log that I mention in the post, to see what the error detail is.

  3. Somnath Says:

    If anyone has Oracle 10g Client and facing this issue then you can follow the below steps to resolve.

    Copy ORACORE10.dll in the same location
    Remane it to ORACORE10.dll
    Make sure %ORACLE_HOME%\BIN is added to your PATH variable.
    Restart Admin Tool.

    This has resolved the problem in many of our machines.


  4. Somnath Says:

    There is a small typo in my last comment. Line number 3. It should be “Remane it to ORACORE11.dll” and not “Remane it to ORACORE10.dll”

  5. Krish Says:

    Nice it solved my issue with tool

  6. Ashok Says:

    Thanks a lot somntath. Its worked.


  7. Justin Says:

    After following the steps in the article, I still cannot resolve this issue. From Process Monitor it appears that oracore11.dll is not even searched for. No matter where I place the file or how many times I install the Oracle Client I still get the error in the NQSAdminTool log that the library cannot be found. But I don’t see it being searched for in Process Monitor. I do see a bunch of dll’s getting loaded, such as oraociei11.dll and oci.dll. I see my tnsnames file getting loaded as well. Anyone have any suggestions? Are there certain versions of the OBIEE Admin tool that are buggy?

  8. James O. Says:

    I know this is an old thread but we were having this issue in on a Windows Server 2008 R2 box. Problem ended up being the compatibility of the 32-bit drivers – we are using the 32-bit 11gR2 client driver and therefore needed to use the 32-bit Admin Tool install, not the 64-bit one.
    Hope that helps someone…

  9. Gustavo Says:

    Yes, 32-bit biee client works fine.

    Thanks for your help.

    Best Regards,

  10. Somnath De Says:

    I just copy the ORACORE10.DLL and rename the copy as ORACORE11.DLL to resolve the issue. But my question why Oracle has hard coded the name of the library file. As the driver we are selecting is Oracle 10g/11g so it can be either ORACORE10.DLL or ORACORE11.DLL. This should be handled in the tools code.

  11. FFM Says:

    Thank you so much. That worked for me. The missing library was the problem.

  12. Jeroen Kloosterman Says:

    Although not officially supported yet, I am running with a 12c database client. I mean, the Admin Tool connects to the target database using an Oracle 12c database client installation. The library there is called oracore12.dll. After copying that to oracore11.dll the metainformation of the tables is shown in the Admin Tool.

Website Design & Build: