Database Install/Upgrade/Opatch (MOSC)

MOSC Banner

datapatch through opatchauto in the last RAC node fails with locks in the database

in Database Install/Upgrade/Opatch (MOSC) 5 comments

Applying 19c April'21 PSU (19.11) on Linux x64

2 node RAC cluster

1 node completed successfully

while running opatchauto on the 2nd node, binary patches were successfully applied but the datapatch portion was running for over 20 minutes. When I reviewed session logs, the datapatch was attempting to acquire a lock on an object and since there were live transactions in the database, it failed to acquire lock.

Oracle support suggests to run datapatch after starting database in RESTRICT mode. Well, this is a RAC rolling patch install and I don't understand why should the database be taken down for datapatch? We had similar issues with 19c October'20 PSU and had to take databases down. But can't afford to take an outage every quarter.

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