DataPump on Standby Database

Similar Questions

• Roll forward standby database with the incremental backup, when a data file is deleted in primary education

  Hello

  I'm nologging operations + deleting some files in the primary and you want to roll forward the day before using the incremental backup Yvert.

  I do in particular, as the files are dropped?

  I got to meet ( Doc ID 1531031.1 ) which explains how to roll forward when a data file is added.

  If I follow the same steps, to make the move to restore the data file newly added, will it work in my case?

  Can someone please clarify?

  Thank you

  San

  I was wondering if reocover noredo is performed before restored controlfile, oracle will apply the incremental backup error-free files, and in this case, what would be the status of the data file in the control file.

  Why do you consider to retrieve the day before first and then in the restaurant of the controlfile will lead to problems. Please read my first post on this thread - I had clearly mentioned that you would not face problems if you go with the method of deployment.

  Here is a demo for you with force logging is disabled. For the first time the day before resuming and restored then the controlfile ensures:

  Primary: oraprim

  Standby: orastb

  Tablespace DataFile of MYTS is removed on primary:

  SYS @ oraprim > select force_logging in the database of v$.

  FORCE_LOGGING

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

  NO.

  Currently the tablespace is to have 2 data files.

  SYS @ oraprim > select file_name in dba_data_files where nom_tablespace = 'MYTS;

  FILE_NAME

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

  /U01/app/Oracle/oradata/oraprim/myts01.dbf

  /U01/app/Oracle/oradata/oraprim/myts02.dbf

  In standby mode, the tablespace is to have 2 data files:

  SYS @ orastb > select name from v$ datafile where ts #= 6;

  NAME

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

  /U01/app/Oracle/oradata/orastb/myts01.dbf

  /U01/app/Oracle/oradata/orastb/myts02.dbf

  Postponement of the day before on the primary log shipping

  SYS @ oraprim > alter system set log_archive_dest_state_3 = delay;

  Modified system.

  Dropped 1 MYTS datafile on the primary.

  SYS @ oraprim > alter tablespace myts drop datafile ' / u01/app/oracle/oradata/oraprim/myts02.dbf';

  Tablespace altered.

  Removed some archives to create a space.

  [oracle@ora12c-1 2016_01_05] $ rm - rf * 31 *.

  [oracle@ora12c-1 2016_01_05] $ ls - lrt

  13696 total

  -rw - r - 1 oracle oinstall 10534400 5 January 18:46 o1_mf_1_302_c8qjl3t7_.arc

  -rw - r - 1 oracle oinstall 2714624 5 January 18:47 o1_mf_1_303_c8qjmhpq_.arc

  -rw - r - 1 oracle oinstall 526336 5 January 18:49 o1_mf_1_304_c8qjp7sb_.arc

  -rw - r - 1 oracle oinstall 23552 5 January 18:49 o1_mf_1_305_c8qjpsmh_.arc

  -rw - r - 1 oracle oinstall 53760 5 January 18:50 o1_mf_1_306_c8qjsfqo_.arc

  -rw - r - 1 oracle oinstall 14336 Jan 5 18:51 o1_mf_1_307_c8qjt9rh_.arc

  -rw - r - 1 oracle oinstall 1024 5 January 18:53 o1_mf_1_309_c8qjxt4z_.arc

  -rw - r - 1 oracle oinstall 110592 5 January 18:53 o1_mf_1_308_c8qjxt34_.arc

  [oracle@ora12c-1 2016_01_05] $

  Current main MYTS data files:

  SYS @ oraprim > select file_name in dba_data_files where nom_tablespace = 'MYTS;

  FILE_NAME

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

  /U01/app/Oracle/oradata/oraprim/myts01.dbf

  Current data of MYTS standby files:

  SYS @ orastb > select name from v$ datafile where ts #= 6;

  NAME

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

  /U01/app/Oracle/oradata/orastb/myts01.dbf

  /U01/app/Oracle/oradata/orastb/myts02.dbf

  Gap is created:

  SYS @ orastb > select the process, status, sequence # v$ managed_standby;

  STATUS OF PROCESS SEQUENCE #.

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

  ARCH. CLOSING 319

  ARCH. CLOSING 311

  CONNECTED ARCH 0

  ARCH. CLOSING 310

  MRP0 WAIT_FOR_GAP 312

  RFS IDLE 0

  RFS IDLE 0

  RFS IDLE 0

  RFS IDLE 320

  9 selected lines.

  Backup incremental RMAN is taken elementary school.

  RMAN > incremental backup of the format of database of SNA 2686263 ' / u02/bkp/%d_inc_%U.bak';

  From backup 5 January 16

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

  the DISC 2 channel configuration is ignored

  the DISC 3 channel configuration is ignored

  configuration for DISK 4 channel is ignored

  allocated channel: ORA_DISK_1

  channel ORA_DISK_1: SID = 41 type device = DISK

  channel ORA_DISK_1: starting full datafile from backup set

  channel ORA_DISK_1: specifying datafile (s) in the backup set

  Enter a number of file datafile = 00001 name=/u01/app/oracle/oradata/oraprim/system01.dbf

  Enter a number of file datafile = name=/u01/app/oracle/oradata/oraprim/sysaux01.dbf 00003

  Enter a number of file datafile = name=/u01/app/oracle/oradata/oraprim/undotbs01.dbf 00004

  Enter a number of file datafile = name=/u01/app/oracle/oradata/oraprim/users01.dbf 00006

  Enter a number of file datafile = name=/u01/app/oracle/oradata/oraprim/myts01.dbf 00057

  channel ORA_DISK_1: starting total, 1-January 5, 16

  channel ORA_DISK_1: finished piece 1-January 5, 16

  piece handle=/u02/bkp/ORAPRIM_inc_42qqkmaq_1_1.bak tag = TAG20160105T190016 comment = NONE

  channel ORA_DISK_1: complete set of backups, time: 00:00:02

  Backup finished on 5 January 16

  Saved controlfile on primary:

  RMAN > backup current controlfile to Eve format ' / u02/bkp/ctl.ctl';

  Cancel recovery in standby mode:

  SYS @ orastb > alter database recover managed standby database cancel;

  Database altered.

  Recover the day before by using the above backup items

  RMAN > recover database noredo;

  From pick up to 5 January 16

  the DISC 2 channel configuration is ignored

  the DISC 3 channel configuration is ignored

  configuration for DISK 4 channel is ignored

  allocated channel: ORA_DISK_1

  channel ORA_DISK_1: SID = 26 type of device = DISK

  channel ORA_DISK_1: from additional data file from the restore backup set

  channel ORA_DISK_1: specifying datafile (s) to restore from backup set

  destination for the restoration of the data file 00001: /u01/app/oracle/oradata/orastb/system01.dbf

  destination for the restoration of the data file 00003: /u01/app/oracle/oradata/orastb/sysaux01.dbf

  destination for the restoration of the data file 00004: /u01/app/oracle/oradata/orastb/undotbs01.dbf

  destination for the restoration of the data file 00006: /u01/app/oracle/oradata/orastb/users01.dbf

  destination for the restoration of the data file 00057: /u01/app/oracle/oradata/orastb/myts01.dbf

  channel ORA_DISK_1: backup /u02/bkp/ORAPRIM_inc_3uqqkma0_1_1.bak piece reading

  channel ORA_DISK_1: room handle=/u02/bkp/ORAPRIM_inc_3uqqkma0_1_1.bak tag = TAG20160105T190016

  channel ORA_DISK_1: restored the backup part 1

  channel ORA_DISK_1: restore complete, duration: 00:00:01

  Finished recover to 5 January 16

  Restored the controlfile and mounted the day before:

  RMAN > shutdown immediate

  dismounted database

  Instance Oracle to close

  RMAN > startup nomount

  connected to the database target (not started)

  Oracle instance started

  Total System Global Area 939495424 bytes

  Bytes of size 2295080 fixed

  348130008 variable size bytes

  583008256 of database buffers bytes

  Redo buffers 6062080 bytes

  RMAN > restore controlfile eve of ' / u02/ctl.ctl ';

  From 5 January 16 restore

  allocated channel: ORA_DISK_1

  channel ORA_DISK_1: SID = 20 type of device = DISK

  channel ORA_DISK_1: restore the control file

  channel ORA_DISK_1: restore complete, duration: 00:00:01

  output file name=/u01/app/oracle/oradata/orastb/control01.ctl

  output file name=/u01/app/oracle/fast_recovery_area/orastb/control02.ctl

  Finished restore at 5 January 16

  RMAN > change the editing of the database;

  Statement processed

  output channel: ORA_DISK_1

  Now the data file does not exist on the standby mode:

  SYS @ orastb > alter database recover managed standby database disconnect;

  Database altered.

  SYS @ orastb > select the process, status, sequence # v$ managed_standby;

  STATUS OF PROCESS SEQUENCE #.

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

  CONNECTED ARCH 0

  CONNECTED ARCH 0

  CONNECTED ARCH 0

  ARCH. CLOSING 329

  RFS IDLE 0

  RFS IDLE 330

  RFS IDLE 0

  MRP0 APPLYING_LOG 330

  8 selected lines.

  SYS @ orastb > select name from v$ datafile where ts #= 6;

  NAME

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

  /U01/app/Oracle/oradata/orastb/myts01.dbf

  Hope that gives you a clear picture. You can use this to roll forward day before using the SNA roll forward Eve physical database using RMAN incremental backup | Shivananda Rao

  -Jonathan Rolland

