RAC Redo Log Internal

Hi all
I want ask some questions about redo log generation in RAC.
1. Does Oracle confirms that each committed transaction, from begin_transaction to commit, redo and undo information resides in redo log of one node? Which means, would it possible that Oracle put begin transaction in redo log of node A, and put commit in redo log of another node B?

Reup this thread :)
Another questions:
What about RAC broadcast performs? I mean is it true that when node A commits a transaction T, then it broadcast this information to all other nodes, would Oracle write this information about T to node B's online redo log? for example, in redo log of Node B contains a redo record including opcode=5.4 and T's transaction id and Node A's thread number.
But during my analyze, Oracle 10.2.0.1.0 RAC, (NFS share), both dump file of redo log and binary redo log don't contains that redo record.
So I wonder what Oracle does?
Black Thought

Similar Messages

RAC redo logs (Confusion)

I was reading RAC documents that is written by Steve Karam.
Cache Fusion for RAC
RAC provides us a multiple instance, single database system. In a RAC environment, there is one shared set of datafiles. Each instance in the “cluster” will have its own SGA (RAM areas) and binary processes. They will also have their own control files and redo log files, though these must be viewable by all nodes, or systems, in the cluster.
http://www.dba-oracle.com/t_implementation_decision_rac_clusters.htm
I'm confused whether each instance has it's own redo log file or they are centrally stored. The above document says that each instance has it's own redo log files.
Rakesh Soni.

I'm confused whether each instance has it's own redo log file or they are centrally stored. The above document says that each instance has it's own redo log files.No it is not...
We do have log_archive_format parameter here we will be using _%t along with the format
t=Thread whih tells oracle which instance the log is coming from...
I am not RAC expert but it cannot be like that

Resizing redo log files on a 3 node RAC with single node standby database

Hi
On a 3 node 11g RAC system,I have to resize the redo logs on primary database from 50M to 100M. I was planning to do the following steps:
SQL> select group#,thread#,members,status from v$log;
GROUP# THREAD# MEMBERS STATUS
1 1 3 INACTIVE <-- whenefver INACTIVE, logfile group can be dropped
2 1 3 CURRENT & resized, switch logfile can change logfile group
3 1 3 INACTIVE
4 2 3 INACTIVE
5 2 3 INACTIVE
6 2 3 CURRENT
7 3 3 INACTIVE
8 3 3 INACTIVE
9 3 3 CURRENT
9 rows selected.
SQL> alter database drop logfile group 1;
Database altered.
SQL> ALTER DATABASE ADD LOGFILE THREAD 1
GROUP 1 (
'/PROD/redo1/redo01a.log',
'/PROD/redo2/redo01b.log',
'/PROD/redo3/redo01c.log'
) SIZE 100M reuse; 2 3 4 5 6
Database altered.
However I am not sure what needs to be done for the standby. The standby_file_management is set to auto and it is single instance standby.
SQL> select group#,member from v$logfile where type='STANDBY';
GROUP#
MEMBER
10
/PROD/flashback/PROD/onlinelog/o1_mf_10_7b44gy67_.log
11
/PROD/flashback/PROD/onlinelog/o1_mf_11_7b44h7gy_.log
12
/PROD/flashback/PROD/onlinelog/o1_mf_12_7b44hjcr_.log
Please let me know.
Thanks
Sumathy

Hello;
For Redo and Standby redo this won't help :
standby_file_management is set to auto
On the Standby cancel recovery, then drop and recreate the redo and or Standby redo.
Then start recovery again.
Example ( I have a habit of removing the old file at the OS to avoid REUSE and conflicts )
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
SQL> ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT='MANUAL';
alter database add standby logfile group 4
('/u01/app/oracle/oradata/orcl/standby_redo04.log') size 100m;
ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT='AUTO'
Notes worth reviewing :
Online Redo Logs on Physical Standby [ID 740675.1]
Error At Standby Database Ora-16086: Standby Database Does Not Contain Available Standby Log Files [ID 1155773.1]
Example of How To Resize the Online Redo Logfiles [ID 1035935.6]
Best Regards
mseberg

Brarchive not backing up offline redo log on RAC

