Hi all,
I'm running EM12cR3 (12.1.0.3) on Linux x86-64 (SLES 11) with an 11.2.0.3.7 EE repository database.
Since upgrading to EM12cR3, it appears that I can no longer edit customized compliance standard rules as any user other SYSMAN. Doing so worked just fine with my regular administrator account (which has the EM_ALL_ADMINISTRATOR role) prior to the upgrade. If I edit the rule as SYSMAN, everything works as expected.
Does anybody else see similar behavior or have a fix for it? Is there perhaps some other role or privilege I am missing?
Here's what I've tried without any luck:
- Granting my user account the EM_COMPLIANCE_DESIGNER role
- Granting my user account the Create Compliance Entity, Full any Compliance Entity, and View any Compliance Framework EM resource privileges
- Creating a new user account with all of the mentioned privileges
- Logging out and bouncing the OMS between each of these steps
When I try to edit a compliance standard rule as a non-SYSMAN user I am able to step through the entire process, hit Save at the end, and I receive the message that the rule was updated successfully. But when I view the rule again afterward, I cannot see the changes. I have only confirmed that this happens when editing the SQL used to pull the compliance data out of the repository, I haven't checked if items like changing the rule priority are similarly impacted.