No. Just did it today but started creating a ‘New’ rather than demo database and stopped the process once the common DB was created.
3 Likes
Indeed. Just figured that out myself. Still used Demo but only checked the first item:
And if you have to upgrade many separate environments (as opposed to many appservers on the same DB), each time you can just delete the Ice Common DB, re-run task 200,and you’re good. Otherwise you get the issue Jose mentioned where it looks for ICECommon_4_3_1004_3_100 instead of ICECommon_4_3_100.
If you’re doing multiple AppServers on the same DB it seems fine. Sorry @josecgomez not sure if this should be a new thread at this point…
EDIT: Don’t take this to the bank… now I’m getting an error where upgrading an appserver WANTS ICECommon_4_3_1004_3_100 and can’t find it, and adding a demo or adding another DB with and without dropping ICECommon_4_3_100 does not create ICECommon_4_3_1004_3_100…
4 Likes
Yeah it’s a nightmare I hate this new common Db
3 Likes
Is it more a nightmare because it tries to re-create it for every conversion ran? I recall you did an extensive write up on it. Perhaps I’ll re-read.
The intent behind it is fine, the implementation with this whole READ ONLY setup is a head ache.
1 Like