I see that 26925263, 27322338 are common conflicts which you can roll back to apply couple of fixes first. Then reapply them. Sometimes it might be even possible that once you roll back these one-off are either included next patches you are applying or not needed for ETCC.
I dealt with similar situation in Super Cluster where I had to roll back several patches and apply back and forth. So remember to note down the sequence once you do it so that in PROD/Next iterations you don't have to work hard.
But that is so subjective, my mind can not analyze and comprehend that far.
Like this sample task below, how the support able to come out the action plan:
1 - Rollback Patches 20204035,, 26041567, 25128602, 22338374, 24568754
2 - Apply Patch 28729169
3 - Apply the following:
Patch 25906117 - version 188.8.131.52.0
Patch 29171320 - version 184.108.40.206.190115
Patch 27720266 - version 220.127.116.11.180417
Patch 29171350 - version 18.104.22.168.190115
Patch 25099339 - version 22.214.171.124.180417
Patch 25305405 - version 126.96.36.199.160119
Patch 28682351 - version 188.8.131.52.5
Patch 20123899 - version 184.108.40.206.5
Patch 28790654 - version 220.127.116.11.0
I better leave my database alone or raise SR to support to do the analysis in applying PSU patches like the one above.
I better leave my database alone or raise SR to support to do the analysis in applying PSU patches like the one above. - I agree with you!