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?
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)