Hi all Oracle and SAP experts,
After running brarchive on my newly setup RAC system, the program reports that there are 'No offline redo log files found for processing'. Hence, non of the archive log files are being backup.
Tons of archive log files are generated in the archive log directory. I do not understand why brarchive is unable to locate these files.
There are 2 Windows RAC nodes. I used the command 'brarchive -u / -c force -p initTST.sap -sd' to trigger brarchive. It is using rman to backup to a windows shared folder. And the brbackup runs successfully.
The output from brarchive is below:
BR0002I BRARCHIVE 7.00 (16)
BR0006I Start of offline redo log processing: aebbxosu.svd 2009-07-24 14.07.36
BR0477I Oracle pfile F:\oracle\TST\102\database\initTST1.ora created from spfile F:\oracle\TST\102\database\spfile.ora
BR0101I Parameters
Name                           Value
oracle_sid                     TST1
oracle_home                    F:\oracle\TST\102
oracle_profile                 F:\oracle\TST\102\database\initTST1.ora
sapdata_home                   F:\oracle\TST
sap_profile                    F:\oracle\TST\102\database\initTST.sap
backup_dev_type                disk
archive_copy_dir
10.11.0.101\backup\RAC_test
compress                       no
disk_copy_cmd                  rman
cpio_disk_flags                -pdcu
rman_compress                  no
archive_dupl_del               only
parallel_instances             TST2:F:\oracle\TST\102@TST2
system_info                    tstadm RACNODE1 Windows 5.2 Build 3790 Service Pack 2 AMD64
oracle_info                    TST 10.2.0.4.0 8192 1492 10504542 RACNODE1 UTF8 UTF8
sap_info                       620 SAPTST TST D1583565402 R3_ORA 0020087949
make_info                      NTAMD64 OCI_10201_SHARE Aug 22 2006
command_line                   brarchive -u / -c force -p initTST.sap -sd
BR0013W No offline redo log files found for processing
BR0007I End of offline redo log processing: aebbxosu.svd 2009-07-24 14.07.54
BR0280I BRARCHIVE time stamp: 2009-07-24 14.07.55
BR0004I BRARCHIVE completed successfully with warnings

I had set BR_TRACE to 15 and receive the following in my trace file:
BR0249I BR_TRACE: level 3, function BrCurrRedoGet exit with 0
BR0249I BR_TRACE: level 2, function BrInstCheck exit with -10
BR0248I BR_TRACE: level 2, function BrDiskStatGet entry with '
10.11.0.101\backup\RAC_test'
BR0250I BR_TRACE: level 2, function BrDiskStatGet exit with '19999863332864 9780518486016 9780518486016 9770967198432'
BR0248I BR_TRACE: level 2, function arch_last_get entry with 'F:\oracle\TST\saparch\archTST1.log'
BR0249I BR_TRACE: level 2, function arch_last_get exit with 0
BR0248I BR_TRACE: level 2, function BrArchNameGet entry with '0 TST1'
BR0250I BR_TRACE: level 2, function BrArchNameGet exit with 'G:\oracle\TST\oraarch\681026106_1_0.dbf'
BR0248I BR_TRACE: level 2, function BrNameBuild entry with '41 G:\oracle\TST\oraarch\681026106_1_0.dbf NULL'
BR0250I BR_TRACE: level 2, function BrNameBuild exit with 'G:\oracle\TST\oraarch'
BR0248I BR_TRACE: level 2, function BrFileStatGet entry with 'G:\oracle\TST\oraarch'
BR0250I BR_TRACE: level 2, function BrFileStatGet exit with '39171616256 0'
BR0248I BR_TRACE: level 2, function BrArchExist entry with 'TST1'
BR0248I BR_TRACE: level 3, function BrArchNameGet entry with '987656789 TST1'
BR0250I BR_TRACE: level 3, function BrArchNameGet exit with 'G:\oracle\TST\oraarch\1_1_987656789.dbf'
BR0249I BR_TRACE: level 2, function BrArchExist exit with -3
BR0248I BR_TRACE: level 2, function BrDiskStatGet entry with '
10.11.0.101\backup\RAC_test'
BR0248I BR_TRACE: level 2, function BrDbDisconnect entry with 'void'
BR0280I BRARCHIVE time stamp: 2009-07-27 09.41.42
BR0644I BR_TRACE: location BrDbDisconnect-1, SQL statement:
'COMMIT RELEASE'
BR0300I BR_TRACE: SQL code: 0, number of processed rows: 0
BR0248I BR_TRACE: level 3, function BrZombieKill entry with 'void'
BR0250I BR_TRACE: level 3, function BrZombieKill exit with 'void'
BR0249I BR_TRACE: level 2, function BrDbDisconnect exit with 0
BR0013W No offline redo log files found for processing
My current database incarnation is 681026106 but brarchive is searching for archivelog from incarnation 987656789 (1_1_987656789.dbf). As a workaround, I created dummy files (eg. 1_1_987656789.dbf') for each node and managed to trick brarchive into believing these are the real files. Subsequent backup works fine. Thanks Michael!

Question on Redo logs in RAC

DB version:11.2
Platform : Solaris 10
We create RAC DBs manually. Below is a log of the DB creation from Node1 . Instance in Node2 is not yet created (only binary is installed in Node2).
SQL> conn / as sysdba
Connected to an idle instance.
SQL> startup nomount pfile=/u03/oracle/11.2/db_1/dbs/initnehprd1.ora
ORACLE instance started.
Total System Global Area 1252643278 bytes
Fixed Size                  2219208 bytes
Variable Size             771752760 bytes
Database Buffers          469762048 bytes
Redo Buffers                8929280 bytes
SQL> CREATE DATABASE nehprd MAXINSTANCES 8 MAXLOGFILES 16 MAXLOGMEMBERS 4 MAXDATAFILES 1024
2 CHARACTER SET AL32UTF8 NATIONAL CHARACTER SET AL16UTF16
3 DATAFILE '+DG_DATA01/nehprd/nehprd_system01.dbf' SIZE 1000m EXTENT MANAGEMENT LOCAL
4 SYSAUX DATAFILE '+DG_DATA01/nehprd/nehprd_sysaux01.dbf' SIZE 600m
5 DEFAULT TEMPORARY TABLESPACE temp
6 TEMPFILE '+DG_DATA01/nehprd/nehprd_temp01.dbf' SIZE 2000m EXTENT MANAGEMENT LOCAL UNIFORM SIZE 5m
7 UNDO TABLESPACE undotbs11 DATAFILE '+DG_DATA01/nehprd/nehprd_undotbs1101.dbf' SIZE 700m
8 LOGFILE
9          GROUP 1 ('+DG_DATA01/nehprd/nehprd_log01.dbf') SIZE 150m,
10          GROUP 2 ('+DG_DATA01/nehprd/nehprd_log02.dbf') SIZE 150m,
11          GROUP 3 ('+DG_DATA01/nehprd/nehprd_log03.dbf') SIZE 150m
12 /
Database created.
Elapsed: 00:00:18.95
SQL> CREATE UNDO TABLESPACE undotbs12 DATAFILE '+DG_DATA01/nehprd/nehprd_undotbs1201.dbf' SIZE 700m;
Tablespace created.
Elapsed: 00:00:01.30
SQL> ALTER DATABASE ADD LOGFILE thread 2 GROUP 4 '+DG_DATA01/nehprd/nehprd_log04.dbf' SIZE 150m;
Database altered.
Elapsed: 00:00:00.25
SQL> ALTER DATABASE ADD LOGFILE thread 2 GROUP 5 '+DG_DATA01/nehprd/nehprd_log05.dbf' SIZE 150m;
Database altered.
Elapsed: 00:00:00.43
SQL> ALTER DATABASE ADD LOGFILE thread 2 GROUP 6 '+DG_DATA01/nehprd/nehprd_log06.dbf' SIZE 150m;
Database altered.But after the above activity, the following log files are created in the DB.
6 log groups for each Instance and they all are on the same location +DG_DATA01/nehprd !
INST_ID     GROUP# STATUS TYPE             MEMBER                                   IS_
         1          1         ONLINE +DG_DATA01/nehprd/nehprd_log01.dbf             NO
         1          2         ONLINE +DG_DATA01/nehprd/nehprd_log02.dbf             NO
         1          3         ONLINE +DG_DATA01/nehprd/nehprd_log03.dbf             NO
         1          4         ONLINE +DG_DATA01/nehprd/nehprd_log04.dbf             NO
         1          5         ONLINE +DG_DATA01/nehprd/nehprd_log05.dbf             NO
         1          6         ONLINE +DG_DATA01/nehprd/nehprd_log06.dbf             NO
         2          1         ONLINE +DG_DATA01/nehprd/nehprd_log01.dbf             NO
         2          2         ONLINE +DG_DATA01/nehprd/nehprd_log02.dbf             NO
         2          3         ONLINE +DG_DATA01/nehprd/nehprd_log03.dbf             NO
         2          4         ONLINE +DG_DATA01/nehprd/nehprd_log04.dbf             NO
         2          5         ONLINE +DG_DATA01/nehprd/nehprd_log05.dbf             NO
         2          6         ONLINE +DG_DATA01/nehprd/nehprd_log06.dbf             NO How was redo log group 4,5,6 created for thread 1 and how was redo log group 1,2,3 created for thread 2 ?

Hi,
To make things worse, when you query v$logfile , It will show 6 redo logfiles belonging to 6 redo groups for each instance.The fact that it shows all groups of redo does not mean it belongs to that instance. Try to query v$database or v$datafile, this means that database/datafiles belongs to only one instance, of course not.
Isn't this a bit of a bug ?Of course not. It's concept.
To understand it you need understand the difference between instance and database. An database (i.e files) can be opened by many instances.
An Oracle database server consists of a database and at least one database instance (commonly referred to as simply an instance). Because an instance and a database are so closely connected, the term Oracle database is sometimes used to refer to both instance and database. In the strictest sense the terms have the following meanings:
Database
A database is a set of files, located on disk, that store data. These files can exist independently of a database instance.
Database instance
An instance is a set of memory structures that manage database files. The instance consists of a shared memory area, called the system global area (SGA), and a set of background processes. An instance can exist independently of database files.
Database: (v$database)
CONTROLFILE (v$controlfile)
DATAFILE (v$datafile)
ONLINELOG (v$logfile,v$log)
ARCHIVELOG (v$archivelog)
SPFILE
These views above will show the same values in either instance, because if the file (database) is changed it is modified in all instances. That's means you not need use gv$ because the information are the same in all instances, also you not need get info connecting in each instance querying theses v$ because the inf are the same independent of the instance
Instances: (v$instance)
PARAMETERS (v$parameter)
MEMORY STRUCTURE (e.g v$session)
The view v$session will show information about sessions from that instance only. In RAC each instance have you own info about session so you will need query gv$session because it get information about session from others instances.
The fact that each instance assign its own REDO/UNDO not mean they are part of the instances, REDO/UNDO are part of Database. They can be write by assigned instance and read by all instance (just it)
It's not a bug when you query v$datafile, v$logfile, v$controlfile in all instances you will get same result, because it's the DATABASE. (An database (i.e files) can be opened by many instances).
Levi Pereira

Redo log groups/files on the local disk for RAC DB

Whether is it possible/supported to place redo log files/groups on the local disk for a RAC databases ?
Thank you,

Hi Mufalani,
are you sure about this one? I'd think that this only works as long as the nodes don't restart/crash. I can imagine this like this:
The nodes store redo logs on local disks which are NFS-exported to the other node. Everything should be fine. But when one node crashes/reboots, the other one has to perform crash recovery for the crashed instance but this won't work when the NFS mount (with redo logs) is unaccessible. So I would not want to do this.
Bjoern

Adding bigger size Redo log groups In RAC , ASM

Hi Folks,
Database version - 10.1.0.4.0
OS version - AIX 5.3
RAC node 2 and ASM
We had 4 redo log groups of lesser size on both nodes.yesterday I added 4 new groups of bigger size using pl/sql developer tool and deleted 2 old redolog groups. But I m not able to delete remaining 2 old groups.
ORA-01567 dropping log2 would have less than 2 log files for instance 1.
Our redolog files are on SAN and both node points to same storage. when I fired this query from command prompt
SELECT v$logfile.member, v$logfile.group#, v$log.status, v$log.bytes
FROM v$log, v$logfile
WHERE v$log.group# = v$logfile.group#;
I got same result for both nodes.
The problem I suspect is that All the 4 new log groups are added to instance 2 and its 2 old grouips are are also deleted.
Now my ques is that :
1. shouild I have added redo log groups separately on both nodes even storage is same for both nodes ?
2. redologs groups are defined separately for each node ?
How should I assign 2 new redo log groups to instance 1 ?
Regards,

Please check:
SQL> select instance_number, instance_name, thread# from gv$instance;
Show Instance with thread ID
SQL> select group#, thread#, members ,status from v$log;
Check number groups in each of thread.
On RAC, you have to add redo log Group each of node (each of thread )
SQL> select group#, thread#, members ,status from v$log;
From your environment ,I think you have 2 nodes = 2 thread
If these're thread 1, 2
So, add redo group should:
Example:
ALTER DATABASE ADD LOGFILE THREAD 1 GROUP 11 ( '+DATA') SIZE 500M;
ALTER DATABASE ADD LOGFILE THREAD 1 GROUP 12 ( '+DATA') SIZE 500M;
ALTER DATABASE ADD LOGFILE THREAD 2 GROUP 13 ( '+DATA') SIZE 500M;
ALTER DATABASE ADD LOGFILE THREAD 2 GROUP 14 ( '+DATA') SIZE 500M;
You should check each thread has >= 2 groups and that group had "INACTIVE" status before drop:
SQL> select group#, thread#, members ,status from v$log;
My Idea, you should have 3 redo log groups for each node(thread)
Good Luck

Redo log corruption

In a 2 node RAC Node1 crashes due to the online redo-log file corruption.
During this scenario...,Node2 should perform instance recovery; but since redo-log is corrupted, it cannot do the instance recovery.
what will happen at this point ? Will the other node2 continue working ?

please note that I hav'nt tested this to validate this ..
this is a theoritical answer based on what I believe how it might work ..
a) Node:2 attempts to perform an Instance Recovery by reading the Shared
Redo Log threads of Node:1
b) It runs into the same corrupt Redolog block messages and reports an
Internal error { ora-00600 / ora-07445 }
c) Depending on whether it was a fatal or non-fatal error , Node:2 might crash or
continue to work .. if it is the latter , everytime any access is needed to blocks
which still have those uncommitted transactions from Node:1 , you would
see an error / trace generated ..
Vishwa

Problem in creating database -Missing Redo log file

I am try to create a new database using DBCA .While creating a database it shows the error oracle instance terminated.Force Disconnected.
My alert log file is
Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/oracl/redo01.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Wed Nov 06 10:07:27 2013
Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/oracl/redo02.log'
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/oracl/oracl/trace/oracl_ora_5424.trc:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/oracl/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Wed Nov 06 10:07:38 2013
Setting recovery target incarnation to 2
Wed Nov 06 10:07:38 2013
Assigning activation ID 1876274518 (0x6fd5ad56)
Thread 1 opened at log sequence 1
Current log# 1 seq# 1 mem# 0: /u01/app/oracle/oradata/oracl/redo01.log
Successful open of redo thread 1
Wed Nov 06 10:07:38 2013
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Wed Nov 06 10:07:38 2013
SMON: enabling cache recovery
Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc (incident=1345):
ORA-00600: internal error code, arguments: [kpotcgah-7], [12534], [ORA-12534: TNS:operation not supported
Incident details in: /u01/app/oracle/diag/rdbms/oracl/oracl/incident/incdir_1345/oracl_ora_5424_i1345.trc
Wed Nov 06 10:07:46 2013
Trace dumping is performing id=[cdmp_20131106100746]
Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc:
ORA-00600: internal error code, arguments: [kpotcgah-7], [12534], [ORA-12534: TNS:operation not supported
Error 600 happened during db open, shutting down database
USER (ospid: 5424): terminating the instance due to error 600
Instance terminated by USER, pid = 5424
ORA-1092 signalled during: alter database "oracl" open resetlogs...
ORA-1092 : opiodr aborting process unknown ospid (5424_47935551851664)
Wed Nov 06 10:07:47 2013
ORA-1092 : opitsk aborting process
251,1 95%

>I am try to create a new database using DBCA
>Please help me to resolve this issue.My redo log file was missing
DROP and recreate the database. It is a *new* database without any data.
Check what datafile locations and redo log file locations you specify when creating the new database. Check if you have permissions and enough disk space.
Hemant K Chitale

Best way to move redo log from one disk group to another in ASM?

Hi All,
Our db is 10.2.0.3 RAC db. And database servers are window 2003 server.
We need to move more than 50 redo logs (some are regular and some are standby) which are not redundant from one disk group to another. Say we need to move from disk group 1 to 2. Here are the options we are thinking about but not sure which one is the best from easiness and safety prospective.
Thank you very much for your help in advance.
Shirley
Option 1:
1)     shutdown immediate
2)     copy log files from disk group 1 to disk group2 using RMAN (need to research on this)
3)     startup mount
4)     alter database rename file ….
5)     Open database open
6)     delete the redo files from disk group 1 in ASM (how?)
Option 2:
1)     create a set of redo log groups in disk group 2
2)     drop the redo log groups in disk group 1 when they are inactive and have been archived
3)     delete the redo files associated with those dropped groups from disk group 1 (how?) (According to Oracle menu: when you drop the redo log group the operating system files are not deleted and you need to manually delete those files)
Option 3:
1)     create a set of redo members in disk group 2 for each redo log group in disk group 1
2)     drop the redo log memebers in disk group 1
3)     delete the redo files from disk group 1 associated with the dropped members

Absolutely not, they are not even remotely similar concepts.
OMF: Oracle Managed Files. It is an RDMBS feature, no matter what your storage technology is, Oracle will take care of file naming and location, you only have to define the size of a file, and in the case of a tablespace on an OMF DB Configuration you only need to issue a command similar to this:
CREATE TABLESPACE <TSName>; So the OMF environment creates an autoextensible datafile at the predefined location with 100M by default as its initial size.
On ASM it should only be required to specify '+DGroupName' as the datafile or redo log file argument so it can be fully managed by ASM.
EMC. http://www.emc.com No further commens on it.
~ Madrid
http://hrivera99.blogspot.com

How to increase the size of Redo log files?

Hi All,
I have 10g R2 RAC on RHEL. As of now, i have 3 redo log files of 50MB size. i have used redo log size advisor by setting fast_start_mttr_target=1800 to check the optimal size of the redologs, it is showing 400MB. Now, i want to increase the size of redo log files. how to increase it?
If we are supposed to do it on production, how to do?
I found the following in one of the article....
"The size of the redo log files can influence performance, because the behavior of the database writer and archiver processes depend on the redo log sizes. Generally, larger redo log files provide better performance, however it must balanced out with the expected recovery time.Undersized log files increase checkpoint activity and increase CPU usage."
I did not understand the the point however it must balanced out with the expected recovery time in the above given paragraph.
Can anybody help me?
Thanks,
Praveen.

