I am new to upgrading Apex versions. We will be upgrading from v: 4.0.1 to v: 4.1. I have read the documentation, just wanted to know do I have to export the data prior to the upgrade or will the data be migrated with the upgrade?
Thank you for all your help so far,
Melanie
You don't need to perform an export\import Your Apex applications will be migrated with the upgrade.
The
documentation doesn't explain it well but it states:
If you have version 1.5.x, 1.6.x, 2.0.x, 2.2.x, 3.0.x, 3.1.x, 3.2.x or
4.0x of Oracle Application Express, following any of the installation
scenarios in this guide upgrades your Oracle Application Express
instance to version 4.1 and creates Oracle Application Express 4.1
database objects in a new schema and migrates the application metadata
to the new version.
I would suggest conservative approach and making export in any case. During our upgrade we hit specific problems with LDAP authentication. So in most cases you could stay with direct upgrade, but in case you use functionality outside of Oracle you will probably need the export for tunning external functionality (trial-error).
Related
I am using Derby 10.8.2 which requires Gemini DBAcess. These versions are very old (circa 2011) and do not work with JRE > 1.8.
As the title asks, does anyone know of a more recent version that will work in an OSGi evnironment?
Thanks
The Derby community have an open Enhancement Request to support OSGi on the most recent versions of Derby: DERBY-7056
There are a set of proposed changes to provide this support.
My understanding is that the primary blocker on this is access to somebody who is relatively familiar with OSGi and could test the support, as none of the Derby committers are users of OSGi.
So perhaps you could volunteer to work with the Derby community and help get the OSGi support tested and committed?
I am using 5.6 version of sonar, want to upgrade to 6.7. Can I directly upgraded to 6.7 ?
I have 8-10 sonar projects hosted on a same instance of sonar server. I am not sure what would break after upgrade. I am thinking of following approach
Install (do not upgrade) a new version of sonar 6.7, this would run on the different port(s).
Create a copy of sonar database which I have with my older sonar version, attach that copy of DB to new installation of sonar (by updating the sonar configuration file).
Assuming everything works fine, retire the older version (sonar server & DB).
I am using dedicated database as SQL server.
Anybody tried this approach? does it work?
Atul
If you're using one of the supported databases, you can upgrade directly from 5.6 to 6.7.
Simply follow the Upgrade Guide - and make sure that you back up your DB first in case of troubles.
I have a large project running on Laravel 4.2 and now I would like to upgrade it to the latest release (5.4)
On the upgrading guide I can see the steps to upgrade from each release to the next one, but the 4.2 to 5.0 requires a fresh install. Hence the question: should I install 5.4 (and fix problems) or 5.0 (running each upgrade)?
I'm possibily using any Laravel functionality, and have organized repositories for my own custom methods; I also need to maintain the database. I need to upgrade because I would like to use event bradcasting with Laravel Echo.
Thanks
To those looking for an answer: update directly to latest version, then fix changes along the way.
Explanation:
At first I tried to upgrade version by version; it was a pain. Every single vendor had different packages for each version and that caused issues even before correcting the code. I couldn't start fixing my code because the installation requirements of the vendors were failing at a certain point of the upgrade process.
Upgrading directly to latest version requires the correction of many things, but at least those are only related to your code. In my case I had to remove Sentry (authentication), Laravel OAuth, and some others I don't remember in favor of some native packages which I hope will be maintained properly. The upside of this approach is that once you have all the packages you need installed you can work directly on your code... which is what you have to do anyway.
Is there a way to upgrade WebSphere 8.5.5.10 to version 9?
When installing Fix Packs using IBM Installation Manager, I only add the repository.config, but after adding the repository.config for Version 9, I only have the install option.
You'll have to do a new install of v9, and then migrate your configuration from the old to the new environment. There are a few different kinds of config migration, but the main overview is here: https://www.ibm.com/support/knowledgecenter/SSEQTP_9.0.5/com.ibm.websphere.migration.base.doc/ae/welcome_migrating.html
In particular, the provided tools will include WASPreUpgrade (https://www.ibm.com/support/knowledgecenter/en/SSAW57_9.0.5/com.ibm.websphere.migration.nd.doc/ae/rmig_WASPreUpgrade.html) and WASPostUpgrade (http://www.ibm.com/support/knowledgecenter/en/SSAW57_9.0.5/com.ibm.websphere.nd.multiplatform.doc/ae/rmig_WASPostUpgrade.html). For each profile you want to migrate, you use WASPreUpgrade to create a backup of your old configuration in a separate location, and WASPostUpgrade to merge that configuration with a new profile in the new configuration. You can do this disabling the old environment (standard migration) or keeping them both running side by side (clone migration) and have a choice of staying on the same system or migrating to a new one (remote migration.) All those terms are explained in the overview.
You can only indirectly upgrade by way of migration. You cannot just apply service/maintenance to change the Version or Release (WebSphere use a V.R.M.F versioning)
When migrating from one version or release to another, you perform a full install and use the provided tools to migrate your configuration.
As per this post Infinispan 4.x can be run on Jboss AS 5.1.0 GA.
1. So, is that it? Can't we run higher versions of Infinispan on Jboss AS 5.1.0 GA?
2. Some bug fixes would have been done on Infinispan 4.x and upgraded to higher versions. So, if I use Infinispan 4.x what all bugs I could face?
You can run any version you like, but you'll have to isolate the classes to avoid conflicting with the ones included in the AS. Of course you can't replace the clustering technology in AS5 with it: you can use it exclusively with your own applications. If you intend to use it with Hibernate make sure you pick an Hibernate version compatible with the Infinispan version you choose: consequentially you might need to bundle a custom Hibernate version as well, and isolate from the older version provided in AS5. Generally, the Infinispan team does not consider AS5 support a goal and we're not actively testing for this.
Hard to tell which issues could affect you not knowing what you plan to use it for. All issues are tracked in the open as well so feel free to check: Infinispan changelog or ask for more advice on the Infinispan forums.