'FRM-40815' and 'ORA-04062' errors in OC following multiple patches being applied
(Doc ID 2524410.1)
Last updated on FEBRUARY 21, 2023
Applies to:
Oracle Clinical - Version 5.1.0 and laterOracle Thesaurus Management System - Version 5.1.0 and later
Information in this document applies to any platform.
Symptoms
Issue related to an OC/RDC 5.1 environment having 3 databases, only 2 of which have TMS installed (and so the database component of the TMS patches were only applied to those 2 databases).
All the 3 databases are sharing the same Middle Tier server.
In the database without TMS, after applying a set of patches , numerous FRM-40815 and ORA-04062 errors were shown when navigating the Oracle Clinical application; some examples are:
On login to OC:
Changes
Below patches were applied:
* Weblogic Patchset 26519424
* RDBMS Patch 21321210
* RDBMS Patchset 26636270
* Patch 25825851
* ADF Patch 24730407
* JDK 26595535
* Forms Patch 16920856
* Patch 22607090
* OHS Patch 17664562
* OHS Patch 17555224
* ADF Patch 16546129
Important observation: The following patches show up in one of the working databases and are NOT present in the non-working one:
OPA UPGRADE 5.1.1 0 511b3 12-JAN-2017 00:00:00 08-MAR-2019 06:36:05
OPA UPGRADE 5.1.2 0 512b7r3 12-JAN-2017 00:00:00 08-MAR-2019 06:37:15
TMS UPGRADE 5.1.1 0 511b3 12-JAN-2017 00:00:00 08-MAR-2019 06:37:34
TMS UPGRADE 5.1.2 0 512b7r3 12-JAN-2017 00:00:00 08-MAR-2019 06:41:55
Clarification: TMS was not installed in the "problematic" database. Note that any OC-specific patches have been applied consistently across the entire environment. It is only the TMS patches that are missing from the "problematic" database.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |