Redo Logs after duplication 3 RAC node to node 2 RAC

Similar Questions

• 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

• Path of redo logs after restoring controlfile

  Hello!
  
  After restoration of the controlfile I see distorted redo logs metadata (column v$ logfile.member):

  $OH/dbs/data/ora/MY_SID/rlog/redo1a.log

  in the redo logs placed in another directory, source database
  also I should drop logfile member and log file groups, and then create them again, but may be there other way to solve this problem?
  Please notify.
  I'm usung 11.2.0.3
  
  Thank you and best regards,
  Pavel

  As I said earlier, is that your database is working well? If so, then forget those files which are present in $OH/dbs/data/ora/file/rConnectez/MY_SID. Ok?

  Suppose now, the question is what are these files? Who created/copied?
  So the answer is if these files are used by your this database (MY_SID); that can be confirmed by query:
  Select Member from v$ logfile; then the redo logs are used by this database else chances are these files were the first part of this database, but not now due to may be a corruption that happened, so another / previous DBA has left.

  And if the database is not running, then what is the error you found it please post it here; otherwise leave these files such what.

  Concerning
  Girish Sharma

• Increased repository DB redo logging after upgrade EM12cR2?

  Has anyone else noticed increased redo logging in their repository database after upgrade to EM12cR2?
  
  I'm running on Linux x 86-64 with a 11.2.0.3 repository database. Before the upgrade, I was running 12.1.0.1.0 with BP1, and my repository database produced, on average, about 80-120 MB of archived redo logs / hour. Since the upgrade to 12.1.0.2.0, my product repository database, on average, 450-500 MB of newspapers archived redo / hour.
  
  Reclassification of deployed agents of 12.1.0.1.0 to 12.1.0.2.0 has not seemed to help; I've updated about 10 of the 15 without any apparent loss of logging of redo.
  
  I was wondering if it's comparable to what others see, or if I have a local question I should study.

  The following fix has been released for this problem:

  Patch 14726136 - INCREASED REDO LOGGING ON REPOSITORY DB AFTER UPGRADING TO OEM 12.1.0.2

  Kind regards
  Vincent

• Create the REDO Logs after restoration of RMAN

  Version 11.2
  Platform: Solaris 10
  
  We restore the cold RMAN backup to a new server. It's a basic restore RMAN where DB name remains the same.
  
  I understand that RMAN backup online redo logs, and for good reason.
  
  We have restored our datafiles successfully. The control file still has the old entries so the query below shows old information about recovery logs
  
  -Display of the configuration of the log file the old control file data

  SYS > select * from v$logfile;         ------------> The below output shows the result of the source server
  
      GROUP# STATUS  TYPE    MEMBER                              IS_
  ---------- ------- ------- ----------------------------------- ---
           1         ONLINE  /DATAM/DB/oradata/slmps/redo1.log      NO
           2         ONLINE  /DATAM/DB/oradata/slmps/redo2.log      NO
           3         ONLINE  /DATAM/DB/oradata/slmps/redo3.log      NO

  I have to use ALTER DATABASE RENAME FILE command as below to update the control file.

  alter database rename file '/DATAM/DB/oradata/slmps/redo1.log' to '/data/oradata/slmps/slmps_log01.dbf' ;
  alter database rename file '/DATAM/DB/oradata/slmps/redo2.log' to '/data/oradata/slmps/slmps_log02.dbf' ;
  alter database rename file '/DATAM/DB/oradata/slmps/redo3.log' to '/data/oradata/slmps/slmps_log03.dbf' ;  

  Currently, in the new server, at the level of the BONE there is no physical file above to
  

  /data/oradata/slmps

  I need to create physically redo new logs using the command or the command ALTER DATABASE RENAME above key create a physical file at the level of the BONE?

  Salvation in spiral,

  Surely, RMAN will search for redo logs when RECOVER is issued.

  When you issue the command RECOVER after restore, RMAN does not check online redo logs. During RECOVERY, RMAN will try to apply the archivelogs or incremental L1 if it has been saved on the source server. RMAN Backup restorations online redo logs or never.

  Here OP tries to restore the backup from the cold to a new server. In this case the RECOVER command is not necessary. The example of the Oracle doc you mentioned should do a restore, recovery of a backup hot. In this case, during the RESTORATION, RMAN will try to apply archivelogs or L1 of the incremental backups.

  In both cases (cold backup restore or restore, recover from Hot Backup), it is the

  alter database open resetlogs
  

  command that will create the online redo log, so it is absent in the location specified by the control file. Because it is a restoration to a new server, recovery logs is missing because it has not been restored (because it has not been saved)

