Skip to Main Content

Core Infrastructure

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.

IMDS does not include preemptible action state (but OKE termination handler does)

Jakub KoralewskiJan 21 2025

Description of OKE node termination handler contains reference to IMDS containing preemption event data, but checking myself on a running preemptible instance I don't see any tag that specifies whether the instance is being terminated.

Quote in question:

> OKE automatically deploys an OCI node termination handler to each preemptible instance in your cluster, so you don’t have to build automation and deploy yourself. The termination handler runs as a daemonset on each preemptible instance and polls the Instance Metadata service (IMDS) every two seconds to detect a preemption event on the preemptible node. If a preemption event is detected, the node is terminated in two minutes from the time the preemption event was created.

https://blogs.oracle.com/cloud-infrastructure/post/reduce-your-kubernetes-costs-preemptible-nodes

Metadata docs don't contain any reference to preemptible action events: https://docs.oracle.com/en-us/iaas/Content/Compute/Tasks/gettingmetadata.htm#metadata-keys__instance

Preemptible instance docs only say that you can use Events: https://docs.oracle.com/en-us/iaas/Content/Compute/Concepts/preemptible.htm#howitworks__events

AWS supports both EventBridge and instance approach (plus you say OKE uses this metadata already + ChatGPT hallucinates as if you already have this) so either it's something I'm not seeing in the instance metadata or it's a hidden feature?

This post has been answered by Jakub Koralewski on Jan 23 2025
Jump to Answer

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 Jan 21 2025
1 comment
40 views