Error on duplicated to 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

• ORA-01403: no data found on the LOGICAL standby database

  Hello
  
  Logical question of Eve:
  Enterprise Edition Oracle 10.2.0.2.
  
  M work waiting LOGIC for 1 year but still i have not had this...
  I m not be countinuously no data foud errror on the logic of the standby database.
  
  I found the table causing the problem (db_logstdby_events) and jumped this table and table instantiated using the package bwlow:
  
  exec dbms_logstdby.instantiate_table (...)
  
  but when I start to apply the logical waiting process it gives again some were found for the new data table:
  
  I even tried to instantiate the table to EXPORT/IMPORT assistance over time, but the same problem same deal with.
  
  As much as I knew abt the error that is:
  Table1:
  ID
  10
  20
  30
  
  
  Now if sql apply processes on standby logic tent performs the operation of (for example) updated as below
  
  Update table1 set id = 100 where id = 50;
  
  above request will not be completed cos he'll never find 50 values which is not in the table. That is why this error coming...
  
  
  Now my concern is... no user didn't dare change/make of such changes on the logic ensures. So if there is no change in the tables, then apply it sqll should get all the values to be needded for an update...
  
  watingggg guyssss...

  Hello;

  How do you know that the database pending is compatible with the primary?

  Are there opportunities has one or several tables have been created on the eve before they were created on the primary? (If Yes check in DBMS_LOGSTDBY. INSTANTIATE_TABLE)

  Or jump and re-instantiate the table.

  Example of

  EXEC DBMS_LOGSTDBY.SKIP('DML','EMPLOYEES','%');
  
  EXECUTE DBMS_LOGSTDBY.INSTANTIATE_TABLE  ('YOUR_USER', 'EMPLOYEES', 'YOUR_DBLINK');
  

  Best regards

  mseberg

• Error recovery in the backup database

  I got the following error to the standby database. No idea what this means and how can I get it without a full clone.
  
  
  Kills Aug 14 17:23:32 2012
  Recovery Media Log /spdata07/SPDB/fra/FINSP_GDRSD_LISTENER_NL/archivelog/2012_08_10/o1_mf_1_11131_82bmbgvs_.arc
  Kills Aug 14 17:23:32 2012
  Errors in the /spdata07/ora_11202/product/dbhome/rdbms/log/spdb_pr00_24915.trc file:
  [ORA-00600: internal error code, arguments: [2619], [11131], [], [], [], [], [], [], [], [], []]
  Completed: alter the managed standby database recovery database using the current log file disconnect from the session
  Use ADRCI or Support established for the packaging of the incident.
  See Note 411,1 to My Oracle Support to error and packaging details.
  Errors with /spdata07/SPDB/fra/FINSP_GDRSD_LISTENER_NL/archivelog/2012_08_10/o1_mf_1_11131_82bmbgvs_.arc newspaper
  MRP0: Background Media Recovery terminated with error 600
  Kills Aug 14 17:23:34 2012
  Errors in the /spdata07/ora_11202/product/dbhome/rdbms/log/spdb_pr00_24915.trc file:
  [ORA-00600: internal error code, arguments: [2619], [11131], [], [], [], [], [], [], [], [], []]
  Managed Standby recovery not using real time applies
  Recovery interrupted!
  
  
  spdb_pr00_24915.TRC trace file:
  
  
  
  
  Has started the recovery of parallel media
  krsh.c 17:23:31.503 4265 2012-08-14
  Managed Standby recovery to apply in real time
  Dumping table incarnation of database:
  RESETLOGS 0 Yvert and time: 22/05/2012 0x0000.00000001 20:55:23
  Incarnation of recovery targets = 1, activation ID =-328156793
  The flow buffer limit = 55611 min (50% x 111222, 100000)
  
  2012-08-14 17:23:32.106
  Start the recovery to the thread 1 ckpt SNA 26430758 logseq 11131 block 2
  Initial size of the buffers: read 1024K, K 820 overflow, change 805K
  
  2012-08-14 17:23:32.132
  Add a Media Recovery redo thread 1
  
  2012-08-14 17:23:32.249
  Recovery Media Log /spdata07/SPDB/fra/FINSP_GDRSD_LISTENER_NL/archivelog/2012_08_10/o1_mf_1_11131_82bmbgvs_.arc
  = Critical error (any incident) dump (ORA 600 [2619]) =.
  
  2012-08-14 17:23:32.315
  dbkedDefDump(): from the default crash dumps (flags = 0 x 0, level = 3, mask = 0 x 0)
  -Error stack dump-
  [ORA-00600: internal error code, arguments: [2619], [11131], [], [], [], [], [], [], [], [], []]
  -SQL statement (none).
  Run SQL information not available - no cursor.
  -Call trace stack memory-

  ORA-00600 = open an SR to MyOracleSupport.

• Newspapers do not apply to Standby Database

  I'm scared, I'm back.
  
  I now a primary database and an expectation of database and logs are shipped but not applied. Did some research and I got to the point where in my alert log I find the following when I try to start MRP:
  Fri Jun 29 15:03:40 2012
  modify the recovery of database managed standby database disconnect from the session
  Try to start the standby recovery process thoroughly managed (SAPDS)
  Fri Jun 29 15:03:40 2012
  MRP0 started with pid = 29, OS id = 23272
  MRP0: Background Managed Standby recovery process started (SAPDS)
  has started the process of logmerger
  Fri Jun 29 15:03:45 2012
  Managed Standby recovery not using real time applies
  Reading file ' / var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf' header (fno 2) failed with ORA-01206
  Data file header 2 replay failed with ORA-01206
  MRP0: Background Media Recovery terminated with error 1110
  Errors in the /var/hpsrp/drforp03/oradata/u04/SAPDS/admin/diag/rdbms/drfsapds/SAPDS/trace/SAPDS_pr00_23308.trc file:
  ORA-01110: data file 2: ' / var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
  ORA-01122: database file 2 failed verification check
  ORA-01110: data file 2: ' / var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
  ORA-01206: the file is not part of this database - bad database id
  Recovery slave PR00 is previously released with the exception of 1110
  Errors in the /var/hpsrp/drforp03/oradata/u04/SAPDS/admin/diag/rdbms/drfsapds/SAPDS/trace/SAPDS_mrp0_23272.trc file:
  ORA-01110: data file 2: ' / var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
  ORA-01122: database file 2 failed verification check
  ORA-01110: data file 2: ' / var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf'
  ORA-01206: the file is not part of this database - bad database id
  MRP0: Stopping the process background Media Recovery (SAPDS)
  Completed: change the recovery of database managed standby database disconnect from the session
  
  Therefore, my question is how can I get out of this and get my logs to apply pending?

  Hello again;

  Do you think if I tried to repeat the duplicate?

  Yes I think you should do this.

  Give me a few minutes and I'll review my Word document and provide here an overview step by step as insurance.

  I always clean the day before before trying another dup

  OVERVIEW

  Step 1 - password file FRO sleep - the primary copy and rename
  Step 2 - On the remote server Directory Structure - Make sure noting is missing
  Step 3 - Oracle Net Setup - entered for the CLONE in your TNSNAMES file. ORA on both servers
  Step 4 - Adding SID_LIST_LISTENER (guess named listener LISTENER)
  Step 5 - located in listener.ora and sqlnet.ora both servers wait times
  Step 6 - settings of the auxiliary Instance initialization file
  Step 7 - Set SID of the auxiliary Instance
  Step 8 - create a SPFILE to the new database using a file with the INIT parameters pfile
  Step 9 - shutdown and startup nomount on new Spfile (auxiliary Instance)
  Step 10 - Start RMAN and run the command DUPLICATE

  SID_LIST_LISTENER example of mine

  SID_LIST_LISTENER =
     (SID_LIST =
         (SID_DESC =
         (SID_NAME = PLSExtProc)
         (ORACLE_HOME = /u01/app/oracle/product/11.2.0.2)
         (PROGRAM = extproc)
       )
         (SID_DESC =
         (global_dbname = CLONE.hostname)
         (ORACLE_HOME = /u01/app/oracle/product/11.2.0.2)
         (sid_name = CLONE)
     )
  )
  

  Avoid delays

  Add these to both servers
  
  To listener.ora
  INBOUND_CONNECT_TIMEOUT_ = 120
  
  To sqlnet.ora
  SQLNET.INBOUND_CONNECT_TIMEOUT = 120
  
  Then stop and start the listener.
  

  RMAN

  $ORACLE_HOME/bin/rman target=sys/@primary auxiliary=sys/@standby

  Connect should return something like this

  connected to target database: RECOVER9 (DBID=3806912436)
  connected to auxiliary database: CLONE (not mounted)
  

  RMAN > current database of target duplicate for the eve of the database NOFILENAMECHECK.

  INIT Extras

  In order to avoid the ORA-09925 do of course the PFILE core_dump_dest value and audit_file_dest a file

  Best regards

  mseberg

  Published by: mseberg on June 29, 2012 11:12