• Question on create Redo log after restoring files and recover

  Log files to rebuild RMAN backup? Below the blog describes the steps to restore and recover a RMAN backup in a new host.
  http://blog.CSDN.NET/sweethouse1128/article/details/6948273
  
  
  RMAN seems to have backed up and restored the redo log files
  
  
  After the resumption, blogger issues

  select * from v$logfile;

  and the result obtained some log files. The rows returned are restored files redo log. right? Redo of RMAN backup and restore log files?

  Redo of RMAN backup and restore log files?

  N ° never. Even when you do a 'coherent' backup (i.e. with the database MOUNT but the mode is not OPEN).

  When you restore a full RMAN on a new server backup, RMAN restore REDO LOG files in the respective directories

  Does not apply because RMAN does not save logs in restoration online.

  Isn't better to manually create redo log files after restoration

  When you perform incomplete recovery, you must issue an ALTER DATABASE OPEN RESETLOGS.
  The RESETLOGS creates log files remake it, if they are not present OR reset them if they are present.
  In a scenario of complete restoration, the online redo log files are already present on the drive (i.e. they are not lost or destroyed and they are not restored a backup).

  Hemant K Collette

• 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

• Redo Log in Oracle RAC 11G

  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

• Questions about the parameters of database using a fast recovery area and the writing of two copies of archived redo logs.

  My databases are 11.2.0.3.7 Enterprise Edition. My OS is AIX 7.1.

  I am to convert databases to use individual zones of rapid recovery and have two questions about what values to assign to database settings related to archived redo logs. This example refers to a database.

  I read that if I specify

  Log_archive_dest_1 =' LOCATION = USE_DB_RECOVERY_FILE_DEST'

  the names of newspapers archived redo written in the default quick recovery area is '% t_%S_%r.dbf '.

  In the past my archived redo logs have been appointed based on the parameter

  log_archive_format='GPAIDT_archive_log_%t_%s_%r.arc'

  I think log_archive_format will be ignored for logs archived redo written in the fast recovery area.

  I am planning to write a second copy of the archived redo logs based on the parameter

  ALTER system set log_archive_dest_2 = ' LOCATION = / t07/admin/GPAIDT/arch.

  If I do this, the copy of logs placed in /t07 will be called '% t_%S_%r.dbf' or 'GPAIDT_archive_log_%t_%s_%r.arc '?

  Before my use of a fast recovery area, I used the OEM 12 c Console to specify settings of backup of database that has been deleted and archived redo logs after 1 backup. Oracle manuals say rather specify a deletion of "none" policy and allow Oracle delete newspapers in the area of fast recovery if necessary. Since I got to keep a second copy of these log files in /t07 should I keep the policy that says to delete logs after 1 backup? If I don't do that, how will they removed from /t07?

  Thank you

  Bill

  If I do this, the copy of logs placed in /t07 will be called '% t_%S_%r.dbf' or 'GPAIDT_archive_log_%t_%s_%r.arc '?

  They will be "GPAIDT_archive_log_%t_%s_%r.arc". LOG_ARCHIVE_FORMAT is only ignored for directories under OMF.

  Since I got to keep a second copy of these log files in /t07 should I keep the policy that says to delete logs after 1 backup? If I don't do that, how will they removed from /t07?

  You can hold the deletion policy as it is. Oracle documentation, defining the STRATEGY of the ARCHIVELOG DELETION: "the deletion of archived newspaper policy applies to logs archive destinations, including the area of fast recovery."

