I am working on data stage application usinf InfoSphere 8.7 FixPack tool. Now I am planning to migrate to InfoSphere 11.3 version.
Could you please suggest me the pros and cons which I need to know before migration?
Thanks,
Venkat
I am new on this, and I am migrating from 8.5 To 11.3. Something I learned is not to bother migrating your .ds files, because they won't work with the newer version. Also be sure to install a g++ compiler in your new server.
Related
Need some help on TWS/IWS upgrade from 9.3 to 9.5.
As 9.3 is out of support version , we are not getting help from IBM team. Can some one please help with the procedure to upgrade DB2,WAS liberty , DWC and IWS upgrade.
DB2 is upgraded successfully today. Stuck with Websphere liberty installation.
Thanks in advance
Srinivasa Rao
Stackoverflow is for programming questions. But your question is about administration.
Please refer to the "IBM Workload Automation" v9.5 "Planning and Installation Guide" for upgrading information, taking care to ensure your starting point is only the most recent fixpack for the v9.5 build.
See https://www.ibm.com/docs/en/workload-automation/9.5.0?topic=installation-upgrading and all related pages in this category, some studying required, careful planning, rehearse in a non-production environment first.
In general consider upgrading only to the "currently supported" versions of IBM software, if you wish to avail of IBM paid support services.
I am not able find any related information regarding to my current situation. Is it possible to use the Oxygen 14.1 xml author with DITA-OT 2.5.2? We plan to upgrade our sofware too, but before that the leaders of my company are interested in the possible benefits of the new DITA-OT version.
For testing purposes you can try using an oXygen 19.0 trial (https://www.oxygenxml.com/xml_author/register.html). I don't think oXygen 14.1 will work too well with the newest DITA-OT. Maybe yes, maybe not... But if you plan to upgrade to 19.0, there's no need to try 14.1 with DITA-OT 2.5.2. Just try the oXygen + DITA-OT pair that you are planning to use.
You could try using the new OT with oXygen 14.1. I believe that you'd have to create versions of the transforms to point to the new OT. However, you won't be able to use any DITA 1.3 features unless you extend the oXygen framework to pick up the newer DTDs. Probably more work than using a trial version of 19.
we are going to upgrade our typo3-instance from version 6.1.5 to 7.6. Since we need to clone the instance and afterwards upgrade it in two steps (6.1.5 -> 6.2, 6.2 -> 7.6) we wonder if it was easier to setup a clean 7.6 instance and migrate the data (templates, sites, binaries etc.) afterwards.
There are multiple instruction pages on the web describing how to upgrade to 6.2 and to 7.6 but it seems to be a really tricky process.
So I'd like to know if the t3d data is compatible between those versions. Can we export the data from 6.1.5 and import it to 7.6 without troubles?
What do you think of the approach?
Thanks,
Thomas
So I'd like to know if the t3d data is compatible between those versions. Can we export the data from 6.1.5 and import it to 7.6 without troubles?
Most likely this process will not go without troubles.
Best advice I can give, is to upgrade to 6.2, do the upgrade wizards in the install tool. After that upgrade to 7.6 and do the upgrade wizards in the install tool again (those will be different ones).
Your content should now be fine.
You can keep incompatible extensions uninstalled during this process as it is merely targeting content migration. Don't bother with extension code while doing this. Just the core and your content is enough to provide a working content structure for 7 LTS. Migrate the extensions afterwards.
I prefer the upgrade way to do it, because the t3d export / import thing may work, but may cause some troubles too, especially if this is a bigger site.
If you update the extensions on your 6.2 site to current versions, fix the namespaces and deprecation log entries in your individual extensions, the 6.2. => 7.6 upgrade should be quite smooth. In my experience it is much more convenient than a 4.5 => 6.2 upgrade.
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.
Has any one attempted this before? I would like to know how to upgrade from 4.2 to 4.4 bearing in mind that there are exisiting services on the latter, which I hope will still work on the newly upgraded 4.4.
FuseSource offers migration guides. If you are a FuseSource subscriber then I suggest to use that channel to help with the upgrade.