Is There An Alternative Method To Patch Calendar Server In A "passive" Mode
Last updated on MAY 15, 2013
Applies to:Oracle Communications Calendar Server - Version 7.0 and later
Information in this document applies to any platform.
Calendar Server 7 with patch 9
The act of patching a calendar server that is not live in production requires a connection to the DB. And it seems that during the patching process, which then upgrades the schema, the patching process then potentially breaks the other un-patched servers in production that are talking to that same DB.
How can we achieve High Availability in this multi-host setup? Is there a way to patch in a 'passive' mode that either does not require a connection to the DB or does not perform the schema upgrade during the patching process? This would be a useful feature, since then, you could have some sort of config "option" or davadmin switch to tell the server to go ahead and perform the schema upgrade. This would allow you to patch servers out of the VIP, switch the VIP to those servers, and then issue the schema upgrade command.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms