BI Publisher - Missing Data Source in Data Models even after Creating Data Sources.

Pradeep Viswaraju

Summary

Data Sources can only be accessed and found in Data Models for user SYSADM.The system cannot find the Data source when individual Users login and try to run the report.

Content

We are in the process of Migrating BI Publisher reports from Test to Production.Here is what we did.

1.Created the JDBC Connection and defined the Data Source in Production.The name is similar to the one in test Instance but points to Prod Database.

2.Archived all the Data Models and Reports From the Application in Test.

3.Un-Archived the Folder(from Step2) in Production.

4.When I try to run the report or look at the properties of the data model,i am unable to locate the default data Source.The error that i get when we run the report is oracle.xdo.XDOException: Not able to find data source with name:XXXX where XXXX is the name of my Data Source.

Let me know if anybody had experienced the same and how was it resolved.

 

FPonte

Hello Pradeep.

Just checking. Did you added the Roles or Users to the new Data source in the security tab when creating it in production?

Edit the data source and go to the bottom of the page, Security section.

Regards.

Fernando

 

Pradeep Viswaraju

Hello,

Thanks for your insights on this.I did check this before and our page is currently blank without an option to Select anything.

We believe the above information you shared  was there before when we implemented the same in DEV and TEST and it's no longer appears now.However,the reports run fine and Data Source is available.

I did find a DOC ID  2358963.1 which reports a similar issue caused because of applying Bundled Patches.In our case,we didn't  apply any of those patches.We will see if the workaround suggested in the DOC ID helps and make the Allowed Roles appear.

 

Regards,

Pradeep

 

FPonte

Hi Pradeep.

Interesting information on that DOC.

Which version are you in OBIEE/BI Pub?

Please let us know if you applied the workaround and if that worked.

Best Regards.

Fernando

Pradeep Viswaraju

Hi,

Yes,we applied the workaround and it worked.

We are on Verison 11.1.1.9.0

Thanks to your inputs

Regards,

Pradeep