ORA-01294: error occurred while processing information in
dictionary file string, possible corruption
Answers were Sorted based on User's Feedback
Answer / johnpaul
After successfully creating the dictionary to a flat file,
when attempting to start the Logminer utility, it fails
with errors:
ERROR at line 1:
ORA-01294: error occurred while processing information in
dictionary file , possible corruption
ORA-06512: at "SYS.DBMS_LOGMNR", line 53
ORA-06512: at line 1
Cause
The ATTRIBUTE$_TABLE is not being created in the dictionary
file
If the dictionary file is opened, we can see the syntax to
insert into the ATTRIBUTE$_TABLE table:
INSERT_INTO ATTRIBUTE$_TABLE VALUES
(00000000000000000000000000000003,1,'KOTADKVN',1,00000000000
000000000000000000013,1,,2,,,,,,'',0,,,,,,,);
However, the syntax to create the table should be prior to
the insert statement and it is missing. It should contain
the following:
CREATE_TABLE ATTRIBUTE$_TABLE (TOID RAW(16), VERSION# NUMBER
(22), NAME VARCHAR2(30), ATTRIBUTE# NUMBER(22), ATTR_TOID
RAW(16), ATTR_VERSION# NUMBER(22), SYNOBJ# NUMBER(22),
PROPERTIES NUMBER(22), CHARSETID NUMBER(22), CHARSETFORM
NUMBER(22), LENGTH NUMBER(22), PRECISION# NUMBER(22), SCALE
NUMBER(22), EXTERNNAME VARCHAR2(4000), XFLAGS NUMBER(22),
SPARE1 NUMBER(22), SPARE2 NUMBER(22), SPARE3 NUMBER(22),
SPARE4 NUMBER(22), SPARE5 NUMBER(22), SETTER NUMBER(22),
GETTER NUMBER(22) );
Solution
1. Use the online catalog
Example:
SQL> EXECUTE DBMS_LOGMNR.START_LOGMNR(OPTIONS =>
DBMS_LOGMNR.DICT_FROM_ONLINE_CATALOG);
Is This Answer Correct ? | 0 Yes | 0 No |
Answer / guest
Cause: The dictionary file is corrupt.
Action: Get a new dictionary file.
Please add more information about this Error
Is This Answer Correct ? | 0 Yes | 1 No |
DRG-11826: Proxy Authentication Required
ORA-39307: the operation is illegal without an initial clone
QSM-01026: query rewrite is disabled for, string
ORA-07271: spwat: invalid oracle process number.
ORA-36872: (XSTFDSC02) Column type specifier cannot be used when the table function data type is specified.
ORA-31622: ORACLE server does not have string access to the specified file
ORA-37083: Invalid object string
ORA-16805: Change of LogXptMode property violates overall protection mode.
DBV-00200: Block, dba number, already marked corrupted
RMAN-06133: recovery catalog may have obsolete data for datafile string
ORA-02235: this table logs changes to another table already
RMAN-06040: controlfile is already restored to file string