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 |
NNL-00930: Requests refused, unknown data type: number
DRG-10817: CONTAINS term consists of stopword or phrase of stopwords: string
DRG-10851: Invalid grammar string specified for query template
ORA-24169: rule condition has unrecognized variables
ORA-16574: switchover disallowed when required databases are offline
PCC-01102: Invalid label at line number in file string
ORA-28579: network error during callback from external procedure agent
ORA-10644: SYSTEM tablespace cannot be default temporary tablespace
ORA-10585: Test recovery can not apply redo that may modify control file
ORA-02736: osnfpm: illegal default shared memory address
ORA-01572: rollback segment 'string' cannot be brought online, string extents exceeded
ORA-06770: TLI Driver: error sending version