Are there any known issues with database compatibility (GDB files) when switching Firebird Classic server from 64bit to 32bit or vice versa? I found information, that databases are compatible among Classic and Superserver, but this information was for Firebird 2.1 and I didn't find anything newer - http://firebirdsql.org/rlsnotesh/install210.html#install-model
The databases are compatible between Classic, SuperClassic and SuperServer as well as 32bit and 64bit within same Firebird version (between versions it's recommended (needed since FB3) to do backup & restore). It's the same code, same structure, just different execution model.
Related
I am running the latest DB2 connectors installer at https://www.ibm.com/support/pages/download-initial-version-115-clients-and-drivers and downloading & installing "IBM Data Server Driver Package (DS Driver)"
It installs the 32-bit ADO.NET connectors and puts them in the 32-bit machine.config.
But it puts no entries in the 64-bit machine.config (I have 64-bit Windows 10).
How can I get the 64-bit connectors installed?
Just make sure you have selected the correct driver.
There are different download options for 32 and/or 64bit on that page.
And if that is the case, no worries.. who never did something like that!
I'm using ATG 9.1. how can I know which version of JDK must be used for different versions of ATG?
With JDK 6 I am able to work normally, whereas ACC is not working as it Requires a small version of JRE.
Why is that only ACC requires a small version of JRE and not other modules?
ATG/Oracle Commerce's required versions can be found on https://support.oracle.com -- you will need to log-in, and you may need access to be granted by an Oracle representative.
ATG 9.1 compatibility is covered in document "Oracle Art Technology Group (ATG) Commerce Supported Environments - Release 9.x (Doc ID 1342327.1)", which will link you to https://support.oracle.com/epmos/main/downloadattachmentprocessor?parent=DOCUMENT&sourceId=1342327.1&attachid=1342327.1:ATG9404&clickstream=yes
The 'compatibility matrix' shows the required JDK is "Sun 32-bit or 64-bit JDK 1.6.0_41" on all supported platforms (Windows, Solaris, RedHat) for JBoss and Weblogic application servers, but different for WebSphere.
The ACC can be run from within the app server, or in separate JVM. I don't know a reason why it would require a different JDK version.
Oracle usually suggest that this as a base version, so if a minor update to your application server requires a minor update to the JVM, you should probably follow your appserver's requirements.
My mongodb is in version 3.0 and run on Linux Redhat 6.
I do not use entreprise options, then I would like to switch enterprise edition to community edition. Any drawback on data? It's much like binary upgrade?
Unless you are using an Enterprise storage engine (eg. Encrypted Storage Engine in MongoDB 3.2+), the data format in MongoDB Community and Enterprise editions is identical and changing between editions is just a change in the MongoDB server binaries. If you need to change storage engines you can do so without downtime on replica sets using a rolling maintenance procedure (see: Your Ultimate Guide to Rolling Upgrades).
I would recommend using matching release versions when changing between MongoDB Enterprise and Community editions to minimize any unexpected issues. The standard upgrade/compatibility caveats (as mentioned in the MongoDB Release Notes) apply if you happen to be upgrading or downgrading between major MongoDB versions (i.e. 3.2 and 3.4).
Is there a list anywhere or best practice instructions for update firebird databases from one version to another (in my case 2.1.3 to 2.5.2)?
I have seen backup and restore mentioned. I have updated from 1.5 to 2.1 in the past but that just worked i.e. I just installed the new firebird version, however I aware that this was probably just luck.
Regards
The Firebird 2.5.2 release notes has a section on compatibility issues that you need to be aware of when upgrading. Also the Firebird install directory contains additional info on upgrading in misc/upgrade/metadata/metadata_charset.txt. If your database has the incorrect metadata charset things might break (but AFAIK they would have been broken under Firebird 2.1 as well).
Technically you can upgrade to 2.5 without a backup and restore cycle on your database, but that means the On Disk Structure (ODS) of the database isn't upgraded to ODS 11.2, which could mean that you can't actually use some of the new features (or: performance improvements) introduced with the newer version. This could be worse if you are actually still on ODS 10.1 from Firebird 1.5.
I want to use Embedded FireBird with .NET 3.5. I have few queries:
(1) Are there any new developments done on the embedded version by the FireBird community?
(2) Are there any database file repair & optimize (shrink etc.) features in it?
(3) Does it supports Triggers, Foreign Keys, PL/SQL type of things etc.?
(1) Are there any new developments
done on the embedded version by the
FireBird community?
Yes, both the embedded and the client-server version are very active projects.
Using the same embedded version dll for ADO.NET for example, you can use the most recent version of the firebird engine dlls, even if the ADO.NET Firebird provider is not build for that version, but for a previous.
Check the issue tracker here: http://tracker.firebirdsql.org/secure/Dashboard.jspa
(2) Are there any database file repair
& optimize (shrink etc.) features in
it?
Yes, as described here: http://www.firebirdfaq.org/faq324/. You need to install the client-server version of firebird to use GFIX and GBAK from the command line. It is just a few megabytes.
Firebird does not have a "Compacting" feauture to shrink the database. You need to backup and then restore the database to do this. However you can use a firebird database for years without backup/restore (if you are lucky and the hard disk does not die). The only thing that you might need to do is to recalculate all indeces selectivity as described here: http://www.firebirdsql.org/dotnetfirebird/blog/2005/03/improving-query-performance-through.html
(3) Does it supports Triggers, Foreign
Keys, PL/SQL type of things etc.?
Yes. The 2.5 version of the embedded engine also supports accessing the same database file from different proccess at the same time.
Answering your questions:
The Embedded version is like a normal Firebird but encapsulated in a DLL and with some minor limitations. The Firebird Team just released some days ago the 2.5 version of SuperServer, Classic and Embedded flavors. More info at Embedded Firebird Server and Firebird website.
There are tools to repair and optimize databases. Check How to repair a corrupt Firebird database
Firebird is SQL:2003 conformant as stated in Firebird: SQL Conformance. It has triggers, foreiggn keys and stored procedures.
Hope that helps