Environment:
Visual Studio 2010
Windows Forms Application
Oracle Database
I am trying to use a parameter in a DataSet.xsd DataTable.
The query and parameter work fine in Query Builder but gives an error if I try "Preview Data" or use in my application.
Error: An unhandled exception of type 'System.Data.OleDb.OleDbException' occurred in System.Data.dll
Additional information: ORA-01008: not all variables bound
For full details on the application setup / my troubleshooting so far see here:
http://www.fullstackbusinessdesign.com/forums/ORA-01008.html
I am using the OleDb provider for Oracle.
The bind variable should be a question mark ? not :DEPTCODE
The bind variable :DEPTCODE would be valid for System.Data.OracleClient.
Many thanks to Prashant Kumar for this solution.
http://forums.asp.net/members/Prashant%20Kumar.aspx
Related
I'm trying to use SSIS to load some data from Oracle database to MSSQL database.
I created the project and used the ADO.Net source and was able to create a connection to Oracle and run queries and view results.
However when I actually run the package I get the following error:
Error: 0xC0208449 at Data Flow Task, ADO NET Source 2: ADO NET Source has failed to acquire the connection {EECB236A-59EA-475E-AE82-52871D15952D} with the following error message: "Could not create a managed connection manager.".
It seems similar to the issue here
And I did find that I have two oracle clients version installed "11.1" and "12.2".
One is used by PL/SQL and the other by other entity framework project.
If this is the issue I just wanted a way to tell the SSIS to pick-up the correct one.
I tried adding Entry in machine.config for "oracle.manageddataaccess.client" section with the desired version.
I also tried using other types of data sources but couldn't even create a successful connection
I tried changing the Run64bitRuntime property in the project to False
Note: I don't have SSIS installed on my machine.
Eventually, I just had to remove the entries related to 11.1 in path variable then restarted my machine.
Also I switched to "dotConnectForOracle" for connection and now it seems to be working fine.
I'm expecting issues related to other applications that might still be using the 11.1 version, but that will be a problem for another day.
Always make sure to write the user (oracle schema) in uppercase and some special characters [in my case it was $] in the password needs escape character even if you're using the wizard not the cmd
I still don't understand the whole issue but I hope this helps someone some day.
My reports were working like a charm until yesterday. But after un-installing and installing again these Nugets packages i.e. Jquery, Bootstrap, Microsoft reporting service control web and others, it not working any more. Although i can build and display new reports but not able to view the old ones. Could you please give me some hint to fix these. I am using visual studio 2017, sql server 2016.
This is the exact error
An unexpected error occurred in Report Processing.Exception has been
thrown by the target of an invocation.The type initializer for
'System.Diagnostics.Activity' threw an exception.Operation could
destabilize the runtime.
Thanks,
Ghaffar
On PhpStorm version 2017.1.3 but I think that this error is present on any JetBrains IDE with database support.
When I choose to synchronize an Oracle schema, some objects like triggers are not shown on database and I found an error on the log.
I could not find any reason and it was working on older PhpStorm / DataGrip version (before 2016.1)
In the options tab I've added an object filter. Without it there are 5000+ tables. Even removing the regular expression on the object filter I still have the same error.
Capture of Options and Advance Options. The oracle client used is Thin.
On your connection properties check if you are using Thin Driver and change it to change to OCI.
When I use the Entity Framework Profiler 3.0 to log the real SQL statement in background, sometimes I give this exception:
Message: unable to determine the provider name for provider factory of type 'system.data.sqlclient.sqlclientfactory'.
Source: EntityFrameWork.
I give this error when I run the project in visual studio 2015 debugging mode, it displays a file browser to locate r5wldbbb.5.cs. I don't know what's this file and also it doesn't exist in Entity Framework Profiler folder. So when I cancel it I give the above exception and raise this error:
r5wldbbb.5.cs not found.
You need to find r5wldbbb.5.cs to view the source for the current call stack frame.
However, when I cancel the Entity Framework Profiler I don't give this error.
I use these programe:
Visual Studio 2015.
MSSQL Server 2014.
EntityFramework 6.
Any helps appreciated.
I finally fixed it.
The trick is to update the way you get and open the connection to the database:
var connectionString = ConfigurationManager.ConnectionStrings["yourContextName"].ConnectionString;
var connectionFactoryService = (IDbConnectionFactory)DbConfiguration.DependencyResolver.GetService(typeof(IDbConnectionFactory);
var DbConn = connectionFactoryService.CreateConnection(connectionString);
Let me know if it works for you too :) Also, don't forget to update the EF profiler to the latest version using NuGet.
sup?
I got this problem wich has been slowing down my production a lot, hope u guys can give me any tip on how to solve it....
I'm currently using EF6 and a custom ConnectionString with a connectionString builder class that reads and external xml file.
My database is all set up and running in SQL 2010 and Management Studio ok, but whenever I generate the edmx file, it generates the class mappings okay, I've compared the original ConnectionString to my ConnectionString Builder they're the same, changed the :base to receive a custom ConnectionString, all set.
But when I try to save changes it doesn't find the table object, I have deleted it, created again from the start, still same "Invalid database object Dbo.TableName" error.
Does any one have a clue on this?
Thanks in Advance!
This error is not coming from Entity Framework but directly from the database.
Use SQL Profiler and include in the trace the "DatabaseName" and "ServerName" and you will find out it's not the same as your expected.
The only other options which this issue happen is if your "tableName" is not the same as the table name in SQL, so run the SQL from the SQL Profiler directly into SSMS.