Create the REDO Logs after restoration of RMAN

Similar Questions

• 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

• 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

• Truncate a table without removing the redo log

  Hi Experts,
  
  Could you please tell me is it possible to truncate a table without removing the Redo log. In fact, I know it is not possible, but some body asked me the same question, and I want to be sure before answering him.
  
  Help, please.
  
  Concerning
  Rajat

  >
  I'm not familiar with these tearms (Flashback or Rman backup). But I acccess DBA. Could you please tell me the procedures.
  >
  You can restore data from a backup or export.

  You cannot use FLASHBACK to recover the data unless you use GR 11, 2 and that you have prepared (using TOTAL RECALL) for this in advance.

  See Tubby response in this thread
  Flashback the truncate table is possible in 11g?

• Question about how Oracle manages the Redo logs

  Hello
  
  Assuming a configuration which consists of 2 redo log groups (groups A and B), each group of 2 disks (disks A1 and A2 for Group A) and B1 and B2 disks for Group B. Additionally, assume that each redo log file resides by itself in a disk storage device and that the device is dedicated to her. So in the situation described above, there are 4 discs, one for each redo log file, and each disc contains nothing other than a redo log file. Also, assume that the database is in ARCHIVELOG mode and the files from archive is stored on another different set of devices.
  
  kind of graphically:
  

      GROUP A             GROUP B
  
        A1                  B1
        A2                  B2

  The question is: when the disks that make up the Group A are filled and Oracle switches to the disks in the Group B, can the group drives to take offline, perhaps even physically removed from the system if necessary without affecting the functioning of the database? Can the archiver process temporarily delayed until the disks (which have been removed) are presented online or is the DBA have to wait until the end of the process to archive a copy of the redo log file creating in archive?
  
  Thank you for your help,
  
  John.

  Hello
  A journal of the groups fall

  To remove a group of online redo logs, you must have the ALTER DATABASE system privilege. Before you delete a line redo log group, consider the following precautions and restrictions:

  * An instance requires at least two groups of files logging online, regardless of the number of members in the groups. (A group is one or more members.)
  * You can delete a group of newspapers online redo only if it is inactive. If you need to drop the current group, first force a log switch occurs.
  * Make sure a group of online redo logs is archived (if archiving is enabled) before dropping. To see if this happens, use the view LOG V$.

  SELECT GROUP #, ARCHIVED, STATUS FROM V$ LOG;

  GROUP # ARC STATUS
  --------- --- ----------------
  1 ACTIVE YES
  2. NO CURRENT
  3 INACTIVE YES
  4 INACTIVE YES

  Delete a group of newspapers online redo with the SQL ALTER DATABASE statement with the DROP LOGFILE clause.

  The following statement drops redo log group number 3:

  ALTER DATABASE, DROP LOGFILE GROUP 3;

  When a group of online redo logs is deleted from the database, and you do not use Oracle managed files, operating system files are not removed from the disk. Instead, control of the associated database files are updated to remove members of the Group of the database structure. After deleting a group of online redo logs, make sure the drop completed successfully and then use the command of operating system appropriate to delete the dropped online redo log files.

  When you work with files managed by Oracle, the cleaning of operating system files is done automatically for you.
  Your database will not be affected as you can work with 2 files, redo log in each group, as the minimum number of redo log in a database file is two because the process LGWR (newspaper writer) writes in the redo log in a circular way. If the process crashes because you have 2 groups only if you want to remove 1 Add a third and make that the current group and remove the one you want to be offline.

  Please refer to:
  http://download.Oracle.com/docs/CD/B10500_01/server.920/a96521/onlineredo.htm#7438
  Kind regards
  Mohamed
  Oracle DBA