• Redo Log apply after reboot pending

  Hi all
  
  To start learning about Data Guard, I followed successfully the manual steps to create a database of physical intelligence. What I have noticed is when I restart the database pending, received redo log are not automatically applied until I issued the following command:

  ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;

  Is this normal? If so, is there a way to redo the remains of automatic application after restarting the database pending?
  
  Thanks in advance.

  When you configure the DataGuard in a SQL environment, you must manually start it again the process after the installation of the database of the previous day. You can start the script database and understand that when ' select database_role from v$ database "is physical Standby then 'ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT";

  OR

  Yo can configure the DataGuard under the broker control that will start at the redo apply process automatically at the start of the backup server.

  Sudhir.

• Redo log shipping after a stop pending physical

  Hallo,

  I just have a question for redo log shipping

  in a configuration simple primary/secondary 11g.

  In a shutted down an instance physical standby, redoshipping is active? Primary redo file transfer is still ongoing?

  Thanks in advance

  Hello;

  I'm not going to say no. I still SEE on the primary side before I shutdown, maintains false alarms from happening.

  Test

  Using this query

  http://www.mseberg.NET/data_guard/monitor_data_guard_transport.html

  DB_NAME HOSTNAME LOG_ARCHIVED LOG_APPLIED APPLIED_TIME LOG_GAP

  ---------- -------------- ------------ ----------- -------------- -------

  TDBGIS01B PRIMARY 5558 5557 21-OCT/12:51 1

  Stop waiting

  SQL > alter database recover managed standby database cancel;

  Database altered.

  SQL > shutdown

  ORA-01109: database is not open

  The database is dismounted.

  Journal of strength comes on primary side

  SQL > alter system switch logfile;

  Modified system.

  (3)

  Journal of before was 5558 check so make sure 5559 or higher

  Last log is

  o1_mf_1_5558_c2hn5vdf_.arc

  Wait a few minutes, no change

  Best regards

  mseberg

• Check the configuration of Redo Log Archives to

  DB version: 10 gr 2, 11 2 GR
  Version of the operating system: Solaris 5.10, AIX 6.1
  
  While allowing for a DB from Production 2 node RAC, I made a mistake specifying LOG_ARCHIVE_DEST (a typing error).
  
  After I brought the DB to the top (open) after you have enabled archiving, I tested the journal using switching

  SQL> alter system switch logfile;
  
  System altered

  and had no error.
  
  Later, I realized, archiving does not work. But I wonder, why I have no error for

  SQL> alter system switch logfile;

  Errors may have been recorded in the log of alerts. Since then I have no error from sqlplus to the command above, I thought everything was fine.
  
  But the following command triggered error.
  

  SQL> ALTER SYSTEM ARCHIVE LOG CURRENT;
  ALTER SYSTEM ARCHIVE LOG CURRENT
  *
  ERROR at line 1:
  ORA-16038: log 4 sequence# 127 cannot be archived
  ORA-00254: error in archive control string ''
  ORA-00312: online log 4 thread 2: '+LTMPROD_DATA/LTMPROD/redo04.log'
  ORA-15173: entry 'ltmprod_arch' does not exist in directory '/'

  Should what command I use to ensure that activation of Archive was successful?

  Hello

  Any more ways on how professional to check whether the archive allowing a success?

  ALWAYS... After putting data in ARCHIVE MODE, you must force the newspaper archive database.

  SQL > ARCHIVE LOG LIST; # To check status
  
  SQL > ALTER SYSTEM ARCHIVE LOG CURRENT; # This command must be executed sucessfull.
  
  Query V$ARCHIVE_LOG or use RMAN to check path/location of ARCHIVELOG. 
  
  $ rman target /
  RMAN > LIST ARCHIVELOG ALL; 
  

  Use ARCHIVE LOG SWITCH LOGFILE command to force again them to archive the disk, because they have a slight difference.

  JOURNAL of ARCHIVING is synchronous, this command waits until the online redo log has completed writing the log file again the file system, if again is not archived error is thrown on command prompt.

  SWITCH LOGFILE is asynchronous, this command start only switch / archive run in the background if ARCH process cannot finish writing the archivelog directory on file the error not returned not invite since he was released.

  You can use this technical note:
  * How to enable archiving ON and OFF [ID 69739.1] *.

  Hope this helps,
  Levi Pereira

  Published by: Levi Pereira on September 23, 2011 01:28

