Answer / guest

Cause: Some AWR tables encountered errors while taking one
ore more snapshots in the given range. The missing table,
being one of the key tables that ADDM looks at, renders ADDM
unable to run.

Action: Look in DBA_HIST_SNAP_ERROR to find what tables are
missing in the given snapshot range. Use the ERROR_NUMBER
column in that view together with the alert log to identify
the reason for failure and take necessary action to prevent
such failures in the future. Try running ADDM on a different
snapshot range that doesn't include any incomplete snapshots.

Please add more information about this Error

ORA-24042: no propagation schedule exists for QUEUE string and DESTINATION string

2 Answers  

---

NNF-01003: DCE could not find cell name

1 Answers  

---

ORA-29746: Cluster Synchronization Service is being shut down.

1 Answers  

---

PCC-02385: CHAR_MAP disallowed when using NLS_CHAR and NLS_LOCAL=TRUE

1 Answers  

---

RMAN-06437: cannot drop catalog - catalog is newer than this RMAN

1 Answers  

---

SQL*Loader-00435: invalid constant value string for nested table column string

1 Answers  

---

LSX-00130: attribute "processContents" has invalid value "~S"

1 Answers  

---

PCC-00018: Expected "string", but found "string" at line number in file string

1 Answers  

---

ORA-04032: pga_aggregate_target must be set before switching to auto mode

1 Answers  

---

PCB-00556: Unrecoverable error. Fix previous errors and re-precompile

1 Answers  

---

PROT-00007: Failed to open the specified import file

1 Answers  

---

ORA-28118: policy group already exists

1 Answers  

---