• Question about the size of the redo log buffer

  Hello
  
  I am a student in Oracle and the book I use says that having a bigger than the buffer log by default, the size is a bad idea.
  
  It sets out the reasons for this are:
  
  >
  The problem is that when a statement COMMIT is issued, part of the batch validation means to write the contents of the buffer log for redo log to disk files. This entry occurs in real time, and if it is in progress, the session that issued the VALIDATION will be suspended.
  >
  
  I understand that if the redo log buffer is too large, memory is lost and in some cases could result in disk i/o.
  
  What I'm not clear on is, the book makes it sound as if a log buffer would cause additional or IO work. I would have thought that the amount of work or IO would be substantially the same (if not identical) because writing the buffer log for redo log files is based on the postings show and not the size of the buffer itself (or its satiety).
  
  Description of the book is misleading, or did I miss something important to have a larger than necessary log buffer?
  
  Thank you for your help,
  
  John.
  
  Published by: 440bx - 11 GR 2 on August 1st, 2010 09:05 - edited for formatting of the citation

  A commit evacuates everything that in the buffer redolog for redo log files.
  A redo log buffer contains the modified data.
  But this is not just commit who empty the redolog buffer to restore the log files.
  LGWR active every time that:
  (1) a validation occurs
  (2) when the redo log is 1/3 full
  (3) every 3 seconds
  It is not always necessary that this redolog file will contain validated data.
  If there is no commit after 3 seconds, redologfile would be bound to contain uncommitted data.

  Best,
  Wissem

• SIZE OF THE REDO LOG FILE

  
  Hello

  I got an error message when I add me new group. log files I searched and found the answer on the form. Ago 4 M minimum size of 11 g R2 log file size.

  My question is why a log file size depends on DB_BLOCK_SIZE? This parameter is set to the component structures of memory that create an instance when a log file is an operating system file that depend on the version of the OS not DB_BLOCK_SIZE.

  Thank you.

  
  SQL > alter database add logfile group 4 'c:\app\asif\oradata\employee\redo04.log' size 1 m;
  alter database add logfile group 4 'c:\app\asif\oradata\employee\redo04.log' size 1 m
  *
  ERROR on line 1:
  ORA-00336: 2048 blocks the size of the log file is minimum lower than 8192 blocks

  
  SQL > show parameter db_block_size

  VALUE OF TYPE NAME
  ------------------------------------ ----------- ------------------------------
  Whole DB_BLOCK_SIZE 8192
  SQL >

  You are assuming that the redo log block size is the same as the database block size. This is not correct.

  The error indicates that 8192 is the minimum number of blocks of a redo log file. The documentation states that the minimum size is 4 M. For example, you can deduct your redo log block size is 512 bytes.

  Here's some more information about the size of redo log, the documentation block.

  Unlike the database block size, which can always be between 2 K and 32 K, redo log default files to a block size that is equal to the size of physical sector of the disk. Historically, it is usually 512 bytes (512 b).

  Some new large disks offer 4K sizes byte (4K) to increase sector efficiency improved format and ECC capabilities. Most of the Oracle database platforms are able to detect this bigger sector size. The database then automatically creates files redo log with a block size of 4 K of these discs.

• Redo Logs after duplication 3 RAC node to node 2 RAC

  I use RMAN to clone my production database 10.2.0.4 (3 node RAC) in my test database (2 node RAC). When I finished, I find myself with the Redo Logs from the 3rd node RAC in a State of "weird." Newspapers of recovery for "thread 3", which does not exist, cause no problem, I want to clean them and reclaim the space.
  
  Ideas or suggestions?
  
  Thank you!

  Have you tried: -.

  ALTER DATABASE DISABLE THREAD 3.

• delete the archive logs after cold backup?

  Hi all
  my database is in archivelog mode, I do COLD backup every night, can I just remove the archive logs after I do my cold backup, because there is no need of them, as the closed DB should have all the info in the archived papers
  
  and archive connected is needed only during the day, if a sudden power outage that happened.
  
  Thank you very much

  The ArchiveLogs allow you RollForward a backup restored to a specific point in time.

  Assuming that stop you your database at 23:00 (2300) every night and backup up to 11 h 45 (2345) tracks...

  Significant transactions entered between 15:00 and 16:00 on Friday, but a person deleted by mistake the lines (or some other lines) at 17:00

  your current backup strategy of "restoration" of the database only allows 23:00 Thursday night. If you also back up your archivelogs (in this case, the backup of Friday night would the archivelogs), you restore Thursday night backup 'cold' and "rollforward" by publishing a RECOVER database with the HELP of BACKUP CONTROLFILE until 16:00 Friday.

