Skip to Main Content
  • Questions

  • LogMiner REDO_SQL missing WHERE clause

Breadcrumb

Connor and Chris will both be at AI World from October 12 to October 17 , the premier Oracle conference of 2025. If you're in Vegas, please come say Hi or pop into our sessions

Question and Answer

Connor McDonald

Thanks for the question, Chris.

Asked: March 04, 2021 - 7:39 pm UTC

Last updated: March 10, 2021 - 1:35 am UTC

Version: 19.5.0.0.0

Viewed 1000+ times

You Asked

I came across a unique LogMiner situation recently where the mined redo log entry generated a REDO_SQL for an update that contained the SET-clause however there was no WHERE-clause, i.e.

update "SCHEMA"."TABLE" set "COL1" = '25', "COL2" = '45', "COL3" = NULL;


The table has full supplemental logging enabled, has approximately 2 dozen or so columns, contains over 95 million rows, and all columns are either of NUMBER, VARCHAR2, or DATE data types. Can anyone explain why the reconstructed REDO SQL does not contain a WHERE-clause?

and Connor said...

There's a few notes on MOS about REDO_SQL becoming garbled under certain conditions, but I've never seen one where the WHERE clause is just simply dropped.

If you have a test case you can reproduce it with, then it would be worth logging a call with Support (and perhaps posting it here as a comment so we can test it too)

Is this answer out of date? If it is, please let us know via a Comment
more

Connor and Chris don't just spend all day on AskTOM. You can also catch regular content via Connor's blog and Chris's blog. Or if video is more your thing, check out Connor's channel and Chris's channel from their Youtube channels. And of course, keep up to date with AskTOM via the official twitter account.

More to Explore

Utilities

All of the database utilities are explained in the Utilities guide.