• Bandwidth of the network for the redo log switches

  Hi all

  I'm using Oracle 11 g R2, I want to clarify the necessary bandwidth of my primary site to the secondary site (using Oracle Data guard)

  My database is an Oracle RAC 2 nodes each node has a log size to 2 GB again. listen to this file in operation every 5 minutes. It means that I'm spending a 2 GB redo log file every 5 minutes from each node. This means that 4 GB in total every 5 minutes.

  I'm planing to set up Oracle Dataguard in maximum performance mode. Is that mean I need a link between the primary and secondary site that is able to transfer files of 2 GB + 2 GB every 5 minutes?

  I do the calculation below and need your advice:

  4 GB / (5x60s) = 13981 KByte/s

  This means that I need to link to 13981x8bites/s = 111, 848Kbit/s?

  Is the above correct? your advice please

  Kind regards

  Please check below two

  http://www.Oracle.com/au/products/database/MAA-WP-10gR2-dataguardnetworkbestpr-134557.PDF

  How to calculate bandwidth transfer network required recovery in care of data (Doc ID 736755.1)

• Many redo logs switches the line seconds on an irregular basis

  Hello

  We are 11 GR 2 RAC. We migrated a DB 10 g that used to pass on every 20-25 minutes all the

  While doing about 160 to 200 GB per day; I noticed this newly migrated DB now show

  pics of quick saves switches from time to time, for example yesterday (excerpt):

  SQL > select thread #, FIRST_TIME from v$ log_history by 2;

  ...

  1 20140524 10:19.36
  1 20140524 11:24.34
  2 20140524 11:24.35
  2 20140524 12:00.02
  1 20140524 12:00.03
  1 20140524 12:00.05
  2 20140524 12:00.08
  1 20140524 12:00.14
  1 20140524 13:06.19
  2 20140524 13:09.44
  2 20140524 14:15.46
  1 20140524 15:00.08
  2 20140524 15:00.50
  2 20140524 15:53.56
  2 20140524 16:45.37
  1 20140524 16:45.39
  2 20140524 17:43.26

  Ignore lines because of lunch at this time that I start a backup of archive logs, but to explain

  switches 11:24.34 et.35 for example, or 15:00.08 et.50, then at 16:45, where

  Do you think I should study? I have no reason why in these moments my DB suddenly

  give 3 GB of Oder, before you wait another hour to do this (e.g. between 16:45 and 17:43)...

  Everything about the fact that we are on CARS now?

  Thank you very much.

  Kind regards

  SEB

  Nothing to worry about.

  Each node in a RAC has it of own redo logs and performs his own logswitches.

  If you look for each thread (1 and 2 that correspond to the node) itself, everything is ok.

• Clusterware and/or CARS on separate storage, synchronized by applying the redo logs?

  Hello Experts,

  I am doing research on architectures high availability to meet high service LEVEL requirements (> = uptime of 99.7 percent and "without loss of important data") for a client.

  I have few resources for the implementation of this architecture: two physical database servers running 11g Standard Edition (so Data Guard is not an option), Enterprise Edition is not an option because of the price. Data storage will be on a San.

  The ideal solution would be an architecture whose node redundancy (Clusterware / RAC) and redundancy of the data (as in physical Standby: application of redo logs instead of data mirroring (corrupt physical) files).

  I did research Clusterware and CARS, but they use a shared storage. I'll use a SAN for storage, but this will not prevent physical mirroring of the corrupt data files.

  Is it possible to set up a PAP/Clusterware architecture with each separate storage node, where the two databases are synchronized by applying the redo logs?

  Is it possible to instantly apply redo logs to minimize the loss of data in case of automatic failover?

  If we need more information, I'll give you a pleasure it.

  Thanks in advance,

  Peter

  A RAC cluster still need a shared storage for database files: each cluster node cannot have its own separate storage.

  You need at least a physical database server 3rd for the standby database that can function without Data Guard as long as you use you own scripts to send and apply archived redo logs or use a product like dbvisit.

  I don't think it's possible to apply again immediately without Data Guard.