Hi Mike,

Just to update you about our last problem we had after last Security Patch 2024, we ran where we had a mismatch of database and inventory release number. So, we ran the first quartely SP 2025 which fixed the problem, we 19.26.0.0.0 between database and inventory catalog.
Thank you

Hi Mike,
Regarding bug number, no I didn't get one. And yes I can confirm you that the SR has been closed my support team

Hi Mike,
Happy new year.
I assume, you didn't get the time to have a look into SR.
Never mind.
Just, one question : Do you think that mismatch on full_version value between inventory and v$database will be fixed when next first quartely security patch on 2025 will be applied ?
Thank you

Sure
SR 3-38852010251

Hi Mike,
Thank you for your feedback.
Yes, we started by opening an SR but all attempts and suggestions failed.
At this time, we are on freeze period and will resume "datapatch -verbose" during a week-end as suggested lastly by Oracle support.
Thank you

Do you think, we have to rollback all patches numbers from db_home and re-apply them again on db_home ?
Oracle support asked us to résumé datapatch but we had registre composants with invalid status. I had to fix XML and XDB. XDB fixed by adding Oracle Text component.
Thank you

And v$sqlpatch shoping status "with errors" about patch number.And "datapatch -sanity_checks" failed with errors like "opatch directrices unable to déterminer on remote node".Drop/create ooatch directrices d'if not help.