Forum Stats

  • 3,728,472 Users
  • 2,245,631 Discussions
  • 7,853,549 Comments

Discussions

EM13.5 with Oracle Database 19.11 on OL7 Fails badly

Stephen Windsor
Stephen Windsor Member Posts: 42 Blue Ribbon

hi, hope someone can help - no help from Tech support so far.

I have installed EM13.5 twice and EM13.4 five times, all install successfully but are NEVER configured and never run. Most of the times the EM internal jobs are SKIPPED forever.

Running the latest Oracle database 19.11. The database was created generic as there are no 13.5 templates. There are no space issues. No invalid objects. Nothing the EM13.5 install objected.

The FIRST error in the install is from the alert log of the database, OMR, in this case OEM2PROD, early on in the install.

2021-04-28T11:39:49.384497-04:00

Errors in file /oracle/oradata/OEM2PROD/trace/diag/rdbms/oem2prod/OEM2PROD/trace/OEM2PROD_j000_132312.trc:

ORA-12012: error on auto execute of job "SYSMAN"."COMPLIANCE_RE_EVAL_SCAP"

ORA-20421: find_queue(ComplianceAsyncMgr) queue does not exist

ORA-06512: at "SYSMAN.EM_JOB_QUEUE", line 149

ORA-06512: at "SYSMAN.EM_JOB_QUEUE", line 1246

ORA-06512: at "SYSMAN.GC_JOB", line 273

ORA-06512: at "SYSMAN.EM_COMPLIANCE_UTIL", line 9031

ORA-06512: at line 1

A duplicate of this error occurs at 2021-04-28T16:00:00.228549-04:00

Errors in file /oracle/oradata/OEM2PROD/trace/diag/rdbms/oem2prod/OEM2PROD/trace/OEM2PROD_j001_193017.trc:

ORA-12012: error on auto execute of job "SYSMAN"."COMPLIANCE_RE_EVAL_SCAP"

ORA-20421: find_queue(ComplianceAsyncMgr) queue does not exist

ORA-06512: at "SYSMAN.EM_JOB_QUEUE", line 149

ORA-06512: at "SYSMAN.EM_JOB_QUEUE", line 1246

ORA-06512: at "SYSMAN.GC_JOB", line 273

ORA-06512: at "SYSMAN.EM_COMPLIANCE_UTIL", line 9031

ORA-06512: at line 1


The trace file does not show much:

*** 2021-04-28T11:39:49.380645-04:00

*** SESSION ID:(586.6536) 2021-04-28T11:39:49.380681-04:00

*** CLIENT ID:() 2021-04-28T11:39:49.380687-04:00

*** SERVICE NAME:(SYS$USERS) 2021-04-28T11:39:49.380691-04:00

*** MODULE NAME:(DBMS_SCHEDULER) 2021-04-28T11:39:49.380696-04:00

*** ACTION NAME:(COMPLIANCE_RE_EVAL_SCAP) 2021-04-28T11:39:49.380702-04:00

*** CLIENT DRIVER:() 2021-04-28T11:39:49.380707-04:00

 

ORA-12012: error on auto execute of job "SYSMAN"."COMPLIANCE_RE_EVAL_SCAP"

<error barrier> at 0x7ffc97228ef0 placed [email protected]

ORA-20421: find_queue(ComplianceAsyncMgr) queue does not exist

ORA-06512: at "SYSMAN.EM_JOB_QUEUE", line 149

ORA-06512: at "SYSMAN.EM_JOB_QUEUE", line 1246

ORA-06512: at "SYSMAN.GC_JOB", line 273

ORA-06512: at "SYSMAN.EM_COMPLIANCE_UTIL", line 9031

ORA-06512: at line 1

=======================

Looking at the two tables,

WELL Let US look at EM_TRACE_DEBUG_E which has over 1.2 MILLION ROWS just for today!!!

AND what to all of those 1.2 million rows say??? THIS

Getting steps to be dispatched unexpectedly failed

Error: ORA-06530: Reference to uninitialized composite

ORA-06512: at "SYSMAN.EM_JOB_DISPATCH", line 1886


----- PL/SQL Call Stack -----

object line object

handle number name

0x87cf2160 947 package body SYSMAN.EMDW_LOG.STACK_TRACE

0x70ad3b90 694 package body SYSMAN.GC$OBJ_LOG.LOG

0x843c8a38 702 package body SYSMAN.EM_JOB_DIAG.LOG_EXCEPTION

0x843c8a38 762 package body SYSMAN.EM_JOB_DIAG.LOG_EXCEPTION

0x87bb5d18 1886 package body SYSMAN.EM_JOB_DISPATCH.GET_ALL_SCHEDULED_STEPS

0x83c0c1f8 1 anonymous block

==================================================


and here's the sister table, just as bad:


SELECT * FROM em_trace_critical_e WHERE TRUNC( log_timestamp ) = TRUNC( SYSDATE ) ORDER BY log_timestamp;


a couple rows from today - also ALL THE SAME ERROR


CONTEXT_TYPE_ID CONTEXT_IDENTIFIER MODULE OMS_HOST OBJ_GUID OBJ_NUM_DATA OBJ_STR_DATA LOG_TIMESTAMP LOG_LEVEL LOG_SUB_LEVEL LOG_VISIBILITY LOG_MESSAGE LOG_MESSAGE_ID LOG_MESSAGE_BUNDLE LOG_MESSAGE_PARAMS SID SERIAL# AUDSID

--------------- -------------------------------- ------------ -------- -------- ------------ ------------ ------------------------ --------- ------------- -------------- -------------------------------------------------- -------------- --------------------------------------------- --------------------------------------------------- --- ------- ------

21 Job System Daemons:JobDispatcher EM.jobs.diag (Null) (Null) (Null) (Null) 5/3/2021 01:22:16.596632 4 1 3 Getting steps to be dispatched unexpectedly failed EM-03151 oracle.sysman.resources.diag.jobs.JobsDiagMsg ('ORA-06530: Reference to uninitialized composite') 815 25633 279059

21 Job System Daemons:JobDispatcher EM.jobs.diag (Null) (Null) (Null) (Null) 5/3/2021 01:22:16.702919 4 1 3 Getting steps to be dispatched unexpectedly failed EM-03151 oracle.sysman.resources.diag.jobs.JobsDiagMsg ('ORA-06530: Reference to uninitialized composite') 815 25633 279059

21 Job System Daemons:JobDispatcher EM.jobs.diag (Null) (Null) (Null) (Null) 5/3/2021 01:22:16.705948 4 1 3 Getting steps to be dispatched unexpectedly failed EM-03151 oracle.sysman.resources.diag.jobs.JobsDiagMsg ('ORA-06530: Reference to uninitialized composite') 815 25633 279059


I've checked database sizing and parameters three times already.


Any ideas? I think the errors above are the symptom, but there's no information on any of these :(

Thank you, Frustrated Steve

Sign In or Register to comment.