• RMAN duplicate for standby database failed

  Hello
  I have try several times and for one reason, the auxialiary database finished just as it goes up the auxiliary instance.
  Target database in double check to stanby with the following error. Primary and auxiliary bodies
  Run 11.2.0.2 and are on the same platform of Solaris/patches. Everyone ran in that issue and solve it?
  
  RMAN target / catalog user@catalog
  startup nomount
  Run {}
  allocate auxiliary channel tp1 type sbt_tape;
  allocate auxiliary channel tp2 type sbt_tape;
  target database double standby nofilenamecheck;
  }
  :
  :
  :
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-00601: fatal error in the Recovery Manager
  RMAN-03004: fatal error when executing command
  RMAN-04006: auxiliary database error: ORA-01092: ORACLE terminated instance. Disconnection forced
  RMAN-03002: failure of the command duplicate Db at the 15:28:52 01/02/2012
  RMAN-05501: abandonment of duplicate target database
  RMAN-03015: an error has occurred in the script stored memory Script
  RMAN-03009: failure of switch control on channel clone_default at the 15:28:52 01/02/2012
  ORA-03113: end of file on communication channel

  You have error ORA-7445. I would ask allows you to check the MOS document that said Mseberg.

  Also, do not have the DATA01 on the standby database if your wait is a database not ASM. But you must give the path in the db_file_name_convert and log_file_name_convert on the eve pfile/spfile database

  1 question: is your watch set up database to be on ASM or not?

  See document MOS * no not guide to create physical standby on Normal file system for ASM primary with RMAN [838828.1 ID] * If your principal is on ASM and intelligence on the file system

  See document MOS * Step By Step Guide on creating physical standby with RMAN duplicate in ASM Filesystem for primary ASM [837102.1 ID] * If your primary and the day before are on ASM

  Published by: srp on February 3, 2012 03:49

• ORA-16086: standby database does not available? Help me

  Hi all
  I use logic ensures db,.
  my database is very well that there is an error: ORA-16086: does not log pending available files, standby database contain
  It's log_archive_dest_2 on the primary database: log_archive_dest_2 = "service = LGWR SYNC dgora SAY valid_for =(online_logfiles,primary_role) db_unique_name = dgora'"
  
  even then, oder data still are transported from primary eve db db and then applied on the eve of the database.
  I run the command: select group #, the journal of v status $; -> the result is normal.
  
  can someone help with this problem?
  
  I thank you,

  They are a bit like the pads to do it again.

  It will speed up to apply, rocking and tilting.

  Standby Redo Logs are similar to online redo logs and the difference between the two is that standby Redo Log is used to store restore data by progress coming from another (primary) database.

  Standby redo logs are used only when the database_role is in sleep mode, it is recommended to add in the primary also so that they can be used on the evolution of the role, however, in the normal course work standby redo logs will be used at all on the primary.

  Using groups of waiting for redo log depends on the rate of generation of redo, you can see only 2 newspapers roll forward pending use even if you have 4 groups of waiting for redo log, when the production of roll forward rate is lower.

  It is recommended to have a group of newspapers of recovery sleep when redo production rates are high and all of the current log roll forward pending use.

  Best regards

  mseberg

  Add correct you issue?

  Published by: mseberg on July 20, 2011 08:17