• Weird behavior of our standby database active Data Guard

  Hi all

  11 GR 2

  Rhel6.5

  I'm testing an active dataguard for our database awaiting.

  I've activated active dataguard, using the following command:

  Pending:

  ==========

  1. start-up open read-only.

  2 Alter database recover standby database managed disconnect from the session;

  SQL > select status instance_name, database_role, open_mode from v$ database, v $instance;

  STATUS INSTANCE_NAME OPEN_MODE DATABASE_ROLE

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

  OPEN PHYSICS READ UAT SHALL ONLY APPLY

  Primary:

  ==========

  1. go to user APPS/APPS and create the TEST table.

  2. then connect / as sysdba and alter system switch logfile;

  3. check that log is transported.

  Pending:

  ==========

  1. open a session is verified and applied.

  2. connect apps/apps and desc the TEST table.

  ERROR: can't do everything and everything is FROZEN?

  I can't select the test as well as all the other tables table.

  Please help what's happening...

  Thank you very much

  JC

  You may need the parameter sql_trace set to true for the level of database tracking.

  But I suspect you may be hitting a bug, suggest you to trigger a SR with Oracle support for more information on the crash of Eve.

  -Shivananada Rao

• Block corruption on the physical Standby database

  Hi all

  Operating system: HP Unix

  DB: 10.2.0.4

  We are facing corruption block on our database of physical intelligence. The same has been detected using commands below and several blocks were found to be corrupt.

  RMAN > backup validate check the logic of database;

  SQL > select * from v$ database_block_corruption

  As it is a basic data watch no backup is present, pulling the command below did not help

  RMAN > list of corruption block restoration;

  I think taking the incremental backup of the PR and the same application on DR, y at - it another way to eliminate corruption said?

  Kind regards

  Sphinx

  You can check below link if corruption block results nologging, there is a thread already with the question.

  Block corruption on the standby database

  10.5.2 steps of recovery for databases physical standby

  Data protection scenarios

