Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Services / Reporting Services / January 2008

Tip: Looking for answers? Try searching our database.

Oracle error witrh Report Builder

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Enzo M - 07 Mar 2006 09:33 GMT
Hi
I am doing reports and UDMs from a DW in Oracle and it is great (some
doubt expressed in another post).
I tried Report Builder but the new model wizard comes back with the
error:
ORA 02179: valid options: ISOLATION LEVEL { SERIALIZABLE | READ
COMMITTED }

The data source file (.ds) has been configured with most of the
connections to Oracle available (e.g. .NET Providers Oracleclient Data
provider; Microsoft OLE DB Provider for ORacle etc.) with same error.

The strange thing is that I can create the .dsv with no problem, browse
the tables, refresh with no problems.

What I am doing wrong?

cheers
Enzo
Bruce L-C  [MVP] - 07 Mar 2006 14:51 GMT
You are not doing anything wrong. Oracle is not supported for the Report
Builder (note that it is supported for the Report Designer).

Signature

Bruce Loehle-Conger
MVP SQL Server Reporting Services

> Hi
> I am doing reports and UDMs from a DW in Oracle and it is great (some
[quoted text clipped - 15 lines]
> cheers
> Enzo
Xfonhe - 20 Apr 2006 21:46 GMT
Work-around for Report Builder:

1. Create linked server connection to Oracle database using the
OraOLEDB.Oracle provider(more up-to-date than Microsoft's).

2. Create a Data Source using the native SQL provider to the SQL Server
where you created in step 1.

3. Create a data source view; do not select objects.

4. Right-click in the DSV designer pane and create a New Named Query. Build
your query against the linked server (i.e. use 4-part names: select * from
linkedservername..schema.object).  Repeat step 4 for each object you wish to
add to your model.

5. Add logical keys where applicable.

6. Build your model.

7. Deploy & build reports using Report Builder :-)

X
Clyde Danganan - 31 Jan 2008 19:41 GMT
Are there plans for a permanent fix for this?  This could be a pain if you
have many tables.

url:http://www.ureader.com/msg/115710202.aspx
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.