You dont have to shutdown the database before dropping redo log group but make sure you have atleast two other redo log groups. Also note that you cannot drop active redo log group.
Here is nice link,
http://www.idevelopment.info/data/Oracle/DBA_tips/Database_Administration/DBA_34.shtml
And make sure you test this in test database first. Production should be touched only after you are really comfortable with this procedure.

Online redo log files being removed physically

Grid Infra version: 11.2.0.4
RDBMS Version: 11.2.0.4
Although this is a RAC DB, this is not a RAC-specific question. Hence posting it here.
Few months back, I remember issuing a command similair to below (DROP LOGFILE GROUP ...) and the redo log files were still physically present in the diskgroup.
If I remember correctly, the file is not deleted physical so that we can use the REUSE functionality (ALTER DATABASE ADD LOGFILE MEMBER '+REDO/orcl/onlinelog/redo1b.log' reuse to group 11; ) ie. you can use the REUSE command to add the logfile of the same name which is physically present in OS Filesystem/Diksgroup to redo log group.
But today, after I issued the below command, I checked the diskgroup location from ASMCMD
SQL> alter database drop logfile group 31;
Database altered.
From ASMCMD, I can that the file has disappeared physically. Is this a new feature with 11.2.0.4 or am I missing something here ?
ASMCMD> ls +DATA/msblprd/onlinelog/group_31.548.833154995
ASMCMD-8002: entry 'group_31.548.833154995' does not exist in directory '+DATA/msblprd/onlinelog/'

Just to add to what Aman has said.
It is a bad practice not to let OMF decide the placement of Online redo logs because of this issue especially when you use ASM.
Executing rm command in Linux/Unix is easy but Dropping ASM aliases in the disk group can be a hassle.
This is documented.
"When a redo log member is dropped from the database, the operating system file is not deleted from disk. Rather, the control files of the associated database are updated to drop the member from the database structure. After dropping a redo log file, ensure that the drop completed successfully, and then use the appropriate operating system command to delete the dropped redo log file."
http://docs.oracle.com/cd/E11882_01/server.112/e25494/onlineredo.htm#ADMIN11324
BTW . You don't even need to set db_create_online_log_dest_n to enable OMF for ORLs.
SQL> show parameter log_dest
NAME                                 TYPE        VALUE
db_create_online_log_dest_1          string
db_create_online_log_dest_2          string
db_create_online_log_dest_3          string
db_create_online_log_dest_4          string
db_create_online_log_dest_5          string
SQL> show parameter db_create_file_dest
NAME                                 TYPE        VALUE
db_create_file_dest                  string      +MBL_DATA
alter database add logfile thread 4
group 31 ('+MBL_DATA','+MBL_FRA') size 4096M,
group 32 ('+MBL_DATA','+MBL_FRA') size 4096M,
group 33 ('+MBL_DATA','+MBL_FRA') size 4096M,
group 34 ('+MBL_DATA','+MBL_FRA') size 4096M ;
Database altered.
And redo logs will be neatly placed as shown below
   INST     GROUP# MEMBER                                             STATUS           ARC
         4         31 +MBL_DATA/bsblprd/onlinelog/group_31.276.832605441 UNUSED           YES
                      +MBL_FRA/bsblprd/onlinelog/group_31.297.832605445 UNUSED           YES
                   32 +MBL_DATA/bsblprd/onlinelog/group_32.547.832605451 UNUSED           YES
                      +MBL_FRA/bsblprd/onlinelog/group_32.372.832605457 UNUSED           YES
                   33 +MBL_DATA/bsblprd/onlinelog/group_33.548.832605463 UNUSED           YES
                      +MBL_FRA/bsblprd/onlinelog/group_33.284.832605469 UNUSED           YES
                   34 +MBL_DATA/bsblprd/onlinelog/group_34.549.832605475 UNUSED           YES
                      +MBL_FRA/bsblprd/onlinelog/group_34.359.832605481 UNUSED           YES

Question on redo log files at the standby

Oracle version: 10.2.0.5
Platform : AIX
We have 2 node RAC primary with 2 node RAC standby
Primary Instance1 named as cmapcp1
Primary Instance2 named as cmapcp2
Standby Instance1 named as cmapcp3
Standby Instance2 named as cmapcp4At standby side
SQL> show parameter log_file_name_convert
NAME                 TYPE                 VALUE
log_file_name_conver string               cmapcp1, cmapcp3, cmapcp2, cmapcp4
Despite the value set for log_file_name_convert, I don't see any change in names of Online and Standby redo logs at the Standby site.
-- From primary
SQL> select member,type from v$logfile;
MEMBER                                             TYPE
+CMAPCP_DATA01/cmapcp/cmapcp_log01.dbf             ONLINE
+CMAPCP_DATA01/cmapcp/cmapcp_log02.dbf             ONLINE
+CMAPCP_DATA01/cmapcp/cmapcp_log03.dbf             ONLINE
+CMAPCP_DATA01/cmapcp/cmapcp_log04.dbf             ONLINE
+CMAPCP_DATA01/cmapcp/cmapcp_log05.dbf             ONLINE
+CMAPCP_DATA01/cmapcp/cmapcp_log06.dbf             ONLINE
+CMAPCP_DATA01/cmapcp/cmapcp_log11.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log12.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log13.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log14.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log15.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log16.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log17.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log18.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log19.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log20.dbf             STANDBY
16 rows selected.-- From standby
SQL> select member,type from v$logfile;
MEMBER                                             TYPE
+CMAPCP_DATA01/cmapcp/cmapcp_log01.dbf             ONLINE
+CMAPCP_DATA01/cmapcp/cmapcp_log02.dbf             ONLINE
+CMAPCP_DATA01/cmapcp/cmapcp_log03.dbf             ONLINE
+CMAPCP_DATA01/cmapcp/cmapcp_log04.dbf             ONLINE
+CMAPCP_DATA01/cmapcp/cmapcp_log05.dbf             ONLINE
+CMAPCP_DATA01/cmapcp/cmapcp_log06.dbf             ONLINE
+CMAPCP_DATA01/cmapcp/cmapcp_log11.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log12.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log13.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log14.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log15.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log16.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log17.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log18.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log19.dbf             STANDBY
+CMAPCP_DATA01/cmapcp/cmapcp_log20.dbf             STANDBY
16 rows selected.--- Another thing I noticed, v$log doesn't list Standby Redo Logs. This is expected behaviour , I guess
Below is the output from Primary and Standby (it is the same)
set linesize 200
set pagesize 50
col member for a50
break on INST SKIP PAGE on GROUP# SKIP 1
select l.thread# inst, l.group#,lf.member, lf.type
    from v$log l , v$logfile lf
    where l.group# = lf.group#
    order by 1,2 ;
      INST     GROUP# MEMBER                                             TYPE
         1          1 +CMAPCP_DATA01/cmapcp/cmapcp_log01.dbf             ONLINE
                    2 +CMAPCP_DATA01/cmapcp/cmapcp_log02.dbf             ONLINE
                    3 +CMAPCP_DATA01/cmapcp/cmapcp_log03.dbf             ONLINE
      INST     GROUP# MEMBER                                             TYPE
         2          4 +CMAPCP_DATA01/cmapcp/cmapcp_log04.dbf             ONLINE
                    5 +CMAPCP_DATA01/cmapcp/cmapcp_log05.dbf             ONLINE
                    6 +CMAPCP_DATA01/cmapcp/cmapcp_log06.dbf             ONLINE

John_75 wrote:
Thank you ckpt, mseberg.
I think log_file_name_convert is set wrongly as you've mentioned. But If I don't want to any change to name of Online or standby redo log files in standby, I don't have to set log_file_name_convert at all. Right ?From Same link
If you specify an odd number of strings (the last string has no corresponding replacement string), an error is signalled during startup. If the filename being converted matches more than one pattern in the pattern/replace string list, the first matched pattern takes effect. There is no limit on the number of pairs that you can specify in this parameter (other than the hard limit of the maximum length of multivalue parameters).

Require 9i Primary and Standby redo logs files same size?

Hi,
We have 9.2.0.6 Oracle RAC (2 node) and configured data guard (physical standby).
I want to increase redo log files size, but i can't this do same time primary and standby side.
Is there a rule, primary and standby database instances have same size redo log files?
If I increase only primary redo log files, is there any side effect? However I try this issue on test system. I increased all primary redo log files(if status='INACTIVE' drop redo log group and add redo log group, switch logfile,...)
, but i couldn't changed standby side. So the system is work well. Is this correct solution or not? How can i increase both sides redo log files?
Thank you for helps..

Thank you for your helps.. I found this issue answer:
http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14239/manage_ps.htm#i1010448
Consequently, when you add or drop an online redo log file at the primary site, it is important that you synchronize the changes in the standby database by following these steps:
If Redo Apply is running, you must cancel Redo Apply before you can change the log files.
If the STANDBY_FILE_MANAGEMENT initialization parameter is set to AUTO, change the value to MANUAL.
Add or drop an online redo log file:
To add an online redo log file, use a SQL statement such as this:
SQL> ALTER DATABASE ADD LOGFILE '/disk1/oracle/oradata/payroll/prmy3.log' SIZE 100M;
To drop an online redo log file, use a SQL statement such as this:
SQL> ALTER DATABASE DROP LOGFILE '/disk1/oracle/oradata/payroll/prmy3.log';
Repeat the statement you used in Step 3 on each standby database.
Restore the STANDBY_FILE_MANAGEMENT initialization parameter and the Redo Apply options to their original states.
bye..

