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-07449: sc: usnewlock failed.
ORA-38425: attribute set used for an index object may not be unassigned
ORA-13839: V$SQL row doesn't exist with given HASH_VALUE and ADDRESS.
SQL*Loader-00419: input datatype for column string is not supported when loading varrays
ORA-04092: cannot string in a trigger
SQL*Loader-00460: Column (string), form of use (number) does not match char set id of (number)
ORA-23420: interval must evaluate to a time in the future
TNS-12651: Encryption or data integrity algorithm unacceptable
ORA-15021: parameter "string" is not valid in string instance
PCC-02310: formal parameter VARCHARs should be declared as pointers
ORA-00401: the value for parameter string is not supported by this release
ORA-31076: required attribute "string" not specified