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-29848: error occurred in the execution of ODCIINDEXMERGEPARTITION routine
ORA-06754: TLI Driver: unable to get local host address
ORA-14158: too many subpartition descriptions
ORA-12463: undefined group string for policy string
ORA-23345: table "string"."string" not registered to collect statistics
ORA-01528: EOF while processing SQL statement
PLS-00552: flexible character set is not allowed on component element
ORA-03124: two-task internal error
ORA-16726: the external condition supplied to resource manager is invalid
PCB-00200: Cannot equivalence PIC N or PIC G variable "string"
ORA-12696: Double Encryption Turned On, login disallowed
TNS-02517: key smaller than requested size