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 regards
Redo 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
Tags: Database
Similar Questions
-
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
-
Windows Server 2008 64 bit - Oracle 11g (11.02.0)
We have our first oracle database implementation.
The go live is supposed to happen in March or April.
Our Oracle courses will begin next week, but because of the performance, I need to change the size of redo log groups.
Users are just load data of the year 2010 in the database, but the performance is terrible.
I would like to know if it is possible to do using the Manager of the company.
I was able to modify the storage spaces and their files, but I don't succeed with redo log groups.
I have 3 groups with 50 MB each. I would change the 500 MB each.
When I try to change groups, it does not open the possibility of change.
Do I have to stop the database? do I have to clean the Group? How can I change the size of them?
EduardoHello
As vmalepati says, you can't resize redo log groups.
Create three new newspaper groups, with the size you need.
As the database is through the loggroups, you will be able to drop the 'old' (small ones).(1) find the instance in OEM
2) enter the tab "Server".
(3) with the 'storage', press 'Redo log groups'
(4) connect the database with a strong user
(5) use the "create as.
(6) change the size and all the other things you need and press "ok".
(7) repeat 5 & 6 until you have the number of new redo log groups you need
(8) remove the old redologs. Choose those showing "inactive".To force a logswitch, newspaper in sqlplus as user hard (System, for example) and run the command
alter system switch logfile;Best regards
Anders. -
[Account] redo logs groups and its members?
Hello gurus,
Well well, the theory written in the book may be different on the actual situation, different configuration of the different company...
How we determine how many redo logs groups it is should be? And how many members each group better?
What are the considerations?
Kind regards
NIA...What are the considerations?
How journal frequent switches under the load of work 'normal' (time in minutes)?
Can the archiver complete its work before this log file is required to be used again? -
How much max redo log groups we create and how many members max groups can created b
Here are the most bone depenedent. They are defined during the creation of the database or the creation of control files are identified by the MAXLOGFILES and MAXLOGMEMBERS parameters respectively.
They may have a value maximum 255 and 5 respectively
-
10G.2 ORacle vErsion on HP - UX11.31 (archivelog mode)
I have 3 redo group, each group of redo 1 Redo memmber; If my group again 3 become missing or corrupted (and I can't start my dabatase), how can I recover my database?RESETLOGS option requires one case when you lost all the group not an individual group
SQL> shutdown immediate Database closed. Database dismounted. ORACLE instance shut down. SQL> startup ORACLE instance started. Total System Global Area 171966464 bytes Fixed Size 787988 bytes Variable Size 145750508 bytes Database Buffers 25165824 bytes Redo Buffers 262144 bytes Database mounted. ORA-00313: open failed for members of log group 3 of thread 1 ORA-00312: online log 3 thread 1: 'F:\ORACLE\PRODUCT\10.1.0\ORADATA\PROD\REDO03.LOG' SQL> shutdown immediate ORA-01109: database not open Database dismounted. ORACLE instance shut down. SQL> startup mount ORACLE instance started. Total System Global Area 171966464 bytes Fixed Size 787988 bytes Variable Size 145750508 bytes Database Buffers 25165824 bytes Redo Buffers 262144 bytes Database mounted. SQL> alter database open resetlogs 2 / alter database open resetlogs * ERROR at line 1: ORA-01139: RESETLOGS option only valid after an incomplete database recovery
To Op
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/recoscen.htm#i1006437
Khurram
-
Hello
I work with oracle RAC 11gr2.0.3.
We have an expectation to top event 'parallel log file reading', and other types of waiting as 'log sequential read', 'log file sync '...
When I check the size of redo log = 50 M, while in the old database oracle 10 g 2 (no CARS), the size of redo log = 150 M.
So, I want to know if I should increase our redo log in our Oracle RAC database, or not?
Should be again small use connect oracle RAC, oracle RAC without difference?
Thank you for your help.
No matter the size, it is recommended to use at least 3 groups of newspapers by thread. This is particularly important if the archive log mode is activated.
See you soon,.
Brian
-
What is the hard drive more large size taken supported by the HP Pavilion a6650f?
Hello, I have a HP Pavilion a6650f that I got from a friend a few years ago.
I'm looking into upgrading the hard drive to a SATA 1 TB or 2 TB drive. The vehicle currently has a 80 GB IDE drive. I know it is originally with a 500 GB SATA drive (which was later to be defective, so he gave it to me after his warranty missed). The original drive left after that (of course) missed coverage.
He currently runs Ubuntu Linux 12.04 EAP 32-bit.
This PC would be able to use the 2 TB drive Seagate Barracuda ST2000DM001 7 200 RPM?
The computer should be fine with SATAII disks up to 2 TB. Greater than 2 to cause problems for you. In addition, you may need to update the drivers for the readers of Format 'Advance '.
-
Redo log size of the defect of EBS
Hi all
EBS R12.2.4
11 GR 2
Rhel6.5
I noticed that the installation by dΘfaut of EBS has only two 1 GB size redo log groups.
Is this acceptable to perform better?
Your comment is very much appreciated.
Thank you very much
JC
Protection for the primary database in three ways:
Maximum availability: Transactions on the primary do not commit to redo information was written for the online redo log and newspapers awaiting restoration by progression of at least a place to sleep. If no location intelligence is available, it in the same way as the maximum performance mode until a standby is available again.
Maximum performance: Transactions on the validation of primary as soon as redo information has been written for the online redo log. Transfer of information to roll forward to the standby server is asynchronous, so it has no impact on the performance of the primary.
Maximum protection: the Transactions on the primary do not commit to redo information was written for the online redo log and newspapers awaiting restoration by progression of at least a place to sleep. If the standby not suitable location is available, the primary database stops.By default, a newly created Eve, the primary database is in maximum performance mode.
I suggest to use the maximum performance with delay mode in the application of 15 minutes. You can drop the idea of delay if you are not comfortable with data loss
concerning
Pravin
-
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 '.
-
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.
-
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
-
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:49Pavel 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 -
Hi I got very confused by looking at the documentation of redo log groups and members of 11g.
Please could someone help me with that?
-What is the difference between a group of newspapers of restoration by progress and members within the Group?
-How does add a member help protect / multiplex a group?
-I am course I've read that if all members of the current redo log group are damaged, then 2 other groups does not bring the database back to how it was? ... so what's the point of having them?
Any help would be appreciated806595 wrote:
OK thanks, so again an allows for example, we had only one newspaper group and the database was NOT in archivelog mode, once the newspaper filled redo id, it would be re-written and proevious changes would be lost?Before you start, don't forget not that whenever you would need redolog groups, this will be the mandatory requirement, 2:1, and that means that 2 groups of newspaper with 1 member of each. Now, the newspaper group is a logic thing. There is no such thing actually exists. His way to the club/join/merge/combine/group multiple and physics redo log files that are written together. A minimum of a physical member is a must in a group, therefore 2:1.
Now, groups of newspapers (and in their midst, the log files are in fact) are written sequentially by LGWR, which means that LGWR would write about a group and all its members at the same time, fill it out completely and then made a switch (called a LOG SWITCH) to the next group of inactive log and keeps current processes. This is why a minimum of paper two groups are needed for the LGWR to work. The ius of work done on a single group and when the switch happens, work of the previous, filled will be controlled for the data files and will be marked as inactive thereafter, which makes even elgible for the LGWR to write to.
HTH
Aman...
Maybe you are looking for
-
DeskJet 2135: An error occurred while parsing
I tried all the methods. (1) uninstall and install again (2) disconnect and reconnect (3) Windows Image Acquisition (WIA) services are working properly (4) turn off the printer all in one (5) restart my computer (6) follow all the troubleshooting ste
-
Netflix icon disappeared.
For some reason, my Netflix icon on my desktop is gone (I perhaps accidentally deleted). I went on the site and file/send to / desktop shortcut. The icon appeared... but when I clicked it, error message: application not available. What is going on
-
I need help... I can't open my hotmail
the problem started 2 weeks ago... and I tried everything but I don't want to give up. I did to opcions may for my password and the hotmail send me whenever some newones so I tried everything... but now is not working and I don't know what to do I do
-
PST problem, stability, etc. (modern!)
My computer has been acting 'weird' - unstable. And I was working to "fix" - disk cleanup, getting rid of the additional software, etc. I also have an external hard drive. I've been in Outlook and all of a sudden my eyes got stuck and would not "take
-
This computer worked fine until two days ago, when an upgrade of the software McAfee killed my internet access and AT & T has removed (by chance, they say) my static IP. They have restored these and I have reassigned IPs and dumped McAfee. Now I can