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-27155: could not execute file
PLS-00645: character set mismatch found at 'string' among operands in a COALESCE expression
RMAN-06743: specification does not match any backupset in the repository
ORA-01070: Using an old version of Oracle for the server
KUP-02006: script line too long
ORA-02852: Invalid critical-section time out value
PCB-00901: Pro*COBOL internal error condition detected (Code = number)
NNL-00907: NOT ALLOWED responses sent: number
ORA-28560: error in configuration of agent process
QSM-00504: internal error
SQL*Loader-00600: Bind size of number bytes increased to number bytes to hold 1 row.
PLW-07202: bind type would result in conversion away from column type