All groups of redo log is active
Hello dear gurus!After the closing of the database with the option "Cancel".
We have unconsisten State of data files.
I ask to explain:
(1) - ARCH background processes flashes all redo buffer in redolog?
(In other words how achieved consistency if all redo log groups was in Active state before you stop?)
(2) where the content buffer in this case are being dumped?
Thank you and best regards,
Pavel
Published by: Pavel on July 19, 2012 21:49
Pavel wrote:
After the closing of the database with the option "Cancel".
We have unconsisten State of data files.
I ask to explain:
(1) - ARCH background processes flashes all redo buffer in redolog?
(In other words how achieved consistency if all redo log groups was in Active state before you stop?)
He is the author of newspaper (lgwr) that copies the buffer log in log files - but if you make a judgment that the last piece of information in the log buffer is not copied, he lost.
Note: one of your log files will be CURRENT, that's the one that the editor of newspaper is written, ASSETS are simply online redo logs that are still necessary for recovery and therefore can not be overwritten.
(2) where the content buffer in this case are being dumped?
See (1) - they are not.
Concerning
Jonathan Lewis
Tags: Database
Similar Questions
-
One group of standby Redo Log is ACTIVE
Hi guys,.
I have successfully configured a custodian of data between a primary database (oradb) and a database ensures Physics (oradb_s8).
However, I have noticed that in V$ STANDBY_LOG only one group of standby Redo Log is ACTIVE, regardless of how many times I go log in the primary database.
' The following was stated in the documentation:
When a switch of newspaper occurs on the database of the source again, redo incoming is then written to the next group of waiting for redo log, and the group used newspaper before again Eve is archived by a foreground ARCn process.
So, I guess that group of standby Redo Log is turned on when the Redo Log is enabled in the primary database.
Could you please clarify it for me?
It's the Oracle 11 g R2 (11.2.0.1) on Red Hat Server 5.2.
On autonomy in standby:
SQL > SELECT GROUP #, THREAD #, SEQUENCE #, ARCHIVED, STATUS FROM V$ STANDBY_LOG
GROUP # THREAD # SEQUENCE # ARC STATUS
---------- ---------- ---------- --- ----------
4 1 248 YES ACTIVE <-this is the only group that is still ACTIVE
5 1 0 NOT ASSIGNED NO.
6 0 YES 0 UNASSIGNED
7 0 YES 0 UNASSIGNED
SQL > SELECT SEQUENCE #, APPLIED, FIRST_TIME NEXT_TIME
V $ ARCHIVED_LOG
SEQUENCE ORDER #;
SEQUENCE # FIRST_TIM NEXT_TIME APPLIED
---------- --------- --------- ---------
232 06-06-SEPT.-15-15-SEP YES
233 06-06-SEPT.-15-15-SEP YES
234 06-06-SEPT.-15-15-SEP YES
235 06-06-SEPT.-15-15-SEP YES
236 06-06-SEPT.-15-15-SEP YES
237 06-06-SEPT.-15-15-SEP YES
238 06-06-SEPT.-15-15-SEP YES
239 07-06-SEPT.-15-15-SEP YES
240 YES 15-SEP-07 07-SEVEN.-15
241 YES 15-SEP-07 07-SEVEN.-15
242 YES 15-SEP-07 07-SEVEN.-15
YES 243 15-SEP-07 07-SEVEN.-15
244 YES 15-SEP-07 07-SEVEN.-15
245 YES 15-SEP-07 07-SEVEN.-15
246 YES 15-SEP-08 15-SEP-07
247 15 - SEP - 08 IN-MEMORY 15-SEP-08
16 selected lines.
On the primary:
SQL > SELECT SEQUENCE #, APPLIED, FIRST_TIME NEXT_TIME
V $ ARCHIVED_LOG
WHERE NAME = 'ORADB_S8 '.
SEQUENCE ORDER #;
SEQUENCE # FIRST_TIM NEXT_TIME APPLIED
---------- --------- --------- ---------
232 06-06-SEPT.-15-15-SEP YES
233 06-06-SEPT.-15-15-SEP YES
234 06-06-SEPT.-15-15-SEP YES
235 06-06-SEPT.-15-15-SEP YES
236 06-06-SEPT.-15-15-SEP YES
237 06-06-SEPT.-15-15-SEP YES
238 06-06-SEPT.-15-15-SEP YES
239 07-06-SEPT.-15-15-SEP YES
240 YES 15-SEP-07 07-SEVEN.-15
241 YES 15-SEP-07 07-SEVEN.-15
YES 07-SEP-15 242 07-SEP-15
YES 243 15-SEP-07 07-SEVEN.-15
244 YES 15-SEP-07 07-SEVEN.-15
245 YES 15-SEP-07 07-SEVEN.-15
246 YES 15-SEP-08 15-SEP-07
247 NO. 15-SEP-08 08 - SEPT.-15
If you have a large DML activity on primary, you see more than one group # in v$ active standby_log.
RFS will always try to assign the next available standby log, because your group changes # 4 are already applied, it allocates this group again after the switch.
Check metalink doc: bug 2722195 and 219344.1
-
How to replace the members of the Group missing redo log after the failure of a support
Hello
I'm testing a disk failure scenario. I had recovery multiplexes on three sites (Windows drive letters) logs; one of the three locations also contained the data files. I deleted the Windows player that contained data files and saw a restoring with RMAN. All is well except that redo log members who are found on the occult Windows disk are of course still missing; the database opens, etc., but puts messages like this in the ALERT.log:
ORA-00321: log thread 2 1, cannot update log file header
ORA-00312: wire 2 1 online journal: ' F:\APP\NGORA12CR2SRV\ORADATA\ORATEST5\ONLINELOG\O1_MF_2_BW4B5MY0_. JOURNAL"What is the 'right' way to replace missing limbs? Just get all the new groups of newspapers with new members on all three discs? Carefully copy the LOG files representing missing members of one of the other sites? I add new members at this location and remove existing members (missing)?
Is how important it?
Thank you!
Martin
See 'Recover after losing a member of a group of Redo Logs online multiplexed'
at http://docs.oracle.com/cd/E11882_01/backup.112/e10642/osadvsce.htm#sthref2205
Hemant K Collette
-
Impossible to move a group of Redo Log
Hello
My database is running on version 11.1.0.7 on platform OEL.
I am trying to remove one of the Redo Log group Active, it fails with the error below. Could someone please help me solve this problem?
It was previously a node 3 CARS, and when he was moved to another machine, he got to build with a 2 RAC nodes.SQL > select * from v$log; GROUP# THREAD# SEQUENCE# BYTES MEMBERS ARCHIVED STATUS FIRST_CHANGE# FIRST_TIME ---------- ---------- ---------- ---------- ---------- --------- ------------------------------------------------ ------------- -------------------------- 10 1 8017 524288000 2 YES INACTIVE 1.2120E+13 17-JUN-2012 19:43:49 11 1 8018 524288000 2 YES INACTIVE 1.2120E+13 18-JUN-2012 06:49:45 12 1 8019 524288000 2 YES INACTIVE 1.2120E+13 18-JUN-2012 16:56:43 13 1 8021 524288000 2 YES INACTIVE 1.2120E+13 18-JUN-2012 23:18:07 14 1 8020 524288000 2 YES INACTIVE 1.2120E+13 18-JUN-2012 23:14:27 15 1 8022 524288000 2 NO CURRENT 1.2120E+13 19-JUN-2012 01:07:27 16 2 6835 524288000 2 YES INACTIVE 1.2120E+13 18-JUN-2012 23:15:46 17 2 6836 524288000 2 YES INACTIVE 1.2120E+13 18-JUN-2012 23:18:04 18 2 6837 524288000 2 YES INACTIVE 1.2120E+13 18-JUN-2012 23:20:22 19 2 6838 524288000 2 YES INACTIVE 1.2120E+13 18-JUN-2012 23:22:38 20 2 6839 524288000 2 NO CURRENT 1.2120E+13 19-JUN-2012 01:07:24 21 2 6832 524288000 2 YES INACTIVE 1.2120E+13 18-JUN-2012 23:11:45 22 3 3771 524288000 2 YES INACTIVE 1.2103E+13 09-SEP-2011 22:04:11 23 3 3772 524288000 2 YES INACTIVE 1.2103E+13 09-SEP-2011 23:55:55 24 3 3773 524288000 2 YES ACTIVE 1.2103E+13 09-SEP-2011 23:55:59 25 3 3766 524288000 2 YES INACTIVE 1.2103E+13 08-SEP-2011 22:05:29 26 3 3767 524288000 2 YES INACTIVE 1.2103E+13 08-SEP-2011 22:05:50 27 3 3768 524288000 2 YES INACTIVE 1.2103E+13 09-SEP-2011 14:02:05 SQL > archive log list; Database log mode Archive Mode Automatic archival Enabled Archive destination /archive/MYCSMA/MYCSMA2 Oldest online log sequence 6832 Next log sequence to archive 6839 Current log sequence 6839 SQL > archive log all; ORA-00271: there are no logs that need archiving SQL > ALTER SYSTEM ARCHIVE LOG GROUP 24; ALTER SYSTEM ARCHIVE LOG GROUP 24 * ERROR at line 1: ORA-16013: log 24 sequence# 3773 does not need archiving SQL > alter database drop LOGFILE group 24; alter database drop LOGFILE group 24 * ERROR at line 1: ORA-01623: log 24 is current log for instance MYCSMA3 (thread 3) - cannot drop ORA-00312: online log 24 thread 3: '/u247/oradata/MYCSMA/redo24_1.log' ORA-00312: online log 24 thread 3: '/u247/oradata/MYCSMA/redo24_2.log'
So, 3 wire is no more necessary. This is why I intend to drop these of Redo Log groups.
Thank you!Try
ALTER DATABASE DISABLE THREAD 3.
-
Ungroup all groups on a layer (JavaScript) active.
Does anyone know how you would you unlink all groups on a layer active with JavaScript?
looking for "Recursion", check this thread, Mark has an example of recursion of layers and groups.
-
Loss/Corruption of a Redo Log multiplex group member
Grid infrastructure: 11.2.0.4
DB version: 11.2.0.4
OS: RHEL 6.5
All recovery logs are multiplexed IE once. Copy of a mirror
I created a document on how to cope with the loss of a member of a group of Redo Log multiplex. It applies to DBs in ASM or Linux Filesystem.
If a member of a multiplex redo logs group is lost/damaged is in State assets or CURRENT (v$ log.status), will be the following work?
Assuming that the DB would not crash (well that's the whole point of multiplexing)
Step 1. Switch redo log group and bring him to the INACTIVE State IE. LGWR is not written for her now
Step 2. Remove the Member lost/damaged.
ALTER DATABASE DROP LOGFILE MEMBER "+ DATA_DG1/mbhsprd/onlinelog/group_1.256.834497203";
Apparently, this command does not actually remove the log file at the level of the ASM/OS; It updates only the control file
Step 3. If it is a corrupt then log file physically remove the damaged location ASM/OS file
Step 4. I hope the below will create a mirror copy of the survivor
ALTER DATABASE ADD LOGFILE MEMBER '+ DATA_DG1/mbhsprd/onlinelog/group_1.256.834497203' to GROUP 3.
The above steps won't work?
There is no point in writing in the document if you do not actually test what you write
It seems that you are working with Oracle managed files. In this case:
You will find that your "apparently" in step 2 is not correct, and that your step 4 will throw an ora-01276.
-
Recreate the Member lost/damaged redo log in a group
DB version: 11.2.0.4
OS: Oracle Linux 6.5
In this particular PB we have multiplexes recovery logs (2 members from each group of redo).
If one member of a group of Redo log is corrupted then, regardless of whether the Member belonged to the Group that is CURRENT, ACTIVE or INACTIVE, can we just let GO and CREATE the file journal lost this group member by following the steps below?
-Find the corrupted Member
SELECT GROUP #, STATUS, MEMBER OF V$ LOGFILE WHERE STATUS = 'INVALID ';
1 back UP the DB
2. CHANGE THE SYSTEM CHECKPOINT;
3 ALTER DATABASE CLEAR LOGFILE GROUP 3; - , This step should not be executed. Right?
4. ALTER DATABASE DROP LOGFILE MEMBER ' / oracle/oradata/wms/redo02.log';
(Apparently, this removes not the logfile at the OS level, only the control file is updated in the DB)
5 ALTER DATABASE ADD LOGFILE MEMBER ' / oracle/oradata/wms/redo02b.log' to GROUP 3.
When I googled for steps, I found the table below in the official documentation of the Oracle. This table is applicable only if the ENTIRE REDO LOG disappeared.
http://docs.Oracle.com/CD/E25054_01/backup.1111/e10642/osadvsce.htm#CACFJDBG
I want just the steps if only 1 member of a multiplex group is lost/damaged.
3. ALTER DATABASE CLEAR LOGFILE GROUP 3; -This step should not be executed. Right?
Yes. It's true. You can refer to the section 'Recovery after losing a member of the a multiplex online Redo Log group' under recovery after the loss of online redo log files: scenarios
HTH
-Jonathan Rolland
-
Adding more large size Redo log groups in RAC, ASM
Hi people,
Version of database - 10.1.0.4.0
Version of the OS - AIX 5.3
Node 2 RAC and ASM
We had 4 groups of log roll forward of any size on the two nodes.yesterday, I added 4 new larger size groups using pl/sql developer tool and deleted the old 2 redolog groups. But I'm not able to remove the rest of the 2 groups of old.
ORA-01567 a log2 fall would have less than 2 log files for example 1.
Our redolog files are the SAN and the two points of the same storage node. When I pulled this command line query
SELECT v$ logfile.member, v$ logfile.group #, v$ log.status, v$ log.bytes
V $ log v$ logfile
WHERE v$ log.group # v = $logfile.group #;
I had the same result for both nodes.
The problem that I think, is that all 4 new newspaper groups are added to instance 2 and its old 2 grouips are are also deleted.
Now my question is that:
1 should I I added groups of redo log separately on the two nodes of storage is the same for both nodes?
2 redologs groups are defined separately for each node?
How can I assign 2 new groups of newspapers to instantiate redo 1?
Kind regardsRedo log group should minus 2 groups each of the thread.
But it is good to use 3 groups... each of the threads.and 2 members on each of the groups.
all redo check journal... from v$ session, v$ logfile, v$ archvied_log
If you mean the idea to determine approximately the size of the log to roll forward... you can check newspaper alerts.
or
ALTER session set nls_date_format = "YYYY/MM/DD HH24:MI:SS;
Select INST_ID select, name, control gv completion_time $ archived_log by 3.1.Good luck
-
I have to create the new group for waiting for redo log files?
I have 10 group of files redo log with 2 members of each group for my primary database, I need to create new group for redo log files for the database of relief pending
Group # members
==============
1 2
2 2
3 2
4 2
5 2
6 2
7 2
8 2
9 2
2 of 10
If so, the following statement is correct? or nto
ALTER DATABASE ADD STANDBY LOGFILE GROUP 1 ('D:\Databases\epprod\StandbyRedoLog\REDO01.) LOG',D:\Databases\epprod\StandbyRedoLog\REDO01_1.log');
Please correct me if am doin wrong
because when I run the statement I have error message saying: the group is already created.
Thanks John
I just found the answer
Yes, it of recomeded to add the new group, for instnace if I have 10 group of 1 to 10, then the wait should be from 11 to 20
Thanks I found the answer.
-
Controlfile and Redo Log on a disk group
Hello!
Controlfile and Redo Log on a disk group - it's good or bad?
You have the best practices or Doc ID on Metalink?918027 wrote:
You must have two control files on two separate disks and at least 2 members of each group redolog, each on a separate drive.http://docs.Oracle.com/CD/B10500_01/server.920/a96521/control.htm#4578
No, you do not have "must have".
You have not yet 'must have' more than a control queue.
You do not have 'must have' more than 2 redo log groups, and these groups don't 'must have', but one file each.This is the "must have".
Now, it's something else.
You "should" have a minimum of 2 files of control, and that they "should" (not "needs") be on separate disks.
You "should" have at least 2 files of members in each group of redo log, and that they "should" (not "needs") be on separate disks.And FWIW, I see no reason to keep necessarily completely separate redo file control file. They key is to have versions multiplexed of a particular type, separated from their 'twin '.
-
I have a dowstreams that has four groups of log roll forward pending. one of these groups is always in a redo of the day 23/04/2010. This former roll forward is not filed, always there.
This implies that the endorsements of the database are working with three groups of redo log and some oacaciones all that is in the active State and at this time that the view v $ archived_dest returns the error for that destination (natural).
the question is:
How can I eliminate this newspaper waiting for redo which is more archived.
Thank you very much for your attentionYou have error messages in the alert log?
See this Metalink Note:
Alert.log watch no. standby redo Logfiles of size 153600 available blocks [405836.1 ID] -
Hello
We will soon migrate our database in an environment with active archivelogs. Common sense is, if possible, recovery logs and the archivelogs must reside in independent storage subsystems. But I wanted to know if there is an advantage of performance for storage to different groups of newspapers in the subsystems of storage independent also.
Thank you.Some slightly possible advantage if you have very high Redo write rate.
So, if your 3 groups of Redo Log Online are on Disk_1, Disk_2, and Disk_3 (each being a physical separate disk / disk group), then your ArchiveLogs go to Disk_AL what can happen is
LGWR writes in Disk_1
First group ended and LGWR switches
LGWR began writing at Disk_2
ARC starts to read Disk_1 and write to Disk_AL
Second group ended and LGWR switches
LGWR began writing at Disk_2 - sorry, Disk_3
When ARK ends wrote Group1 to Disk_AL, he now began reading Disk_2In this way, it is there never discord IO disc between LGWR writes a group of newspapers online redo and ARCH read an online Redo Log group - which could happen otherwise, if all the Oneline Redo Log groups are on the same disk / DiskGroup.
This type of design is to 'extreme '!
Published by: Hemant K Collette on May 20, 2009 17:51
Published by: Hemant K Collette on May 20, 2009 22:13
Update of the third LGWR write on disk as Disk_3 -
How to create Redo Log as a good way to avoid the problem of performance
Hi Experts,
I work in the following environment.
OS - Windows server 2012
version - 11.2.0.1.0
Server: production server
1 to 10 of each month, we have huge process. Like many DML and ddl involve.
I've implemented the RMAN also.
My Alerts log entry is as below,
Kills Sep 08 17:05:34 2015
Thread 1 cannot allot of new newspapers, 88278 sequence
Private stream flush is not complete
Currently journal # 1, seq # 88277 mem # 0: D:\APP\ADMINISTRATOR\ORADATA\AWSPROCESS\REDO01. JOURNAL
Thread 1 Advanced to record the sequence 88278 (switch LGWR)
Currently Journal # 2 seq # 88278 mem # 0: D:\APP\ADMINISTRATOR\ORADATA\AWSPROCESS\REDO02. JOURNAL
Kills Sep 08 17:05:38 2015
Archived journal 81073 extra for each sequence 1 88277 0x38b3fdf6 dest ID thread entry 1:
Kills Sep 08 17:05:52 2015
Thread 1 cannot allot of new newspapers, sequence 88279
Checkpoint is not complete
Currently Journal # 2 seq # 88278 mem # 0: D:\APP\ADMINISTRATOR\ORADATA\AWSPROCESS\REDO02. JOURNAL
Thread 1 Advanced to record the sequence 88279 (switch LGWR)
Currently Journal # 3 seq # 88279 mem # 0: D:\APP\ADMINISTRATOR\ORADATA\AWSPROCESS\REDO03. JOURNAL
Kills Sep 08 17:05:58 2015
Archived journal 81074 extra for each sequence 1 88278 0x38b3fdf6 dest ID thread entry 1:
Kills Sep 08 17:06:16 2015
Thread 1 cannot allot of new newspapers, sequence 88280
Checkpoint is not complete
When I check in the internet I found a few points and need clarity also by the following.
-It is recommended that this switch Redo log 5 times maximum per hour, but I have this time of maximum peak about 100 redo log changes occur.
-It is recommended to have the large size of the Redo log. But I have 3 Group of redo and each size is 50 MB by default.
-My group of Redo log not multiplexed and it by default with each group have only a single Member
Group 1 - D:\APP\ADMINISTRATOR\ORADATA\AWSPROCESS\REDO01. JOURNAL
Group 2 - D:\APP\ADMINISTRATOR\ORADATA\AWSPROCESS\REDO02. JOURNAL
Group 3 - D:\APP\ADMINISTRATOR\ORADATA\AWSPROCESS\REDO03. JOURNAL
And advised by experts with add that again group will give more performance in the other location. Is it mean that I need to add the Redo log as a different group, player or Redo Log itself I need to replace the other location.
Say in the end, My Live server works with the location and size of restore default. I'm trying to create a better way and get all confused
How to do it perfectly.
Experts, please share your comments to my environment to log redo instance as better through your comment or recommended weblink based on my above needs, or a document.
Thanks in advance, if you need more information to help me, then ask me, I'll share you.
Hello
You can't resize an existing redo log group.
You will need to create 3 new redo log groups and drop old log redo (with 200 MB size) groups.
Here you can find a good explanation: DBA for Oracle tips Archives
-
A PL/SQL to add the archived redo log for logminer files - please help debug
Hello
I have a PL/SQL to add recovery logs a day archived files to logminer utility in order to catch all LMD, which happened for a paticular at a particular time scheme
as below,
-logmnr.sql
Set serveroutput on
declare
v_redo_dictionary_file VARCHAR2 (100);
v_archived_log_file VARCHAR2 (100);
-catch all them archived redo logs today, put in a cursor
CURSOR logfile_cur IS
SELECT name from v$ archived_log WHERE the to_char (COMPLETION_TIME, 'dd_MM_yyyy') > '18_01_2010' and not in sequence # (select sequence # v$ archived_log WHERE DICTIONARY_BEGIN = 'YES' AND dictionary_end = 'YES');
Start
-Create the DICTIONARY file on the files of the SOURCE database redo
sys. DBMS_LOGMNR_D.build (OPTIONS = > sys.) DBMS_LOGMNR_D.store_in_redo_logs);
Select name from v_redo_dictionary_file from v$ archived_log where DICTIONARY_BEGIN = 'YES' AND dictionary_end = 'YES', and sequence # = (select MAX(sequence#) from v$ archived_log WHERE DICTIONARY_BEGIN = 'YES' AND dictionary_end = 'YES');
-Add newspapers of dictionary files
sys.dbms_logmnr.add_logfile (nom_fichier_journal = > v_redo_dictionary_file,)
Options = > sys.dbms_logmnr.new);
-Add the log files
Open logfile_cur;
LOOP
SEEK logfile_cur INTO v_archived_log_file;
EXIT WHEN logfile_cur % NOTFOUND;
sys.dbms_logmnr.add_logfile (nom_fichier_journal = > v_archived_log_file);
END LOOP;
CLOSE Logfile_cur;
-Start LogMiner, also enable the ddl
sys.dbms_logmnr.START_LOGMNR (options = > dbms_logmnr.dict_from_redo_logs + dbms_logmnr.ddl_dict_tracking);
EXCEPTION
WHILE OTHERS
THEN
DBMS_OUTPUT. PUT_LINE (SQLERRM);
END;
/
###############
SQL > @logmnr.sql
ORA-01291: missing logfile
PL/SQL procedure successfully completed.
What I did wrong?
Thank you very much
Roy[Double wire | http://forums.oracle.com/forums/message.jspa?messageID=4035521#4035521]
-
Will the DB down if INACTIVE redo log group is deleted?
Platform: Oracle Linux 6.5
DB version: 11.2
If I delete one or all members of a Redo Log group online that is IDLE, manually (using the rm command) will be the DB crash?
Instead of everybody speculating, why not just run a test?
Oracle 11.2.0.1, Enterprise Edition, 64-bit on OL 5, running in archivelog mode
SQL> select group#, 2 sequence#, 3 archived, 4 status 5 from v$log 6 order by group# 7 ; GROUP# SEQUENCE# ARC STATUS ---------- ---------- --- ---------------- 1 1 YES INACTIVE 2 2 YES INACTIVE 3 3 NO CURRENT 3 rows selected. SQL> -- SQL> insert into scott.mytest values (sysdate); 1 row created. SQL> commit; Commit complete. SQL> alter system switch logfile; System altered. SQL> select * from v$logfile; GROUP# STATUS TYPE MEMBER IS_ ---------- ------- ------- ------------------------------ --- 3 ONLINE /oradata/tulsa/redo03.rdo NO 2 ONLINE /oradata/tulsa/redo02.rdo NO 1 ONLINE /oradata/tulsa/redo01.rdo NO 3 rows selected. SQL> SQL> select group#, 2 sequence#, 3 archived, 4 status 5 from v$log 6 order by group# 7 ; GROUP# SEQUENCE# ARC STATUS ---------- ---------- --- ---------------- 1 4 NO CURRENT 2 2 YES INACTIVE 3 3 NO ACTIVE 3 rows selected.Group 2 is inactive, so delete the
SQL> !rm /oradata/tulsa/redo02.rdo SQL> !ls -l /oradata/tulsa/redo02.rdo ls: /oradata/tulsa/redo02.rdo: No such file or directory
And continue the activity of db. Keep an eye on the #2 group
SQL> select group#, 2 sequence#, 3 archived, 4 status 5 from v$log 6 order by group# 7 ; GROUP# SEQUENCE# ARC STATUS ---------- ---------- --- ---------------- 1 4 NO CURRENT 2 2 YES INACTIVE 3 3 YES ACTIVE 3 rows selected. SQL> insert into scott.mytest values (sysdate); 1 row created. SQL> commit; Commit complete. SQL> alter system switch logfile; System altered. SQL> -- SQL> select group#, 2 sequence#, 3 archived, 4 status 5 from v$log 6 order by group# 7 ; GROUP# SEQUENCE# ARC STATUS ---------- ---------- --- ---------------- 1 4 NO ACTIVE 2 5 NO CURRENT 3 3 YES ACTIVE 3 rows selected. SQL> insert into scott.mytest values (sysdate); 1 row created. SQL> commit; Commit complete. SQL> alter system switch logfile; System altered. SQL> -- SQL> select group#, 2 sequence#, 3 archived, 4 status 5 from v$log 6 order by group# 7 ; GROUP# SEQUENCE# ARC STATUS ---------- ---------- --- ---------------- 1 4 YES INACTIVE 2 5 NO ACTIVE 3 6 NO CURRENT 3 rows selected. SQL> insert into scott.mytest values (sysdate); 1 row created. SQL> commit; Commit complete. SQL> alter system switch logfile; System altered. SQL> -- SQL> select group#, 2 sequence#, 3 archived, 4 status 5 from v$log 6 order by group# 7 ; GROUP# SEQUENCE# ARC STATUS ---------- ---------- --- ---------------- 1 7 NO CURRENT 2 5 NO ACTIVE 3 6 NO ACTIVE 3 rows selected. SQL> insert into scott.mytest values (sysdate); 1 row created. SQL> commit; Commit complete. SQL> alter system switch logfile;At this point, the SWTICH LOGFILE command has been attached, and in the alerts log, we see this:
CJQ0 started with pid=26, OS id=4817 Sat Sep 19 10:48:11 2015 Thread 1 advanced to log sequence 4 (LGWR switch) Current log# 1 seq# 4 mem# 0: /oradata/tulsa/redo01.rdo Sat Sep 19 10:48:11 2015 Archived Log entry 1 added for thread 1 sequence 3 ID 0xdaf1e381 dest 1: Sat Sep 19 10:48:44 2015 Thread 1 advanced to log sequence 5 (LGWR switch) Current log# 2 seq# 5 mem# 0: /oradata/tulsa/redo02.rdo Sat Sep 19 10:48:44 2015 Archived Log entry 2 added for thread 1 sequence 4 ID 0xdaf1e381 dest 1: Thread 1 cannot allocate new log, sequence 6 Checkpoint not complete Current log# 2 seq# 5 mem# 0: /oradata/tulsa/redo02.rdo Thread 1 advanced to log sequence 6 (LGWR switch) Current log# 3 seq# 6 mem# 0: /oradata/tulsa/redo03.rdo Sat Sep 19 10:48:48 2015 Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc3_4789.trc: ORA-00313: open failed for members of log group 2 of thread 1 ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo' ORA-27037: unable to obtain file status Linux-x86_64 Error: 2: No such file or directory Additional information: 3 Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc3_4789.trc: ORA-00313: open failed for members of log group 2 of thread 1 ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo' ORA-27037: unable to obtain file status Linux-x86_64 Error: 2: No such file or directory Additional information: 3 Thread 1 advanced to log sequence 7 (LGWR switch) Current log# 1 seq# 7 mem# 0: /oradata/tulsa/redo01.rdo ARCH: Archival stopped, error occurred. Will continue retrying ORACLE Instance tulsa - Archival Error Thread 1 cannot allocate new log, sequence 8 Checkpoint not complete Current log# 1 seq# 7 mem# 0: /oradata/tulsa/redo01.rdo ORA-16038: log 2 sequence# 5 cannot be archived ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo' Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc3_4789.trc: ORA-16038: log 2 sequence# 5 cannot be archived ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo' Sat Sep 19 10:48:48 2015 Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc0_4777.trc: ORA-00313: open failed for members of log group 2 of thread 1 ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo' ORA-27037: unable to obtain file status Linux-x86_64 Error: 2: No such file or directory Additional information: 3 Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc0_4777.trc: ORA-00313: open failed for members of log group 2 of thread 1 ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo' ORA-27037: unable to obtain file status Linux-x86_64 Error: 2: No such file or directory Additional information: 3 Sat Sep 19 10:48:48 2015 Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_m000_4864.trc: ORA-00313: open failed for members of log group 2 of thread 1 ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo' ORA-27037: unable to obtain file status Linux-x86_64 Error: 2: No such file or directory Additional information: 3 Checker run found 2 new persistent data failures ORACLE Instance tulsa - Can not allocate log, archival required Thread 1 cannot allocate new log, sequence 8 All online logs needed archiving Current log# 1 seq# 7 mem# 0: /oradata/tulsa/redo01.rdo Sat Sep 19 10:48:59 2015 Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc2_4785.trc: ORA-00313: open failed for members of log group 2 of thread 1 ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo' ORA-27037: unable to obtain file status Linux-x86_64 Error: 2: No such file or directory Additional information: 3 Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc2_4785.trc: ORA-00313: open failed for members of log group 2 of thread 1 ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo' ORA-27037: unable to obtain file status Linux-x86_64 Error: 2: No such file or directory Additional information: 3 Sat Sep 19 10:48:59 2015 Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc1_4781.trc: ORA-00313: open failed for members of log group 2 of thread 1 ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo' ORA-27037: unable to obtain file status Linux-x86_64 Error: 2: No such file or directory Additional information: 3 Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc1_4781.trc: ORA-00313: open failed for members of log group 2 of thread 1 ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo' ORA-27037: unable to obtain file status Linux-x86_64 Error: 2: No such file or directory Additional information: 3 Sat Sep 19 10:49:59 2015 Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc2_4785.trc: ORA-00313: open failed for members of log group 2 of thread 1 ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo' ORA-27037: unable to obtain file status Linux-x86_64 Error: 2: No such file or directory Additional information: 3 Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc2_4785.trc: ORA-00313: open failed for members of log group 2 of thread 1 ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo' ORA-27037: unable to obtain file status Linux-x86_64 Error: 2: No such file or directory Additional information: 3 Sat Sep 19 10:49:59 2015 Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc3_4789.trc: ORA-00313: open failed for members of log group 2 of thread 1 ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo' ORA-27037: unable to obtain file status Linux-x86_64 Error: 2: No such file or directory Additional information: 3 Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_arc3_4789.trc: ORA-00313: open failed for members of log group 2 of thread 1 ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo' ORA-27037: unable to obtain file status Linux-x86_64 Error: 2: No such file or directory Additional information: 3 Sat Sep 19 10:49:59 2015 Errors in file /u01/app/oracle/diag/rdbms/tulsa/tulsa/trace/tulsa_m000_5163.trc: ORA-00313: open failed for members of log group 2 of thread 1 ORA-00312: online log 2 thread 1: '/oradata/tulsa/redo02.rdo' ORA-27037: unable to obtain file status Linux-x86_64 Error: 2: No such file or directory Additional information: 3
Maybe you are looking for
-
How can I get the computer to indicate when an e-mail arrived.
I would like the computer to indicate with a sound of my choice, when an e-mail arrived. This would be useful when I'm not working in other programs. I use the latest version of Firefox.
-
HP 14-r208nv: no driver found for x 84 OS win7 (hp 14-r208nv wifi problems) and BRIGHTNESS
-
Need assistance to recover gamertag
Help! MICROSOFT WONT GIVE ME GAMERTAG OR REFUND MICROSOFT POINTS... I ME LIKE A BALL PINBALL GAME! After 4 years and more than 40 emails WHY USED MICROSOFT RESET MY PASSWORD on MY GAMERTAG GABENO my only current in mcspaddi .i responded to ALL previo
-
C740 Chromebook 11 display distortion
I'm having a problem with this particular model and replacement screens. I was able to check the number on about 40 machines Acer C740. As part of a school program, students were issued this model Chromebook and often break views. I ordered several d
-
Download laserjet 2600n toolbox
How can I find and download for Laserjet 2600n Toolbox