ORA-01333: failed to establish Logminer Dictionary
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
Is This Answer Correct ? | 0 Yes | 0 No |
ORA-36683: (XSDPART21) Partition string dimensioned by more than one composite.
RMAN-06525: RMAN retention policy is set to none
RMAN-08531: channel string: proxy copy string is string in media management catalog
QSM-01042: anchor and matching join arc check failed for string
ORA-08316: sllfsk: Error seeking in file.
ORA-22998: CLOB or NCLOB in multibyte character set not supported
QSM-01123: self-join algorithm could not resolve multiple instances
ORA-15018: diskgroup cannot be created
ORA-29905: method string does not exist in type string.string
ORA-28515: cannot get external object definitions from string
ORA-38105: Delete not yet supported when Update row-migration is possible
ORA-13914: Threshold notification failed.