Import Metadata Issue in OBIEE RPD - [nQSError: 93001] Can not load library, oracore11.dll

Problem Summary

Sometimes after the installation of OBIEE Client, when you try to import tables into the RPD, you might not be able to do and the entire database schema tree appears blank [as shown in the image that follows]. Or in some cases, the table import stops working suddenly which would have been working just fine a few days earlier. 

If you ever wonder what could be the reason for this, here it is.

Cause

You are unable to import the tables in the RPD just because, the Admin tool is unable to find the required DLL file in your machine. Most often when you face this issue, if you investigate your NQSAdminTool.log, it will have an entry like this.

[nQSError: 93001] Can not load library, oracore11.dll, due to, The specified module could not be found.

While attempting to import a table from the database, the Admin tool searches for the oracore11.dll [oracore10.dll in case of 10g] file in your machine and when it is unable to look this one up, it ends up showing nothing in the front end but throws this error in the logs.

Solution

To solve this issue, all you need to do is to make this oracore11.dll [or oracore10.dll in case of 10g] file accessible to your Admin Tool. 

 How would you do that? 

 1. If your machine doesn’t have Oracle database or database client, installing one would fix the issue. Or also if you already have a client and the dll is missing in <ORACLE_HOME>/bin, you could selectively install the Oracle Call Interface [OCI] which will fix it for you.

2. If your machine already has a working Oracle database or database client with the DLL, all you need to blame is your environment variables. Even if this import has suddenly started surprising you and was working fine earlier, you ought to name this the culprit.

Check if your PATH variable includes the bin directory of the oracle home. In other words, <ORACLE_HOME>/bin should be included in PATH variable.

3. If your PATH variable includes the <ORACLE_HOME>/bin path and you still get this issue, then it is more likely that there is some problem with list of paths you have set for the variable [may be the separators]. Try adding the <ORACLE_HOME>/bin at the beginning of the PATH variable like this.

D:\Installations\app\product\11.2.0\dbhome_1\bin;C:\Informatica\9.5.1\clients\PowerCenterClient\client\bin;C:\Program Files\Common Files\Microsoft Shared\Microsoft Online Services; C:\Program Files (x86)\Common Files\Microsoft Shared\Microsoft Online Services; C:\ProgramData\Oracle\Java\javapath; C:\Informatica\9.5.1\clients\tools\datadirect

4. On the other hand, you may also check the ‘bi_init.bat’ file [by opening in any text editor] under <MW_HOME>\bifoundation\server\bin since it would be overriding your PATH & ORACLE_HOME variable. In such a case, add the value of <ORACLE_HOME>/bin to this variable to the declaration.

Finally, if none of these help may be try re-installing your clients with the right bit type [32/64] as these incompatibilities could also cause this issue.