• Enterprise Manager on the logical standby database

  Hello

  I just put in place a system of logical standby database.

  Is it possible to install the Manager of the business on the logical database?
  Since it works in "read only mode", I'm not sure about this

  Concerning

  Christian

  Enterprise Manager can be used to monitor and manage backup of database, logical and physical targets.

  See you soon,.
  Brian

• Upgrade to 11.2.0.4 with the physics of the standby database

  Dear gurus,

  
  We have the obligation to upgrade databases 11.2.0.1 existing 11.2.0.4 and 11.2.0.2 to 11.2.0.4 running on AIX boxes. We have physical databases of Eve configured for these databases of different version.

  During the preparation of the documentation for upgrade, we observed that FORCE_LOGGING is disabled for the production databases and observed, there are objects along 350 + with journaling = No. and logging = NULL and patterns are SYS, SYSMAN, APEX_030200, OLAPSYS, XDB, SYSTEM, OIMDBUSER, MDSYS, EXFSYS, WMSYS, ORDDATA, PERFSTAT.

  My query:

  I can still proceed with the upgrade still under the document indicated for "upgrading a database with a physical Standby database in place" without you connect the data dictionary objects will be not be updated pending database.

  Can you please let me know your suggestions on this please?

  Kind regards

  Kumar

  Hello;

  Quote:

  "Keep the database in LOGGING mode FORCE as long as the backup database is necessary."

  Of

  Oracle® DataGuard of Concepts and Administration 11 g Release 2 (11.2) E10700-02

  I think I FORCE turn on CONNECTING to the primary database and rebuild the eve before doing the upgrade.

  Best regards

  mseberg

