Redo apply stop

Similar Questions

• How to take the database waiting for return in redo apply a State of

  Hello
  
  I have 2 questions on physical standby
  
  1. I have cancel the roll forward apply on a database of Eve, opened in read-only mode to querry. And how I could do to take the day before to redo apply a State as before? A command that will help me?
  
  2. in what cases to the primary database redo log is transported to the backup database
  -primary: validation
  -primary: checkpoint
  -primary: Journal of switch
  
  
  So thank you

  http://download.Oracle.com/docs/CD/B28359_01/server.111/b28294/protection.htm

  Since you move only protection max max availability all you need is to run:

  SQL > ALTER DATABASE DATABASE SET STANDBY TO MAXIMIZE AVAILABILITY.

• 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

• Logs archiving shipped and registered, but not applied in physical standby

  Our principal is node 3 RAC 11.2.0.1 on Redhat 5.2. Even for physical intelligence except that there is an instance. Applying recovery found the order Dec. 15. I checked and see that all archivedlogs are transported to the waiting and they are up-to-date in comapare the result of the query v$ archive_log primary and standby and comparing the physical files. I then tried to save the journal archived pending. I started the archivelog unapplied ealiese

  SQL> ALTER DATABASE REGISTER OGFILE '/u01/flash/flashback_recovery_area/CCHDR/archivelog/2010_12_15/o1_mf_2_10620_6jlk3g25_.arc';
  ALTER DATABASE REGISTER LOGFILE '/u01/flash/flashback_recovery_area/CCHDR/archivelog/2010_12_15/o1_mf_2_10620_6jlk3g25_.arc'
  *
  ERROR at line 1:
  ORA-16089: archive log has already been registered

  Check the standby file alert_log and see that the primary connection was broken at the point where redo apply stop:

  .....
  Recovery of Online Redo Log: Thread 2 Group 10 Seq 10615 Reading mem 0
    Mem# 0: +REDO/cchdr/onlinelog/group_10.303.736441613
  Wed Dec 15 16:33:14 2010
  RFS[22]: Possible network disconnect with primary database
  ....

  While primary alert_log indicates that at the time where the database has been reset. Afyer the primaries started, Data Guard Broker has been initialized

  ....
  ALTER DATABASE OPEN
  Data Guard Broker initializing...
  Data Guard Broker initialization complete
  Data Guard: verifying database primary role...
  Starting Data Guard Broker (DMON)
  Wed Dec 15 16:46:15 2010
  This instance was first to open
  Block change tracking file is current.
  Beginning crash recovery of 2 threads
   parallel recovery started with 3 processes
  ....

  Now how can I leave again apply service continue?

  Audit of...

  «We watch, entry here strictly only by sequnece #.»

  Expected result. It's just to get a game from the primary.
  The main is followed by two series.

  "You find clues here?

  Others that you have removed any doubt thereon being not applied no..

  And I really sorry, I want to provide something more.

  '' Waiting, sone entries are with dest_id = 2, they are really initially generated from standby ''?

  Big question. I do not know. Checked: oracle note 241374.1 for details on dest_id without success.

  I think it's that dest_id indicates whether the destination is local or remote. If, if it is true that the answer is no.

  This makes sense since the database is read_only mode, why it would generate archive here?

  If you still have all the archive back to 12-15 then there is still hope.

  However, 12-15 is a long time ago. I consider at least rebuild the day before.

  241374.1 is worth a visit because it can provide additional information for the future.

  Published by: mseberg on January 5, 2011 15:01

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

