ORA-00310: archived log contains sequence 12; sequence 9 required : [message #562577] |
Thu, 02 August 2012 06:50 |
|
priteshranjan.preet
Messages: 131 Registered: April 2012 Location: delhi
|
Senior Member |
|
|
hi i perform logminer in os (window xp and oracle linux 6) both. all the operation are successfully completed but at last i found the same error in both os. the error is
SQL> create table myLogAnalysis
as
select * from v$logmnr_contents;
select * from v$logmnr_contents
*
ERROR at line 3:
ORA-00310: archived log contains sequence 12; sequence 9 required
ORA-00334: archived log:
'/home/oracle/oracle/product/10.2.0/oradata/orcl/redo02.log'
how can i resolve this please help me.
oracle 10g(10.2.0.1.0)
thanks & regards
pritesh ranjan
|
|
|
|
Re: ORA-00310: archived log contains sequence 12; sequence 9 required : [message #562600 is a reply to message #562580] |
Thu, 02 August 2012 12:57 |
|
priteshranjan.preet
Messages: 131 Registered: April 2012 Location: delhi
|
Senior Member |
|
|
i already run this procedure.
SQL> begin
dbms_logmnr.add_logfile
(
logfilename => '/home/oracle/oracle/product/10.2.0/oradata/orcl/redo02.log',
options => dbms_logmnr.new
);
end;
/
i search this procedure DBMS_LOGMNR_SESSION.ADD_LOG_FILE. on google but not found. can i run this procedure like this
SQL> begin
DBMS_LOGMNR_SESSION.ADD_LOG_FILE
(
logfilename => '/home/oracle/oracle/product/10.2.0/oradata/orcl/redo02.log',
options => dbms_logmnr.new
);
end;
/
if not then please know me the syntax or step or any link.
thanks & regards
pritesh ranjan
7827825499
[Edit MC: add code tags and remove useless ending empty lines]
[Updated on: Thu, 02 August 2012 13:02] by Moderator Report message to a moderator
|
|
|
|
|
|
Re: ORA-00310: archived log contains sequence 12; sequence 9 required : [message #562657 is a reply to message #562650] |
Fri, 03 August 2012 03:12 |
|
priteshranjan.preet
Messages: 131 Registered: April 2012 Location: delhi
|
Senior Member |
|
|
hi please help me i use the following code.
sql>startup
ORACLE instance started.
Total System Global Area 289406976 bytes
Fixed Size 1248576 bytes
Variable Size 109052608 bytes
Database Buffers 171966464 bytes
Redo Buffers 7139328 bytes
Database mounted.
Database opened.
SQL> select log_mode from v$database;
LOG_MODE
------------
ARCHIVELOG
SQL> show parameter utl_file_dir;
NAME TYPE VALUE
------------------------------------
----------- ------------------------------
utl_file_dir string
c:\log_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> alter system switch logfile;
System altered.
SQL> select g.group# , g.status , m.member
from v$log g, v$logfile m
where g.group# = m.group#
and g.status = 'CURRENT';
GROUP# STATUS------MEMBER------
2 CURRENT D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO02.LOG
SQL> create table scott.test_logmnr
(id number,
name varchar2(10)
);
Table created.
SQL>begin
dbms_logmnr_d.build
(
dictionary_filename => 'dictionary.dic',
dictionary_location => 'c:\log_dir',
options => dbms_logmnr_d.store_in_flat_file
);
end;
SQL> /
PL/SQL procedure successfully completed.
SQL> conn scott/tiger
Connected.
SQL> insert into test_logmnr values
(1,'TEST1');
1 row created.
SQL>
insert into test_logmnr values (2,'TEST2');
1 row created.
SQL> insert into test_logmnr values
(3,'TEST3');
1 row created.
SQL> commit;
Commit complete.
SQL> update test_logmnr set name = 'TEST';
3 rows updated.
SQL> commit;
Commit complete.
SQL> delete from test_logmnr;
3 rows deleted.
SQL> commit;
Commit complete.
SQL> conn / as sysdba
Connected.
SQL> select g.group# , g.status , m.member
from v$log g, v$logfile m
where g.group# = m.group#
and g.status = 'CURRENT';
GROUP# STATUS-----------MEMBER------
2 CURRENT D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO02.LOG
SQL> begin
dbms_logmnr.add_logfile
(
logfilename => 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO02.LOG',
options => dbms_logmnr.new
);
dbms_logmnr.add_logfile
(
logfilename => 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO03.LOG',
options => dbms_logmnr.ADDFILE
);
end;
/
PL/SQL procedure successfully completed.
SQL> select filename from v$logmnr_logs;
FILENAME
--------------------------------------------------------------------------------
D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO03.LOG
D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO02.LOG
SQL> begin
2 dbms_logmnr.start_logmnr
3 (
4 dictfilename =>
5
6 'c:\log_dir\dictionary.dic',
7 options =>
8
9 dbms_logmnr.print_pretty_sql +
10
11
12 dbms_logmnr.no_sql_delimiter +
13
14
15 dbms_logmnr.ddl_dict_tracking
16 );
17 end;
18 /
PL/SQL procedure successfully completed.
SQL> create table myLogAnalysis
2 as
3 select * from v$logmnr_contents;
select * from v$logmnr_contents
*
ERROR at line 3:
ORA-00310: archived log contains sequence 67; sequence 64 required
ORA-00334: archived log: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO02.LOG'
SQL>
where i have done error please help me.
thanks & regards
pritesh ranjan
7827825499
|
|
|
Re: ORA-00310: archived log contains sequence 12; sequence 9 required : [message #562658 is a reply to message #562657] |
Fri, 03 August 2012 03:35 |
|
Michel Cadot
Messages: 68728 Registered: March 2007 Location: Saint-Maur, France, https...
|
Senior Member Account Moderator |
|
|
- Never ever use SYS (or SYSDBA) but for maintenance purpose (startup, shutdown, backup, recover)
- SYS/SYSDBA is special
- SYS/SYSDBA is Oracle proprietary (try to open a SR/TAR starting with "i did that with SYS/SYSDBA" and you'll see the immediate answer)
- SYS/SYSDBA does not act like any other user
- When you use SYS/SYSDBA Oracle deactivates some code path and activates others
- Whatever you do with SYS/SYSDBA will neither validate nor invalidate the same thing with any other user.
NEVER EVER use SYS/SYSDBA for anything that can be done by another user.
Use SYS/SYSDBA ONLY for something that can't be done by someone else.
Michel Cadot wrote on Thu, 02 August 2012 20:10...Also, Please read OraFAQ Forum Guide and How to use [code] tags and make your code easier to read.
Make sure that lines of code do not exceed 80 characters when you format.
Indent the code, use code tags and align the columns in result.
Use the "Preview Message" button to verify.
...
please help us to help you.
Regards
Michel
|
|
|