1 person found this helpful
What user is the Author of the compliance rule? I am guessing it is SYSMAN.
If so, there is a bug in which non-SA users cannot save changes to rules/standards/frameworks for which they are not the author regardless of roles/privileges.
If you add Super Administrator to the user you will be able to save changes to that rule even not being owner. I am not suggesting this as a workaround but just saying this is something you can do to verify the bug.
We will get this fixed as soon as possible.
I apologize for the delay in responding. Your response never showed up in my communications tab and I didn't manually check this thread again until now.
I've tried this a few different ways, both attempting to edit a compliance rule owned by SYSMAN and another compliance rule owned by my regular, non-super administrator account. The rule edit did not stick either way, so it seems I am unable to edit rules even if my account is the owner. I did file a sev-4 SR on this (3-7587998331) and the support analyst made the same suggestion that you did, to try editing the rule as a super administrator account that is not SYSMAN. That succeeded as expected.
I've just uploaded some OMS debug logs to the SR taken while attempting to edit a rule, where I see an ORA-20221 coming from SYSMAN.EM_CHECK line 120. This may be the same, or a different bug, since you mentioned that you would expect a non-SA user to be able to edit a rule which they do own, which is not what I'm seeing.
Thank you for the response!