Skip to Main Content

Oracle Database Free

Announcement

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.

Remark on an “anomaly” in the eror messages for DOMAINS.

PDVBVDec 20 2024 — edited Dec 20 2024

When using Domain-Enum, there are two different error messages when you try to insert an invalid-item. Re-producing script available.

The first, somewhat confusing error, is when i used the Domain-definition as a Constant to insert the values:

ORA-00984: column not allowed here.

The more clear message is :

ORA-11534: check constraint (SCOTT.SYS_C009881) involving column COLOR due to domain constraint SCOTT.SYS_DOMAIN_C00352 of domain

I far more prefer the 2nd error. Although I can see why the first one would appear.

Any idea to change the error in first case ?

Script: demo_enum_6anomaly.sql

or https://drive.google.com/file/d/11bk1nGPd0hJyod-sQVO-fZamYNV6omQE/view?usp=sharing

note: the error-text is shorter, more concise in SQL*Plus. SQLcl adds a lot of helpful stuff, but this almost obscures the errors.

Screenshot:

Comments

MartinBach-Oracle Jan 8 2025

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

Solomon Yakobson Jan 8 2025

@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

SY.

MartinBach-Oracle Jan 8 2025

As per the article I shared the situation is as follows at the moment

  • You must enable SQL history PDB-wide (only a DBA can do that) so there's a certain level of control over the feature
  • Your session has access to the SQL history
  • If you don't want to record anything, set sql_history_enabled to false.

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.

- Martin

Solomon Yakobson Jan 8 2025

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?

SY.

MartinBach-Oracle Jan 14 2025

Yes,

that's correct as of Oracle Database Free 23.6.

- Martin

Solomon Yakobson Jan 14 2025

Thanks Martin, I hope this will be added to 23AI docs soon.

SY.

1 - 6

Post Details

Added on Dec 20 2024
1 comment
78 views