- Article Type: General
- Product: Aleph
- Product Version: 16.02
When I first ran step 1013 in Upgrade Express 18 to 19, the z108 table was moved from abc30 to abc50, but the structural changes to the table were not made (because of an incorrect and since fixed entry in tab100, I assume).
In trying to make the structural changes, I reran step 1013. However, this time it first deleted the z108 table in abc50 and then tried to move the z108 from abc30. Alas, there was no longer a z108 in abc30, so now there isn't a z108 table in either abc30 or abc50. The only way I see out of this is to export the z108 from our production machine, import it into the upgrade machine abc30 library and then run step 1013 again.
Is there an easier way? (I assume the upgrade_util backup/restore function only works for all files at once.) And will this create a problem because the current z108 table will be slightly out of sync with the data in the upgrade machine?
The Upgrade Express Backup/Restort has the ability to back up just certain files, and the Restore, the ability to restore just certain files. If you ran the Backup as part of the upgrade, it may be you could restore the z108.
Otherwise, the only thing is, as you say, to export the z108 from your production machine, import it into the upgrade machine abc30 library, and then run step 1013 again.
If there are cases where a course has been added on v16 since the last extraction, that course will be brought over but the docs/items which would be linked to the course will not be there.... That is not a problem.
If there are cases where a course has been deleted or inactivated since the last extraction, the doc records might not reflect that. You might need to re-run p_manage_05.
In any case, these things should not be a problem.
[From site:] I was able to restore the z108 from the backup I did before starting 18 to 19.
- Article last edited: 10/8/2013