Skip to Main Content

E-Business Suite

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Oracle Documaker Patching Best Practices

KDLMay 7 2025 — edited May 7 2025

We find that we are spending a lot of time applying Oracle quarterly patches for the Oracle Documaker Windows servers, so we are curious what other customers are doing to maintain their Documaker environments.

Each of our environment consists of three Windows 2019 Standard servers.

  • Oracle Database SE 19c
  • Oracle WebLogic 12.2.1.4
  • Oracle Documaker 12.6.4

We have been applying the Oracle quarterly Critical Patch Update, which takes approximately 2-3 hours per server. We need to do this off hours and Documaker is unavailable while the patches are being installed. With four environments (DEVL, TEST, PROD, and User Acceptance), this takes a great deal of time each quarter.

We find the application of the Oracle Database CPU the most frustrating, since it usually involves rolling off a previous patch.

Are we missing something that would make it easier to apply patches, or is applying each quarterly Critical Patch Update when it is available not a common practice? Is high availability or clustering being used to perform patching without taking down systems?

Any suggestions or tips would be greatly appreciated.

Thank you,
Kevin

Comments
Post Details
Added on May 7 2025
5 comments
297 views