Oracle Bi Administration Tool 11.1.1.5
Posted on by admin
I am using OBIEE 12c which is installed on different server and i am trying to open the deployed repository in online mode from my BI-Administration Client tool but not able to open, I was also configuring BI Server DSN but some error occurred which I am not able to solve.
I had tried different ports (9514,9500,9503,9502,9505) to configure but didn't worked.If i am using wrong port then please tell me where to find the right port for this.
Thanks in advance.
tapan sharmatapan sharma
1 Answer
The nQSError: 12017 is specific to a port configuration issue. Either the port is incorrect, or the server/network firewall is blocking it.
As you may know, 9514 is the default BI system component port; however, it seems as though the BI Server system component port may have been changed since the initial installation.
You can check the BI Server system component (obis1) port in:
Enterprise Manager Fusion Middleware Control (under Target Navigation) -> Business Intelligence -> biinstance -> Availability tab -> Processes sub tab.
Alternatively, you can run the command below on the server to check the ports:[Oracle_Home]/user_projects/domains/bin/bi/bitools/bin/status.sh -v
(My answer above is based on Oracle's internal knowledge article detailing this error (Doc ID 2148653).)
cdabelcdabel
Not the answer you're looking for? Browse other questions tagged obieeoracle-bi or ask your own question.
Troubleshooting Oracle BI EE Connections to Oracle OLAP Oracle BI EE 11.1.1.5, Oracle OLAP and Oracle Database 11g
NOTE:
The following is intended to outline our general product direction. It is intended for information purposes only and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remain at the sole discretion of Oracle.
TABLE OF CONTENTS
NOTE ............................................................................................................. 0 TABLE OF CONTENTS ..................................................................................... 2 INTRODUCTION ............................................................................................. 3 OVERVIEW .................................................................................................... 3 ARCHITECTURE .............................................................................................. 4 KEY CONFIGURATION CHECKLIST .................................................................. 5 TROUBLESHOOTING CONNECTIONS .............................................................. 6 1. [nQSError: 77031] Error occurs calling remote service AWImportService11g. Details: Error sending result for service … no ocijdbc11 in java.library.path .................................................................... 7 2. [nQSError: 77021] Could not load SAW RPC library sawrpcapi.dll ........ 8 3. Error attempting to load oraccore11.dll and the oranls11.dll.............. 8 4. Step 4 of the Import Wizard displays no OLAP cubes or dimensions ... 8 5. [nQSError: 60001] Connection failed for: Remote ServiceJavaHostImportService… Java Host is not available inside the function AWImportService11g of SAW RPC ............................................................ 9 6. Query Failed: [nQSError: 17001] Oracle Error code: 12545, message: ORA-12545: Connect failed because target host or object does not exist at OCI call OCIServerAttach. [nQSError: 17014] Could not connect to Oracle database. (HY000) ......................................................................... 9
Draft – Oracle Confidential
Page 2
Troubleshooting Oracle BI EE Connections to Oracle OLAP
Introduction This paper summarizes how Oracle BI EE connects to Oracle OLAP for both metadata administration and query. It then provides troubleshooting tips for common issues with those connections.
Overview Oracle BI EE 11.1.1.5 offers new capabilities over an Oracle OLAP source. The Administration Tool is now able to import metadata from an analytic workspace using a simple wizard – automatically populating BI EE’s Physical Layer with dimensions, hierarchies, measures and calculations. The BI Server uses this metadata for optimal query execution – exploiting OLAP strengths such as analytic calculations (time-series, shares, financial functions, etc.), advanced hierarchies (skip, ragged, value-based, etc.) and complex aggregations (sum, last, hierarchical last, weighted averages, etc.). These new capabilities result in enhanced developer productivity and outstanding performance for complex analytic queries. Figure 1 highlights the two key steps for metadata import: 1) connecting to the OLAP source and 2) selecting the metadata to import from the analytic workspace:
Draft – Oracle Confidential
Page 3
Figure 1: Administration Tool Import Wizard
Once imported, the creation of the Business Model and Presentation layer are greatly simplified. The Business Model is generally a direct reflection of the Physical Layer – few modifications are typically necessary.
Architecture Figure 2 illustrates how Oracle BI EE connects to Oracle OLAP for both administration and query:
Draft – Oracle Confidential
Page 4
Figure 2: Components required for OLAP access by BI EE
In order to import OLAP metadata, BI EE utilizes the OLAP Java API (the OLAP API libraries are installed with the BI middle tier). This requires the Administration Tool to invoke the middle tier Java Host to access OLAP metadata. Once the metadata is defined, the BI Server queries OLAP cubes and dimensions using SQL. Query access requires a standard OCI connection to the Oracle Database – similar to any other Oracle Database source.
Key Configuration Checklist Consult the following checklist to ensure your system is configured to allow connections between BI EE and Oracle OLAP:
Install the Oracle Database Client (use the Administrator or Runtime client install option). The Oracle Database Client must be in sync with the BI Administration Tool (i.e. both tools must be 32-bit or 64-bit. You cannot mix versions).
The Java Host must be running on the middle tier.
The Data Source in the Administration Tool’s Metadata Import wizard must use the host:port:sid connection string format. Note, the Java Host on the middle tier must be able to make a connection to the Oracle Database using this connection string.
Draft – Oracle Confidential
Page 5
After importing the metadata for your OLAP cubes, update the Data Source Name in the Connection Pool to use an Oracle Database Network Alias (i.e. a valid TNS entry).
Specify the Java Host connection details in NQSCONFIG.INI when running a stand-alone Administration Tool that connects to a remote Java Host: o
On the Administration Tool client machine, edit the NQSCONFIG.INI file in folder [bi_home] oraclebiorainstconfigOracleBIServerComponentco reapplication
o
Update the [JAVAHOST] section with the appropriate connection details. For example, if your Java Host is running on server “mybihost” and is configured for port “9810”, the section should read as follows (ignoring the text wrapping): JAVAHOST_HOSTNAME_OR_IP_ADDRESSES = 'mybihost:9810';
Troubleshooting Connections This section provides solutions to common connection issues. Below you will find a list of error messages with links to the problem’s resolution. Administration Tool Import Error Messages: 1. [nQSError: 77031] Error occurs calling remote service AWImportService11g. Details: Error sending result for service … no ocijdbc11 in java.library.path 2. [nQSError: 77021] Could not load SAW RPC library sawrpcapi.dll 3. Error attempting to load oraccore11.dll and the oranls11.dll 4. Step 4 of the Import Wizard displays no OLAP cubes or dimensions 5. [nQSError: 60001] Connection failed for: Remote ServiceJavaHostImportService… Java Host is not available inside the function AWImportService11g of SAW RPC Answers Error Message 6. Query Failed: [nQSError: 17001] Oracle Error code: 12545, message: ORA-12545: Connect failed because target host
Draft – Oracle Confidential
Page 6
or object does not exist at OCI call OCIServerAttach. [nQSError: 17014] Could not connect to Oracle database. (HY000)
1. [nQSError: 77031] Error occurs calling remote service AWImportService11g. Details: Error sending result for service … no ocijdbc11 in java.library.path
Issue TNS alias names are not supported for metadata import. Resolution The Data Source Name must use a host:port:sid connection string. Note, the Java Host will make the connection to OLAP on behalf of the Administration Tool. This means that the middle tier must be able to make the database connection using the specified connection string.
Draft – Oracle Confidential
Page 7
2. [nQSError: 77021] Could not load SAW RPC library sawrpcapi.dll
Issue There is a mismatch between the BI Administration Tool and the Oracle Database Client installed on the client machine. Resolution The BI Administration Tool and Oracle Database Client must both be either 32-bit or 64-bit.
3. Error attempting to load oraccore11.dll and the oranls11.dll Issue The incorrect type (InstantClient) of Oracle Database Client was installed on the client machine. Resolution You must install one of the following types of Oracle Database Clients: 1) Administrator or 2) Runtime.
4. Step 4 of the Import Wizard displays no OLAP cubes or dimensions Issue The import was able to successfully connect to OLAP – but no metadata is available. Resolution
Draft – Oracle Confidential
Page 8
The OLAP API jars on the middle tier need to be updated to version 11.2.x. The OLAP API libraries are found in your Oracle Database home: [oracledb home]product11.2.0dbhome_1olapapilib. BI EE provides an 11.1.x version of these files in [obiee home]Oracle_BI1bifoundationjavahostlibobisintegrationaw11g. Backup the BI EE version of the OLAP API jars and replace them with the version provided by the database.
5. [nQSError: 60001] Connection failed for: Remote Service-JavaHostImportService… Java Host is not available inside the function AWImportService11g of SAW RPC Issue The import was unable to successfully connect to OLAP using the Java Host. Resolution Ensure the Java Host is running and that the NQSCONFIG.INI file on the client machine is set up to make a connection to that Java Host.
6. Query Failed: [nQSError: 17001] Oracle Error code: 12545, message: ORA-12545: Connect failed because target host or object does not exist at OCI call OCIServerAttach. [nQSError: 17014] Could not connect to Oracle database. (HY000) Issue After importing metadata from OLAP, the Data Source Name in the Connection Pool is using host:port:sid. It must be changed to use OCI.
Draft – Oracle Confidential
Page 9
Resolution Edit the Connection Pool object and specify a valid TNS entry for the Data Source Name.
Draft – Oracle Confidential
Page 10
Troubleshooting Oracle BI EE Connections to Oracle OLAP July 2011 Oracle BI EE 11.1.1.5, Oracle OLAP and Oracle Database 11g Author: Marty Gubar Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores, CA 94065 U.S.A. Worldwide Inquiries: Phone: +1.650.506.7000 Fax: +1.650.506.7200 oracle.com Copyright © Oracle BI EE 11.1.1.5, Oracle OLAP and Oracle Database 11g, Oracle Corporation and/or its affiliates. All rights reserved. This document is provided for information purposes only and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
NOTE:
The following is intended to outline our general product direction. It is intended for information purposes only and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remain at the sole discretion of Oracle.
TABLE OF CONTENTS
NOTE ............................................................................................................. 0 TABLE OF CONTENTS ..................................................................................... 2 INTRODUCTION ............................................................................................. 3 OVERVIEW .................................................................................................... 3 ARCHITECTURE .............................................................................................. 4 KEY CONFIGURATION CHECKLIST .................................................................. 5 TROUBLESHOOTING CONNECTIONS .............................................................. 6 1. [nQSError: 77031] Error occurs calling remote service AWImportService11g. Details: Error sending result for service … no ocijdbc11 in java.library.path .................................................................... 7 2. [nQSError: 77021] Could not load SAW RPC library sawrpcapi.dll ........ 8 3. Error attempting to load oraccore11.dll and the oranls11.dll.............. 8 4. Step 4 of the Import Wizard displays no OLAP cubes or dimensions ... 8 5. [nQSError: 60001] Connection failed for: Remote ServiceJavaHostImportService… Java Host is not available inside the function AWImportService11g of SAW RPC ............................................................ 9 6. Query Failed: [nQSError: 17001] Oracle Error code: 12545, message: ORA-12545: Connect failed because target host or object does not exist at OCI call OCIServerAttach. [nQSError: 17014] Could not connect to Oracle database. (HY000) ......................................................................... 9
Draft – Oracle Confidential
Page 2
Troubleshooting Oracle BI EE Connections to Oracle OLAP
Introduction This paper summarizes how Oracle BI EE connects to Oracle OLAP for both metadata administration and query. It then provides troubleshooting tips for common issues with those connections.
Overview Oracle BI EE 11.1.1.5 offers new capabilities over an Oracle OLAP source. The Administration Tool is now able to import metadata from an analytic workspace using a simple wizard – automatically populating BI EE’s Physical Layer with dimensions, hierarchies, measures and calculations. The BI Server uses this metadata for optimal query execution – exploiting OLAP strengths such as analytic calculations (time-series, shares, financial functions, etc.), advanced hierarchies (skip, ragged, value-based, etc.) and complex aggregations (sum, last, hierarchical last, weighted averages, etc.). These new capabilities result in enhanced developer productivity and outstanding performance for complex analytic queries. Figure 1 highlights the two key steps for metadata import: 1) connecting to the OLAP source and 2) selecting the metadata to import from the analytic workspace:
Draft – Oracle Confidential
Page 3
Figure 1: Administration Tool Import Wizard
Once imported, the creation of the Business Model and Presentation layer are greatly simplified. The Business Model is generally a direct reflection of the Physical Layer – few modifications are typically necessary.
Architecture Figure 2 illustrates how Oracle BI EE connects to Oracle OLAP for both administration and query:
Draft – Oracle Confidential
Page 4
Figure 2: Components required for OLAP access by BI EE
In order to import OLAP metadata, BI EE utilizes the OLAP Java API (the OLAP API libraries are installed with the BI middle tier). This requires the Administration Tool to invoke the middle tier Java Host to access OLAP metadata. Once the metadata is defined, the BI Server queries OLAP cubes and dimensions using SQL. Query access requires a standard OCI connection to the Oracle Database – similar to any other Oracle Database source.
Key Configuration Checklist Consult the following checklist to ensure your system is configured to allow connections between BI EE and Oracle OLAP:
Install the Oracle Database Client (use the Administrator or Runtime client install option). The Oracle Database Client must be in sync with the BI Administration Tool (i.e. both tools must be 32-bit or 64-bit. You cannot mix versions).
The Java Host must be running on the middle tier.
The Data Source in the Administration Tool’s Metadata Import wizard must use the host:port:sid connection string format. Note, the Java Host on the middle tier must be able to make a connection to the Oracle Database using this connection string.
Draft – Oracle Confidential
Page 5
After importing the metadata for your OLAP cubes, update the Data Source Name in the Connection Pool to use an Oracle Database Network Alias (i.e. a valid TNS entry).
Specify the Java Host connection details in NQSCONFIG.INI when running a stand-alone Administration Tool that connects to a remote Java Host: o
On the Administration Tool client machine, edit the NQSCONFIG.INI file in folder [bi_home] oraclebiorainstconfigOracleBIServerComponentco reapplication
o
Update the [JAVAHOST] section with the appropriate connection details. For example, if your Java Host is running on server “mybihost” and is configured for port “9810”, the section should read as follows (ignoring the text wrapping): JAVAHOST_HOSTNAME_OR_IP_ADDRESSES = 'mybihost:9810';
Troubleshooting Connections This section provides solutions to common connection issues. Below you will find a list of error messages with links to the problem’s resolution. Administration Tool Import Error Messages: 1. [nQSError: 77031] Error occurs calling remote service AWImportService11g. Details: Error sending result for service … no ocijdbc11 in java.library.path 2. [nQSError: 77021] Could not load SAW RPC library sawrpcapi.dll 3. Error attempting to load oraccore11.dll and the oranls11.dll 4. Step 4 of the Import Wizard displays no OLAP cubes or dimensions 5. [nQSError: 60001] Connection failed for: Remote ServiceJavaHostImportService… Java Host is not available inside the function AWImportService11g of SAW RPC Answers Error Message 6. Query Failed: [nQSError: 17001] Oracle Error code: 12545, message: ORA-12545: Connect failed because target host
Draft – Oracle Confidential
Page 6
or object does not exist at OCI call OCIServerAttach. [nQSError: 17014] Could not connect to Oracle database. (HY000)
1. [nQSError: 77031] Error occurs calling remote service AWImportService11g. Details: Error sending result for service … no ocijdbc11 in java.library.path
Issue TNS alias names are not supported for metadata import. Resolution The Data Source Name must use a host:port:sid connection string. Note, the Java Host will make the connection to OLAP on behalf of the Administration Tool. This means that the middle tier must be able to make the database connection using the specified connection string.
Draft – Oracle Confidential
Page 7
2. [nQSError: 77021] Could not load SAW RPC library sawrpcapi.dll
Issue There is a mismatch between the BI Administration Tool and the Oracle Database Client installed on the client machine. Resolution The BI Administration Tool and Oracle Database Client must both be either 32-bit or 64-bit.
3. Error attempting to load oraccore11.dll and the oranls11.dll Issue The incorrect type (InstantClient) of Oracle Database Client was installed on the client machine. Resolution You must install one of the following types of Oracle Database Clients: 1) Administrator or 2) Runtime.
4. Step 4 of the Import Wizard displays no OLAP cubes or dimensions Issue The import was able to successfully connect to OLAP – but no metadata is available. Resolution
Draft – Oracle Confidential
Page 8
The OLAP API jars on the middle tier need to be updated to version 11.2.x. The OLAP API libraries are found in your Oracle Database home: [oracledb home]product11.2.0dbhome_1olapapilib. BI EE provides an 11.1.x version of these files in [obiee home]Oracle_BI1bifoundationjavahostlibobisintegrationaw11g. Backup the BI EE version of the OLAP API jars and replace them with the version provided by the database.
5. [nQSError: 60001] Connection failed for: Remote Service-JavaHostImportService… Java Host is not available inside the function AWImportService11g of SAW RPC Issue The import was unable to successfully connect to OLAP using the Java Host. Resolution Ensure the Java Host is running and that the NQSCONFIG.INI file on the client machine is set up to make a connection to that Java Host.
6. Query Failed: [nQSError: 17001] Oracle Error code: 12545, message: ORA-12545: Connect failed because target host or object does not exist at OCI call OCIServerAttach. [nQSError: 17014] Could not connect to Oracle database. (HY000) Issue After importing metadata from OLAP, the Data Source Name in the Connection Pool is using host:port:sid. It must be changed to use OCI.
Draft – Oracle Confidential
Page 9
Resolution Edit the Connection Pool object and specify a valid TNS entry for the Data Source Name.
Draft – Oracle Confidential
Page 10
Troubleshooting Oracle BI EE Connections to Oracle OLAP July 2011 Oracle BI EE 11.1.1.5, Oracle OLAP and Oracle Database 11g Author: Marty Gubar Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores, CA 94065 U.S.A. Worldwide Inquiries: Phone: +1.650.506.7000 Fax: +1.650.506.7200 oracle.com Copyright © Oracle BI EE 11.1.1.5, Oracle OLAP and Oracle Database 11g, Oracle Corporation and/or its affiliates. All rights reserved. This document is provided for information purposes only and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
Comments are closed.