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.

Database Install/Upgrade/Opatch (MOSC)

about: opatchauto apply -norestart

Aug 9, 2023 10:32PM in Database Install/Upgrade/Opatch (MOSC) 10 commentsAnswered ✓

19.18 Grid, DB. Linux

I didn't find much info on the use of -norestart option during opatchauto apply.

I need to apply patch1, patch2 in that order, can I follow the following approach to save time:

opatchauto apply <patch1-loc> -norestart

opatchauto apply <patch2-loc>

after the patch2, I expect the CRS/instances to be up.

Thanks in advance.

-Madhu S

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