Log miner

begin dbmn_logmnr.start_logmnr(starttime => '01-oct-2011 00:00:00',endtime =>'21-feb-2012 00:00:00',options => dbms_logmnr.dict_from_online_catalog+dbms_logmnr.continuous_mine);
ERROR at line 1:
ORA-06550: line 1, column 7:
PLS-00201: identifier 'DBMN_LOGMNR.START_LOGMNR' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
how to fix this problem....?
i need to start log_miner

915855 wrote:
begin dbmn_logmnr.start_logmnr(starttime => '01-oct-2011 00:00:00',endtime =>'21-feb-2012 00:00:00',options => dbms_logmnr.dict_from_online_catalog+dbms_logmnr.continuous_mine);
ERROR at line 1:
ORA-06550: line 1, column 7:
PLS-00201: identifier 'DBMN_LOGMNR.START_LOGMNR' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
how to fix this problem....?
i need to start log_minerPlease read, there is a complete chapter on how to use Log Miner.
http://docs.oracle.com/cd/E11882_01/server.112/e22490/logminer.htm#SUTIL019
And as mentioned by Vivek, check the spellings of the package.
Aman....

Similar Messages

Not getting SCN details in Log Miner

Oracle 11g
Windows 7
Hi DBA's,
I am not getting the SCN details in log miner. Below are steps for the same:-
SQL> show parameter utl_file_dir
NAME                                 TYPE        VALUE
utl_file_dir                         string
SQL> select name,issys_modifiable from v$parameter where name ='utl_file_dir';
NAME               ISSYS_MOD
utl_file_dir    FALSE
SQL> alter system set utl_file_dir='G:\oracle11g' scope=spfile;
System altered.
SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
Total System Global Area 1071333376 bytes
Fixed Size                  1334380 bytes
Variable Size             436208532 bytes
Database Buffers          629145600 bytes
Redo Buffers                4644864 bytes
Database mounted.
Database opened.
SQL> show parameter utl_file_dir
NAME                                 TYPE        VALUE
utl_file_dir                         string      G:\oracle11g\logminer_dir
SQL> SELECT SUPPLEMENTAL_LOG_DATA_MIN FROM V$DATABASE;
SUPPLEME
NO
SQL> ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;
Database altered.
SQL> SELECT SUPPLEMENTAL_LOG_DATA_MIN FROM V$DATABASE;
SUPPLEME
YES
SQL> /* Minimum supplemental logging is now enabled. */
SQL>
SQL> alter system switch logfile;
System altered.
SQL> select g.group# , g.status , m.member
2       from v$log g, v$logfile m
3       where g.group# = m.group#
4       and g.status = 'CURRENT';
    GROUP# STATUS
MEMBER
         1 CURRENT
G:\ORACLE11G\ORADATA\MY11G\REDO01.LOG
SQL> /* start fresh with a new log file which is the group 1.*/
SQL> create table scott.test_logmnr
2 (id number,
3 name varchar2(10)
4 );
Table created.
SQL> BEGIN
2    DBMS_LOGMNR_D.build (
3      dictionary_filename => 'logminer_dic.ora',
4      dictionary_location => 'G:\oracle11g');
5 END;
6 /
PL/SQL procedure successfully completed.
SQL> /*
SQL>   This has recorded the dictionary information into the file
SQL>   "G:\oracle11g\logminer_dic.ora".
SQL> */
SQL> conn scott/
Connected.
SQL> insert into test_logmnr values (1,'TEST1');
1 row created.
SQL> insert into test_logmnr values (2,'TEST2');
1 row created.
SQL> commit;
Commit complete.
SQL> select * from test_logmnr;
        ID NAME
         1 TEST1
         2 TEST2
SQL> update test_logmnr set name = 'TEST';
2 rows updated.
SQL> select * from test_logmnr;
        ID NAME
         1 TEST
         2 TEST
SQL> commit;
Commit complete.
SQL> delete from test_logmnr;
2 rows deleted.
SQL> commit;
Commit complete.
SQL> select * from test_logmnr;
no rows selected
SQL> conn / as sysdba
Connected.
SQL> select g.group# , g.status , m.member
2       from v$log g, v$logfile m
3       where g.group# = m.group#
4       and g.status = 'CURRENT';
    GROUP#         STATUS                                         MEMBER
         1             CURRENT                           G:\ORACLE11G\ORADATA\MY11G\REDO01.LOG
