Will the patching cause an outage or service disruption?

[annmariechu]

Is there any outage or disruption when

[Lisa_Manchester · Accepted solution]

No. Your instance will remain online during the patching. Some performance impact may be observed, but there should be little to no impact after a patch has been applied.

[Mike McCall]

In the past, I've told our users that there will be a quick restart after any upgrade/patch has completed, so they can work during the upgrade process, but they may notice their session being lost at the end.

Will that still be the case? (Was that ever the case?)

[Lisa_Manchester]

I think the emphasis is on "may". It depends on how many nodes in your system and exactly what a user is doing at a very specific point. For example, on multi noded systems, if the user is performing a read operation while on a node that is restarting, they should be redirected to the node that is still online and not notice this change.   If they are making an update, they may see an error message stating that their session and submission tokens do not match and prompted to hit a continue button to continue the operation.

Some sub-prod systems only have one node and users on that system may lose their session at the end of the patching.

So, the safest thing is just to be aware that the patching is happening and that they may notice but it should not interrupt their work.

[Alex125]

Yes it can! Some patches can has bugs that course issue for your instance! So you need to do always testing after patching. Now it is forced to be 4 times a year besides the normal version upgrade.   So plan and test it very well!