Datapatch Failed Due to Invalid Logminer objects left over from Last failed rollback
(Doc ID 3076887.1)
Last updated on MARCH 17, 2025
Applies to:
Oracle Database - Enterprise Edition - Version 19.25.0.0.0 and laterOracle Cloud Infrastructure - Exadata Cloud Service - Version N/A and later
Gen 2 Exadata Cloud at Customer - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Information in this document applies to any platform.
Symptoms
Invalid objects related to Log Miner:
OWNER OBJECT_NAME OBJECT_TYPE
SYS DBMS_LOGMNR_INTERNAL PACKAGE BODY
SYS LOGMNR_KRVRDLUID3 PROCEDURE
SYS LOGMNR_KRVRDREPDICT3 PROCEDURE
SYS DBMS_LOGMNR_FFVTOLOGMNRT PROCEDURE
SQL> show errors
Errors for PACKAGE BODY SYS.DBMS_LOGMNR_INTERNAL:
LINE/COL ERROR
-------- -----------------------------------------------------------------
2319/7 PL/SQL: SQL Statement ignored
2322/33 PL/SQL: ORA-00942: table or view does not exist
2347/11 PL/SQL: Statement ignored
2347/34 PLS-00364: loop index variable 'TABLE_NAME_REC' use is invalid
10767/3 PL/SQL: SQL Statement ignored
10835/35 PL/SQL: ORA-00904: "SAI"."PDBUID": invalid identifier
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 |