• ORA-38500 standby database physical not started

  hiiii,
  
  When I executed the command to the physical server to the standby database.
  It gives the error:
  
  
  
  To start real-time applies:
  
  SQL > ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
  2 > USING the file LOG CURRENT;
  
  
  Error on line 1:
  
  ORA: 38500 using current logfile option not available without support.
  
  Please help me how can I start physics of the standby database
  
  Concerning
  Vaibhav Dixit

  Vaibhav Dixit says:
  and now what to do to start holding the database

  What do you meen under there? Standby DB to apply newspapers in the State Assembly, is not open.
  Or you need to activate?

• How to open a physical standby database "Manual" in read/write mode

  Hello
  
  I am running Oracle Database 10g Release 10.2.0.3.0 - 64 bit Standard Edition Production on Linux version 2.6.9 - 42.0.8.ELsmp ([email protected]) (version gcc 3.4.6 20060404 (Red Hat 3.4.6 - 3))
  
  I created a physical standby database, but since I am running Standard Edition, I don't use the features in DataGuard. I use the utility rsync to copy on the data pending archivelogs, and I periodically applied to the standby database.
  
  The standby database is started in this way:
  
  startup nomount pfile='/u01/oradata/orcl/initorcl.stdby';
  ALTER database base_de_donnees eve of Mount;
  
  Everything works perfectly, I can "open database in read-only alter" and then I can make selects in the tables to confirm that everything is up-to-date.
  
  The thing is, if I stop the database and then perform the boot simply:
  
  stop immediately;
  start-up;
  
  The database opens with an error message, but it is always in read-only mode...
  
  I read that the default behavior for a database ensure must open read-only, as I am experiencing, but I would like to know what is the right way to open it in read-write mode correctly (I understand that after this, my watch will not standby more and I need to recreate my database pending).
  
  Thank you
  
  Carpet

  Try: -.

  ALTER database activate standby database;

  This should open read-write (you will not be able to recover thereafter)

