We have a system to use Oracle flashback data archive flashback data archiving features as a recovery mechanism based on point in time, the frequent inserts, updates found during SYS_FBA_HIST_NNNN XID is the reuse of the two transactions in the table, result in start_scn are the same, so as the execution of the SCN/timestamp query, will come out two records of the same rowid, whether Oracle 11.2.0.4 or Oracle can reproduce 18 c, the former almost 100%, which is much lower probability (first LZ local ran for four or five times with 18 c did not appear, the thought settled, then test and verify out), metalink account was stopped because of the company, so I can only ask for help, trouble you are MOS accounts of classmates or schoolmates help to check whether the bug, or the corresponding patch, complete reproduce phenomenon sample is as follows:
The create flashback archive default fda_test_1day in tablespace 1 day "the USERS" retention;
The create table xyz_test (
C_tenantid varchar2 (20) DEFAULT 'NOT NULL,
C_tacode varchar2 (2) the DEFAULT ',
C_fundacco varchar2 (12) the DEFAULT ',
C_agencyno varchar2 (9) the DEFAULT ',
C_netno varchar2 (9) the DEFAULT ',
C_tradeacco varchar2 (24) DEFAULT ',
C_fundcode varchar2 (12) the DEFAULT ',
C_sharetype char (1) the DEFAULT ',
D_cdate number (8, 0) DEFAULT is 0,
C_cserialno varchar2 (20) DEFAULT 'NOT NULL,
C_sourcetype char (1) the DEFAULT ',
F_remainshares number (16, 2) 0.0, the DEFAULT
D_registdate number (8, 0) DEFAULT is 0,
F_oricfmbalance number (16, 2) 0.0, the DEFAULT
F_oricfmshares number (16, 2) 0.0, the DEFAULT
F_orinetvalue number (7, 4) 0.0, the DEFAULT
C_orisource char (1) the DEFAULT ',
F_ruleagio number (5, 4) 1.0, the DEFAULT
F_oriagio number (5, 4) 1.0, the DEFAULT
F_maxallotratio number (5, 4) 0.0, the DEFAULT
F_minredeemratio number (5, 4) 0.0, the DEFAULT
C_holdflag char (1) the DEFAULT ',
C_acceptmode char (1) the DEFAULT ',
C_firstcserailno varchar2 (20) DEFAULT ',
C_fundmethod varchar2 (2) the DEFAULT ',
C_bankno varchar2 (60) DEFAULT ',
C_subfundmethod varchar2 (2) the DEFAULT ',
F_managefare number (16, 2) 0.0, the DEFAULT
F_interestshare number (16, 2) 0.0, the DEFAULT
D_lastdeductdate number (8, 0) DEFAULT is 0,
F_income number (16, 2) 0.0, the DEFAULT
F_newincome number (16, 2) 0.0, the DEFAULT
C_specialcode varchar2 (20) DEFAULT ',
F_pendsubmit02shr number (16, 2) 0.0, the DEFAULT
F_pendsubmit03shr number (16, 2) 0.0, the DEFAULT
F_pendsubmit50shr number (16, 2) 0.0, the DEFAULT
F_assignshare number (16, 2) 0.0, the DEFAULT
F_pendsubmit13shr number (16, 2) 0.0, the DEFAULT
F_pendsubmit16shr number (16, 2) 0.0, the DEFAULT
F_lastremainshares number (16, 2) 0.0, the DEFAULT
F_pendsubmit14shr number (16, 2) 0.0, the DEFAULT
F_pendsubmit15shr number (16, 2) 0.0, the DEFAULT
F_lastincome number (16, 2) 0.0, the DEFAULT
D_orilastdeductdate number (8, 0) DEFAULT is 0,
F_costprice number (15, 12) 0.0, the DEFAULT
F_lastmanagefare number (16, 2) 0.0, the DEFAULT
F_apportionratio number (9, 8) 0.0, the DEFAULT
F_fareratio number (5, 4) 0.0, the DEFAULT
F_backfareratio number (9, 8) 0.0, the DEFAULT
F_minbackratio number (5, 4) 0.0, the DEFAULT
F_orifareratio number (5, 4) 0.0, the DEFAULT
D_cyclestartdate number (8, 0) DEFAULT is 0,
D_cycleenddate number (8, 0) DEFAULT is 0,
D_cyclenextdate number (8, 0) DEFAULT is 0,
L_cycle number (10, 0) DEFAULT is 0,
F_evennetvalue number (7, 4) 0.0, the DEFAULT
C_protectflag char (1) the DEFAULT ',
F_backfare number (16, 2) 0.0, the DEFAULT
F_costfare number (16, 2) 0.0, the DEFAULT
C_lastoutfundcode varchar2 (20) DEFAULT ',
F_redeemedbaseshr number (16, 2) 0.0, the DEFAULT
nullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnull