Upgrade with copy repository approach

ajamit24

We are in the process of upgrading 6.7 sp1 CS to 7.2 and we need to run both old and new environment.

Current system details:

RHEL: 5.6

CS: 6.7 SP1

New System details we need to move on:

RHEL 6.x/7.x

CS: 7.2

We need to run both current and new system parallel. We have planned to have new machine of RHEL 6.x/7.x and install 7.2 CS (install Connection broker and repositories) on it and then copy the filestore and import the database export from the old env to 7.2 env and upgrade the repositories here.

But in the guide Version 7.2 Upgrade and Migration Guide, team has recommended to have copy of same version of CS. Please share if we can install 7.2 and copy DB and data from 6.7sp1 as mentioned above. Thanks.

Find more posts tagged with

Comments

ChristianDeVries

When you perform Repository copy the source and target should be same version and patch level.

So in your case you should make a copy of the 6.7 SP1 following the steps from the 6.6 Install Guide Chap 13. “Creating a repository copy to test an upgrade”. Also we have it documented in the 7.2 Migration Guide P77. The steps from 6.6 Guide are still valid in 6.7 SP1.

Then once you have the copy of 6.7 SP1 you can do an in-place upgrade to 7.2.

Let me know if that helps

Alvaro_de_Andres


CdeVries wrote:

When you perform Repository copy the source and target should be same version and patch level.

No, even EMC has detailed the procedure to go from one version to another:

http://middle-east.emc.com/collateral/white-paper/h13028-wp-d65sp2-migration-d7x.pdf

PanosK

When you are performing an upgrade, you have to be sure that the issue observed is not due to wrong repository copy or due to the upgrade procedure. The described solution that does not include a technical verification of the copy prior to upgrade can only work well on a "Hello World!" repository sizes.

It is strongly recommended to copy the repository on the same CS version, and after testing that everything is working as expected, you may proceed in the migration.

ChristianDeVries

Thank you for sharing this white paper.

My point is even if you copy the old schema to 7.x repository there is an in-place upgrade that needs to take place to make sure the database schema is also migrated (P26 from white paper). This step is very often missed.

ajamit24

Thanks for the response. If we copy to same version of CS i.e 6.7 sp1 then please when we can move from oracle 11.0.2.3 (not supported by 7.2) to 12g(Supportable by 7.2).

ajamit24

Yes but if we newly install 7.2 CS and copy old schema to 7.x, in this case we need to only upgrade repository later on.

Here, we dont need to install CS 7.x and Connection broker 7.x again and we can easily switch to 12 c oracle too since 7.2 CS is supported the same. Please let me know if my understanding is correct.

ChristianDeVries

I can see 2 options:

- .Perform upgrade with copy of same version so in the 6.7 SP1 target you can upgrade Oracle to 11.2, then do an in-place upgrade to 7.2 and also upgrade Oracle to 12c. (Oracle 11.2 is supported with both CS versions)

- Follow the white paper to install 7.2 and migrate to Oracle 12c right away and then do in-place repository upgrade.

The second approach is easier.

chongw

Another option is to consider is EMC Migration Appliance.
https://www.emc.com/collateral/service-overview/h11784-svo-pdf-emc-migration-appliance.pdf