Standby Redo log creation

DB version: 11.2
OS : AIX 6.1
We have a 2 node RAC. We have one Disk group for all datafiles, tempfiles, redo logs,..etc.
Currenly in our primary DB, Redo logs look like
SQL> SELECT a.group#, b.thread#, a.member, b.bytes
FROM v$logfile a, v$log b WHERE a.group# = b.group#
order by a.group# , b.thread# 2    3 ;
         GROUP#         THREAD# MEMBER                                BYTES
              1               1 +ORCL_DG/orcl/orcl_log01.dbf         104857600
              2               1 +ORCL_DG/orcl/orcl_log02.dbf         104857600
              3               1 +ORCL_DG/orcl/orcl_log03.dbf         104857600
              4               2 +ORCL_DG/orcl/orcl_log04.dbf         104857600
              5               2 +ORCL_DG/orcl/orcl_log05.dbf         104857600
              6               2 +ORCL_DG/orcl/orcl_log06.dbf         104857600
6 rows selected.
1 member per group
3 group per instanceWe need to create a physical standby DB for the above DB with Real Time apply. For standby Redo logs, I need one extra log file for each Instance.
So, I am going to add
     group# 7 for thread 1
     and
     group# 8 for thread 2
Finally , SRLs will look like
         GROUP#         THREAD# MEMBER                                BYTES
              1               1 +ORCL_DG/orcl/orcl_log01.dbf         104857600
              2               1 +ORCL_DG/orcl/orcl_log02.dbf         104857600
              3               1 +ORCL_DG/orcl/orcl_log03.dbf         104857600
           7               1 +ORCL_DG/orcl/orcl_log07.dbf         104857600 -------> Additional
              4               2 +ORCL_DG/orcl/orcl_log04.dbf         104857600
              5               2 +ORCL_DG/orcl/orcl_log05.dbf         104857600
              6               2 +ORCL_DG/orcl/orcl_log06.dbf         104857600
           8               2 +ORCL_DG/orcl/orcl_log08.dbf         104857600 -------> AdditionalAnything wrong with my proposed SRL creation ?

JOE_humble wrote:
DB version: 11.2
OS : AIX 6.1
We have a 2 node RAC. We have one Disk group for all datafiles, tempfiles, redo logs,..etc.
Currenly in our primary DB, Redo logs look like
SQL> SELECT a.group#, b.thread#, a.member, b.bytes
FROM v$logfile a, v$log b WHERE a.group# = b.group#
order by a.group# , b.thread# 2    3 ;
GROUP#         THREAD# MEMBER                                BYTES
1               1 +ORCL_DG/orcl/orcl_log01.dbf         104857600
2               1 +ORCL_DG/orcl/orcl_log02.dbf         104857600
3               1 +ORCL_DG/orcl/orcl_log03.dbf         104857600
4               2 +ORCL_DG/orcl/orcl_log04.dbf         104857600
5               2 +ORCL_DG/orcl/orcl_log05.dbf         104857600
6               2 +ORCL_DG/orcl/orcl_log06.dbf         104857600
6 rows selected.
1 member per group
3 group per instanceWe need to create a physical standby DB for the above DB with Real Time apply. For standby Redo logs, I need one extra log file for each Instance.
So, I am going to add
     group# 7 for thread 1
     and
     group# 8 for thread 2
Finally , SRLs will look like
GROUP#         THREAD# MEMBER                                BYTES
1               1 +ORCL_DG/orcl/orcl_log01.dbf         104857600
2               1 +ORCL_DG/orcl/orcl_log02.dbf         104857600
3               1 +ORCL_DG/orcl/orcl_log03.dbf         104857600
           7               1 +ORCL_DG/orcl/orcl_log07.dbf         104857600 -------> Additional
4               2 +ORCL_DG/orcl/orcl_log04.dbf         104857600
5               2 +ORCL_DG/orcl/orcl_log05.dbf         104857600
6               2 +ORCL_DG/orcl/orcl_log06.dbf         104857600
           8               2 +ORCL_DG/orcl/orcl_log08.dbf         104857600 -------> AdditionalAnything wrong with my proposed SRL creation ?You have to create equal numbers & equal or greater size of standby redo log files than Online redo log files.
Refer http://www.pythian.com/news/581/oracle-standby-redo-logs/ to configure standby redo log files.

RAC Redo Log Internal

Similar Messages

Maybe you are looking for