Hi Team,

We are working on FileNet 5.1 to 5.5.4 Upgrade. And we understand we have to have staging upgrade to atleast 5.2.1 and then to 5.5.x (all in separate servers). This approach is fine and we also understand how database copy needs to be done if we plan to upgrade on a single long weekend.

As we have got huge DB size and critical application we may not be able to do all upgrade activities in a single weekend. And we are planning to get the upgraded environment ready few weeks earlier to our implementation.

So, for this we are thinking to upgrade from 5.1 to 5.2.1 with initial load and restart 5.2.1 to update 5.2.1 schema accordingly. And then with same approach of initial load will get the 5.5.4 environment ready with its schema updates.

However for few weeks (until implementation weekend) we will keep synchronizing data from 5.1 to 5.2.1. And on actual weekend we will just do delta copy from 5.2.1 to 5.5.4.

Question stands - if this is feasible approach in respect to Database schema structure to synchronize data from 5.1 to 5.2.1 once 5.2.1 environment is update with schema changes.

FileNet 5.1 - Oracle 11g

FileNet 5.2 - Oracle 12c

FileNet 5.5.4 - Oracle 19c

Thanks in advance,

Vivek

Vivek, please reach out to me directly so we can discuss your scenario in more detail. On the surface what you are proposing does not seem the best approach. Thanks. My email is rhildebr

Hi Vivek,

For your upgrade scenario, it is suggested that you can upgrade to P8 5.2.1 with all existing data first, then consider the next upgrade to P8 5.5.x.

You can plan a 2-phase upgrade from 5.2.1 to 5.5.x and have a chance to validate the functionality with your data after each phase.

Thank you for inputs.