For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!
Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.
All it says “DBA_SQL_ERROR_MITIGATIONS describes automatic error mitigations for SQL statements.” We can also find new init.ora parameter SQL_ERROR_MITIGATION. But I couldn't find any documetation on how automatic error mitigation works.
DBA_SQL_ERROR_MITIGATIONS
SY.
Hi Salomon,
please have a look at this blog post written by @ulrike-schwinn-oracle :
https://blogs.oracle.com/coretec/post/easy-sql-statement-tracking-in23c
I hope this answers your question, if not, please shout!
- Martin
@martinbach-oracle - No, it doesn't answer my question. Article you pointed to shows uses:
SQL> alter system set sql_history_enabled=true scope=both;
And in my post I said “Works fine when enabled on system level”. My question was about
SQL> ALTER SESSION SET SQL_HISTORY_ENABLED = TRUE;
where I showed SQL history was NOT captured even though it should be based on SQL_HISTORY_ENABLED:
Modifiable **ALTER SESSION**, ALTER SYSTEM
**ALTER SESSION**
ALTER SYSTEM
As per the article I shared the situation is as follows at the moment
sql_history_enabled
I'm currently assessing if that's intended behaviour (in which case the documentation should be amended) or a feature not working as it should (in which case it needs fixing). The parameter is indeed session-modifyable, but not in the sense you expected.
We'll keep you posted.
Do you mean it must be enabled on system level and not on session level and all session can do is disabe it for the session?
Yes,
that's correct as of Oracle Database Free 23.6.
Thanks Martin, I hope this will be added to 23AI docs soon.