Got Invalid Object SYSTEM.DM_RAT_* After Run Data Masking Script
(Doc ID 2852851.1)
Last updated on SEPTEMBER 08, 2024
Applies to:
Enterprise Manager for Oracle Database - Version 13.4.0.0.0 and laterOracle Database Cloud Exadata Service - Version N/A and later
Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Gen 2 Exadata Cloud at Customer - Version All Versions and later
Information in this document applies to any platform.
Goal
After run the Data Masking Script, it created the one invalid object with name like DM_RAT_xxx( this is random number for each run).
Run EXEC UTL_RECOMP.recomp_paralle did not fix anything.
This time only run masking script once and have one invalid object so far.
SQL> select owner, object_name, object_type, status, TIMESTAMP from dba_objects where status like '%INV%';
OWNER OBJECT_NAME OBJECT_TYPE STATUS TIMESTAMP
--------------- --------------- --------------- --------------- --------------------
SYSTEM DM_RAT_455 PACKAGE BODY INVALID 2021-08-16:10:32:42
SQL> EXEC UTL_RECOMP.recomp_parallel(4, 'SYSTEM');
PL/SQL procedure successfully completed.
SQL> select owner, object_name, object_type, status, TIMESTAMP from dba_objects where status like '%INV%';
OWNER OBJECT_NAME OBJECT_TYPE STATUS TIMESTAMP
--------------- --------------- --------------- --------------- --------------------
SYSTEM DM_RAT_455 PACKAGE BODY INVALID 2021-08-16:16:01:53
How to fix it ? Is there any workaround for this ?
Solution
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
| Goal |
| Solution |
| References |