• Ensure physical databases: two types of clauses Apply

  Version: 11.2.0.3
  Platform: AIX 6
  
  
  
  Type1 (I think that's what we call 'Red applies'. I'm not sure)
  =====
  
  In this type of 'traditional', MRP process wait a standby redo log has been archived and then apply the redo it contains the DB pending.
  This type is activated using
  

  sqlplus / as sysdba
  startup mount; 
  alter database recover managed standby database disconnect from session;

  Type2 (Apply in real time)
  =====
  
  With real-time applies, the redo data is always written in standby redo log, but MRP can straigtaway read and apply again to the DB without having to wait for redo log shall check.
  
  Apply real-time is enabled using

  sqlplus / as sysdba
  startup mount; 
  alter database recover managed standby database using current logfile disconnect;

  My statements above are correct?
  
  
  I have another question about why there are 2 options starting at the redo apply, such as foreground and background, process.
  
  For example: to Type1 (' redo apply)
  You can start at the redo apply as
  
  -foreground process

  ALTER DATABASE RECOVER MANAGED STANDBY DATABASE;

  -backround process.
  

  alter database recover managed standby database disconnect from session;

  They all have two returns control to SQL Prompt. Right?
  So what is the difference in starting it again apply as a process in the foreground and background?

  Hello

  Ken_73 wrote:
  Version: 11.2.0.3
  Platform: AIX 6

  Type1 (I think that's what we call 'Red applies'. I'm not sure)
  =====

  In this type of 'traditional', MRP process wait a standby redo log has been archived and then apply the redo it contains the DB pending.
  This type is activated using

  sqlplus / as sysdba
  startup mount;
  alter database recover managed standby database disconnect from session;
  

  Type2 (Apply in real time)
  =====

  With real-time applies, the redo data is always written in standby redo log, but MRP can straigtaway read and apply again to the DB without having to wait for redo log shall check.

  Apply real-time is enabled using

  sqlplus / as sysdba
  startup mount;
  alter database recover managed standby database using current logfile disconnect;
  

  My statements above are correct?

  Yes it's true.
  >
  >

  I have another question about why there are 2 options starting at the redo apply, such as foreground and background, process.

  For example: to Type1 (' redo apply)
  You can start at the redo apply as

  -foreground process

  ALTER DATABASE RECOVER MANAGED STANDBY DATABASE;
  

  -backround process.

  alter database recover managed standby database disconnect from session;
  

  They all have two returns control to SQL Prompt. Right?

  When you start MRP as a background process, you get "Changed Database" and proess background starts and stops not when disconnect you from the session.
  Because MRP running in background.

  So what is the difference in starting it again apply as a process in the foreground and background?

  If you startted MRP as freground, as you said

  ALTER DATABASE RECOVER MANAGED STANDBY DATABASE;
  

  then MRP running on the first level and when you disconnect a session, MRP will end.
  You can check v $ managed_standby do with query below

  1. open a terminal: connect to Sqlplus

  
  ALTER DATABASE RECOVER MANAGED STANDBY DATABASE;
  

  2. open another terminal to connect to sqlplus

  
  select process from  v$managed_standby where process like 'MR%';
  
  PROCESS
  ------------
  MR(fg)   - it means Media Recovery  started as foreground process
  

  3. close the 1. Terminal Server

  4. on 2. Terminal Server

  
  select process from  v$managed_standby where process like 'MR%'; 
  

  Concerning
  Mr. Mahir Quluzade
  http://www.Mahir-quluzade.com

• 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

• Resume it AGAIN APPLY: differences of 10g and 11g

  Versions > 10.2, 11.2
  OS > Solaris
  
  I have a question about step 4 below.
  In 10g and 11g versions for a physical Standby DB, you
  
  Step 1.
  Mount the DB using

  startup nomount;  
  alter database mount ;

  Step 2. Start using it to apply

  alter database recover managed standby database disconnect from session;

  Step 3. Open the DB to help ensure

  recover managed standby database cancel; -- stop the redo apply
  alter database open ; 

  Step 4. Resume it AGAIN APPLY

  alter database recover managed standby database using current logfile disconnect ;

  At this point (after step 4), version 10.2, the standby DB goes back to fashion to Mount , but DB 11.2 remains Open for READ ONLY queries because of the ACTIVE DATAGUARD feature. Am I wrong?

  Yes, you are right.

  In 10g, there is no active dataguard option (application of redo is not possible when the database is open). Application of roll forward is only possible when the backup database is in the editing phase. When the database is opened in read-only, the application mode of archive is not possible. In order to execute queries against database tables, a physical standby database, he had to stop the log apply and open the database in read-only mode. This means that the log files are waiting for this period and should be applied once the database is returned to the managed recovery mode.

  11 g, this isn't the case. It allows users to have read-only access to the pending physical databases. This option gives continuous customers the flexibility to run queries to the database physical standby, while log shipping and apply its work. The application archive is possible even when the database is open read-only. This option is called Active Dataguard (Oracle, high availability). To do this, the steps you have mentioned are perfect. It's the advantage in 11g.

• How to set up a database of Eve 'apply in real time '.

  Hi all

  11 GR 2,

  Rhel6

  How to set up real-time apply such as the transactions are updated in near real-time to the wait, even without switching to log files?

  For example, we have 1 GB size redo logs and assuming that it will take 1 day to fill these newspapers. This means that our expectation will be entitled to 1 day delay of data?

  This means we lost 1 day of a disaster at the primary data value? because the redo log was not able to move the log files?

  Thank you very much

  JC

  Hello

  Hope this helps

  Real time apply ---> all committed changes should have been applied in standby mode

  How to:

  standby mode

  SQL > alter database recover managed standby undo;

  SQL > change managed database recovery ensures assistance to disconnect log current;        --> You should have SRL and this command works up to 11g, 12 c apply by default start with real time

  At the primary level: check the recovery mode:

  SELECT DEST_ID, RECOVERY_MODE FROM V$ ARCHIVE_DEST_STATUS WHERE DEST_ID = 2;

  Read only apply with--> is called as--> ACTIVE DATA GUARD redo apply when the database is open read-only

  
  

  standby mode

  SQL > alter database recover managed standby undo;

  SQL > alter database open read-only.

  SQL > change managed database recovery ensures assistance to disconnect log current;        --> You should have SRL and this command works up to 11g, 12 c apply by default start with real time

  SQL > select name, open_mode, controlfile_type, db_unique_name from v$ database;

  Thank you

• Apply real-time: delay is ignored

  Hello

  I am trying to set up a standby database can be found in paragraph 12.1, but apply in time is always activate.

  Of the primary database, I always see in the alert.log:

  WARNING: Managed Standby recovery started by APPLYING in TIME REAL

  DELAY of 60 minutes ignored elementary

  Same database alert.log emergency exit:

  Managed Standby recovery started by APPLYING in TIME REAL

  Specified previously ignorant DELAY 60 minutes for the sequence of thread 1 169

  Archived newspapers is copied on standby but applied immediately. Delay of log_archive_dest_2 is ignored. Why?

  Primary DB:

  Select the id dest_id, database_mode db_mode, recovery_mode,.

  protection_mode, standby_logfile_count 'litigants. "

  ACTIVE standby_logfile_active,

  archived_seq #.

  v $ archive_dest_status;

  ID DB_MODE RECOVERY_MODE PROTECTION_MODE ACTIVE ARCHIVED_SEQ LAR #.

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

  1 OPEN 0 0 169 IDLE MAXIMUM PERFORMANCE

  2 RISE-STANDBY MANAGED IN TIME REAL IS APPLIES TO MAXIMUM PERFORMANCE 4 0 169

  Specific parameters are:

  log_archive_config DG_CONFIG = (JFDG, JFDG_SB)

  LOG_ARCHIVE_DEST_2 SERVICE = JFDG_SB ARCH ASYNC DELAY = 60 VALID_FOR = (ALL_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME = JFDG_SB

  LOG_ARCHIVE_DEST_STATE_2 ENABLE

  standby_file_management AUTO

  I restarted standby db with

  ALTER DATABASE RECOVER MANAGED STANDBY BASE DISCONNECT FROM THE SESSION.

  or

  recover the parallel managed standby database disconnect 2;

  = > same result

  How can I use a delay of application of archived log?

  The version of the database is:

  Patch 20831110: applied on Thu Sep 24 09:55:04 CEST 2015

  Patch ID: 18977826

  Patch description: "Set update database: 12.1.0.2.4 (20831110).

  Operating system: Redhat 64 x 6.6 (2.6.32 - 504.el6.x86_64)

  Hello

  1. oracle docs: https://docs.oracle.com/database/121/SBYDB/release_changes.htm#SBYDB5408

  Apply specific features to redo

  • The USING CURRENT LOGFILE article is is no longer required to start real-time applies.
  • To physical databases ensure, issue the ALTER DATABASE RECOVER MANAGED STANDBY DATABASE statement. (From the Oracle 12 c Release 1 database (12.1), the USING CURRENT LOGFILE article is obsolete and is no longer necessary to start real-time applies.) (doc: https://docs.oracle.com/database/121/SBYDB/log_apply.htm#SBYDB0050)

  2. entry delay (real-time applies to will does not provide the option, his conflict with your apply requirement)

  Doc: https://docs.oracle.com/database/121/SBYDB/log_apply.htm#SBYDB4762

  Note:

  If you set a deadline for a destination which in real time is activated, delay is ignored. If you set a delay as described in the following paragraph, then you must start the application using the NEWSPAPER ARCHIVE in the HELP file

  clause contained in Section 8.3.1

  .

  3 doc:https://docs.oracle.com/database/121/SQLRF/statements_1006.htm#SQLRF00802

  https://docs.Oracle.com/database/121/SQLRF/statements_1006.htm#BGECJDHB

  Note:

  Beginning with the Oracle 12 c database

  real-time applies

  is enabled by default in the course from the redo apply. Real-time apply redo retrieves waiting for redo log files as soon as they are written, without having to check in all first to the physical database ensures. You can disable real-time apply, with the USING ARCHIVED LOGFILE clause. Refer to:

  It may be useful

  Every bit of information is covered in Oracle docs, spare some time for learning.

  -Pavan Kumar N

• Real as for again time doubt REALITY apply to the Dataguard

  Friends, how to check if "TIME REAL REDO APPLY" is set in my configuration of dataguard. If it is not "active", how do I activate the "TIME REAL REDO APPLY" on the use of dataguard broker.
  
  Thanks in advance.

  This will help you

  http://aprakash.WordPress.com/2012/03/14/how-to-check-real-time-apply-is-enabled-on-standby-database/

  http://easyoradba.com/2011/01/10/real-time-apply-in-Oracle-Data-Guard-10G/

• Repeat applies without using Data Guard

  Hello everyone,
  
  I would like to redo apply to a database of pending. Unfortunately, the DB's standard edition for Data Guard is not an option. Is there documentation on how to achieve something like the roll forward apply without using Data Guard?
  
  Kind regards
  Frank

  There are a lot of threads on this same forum on this specific topic.
  Please use the search (top right of page), and see the list of threads returned:
  https://forums.Oracle.com/forums/search.jspa?threadID=&q=%2Bstandby+%2Bstandard+%2Bedition&objid=F61&DateRange=all&userid=&NumResults=15

  Nicolas.

• stop the sound with the action script?

  Hello

  Im a beginner with action script, and is there a way to stop a sound using actionscript?

  My sound is called "CRICKET.mp3", if it is necessary to know.

  You can still use:

  SoundMixer.stopAll ();

  to stop all sounds.  but, if you want to stop a particular sound, you must apply stop() to soundchannel your sound (created when the play() method is applied to your sound).

• Duplicate active Linux64 on Windows32

  Hello

  I try active duplicate of Centos5.9 64-bit to 32-bit of Windows XP. Because from what I've read, this should be possible, at least they have the same endian format. However, when I try it fails with the following error. Tried searching to no avail. If you can give some ideas that could be the reason.

  RMAN output:

  C:\Documents and Settings\Oracle > auxiliary rman to 'sys@ORCL as sysdba' target 'sys@ORAKAL as sysdba'

  Recovery Manager: release 11.2.0.3.0 - Production on Mon Nov 30 16:43:30 2015

  Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

  target password database:

  connected to target database: ORCL (DBID = 1421427435)

  database Assistant password:

  connected to the auxiliary database: ORAKAL (unassembled)

  RMAN > database of target ORAKAL of the active database duplicate;

  From 30 November 15 Db double

  using the control file of the target instead of recovery catalog database

  allocated channel: ORA_AUX_DISK_1

  channel ORA_AUX_DISK_1: SID = 192 type device = DISK

  content of Script memory:

  {

  clone of SQL 'alter system set = db_name

  "ORCL" comment =

  ' Modified by RMAN duplicate "scope = spfile;

  clone of SQL 'alter system set db_unique_name =

  "ORAKAL" comment =

  ' Modified by RMAN duplicate "scope = spfile;

  clone to stop immediately;

  Start clone force nomount

  backup format copy current controlfile auxiliary ' C:\APP\ORACLE\FAST_RECOVERY_AREA\ORAKAL\CONTROLFILE\O1_MF_C5RR507Q_. CTL';

  change the clone database mount;

  }

  execution of Script memory

  SQL statement: change the system db_name set = comment "ORCL" = "modified by RMAN duplicate" scope = spfile

  SQL statement: alter system set db_unique_name = comment "ORAKAL" = "modified by RMAN duplicate" scope = spfile

  Instance Oracle to close

  Oracle instance started

  Total System Global Area 523108352 bytes

  Bytes of size 1385752 fixed

  314575592 variable size bytes

  201326592 of database buffers bytes

  Redo buffers 5820416 bytes

  From 30 November 15 backup

  allocated channel: ORA_DISK_1

  channel ORA_DISK_1: SID = 147 type device = DISK

  channel ORA_DISK_1: from data file copy

  copy the current control file

  tag name=/u01/app/oracle/product/11.2.0.3/dbs/snapcf_orcl.f output file = TAG20151

  130T 064402 RECID = STAMP 5 = 897115443

  channel ORA_DISK_1: datafile copy complete, duration: 00:00:01

  Backup completed on 30 November 15

  RMAN-00571: ===========================================================

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

  RMAN-00571: ===========================================================

  RMAN-03002: failure of the command duplicate Db at 30/11/2015-16:44

  RMAN-04006: auxiliary database error: ORA-12518: TNS:listener could not hand off client connection

  RMAN-03015: an error has occurred in the script stored memory Script

  RMAN-06136: the auxiliary database ORACLE error: ORA-03113: end of file on communication channel

  Process ID: 2652

  Session ID: 63 serial number: 5

  SPFile to the database:

  * .audit_trail = "db".

  * full = '11.2.0.0.0'

  * .control_files = "

  * .db_block_size = 8192

  *.db_file_name_convert='/U01/app/Oracle/oradata/ORCL / ',' C:\app\oracle\oradata'

  * .db_name = "ORAKAL".

  * .db_recovery_file_dest = "C:\app\oracle\fast_recovery_area".

  * .db_recovery_file_dest_size = 4322230272

  * .db_unique_name = "ORAKAL".

  * .diagnostic_dest = "C:\app\oracle".

  *.log_file_name_convert='/U01/app/Oracle/oradata/ORCL ',' C:\app\oracle\oradata'

  * .memory_target = 524288000

  * .open_cursors = 300

  * runoff = 150

  * .remote_login_passwordfile = "EXCLUSIVE."

  * .standby_file_management = "auto".

  * .undo_tablespace = "UNDOTBS1.

  Listener.ora on server to the:

  SID_LIST_LISTENER =

  (SID_LIST =

  (SID_DESC =

  (GLOBAL_DBNAME = ORAKAL)

  (SID_NAME = ORAKAL)

  (ORACLE_HOME = C:\app\oracle\product\11.2.0.3)

  )

  )

  LISTENER =

  (DESCRIPTION_LIST =

  (DESCRIPTION =

  (ADDRESS = (PROTOCOL = TCP) (HOST = < ip >)(PORT = 1521))

  )

  )

  ADR_BASE_LISTENER = C:\app\Oracle

  I managed to pass this error. The problem was that I had specifically put control_files empty string "(always check the alerts log!). I just put it in a file specific to the place. But now, to recover, I got the error:

  ORA-00600: internal error code, arguments: [ktbrcl:CDLC not in Czech Republic]

  which is described in several notes of support but the cause is if the primary database has been improved v10 or lower, but in my case - I installed 11.2.0.3 own on both machines.

  ---

  EDIT:

  Note, application of redo is not supported between Linux and Windows except with a database of pending. This means that the backup must be a

  cold (consistent) backup, requiring no application of redo.  If redo applies is required to recover the database on the new platform, it will fail.

  The backup method using coherent (cold) should be used for duplication of cross-platform.

• is this problem with newspapers to 5

  Salute to the primary side, I have 3 logfile and after a few days, my day also 3 redo log files... a few days standby does not,., at the moment I can build good incremental backup... to order question time

  recover the database noredo;

  Adjust your command file according to your expectation by scenarios

  After create new redo log files;

  Step 10: On the eve... Create the standby Redo Log file

  For example (departure for the location, the group number and size)

  SQL > alter database add thread 1 standby logfile group x "remake the log location" MB in size;

  SQL > alter database add standby logfile thread 1 Group 5 ' / oracle/oradata01/test1/redo05.log' size

  52428800;

  SQL > alter database add standby logfile thread 1 Group 6 ' / oracle/oradata01/test1/redo06.log' size

  52428800;

  Step 11: for help... If there is inconsistency in the location of the data between the primary and standby files,

  need to update the control file, follow these steps

  SQL > Alter system set standby_file_management = manual;

  SQL > alter database recover managed standby database cancel;

  SQL > shutdown immediate;

  SQL > startup mount

  SQL > alter database rename datafile ' data primary file location ' to 'sleep datafile rental;

  I followed these steps, I got 5 again connects now... but my prod only 3 newspaper are there questions

  ??

  Hello;

  Looks like you are missing at least one day before newspaper. Might want to consider adding a.

  While waiting for redo logs is not mandatory, it is a good idea to have them. They must be the same size as the redo log and

  You should have the same number of newspapers of recovery sleep (or higher) as regular redo logs.

  Another query, you can use this:

  Select Group #, Member of v$ logfile where type = "STANDBY."

  Also if you need to delete or correct a standby log on the database in standby mode you must first cancel recovery.

  ALTER database recover managed standby database cancel;

  If you broker Data Guard configuration do not use the above command.

  DATABASE EDITION SET STATE = "APPLY-STOP."

  Best regards

  mseberg