Database Install/Upgrade/Opatch (MOSC)

MOSC Banner

guidance and best practices as we prepare for the transition to a monthly Oracle security patching c

in Database Install/Upgrade/Opatch (MOSC) 1 comment

We are seeking guidance and best practices as we prepare for the transition to a monthly Oracle security patching cadence beginning May 28. To help us align our internal processes effectively, we would appreciate any detailed information or examples you can provide in the following areas:

  • Recommended customer approaches for structuring patching processes, including testing, rollout, and rollback strategies
  • Use of Oracle Enterprise Manager (OEM) or other tools to automate or streamline patching activities

 

Additionally, we would like guidance on patching strategies that could help minimize downtime. Specifically:

  • Is it possible to stage or apply Oracle security updates to the database without requiring an immediate restart?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center