We are planning to upgrade Informatica Powercenter from 9.0.1 to 10.2.0.Below are few queries regarding the upgradation:
1)What would be hardware configuration required for 10.2.0 for the below scenario:
(a)All Informatica services and repository will be in one node
2)To upgrade from 9.0.1 to 10.2.0 ,we would follow this approach: 9.1.0--> 9.6.0 -->10.2.0 .Is it fine?
3)How many servers would be require to perform this upgradation .Do i need 3 servers each for 9.1.0,9.6.0 ,10.2.0 or 1 new server is sufficient to perform this upgradation? If 3 servers are required,what would be the hardware configuration required to perform this installation for each version(9.1.0,9.6.0,10.2.0)?
4)Any document that can be helpful to perform this upgradation smoothly.
Please respond as early as possible.
Thanks,
Piyush Khurana
Go to Informatica support site and go through the upgrade planner
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.
Current version 9.0.7.0
Upgrade version 9.0.11.0
When we looked at how to upgrade, we found below link
ML Knowledgebase
This document is of April 2018.
So i would like to know if we have to follow any additional steps, configuration, process?
Upgrading from Release 9.0-1 or Later
To upgrade from release 9.0-1 or later to the current MarkLogic 10 release (for example, if you are installing a maintenance release of MarkLogic 10), perform the following basic steps:
Stop MarkLogic Server (as described in step 1 of Removing MarkLogic).
Uninstall the old MarkLogic 9 release (as described in Removing MarkLogic).
2.1. If you want to uninstall MarkLogic 9.0-4 or later, and if the converters package was previously installed with it, you will have to perform a two-step uninstall: first uninstall MarkLogic Converters and then uninstall MarkLogic Server. For more detail, see MarkLogic Converters Installation Changes Starting at Release 9.0-4 and Removing MarkLogic.
Install the new MarkLogic 10 release (as described in Installing MarkLogic).
If you want to install MarkLogic 9.0-4 or later, and you plan to use the converters package with it, you will have to perform a two-step installation: first install MarkLogic Server and then install MarkLogic Converters. For more detail, see MarkLogic Converters Installation Changes Starting at Release 9.0-4 and Installing MarkLogic.
Start MarkLogic Server (as described in Starting MarkLogic Server).
Open the Admin Interface in a browser (http://localhost:8001/).
When the Admin Interface prompts you to upgrade the databases and the configuration files, click the button to confirm the upgrade.
If you are upgrading a cluster to a new release, see Upgrading a Cluster to a New Maintenance Release of MarkLogic Server in the Scalability, Availability, and Failover Guide. The Security database and the Schemas database must be on the same host, and that host should be the first host you upgrade when upgrading a cluster.
If you are upgrading two clusters that make use of database replication to replicate the Security database on the master cluster, then you must enter the following to manually upgrade the Security database configuration files on the machine that hosts the replica Security database:
http://host:8001/security-upgrade-go.xqy?force=true
Recently we started getting a message on the Azure portal that our SF version on the cluster we use will become unsupported (5.7.198). Which I interpret as that we need to upgrade to 6.0.
Has anyone done such an upgrade on a prod system with real customers and data that should be kept safe?
Is there an upgrade we should follow (i.e. go through intermediate versions)
Any issues that I should expect?
Thanks!
I have two TeamCity Servers which are running on different software versions: one server is running "TeamCity Enterprise 9.1.7" whereas the other Server is running "TeamCity Professional 7.0.2". What is the best way to perform a migration. I want to transfer the projects that exist on Server 7.0.2 to the Server 9.1.7.
I would be very grateful if you could provide me with the steps to undertake.
There are a lot of TC versions between 7.0.2 and 9.1.7, more than 4 years of updates: https://confluence.jetbrains.com/display/TW/Previous+Releases+Downloads
First of all, you should make a backup using maintainDB tool, then you can try to migrate from major to major version and test the results:
UPDATE: base on vlad-p53's comment you can migrate directly form 7.0.2 to 9.1.7, so, just follow the tutorial A Step by Step Guide to Migrating a TeamCity Instance from One Server to Another.
7.0.2 to 8.0 and test the results.
8.0 to 9.0 and test the results
9.0 to 9.1.7
If a migration to a major version does not work, you can try a previous versions and repeat the process.
Each release has a release note that explains if there is a migration issue, I recommend to you to read them.
To each migration you can follow the steps of this tutorial: A Step by Step Guide to Migrating a TeamCity Instance from One Server to Another.
I was asked to implement a High Availability and auto-failover in postgresql and I have been searching the internet all over to find the right architecture for that.
I have tried to do it in two architectures:
RedHat cluster
UCARP
Both ways came out pretty bad when I've meet bugs on UCARP restarting as master-master after several reboots and Redhat cluster fails to manage properly PostgreSQL service.
I would like to ask if anyone has ever succeeded to implement such an architecture and would like to explain me how or refer me to a tutorial that actually works.
The components that I have are: PostgreSQL at latest version (9.4), RHEL 6.6 and higher, all on virtual machines.
Thanks in advance,
Aviel Buskila.