Idea ID 1646189
Our issue: When updating HP OO and having the DB Schema changed by this update, we can't perform this update without a Downtime to our environment. Even if we install a second OO Central, it won't work, as both are using the same DB Schema.
Our suggestion to solve this issue: Enhance HP OO to handle DB Schemas with backwards compatibility based on a flag set during update:
When updating, hand over a parameter (like '-noDBS') and the update will not touch the DB Schema and will set the flag to active.
The updated OO is now working in compatibility mode with old DB Schema as well.
When updating last one, do not hand over the parameter and the DB Schema will be updated as well.
Remove the flags from the previous updated OOs to set them to the new DB Schema version only.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.