• importance of the size of the Redo Log

  Hi guys,.

  What is the importance of the size of the size of Redlog?

  whether large or small size?

  Thanks in advance

  REDA

  What is the importance of the size of the size of Redlog?

  Setting up a database of Performance

  Manage the Redo Log

• 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.

• bottleneck during the passage of the redo log files.

  Hi all
  
  I'm using Oracle 11.2.0.3.
  
  The enforcement team has indicated that they are facing slow at some point.
  
  I followed the database and I found that at some passage of redo log files (not always), I am facing a slow at the application level.
  
  I have 2 son since my database is CARS, each thread has 3 groups of multiplexed redo logs the FIU, with size of 300 MB each.
  
  Is it possible to optimize the switch of the redo log files? knowing that my database is running in ARCHIVELOG mode.
  
  Kind regards

  Hello

  Yes, Oracle recommends 1 validation by 30 calls from users or less. Of course, every database is different, so this rule cannot be taken too literally, but in your case, this rule seems to apply. In any case State, 900 undertakes seconds it looks like a very large number and the need for a high number of transactions should be questioned. You should talk to your analysts/application management/enterprise architect if warranted - that is to say if the application does in fact almost 2 000 business transactions per second.

  What about DB CPU: here is a link to a blog that I wrote on this subject, it should help to better understand this number:

  http://Savvinov.com/2012/04/06/AWR-reports-interpreting-CPU-usage/

  But briefly: DB processor isn't a real event, it is simply an indication that the sessions are on CPU (or waiting for CPU) rather than wait on i/o requests or events in the database. It is not necessarily a bad thing, because the database must perform tasks and he cannot do without loading the CPU. It may indicate a problem in two cases: when the CPU usage is close to the limit of the host (OS stats section indicates that you are very far from there) or when the CPU is a % of DB time - in the latter case, this could mean that you are making too many logical reads due to inefficient plans or analysis too. In any case, this does not apply to you, because 20 percent is not very high a number.

  Other items in the list of the top 5 deserve attention, too - gc buffer busy acquire, gc current block busy, enq: TX - line lock conflict.

  To summarize, your database under a lot of stress - whether it is the legitimate workload, and if this is the case, you may need to upgrade your hardware later. There is chance that it isn't - for example a high number of runs may indicate that rather than to bulk operations database code using PL/SQL loops, which is a big performance killer. Check "Top SQL by executions" about whether or not this is the case.

  Good luck!

  Best regards
  Nikolai

• How do I know the delay in the redo log apply on Active 11g Dataguard

  Hi all
  
  How do I know the delay in the redo log apply on Active Dataguard 11 g...
  
  Do we need to wait until the log switch occurs?
  
  Or is it recommended to provide a switch to log every 15 min, regardless of data is updated / inserted in primary school or not?
  
  Please suggest...
  
  Oracle: oracle 11g Release 2
  OS: RHEL 5.4
  
  Thank you
  
  Published by: user1687821 on February 23, 2012 12:02

  apply for time of arrival + 00 00:00:00.0 day (2) to second (1) interval February 23, 2012 03:02:16

  Here apply finish time is 'Zéro' if there are gaps in log files, this parameter shows the time it will take to resolve the discrepancy.

  apply the offset + 00 01:50:49 day (2) second (0) interval February 23, 2012 03:02:16
  transportation of shift + 00 01:50:49 day (2) second (0) interval February 23, 2012 03:02:16

  the time that redo data is not available (or) on the basis of data behind pending with the primary database.

  SQL >! date
  Thu Feb 23 03:03:34 CST 2012

  If you see your date system current and last does the end is not even a second. So probably there is no delay I would say.
  You can test by setting the timeout setting in log_archive_dest_2 (or) disable log_archive_Dest_2 for a while do two or three switches of newspaper and made attention to discrepancies between primary & eve and how does it point of view.