• Problem with data hold creating a Physical Standby Database turorial

  There is a tutorial for creating a Data Guard Physical Standby Database:
  http://www.Oracle.com/technology/OBE/11gr1_db/HA/DataGuard/physstby/physstdby.htm
  
  I tried to install it on two servers. One for a primary database (deuxieme for the physical standby.
  I have the error on creating C. the database of watch on the #6 action network:
  
  «On the rescue system, set the ORACLE_SID to your < SID physical standby > environment variable (i.e. orclsby1) and start the instance in NOMOUNT mode with the text initialization parameter file.»
  
  When I try to connect to the instance that is idle, there is an error pops up:
  
  C:\ > sqlplus / as sysdba
  
  SQL * more: version 11.1.0.7.0 - Production Thursday, May 21, 16:28:10 2009
  
  Copyright (c) 1982, 2008, Oracle. All rights reserved.
  
  ERROR:
  ORA-12560: TNS:protocol adapter error
  
  I ' v checked listener, and it is managed. There is no database service because there is still no database.
  
  The question is did some data installed a guard configuration using this tutorial? Are there errors in there? What should I do to complete the installation?

  On Windhose for any service must have been created using the oradim command.
  Oracle tutorials are usually centered on Unix, because Windhose is an odd man out, so they do not discuss.
  "Please do the needful" and create the service before the beginning of the instance in nomount mode

  Tip: oradim is documented and has a help = clause of y.

  IIRC there is an option in control database (in the part of the interview) that automates everything.

  ----------------
  Sybrand Bakker
  Senior Oracle DBA

  Experts: those who read documentation

• problem in physical recovery standby database (Data Guard) by rman

  Hi all
  
  I created a physical database Eve, I want to make a backup of it by rman and when I lose datafile is that I can restore, backup and restore is fine, but in recovery I encounter a problem
  scenarios is followed
  
  1. in rman, I create a backup of database Eve by this command:
  backup database more archivelog delete all entries;
  
  2. I run this command in rman to recover standby database
  Run {}
  2 > set up what SNA 1392701.
  3 > restore database;
  4 > restore database;
  {5 >}
  (1392701 is extracted from this query "SELECT MAX (NEXT_CHANGE #) + 1 UNTIL_SCN FROM V$ LOG_HISTORY LH ')
  V$ DATABASE DB WHERE LH. RESETLOGS_CHANGE #= DB. RESETLOGS_CHANGE # AND LH. RESETLOGS_TIME =
  DB. RESETLOGS_TIME; (""http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rman.htm")
  
  but result RMAN is like this:
  executing command: SET until clause
  
  
  From restoration to 13 December 08
  using channel ORA_DISK_1
  channel ORA_DISK_1: from datafile backupset restoration
  channel ORA_DISK_1: specifying datafile (s) to restore from
  backup set
  restoring datafile 00001 to /u01/app/oracle/oradata/sari/system01.dbf
  restoring datafile 00002 to /u01/app/oracle/oradata/sari/undotbs01.dbf
  restoring datafile 00003 to /u01/app/oracle/oradata/sari/sysaux01.dbf
  restoring datafile 00004 in /u01/app/oracle/oradata/sari/users01.dbf
  restoring datafile 00005 to /u01/app/oracle/oradata/sari/example01.dbf
  restoring datafile to /u01/app/oracle/oradata/sari/users02.dbf 00006
  channel ORA_DISK_1: reading of the backup/home/oracle/backup/0ek24dt4_1_1 element
  channel ORA_DISK_1: restored the backup part 1
  piece handle = / home/oracle/backup/0ek24dt4_1_1
  tag = TAG20081213T042506
  channel ORA_DISK_1: restore complete, duration: 00:01:07
  Finished restoration to 13 December 08
  From back to 13 December 08
  using channel ORA_DISK_1
  starting media recovery
  archive log thread 1 116 sequence is already on the disk that the file /u01/app/oracle/oradata/archive/1_116_666786084.arc
  archive log thread 1 sequence 117 is already on the disk that the file /u01/app/oracle/oradata/archive/1_117_666786084.arc
  Archive newspaper filename=/u01/app/oracle/oradata/archive/1_116_666786084.arc thread = 1 sequence = 116
  Archive newspaper filename=/u01/app/oracle/oradata/archive/1_117_666786084.arc thread = 1 sequence = 117
  Cannot find the log archiving
  archive log thread = 1 sequence = 118
  RMAN-03002: failure of the command recover to 2008-12-13 05:14:13
  RMAN-06054: recovery of media asking unknown journal: thread 1
  SEQ 118 lowscn 1392700
  
  
  3. then I refuse 1392701 to 1392700 and I run this command
  
  Run {}
  2 > set up what SNA 1392700.
  3 > restore database;
  4 > restore database;
  {5 >}
  executing command: SET until clause
  From restoration to 13 December 08
  using channel ORA_DISK_1
  channel ORA_DISK_1: from datafile backupset restoration
  channel ORA_DISK_1: specifying datafile (s) to restore from
  backup set
  restoring datafile 00001 to /u01/app/oracle/oradata/sari/system01.dbf
  restoring datafile 00002 to /u01/app/oracle/oradata/sari/undotbs01.dbf
  restoring datafile 00003 to /u01/app/oracle/oradata/sari/sysaux01.dbf
  restoring datafile 00004 in /u01/app/oracle/oradata/sari/users01.dbf
  
  restoring datafile 00005 to /u01/app/oracle/oradata/sari/example01.dbf
  restoring datafile to /u01/app/oracle/oradata/sari/users02.dbf 00006
  channel ORA_DISK_1: reading of the backup/home/oracle/backup/0ek24dt4_1_1 element
  channel ORA_DISK_1: restored the backup part 1
  total, handle = / home/oracle/backup/0ek24dt4_1_1 tag = TAG20081213T042506
  channel ORA_DISK_1: restore complete, duration: 00:01:08
  Finished restoration to 13 December 08
  From back to 13 December 08
  using channel ORA_DISK_1
  
  starting media recovery
  archive log thread 1 116 sequence is already on record as
  file /u01/app/oracle/oradata/archive/1_116_666786084.arc
  
  archive log thread 1 sequence 117 is already on record as
  file /u01/app/oracle/oradata/archive/1_117_666786084.arc
  
  archive log filename=/u01/app/oracle/oradata/archive/1_116_666786084.arc = 1 thread
  sequence = 116archive log
  filename=/U01/app/Oracle/oradata/archive/1_117_666786084.arc
  thread = 1 sequence = error 117Oracle:
  
  ORA-01547: WARNING: RECOVER succeeded but OPEN RESETLOGS
  would get the below error
  ORA-01152: 1 no file has been restored from a sufficiently old backup
  ORA-01110: data file 1: ' / u01/app/oracle/oradata/sari/system01.dbf'
  
  media recovery complete, duration: 00:00:10
  Finished recover to 13 December 08
  
  
  4. If I run
  Run {}
  restore the database;
  recover the database;
  }
  
  I receive this error on step 2 (06054 RMAN: recovery of media asking unknown journal: thread 1)
  SEQ 118 lowscn 1392700)
  
  5. If I just restore the database and I do not perform a recovery by rman and I restart repeat if applies to all things seem well
  but in the opening of database, I get ORA-01152: 1 file was not restored from a sufficiently old backup
  Ora-01110: data file 1: ' / u01/app/oracle/oradata/sari/system01.dbf' error)
  
  do you know what is the problem
  
  Thank you
  
  Published by: ARKH 12 December 2008 23:06

  This is because as soon as you open the standby database, application of roll forward stops. At least that's true up to 10 gr 2, 11 g, you have the option "Active Dataguard" (requires an additional license), which allows to apply, while the database is open.

  Werner

