Ugrading 3.4 to 3.7.2 (and once that, the other upgrades) (OpenInsight Specific)
At 19 JUN 2001 02:34:55PM Mike Parrish wrote:
Now for my next trick… upgrading. It's not like ARev anymore….
I have been developing my application-from-hell in OI 3.4. Weeks ago I received the full 3.7.2 version and haven't had the nerve to perform the upgrade, but I'm desperate for the better Reporter, so I've got to bear down and do it.
I'm a little confused about how upgrades work in OI. When I install the 3.7.2 version, that will have to be to an entirely new directory (currently I have 3.4 at F:\Revsoft\OI), since SETUP won't install new versions over old versions. So after I've installed the new version (can/should I install to, say, F:\Revsoft\OI3_7 or to a totally different branch?), what do I do with my existing DATAVOL? I'd like my application-in-development to follow me and reside on the new version branch, but the docs are unclear on the upgrade process, as far as I can tell. Will I have the same situation when I try for 3.7.3 and .4? Can I go from 3.7.2 to 3.7.4 and skip .3? Once I've got all the files in the right place, how does my application get upgraded?
There were always very careful and very explicit upgrade instructions for ARev. Is there such a thing for OI?? I can't afford the time to mess up so hopefully you can understand my reluctance and very real fear that mayhem will ensue.
I'm terribly sorry for being a complete pest and I'm sure I worry too much about the little things. But ignorance make me very nervous and there's a lot riding on what I'm working on.
Thanks for your patience and help!!
Mike
At 19 JUN 2001 03:01PM Mike Parrish wrote:
Well, I found the White Paper: Application Backup Procedures for OpenInsight 3.7+. Seems pretty straight-forward to me.
Wish me luck!
Mike
At 19 JUN 2001 03:19PM Mike Parrish wrote:
Sigh…nothing ever being easy…
I received messages that relational indexes would not be backed up. Fine. However I ran into FS100 messages on the files that have associated relational indexes and the backup did not complete. Was I supposed to remove all of my relational indexes before running APPBACKUP?
Mike
At 20 JUN 2001 04:26AM Richard Bright wrote:
Mike, Things should be easy.
1. Use Appbackup - but do NOT include your data tables.
Thus you will have your application forms, proceedures all split out into a backup folder.
2. Copy the directories (folders) to become subdirectories of your new system.
3. In your new system in SYSPROG create the application, then within this application run Appbackup and restore from the appbackup location.
3. All done (well almost)
4. Re-establish the application entry point.
5. (optional) At dos level run fixvol on the lh files to ensure that there is no data corruption.
All this should take about the time I have taken to type this out.
- Oh problem with DATAVOL - cant replace? Might have to use Alias to attach and copy to new datavol? Or some switcharoo.
Richard Bright
BrightIdeas New Zealand
r.bright@ark.co.nz
At 20 JUN 2001 10:20PM Mike Parrish wrote:
Richard,
Thanks for the tips. I'll give them a try tomorrow. Totally contrary to the White Paper. But this isn't the first time that's happened. ;)
Mike
At 25 JUN 2001 04:58PM Mike Parrish wrote:
Richard,
Ok, so I haven't tried your upgrade tips, mainly because my workstation has been down since Friday. But I'm a little concerned by your advice. Just what is the point of backing up my application to upgrade the development set to a higher version and NOT backup my datatables?? That hardly protects the data that I've slaved away entering and I want to be sure that once 3.7.2 is installed that my appliction will be upgraded in the process. And am I going to have to repeat all of these steps to go from 3.7.2 to 3.7.3 and then again to 3.7.4???
Now, I know RTI is not always forthcoming with regard to documentation, but your suggestions are clearly contrary to what RTI has provided in the white paper. It is not my intention to be argumentative or confrontational, but this is ridiculously unclear.
Mike