home.social

#oracledatabase — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #oracledatabase, aggregated by home.social.

  1. 📢 [Sponsored Post] Registration for Oracle CloudWorld 2025 is open!

    Join in on Oct 13–16 in Las Vegas to explore 900+ sessions, keynotes & networking.

    🎟️ Save $700 by June 16!
    👉 Register now: apex.oracle.com/go/oug/oug-ocw

    #ocw #cloudworld #oracledatabase

  2. 🚀 Dive into Distributed Tracing with Helidon, Coherence, and Oracle Autonomous Database using OpenTelemetry!

    In this article, Ali Mukadam explains how to enhance observability in modern applications. A must-read for developers and architects!

    📖 Read it here: medium.com/helidon/distributed

    #DistributedTracing #OpenTelemetry #Helidon #Coherence #OracleDatabase #Tech #Observability

  3. #OracleDatabase 23ai for on-premises #Exadata, offloading AI vector searches, and 17 microsecond latencies... OH MY. I am living in the future.
    blogs.oracle.com/exadata/post/

  4. #Oracle will interconnect with #Google’s #cloud to make its #database services more widely available.

    Initial regions to participate: Sydney, Melbourne, São Paulo, Montreal, Frankfurt, Mumbai, Tokyo, Singapore, Madrid, London, and Ashburn.

    infoworld.com/article/3715540/

    #OracleDB #oracledatabase

  5. Storage performance with #OracleDatabase on #Exadata can be mysterious, confounding, and outstanding especially when you have both DBRM and IORM active with multiple databases. Having a CDB-level Global AWR can give you all the deets on both layers to see what may and may not be happening. This new whitepaper from Oracle tells you more.
    oracle.com/docs/tech/database/

  6. Even on #Exadata, it will take a while to read 30+ TB from 3 tables. I think there is probably a way to optimize this query from an #OracleDatabase perspective. 🤨

  7. Really, Bard? At least tell me you're being aspirational or telling me what I want to hear. AFAIK there have never been nor can I find any reference to these #OracleDatabase parameters that could indirectly control behavior on #Exadata. 🙄

  8. Each day that goes by when I'm running queries on #OracleDatabase #Exadata, I hope that I will actually run into a case of "Delayed Block Cleanout" that I can confirm wrecks the performance of my query. 🤨

  9. In the "Is it a bug or a feature?" department -- in Oracle Database 23c (developer edition), the DBA role grants privileges (directly or via another role) to see tables owned by SYS in ALL_TABLES, but cannot see triggers owned by SYS in ALL_TRIGGERS. This has changed since 19c.
    #OracleDatabase #BugOrFeature

  10. In the "Is it a bug or a feature?" department -- in Oracle Database 23c (developer edition), the DBA role grants privileges (directly or via another role) to see tables owned by SYS in ALL_TABLES, but cannot see triggers owned by SYS in ALL_TRIGGERS. This has changed since 19c.
    #OracleDatabase #BugOrFeature

  11. In the "Is it a bug or a feature?" department -- in Oracle Database 23c (developer edition), the DBA role grants privileges (directly or via another role) to see tables owned by SYS in ALL_TABLES, but cannot see triggers owned by SYS in ALL_TRIGGERS. This has changed since 19c.
    #OracleDatabase #BugOrFeature

  12. In the "Is it a bug or a feature?" department -- in Oracle Database 23c (developer edition), the DBA role grants privileges (directly or via another role) to see tables owned by SYS in ALL_TABLES, but cannot see triggers owned by SYS in ALL_TRIGGERS. This has changed since 19c.
    #OracleDatabase #BugOrFeature

  13. In the "Is it a bug or a feature?" department -- in Oracle Database 23c (developer edition), the DBA role grants privileges (directly or via another role) to see tables owned by SYS in ALL_TABLES, but cannot see triggers owned by SYS in ALL_TRIGGERS. This has changed since 19c.
    #OracleDatabase #BugOrFeature

  14. Bloom filters on #OracleDatabase #Exadata can be offloaded IF the datasets are "small enough". What is "small enough"? And what about those ~10 hidden parameters that control bloom filters? Even my biggest Exadata customers can't get a clue from Oracle Development, and it's really ticking me off. 🤬