Problems starting logminer

[kingfisher]

Hi,

I've recently started, stopped and started again logminer without any problems, but today this happens:

SQL> execute dbms_logmnr.START_LOGMNR(dictfilename => dbms_logmnr.dict_from_online_catalog);
BEGIN dbms_logmnr.START_LOGMNR(dictfilename => dbms_logmnr.dict_from_online_catalog); END;

*
ERROR at line 1:
ORA-01284: file 16 cannot be opened
ORA-06512: at "SYS.DBMS_LOGMNR", line 58
ORA-06512: at line 1

Only relevant content of the alert_xxx.log:

Ma Sep 17 12:26:17 2007
logminer Bld: Build started
Ma Sep 17 12:26:17 2007
logminer Bld: Catalog lockdown FAILED, status -258

I've checked the docs, and it seems the logminer package cannot open the dictionary.

How can I fix this?

Config: Oracle 10g on Windows. Test installation on Windows XP.

Any help appreciated.

Regards,
Rolf Barbakken

[jay_l_a]

Pathname exceeds 256 characters??

[kingfisher]

Pathname exceeds 256 characters??

No the path does not exceed 256 chars. As I said, the logminer has worked fine for a while, then suddenly refuses to start, so the path has not changed.

[dbtoo]

IS file 16 in backup or readonly?

[kingfisher]

IS file 16 in backup or readonly?

As I don't even know what "file 16" is, I don't know if it is in backup or readonly.

[hrishy]

Hi

i am not very sure but whats the output of

select * from dba_data_files where file_id = 16

regards
Hrishy

[kingfisher]

Hi

i am not very sure but whats the output of

select * from dba_data_files where file_id = 16

regards
Hrishy

The results from this query is

no rows selected

I still get the same error.

[kingfisher]

I changed from "dictfilename" to "options" and now it runs again. Don't know why this was the solution or why "dictfilename" was working before.

Thank you all, though.