Is there any harm or issue using the Oracle 19C JDBC [ojdbc8-19.3.0.0.jar] drivers to work with 11G database? We are in mid of migration but due to internal complex mechanism there will be case during which this scenario can happen in the Prod environment.
Check out JDBC FAQ. Latest JDBC drivers are backward compatible but, if the support period ends then, we cannot guarantee support for the older versions.
You can check out the Lifetime Support Policy for Oracle Database. The Oracle Database 11.2.0.4 extended support ended on Dec 2020.
You can take a look at oracle doc for more info:
https://docs.oracle.com/en/database/oracle/oracle-database/19/jjdbc/JDBC-getting-started.html#GUID-926E5324-D89A-4A00-B1AE-975C1089F0EA
I think it can work but not sure how compatible it is. Also depend on your java version. if u want to integration between java version 8+ and Oracle database version 11G.
In the best, it should be ojdbc6.jar with JDK 6, JDK 7, JDK 8 or ojdbc5.jar with JDK 5 for 11G database.
What's the latest version of berkeley-db-je?
From oracle, it is 7.5.
But from maven repository, it is 18.3.12.
It there anyone know more details?
The latest version of Berkeley DB Java Edition is 7.5.11
https://www.oracle.com/technetwork/database/berkeleydb/overview/index-093405.html
The 18.x versions you are seeing in maven are Oracle NoSQL Database Community Edition (CE).
Some info on the database can be found here: https://docs.oracle.com/en/database/other-databases/nosql-database/19.5/concepts/introduction.html
Oracle NoSQL Database uses Oracle Berkeley DB Java Edition as its underlying storage engine.
I have a project with Phalcon 2.0 and Oracle 11g database and running successfully. I tried to upgrade to Phalcon 3.0 but it is not working.
As of Phalcon version 3.0 Oracle support has been dropped from the project. Quoting from the 3.0 Blog announcement:
Dropped support of Oracle #12008, #12009 Support of Oracle has been
dropped from the Phalcon Core for the following reasons:
The lack of Oracle maintainer
The lack of relevant experience among the Phalcon Core Team
Weak support or interest from the community
Incomplete implementation that creates only the illusion of support
for Oracle
Some issues hampering for the support of PHP 7 in Phalcon
Oracle components will be ported to the Phalcon Incubator. If the
adapter receives support and enhancements from the community, we will
consider making it part of the core again.
More info and patch notes in the blog: https://blog.phalconphp.com/
I think they already dropped support with OracleDB in 3.0.x, check it here https://blog.phalconphp.com/post/phalcon-3-0-0-released
Presently our application has been deployed in Alfresco 4.2.2 Enterprise version.We want to move our application to 5.x Alfresco version.
What are all versions released so far in 5.x?Initially I want to test our application in all 5.x Community Versions that are released so far.Where can we download old & new 5.x Community Versions?
What are the new features added in 5.x w.r.t 4.2.2?
You can find the community versions here : https://sourceforge.net/projects/alfresco/files/
The current enteprise version is the 5.1. The previous version was 5.0.3.
About the new features, I encourage you to look at the different releases notes because I don't know what you are looking for.
The biggest change for me is the disappearance of the alfresco legacy backend, the end of lucene and the refactoring of some apis.
We’re thinking about downgrading our Alfresco Enterprise 3.4.1 to Alfresco Community.
I’m used to Alfresco Enterprise, but I have no experience with Community version.
We’re using EMC, Alfresco Explorer and our own development based on Web Services API and Foundation API.
I’m worried about database migration. Could I simply configure Alfresco Community 3.4.e to use our Oracle Database for Alfresco Enterprise 3.4.1? Is the schema compatible for both Community and Enterprise distributions? Which version of Alfresco Community should I use? 3.4.e? What is the downgrade path between distributions? Is there any kind of correspondence between versions of both distributions?
Any downgrade experience, guide or any related information will be welcomed.
The Alfresco Community Edition is open source, and works with a fully open source stack. Your DB options are PostGreSQL (recommended) or MySQL.
Alfresco Enterprise supports the open source databases that Community supports, PostGreSQL and MySQL, as well as a few proprietary databases too. You can look at the Database Configuration page for more information. Support for Oracle databases is only available in Enterprise.
If you want to keep paying Oracle all that money for your database licenses, then you'll need to continue to pay a tiny fraction of that cost to Alfresco for an Enterprise License. Community, being open source, only supports a fully open source stack, so you can't use Community with your uber expensive proprietary database!
If you were using an open source database like PostGreSQL or MySQL, then you might be able to do the switch as part of an upgrade. Enterprise Service Packs (eg 3.4.1) are normally newer than the equivalent community release from that series (Community gets the bug fixes on Head). Moving from a 3.4.x enterprise service pack back to a 3.4 community wouldn't be recommended, but moving from 3.4.x enterprise to a 4.x community might work. However, that's not a tested migration path, so you could well be on your own... Alfresco QA tests community -> newer community, enterprise -> newer enterprise, and community upgrading to enterprise, which are the supported paths.
This question is similar with this one about difference between Community and Enterprise version
You can not use Oracle database for Community version. It is only available for Enterprise.
There is not downgrade path for any Alfresco versions. If you are using Enterprise 3.4.2 try to use the same Community version.
I searched the web for possibilities of a downgrade from enterprise to community version, too. What I found is the answer "You may be able to downgrade, however that is never supported or tested."
When downgrading, you have to keep in mind that the community version X usually has more functionalities than the enterprise version with the same version number.
So, downgrading is experimental. I have already seen log files where the downgrade failed.
Maybe it is an option for you to export all content and import this ACP file on the new system with the community version?
Please read your contract carefully. Support and Licensing might not be the same thing in your case. If you don't want to pay anymore to Alfresco, you might be entitled to keep using your current enterprise version, but you would not longer have support. Before considering downgrading, check your contract. If in the future you want to get support and upgrade again, it might just be easier to do it with your current Alfresco Enterprise version.
But, as I said, it depends on your agreement with Alfresco.
Migration of the Alfresco repo database is no fun at all. There is no official way switching databases and in 3.x version you may have serialized objects which could be stored by hibernate db specific. This changed a little when Alfresco removed most of hibernate dependencies after 3.4. It may be an option to migrate to 4.0 EE first, migrate the db to postgres (which is closer to oracle than mysql) and finally upgrade to Alfresco Community 4.2.f (latest version with Web Services API). This may be a lot of work (even in your code) but should work.
Here in Germany it is legaly problematic to limit software usage in time if you sell a support subscription (at least for the old contracts you may have) so customers here can request support for a time unlimited EE license key before canceling the subscription contract. I recommend you go this way and update your old 3.4 to the latest 3.4.x or 4.x enterprise version available and stay on Oracle db if you don't care these costs. This step should be done anyway ;-)
I have done it before in order to create a development environment in my local machine,
First, you cannot use Oracle database so you have to use postgresql (recommended) or MySql, exporting and importing the database is not recommended, so you have to create the repository hierarchy and fix the rules, etc., then copy all custom jars (jobs, actions, workflows...) and library from the lib folder to the new one,
If you are using an external application based on alfresco uuids, make sure you updated the uuids after creating the repositories and rules