Urgent.News

What's breaking now, across thousands of outlets.

Thursday, 22 October 2026 Reading Room

Tech

Automatic maintenance tasks controls the automatic optimizer statistics

Query to check the current state of jobs in CDB_AUTOTASK_CLIENT of the database, auto optimizer stats collection job is disabled in PDBs. SELECT COALESCE ( p . name , ( SELECT name FROM v $ database )) AS DATABASE , CASE WHEN c . con_id = 1 THEN 'CDB' WHEN c . con_id = 2 THEN 'SEED' ELSE 'PDB' END AS type_db , c . client_name , c . status , c . attributes FROM cdb_autotask_client c LEFT JOIN v $…

dev.to ·

The auto optimizer statistics collection job is disabled in PDBs (Portable Database Instances) by default, according to the database configuration. This can be confirmed by querying the CDB_AUTOTASK_CLIENT view, which shows that the job is enabled by default in the CDB (Common Database) but disabled in the PDBs. Specifically, the auto optimizer stats collection job is set to ENABLED ON BY DEFAULT, VOLATILE, SAFE TO KILL in the CDB, while it is DISABLED ON BY DEFAULT, VOLATILE, SAFE TO KILL in both PDB1 and PDB2.

Furthermore, the CDB_AUTOTASK_WINDOW_CLIENTS view reveals the configured windows for autotask activities in each database. In the CDB, all windows (FRIDAY_WINDOW, MONDAY_WINDOW, SATURDAY_WINDOW, SUNDAY_WINDOW, THURSDAY_WINDOW, TUESDAY_WINDOW, and WEDNESDAY_WINDOW) have an autotask status of ENABLED. However, in PDB1, only the FRIDAY_WINDOW has an enabled status, while the other windows are DISABLED. Similarly, in PDB2, all windows are DISABLED.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

The Python ML Cheat Sheet Repo You'll Actually Use

Every ML beginner hits the same wall: you know what you want to do, but you can't remember the exact syntax. Is it fit_transform or transform ? Which scaler do I use for outliers?

  • Nine comprehensive cheat sheets cover every step of the ML process
  • Foundation includes NumPy guides on arrays, indexing, broadcasting, and linear algebra
  • Scikit-learn catalogues popular models with pipelines for cross-validation and hyperparameter tuning

·dev.to

Charts as Epistemic Actions: Why Data Agents Need Visual Reasoning, Not Just Text Loops

Most data agents run ReAct loops that turn every intermediate reasoning step into text tokens. They query databases, summarize results, and chain tool calls, but they rarely generate or consume visual…

  • Charts are epistemic actions aiding agents in discovering next knowledge needs.
  • ReAct-style agents serialize intermediate states into text, missing visual reasoning.
  • Adding plotting tools to agents is simple, but getting them to use effectively is challenging.

·dev.to

Graphify: AST-Based Knowledge Graphs for Agent Code Navigation

Agents need to navigate codebases, SQL schemas, and documentation to answer questions like "which functions call this API endpoint?" or "what tables does this migration touch?" Vector embeddings give…

  • Graphify provides AST-based knowledge graphs for agent code navigation.
  • Unlike vector embeddings, Graphify preserves structural relationships through deterministic edges.
  • The system parses code into ASTs, extracts entities, and offers query tools for agents.

·dev.to

Our terms notice has no Agree button, because carrying on is the acceptance

Terms change. The question nobody enjoys answering is what should happen to the accounts that are already signed in. The common answers are all a bit wrong.

  • Nakodo presents updated terms and privacy notices without an Agree button.
  • By continuing to use the service, user accepts updated terms automatically.
  • Acceptance recorded through continued service use, not forced interaction.

·dev.to

More from Thursday 22 October →