
How to Describe Types at Run Time with ANYTYPE
Find out at run time what type a value has, its name, and the name and type of each of its attributes.
Posts tagged AI-Assisted are created with support from artificial intelligence. I use AI tools to research, draft, and refine ideas—combining human insight with machine precision to deliver clear, informed, and creative content.

Find out at run time what type a value has, its name, and the name and type of each of its attributes.

Keep numbers, strings, dates, and objects in one column with ANYDATA, and read each value back according to its type.

Find out how full a table's blocks are, and estimate how much space a planned table of millions of rows will need.

Record which blocks of PL/SQL code your tests actually run, see the percentage covered, and find the untested branches.

Record every PL/SQL call and SQL statement while code runs, and find the functions and statements where the time goes.

See cached query results being reused, and check, flush, or invalidate the server result cache with DBMS_RESULT_CACHE.

Measure the work of one end user, module, or session with targeted statistics and SQL tracing, instead of the whole database.

Change how one table's statistics are gathered with preferences, and freeze them with a lock to keep plans stable.

Keep the optimizer's picture of your data current by gathering table, column, and histogram statistics after large changes.

See the plan a statement actually ran with, and compare the optimizer's estimated rows with the actual rows of each step.

Recompute the hash chain of a blockchain table to prove no row was changed, and delete rows once their retention ends.

Run a large UPDATE as many small committed chunks in parallel jobs, and resume the chunks that fail.

Partition a table or change its columns while it stays in use, with an interim table and DBMS_REDEFINITION.

Find the rows that differ between two copies of a table, then make one copy match the other with CONVERGE.

Make every query of a session see the database as it was at an earlier SCN or time, then return to the present.

Send PL/SQL values into JavaScript, compute with them, and read the results back into PL/SQL variables.

Evaluate JavaScript source at run time inside the database, run SQL from JavaScript, and find where JavaScript errors happened.

Build one search index over several tables and every column, and find matching rows in all of them with one query.