DML DDL reported the solution of ORA-00600: [kntgMvLogObjn]

This article will explain in detail the solution of DML DDL report ORA-00600: [kntgMvLogObjn]. The content of the article is of high quality, so the editor will share it with you for reference. I hope you will have some understanding of the relevant knowledge after reading this article.

DML or DDL the table to ORA-00600: [kntgMvLogObjn].

(1) delete materialized view log first, and then DML or DDL the table.

Select * from dba_mviews

Select * from dba_mview_logs

Drop materialized view log on TABLE_NAME

(2) if the first step cannot be solved, then the MATERIALIZED VIEW LOG needs to be rebuilt.

Typically, the user or table has been renamed before. It may be that the information in data dictionaries such as obj$ is inconsistent.

You can refer to Doc ID 1612402.1 for one of the recommendations of Oracle for such problems is to use to rebuild the materialized view log, create it using with rowid, and then delete it.

SELECT * FROM sys.MLOG$

CREATE MATERIALIZED VIEW LOG ON TABLE_NAME WITH ROWID

Drop materialized view log ON TABLE_NAME

CauseThe MLOG$ entry didn't exist but the MLOG$_... Segment in OBJ$ still existed, and the table referenced in its flags that it uses a materialized view log.To implement a solution for this issue please execute the following steps in the given order:create a new materialized view log using CREATE MATERIALIZED VIEW LOG ON WITH ROWID