My Oracle Support Banner

OEM: Sysman.EM_COMPLIANCE_STANDARD_OP Package Body Is Invalid After Upgrading Repository Database (Doc ID 2759152.1)

Last updated on JANUARY 26, 2022

Applies to:

Enterprise Manager for Exadata - Version 13.4.0.0.0 and later
Information in this document applies to any platform.

Symptoms

OEM: sysman.EM_COMPLIANCE_STANDARD_OP package body is invalid after upgrading repository database
After upgrade OEM respository database from 12.1.0.2 to 19.6.1 one of the sysman package body is invalid.

SQL> r
 1  select owner, object_name, object_type
 2  from dba_objects
 3* where status = 'INVALID'

OWNER                            OBJECT_NAME                      OBJECT_TYPE
-------------------------------- -------------------------------- -----------------------
PUBLIC                           VW_SUBSCRIPTIONS                 SYNONYM
ORACLE                           VW_SUBSCRIPTIONS                 VIEW
SYSMAN                           EM_COMPLIANCE_STANDARD_OP        PACKAGE BODY
SQL> alter package sysman.EM_COMPLIANCE_STANDARD_OP compile body;

Warning: Package Body altered with compilation errors.

SQL> show errors
Errors for PACKAGE BODY SYSMAN.EM_COMPLIANCE_STANDARD_OP:

LINE/COL ERROR
-------- -----------------------------------------------------------------
2039/7   PL/SQL: SQL Statement ignored
2039/14  PL/SQL: ORA-00932: inconsistent datatypes: expected
        SYSMAN.EM_CS_HIERARCHY_OP got SYSMAN.EM_CS_HIER_MOVE_NODE

Changes

 upgrade OEM respository database from 12.1.0.2 to 19.6.1 happened

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
Changes
Cause
Solution


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