i wanna build a crystal report using crystal reports 2013 with oracle database.
i've created an odbc connection to connect to this db named "abc".
then from the database expert in the crystal reports i've created a new connection ,then i've click on odbc ,and i choose the "abc" .
the problem is that only the stored procedure are shown , cannot find any table from the database, only the stored procedure,
i don't know why .. Can any one help me please .
Right click on the connection , go to properties and find the options. Most likely tables are not selected to be shown in the tree
Related
I have a table comprised of columns varchar2's of ascending length. They range from varchar2(1911) to varchar2 (2865).
I use an Oledb Connection to the database and in the Dataflow source editor, under the 'table or view' I am able to see the table. However when I select that table I get the following error:
Error Code: 0x80040e37
Error at DataflowTask[Ole DB Source[1]]: Opening a rowset for "inserttablename" failed. Check that the object exists in the database.
I do not think it is a datatype length issue as it is able to find a table with a range of varchar2(3993) to varchar2(4000). Maybe it is the cumulative size of the table?
Whats more strange is that it works fine when targeting SQL Server 2017, it is only in 2016 and 2014 that it does not appear to work. Any insight would be greatly appreciated.
I am using Visual Studio 2017.
It also works with AdoNet connections as well as ODBC connections.
I have created an Oracle Database Project Version 2 on visual studio 2017 and imported an existing database to the project to obtain the database schema on my project, and I got an SQLfile for such object in my project. The problem is when I'm modifying a table for example and saving the changes on my oracle database project and build it, I get a create script as output instead of an alter script so this script can't be deployed to my database due to "existing object error".
I tried to do it otherwise by proceeding to schema compare option:
I launched the schema comparison by mentionning my oracle database project as source and my database as target
The result of the comparison indicated that there is an non indentical object between the source and the target which was the table (because i added a coloumn to the table)
Again the problem is when I generate the update script it gives a drop/create table script instead of an alter and I can't deploy this script because I will lose data.
Does anyone have any ideas? how can I get the alter script by building the project or launching a schema compare operation?
I've found that comparing two databases DO generate a "somewhat" correct diff script (it may need some manual adjustment). So you can run the SQL file generated by the database project against a different oracle instance, and then compare both.
I've installed the ODT for Visual Studio 2015 (I've also tried VS2013) in hopes of using the "Oracle Database Project" but experiencing some specific error messages that don't appear to be very common.
When I browse the database via the Server Explorer, there is an option for you to be able to right click on a Relational Table and click "Generate Create Script to Project...".
However, when clicking this option I get a very non-specific error message and cannot work out why;
"Create script was not generated to Project for some of the selected object(s). See the 'Oracle Database Output' output pane for more information."
When I look at the "Oracle Database Output" window I get the message;
"Script Generation failed - Internal Error."
For here-on-in, it's gets very frustrating to find out what's wrong and to debug this non-descriptive error message.
What's most interesting is that the script generation function works for other database objects such as views & procedures, it just fails to work for database tables.
Has anybody experienced this error before? I'm wondering if it's a driver issue of some sort! (I have the oracle 11g client installed, and just tried with a specific ODAC/ODT combination package which appears to also install the 12c client, connecting to an Oracle Elements 11g server)
Any help appreciated, Thanks.
I have this problem too.
I was able to Create the scripts earlier, but now I cannot.
I did some investigating and decided this is not a problem with the oracle database. It is something to do with the state of VS.
I restarted VS2015 and I could create scripts again.
I have created a new Sql 2008 Database Project in Visual Studio 2010. I imported the database objects and only kept the stored procedures. That all worked as expected. Where I have the problem is that it tries to deploy the entire set of procedures each time. I expect it to only create the deployment script for the delta. I am pretty sure that I combed every setting, but I can't find it. So if someone could first validate that this is possible and second tell me where to look. I need to do this because we only deploy the stored procedures with each release, the database schema is not modified.
Do a Schema compare of the project (as source) with the database where you want to deploy (as target). Once shcem comparison results are shown you have a choice to select which changes you want to deploy and then click the button "Export to T-SQL Editor". It will create the delta script.
I just created a new table and filled it with data. When I run a simple select query, I can see all the data.
But when I try to build a report in Crystal with this table, I get no data. It doesn't matter if I have other tables included or not, so it isn't a linking issue.
If I right click a field and choose "browse data", I get nothing, which tells me that somehow Crystal can't read the data at all.
I created the table with the same user name/password that I used when connecting to the database from Crystal Reports.
Any ideas?
(If it matters, I'm using Oracle 10g Release 1 and Crystal Reports XI Release 2. We use a direct Oracle connection, not an ODBC.)
I found the problem. I hadn't yet committed the data on the database.
This taught me something about Oracle. I rarely use the "commit" command - but when I have created tables and filled them with data it's been via a "select" statement. Those tables have always worked. This time I did it via the insert all command. I needed to commit for that to work!