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

ORA-16515: no rcv channel

1 Answers  

---

ORA-28157: Proxy user 'string' forbidden to set role 'string' for client 'string'

1 Answers  

---

AMD-00110: parameter string of "string" not valid

1 Answers  

---

ORA-25439: duplicate variable value for variable: string

1 Answers  

---

ORA-25507: resource manager has not been continuously on

1 Answers  

---

PLS-00492: variable or constant initialization may not refer to functions declared in the same package

1 Answers  

---

ORA-14312: Value string already exists in partition string

1 Answers  

---

ORA-19039: Keyword string reserved for future use

1 Answers  

---

ORA-12071: definition query of "string"."string" is invalid for offline instantiation

1 Answers  

---

ORA-13120: invalid face_id [string]

1 Answers  

---

IMG-00713: unsupported destination image format

1 Answers  

---

KUP-04091: little endian byte order mark found when big endian expected in string

1 Answers  

---