I coded a CRM application in Delphi some years ago and worked with it. Now I reinstalled my computer and the only thing that changed was the Username of Windows 10 itself. Result is, that I cannot access the Firebird 3.0 db anymore and I have no idea what the problem is or might be, because, as far as I know, the Firebird 3.0 Embedded librart does not perform authentication.
Has anybody an idea?
There are tools to inspect access to your DB. Starting with Firebird 3 there is a new more secure way to access databases.
If your application use "old-school" (Firebird 2.5 and earlier) connection way you should provide legacy Authentication
Related
I need to connect to an Oracle 9i server from my machine using SQLDeveloper. I already have a functioning version of SQLDeveloper 18.2 + Oracle Client 12 for more modern databases, but for this connection I want a separate older version of SQLDeveloper.
I've installed SQLDeveloper 3.2.20.09 in a separate folder on my machine and can launch it, but it defaults to finding the ojdbc6.jar file from Oracle Client 12. if I go to Help > About and select properties, the jdbc.library says jdbc.library /C:/app/client/product/12.1.0/client_1/jdbc/lib/ojdbc6.jar
and if I try to connect I get the error ORA-01460: unimplemented or unreasonable conversion requested
I tried putting the path to the SQL Developer 3.2 install first in the PATH variable, but no difference. Is there a way to tell SQL Developer which jdbc driver to use for Oracle ? (maybe in sqldeveloper.conf)
The official answer is:
use the jar (driver) we ship with the product OR
use a Thick Client, and we'll pull the jdbc driver from an Instant Client or Oracle HOME on your machine
The 2nd option will work so long as you don't try to go back back or forward in time to the point that the software will recognize/support the driver.
In other words, you can't tell SQL Developer 18.x to use a 9i Home, we have a hard dependency to require at least a 11gR2 client (I believe, it could actually be a 12c based client which is required).
You'd be better off getting your data out of that ancier 9i Database and into a modern 12 or 19c Oracle instance.
but it defaults to finding the ojdbc6.jar file from Oracle Client 12.
Sounds like you've managed to get a thick connection defined, go into preferences and disabled on the advanced page any reference to OCI or Thick, then it will use the jdbc driver shipped with SQLDev.
Currently we are using microstrategy as a reporting tool 11.1 version and using Oracle DB - micro strategy metadata, Statistics , history all installed in Oracle
now we are planning to move Db from Oracle to Postgres. just wanted to check if microstrategy support Potgres DB
Here is the list of certified and supported versions: Repositories
From personal experience I can say PostgreSQL v9,v10 and v11 runs fine as metadata repository. Tested v9-v12 as DWH too, all working without problems.
As far as I remember they didn't deliver the bundled driver in one of the MSTR-versions (2019-something), but that seems to have changed in MSTR-2020 again. Not a showstopper, but something to be aware of.
I am also running PG-11 as repo for History List too, but you definitely won't get help from support for this. OT: They even made me switch from MariaDB to MySQL for a support case (don't really blame them though, it's not certified and that's that).
My last attempt at running Statistics-Repo with PG is a long while ago and it didn't really work out of the box. Don't know what the situation is there. You might have to consider moving to PlatformAnalytics and/or MySQL(/MariaDB) for this too. EM only receives bugfixes from MSTR-2020 onwards, so this seems to be future-proof (EM discontinued from 2020 onwards?)
This mostly reflects our experience, the only certified PG version for MSTR 11.1 is PG-9 and only for the MD-Repo!
There are many posts here and all over the web about getting the message:
Connection using old (pre-4.1.1) authentication protocol refused (client option 'secure_auth' enabled)
when trying to connect a a MySQL database. In my case, it's coming from MySQLWorkbench version 6.3 newly installed on a almost as newly install Ubuntu 15.10 system.
The advice is always to update the password on the database to use the new authentication.
However, that is not my problem, and that's not what the message says. It says that the OLD authentication is being used when the database wants the NEW authentication.
This version of MySQLWorkbench has a checkbox that tells it to use the OLD authentication, which is unchecked, but, from the message, it appears to be using the OLD authentication all the time.
I can connect to the database easily from version 5.2 of MySQLWorkbench running on Mac OS X.
I tried installing an older version of MySQLWorkbench on my Ubuntu system, but there were numerous errors with the package, which is intended for an earlier version of Ubuntu.
Any ideas about how I can force MySQLWorkbench to use the NEW authentication? I tried setting:
useLegacyAuth=0
but that did nothing.
OK, got the answer. The hosting outfit (Siteground) sets up MySQL passwords to work with EITHER the legacy or the new protocol. I don't know if this is homegrown, some sort of plugin that's generally available, or a standard MySQL feature. With this option, MySQLWorkbench fails to connect and erroneously reports the problem as the server not supporting the old protocol. Probably it's just confused by the error response which its programmers didn't anticipate.
Siteground very quickly set my password to use the new authentication ONLY upon my request, and then MySQLWorkbench connected with no problem.
I am using the trial version of the Zend Server edition. From all the videos/documentation supposedly you are able to change the database version from SQLITE to MySQL, but all I get when deploying an application on Zend Server is to set the Host, Database name, username and password?
Just install mysql on your system and use it. ZendServer does not care what database engine you use. When installing Zend Server it is supposed to ask if you want to install mysql (possibly you have to chose manual installation or custom or extra stuff) you might of mised that option so perhapds reinstalling is the simpler solution.
But really, you should be able to just install mysql and start using it.
I am requested to support a legacy system. I needed to install PHP4 on my computer for that and also MySQL 4.x. I couldn't find a MySQL 4.x version that installs on my computer so I thought I'd upgrade the system to MySQL 5.x. The problem is, PHP4 does not seem to work with MySQL 5.x.
I've read somewhere that something called mysqli is needed in PHP for it to be able to work with MySQL 5.x. I just couldn't quite understand whether it's something that is included in PHP5 or something I can add to PHP4.
If it's something I can add to PHP4, how?
Thanks.
PHP4 should work mostly fine with MySQL 5. Note I'm just talking from experience, sometimes it seems the technical stuff I read on the official MySQL and PHP sites have conflicted with what I observe. For what I've done, the only thing I really needed to worry about for compatibility between the two is authentication. Make sure the MySQL account you're trying to connect with from PHP4 uses the old password encoding. You can see this yourself in the mySQL user table. I can't remember the exact numbers but passwords stored under the old format are around 16 characters hashed whereas under the new format they are significantly longer.
More info here:
http://dev.mysql.com/doc/refman/5.5/en/old-client.html