Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 17001] Oracle Error code: 12154, message: ORA-12154: TNS:could not resolve the connect identifier specified at OCI call OCIServerAttach. [nQSError: 17014] Could not connect to Oracle database. (HY000)
It is clear that ....Oracle is not connecting.
1) Check RPD Connection pool properties.....give correct Datasource name and username/password.
2) If it is not connecting...then problem with tns file...
3)Have you copied tns file oracleBi home location....check once....
Mark if it helps you..
Oracle® Fusion Middleware
User's Guide for Oracle Business Intelligence Data Warehouse
11g Release 1 (11.1.1)
Oracle BI Applications Release (220.127.116.11) Certification Matrix:
This document covers Oracle BI Applications and associated components including:
∙ OEM Informatica PowerCenter 9.0.1 Hot Fix 2 and OEM Informatica PowerCenter 9.1 Hot Fix 2
∙ Oracle Business Intelligence Data Warehouse Administration Console 11g (DAC) version 18.104.22.168.4
Oracle BI Applications 22.214.171.124 is supported with
∙ Oracle Business Intelligence Enterprise Edition version 126.96.36.199.4+ and 188.8.131.52+
(To install Oracle BI Applications on Oracle Business Intelligence Enterprise Edition 184.108.40.206+, see the following document on My Oracle Support:
Installing BI Applications 220.127.116.11 on BI EE 18.104.22.168.0 [ID 1561846.1])
1) According to Certification Matrix of (22.214.171.124) only DAC 11g is possible
2) This process is as follows:
1. DAC Client logs in using FMW authentication:
a. Gets user name and password from user (can be optionally saved on the file
b. Reads the database connection information from the encrypted cwallet.sso file
stored on the file system
c. Logs into the DAC repository.
d. Reads the DAC Server URL from the DAC repository.
e. Authenticates and gets permissions through the DAC Server in the BI domain
using the BI domain URL.
2. DAC Server reads the database connection information from the file system and
connects to the DAC repository upon startup.
3. Automation utilities read the database connection information from the file system
and connect to the DAC repository.
Note: The automation utilities are not interactive
4. DAC Server command line utilities read the DAC Server information from the file
system and send it as a Web service request, which is authenticated with proper
This is not exactly DAC client. This is a way to monitor DAC server services and status.
I think that you've some security (Role/group) problem.
But the DAC Server can also run in standalone mode.
When DAC runs in standalone authentication mode, the DAC Client
authenticates users stored in the DAC repository.
So i suggest you first of all to try the standalone way.