Redo log shipping after a stop pending physical

Similar Questions

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

• 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

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

• REDO LOG STOP TRANSPORT MARITIMES TO THE BACKUP SITE

  Hi guru,.

  After physical creation Eve redologs are shipped and applied to standby mode. But suddenly stopped shipping redo log. I checked the main site from the log file it log archiving generates here but that is not delivered to the backup site. As I checked the pwd file is same on both sites, so I am able to connect to the db of the main site backup site.

  Can any of clarify you why it happens so.

  Thanks in advance

  From point 1 to 3, I check that all are defined

  But for pt 4 when I run the above command is as below:

  STATE ERROR

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

  VALID

  DISABLED ORA - 16057:DGID OF THE SERVER NOT IN THE CONFIG OF DATA HOLD

  OK, I got the error where is is LOG_ARCHIVE_CONFIG check box enabled on db primary

  I correct and now delivery is correct, but one thing which still confuse me, is that when I run the command to check the archiev applied

  SEQUENCE # FIRST_TIME NEXT_TIME APP

  APP COLUMN ALWAYS SHOWS NO standby, as well as on the primary, but before it shows why Yes

• Waiting for redo log file missing when restore main database using RMAN backup that was taken on the database physical standby

  Here's my question after tons of research and test without have the right solutions.

  Target:

  (1) I have a 12.1.0.2 database unique main enterprise 'testdb' as database instance running on the server "node1".

  (2) I created physical standby database "stbydb" on the server "node2".

  (3) DataGuard running on the mode of MaxAvailability (SYNC) with roll forward in real time 12 default c apply.

  (4) primary database has 3 groups of one-man redo. (/oraredo/testdb/redo01.log redo02.log redo03.log)

  (5) I've created 4 standby redo logfiles (/oraredo/testdb/stby01.log stby02.log stby03.log stby04.log)

  (6) I do RMAN backup (database and archivelog) on the site of relief only.

  (7) I want to use this backup for full restore of the database on the primary database.

  He is a DR test to simulate the scenario that has lost every primary & Eve total servers.

  Here is how to save, on the database pending:

  (1) performance 'alter database recover managed standby database Cancel' to ensure that compatible data files

  (2) RMAN > backup database;

  (3) RMAN > backup archivelog all;

  I got elements of backup and copied to primary db Server something like:

  /Home/Oracle/backupset/o1_mf_nnndf_TAG20151002T133329_c0xq099p_.BKP (data files)

  /Home/Oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.BKP (spfile & controlfile)

  /Home/Oracle/backupset/o1_mf_annnn_TAG20151002T133357_c0xq15xf_.BKP (archivelogs)

  So here's how to restore, on the main site:

  I clean all the files (data files, controlfiles oder all gone).

  (1) restore spfile from pfile

  RMAN > startup nomount

  RMAN > restore spfile from pfile ' / home/oracle/pfile.txt' to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';

  (2) modify pfile to convert to db primary content. pFile shows below

  *.audit_file_dest='/opt/Oracle/DB/admin/testdb/adump '

  * .audit_trail = "db".

  * full = '12.1.0.2.0'

  *.control_files='/oradata/testdb/control01.ctl','/orafra/testdb/control02.ctl'

  * .db_block_size = 8192

  * .db_domain = "

  *.db_file_name_convert='/testdb/','/testdb /'

  * .db_name = "testdb".

  * .db_recovery_file_dest ='/ orafra'

  * .db_recovery_file_dest_size = 10737418240

  * .db_unique_name = "testdb".

  *.diagnostic_dest='/opt/Oracle/DB '

  * .fal_server = "stbydb".

  * .log_archive_config = 'dg_config = (testdb, stbydb)'

  * .log_archive_dest_2 = "service = stbydb SYNC valid_for = (ONLINE_LOGFILE, PRIMARY_ROLE) db_unique_name = stbydb'"

  * .log_archive_dest_state_2 = 'ENABLE '.

  *.log_file_name_convert='/testdb/','/testdb /'

  * .memory_target = 1800 m

  * .open_cursors = 300

  * runoff = 300

  * .remote_login_passwordfile = "EXCLUSIVE."

  * .standby_file_management = "AUTO".

  * .undo_tablespace = "UNDOTBS1.

  (3) restart db with updated file pfile

  SQLPLUS > create spfile from pfile='/home/oracle/pfile.txt'

  SQLPLUS > the judgment

  SQLPLUS > startup nomount

  (4) restore controlfile

  RMAN > restore primary controlfile to ' / home/oracle/backupset/o1_mf_ncsnf_TAG20151002T133329_c0xq0sgz_.bkp';

  RMAN > change the editing of the database

  (5) all elements of backup catalog

  RMAN > catalog starts by ' / home/oracle/backupset / '.

  (6) restore and recover the database

  RMAN > restore database;

  RMAN > recover database until the SNA XXXXXX; (this YVERT is the maximum in archivelog backups that extends beyond the scn of the backup of the data file)

  (7) open resetlogs

  RMAN > alter database open resetlogs;

  Everything seems perfect, except one of the file log roll forward pending is not generated

  SQL > select * from v$ standby_log;

  ERROR:

  ORA-00308: cannot open archived log ' / oraredo/testdb/stby01.log'

  ORA-27037: unable to get file status

  Linux-x86_64 error: 2: no such file or directory

  Additional information: 3

  no selected line

  I intended to use the same backup to restore primary basic & helps record traffic and the downtime between them in the world of real output.

  So I have exactly the same steps (except STANDBY restore CONTROLFILE and not recover after database restore) to restore the database pending.

  And I got the same missing log file.

  The problem is:

  (1) complete alert.log filled with this error, not the concern here

  (2) now repeat it in real time apply won't work since the Party shall LGWR shows always "WAITING_FOR_LOG."

  (3) I can't delete and re-create this log file

  Then I tried several and found:

  The missing standby logfile was still 'ACTIVE' at present RMAN backup was made.

  For example, on db standby, under Group #4 (stby01.log) would be lost after the restoration.

  SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;

  GROUP # SEQUENCE # USED STATUS

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

  4 19 ACTIVE 133632

  5 0 0 UNASSIGNED

  6 0 0 not ASSIGNED

  7 0 0 UNASSIGNED

  So until I take the backup, I tried on the primary database:

  SQL > alter system set log_archive_dest_state_2 = delay;

  This was the Group of standby_log side Eve #4 was released:

  SQL > select GROUP #, SEQUENCE #, USE (s), the STATUS from v$ standby_log;

  GROUP # SEQUENCE # USED STATUS

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

  4 0 0 UNASSIGNED

  5 0 0 UNASSIGNED

  6 0 0 not ASSIGNED

  7 0 0 UNASSIGNED

  Then, the backup has been restored correctly without missing standby logfile.

  However, to change this primary database means break DataGuard protection when you perform the backup. It's not accept on the production environment.

  Finally, my real questions come:

  (1) what I do may not do on parameter change?

  (2) I know I can re-create the control file to redo before delete and then recreate after. Is there any simple/fast to avoid the standby logfile lost or recreate the lost one?

  I understand that there are a number of ways to circumvent this. Something to keep a copy of the log file waiting restoration progress and copy up one missing, etc, etc...

  And yes I always have done no real-time applies "to the aid of archived logfile" but is also not accept mode of protection of production.

  I just want proof that the design (which is displayed in a few oracle doc Doc ID 602299.1 is one of those) that backs up data backup works effectively and can be used to restore the two site. And it may be without spending more time to resume backups or put the load on the primary database to create the database before.

  Your idea is very much appreciated.

  Thank you!

  Hello

  1--> when I take via RMAN backup, RMAN does not redo log (ORL or SRL) file, so we cannot expect ORLs or SRL would be restored.

  2nd--> when we opened the ORL database should be deleted and created

  3rd--> Expecting, SRL should not be an issue.we should be able to do away with the fall.

  DR sys@cdb01 SQL > select THREAD #, SEQUENCE #, GROUP #, STATUS from v$ standby_log;

  THREAD # SEQUENCE # GROUP # STATUS

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

  1 233 4 ACTIVE

  1 238 5 ACTIVE

  DR sys@cdb01 SQL > select * from v$ logfile;

  GROUP # STATUS TYPE MEMBER IS_ CON_ID

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

  3 /u03/cdb01/cdb01/redo03.log no. 0 online

  /U03/cdb01/cdb01/redo02.log no. 0 2 online

  1 /u03/cdb01/cdb01/redo01.log no. 0 online

  4 /u03/cdb01/cdb01/stdredo01.log WATCH No. 0

  /U03/cdb01/cdb01/stdredo02.log EVE 5 No. 0

  DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

  method: cannot access the /u03/cdb01/cdb01/stdredo01.log: no such file or directory

  DR sys@cdb01 SQL >! ls - ltr /u03/cdb01/cdb01/stdredo02.log

  -rw - r-. 1 oracle oinstall 52429312 17 Oct 15:32 /u03/cdb01/cdb01/stdredo02.log

  DR sys@cdb01 SQL > alter database force claire logfile 4;

  change the database group claire logfile 4

  *

  ERROR on line 1:

  ORA-01156: recovery or current flashback may need access to files

  DR sys@cdb01 SQL > alter database recover managed standby database cancel;

  Database altered.

  DR sys@cdb01 SQL > change the database group claire logfile 4;

  Database altered.

  DR sys@cdb01 SQL > ! ls - ltr /u03/cdb01/cdb01/stdredo01.log

  -rw - r-. 1 oracle oinstall 52429312 17 Oct 15:33 /u03/cdb01/cdb01/stdredo01.log

  DR sys@cdb01 SQL >

  If you do, you can recreate the controlfile without waiting for redo log entry...

  If you still think it's something is not acceptable, you must have SR with support to analyze why he does not abandon SRL when controlfile_type is "underway".

  Thank you

