OraFAQ Forum: Backup & Recovery » unable to see DMLs in v$logmnr

Home » RDBMS Server » Backup & Recovery » unable to see DMLs in v$logmnr_contents

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

unable to see DMLs in v$logmnr_contents [message #237478]

Mon, 14 May 2007 11:04

Anand Ramaswamy
Messages: 111
Registered: January 2005

Senior Member

Hi All,
I'll explain the steps I performed.

SESSION 1:
SQL>EXECUTE DBMS_LOGMNR.ADD_LOGFILE(LOGFILENAME => '/d1/log01a.dbf', options => dbms_logmnr.new);

SQL>EXECUTE DBMS_LOGMNR.ADD_LOGFILE(LOGFILENAME => '/d1/log02a.dbf', options => dbms_logmnr.addfile);

SQL>EXECUTE DBMS_LOGMNR.ADD_LOGFILE(LOGFILENAME => '/d1/log03a.dbf', options => dbms_logmnr.addfile);

SQL>EXECUTE DBMS_LOGMNR.START_LOGMNR(OPTIONS=>DBMS_LOGMNR.COMMITTED_DATA_ONLY);


SESSION 2:
SQL>connect development/password
SQL>INSERT INTO T1 VALUES(1, 2);
SQL>INSERT INTO T1 VALUES(3, 4);
SQL>COMMIT;
SQL>DELETE FROM T1;
SQL>COMMIT;

SESSION 1:
SQL>SELECT * FROM V$LOGMNR_CONTENTS WHERE SEG_NAME='T1';
no rows selected
SQL>

Am I doing something wrong here. I expected to see the DMLs performed by development user.
Can anyone help??

Thanks in advance
qA

Report message to a moderator

Re: unable to see DMLs in v$logmnr_contents [message #237492 is a reply to message #237478]

Mon, 14 May 2007 11:36

Michel Cadot
Messages: 68716
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

These statements are surely in files you don't give to log miner.
Log Miner can only see data from DML executed before its start.

Regards
Michel

Report message to a moderator

Re: unable to see DMLs in v$logmnr_contents [message #237504 is a reply to message #237492]

Mon, 14 May 2007 12:44

Anand Ramaswamy
Messages: 111
Registered: January 2005

Senior Member

Hi Michel,
Thanks for your reply. Even now I could not see any output in v$logmnr_contents.
Please see the new sequence of events.

SESSION 1:
SQL>connect development/password
SQL>INSERT INTO T1 VALUES(1, 2);
SQL>INSERT INTO T1 VALUES(3, 4);
SQL>COMMIT;
SQL>DELETE FROM T1;
SQL>COMMIT;

SESSION 2:
SQL>EXECUTE DBMS_LOGMNR.ADD_LOGFILE(LOGFILENAME => '/d1/log01a.dbf', options => dbms_logmnr.new);

SQL>EXECUTE DBMS_LOGMNR.ADD_LOGFILE(LOGFILENAME => '/d1/log02a.dbf', options => dbms_logmnr.addfile);

SQL>EXECUTE DBMS_LOGMNR.ADD_LOGFILE(LOGFILENAME => '/d1/log03a.dbf', options => dbms_logmnr.addfile);

SQL>EXECUTE DBMS_LOGMNR.START_LOGMNR(OPTIONS=>DBMS_LOGMNR.COMMITTED_DATA_ONLY);


SESSION 2:
SQL>SELECT * FROM V$LOGMNR_CONTENTS WHERE SEG_NAME='T1'; 
no rows selected
SQL>

--tried lower case 't1' also in the above query

What could be the reason??

Regards
qA

Report message to a moderator

Re: unable to see DMLs in v$logmnr_contents [message #237505 is a reply to message #237504]

Mon, 14 May 2007 12:53

Michel Cadot
Messages: 68716
Registered: March 2007
Location: Saint-Maur, France, https...

Senior Member
Account Moderator

You don't specify where Log Miner has to find dictionary data.
Add "sys.dbms_logmnr.dict_from_online_catalog" to your option.

Regards
Michel

Report message to a moderator

Re: unable to see DMLs in v$logmnr_contents [message #237512 is a reply to message #237505]

Mon, 14 May 2007 13:33

Anand Ramaswamy
Messages: 111
Registered: January 2005

Senior Member

Thanks Michel,
I got it now.

Regards,
qA

Report message to a moderator

Previous Topic:	Clone problem due to mountpoint space constraints
Next Topic:	how to deal with RMAN

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Nov 26 21:39:03 CST 2024