OBIEE 11g Error: NQS 46028 Unable to get the DLL path for the CLI 10g/11g from the NQSConfig.ini file


The behavior has been found in current release of OBIEE 11g .The same problem persist even if you upgrade the OBIEE 10g RPD to 11g version. The problem has been found during “metadata import using the TNS having OCI 10g/11g drive”r or while “view data in RPD” .

The error line shows :

NQS 46028:  Unable to get the DLL path for the CLI 10g/11g from the NQSConfig.ini file

The DB connectivity seems okay using command prompt or sqlplus option .

‘tnsping <service_name>’ from command return the response perfectly .So it is not the DB issue rather RPD is not being able to connect to DB .

Following the below steps resolved the issue:

1) Copied the ‘tnsnames.ora’ from Oracle DB path “E:\OraDeba11gR2\product\11.2.0\dbhome_1\NETWORK\ADMIN”  to “E:\OraFMW11g\Oracle_BI1\network\admin” doesn’t resolves the issue fully .

2) Create a Environment System variable in windows advanced option of system properties called as ORACLE_INSTANCE and set the value asE:\OraFMW11g\instances\instance1′   (without quote) .

3) Use absolute connection pool information to RPD or if the VALUEOF has been used just need to make sure that it will match exactly with the tnsnames.ora configuration . (having same value for SID or SERVICE_NAME will be fine in some cases)

ORADEBA =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = Oradeba)
)
)

4) Restart the BI Server .

Voila …Everything will be fine  🙂

The reason behind the issue is that, till earlier release of OBIEE 1og doesn’t bundled with the Oracle client hence the required drivers and all the DB connectivity has been done using the default native Oracle driver(having single look-up point for tnsnames.ora) .But  OBIEE 11g itself includes the Oracle client bundle, hence connecting from repository will always try to look-up the tnsnames.ora file inside the Fusion path rather 11g DB network\admin path .So copying the same TNS file across two path resolves the issue.

Hopefully Oracle will fix the issue in later release just to pick the absolute reference of Oracle DB path always.

OBIEE 11g Error: Unable to start coreapplication_obips1 component


While OBIEE presentation server is not up and running you will get below messages:

Error 500–Internal Server Error
From RFC 2068 Hypertext Transfer Protocol — HTTP/1.1:
10.5.1 500 Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.

Just check the status of all OBIEE components using opmnctl command as below
F:\MiddlewareHome\instances\instance1\bin>opmnctl status

All the components are alive except coreapplication_obips1.

Processes in Instance: instance1
———————————+——————–+———+———
ias-component | process-type | pid | status
———————————+——————–+———+———
coreapplication_obiccs1 | OracleBIClusterCo~ | 1160 | Alive
coreapplication_obisch1 | OracleBIScheduler~ | 1604 | Alive
coreapplication_obijh1 | OracleBIJavaHostC~ | 5484 | Alive
coreapplication_obips1 | OracleBIPresentat~ | N/A | Down
coreapplication_obis1 | OracleBIServerCom~ | 1236 | Alive

Also EM log showing error message below:

Failed to get messages for target /Farm_bifoundation_domain

Also the diagnostic log shows below:

EM-02694    Supplementary information regarding operation:
PROCESS:coreapplication_obips1;FAI

There may be various reason to it and one of the obvious reason is Loop-back adapter not configured for DHCP client .

The another main reason is any mistake at ‘instanceconfig.xml’ file .Any mistake in instanceconfig.xml tag placement could cause the issue of BIPS not starting up properly .Just correct the issue if did any changes and try to restart the service individually from EM UI .

Hope this could help somebody as it is very difficult to dig into issue just because of the junk OBIEE log file 😦 So tip is , do think and not blindly incorporate !!

OBIEE 11g Error: Unable to Retrieve Log because OPMN is not currently running


OPMN plays a key role on triggering OBIEE system modules start-up including BI Server , Presentation server and other BI system modules.Also it helps to log any diagnostics issues.

Sometime you may find the error “Unable to Retrieve Log because OPMN is not currently running” just after you deploy new RPD and Catalog path in OFMW deployment module and trigger the activate changes and restart the services .It typically occurs when you did a mistake while editing the instanceconfig.xml file and OPMN just looses the track to update presentation server properly.

When you observer this issue go to command prompt and type :

opmnctl status

You should see :

opmnctl: ORACLE_INSTANCE is not set.
opmnctl status requires that ORACLE_INSTANCE be correctly set in your
environment.
Make sure you are using ORACLE_INSTANCE/bin/opmnctl.bat, or set ORACLE_INSTANCE
in your environment.

So it seems OPMN looses the ORACLE_INSTANCE path to trigger the necessary activities after the BI code changes (Repository and Catalog).

There could be two options then:

1) Either create a variable from ‘Environment Variable’ option of windows as below and apply the changes. It would effect immediately to the environment.

‘ORACLE_INSTANCE’ and set the value to be ‘E:\OraFMW11g\instances\instance1’  .

(Pls note that you need to change the path according to your setup)

2) Run below from command prompt and set the variable temporarily.

set ORACLE_INSTANCE=E:\OraFMW11g\instances\instance1

Just trigger from command prompt:

opmnctl startall

After successful completion you can see the BI processes started up:

opmnctl status

C:\>opmnctl status

Processes in Instance: instance1
———————————+——————–+———+———
ias-component                    | process-type       |     pid | status
———————————+——————–+———+———
coreapplication_obiccs1          | OracleBIClusterCo~ |     536 | Alive
coreapplication_obisch1          | OracleBIScheduler~ |    5096 | Alive
coreapplication_obijh1           | OracleBIJavaHostC~ |    2064 | Alive
coreapplication_obips1           | OracleBIPresentat~ |     N/A |  Alive
coreapplication_obis1            | OracleBIServerCom~ |    5160 | Alive

If the problem still persist with the start-up of any of  the server component just bounce the whole server and retry .