• Reporter mode physical log shipping standby when you apply the patch

  I apply a (Group of hotfixes) processor for a dataguard primary and physical shall help Doc-ID 278641.1 . I need to temporarily stop archivelog shipment from primary to standby. The documentation gives this example of order:
  
  ALTER system set log_archive_dest_state_X = reporter brought = the two sid ='* '
  
  Where X is the number of destination used for shipment of recovery for the backup site.
  
  So, what is the X? In online research, the answer is almost always Log_archive_dest_state_2. Questioning primary school, 2 is idle and waiting seems to be on 1, so I think I use 1. Which should I use?
  
  On the primary:
  
  Select the State, nom_dest, DESTINATION of v$ archive_dest where status = "VALID";
  
  VALID
  LOG_ARCHIVE_DEST_1
  prod1s
  
  VALID
  LOG_ARCHIVE_DEST_10
  USE_DB_RECOVERY_FILE_DEST
  
  view the log_archive_dest_1 setting;
  
  Log_archive_dest_1 SERVICE string VALID_FOR = (ONLINE_LOGFILES, PRIMARY_ROLE) prod1s = LGW R SYNC AFFIRM DB_UNIQUE_NAME = prod1s
  
  LOG_ARCHIVE_DEST_10 string LOCATION = USE_DB_RECOVERY_FILE_DEST REQUIRED
  
  
  view the log_archive_dest_state setting
  
  VALUE OF TYPE NAME
  ------------------------------------ ---- ------------------------------
  log_archive_dest_state_1 ENABLE stri
  NG
  log_archive_dest_state_10 ENABLE stri
  NG
  LOG_ARCHIVE_DEST_STATE_2 ENABLE stri
  NG
  activate log_archive_dest_state_3 stri
  NG
  activate log_archive_dest_state_4 stri
  NG
  activate log_archive_dest_state_5 stri
  NG
  activate log_archive_dest_state_6 stri
  NG
  activate log_archive_dest_state_7 stri
  NG
  activate log_archive_dest_state_8 stri
  NG
  activate log_archive_dest_state_9 stri
  NG
  
  
  On the physics of the day before:
  
  Select the State, nom_dest, DESTINATION of v$ archive_dest where status = "VALID";
  
  VALID
  LOG_ARCHIVE_DEST_2
  prod1
  
  VALID
  LOG_ARCHIVE_DEST_10
  USE_DB_RECOVERY_FILE_DEST
  
  VALID
  STANDBY_ARCHIVE_DEST
  USE_DB_RECOVERY_FILE_DEST
  
  view the log_archive_dest_ setting
  
  LOG_ARCHIVE_DEST_10 string LOCATION = USE_DB_RECOVERY_FILE_DEST REQUIRED
  SERVICE string LOG_ARCHIVE_DEST_2 = VALID_FOR (ONLINE_LOGFILES, PRIMARY_ROLE) = prod1 LGWR
  SYNC AFFIRM DB_UNIQUE_NAME = prod1
  
  view the log_archive_dest_state setting
  
  VALUE OF TYPE NAME
  ------------------------------------ ----------- ------------------------------
  log_archive_dest_state_1 string DAVID
  log_archive_dest_state_10 string ENABLE
  allow the chain of LOG_ARCHIVE_DEST_STATE_2
  allow the chain of log_archive_dest_state_3
  allow the chain of log_archive_dest_state_4
  allow the chain of log_archive_dest_state_5
  allow the chain of log_archive_dest_state_6
  allow the chain of log_archive_dest_state_7
  allow the chain of log_archive_dest_state_8
  allow the chain of log_archive_dest_state_9
  
  DataGuard with physical standby
  DB to: 10.2.0.4.0
  No RAC, ASM or DG broker
  
  Published by: JJ on May 2, 2012 10:05
  
  Published by: JJ on May 2, 2012 10:05

  Hello;

  You want this

  ALTER system set log_archive_dest_state_2 = reporter; (you need to do to your log_archive_dest_state_n) DEST ID that apply to your system (looks like 2 also)

  I'll post my full how patch is here a moment.

  0. Disable log shipping from the Primary
  1. Shutdown Standby
  2. Install patch on Standby software only
  3. Startup Standby in recovery mode (do NOT run any SQL at the standby)
  4. Shutdown Primary
  5. Install patch on Primary
  6. Run SQL on Primary
  7. Re-enable log shipping
  8. Monitor the redo apply from Primary to Standby --- this will also upgrade the Standby 
  
  See Oracle support article : How do you apply a Patchset,PSU or CPU in a Data Guard Physical Standby configuration [ID 278641.1]
  

  Please consider old questions of closing some of you.

  Best regards

  mseberg

  Published by: mseberg on May 2, 2012 09:16

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

