Highlighted
Frequent Contributor.
Frequent Contributor.
1378 views

miggui - Transfer ID Error: Failed to execute others repair

Everything went fine till the last step: miggui - Transfer ID Error: Failed to execute others repair

I´m migrating a OES 2 Sp 3 to OES 11 Sp 1.

Sadly i can`t find anything helpful about this error.

Can´t find the right log for further informations too.

Any Clues? Thank you!



Sebastian
Labels (1)
0 Likes
5 Replies
Highlighted
Knowledge Partner
Knowledge Partner

Ronnenberg;2255300 wrote:
Everything went fine till the last step: miggui - Transfer ID Error: Failed to execute others repair

I´m migrating a OES 2 Sp 3 to OES 11 Sp 1.

Sadly i can`t find anything helpful about this error.

Can´t find the right log for further informations too.

Any Clues? Thank you!



Sebastian


I'm going to move this into the OES Migration thread in case Ramesh wanders by. I'm not sure about that final error. Usually it'll let you re-run it again (sometimes there's just a timing where it's repairing the SSL certs or something and the replica ring isn't fully in sync yet).
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

kjhurni;2255324 wrote:
I'm going to move this into the OES Migration thread in case Ramesh wanders by. I'm not sure about that final error. Usually it'll let you re-run it again (sometimes there's just a timing where it's repairing the SSL certs or something and the replica ring isn't fully in sync yet).


All the logs are in the:
/var/opt/novell/migration/NAMEOFPROJECT/log
directory

Usually the debug log has the most information
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

In article <kjhurni.5sxj5d@no-mx.forums.novell.com>, Kjhurni wrote:
> miggui - Transfer ID Error: Failed to execute others repair
>

Several places too look and perhaps find the clue.
The miggui logs themselves are
/var/opt/novell/migration/projectname/log/migration.log (and others in
same folder) this should have been run on the OES11 system.

Check each server's /var/log/messages for any system problems that
could be hanging things up.

Check memory usage. Running out or too tight can cause all kinds of
'fun'
free -m
Note that this shows 'now' stats, so if you are hitting a problem here,
it would most likely show best during the migration.


Andy Konecny
Knowledge Partner (voluntary SysOp)
KonecnyConsulting.ca in Toronto
----------------------------------------------------------------------
Andy's Profile: http://forums.novell.com/member.php?userid=75037


___
“i’ve sworn an oath of solitude til the blight is purged from these lands”
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
Highlighted
Frequent Contributor.
Frequent Contributor.

Sadly the logs didn´t contain any usefull information besides the error message displayed, i just ignored the error and the server is now populated by our users without any problems.


Thanks for your help!

Sebastian
0 Likes
Highlighted
Micro Focus Contributor
Micro Focus Contributor

There will be a set of scripts get executed in every step. We need to know what script failed here in your server.
This information will be logged in either debug.log or serveridswap.log located in /var/opt/novell/migration<project_name>/log folder.

I will be glad to assist if you can paste the error from the logs here or can send me to my mail id: mramesh @novell.com

-Ramesh
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.