cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Migration V1R3 CP13 to V1R3 CP17 - no Environment conversion requested

Solved
Contributor

Migration V1R3 CP13 to V1R3 CP17 - no Environment conversion requested

Hi,

 

When I migrated my Hopex installation from V1R3 CP13 to V1R3 CP17, I linked the environment to this new version.

After opening the environment using Administration tool, no message is displayed requesting conversion.

 

SysDb > Conversions menu is greyed out, same as Data db > conversions.

SysDb > RDBMS admin > Technical conversion > start it > no upgrade needed message

Data Db => RDBMS admin > Technical conversion > start it > no upgrade needed message

Metamodel conversion goes well.

 

Is there a way to force the conversion? or is it ok to use it as it is?

 

Thanks

Mehdi

7 Replies
png MEGA
MEGA

Re: Migration V1R3 CP13 to V1R3 CP17 - no Environment conversion requested

Hi,

 

Since you are only applying patches, you do not need to do that conversion but just the "environment automatic update" and "convert data from version V1R2" (if you were on V1R2).

 

Here is the guide on how to upgrade CPs. Probably you can start with #7 if there are no warning message popping up related to any conversions. 

 

For each MEGA Environment:
1.Start the Administration Console (Administration.exe).
 
2.Select the environment to be upgraded.
 
3.R click > Open.
 
4.If a warning is displayed (You cannot access repository "SystemDb". Its internal structure is not up to date. Run the menu "Technical Conversion" to perform the upgrade):
oSelect the environment in the administration tree.
oR click > Technical conversions.
A window 'MEGA RDBMS Technical Conversion' is displayed.
oClick 'OK'.
oWait until the processing is complete and click 'Close'.
oSelect the environment to be upgraded.
oR click > Open.
 
5.Login with the System identifier.
 
6.If warnings are displayed (You cannot access repository "XXX". Its internal structure is not up to date. Run the menu "Technical Conversion" to perform the upgrade).
oFor each data repository (ex: MEGA (Tutorial))
Select the data repository in the administration tree.
R click > Technical conversions.
A window 'MEGA RDBMS Technical Conversion' is displayed.
Click 'OK'.
Wait until the processing is complete and click 'Close'.
 
7.In the folder 'Repositories', select 'Systemdb'
 
8.R click > 'Conversions > Environment automatic update > Apply'.
 
9.Read the information, check the option 'I have taken note of the above text' then click OK.
The process 'Environment Automatic Upgrade' is executed.
 
10.Wait until the upgrade is complete.
A message like 'Your environment has been successfully updated is displayed.
 
11.Click OK.
 
12.In the folder 'Repositories', select 'Systemdb'
 
13.R click > Conversions > Convert data into the current version > From HOPEX V1R2 data
A list of conversions is displayed
 
14.Check only the option 'MEGA Repository - Conversion of Code Template related with MetaCommand'
 
15.Click 'OK' to trigger the conversion.
 
16.Close the environment.
 
17.Exit the Administration Console.
 
Please let me know if you have any questions.
 
Thanks,
Philip
Contributor

Re: Migration V1R3 CP13 to V1R3 CP17 - no Environment conversion requested

Hi Philip,

 

I was on V1R3, just applied patchs up to CP17, no data conversion is needed then.

 

Thank you very much for your quick reply.

 

Mehdi

 

 

png MEGA
MEGA

Re: Migration V1R3 CP13 to V1R3 CP17 - no Environment conversion requested

Hi Mehdi,

 

After the CP upgrade completed, make sure your HOPEX version match with your SystemDB version.

 

To find the version/build #:

HOPEX version "Help --> About"

SystemDB version "Environment folder --> SysDb --> SystemDB.emv". Scroll all the way down for the latest installed build #.

 

Please see attachment for screenshots.

 

Thanks,

Philip 

 

Contributor

Re: Migration V1R3 CP13 to V1R3 CP17 - no Environment conversion requested

Tool version : Mega Hopex V1R3 (750-4936)

 

Sysdb version :

########################################

[UpgradeR3.mol - 2018/05/16 18:53:56]
Date=10/15/19 11:35:09
ProductVersion=MEGA HOPEX V1R3 (750)
Release=750
Build=4936
MetaModelVersionOrigin=MEGA HOPEX V1R3
Diagnostic=4
Reject=d:\program files (x86)\mega\mega hopex v1r3\GEAR_DEV\SysDb\USER\G\UpgradeR3.reject.mgr

################################################

 

Thank you

Mehdi

png MEGA
MEGA

Re: Migration V1R3 CP13 to V1R3 CP17 - no Environment conversion requested

Hi Mehdi,

 

Looks good to me! Both are on V1R3 CP17. You might want to log in and see if the data and the functionalities are good. Are you planning to migrate to V2R1 from V1R3 CP17?

 

Thanks,

Philip

Contributor

Re: Migration V1R3 CP13 to V1R3 CP17 - no Environment conversion requested

Hi Philip,

 

Yes next step is V2R1 then V3

 

Mehdi

Highlighted
png MEGA
MEGA

Re: Migration V1R3 CP13 to V1R3 CP17 - no Environment conversion requested

Hi Mehdi,

 

Have you consulted with any MEGA Consultants on upgrading to V3? I don't think it is recommended for existing customers to V3. You should wait for V3 CP2 which will be released by end of this year. In order to upgrade to V3 CP2, you should get to V2R1 Update 3 CP5 first. I believe CP5 will be released end of this month. Again, please discuss the migration with a MEGA consultant or an Account Manager.

Let me know if you have any questions.

 

Thanks,

Philip