LogMiner Returns Wrong Delete SQL_REDO Statement For BLOB Datatype
(Doc ID 2179380.1)
Last updated on AUGUST 04, 2018
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
LogMiner returns wrong sql_redo for BLOB data type as shown below:
PRIMARY KEY ("ID")
LOB ("DEVICEOBJECT") STORE AS BASICFILE (
TABLESPACE "USERS" ENABLE STORAGE IN ROW CHUNK 8192 RETENTION
SQL> insert into LOGDEVICE values ('aaa',1);
1 row created.
SQL> delete from LOGDEVICE where id =1;
1 row deleted.
By mining the corresponding redo log the output from v$logmnr_contents shows the following statement for the DELETE sql executed above:( NOTE: the "and" in the where clause):
delete from "QATUSER"."LOGDEVICE" where and "ID" = '1'; >>>>>> we can see "and"immediately after where without a condition.
The correct sql_redo should look like below:
delete from "SCOTT"."LOGDEVICE" where "ID" = '1' and ROWID = 'AAATu8AABAAAZhZAAA';
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document