Answer / guest

Cause: No previously established Logminer Dictionary is
available and a complete gather of a source system data
dictionary was not found in the logstream. build() may not
have been run to force the gathering of a source system data
dictiony. Or add_log_file() may not have been called to add
all log files which contain the complete gathered system
data dictionary.

Action: If build() was not employed prior to this mining
session the Logminer Ad Hoc user may elect to employ an
alternate dictionary such as the current system catalog or a
previously built flat file dictionary. Other Logminer
clients must run build() prior to mining. If build() has
been run, ensure that all logfiles which comprise the
gathered system dictionary have beed added. The following
query, run on the system which build() was run, can be
helpful in identifying the requried files. select
DICTIONARY_BEGIN, DICTIONARY_END, name from v$archived_log;
Minimally a set of files beginning with one which has
DICTIONARY_BEGIN = 'YES' and all following log files through
one marked DICTIONARY_END = 'YES' must be added.

Please add more information about this Error

DRG-11520: error writing to file

1 Answers  

---

ORA-01977: Missing thread number

1 Answers  

---

ORA-15002: parameter LOCK_NAME_SPACE exceeds limit of string characters

1 Answers  

---

ORA-04008: START WITH cannot be more than MAXVALUE

1 Answers  

---

NNO-00257: warning: cannot get serial number from region store

1 Answers  

---

ORA-15095: reached maximum ASM file size (string GB)

1 Answers  

---

TNS-12591: TNS:event signal failure

1 Answers  

---

TNS-00088: * exit - quit the Interchange controller

1 Answers  

---

ORA-16094: database shutdown during archival operation

1 Answers  

---

ORA-23327: imported deferred rpc data does not match string of importing db

1 Answers  

---

SQL*Loader-00559: error closing file

1 Answers  

---

ORA-13263: column string in table string is not of type SDO_GEOMETRY

1 Answers  

---