• Protection of data error: no active Managed Standby recovery

  Hi all
  I have a strange problem. Right now I have 2 primary node RAC on Windows and another 2 RAC standby node (physical standby) also on Windows 2003 (R2). I've done a few time to spend waiting for redo apply read-only with no problems. Today, I tried the switch and he kept giving me the error as follows:
  
  SQL > alter database recover managed standby database disconnect;
  
  Database altered.
  
  SQL > alter database recover managed standby database cancel;
  ALTER database recover managed standby database cancel
  *
  ERROR on line 1:
  ORA-16136: Managed Standby Recovery non-active
  
  I also check the logs broker and archiving of guard data and all seems fine. All recovery logs are applied to standby mode. At the same time, the recovery of database alter managed declaration, standby database cancel works, but the open next alter database statement crashed to the instance.
  
  Any suggestions?

  Another instance is resumed by chance?

  This will automatically launch after restart of the mount if you activate dataguard broker configuration and instance to apply may not be one where you connect to with sqlplus.

  Try to look at the alert logs of bodies and gv$ managed_standby

• During startup, I get an error message that the registry database cannot find a file and modify registry to delete the reference to the file in the registry. How can I do this?

  Original title: Registery Error Message

  During startup, I get an error message that the registry database cannot find a file and modify registry to delete the reference to the file in the registry.  How can I do this?

  Hello

  • What were the changes made before the problem occurred?

  I recommend you perform the clean boot.
   
  Configuration of your system in a clean boot state helps determine if third-party applications or startup items are causing the problem. If so, you need to maybe contact the manufacturer of the program for updates or uninstall and reinstall the program.
   
  See the following article in the Microsoft KB for more information on how to solve a problem by performing a clean boot in Windows Vista or Windows 7:
   
  How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7
  http://support.Microsoft.com/kb/929135 
   
  Note: After troubleshooting, be sure to set the computer to start as usual as mentioned in step 7 in the above article.

• 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