Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Patch Reviews - DB (MOSC)

Doc ID 2925054.1

Apr 28, 2023 8:47AM edited Apr 28, 2023 8:53AM in Patch Reviews - DB (MOSC) 2 commentsAnswered

Hello, my problem is exactly the one described in the article. I completed the steps suggested in "Solution" but the problem is exactly the same: after relaunching opatchauto the "opatchautocfg" directory is recreated identical to before, with OH 12.1 instead of 19

0

Howdy, Stranger!

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

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

Category Leaderboard

Top contributors this month