SQL> begin
2        dbms_logmnr.add_logfile
3        (
4         logfilename => 'G:\oracle11g\oradata\my11g\REDO01.LOG',
5         options     => dbms_logmnr.new
6        );
7
8       /
PL/SQL procedure successfully completed.
SQL> select filename from v$logmnr_logs;
FILENAME
G:\oracle11g\oradata\my11g\REDO01.LOG
PL/SQL procedure successfully completed.
SQL> BEGIN
2    -- Start using all logs
3    DBMS_LOGMNR.start_logmnr (
4      dictfilename => 'G:\oracle11g\logminer_dic.ora');
5
6   END;
7 /
PL/SQL procedure successfully completed.
SQL> DROP TABLE myLogAnalysis;
Table dropped.
SQL> create table myLogAnalysis
2       as
3       select * from v$logmnr_contents;
Table created.
SQL> begin
2         DBMS_LOGMNR.END_LOGMNR();
3       end;
4       /
PL/SQL procedure successfully completed.
SQL> set lines 1000
SQL> set pages 500
SQL> column scn format a6
SQL> column username format a8
SQL> column seg_name format a11
SQL> column sql_redo format a33
SQL> column sql_undo format a33
SQL> select scn , seg_name , sql_redo , sql_undo
2 from   myLogAnalysis
3 where username = 'SCOTT'
4 AND (seg_owner is null OR seg_owner = 'SCOTT');
SCN SEG_NAME
SQL_REDO
SQL_UNDO
set transaction read write;
commit;
set transaction read write;
########## TEST_LOGMNR insert into "SCOTT"."TEST_LOGMNR" delete from "SCOTT"."TEST_LOGMNR"
("ID","NAME") values ('1','TEST1' where "ID" = '1' and "NAME" = 'T
EST1' and ROWID = 'AAARjeAAEAAAAD
PAAA';
########## TEST_LOGMNR insert into "SCOTT"."TEST_LOGMNR" delete from "SCOTT"."TEST_LOGMNR"
("ID","NAME") values ('2','TEST2' where "ID" = '2' and "NAME" = 'T
EST2' and ROWID = 'AAARjeAAEAAAAD
PAAB';
commit;
set transaction read write;
########## TEST_LOGMNR update "SCOTT"."TEST_LOGMNR" set update "SCOTT"."TEST_LOGMNR" set
"NAME" = 'TEST' where "NAME" = 'T "NAME" = 'TEST1' where "NAME" = '
EST1' and ROWID = 'AAARjeAAEAAAAD TEST' and ROWID = 'AAARjeAAEAAAAD
PAAA';
PAAA';
########## TEST_LOGMNR update "SCOTT"."TEST_LOGMNR" set update "SCOTT"."TEST_LOGMNR" set
"NAME" = 'TEST' where "NAME" = 'T "NAME" = 'TEST2' where "NAME" = '
EST2' and ROWID = 'AAARjeAAEAAAAD TEST' and ROWID = 'AAARjeAAEAAAAD

Kindly type
Desc v$logmnr_contents
Please notice the scn is a *number* column,not varchar2
By using format a6 you are forcing Oracle to display a too big number as a char. Hence the ##.
Sybrand Bakker
Senior Oracle DBA

Log miner end-of-file on communcation channel

Hi,
I'm trying to use log miner but when I perform a select from the
v$logmnr_conents table such as
select operation from v$logmnr_conents where username = 'FRED'
I get a ORA-03113: end-of-file on communcation channel.
the trace files given no information expect the very unuseful 'internal
error'.
Anyone had this problem? is it possible to read the archive log without
logminer?? I really need to read the logs because someone updated the wrong data in the database and I need to recover this.
Thanks in advance,
steve.

Hi Joel,
Here is SGA information:
select * from v$sgastat where name = 'free memory';
POOL NAME BYTES
shared pool free memory 75509528
large pool free memory 16777216
java pool free memory 83886080
Thank you for your time,
Katya

Log miner doesn't show all transactions on a table

I'm playing a little with log miner on oracle 11gR2 on a 32bit CentOS Linux install, but it looks like it's not showing me all DML on my test table. Am I doing something wrong?
Hi, there's my test case:
- Session #1, create table and insert first row:
SQL> create table stolf.test_table (
col1 number,
col2 varchar(10),
col3 varchar(10),
col4 varchar(10));
2 3 4 5
Table created.
SQL> insert into stolf.test_table (col1, col2, col3, col4) values ( 0, 20100305, 0, 0);
1 row created.
SQL> commit;
SQL> select t.ora_rowscn, t.* from stolf.test_table t;
ORA_ROWSCN COL1 COL2 COL3 COL4
1363624 0 20100305 0 0
- Execute shell script to insert a thousand lines into table:
for i in `seq 1 1000`; do
sqlplus -S stolf/<passwd><<-EOF
insert into stolf.test_table (col1, col2, col3, col4) values ( $ , 20100429, ${i}, ${i} );
commit;
EOF
done
- Session #1, switch logfiles:
SQL> alter system switch logfile;
System altered.
SQL> alter system switch logfile;
System altered.
SQL> alter system switch logfile;
System altered.+
- Session #2, start logminer with continuous_mine on, startscn = first row ora_rowscn, endscn=right now. The select on v$logmnr_contents should return at least a thousand rows, but it returns three rows instead :
BEGIN
SYS.DBMS_LOGMNR.START_LOGMNR(STARTSCN=>1363624, ENDSCN=>timestamp_to_scn(sysdate), OPTIONS => sys.DBMS_LOGMNR.DICT_FROM_ONLINE_CATALOG + sys.DBMS_LOGMNR.COMMITTED_DATA_ONLY + SYS.DBMS_LOGMNR.CONTINUOUS_MINE);
END;
SQL> select SCN, SQL_REDO, SQL_UNDO FROM V$LOGMNR_CONTENTS where SQL_REDO IS NOT NULL AND seg_owner = 'STOLF';
SCN
SQL_REDO
SQL_UNDO
1365941
insert into "STOLF"."TEST_TABLE"("COL1","COL2","COL3","COL4") values ('378','20100429','378','378');
delete from "STOLF"."TEST_TABLE" where "COL1" = '378' and "COL2" = '20100429' and "COL3" = '378' and "COL4" = '378' and ROWID = 'AAASOHAAEAAAATfAAB';
1367335
insert into "STOLF"."TEST_TABLE"("COL1","COL2","COL3","COL4") values ('608','20100429','608','608');
delete from "STOLF"."TEST_TABLE" where "COL1" = '608' and "COL2" = '20100429' and "COL3" = '608' and "COL4" = '608' and ROWID = 'AAASOHAAEAAAATfAAm';
1368832
insert into "STOLF"."TEST_TABLE"("COL1","COL2","COL3","COL4") values ('849','20100429','849','849');
delete from "STOLF"."TEST_TABLE" where "COL1" = '849' and "COL2" = '20100429' and "COL3" = '849' and "COL4" = '849' and ROWID = 'AAASOHAAEAAAATbAAA';+

Enable supplemental logging.
Please see below,
SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 422670336 bytes
Fixed Size                  1300352 bytes
Variable Size             306186368 bytes
Database Buffers          109051904 bytes
Redo Buffers                6131712 bytes
alter databsDatabase mounted.
SQL>
2
SQL> alter database archivelog;
Database altered.
SQL> alter database open;
Database altered.
SQL> alter system checkpoint;
System altered.
SQL> drop table test_Table purge;
Table dropped.
SQL> create table test_table(
2 col1 number,
col2 varchar(10),
col3 varchar(10),
col4 varchar(10)); 3    4    5
Table created.
SQL> insert into test_table (col1, col2, col3, col4) values ( 0, 20100305, 0, 0);
1 row created.
SQL> commit;
Commit complete.
SQL> select t.ora_rowscn, t.* from test_table t;
ORA_ROWSCN       COL1 COL2       COL3       COL4
   1132572          0 20100305   0          0
SQL> for i in 1..1000 loop
SP2-0734: unknown command beginning "for i in 1..." - rest of line ignored.
SQL> begin
2 for i in 1..1000 loop
3 insert into test_table values(i,20100429,i,i);
4 end loop; commit;
5 end;
6 /
PL/SQL procedure successfully completed.
SQL> alter system switch logfile;
System altered.
SQL> /
SQL> select * from V$version;
BANNER
--------------------------------------------------------------------------------Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
PL/SQL Release 11.1.0.6.0 - Production
CORE    11.1.0.6.0      Production
TNS for Linux: Version 11.1.0.6.0 - Production
NLSRTL Version 11.1.0.6.0 - ProductionIn the second session,
SQL> l
1 select SCN, SQL_REDO, SQL_UNDO FROM V$LOGMNR_CONTENTS where SQL_REDO IS NOT NULL
2* and seg_owner='SYS' and table_name='TEST_TABLE'
--------------------------------------------------------------------------------insert into "SYS"."TEST_TABLE"("COL1","COL2","COL3","COL4") values ('2','20100429','2','2');
delete from "SYS"."TEST_TABLE" where "COL1" = '2' and "COL2" = '20100429' and "COL3" = '2' and "COL4" = '2' and ROWID = 'AAASPKAABAAAVpSAAC';
   1132607
insert into "SYS"."TEST_TABLE"("COL1","COL2","COL3","COL4") values ('3','2010042
       SCN
SQL_REDO
--------------------------------------------------------------------------------SQL_UNDO
--------------------------------------------------------------------------------9','3','3');
delete from "SYS"."TEST_TABLE" where "COL1" = '3' and "COL2" = '20100429' and "COL3" = '3' and "COL4" = '3' and ROWID = 'AAASPKAABAAAVpSAAD';
   1132607
insert into "SYS"."TEST_TABLE"("COL1","COL2","COL3","COL4") values ('4','20100429','4','4');
<<trimming the output>>
--------------------------------------------------------------------------------429','997','997');
delete from "SYS"."TEST_TABLE" where "COL1" = '997' and "COL2" = '20100429' and
"COL3" = '997' and "COL4" = '997' and ROWID = 'AAASPKAABAAAVpVACU';
   1132607
insert into "SYS"."TEST_TABLE"("COL1","COL2","COL3","COL4") values ('998','20100429','998','998');
       SCN
SQL_REDO
--------------------------------------------------------------------------------SQL_UNDO
--------------------------------------------------------------------------------delete from "SYS"."TEST_TABLE" where "COL1" = '998' and "COL2" = '20100429' and
"COL3" = '998' and "COL4" = '998' and ROWID = 'AAASPKAABAAAVpVACV';
   1132607
insert into "SYS"."TEST_TABLE"("COL1","COL2","COL3","COL4") values ('999','20100429','999','999');
delete from "SYS"."TEST_TABLE" where "COL1" = '999' and "COL2" = '20100429' and
       SCN
SQL_REDO
--------------------------------------------------------------------------------SQL_UNDO
--------------------------------------------------------------------------------"COL3" = '999' and "COL4" = '999' and ROWID = 'AAASPKAABAAAVpVACW';
   1132607
insert into "SYS"."TEST_TABLE"("COL1","COL2","COL3","COL4") values ('1000','20100429','1000','1000');
delete from "SYS"."TEST_TABLE" where "COL1" = '1000' and "COL2" = '20100429' and "COL3" = '1000' and "COL4" = '1000' and ROWID = 'AAASPKAABAAAVpVACX';
       SCN
SQL_REDO
--------------------------------------------------------------------------------SQL_UNDO
1000 rows selected.
SQL>HTH
Aman....

Large number of objets - log miner scalability?

We have been consolidating several departmental databases into one big RAC database. Moreover, in tests databases we are cloning test cells (for example, an application schema is getting cloned hundred of times so that our users may test independently from each others).
So, our acception test database now have about 500,000 objects in it. We have production databases with over 2 millions objects in it.
We are using streams. At this time we're using a local capture, but our architecture aims to use downstream capture soon... We are concerned about the resources required for the log miner data dictionary build.
We are currently not using DBMS_LOGMNR_D.build directly, but rather indirectly through the DBMS_STREAMS_ADM.add_table_rule. We only want to replicate about 30 tables.
We are surprised to find that the log miner always build a complete data dictionary for every objets of the database (tables, partitions, columns, users, and so on).
Apparently there is no way to create a partial data dictionary even by using DBMS_LOGMNR_D.BUILD directly...
Lately, it took more than 2 hours just to build the log miner data dictionary on a busy system! And we ended up with an ORA-01280 error. So we started all over again...
We just increased our redo log size recently. I haven't had a chance to test after the change. Our redo log was only 4MB, we increased it to 64MB to reduce checkpoint activity. This will probably help...
Does anybody has encountered slow log miner dictionary build?
Any advice?
Thanks you in advance.
Jocelyn

Hello Jocelyn,
In streams environment, the logminer dictionary build is done using DBMS_CAPTURE_ADM.BUILD procedure. You should not be using DBMS_LOGMNR_D.BUILD for this.
In Streams Environment, DBMS_STREAMS_ADM.ADD_TABLE_RULE will dump the dictionary only on the first time when you call this, since the capture process is not yet created and it will be created only when you call DBMS_STREAMS_ADM.ADD_TABLE_RULE and a dictionary dump as well. Logminer dictionary will have the information about all the objects like tables, partitions, columns, users and etc.. The dictionary dump will take time depends on the number of objects in the database since if the number of objects are very high in the database then the data dictionary itself will be big.
Your redo size 64MB and this is too small for a production system, you should consider having a redo log size of 200M atleast.
You can have a complete logminer dictionary build using DBMS_CAPTURE_ADM.BUILD and then create a capture process using the FIRST_SCN returned from the BUILD procedure.
Let me know if you have more doubts.
Thanks,
Rijesh

Log Miner is finding DDL for "new" tables, but also DML for "older" tables.

oracle 10.2.0.5.0 Standard Edition
(at some point in the past it was "downgraded" from enterprise edition).
It's making me crazy, i create a table then insert/update rows. Log miner only shows me the create.
However, if i do insert/update on an "older" table, i see the DML. The tables are in the same tablespace, both logging, and the database is forcing logging.
I'm out of ideas, and input would be appreciated.
thanks!
####### CREATE THE ORACLE.LOGMNR1 TABLE ########
SQL> create table ORACLE.LOGMNR1
2 (col1 varchar2(100));
Table created.
####### INSERT ROW AND UPDATE A ROW IN ORACLE.LOGMNR1 TABLE ########
SQL> insert into ORACLE.LOGMNR1 values ('testing insert');
1 row created.
SQL> commit;
Commit complete.
SQL> update ORACLE.LOGMNR1 set col1 = 'TESTING UPDATE';
1 row updated.
SQL> commit;
Commit complete.
####### INSERT 2 ROWS INTO AN OLD TABLE EPACS.COLUMN_COUNTS ########
SQL> insert into epacs.column_counts
2 values ('TEST1',99,'TEST2',88,SYSDATE);
1 row created.
insert into epacs.column_counts
   values('TEST3',77,'TEST4',66,SYSDATE);
1 row created.
SQL> COMMIT;
Commit complete.
####### INSERT ANOTHER ROW INTO ORACLE.LOGMNR1 TABLE ########
SQL> insert into LOGMNR1 values ('ONE MORE TEST');
1 row created.
SQL> COMMIT;
Commit complete.
####### CREATE THE ORACLE.LOGMNRAFTER TABLE ########
SQL> CREATE TABLE LOGMNRAFTER (COL1 VARCHAR2(100));
Table created.
####### INSERT A ROW INTO ORACLE.LOGMNRAFTER TABLE ########
SQL> INSERT INTO LOGMNRAFTER VALUES('FINISHED');
1 row created.
SQL> COMMIT;
Commit complete.
####### MINE THE LOGS FOR ACTIVITY ########
SQL> edit
Wrote file afiedt.buf
1 select to_char(timestamp,'yyyy/mm/dd hh24:mi:ss'), username,
2          operation, sql_redo
3          from v$logmnr_contents
4      where
5      seg_owner in( 'ORACLE','EPACS')
6 and
7      operation <> 'UNSUPPORTED'
8*          order by timestamp
SQL> /
####### IT FINDS THECREATE THE ORACLE.LOGMNR1 TABLE, BUT NO INSERTS ########
2013/10/09 14:02:05 ORACLE
DDL
create table LOGMNR1
(col1 varchar2(100));
####### IT DOES FIND INSERTS FOR THE OLD EPACS.COLUMN_COUNTS TABLE ########
2013/10/09 14:03:54 ORACLE
INSERT
insert into "EPACS"."COLUMN_COUNTS"("TABLE_NM","TABLE_ROW_QTY","COLUMN_NM","COLU
MN_QTY","LAST_UPDATE") values ('TEST1','99','TEST2','88','09-OCT-13');
2013/10/09 14:05:09 ORACLE
INSERT
insert into "EPACS"."COLUMN_COUNTS"("TABLE_NM","TABLE_ROW_QTY","COLUMN_NM","COLU
MN_QTY","LAST_UPDATE") values ('TEST3','77','TEST4','66','09-OCT-13');
####### AND IT FIND THE CREATE FOR THE ORACLE.LOGMNRAFTER TABLE ########
2013/10/09 14:06:11 ORACLE
DDL
CREATE TABLE LOGMNRAFTER (COL1 VARCHAR2(100));
###### BOTH TABLES ARE "LOGGING" AND LIVE IN THE SAME TABLESPACE ######
###### LOGGING IS FORCED AT THE DATABASE LEVEL ####
SQL> select force_logging from v$database;
YES
SQL> select owner,table_name,logging
2 from dba_tables where owner in ('EPACS','ORACLE')
3 and table_name in('COLUMN_COUNTS','LOGMNR1');
EPACS                          COLUMN_COUNTS                  YES
ORACLE                         LOGMNR1                        YES
SQL> SPOOL OFF

Nither the table showing only DDL nor the table showing DML have supplemental logging.
thanks.
select count(*) from ALL_LOG_GROUPS
   where LOG_GROUP_TYPE='ALL COLUMN LOGGING' and OWNER='ORACLE' and table_name='LMTEST1'
SQL> /
COUNT(*)
         0
    select count(*) from ALL_LOG_GROUPS
   where LOG_GROUP_TYPE='ALL COLUMN LOGGING' and OWNER='EPACS' and table_name='COLUMN_COUNTS'
COUNT(*)
         0
Message was edited by: user12156890
apparently this is an issue with the database configuration and not log miner. I ran the same test against the prodcution database and got both the DDL and DML. I used exactly the same test script including the logminer "setup" , obviously changing the name of the log files and the name of a directory.

Enabling log miner

I have to enable log miner on 11g r2 database
i am following How to Setup LogMiner [ID 111886.1]
1. Make sure to specify an existing directory that Oracle has permissions
   to write to by the PL/SQL procedure by setting the initialization
   parameter UTL_FILE_DIR in the init.ora.
   For example, set the following to use /oracle/logs:
     UTL_FILE_DIR =/oracle/database
   Be sure to shutdown and restart the instance after adding UTL_FILE_DIR to the init or spfile.
I am using spfile, how can i modify the initialization parameter, without modifiying the file,
We are using oracle fail safe manager, we restart the database using GUI, when i restart it will always read the spfile thats why i want to know how i can add the parameter
UTL_FILE_DIR without modified init.iora file
if i do
1) create pfile from spfile
and then how can i start the database from this pfile,
2) create spfile from pfile

hi,
you can do with scope=spfile if you don't want to create/modify pfile, for example:
SQL> alter system set utl_file_dir='/backup/logminer' scope=spfile;
SQL> shutdown immediate;
SQL> startup
SQL> sho parameter utl_file_dir
NAME TYPE VALUE
utl_file_dir string /backup/logminer
-- edited
to startup from pfile Nikolay Ivankin told you the correct answer
Edited by: Fran on 16-abr-2012 6:45

Use of LOG MINER - VERY URGENT

Hello,
I have a situation:
I want to recover the database till Friday (Last week).
I am ready to loose the data of Sat/Sun/Mon and Tuesday.
In other words, I need to get the Friday's database state. I have backups of last 30 days. My database is running in archivelog mode.
Can I use the LOGMINER to go back to the Friday's state? If yes then HOW? I have never used the Log miner neither I have been involved in the recovery, so pleaes guide me!!!
If anyone knows the answer and the methodology can they suggest it to me? It will be a greate help!!!!
Thanks in advance.
Himanshu

Hi,
you got it wrong as you think that you will able to go back on friday's database state through logminer.i would say that logminer is used to get the information from the redo log as it got the historic changes about the database,so log miner is used for variety of purposes.
1.the cahnges made to the database (insert,update,delete,ddl)
2.the scn at which the changes were made.
3.the scn at which the changes were commited.
4.the name of the user who issued the the changes etc.
so you can get these information by using log miner either throgh command based utility or oem.log miner gives you a pin point information.assume that if you don't know the time and name of the dropped table what would you do to get around these sort of problem.
you can do one thing with log miner is that you cab get scn no of corrosponding changes which dropped the table.
and you can restore your database prior to thaat scn no.
suppode you get the scn no abc of that changes.
then
run {
set until scn (the no u get through log miner );
restore database ;
recover database ;
you get the disired state of database which you willing to accomplish.
i still feel that your one question remain unanswerd.in which is you saying that i diden't recieve the media failure and your database is still up and running smothly.
so dear i would love to tell you if want to performa theses sort of recoveries then you need to restore your database this is mendetory.the reason is "trancation activity can only be rolled forward to desired time not rolled back to desired time this is why you need to restore all your database files to back in desired time."
thanks..

How to use SIMPLE CDC log MINER in ODI ?

Can you please let me the step to do the simple cdc using log miner

ya that link only tells us about consistent set journalizing . i want to know how to do simple journalizing using log miner ?
when we import the JKM Oracle 11g Consistent (LOGMINER) . we can select in the KM if we want to use simple set or consistent set
I am getting an error at the lock Journalizing step .
update     schema_name.J$S_TRG
set     JRN_CONSUMED = '1'
where     (1=1)
AND JRN_SUBSCRIBER = 'SUNOPSIS' /* AND JRN_DATE < sysdate */
i check the J$S_TRG table it does not have the jrn_consumed and jrn_subscriber column names in it .
error message
904 : 42000 : java.sql.SQLException: ORA-00904: "JRN_SUBSCRIBER": invalid identifier

Is there a Log Miner View in 10.2 GRID

Hello,
I am trying to locate a tool on the GRID 10.2 for log miner. Where can I find this tool on the GRID. Thanks.

Not yet I guess.

Log Miner : cannot create dict file

Hi,
I try to generate the dictionary flat file for Log Miner on a database 817 on a windows 2000.
I do it with the sys account, I put the utl_file_dir init parameter but I get the following error :
SQL> EXECUTE DBMS_LOGMNR_D.BUILD(DICTIONARY_FILENAME =>'TEST.MNR',DICTIONARY_LO
CATION => 'F:\ORACLE\ADMIN\TEST\LOGMNR');
BEGIN DBMS_LOGMNR_D.BUILD(DICTIONARY_FILENAME =>'TEST.MNR',DICTIONARY_LOCATION
=> 'F:\ORACLE\ADMIN\TEST\LOGMNR'); END;
ERROR at line 1:
ORA-06532: Subscript outside of limit
ORA-06512: at "SYS.DBMS_LOGMNR_D", line 793
ORA-06512: at line 1
Thanks
Regards.

I found it :))
Modify the dbmslmd.sql script :
TYPE col_desc_array IS VARRAY(513) OF col_description;
to
TYPE col_desc_array IS VARRAY(900) OF col_description;

Is there any redo log reader tools other than the log miner?

HI all,
Is there any third party redo log reader tools other than the log miner?
thanks
V

OH MY! THAT WAS RIGHT IN FRONT OF ME THE WHOLE TIME!!
THANKS A LOT!!

Enq: MN - contention with log miner

One of our customers is hitting enq: MN - contention wait event.
UKJA@ukja102> exec print_table('select * from v$lock_type where type = ''MN'');
TYPE                          : MN
NAME                          : LogMiner
ID1_TAG                       : session ID
ID2_TAG                       : 0
IS_USER                       : NO
DESCRIPTION                   : Synchronizes updates to the LogMiner dictionary
and prevents multiple instances from preparing the same LogMiner session
-----------------The situation is as following
- Batch job is generating massive redo
- Frequent log file switching occurs during this job
- Multiple sessions are mining archive logs due to some business requirement
- From time to time, one session holds MN lock in excluisve mode and other sessions wait for the ML lock to be released.
Holding session and waiting sessions are executing same SQL statement like following.
SELECT SCN, SQL_REDO, SEG_OWNER, SEG_NAME, OPERATION_CODE, CSF,DATA_OBJ#,
XIDUSN || '_' || XIDSLT || '_' || XIDSQN) AS XID, ROW_ID, ROLLBACK, TIMESTAMP FROM V$LOGMNR_CONTENTS
WHERE (OPERATION_CODE IN (7, 36)
OR ( ( ROLLBACK = 0 OR (ROLLBACK = 1 AND CSF = 0) ) AND ( OPERATION_CODE IN (1, 2, 3)
AND ((SEG_OWNER = 'TEST1' AND TABLE_NAME = 'TABLE1')
OR (SEG_OWNER = 'TEST1' AND TABLE_NAME = 'TABLE2')
OR (SEG_OWNER = 'TEST1' AND TABLE_NAME = 'TABLE3')
OR (SEG_OWNER = 'TEST1' AND TABLE_NAME = 'TABLE4')
OR (SEG_OWNER = 'TEST1' AND TABLE_NAME = 'TABLE5')
OR (SEG_OWNER = 'TEST1' AND TABLE_NAME = 'TABLE6')
OR (SEG_OWNER = 'TEST1' AND TABLE_NAME = 'TABLE7')
OR (SEG_OWNER = 'TEST1' AND TABLE_NAME = 'TABLE8')
OR (SEG_OWNER = 'TEST1' AND TABLE_NAME = 'TABLE9')
OR (SEG_OWNER = 'TEST1' AND TABLE_NAME = 'TABLE10')
OR (SEG_OWNER = 'TEST1' AND TABLE_NAME = 'TABLE'11)
OR (SEG_OWNER = 'TEST1' AND TABLE_NAME = 'TABLE12')
OR (SEG_OWNER = 'TEST1' AND TABLE_NAME = 'TABLE13')
OR (SEG_OWNER = 'TEST1' AND TABLE_NAME = 'TABLE14')
OR (SEG_OWNER = 'TEST1' AND TABLE_NAME = 'TABLE15')
OR (SEG_OWNER = 'TEST1' AND TABLE_NAME = 'TABLE16')
OR (SEG_OWNER = 'TEST1' AND TABLE_NAME = 'TABLE17')
OR (SEG_OWNER = 'TEST1' AND TABLE_NAME = 'TABLE18')
OR (SEG_OWNER = 'TEST1' AND TABLE_NAME = 'TABLE19')
OR (SEG_OWNER = 'TEST1' AND TABLE_NAME = 'TABLE20')
OR (SEG_OWNER = 'TEST1' AND TABLE_NAME = 'TABLE21')
OR (SEG_OWNER = 'TEST1' AND TABLE_NAME = 'TABLE22')
OR (SEG_OWNER = 'TEST1' AND TABLE_NAME = 'TABLE23')
OR (SEG_OWNER = 'TEST1' AND TABLE_NAME = 'TABLE24')
OR (SEG_OWNER = 'TEST1' AND TABLE_NAME = 'TABLE25')
OR (SEG_OWNER = 'TEST1' AND TABLE_NAME = 'TABLE26')
OR (SEG_OWNER = 'TEST1' AND TABLE_NAME = 'TABLE27')))))But my experiments show that normal log miner operations do not need MN lock thus no MN lock contention is reproduceable. Same under the situation of very frequent log file switching.
Does anyone have experience and/or information on this lock?
================================
Dion Cho - Oracle Performance Storyteller
http://dioncho.wordpress.com (english)
http://ukja.tistory.com (korean)
================================

My first test case was flawed, so posted wrong info. :(
Further investigation shows that at certain steps of typical log miner operations need MN lock in exclusive mode. For example, dbms_logmnr.start_logmnr procedure needs exclusive MN lock.
Excerpt from 10704 event trace file.
*** 2009-05-19 13:57:53.812
ksqgtl *** MN-00000000-00000000 mode=6 flags=0x21 timeout=600 ***
ksqgtl: no transaction
ksqgtl: use existing ksusetxn DID
ksqgtl:
     ksqlkdid: 0001-0016-00000014
*** 2009-05-19 13:57:53.828
*** ksudidTrace: ksqgtl
     ksusesdi:   0000-0000-00000000
     ksusetxn:   0001-0016-00000014
ksqgtl: RETURNS 0
*** 2009-05-19 13:57:53.828
ksqrcl: MN,0,0
ksqrcl: returns 0Starting log mining operation would require modification on log miner dictionary.
This means that multiple sessions can't start log mining concurrently, but once they've started successfully other types of jobs can be done concurrently.
Any operation that should access the log miner dictionary would require MN lock. I would contact the customer who reported this problem and let them have more investigation.
================================
Dion Cho - Oracle Performance Storyteller
http://dioncho.wordpress.com (english)
http://ukja.tistory.com (korean)
================================

Log miner utility

Hi
How do i use the log miner utility to retreive the information from the generated archive logs?
Imran

Finf the below output.
SQL>EXECUTE DBMS_LOGMNR_D.BUILD( -
DICTIONARY_FILENAME =>'dictionary.ora', -
DICTIONARY_LOCATION => '/oracle/utl/');> >
PL/SQL procedure successfully completed.
SQL>
EXECUTE DBMS_LOGMNR.ADD_LOGFILSQL> E( -
LOGFILENAME => '/oracle/oradata/arch/1_61_715193506.arc', -
OPTIONS => DBMS_LOGMNR.ADDFILE);
>>
PL/SQL procedure successfully completed.
SQL> BEGIN
DBMS_LOGMNR.start_logmnr (
options => Dbms_Logmnr.DDL_Dict_Tracking);
END;
SELECT OPERATION, SQL_REDO, SQL_UNDO
FROM V$LOGMNR_CONTENTS
WHERE SEG_OWNER='SIFON';
no rows selected
I have deleted few rows and created logs manually. But it does not shows any rows. Did i left any steps. pls help me.

Log miner directory

Hi,
I am trying to create a log dictionary file to analyze log file content through log miner but I couldn't do it and all the time getting following error. It would be great if anyone help me. I'm using Oracle8i.
SQL> execute dbms_logmnr_d.build('logdict.ora','c:\oracle\oradata\');
BEGIN dbms_logmnr_d.build('logdict.ora','c:\oracle\oradata\'); END;
ERROR at line 1:
ORA-06550: line 1, column 7:
PLS-00201: identifier 'DBMS_LOGMNR_D.BUILD' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored
Thanks
Asif

DBMS_LOGMNR_D.BUILD (
     dictionary_filename IN VARCHAR2,
     dictionary_location IN VARCHAR2,
     options              IN NUMBER);
SQL> alter system set utl_file_dir=’<LOCATION>’ scope=spfile;
EXECUTE DBMS_LOGMNR_D.BUILD(‘Log-name’,'<LOCATION>’);Please refer to this :
http://docs.oracle.com/cd/B28359_01/appdev.111/b28419/d_logmnrd.htm

Log miner

Similar Messages

Maybe you are looking for