expdp导出报错！！ 打完补丁记着要开启
ORA-00600: internal error code, arguments: [qosdExpStatRead: expcnt mismatch], [65969], [433], [85888], [1], [], [], [], [], [], [], []
----------
I confirmed there are two bugs to match this issue now.
ORA-00600 [qosdExpStatRead: expcnt mismatch] will happen even after applied both patch 28681153 and patch 31143146,
if you don't try the workaround of MOS
Note 28681153.8
at both CDB and PDB.
- ORA-600: [qosdexpstatread: expcnt mismatch] (
Doc ID 28681153.8
)
- ORA-600: [qosdexpstatread: expcnt mismatch] even after applying 28681153 (
Doc ID 31143146.8
)
Please follow these steps to check if the issue resolves.
1. Try workaround of MOS
Note 28681153.8
at both CDB and PDB.
With b as (
select count(*) cnt,objn,snapshot_id from sys.exp_stat$ es group by
objn,snapshot_id)
select * from sys.exp_obj$ a, b where a.objn=b.objn and
a.snapshot_id=b.snapshot_id
and a.EXP_CNT<>b.CNT;
delete from sys.exp_stat$ b
where b.snapshot_id =
update sys.exp_obj$ a
set a.EXP_CNT=0
where a.SNAPSHOT_ID=
and a.objn =
commit;
2. Run below SQL again to check the query result. "no rows return" is expected.
With b as (
select count(*) cnt,objn,snapshot_id from sys.exp_stat$ es group by
objn,snapshot_id)
select * from sys.exp_obj$ a, b where a.objn=b.objn and
a.snapshot_id=b.snapshot_id
and a.EXP_CNT<>b.CNT;
3. Turn on the fix control of patch 31143146 as following:
alter system set "_fix_control"='31143146:on' scope=both;