I have taken a code from another environment onto my local system. The code is written in VB.NET and the backend technology is oracle 11g. While debugging the code in the local environment , I am unable to connect to the oracle database. The inner exception states 'The provider is not compatible with the version of Oracle client'. What should be the suggested action items to debug the issue and correct it?
Related
I'm developing an app in vb6 and I'm trying to do queries on SQL AZURE thanks to the SQL Server Native Client 11.0 but each time I execute a query (even a simple select * from Users;) the Native Client returned this error :
[Microsoft][SQL Server Native Client 11.0][SQL Server] Executing SQL directly; no cursor.
This problem occurs since I have created a new DB with a different level on azure portal. The database before was a web DB and the new one is a Standard DB. Is there a manip to do for the three new versions of DB in Azure(Basic,Standard,Premium) ?
Thank you very much for your help
The error in question is 16954 (your error reporting should first and foremost show the error number, state and severity, not only the error message). It occurs when an application attempts to use server side cursors in a context not supported. See Client-Side Cursors Versus Server-Side Cursors. This is likely coming from your cursor library choice in RDO, see Choosing an RDO Cursor Library. Switch to rdUseIfNeeded or rdUseNone.
I believe the underlying error is getting hidden by the sql client.
If you are getting an error for simple select * from table queries then I would check you have permissions for the credentials your app is using.
I created ms sql database in SSMS 2012. Connected successfully to Azure and trying to deploy db to the cloud.
Encountering following errors:
Please see screen shot
Numerous Usupported property errors — not supported when used as part of a data package
You're likely using a feature not supported in Azure SQL Database. Please refer to this non supported features list to help you pinpoint the problem:
http://msdn.microsoft.com/en-us/library/azure/ff394115.aspx
This happened with me too. In my case ,i changed the schema of a table after creating once for the first time. After deleting that table database deployed correctly. Usually this error occurs when validating schema fails.
Regards
MAnoj Bojja
I am new to remote database connections and I want to setup a very simple single table Delphi XE6 project to view a table ('CUSTOMERS') that I've just created in a small Windows Azure SQL database. I plan to use this access for both VCL code and FireMonkey on Android later. I can see and edit the table using the Azure dashboard.
To test the VCL code, i've dropped an FDConnection on my form with a TFDTable, TDatasource and TDBGrid. I've seen example connection info here but this refers to the MSSQL driver which I presume that I don't have because I'm using XE6 Professional. So I've used a TFDPhysSQLiteDriverLink and tried using the SQLite driver with connection params:
User_Name=user#56ss8sbeq
Database=tcp:56ss8sbeq.database.windows.net
Password=1234
Encrypt=Yes
MetaDefCatalog=DB123SQL
DriverID=SQLite
My table is CUSTOMERS and this is in the table name property of the TFDTable. When I run the project I get no connection errors but I do get "[FireDAC][Phys][SQLite] ERROR# no such table CUSTOMERS". Does this indicate that I'm being stupid in trying to use that driver? If so, do I have any way of accessing my DB with FireDAC?
AFAIK Windows Azure SQL database is a MS SQL database hosted on the cloud.
You need an MS SQL driver. You just can not link to MS SQL with a SQLite3 driver!
Upgrade your XE6 edition by buying the FireDAC bundle, or switch to other libraries, like ADO Components, which are part of XE6 Professional if I remember well.
I have been trying to figure out how to start with Oracle SQL, but I can't get the "Connection" to work. I'm not sure what the (connection name, username, password, etc.) fields are.
If I want to create a small database on local host, why do I need to connect in the first place.
I searched Google but still can't get it to work. Any help is appreciated.
ERROR MESSAGE: IO Error: The Network Adapter could not establish the connection
SQL Developer is just a client utility that lets you connect to an existing database. It sounds like you don't have a database to connect to yet. If that's the case, you'd either need someone to create a database on another machine for you or you'd need to download the database software on to your local machine and create a database to connect to. You can download the Oracle database from the Oracle Technology Network, the same place you downloaded SQL Developer from. I would guess that you would want to download Oracle 11.2 Express Edition.
Alternately, you may want to download one of the VMs that Oracle has put together that has a lot of related software installed for you to use. For example, this VM has SQL Developer, Oracle 12.1, APEX, XML DB, and a number of labs already installed for you.
Oracle SQL Developer is a tool to ACCESS existing database, you cannot create new database here. The connection is used to define where your existing database sits and how to connect to it. So you need to name you connection (bookmark), provide host name, where database runs and user name plus password to identify yourself.
Problem: Could not find installable ISAM
I am executing a query from MS Access in order to pull information from MS SQL Server 2005.
When I attempt to open a linked ODBC connection to the table directly it opens with no issues. However, when I attempt to create a DSN-less connection, I receive an ISAM error.
I have the following error when I attempt to execute my SELECT query:
"Could not find installable ISAM."
The code I'm using is as follows:
SELECT * FROM [Driver={SQL Server};
Server=Server_Name\Instance;
Database=Database_Name;
Integrated Security=SSPI;].[My_View_Name]
The help from MS Access provides the following information:
Could not find installable ISAM. (Error 3170)
The DLL for an installable ISAM file could not be found.
This file is required for linking external tables (other than ODBC or Microsoft
Jet database tables). The locations for all ISAM drivers are
maintained in the Microsoft® Windows® Registry. These entries are
created automatically when you install your application. If you change
the location of these drivers, you need to correct your application
Setup program to reflect this change and make the correct entries in
the Registry.
Possible causes:
+ An entry in the Registry is not valid. For example, this error occurs if you are using a Paradox external database, and the Paradox
entry points to a nonexistent directory or driver. Exit the
application, correct the Windows Registry, and try the operation
again.
+ One of the entries in the Registry points to a network drive and that network is not connected. Make sure the network is available, and
then try the operation again.
I have also found KB articles from Microsoft explaining when and how this should be handled. However they are unclear to me if they are actually rooted from another type of issue.
For example:
283881 and 209805 Tell me the purpose of ISAM is to tell how to format data other then, MS Access' native formatting. (But I don't want to format it in another way and the other formats do not list what I think to be the appropriate format-er)
and, 90111 Tells us the driver in the .ini file may be pointing to the wrong place in MS Access 2.0 which no longer exists in version 97+.
The odd thing is I have a DNS-less setup for another table which works fine. The only difference I see here is the default naming of the database object is not standard, so possibly I am not referring to the schema correctly in my syntax.
What am I doing wrong here? Is it truly a syntax error?*
Are there any "View" permission considerations which need to be made on the server end?
Try adding ODBC; at the start of the connection string and remove the brackets around the view name:
SELECT * FROM [ODBC;Driver={SQL Server};
Server=Server_Name\Instance;
Database=Database_Name;
Integrated Security=SSPI;].My_View_Name