My Oracle Support Banner

LogMiner Objects Are Invalid After Database Upgrade Or Catalog Rebuild (Doc ID 2207739.1)

Last updated on MARCH 03, 2021

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 to 12.1.0.2 [Release 11.2 to 12.1]
Information in this document applies to any platform.

Symptoms

LogMiner objects are invalid after database upgrade or during rebuild of catalog.

The following objects are left in invalid status:

SYS LOGMNR_DICT_CACHE PACKAGE BODY             INVALID
SYSTEM LOGMNR$KEY_GG_TABF_PUBLIC FUNCTION  INVALID
SYSTEM LOGMNR$SEQ_GG_TABF_PUBLIC FUNCTION  INVALID

SYS DBMS_LOGMNR_LOGREP_DICT PACKAGE BODY INVALID
DBMS_LOGMNR_SESSION PACKAGE BODY INVALID
LOGMNR_KRVRDREPDICT3 PROCEDURE INVALID
LOGMNR_KRVRDLUID3 PROCEDURE INVALID
DBMS_LOGMNR_FFVTOLOGMNRT PROCEDURE INVALID

 

Cause

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
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.