We may see shows unsupported datatype as V$LOGMNR_CONTENTS column "SCN" is the LAST SCN we see for the chained row change.

(Doc ID 1228844.1)

Last updated on OCTOBER 29, 2010

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.4 and later   [Release: 10.2 and later ]
Information in this document applies to any platform.

Goal

LogMiner started with a particular startscn returns unsupported data.

When the startscn is shifted backward then the same records are visible properly.

For example, few DMLs of the transaction at the scn (17773077077) provided at startScn during mining are not included in the output i.e. UNSUPPORTED.

But we are able to retrieve it when the startScn is shifted backward (17773077070).

Case-I
--------
begin
SYS.DBMS_LOGMNR.START_LOGMNR(
StartScn => 17773077077,
endScn => 17773077090,
OPTIONS => SYS.DBMS_LOGMNR.DICT_FROM_ONLINE_CATALOG
);
end;

UNSUPPORTED Unsupported Unsupported EFORMDYNAMICFIELDINSTANCE 2010-08-12 12:09:25 PMSDEVBI 0 17773077077 AAAAAAAAFAAEpolAAH 0 19 984
UNSUPPORTED Unsupported Unsupported EFORMDYNAMICFIELDINSTANCE 2010-08-12 12:09:25 PMSDEVBI 0 17773077077 AAAAAAAAFAAEpolAAH 0 21 928

Case-2
--------
begin
SYS.DBMS_LOGMNR.START_LOGMNR(
StartScn => 17773077076,
endScn => 17773077090,
OPTIONS => SYS.DBMS_LOGMNR.DICT_FROM_ONLINE_CATALOG
);
end;

UPDATE update "PMSDEVBI"."EFORMDYNAMICFIELDINSTANCE" ....17773077077
UPDATE IELD138" IS NULL and "FIELD139" IS NULL ......17773077077

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms