ASM : Current Policy Editon doesn't Work : Mysql Error

Hello Team,

I have an amazing behaviour on ASM with the display of the Current Security Policy. There is absolutely no way to switch to another policy so as to configure it or to fine tune the setup.

Even if it tries to load the selected policy , it fallbacks always to the previous one. So we are not able in our production environement to create a new policy or to fine tune an existing one !

I have some ASM logs which highlights some event related to Mysql :

dcc|ERR|Apr 30 07:00:01.014|3058| [DB::do_top_objects, ] Cannot add or update a child row: a foreign key constraint fails (

DCC

.

OVERVIEW_STAT_OBJECTS

, CONSTRAINT

OVERVIEW_STAT_OBJECTS_ibfk_1

FOREIGN KEY (

account_id

) REFERENCES

ACCOUNTS

(

account_id

) ON DELETE CASCADE)

dcc|ERR|Apr 30 07:00:01.014|3058| [DB::do_top_objects, ] mysql_stmt_execute, failed

This behaviour happens only on ASM and particularly on "Application Security ›› Policy : Policy : Properties" with the "Current edited policy" field of the GUI.

We haven't this behaviour on the reporting panel, we are able to select one policy an view the associated logs and violations.

Any help will be greatly appreciated !

Thks in advance !