Home » RDBMS Server » Server Administration » v$logmnr_contents displaying UNKNOWN
v$logmnr_contents displaying UNKNOWN [message #62765] Thu, 12 August 2004 04:23 Go to next message
James Briar
Messages: 72
Registered: January 2002
Location: Morden (South London)
Member
I'm dabbling with LogMiner on one of our test instances. I've set things up ok (in user SYS) and everything is fine. If i log into user AUDITING to test LogMiner and do "insert into jimtable values ('JIM');" and "commit;" then log into user SYS and run :-

execute dbms_logmnr.add_logfile('/u03/oradata/dev/devlog2.rdo1', dbms_logmnr.NEW
);                                                                             
execute dbms_logmnr.start_logmnr(-                                             
dictfilename=>'/export/home/oracle/devdict.ora',-                              
starttime=>to_date('12-Aug-2004 11:25:00','DD-MON-YYYY HH:MI:SS'),-            
endtime=>to_date('12-Aug-2004 11:29:00','DD-MON-YYYY HH:MI:SS'));              
                                                                               
select timestamp, username, seg_name, sql_redo                                 
from v$logmnr_contents                                                         
where username = 'AUDITING';                                                   
                                                                               
execute dbms_logmnr.end_logmnr;                                                

I get this output :-

2004-08-12 11:27:06 AUDITING                                                   
insert into "UNKNOWN"."Objn:338860"("Col[[1]]") values (HEXTORAW('4252494152')); 

The output is ok but how can i fix things to get v$logmnr_contents to display JIMTABLE rather than UNKNOWN and JIM rather than HEXTORAW? Also SEG_NAME is null? (Oracle 8i on a Sun Solaris 8 Unix box).

Thanks. 
Re: v$logmnr_contents displaying UNKNOWN [message #62769 is a reply to message #62765] Thu, 12 August 2004 06:08 Go to previous message
James Briar
Messages: 72
Registered: January 2002
Location: Morden (South London)
Member
Doh !! I've figured out the problem. I created the table JIMTABLE after i ran "execute dbms_logmnr_d.build('devdict.ora','/export/home/oracle');". I ran dbms_logmnr_d.build again and this corrected the output.
Previous Topic: mission critical database
Next Topic: RE: Segment not shown
Goto Forum:
  


Current Time: Thu Jan 09 14:38:26 CST 2025