• Problem with the archive log when you use RMAN for backup and restore (11g 2)

  Hello world
  Please help me solve this problem.
  I'm just beginner in Oracle Database (11 g 2). Today, I had a problem, I tried to back up and restore my db by RMAN. I delete all the files in /u01/app/oracle/oradata/orcl / * , then I restore them easily, but the point is I have a table, I can restore Hungarian, but cannot restore anything ranks in it (something wrong with step restore database). I'll tell the detail below.
  -First, I create a 'Day' with command table create table hr.day (varchar (20)) day. Then I backup complete by this:
  run{
allocate channel bkp device type DISK FORMAT '/u01/backup/DB_FULL_%d_%T_s%s_p%p' ;
backup as compressed backupset incremental level 0 tag 'DB_FULL' database include current controlfile;
backup as compressed backupset tag 'ARCL_BKP_FULL' archivelog all delete input;
crosscheck archivelog all;
crosscheck backup;
delete noprompt obsolete;
release channel bkp;
}
  

  
  D ' other hand, I have insert 'Monday' to table. then do an incremental backup by this:

  run{
allocate channel bkp device type DISK FORMAT '/u01/backup/DB_INC_%d_%T_s%s_p%p' ;
backup as compressed backupset incremental level 1 tag 'DB_INC' database include current controlfile;
backup as compressed backupset tag 'ARCL_BKP_INC' archivelog all delete input;
crosscheck archivelog all;
crosscheck backup;
delete noprompt obsolete;
release channel bkp;
}

  Repeat 7 times (Monday-> Saturday). And I got these files:

  [oracle@rac ~]$ ls -l /u01/backup/
total 400280
-rw-r----- 1 oracle oinstall  10158080 Jan 20 07:23 c-1428943247-20160120-01
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:04 c-1428943247-20160120-02
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:05 c-1428943247-20160120-03
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:06 c-1428943247-20160120-04
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:08 c-1428943247-20160120-05
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:08 c-1428943247-20160120-06
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:09 c-1428943247-20160120-07
-rw-r----- 1 oracle oinstall  10158080 Jan 20 08:32 c-1428943247-20160120-08
-rw-r----- 1 oracle oinstall 296337408 Jan 20 07:23 DB_FULL_ORCL_20160120_s89_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 07:23 DB_FULL_ORCL_20160120_s90_p1
-rw-r----- 1 oracle oinstall   2266624 Jan 20 07:23 DB_FULL_ORCL_20160120_s91_p1
-rw-r----- 1 oracle oinstall   4073984 Jan 20 07:23 DB_FULL_ORCL_20160120_s92_p1
-rw-r----- 1 oracle oinstall  11201536 Jan 20 07:23 DB_FULL_ORCL_20160120_s93_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:05 DB_INC_ORCL_20160120_s100_p1
-rw-r----- 1 oracle oinstall    146944 Jan 20 08:05 DB_INC_ORCL_20160120_s101_p1
-rw-r----- 1 oracle oinstall    884736 Jan 20 08:06 DB_INC_ORCL_20160120_s103_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:06 DB_INC_ORCL_20160120_s104_p1
-rw-r----- 1 oracle oinstall     82432 Jan 20 08:06 DB_INC_ORCL_20160120_s105_p1
-rw-r----- 1 oracle oinstall    294912 Jan 20 08:07 DB_INC_ORCL_20160120_s107_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:07 DB_INC_ORCL_20160120_s108_p1
-rw-r----- 1 oracle oinstall     18944 Jan 20 08:08 DB_INC_ORCL_20160120_s109_p1
-rw-r----- 1 oracle oinstall    155648 Jan 20 08:08 DB_INC_ORCL_20160120_s111_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:08 DB_INC_ORCL_20160120_s112_p1
-rw-r----- 1 oracle oinstall    131584 Jan 20 08:08 DB_INC_ORCL_20160120_s113_p1
-rw-r----- 1 oracle oinstall    647168 Jan 20 08:09 DB_INC_ORCL_20160120_s115_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:09 DB_INC_ORCL_20160120_s116_p1
-rw-r----- 1 oracle oinstall      8704 Jan 20 08:09 DB_INC_ORCL_20160120_s117_p1
-rw-r----- 1 oracle oinstall   2203648 Jan 20 08:04 DB_INC_ORCL_20160120_s95_p1
-rw-r----- 1 oracle oinstall   1130496 Jan 20 08:04 DB_INC_ORCL_20160120_s96_p1
-rw-r----- 1 oracle oinstall   1899008 Jan 20 08:04 DB_INC_ORCL_20160120_s97_p1
-rw-r----- 1 oracle oinstall    327680 Jan 20 08:05 DB_INC_ORCL_20160120_s99_p1


  And
  RMAN> list backup summary;
