This content has been marked as final. Show 8 replies
1.Copy the tnsnames.ora from Oracle Database home (ORACLE_HOMENETWORKADMIN) to the following locations.
* OracleBI1networkadmin (Example: C:OBIOracle_BI1networkadmin)
* oracle_commonnetworkadmin (Example: C:OBIoracle_commonnetworkadmin)
2.Set the TNS_ADMIN environment variable value with one of the copied locations in the step 1 in user.cmd or http://user.sh file depending on your OS.
This file will be found under
(Example : C:OBIinstancesinstance2bifoundationOracleBIApplicationcoreapplicationsetup)
Edited by: Devarasu on Nov 22, 2011 2:45 PM
OBIS' OCI library is different from that of version that Admintool can see.Or The OCI or Oracle home, etc are not set up properly before running Admintool.
In your case, when opening rpd by double-clicking the rpd file (instead of opening via Admin tool), the Oracle Home is not initialized which could be why the database connection fails.
So to fix the behavior, open rpd file using Administration Tool client.
Please find the NQSAdminTool.log
[2011-11-22T07:23:57.000+00:00] [OracleBIServerComponent] [NOTIFICATION:1]   [ecid: ] [tid: 1128]  Metadata Database Type: [[
Data Source Name: x.x.x.x:1521/SID
Data Source Type: Oracle Database 11g Enterprise Edition Release 184.108.40.206.0 - Pro
[2011-11-22T08:05:50.000+00:00] [OracleBIServerComponent] [ERROR:1]   [ecid: ] [tid: 1128] [nQSError: 17014] Could not connect to Oracle database. [[
[nQSError: 17001] Oracle Error code: 12154, message: ORA-12154: TNS:could not resolve the connect identifier specified
at OCI call OCIServerAttach.
Also I have opened the RPD using the ADMIN tool and I have not double clicked on it.
Multiple Oracle Homes exist which can cause confusion to OBI Admin tool for where to reference OCI libraries, NLS and the tnsnames.ora entries.
So this requires a few additional configuration steps in this case.
1. For the Admin Tool installed with the complete OBIEE server installation:
1.1. Edit registry under HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\<Oracle_Home> to make sure NLS_LANG key is set to a valid characterset for the Oracle Client used as the DSN.
1.2. Please edit the file %MiddleWare_Home%\instances\instance1\bifoundation\OracleBIApplication\coreapplication\setup\bi-init.cmd to set %ORACLE_HOME%\bin as first entry in the PATH.
1.3. Please edit the file %MiddleWare_Home%\instances\instance1\bifoundation\OracleBIApplication\coreapplication\setup\user.cmd to set TNS_ADMIN to your Oracle client tnsnames.ora home directory path (in case exists) or to your OBIEE tnsadmin %OBIEE_Client_Home%\Oracle_BI1\network\admin.
2. For the Admin Tool installed with the new standalone installer:
2.1. Edit registry under HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\<Oracle_Home> to make sure NLS_LANG key is set to a valid characterset for the Oracle Client used as the DSN.
2.2. Please edit the file %OBIEE_Client_Home%\\oraclebi\orahome\bifoundation\server\bin\bi_init.bat to set %ORACLE_HOME%\bin as first entry in the PATH.
2.3. Please add TNS_ADMIN entry to the bi_init.bat file to point to your Oracle client tnsnames.ora home directory path.
Please note to open the Oracle BI Admin Tool using the start menu shortcut (Start >> Programs >> Oracle Business Intelligence >> Administration Tool) and not by double clicking the RPD file nor through a Custom shortcut as this is required to initialize required environment variables.
While connecting from your standalone BI Admin Tool client in online mode. please note that in this case you will be using the tnsnames.ora file on the BI server, so please make sure your connection pool has the correct entries for your oracle DB and the tnsnames.ora file on the BI server has the corresponding TNS entry.
Please make your TNS entry is with the same name as the SID. Also TNS_ADMIN environment variable need to be set on the BI server to point to the tnsnames.ora file location.
for more :