"will it hunt down and touch/convert my Applications and Project schemas automatically?" Pretty sure it will not you should find the project databases show they need to be updated. I suggest you get in touch with support for best way to copy and replace tables, although there may be a guide somewhere here or in the blogs.
My general preference is something like your #2. Although I'd see if you couldn't just replace the project databases only or do project export/import on the final cut-over. Doing #1 is a little to close to this being this guy: http://www.troll.me/2011/05/15/the-most-interesting-man-in-the-world/i-dont-always-test-my-code-but-when-i-do-i-do-it-in-production/ I like my upgrades boring. Best, Tim On Monday, May 6, 2013 11:39:16 AM UTC-4, Richard Ota wrote: > > Hello Tim, > > Yes, the version that I am running is 10.1.2.321, which I do believe it is > spk 2, so it is good for the upgrade. > > Thanks. > > --Rich > > > On Friday, May 3, 2013 10:59:15 AM UTC-4, Tim D wrote: >> >> Are you on 10.1.2 or higher? >> >> On Friday, May 3, 2013 10:03:29 AM UTC-4, Richard Ota wrote: >>> >>> Hello, >>> >>> Yes, this has been a long trail of posts/emails but now it has come to a >>> head. I have been communicating with OpenText support and they have >>> provided good information about upgrade options. I have a VM to work with, >>> a single Oracle server, and a 2 month temp license. I also have a small >>> window to switch the VM to production as there is a need for minimal >>> downtime. >>> >>> 1. On the VM, build a copy of my WSM 10 (production) and utilize copies >>> of my production schemas (Oracle). Test to make sure it works. Perform the >>> standard upgraded, uninstall WSM 10, install the 64-bit Oracle client >>> (uninstall 32-bit Oracle client first), install/upgrade to WSM 11, then >>> test. Days/weeks later, this WSM 11 is using old data, so to get it ready >>> for the final switch to live data and make it the live server, restart the >>> entire process again with a new VM, freeze production, and point to new >>> copies of the production schema. Test and then switch the license and IP to >>> make it my production server. >>> The first VM iteration was to get the steps down and to make sure the >>> upgrade works. >>> >>> OR >>> >>> 2. On the VM, install a fresh WSM 11 and point to copies of my >>> production schemas (WSM 10). This will involve some type of schema updates >>> during the installation. Test to make sure it works. Days/weeks later, >>> Uninstall/reinstall WSM 11, and utilize copies of the production schemas >>> (WSM 10) -- production is now frozen to all changes. Test and then switch >>> the license and IP to make it my production server. >>> >>> My concerns are to not impact the production environment during the >>> install/upgrades to the VM. For #2, when I specify the WSM 10 >>> Administration schema, will it hunt down and touch/convert my Applications >>> and Project schemas automatically? Though I am working with copies of the >>> schemas, the Administration schema knows about the other schemas but not >>> about the copies of them. If it does not go well, then my production WMS 10 >>> is still working "perfectly". >>> >>> Thank you for all you feedback and hopefully, things will go well. >>> >>> --Rich Ota >>> >> -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/reddot-cms-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