List of Backups
===============
Key     TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
------- -- -- - ----------- --------------- ------- ------- ---------- ---
80      B  0  A DISK        20-JAN-16       1       1       YES        DB_FULL
81      B  0  A DISK        20-JAN-16       1       1       YES        DB_FULL
82      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL
83      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL
84      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL
85      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T072332
86      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
87      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
88      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
89      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080440
90      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
91      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
92      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
93      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080545
94      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
95      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
96      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
97      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080657
98      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
99      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
100     B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
101     B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080801
102     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
103     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
104     B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
105     B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080844
106     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
107     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
108     B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC

  My configuration of rman:
  RMAN> show all;
RMAN configuration parameters for database with db_unique_name ORCL are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u01/backup/%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '/u01/backup/backup_df%t_s%s_s%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome/dbs/snapcf_orcl.f'; # default

  - Thirdly, i removed all file in /u01/app/oracle/oradata/orcl/*. then restore control file from the newest backup control file (saturday backup) + restore database. Seem nothing's wrong here.
RMAN> restore controlfile from '/u01/backup/c-1428943247-20160120-08';
Starting restore at 20-JAN-16
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=18 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=20 device type=DISK
channel ORA_DISK_2: skipped, AUTOBACKUP already found
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:09
output file name=/u01/app/oracle/oradata/orcl/control01.ctl
output file name=/u01/app/oracle/flash_recovery_area/orcl/control02.ctl
Finished restore at 20-JAN-16

RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
released channel: ORA_DISK_2

RMAN> restore database;
Starting restore at 20-JAN-16
Starting implicit crosscheck backup at 20-JAN-16
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=20 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=18 device type=DISK
Crosschecked 29 objects
Finished implicit crosscheck backup at 20-JAN-16

Starting implicit crosscheck copy at 20-JAN-16
using channel ORA_DISK_1
using channel ORA_DISK_2
Finished implicit crosscheck copy at 20-JAN-16

searching for all files in the recovery area
cataloging files...
no files cataloged

using channel ORA_DISK_1
using channel ORA_DISK_2

channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to /u01/app/oracle/oradata/orcl/system01.dbf
channel ORA_DISK_1: restoring datafile 00002 to /u01/app/oracle/oradata/orcl/sysaux01.dbf
channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/orcl/undotbs01.dbf
channel ORA_DISK_1: restoring datafile 00004 to /u01/app/oracle/oradata/orcl/users01.dbf
channel ORA_DISK_1: restoring datafile 00005 to /u01/app/oracle/oradata/orcl/example01.dbf
channel ORA_DISK_1: reading from backup piece /u01/backup/DB_FULL_ORCL_20160120_s89_p1
channel ORA_DISK_1: piece handle=/u01/backup/DB_FULL_ORCL_20160120_s89_p1 tag=DB_FULL
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:01:15
Finished restore at 20-JAN-16


  -Fourth, the problem here, I got the database;
.. .every oky until this line...
starting media recovery

channel ORA_DISK_1: starting archived log restore to default destination
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=15
channel ORA_DISK_1: reading from backup piece /u01/backup/DB_INC_ORCL_20160120_s117_p1
channel ORA_DISK_1: piece handle=/u01/backup/DB_INC_ORCL_20160120_s117_p1 tag=ARCL_BKP_INC
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
archived log file name=/u01/app/oracle/flash_recovery_area/ORCL/archivelog/2016_01_20/o1_mf_1_15_c9xsyx9k_.arc thread=1 sequence=15
unable to find archived log
archived log thread=1 sequence=1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/20/2016 08:50:22
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 1 and starting SCN of 1205841

The error said that it is impossible to find the archived log thread = 1 sequence = 1. Then I check it with this command always there (oh, I'm wrong?)
RMAN> list backup of archivelog all;
List of Backup Sets
===================
BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
82      2.16M      DISK        00:00:00     20-JAN-16     
        BP Key: 82   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_FULL
        Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s91_p1

  List of Archived Logs in backup set 82
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
1    1       1154833    20-JAN-16 1177422    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
83      3.88M      DISK        00:00:00     20-JAN-16     
        BP Key: 83   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_FULL
        Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s92_p1

  List of Archived Logs in backup set 83
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
1    1       1162729    20-JAN-16 1188784    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
84      10.68M     DISK        00:00:01     20-JAN-16     
        BP Key: 84   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_FULL
        Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s93_p1

  List of Archived Logs in backup set 84
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    2       1177422    20-JAN-16 1201833    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
88      1.81M      DISK        00:00:01     20-JAN-16     
        BP Key: 88   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s97_p1

  List of Archived Logs in backup set 88
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    3       1201833    20-JAN-16 1204844    20-JAN-16
  1    4       1204844    20-JAN-16 1204893    20-JAN-16
  1    5       1204893    20-JAN-16 1204958    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
92      143.00K    DISK        00:00:00     20-JAN-16     
        BP Key: 92   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s101_p1

  List of Archived Logs in backup set 92
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    6       1204958    20-JAN-16 1205034    20-JAN-16
  1    7       1205034    20-JAN-16 1205253    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
96      80.00K     DISK        00:00:00     20-JAN-16     
        BP Key: 96   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s105_p1

  List of Archived Logs in backup set 96
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    8       1205253    20-JAN-16 1205354    20-JAN-16
  1    9       1205354    20-JAN-16 1205433    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
100     18.00K     DISK        00:00:00     20-JAN-16     
        BP Key: 100   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s109_p1

  List of Archived Logs in backup set 100
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    10      1205433    20-JAN-16 1205519    20-JAN-16
  1    11      1205519    20-JAN-16 1205559    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
104     128.00K    DISK        00:00:00     20-JAN-16     
        BP Key: 104   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s113_p1

  List of Archived Logs in backup set 104
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    12      1205559    20-JAN-16 1205624    20-JAN-16
  1    13      1205624    20-JAN-16 1205739    20-JAN-16

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
108     8.00K      DISK        00:00:00     20-JAN-16     
        BP Key: 108   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
        Piece Name: /u01/backup/DB_INC_ORCL_20160120_s117_p1

  List of Archived Logs in backup set 108
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    14      1205739    20-JAN-16 1205796    20-JAN-16
  1    15      1205796    20-JAN-16 1205840    20-JAN-16

  
If i ignore it and open the database, just my table in full backup come back but rows was not restored. I'm sure the problem is my archive log backup but i don't know how to solve it. Plz help me.

  Sorry for a long post.


  > 1 and from the 1205841 SNA sequence

  The SCN that indicates Oracle is above the range of SNA that you have in the ArchiveLog backups for sequence 1 to 15 (15 sequence ends at 1205840).

  The message

  channel ORA_DISK_1: restoring archives Journal

  Archives journal thread = 1 sequence = 15

  channel ORA_DISK_1: backup/u01/backup/DB_INC_ORCL_20160120_s117_p1 piece reading

  channel ORA_DISK_1: piece handle = / u01/backup/DB_INC_ORCL_20160120_s117_p1 tag = ARCL_BKP_INC

  indicates that he has restored the sequence up to 15

  You can check the log file alert database instance for messages on the fact of recovery.

  He is now asking sequence #1 it seems you did a RESETLOGS after sequence #15.

  Note: If you have NOT issued a COMMIT after the line is INSERTED in the table 'Day', the recovery of the database will have no * transactions * to retrieve.  An uncomitted transaction is cancelled.

  Hemant K Collette

• 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