• Standby Database - No. Enterprise Manager - 11g so what jobs?

  Hello

  So I implemented data guard for our production of 11g database.  I used the SQL method.   No control of the broker, no cloud or the grid.

  The data is synchronized with our production database.   But - if I have to failover to the standby database, there is no enterprise manager to manage it.  I have several scheduled tasks in our production database. (These jobs involve the execution of stored procedures, SQL, etc.).  Of course these jobs wouldn't if we were using the database pending because there is no EM for it.

  Add to this the fact that the company where we license Oracle since (we're a college) does not yet support 12 c.  If I ran 12 c, we are on our own until they do, if there are problems.

  So, if I ever use our database of Eve, what jobs that are not running? I know that I could perform them manually, or I might get them to run with SQL Scripts using Windows batch files, etc..  Essentially reproducing jobs EM with Windows bat files.  (I'm already back up the database ensures that).

  What is the right way to go about this? Install control cloud 12 c on a server and then to administer my database sleep with her? I guess the 12 c cloud control can administer an 11g database?   For those who have done this, have you installed the control server to cloud 12 c on its own server?

  We manage our server under Windows 2008 R2.

  Any contribution is appreciated.

  Thank you

  Fix. They will work in Main Mode. Manages the "SET_ATTRIBUTE" 'DBMS_SCHEDULER' if value "PRIMARY".

  So if you make a hole or failover mode of the database changes and your work are managed.

  EM jobs are not the same thing as that.  DBMS_SCHEDULER is stored in each database.

  There is a forum here also DBMS_SCHEDULER with tons of information.

  Best regards

  mseberg

• Effects of the opening of a primary database in resetlogs on the standby database

  Hi all

  Operating system: Solaris

  DB: 11 gR 2

  Can anyone throw some light below the explanation is given in case of recovery through the OPEN RESETLOGS Statement oracle documentation

  If the database pending...	Then...	Perform these steps...
  Not asked to redo data beyond the new resetlogs SCN (after the start of the new branch of data recovery)	Redo apply automatically takes the new branch of the roll forward.	No manual intervention is required. The MRP automatically resynchronizes the database pending with the new branch of data recovery.

  Here is the link of the source:

  Manage a database of physical standby

  Kind regards

  Just to give a concrete example, I did a test on one of my VM boxes. The database currently shows:

  SQL > select sequence #, the journal of v status $;

  SEQUENCE # STATUS

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

  34 ACTIVE

  CURRENT 35

  ACTIVE 33

  While on the eve, I stopped the redo apply so the standby status is:

  SQL > select sequence #, used from v$ archived_log;

  SEQUENCE # APPLIED

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

  YES 30

  31 YES

  32 YES

  33 NO.

  34 NO.

  The database ensures in a few newspapers behind the primary.

  On the primary, I moved the journal a few sequences, close, the bootable media and restored and recovered 37 sequence:

  RMAN > run

  2 > {}

  3 > restore database;

  4 > up 37 sequence;

  5 > restore database;

  6 > alter database open resetlogs;

  {7 >}

  During the open resetlogs operation, I have to tail the log of alerts on the standby database and the following output shown:

  RFS [11]: identified the type of database such as 'physical' standby: customer is ARCH pid 17192

  RFS [11]: new branch archives REDO: 844006029 current: 843649185

  RFS [11]: Journal selected 102 for thread 1 1 dbid-204899919 branch of the 844006029 sequence

  RFS [11]: new Branch (resetlogs_id) of archive REDO: before 844006029: 843649185

  RFS [11]: ID of Activation of archives: current 0xf3d44942: 0xf3cf5ac3

  RFS [11]: effect of primary database OPEN RESETLOGS

  RFS [11]: entry of Incarnation added to Branch (resetlogs_id): 844006029 (ORCL11PS)

  Fri Apr 04 14:07:39 2014

  Definition of embodiment of recovery target 2

  Fri Apr 04 14:07:39 2014

  Archived journal 21 additional for each sequence 1 1 0xf3d44942 dest ID thread entry 1:

  So as you can see, the log shows the standby detects the resetlogs on the primary operation and the new branch of the roll forward and received the next archivelog with sequence 1.

  Audit on the eve, it shows the status following the archivelogs:

  SEQUENCE # APPLIED

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

  31 YES

  32 YES

  33 NO.

  34 NO.

  35 NO.

  36 NO.

  37 NO.

  38 NO.

  1 NO.

  2 NO.

  And after restart the managed recovery process, it now shows:

  SEQUENCE # APPLIED

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

  31 YES

  YES 30

  YES 19

  YES 33

  34 YES

  35 YES

  YES 36

  37 NO.

  38 NO.

  1 YES

  2 YES

  Archivelogs with sequence 37 and 38 were not implemented because of the CAMILLE on the main sequence until (but not including!) 37 and then properly applied the next archivelogs of the new branch of the roll forward, with sequence 1 and 2.

• Steps to upgrade spirit RAC Standby Database?

  Hi all

  I RAC environment with 8 knots (4 Linux) I have a knot like physical standby for this CAR.

  My oracle is 10.2.0.3, and I want to update 10.2.0.5

  Could you advice I do not like, when I googled I found that I must begin by Clusterware before then?

  Any recommendation?

  Thanks in advance.

  Hello

  If you follow the second link I posted, all necessary measures are there, even if you have some CARS, it is explained here. Take a look at chapter "B.2 upgrade Oracle database with a physical Standby Database in Place", and if you have any questions post here.

  ARM

• GoldenGate to replicate physical of the standby database

  Friends,

  I don't have an answer instead of data guard

  Could we use oracle Portal gold to replicate a physical custody ensures data in a new logical basis?

  Or we need to replicate keeps the primary database data in a new logical basis?

  Thank you

  newdba

  Use the extract parameter TRANLOGOPTIONS with the ARCHIVEDLOGONLY option. This

  force option extracts for ALO mode against a primary or logical standby

  database, as determined by the PRIMARY or STANDBY LOGIC value in the db_role

  column in the view v$ database. The default is to read newspapers online.

  TRANLOGOPTIONS with ARCHIVEDLOGONLY is not necessary if you use the ALO mode against a

  standby database physical, as determined by the PHYSICAL INTELLIGENCE value to the

  db_role column of v database $. Extract works automatically in ALO mode if it

  detects that the database is a physical standby.

• Destination different archivelog on the physics of the standby database

  Hello

  Can I set different archivelog destination for the physics of dual standby database? (Because of space issues) How can I do?

  For example, on the site main archivelogs reside in/u01/ORCL/archivelog and I want on phy. side Eve archive dest. under/u08/ORCL/archivelog.

  You can also give LOG_ARCHIVE_DEST_1 in file init Eve, so whenever you start sleep/auxiliary instance automatically done dest_1 refers to/u08/orcl (whereever you want).  So you can have destination archive anywhere but must have the appropriate permissions and location should be available.

  If you want to set a destination, then again you can use the "ALTERNATE" sort clause only when the primary location unavailable or unable to archive, and then, of course, he wrote in the other location you have specified a pfile.

  You can check this

  http://docs.Oracle.com/CD/B28359_01/server.111/b28294/log_arch_dest_param.htm#i91817

• How to remove the configuration of logical standby database cleanly

  Hello

  We are on the BSG with 11.2.0.3 version of DB. For unknown reasons, we would like to recreate the logic of the standby database and for this I want to cleanly remove/uninstall/remove LOGIC of DATABASE of the EVE of the DATA GUARD configuration that we have.

  Setup of the DG has already 1 PHYSICAL STANDBY DATABASE that works very well. PRIM, PHYSICAL and LOGIC are all on different HOSTS. Could you please guide or we suggest exact MOS Doc id in this regard? I found an MOS Doc id which is close enough, but its steps include dg configuration completely deleting what I don't want. Only the logical Standby database must be delete itself so that it can be installed again properly.

  We use the CONTROL GRID and DATA GUARD BROKER.

  Bundle of thanks in advance.

  Best regards

  Hello

  Thank you very much.

  What I have is:

  -DROP DATABASE (from logical database in standby)

  -asmcmd > and removed the rest of the orphaned files related to the logical database.

  -DGMGRL > remove the database logicladb; one

  -Grid control > removed from here

  -deleted the database logical PRIMARY related to logic, for example, log_archive_config.

  Other steps > ID note (Doc ID 733794.1) about the LOGIC of STANDBY DATABASE (I think that MINING regarding)

  She's.

  Best regards

• How standby database works

  Hello!!

  I created the database (testcat) pending for the primary database (test) using the command RMAN duplicate on the same server (windows XP) on Oracle 11.2. I know how to create the standby database but I don't know how and when Eve database works. I checked the file init.ora backup of database that contains all parameters prefixed to *. as follows

  * .db_create_file_dest = "F:\app\Administrator\oradata".

  * .db_domain = "

  * .db_recovery_file_dest = "F:\app\Administrator\flash_recovery_area".

  * .db_recovery_file_dest_size = 10737418240

  * .db_unique_name = "testcat".

  *. Db_name = 'test '.

  * .control_files = 'D:\APP\ORACLE\ORADATA\TESTCAT\CONTROLFILE\CONTROL_STAND1. CTL "

  While the primary database init.ora file contains entries like

  db_create_file_dest = F:\app\Administrator\oradata

  db_recovery_file_dest = F:\app\Administrator\flash_recovery_area

  db_recovery_file_dest_size = 4039114752

  control_files = 'F:\APP\ADMINISTRATOR\ORADATA\TEST\CONTROLFILE\O1_MF_8TXW6QN0_. CTL.

  So I want to know is

  1. What IS the difference between the settings that start with. * and start without. *

  2. can I set db_create_file_dest parameter in init.ora backup of database to another location.

  3. how to make journal apply to the standby database when I run ALTER DATABASE RECOVER... command

  4. where log files archived on eve of the databases will be stored?

  Hello

  You mean there are two types of transport for recovery logs.

  ((1) ASYNC 2) SYNC.

  1. If the transport type is ASYNC what background process will perform redo transport?

  LNS background process

  2. If the transport type is SYNC then what background process will perform redo transport?

  If version<11.2.0.3 then="" lns="" ,="" else="">

  3. is there a difference between ASYNC and SYNC?

  SYNC required for the Protection of Max and MAX availability Modes, ASYNC held a Max performance.

  4. According to your first post, RFS receives (which exist in standby mode) repeat primary and MRP applies it again then what is the role of SRL, LGWR - LNS, GAP?

  SRL required for demand in time real process and Max Protection and availability modes Max.

  When the GAP occurs, not transported logs archived corrupted or deleted on the side of priamry.

  Concerning

  Mr. Mahir Quluzade

  p.s. Please read: Data Guard - content

• Source Standby Database ARCHIVELOG directory

  Hi guys

  Yesterday, I created a database of pending and everything works correctly.  However, I need to make some adjustments, and one of these is the directory that the standby database expects the archivelogs be.

  I found that the archivelogs have been shipped to $ORACLE_HOME/dbs and named arch*.arc.  Interestingly, a switch of newspaper delivered the archivelog less the 'arc' in front and now all archivelogs did not have this format.

  I moved the archivelogs to the correct location and their fame.  I was able to set the correct location using standby_archive_dest and can see the archivelogs shipped to there. In addition, v$ archived_log shows the path and the file name.

  The problem I have is that when I come to apply archivelogs that he still seems to think they should be in $ORACLE_HOME/dbs and named with 'arch' in front.  Can someone tell me please what setting I need to change to indicate the path and file name to use when you apply the archivelogs in oracle?

  Thank you

  Simon

  your log_archive_dest_1 setting has a change of production of the eve db_unique_name db_unique_name = "TAPSDR".

• Archived not getting applied to the standby database.

  Hello
  
  I turned the parameter standby_file_management to manual and since I created 3 primary data file, but they are not applied to the standby database.
  I turned on the Auto setting and started the MRP process but still not able to apply archive.
  Version Oracle 10.2.0.5
  
  
  Please suggest,
  Amit Sharma

  Hello

  Your problem is that the MRP standby automatically when a data file is added on the primary database. The reason would be that the parameter STANDBY_FILE_MANAGEMENT is set to MANUAL on the standby database.

  Please refer to this http://shivanandarao-oracle.com/2012/04/02/managed-recovery-process-mrp-terminates-on-standby-database-upon-adding-datafile-on-the-primary-database/

  It will be useful.

  Kind regards
  Shivananda