• 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

• Clearing Online redo logs on the physical standby of the target

  Hello
  
  Version 11202.
  
  Primer on computer a.
  Watch on computer b.
  
  Later note: 11.2 Data Guard physical standby failover best practices using SQL * Plus [1304939.1 ID].
  

   
  Online redo logs on the target physical standby need to be cleared before that standby database can become a primary database. 

  And later:

   
  On the target physical standby run the following query to determine if the online redo logs have not been cleared... 

  (1) I did not understand where I have to run the query. On computer A, computer B or?
  2)

   
           Online redo logs on the target physical standby need to be CLEARED 
          

  Which means that it must be DELETED? Does transaction could be lost by running the command of compensation?
  
  Thank you

  Hello again;

  I would NOT use a script. The reason is that you are not sure what "switchover_status" will be returned by the database of v$.

  Oracle a broker data available for a quick pass, but I'm from the old school and I want to see how thing works in SQL for awhile first.

  Best regards

  mseberg

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

• How do I know if there's bottleneck in the redo logs?

  Hi all

  EBS R12.2

  11 GR 2

  OL 6.5

  We have two groups of log of size 1 GB.

  and oyour archiving logs generates 13 newspapers every hour.

  -rw - r-. 1 oraprod s/n 956896768 Jan 25 14:00 1_3372_898613761.dbf

  -rw - r-. 1 oraprod s/n 1004083200 Jan 25 14:03 1_3373_898613761.dbf

  -rw - r-. 1 oraprod s/n 928530432 Jan 25 14:10 1_3374_898613761.dbf

  -rw - r-. 1 oraprod s/n 928728576 Jan 25 14:12 1_3375_898613761.dbf

  -rw - r-. 1 oraprod s/n 967805952 Jan 25 14:20 1_3376_898613761.dbf

  -rw - r-. 1 oraprod s/n 916065792 Jan 25 14:22 1_3377_898613761.dbf

  -rw - r-. 1 oraprod s/n 951790592 Jan 25 14:30 1_3378_898613761.dbf

  -rw - r-. 1 oraprod s/n 978358272 Jan 25 14:32 1_3379_898613761.dbf

  -rw - r-. 1 oraprod s/n 974519808 Jan 25 14:40 1_3380_898613761.dbf

  -rw - r-. 1 oraprod s/n 960421376 Jan 25 14:42 1_3381_898613761.dbf

  -rw - r-. 1 oraprod s/n 917438976 Jan 25 14:49 1_3382_898613761.dbf

  -rw - r-. 1 oraprod s/n 920794624 Jan 25 14:51 1_3383_898613761.dbf

  -rw - r-. 1 oraprod s/n 920704000 Jan 25 14:59 1_3384_898613761.dbf

  I got this alert saves messages:

  Mon Jan 25 15:08:37 2016

  Filled checkpoint up to RBA [0xd3b.2.10], RCS: 5978324588151

  Mon Jan 25 15:10:57 2016

  Thread 1 cannot allot of new newspapers, sequence 3388

  Private stream flush is not complete

  Currently journal # 1, seq # 3387 mem # 0: /home/oraprod/PROD/data/log01a.dbf

  Currently journal # 1, seq # 3387 mem # 1: /home/oraprod/PROD/data/log01b.dbf

  Beginning log switch checkpoint up to RBA [0xd3c.2.10], RCS: 5978324634623

  Thread 1 Advanced for you connect to sequence 3388 (switch LGWR)

  Currently Journal # 2 seq # 3388 mem # 0: /home/oraprod/PROD/data/log02a.dbf

  Currently Journal # 2 seq # 3388 mem # 1: /home/oraprod/PROD/data/log02b.dbf

  Mon Jan 25 15:11:01 2016

  LNS: Standby redo log file selected for thread 1 sequence 3388 for destination LOG_ARCHIVE_DEST_2

  Mon Jan 25 15:11:04 2016

  Archived journal 6791 extra for each sequence 1 3387 ID thread entry 0 x 12809081 dest 1:

  Mon Jan 25 15:11:17 2016

  Filled checkpoint up to RBA [0xd3c.2.10], RCS: 5978324634623

  Mon Jan 25 15:13 2016

  Additional checkpoint up to RBA to RBA [0xd3c.1a8e82.0] [0xd3c.18d210.0], current journal line

  Mon Jan 25 15:13:04 2016

  Thread 1 cannot allot of new newspapers, sequence 3389

  Private stream flush is not complete

  Currently Journal # 2 seq # 3388 mem # 0: /home/oraprod/PROD/data/log02a.dbf

  Currently Journal # 2 seq # 3388 mem # 1: /home/oraprod/PROD/data/log02b.dbf

  Beginning log switch checkpoint up to RBA [0xd3d.2.10], RCS: 5978324673444

  Thread 1 Advanced for you connect to 3389 (switch LGWR) sequence

  Currently journal # 1, seq # 3389 mem # 0: /home/oraprod/PROD/data/log01a.dbf

  Currently journal # 1, seq # 3389 mem # 1: /home/oraprod/PROD/data/log01b.dbf

  Mon Jan 25 15:13:07 2016

  LNS: Standby redo log file selected for thread 1 sequence 3389 for destination LOG_ARCHIVE_DEST_2

  Mon Jan 25 15:13:09 2016

  Archived journal 6793 extra for each sequence 1 3388 ID thread entry 0 x 12809081 dest 1:

  Mon Jan 25 15:13:11 2016

  Filled checkpoint up to RBA [0xd3d.2.10], RCS: 5978324673444

  Is it a sign of botteneck? Users complained that each 15:00 they encounter performance degradation.

  Kind regards

  JC

  Jenna_C wrote:

  We have two groups of size 1 GB log and our archiving logs generates 13 newspapers every hour.

  Is it a sign of botteneck? Users complained that each 15:00 they encounter performance degradation.

  If your users are complaining about slow at 15:00 then look at what is happening on the system at this point in time.  Use the Active Session history, providing that you have the license, at 3 pm to see if there is a problem.  Or take snapshots of the AWR manually around 15:00 in an attempt to capture any anomaly.  Or capture instant V$ SESSION yourself manually around 15:00 and see so many sessions is pending or not.

  I have seen problems like this on shared physical infrastructure systems where the activity on a system can interfere with each other.  Attention to this kind of thing, because if it is caused by another system then you will never find the cause of the problem inside the Oracle.  Examples include backups are made at a specific time, causing large amounts of sequential disk i/o and slows down access to the drive for everything else.  Such a scenario could cause some writing redo log time to increase significantly.  Or the backup could be another system completely who shares the same disks in the same drive bay or the SAN and Bay drives or SAN is inundated by applications e/s backup.  But as it's another system, that you will not see what is happening on your Oracle database system.

  Or a virtualized with environment sharing CPU and memory where another virtual machine running a CPU intensive job and steals the Oracle system CPU capacity.  I saw the same thing with memory so - Vmware has a strange way to virtualize memory, which means it can use all of the memory on the physical hardware and run out, and then he had to intervene to release somehow little memory.  What ends up slowing things down.

  It could be a network problem - is something that the network of the floods at 15:00?  Still, backups can be a common cause of this, during the transfer of data over the network to another system.  Is there a work extracted regularly data which runs at 15:00 for example extract given OLTP to feed into a data warehouse, which is copied on the network?

  It could be many different things, causing the slowdown.  I would definitely recommend watching any expected sessions know and see if this gets worse around 15:00, or if it remains the same, in which case the problem is elsewhere.  You must also eliminate everything else - the disks, network, etc.

  Good luck

  John Brady

• Will be online Redo Logs to sleep never used?

  Version: 11 GR 2

  OS: Oracle Linux 6.5

  Pending a physical DB, newspapers online redo will be ever written because the author of newspaper on the standby site will be inactive. Right?

  In the DB in waiting, only forward Redo logs will be written to by RFS. Right?

  Pending a physical DB, newspapers online redo will be ever written because the author of newspaper on the standby site will be inactive. Right?

  ORL will be used when the database starts to behave like a primary database and LGWR writes the data to the newspaper for the ORL buffer again.

  They are not used while the database behaves like a physical standby.

  In the DB in waiting, only forward Redo logs will be written to by RFS. Right?

  Yes, the process RFS writes that data to the standby redo redo logs on the standby database.

  Just for your reference https://docs.oracle.com/cd/B19306_01/server.102/b14239/log_apply.htm#i1022881

  HTH

  -Jonathan Rolland