I would advise to use 7.2.2 instead until 7.3.1 is out (7.3 is yet too fresh).
If you are forced to upgrade due to issue, then that issue has its own id. Check in what release that issue is fixed. If only 7.3 and there is no hotix for any other release _and_ you must fix it then 7.3 is your only choice. Otherwise use 7.2.2 (or 7.1.4 if you wish to stay at the same SW level).
The structure of the media, res, and index databases have not changed between 7.1.x to 7.2.x, so there is no risk in upgrading. I would recommend a level full backup of the bootstrap and indexes before upgrading (i.e. savegrp -O -l full ....).
I would recommend you do a partial remove (click on change instead of remove in the add/remove software) if on Windows. If you're on Unix, just uninstall the software using swremove or pkgrm, etc...
If you go to version 7.3.x understand that you can't go back to any previous version (i.e.7.2.x or 7.1.x).
ble1
4 Operator
•
14.4K Posts
0
May 18th, 2006 13:00
ble1
4 Operator
•
14.4K Posts
0
May 18th, 2006 13:00
If you are forced to upgrade due to issue, then that issue has its own id. Check in what release that issue is fixed. If only 7.3 and there is no hotix for any other release _and_ you must fix it then 7.3 is your only choice. Otherwise use 7.2.2 (or 7.1.4 if you wish to stay at the same SW level).
Palaciosf
3 Posts
0
May 18th, 2006 13:00
Ok i change the question , have to take any special care to migrate NW7.1.2 to 7.2.2 ?
cluu1
23 Posts
0
June 8th, 2006 14:00
I would recommend you do a partial remove (click on change instead of remove in the add/remove software) if on Windows. If you're on Unix, just uninstall the software using swremove or pkgrm, etc...
If you go to version 7.3.x understand that you can't go back to any previous version (i.e.7.2.x or 7.1.x).