How to get .oce to talk to DAS & bring back data in Interactive Reporting?

Question

Hi Hyperion Experts,
This is also a fairly basic question, I use Hyperion 9.3.1 and I have Shared Services, Workspace and Interactive Reporting Studio running on our Windows 2003 Server.
My goal is to import a .bqy document I created in Interactive Reporting Studio into workspace, and be able to click on the "refresh" button and see it refreshes the data from the backend Oracle 10g database.
I have completed the following steps so far,
1. I have created a DSN. This DSN, named "Oracle 10g Data Source", when I clicked on "Test Connection" button, It ran successfully.
2. I have created a new Datasource entry in the DAS service. If I double click on the newly created Datasource entry, the screen would display the following details.
Connectivity Type = Oracle Net
Database Type = Oracle
Enter the name of the Data source = Oracle 10g Data Source
Select the name of the Data source (it is grayed out, nothing selected)
Server/File (it is grayed out, nothing entered)
then, followed by some default connection parameters.
3. I have created a "Oracle 10g Data Source.oce" file using the Interactive Reporting Studio. I saved the .oce file at
C:\Hyperion\BIPlus\data\Open Catalog Extensions\Oracle 10g Data Source.oce
4. I created a new constrProj_Oracle10gOCE.bqy, during the creation, I chose
"Create a new document with Recent Database Connection File" option, then I chose the Oracle 10g Data Source.oce that I have created in step 3. After I log in with host user/password, I have created a data model and I see that it brings back a data set when I clicked on the "process" button. I saved this .bqy document.
5.
I imported the Oracle 10g Data Source.oce and constrProj_Oracle10gOCE.bqy into the workspace under a folder called
Root/MYBI/Test
6. I right click on the constrProj_Oracle10gOCE.bqy document, and chose "Open". It opened with Results section highlighted on the left hand side, and with data showing on the right hand side. However, when I clicked on the "refresh" button, I'd get a message box with a red X. It says,
An Interactive Reporting Service error has occurred -
Failed to acquire requested service.
(2001)
I guess the data I see in this constrProj_Oracle10gOCE.bqy was just the cached data that was brought back when I hit the process button of this .bqy when it was first created in the Studio, and that it never established any connection via the DAS service to the backend.
Could someone please show me what I have done wrong here?
thanks,
hypuser1010

Answer 1

EricaHarris,
Yes, the issue is still open. Obviously, I have gone down the path of "Scenario One".
Based on your reply, I have done the following.
There are three things I am configuring here: DSN, DAS and OCE.
1) When I created the DSN,
I started the ODBC Data Source Administrator, Click on second tab "System DSN". I added a new ODBC Data Source.
Data Source Name = Oracle 10g Data Source
TNS Service Name = //146-abc.xyz.com:1521/MYORCL0617
2) I re-created the DAS entry, per your suggestion, I made sure that "the name of the data source will be the host name you specified in your OCE".
Connectivity Type = Oracle Net
Database Type = Oracle
Enter the name of the data source= //146-abc.xyz.com:1521/MYORCL0617
3) for my OCE, I specified
Connection Software = Oracle Net
type of Database = Oracle
on the first screen.
then, on the next screen, I specified
Host = //146-abc.xyz.com:1521/MYORCL0617
I reployed the OCE, the .bqy document and restarted DAS. Yes, my .bqy document does refresh its data successfully from the backend.
However, I am not 100% convinced that the .bqy uses the OCE which talks to the DAS, which talks to the DSN entry and brings data back to the .bqy document.
Here is what I did,
I opened up the DSN entry, changed the TNS Service Name from //146-abc.xyz.com:1521/MYORCL0617 to
//146-abc.xyz.com:1521/NONSENSE. I then restarted DAS and redeployed the .bqy document. the .bqy document is still able to refresh its data. So, I have just proven that the .bqy document does not need a valid DSN entry to work, how come??
Can you (or anyone) please explain the phenomenon that I see?
Also, a very basic question. you know that when you create a .bqy in the Studio, you "import" an OCE into the .bqy document so that the .bqy knows that it should use this OCE to talk to the backend data source. but, when you deploy this .bqy in workspace, how does the .bqy know that it is supposed to go through DAS (and DSN) to interact with the database, rather than the "internal" OCE that was pre-built with this .bqy?
thanks,
hypuser1010