EM 13c: Corrective Action Association Entry In Mgmt_corrective_action View Get Changed To <USERID> When Synced Via Admin Group
(Doc ID 2941383.1)
Last updated on APRIL 14, 2023
Applies to:
Enterprise Manager for Oracle Database - Version 13.5.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
Corrective Action is created and added to Monitoring Template. Once Monitoring Template is associated and synced via Admin Group, the CA_OWNER under sysman.mgmt_corrective_action view changes from SYSMAN to <UserID>.
i.e.
SQL> select * from sysman.mgmt_corrective_action where CA_NAME like 'TEST3%';
JOB_ID CA_NAME CA_SCOPE CA_TARGET_GUID CA_TEMPLATE_GUID CA_REFERENCE_COUNT CA_OWNER PUBLISHED VERSION
-------------------------------- ---------------------------------------------------------------- ---------- -------------------------------- -------------------------------- ------------------ ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ---------- ----------
F86EF2D158B358D0E0534724410A90B5 TEST3 CA 2 BE5D6DECDE010FA7C718E9A6D7F0CF38 1 SYSMAN 0 1
F86EFF18E3C759EDE0534724410A6FD5 TEST3 CA 4 0 SYSMAN 1 1
F86EFF18E3D859EDE0534724410A6FD5 TEST3 CA 2 7A8411B54236CAE178C77AE096FF8A95 2 SYSMAN 0 1
F86EFF18E3E159EDE0534724410A6FD5 TEST3 CA 5 194B9D91C065AF7BAE2E0A2314603493 1 SYSMAN 0 1
After Admin group sync
SQL> select * from sysman.mgmt_corrective_action where CA_NAME like 'TEST3%';
JOB_ID CA_NAME CA_SCOPE CA_TARGET_GUID CA_TEMPLATE_GUID CA_REFERENCE_COUNT CA_OWNER PUBLISHED VERSION
-------------------------------- ---------------------------------------------------------------- ---------- -------------------------------- -------------------------------- ------------------ ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ---------- ----------
F86EF2D158B358D0E0534724410A90B5 TEST3 CA 2 BE5D6DECDE010FA7C718E9A6D7F0CF38 1 <USERID> 0 1
F86EFF18E3C759EDE0534724410A6FD5 TEST3 CA 4 0 <USERID> 1 1
F86EFF18E3D859EDE0534724410A6FD5 TEST3 CA 2 7A8411B54236CAE178C77AE096FF8A95 2 <USERID> 0 1
F86EFF18E3E159EDE0534724410A6FD5 TEST3 CA 5 194B9D91C065AF7BAE2E0A2314603493 1 <USERID> 0 1
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 |
| Cause |
| Solution |