Answer / guest

Cause: One or both of the workload tables are missing. The
two workload tables which should be present in the user's
schema are V_192216243_F_5_E_14_8_1 and
V_192216243_F_5_E_15_8_1; the former is mapped to
WORK$_IDEAL_MVIEW and the latter to WORK$_MVIEW_USAGE. The
workload tables are created by the Oracle Trace Formatter
when the data-collection-file (oraclesm.dat) is formatted by
the user.

Action: Check whether the Formatter succeeded in formatting
the data collection. Sometimes the V_192216243_F_5_E_14_8_1
(i.e WORK$_IDEAL_MVIEW) may not be created whereas the other
table is created. The most likely cause of this is the
init.ora parameters needed to invoke mview-rewrite are not
enabled. Check your

Please add more information about this Error

ORA-09787: sllfop: unrecognizable processing option, incorrect format.

1 Answers  

---

ORA-00023: session references process private memory; cannot detach session

2 Answers  

---

ORA-37020: (XSMULTI01) Analytic workspace string is not in MULTI mode.

1 Answers  

---

ORA-33313: (DELDENT05) workspace object cannot be deleted because it is the target of an external partition of a partitioned variable.

1 Answers  

---

ORA-02088: distributed database option not installed

1 Answers  

---

DRG-10702: cannot create or modify preference in another user's schema

1 Answers  

---

ORA-00603: ORACLE server session terminated by fatal error

2 Answers  

---

ORA-39099: cannot create index for "string" on master table string

1 Answers  

---

PLS-00667: Element type of associative array should be pls_integer or binary_integer

1 Answers  

---

DRG-10760: illegal format for procedure name

1 Answers  

---

RMAN-06457: UNTIL scn (string) is ahead of last scn in archived logs (string)

1 Answers  

---

PCB-00629: Host variable is not of Internal LOB type

1 Answers  

---