failover and failback on the physics of the standby database.

Similar Questions

• 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

• Backups on the physics of the standby database?

  I use dataguard and standby a physical database. How to assign backups on the physics of the standby database to reduce the load on the primary database.
  
  environment: windows
  
  Database version: 11.2.0.1.0
  
  
  What are the pro and cons on the allocation of jobs of RMAN backups for the physics of the standby database?

  Hello;

  The backup database is an identical copy of the primary database block.

  Therefore, you just save one of the two (you can choose to only save the day before, however, if you want to remove the load on the primary). But if you are uncomfortable with the primary backup, it is not necessary for the safeguarding of the day before. (Since you can recreate the primary backup before).

  The only important part, is that you use the RMAN catalog. Then only known RMAN, the two are identical and can use the same backup.

  Best regards

  mseberg

• The physics of the standby database Y2K problem

  Hi all
  
  I am the passage of primary school to the physics of the standby database. Physical standby is in "recovery management" mode using real-time applies and is in editing mode. I've run alter database commit to switch to sleep mode physical with the logoff command. Now I'm waiting for standby mrp leave after treated RAH recording, but it seems mrp was hanged.
  
  Here is the content of the database pending:
  
  Online Redo Log recovery: thread 1 mem Group 5 Seq 620 reading 0
  Mem # 0: /oracle/app/oracle/dbrac/th1-redo5a.log
  Activation reset sleep ID 749049115 (0x2ca5951b)
  Met Media Recovery end Redo indicator
  Media recovery continues
  Media, recovery waiting for thread 1 sequence 621
  Journal archived 14 extra for each thread 1 620 0x2ca5951b dest ID sequence entry 1:
  
  
  Need help to solve.
  
  Thank you
  Sandy.

  Hello;

  After after deliver you (successfully) a:

  alter database commit to switchover to physical standby with session shutdown
  

  You must:

  Shutdown the former primary and mount as a standby database
  

  Check out my step by step:

  http://www.Visi.com/~mseberg/data_guard/Data_Guard_switchover.html

  Read everything (all steps) before continuing.

  Best regards

  mseberg

• Is it possible to run vCenter Server and AUVS in the same database?

  Hello. My client has vCenter Server and VUM installed and running in the same database. Yes, the same database (not only same server database) and the same ODBC (ODBC VUM is 32-bit only).

  My question is whether it is supported or not and I would like a source VMware information, not only "it works fine for me".

  I can't find any definitive info on this VMware. Only something to wave in the installation and upgrade guides about or not to run in the same database ' ' (I guess they mean 'server') and it seems that the recommendation is to separate them for the 'large environments,' whatever that means.

  The environment vSphere 4.1 is currently, and there are about 20 guests and 150 virtual machines.

  If it is not supported, I guess the best way to go is to reinstall both from scratch?

  Thanks in advance!

  / Anders

  Yes, it is a supported configuration.  Since VUM and vCenter using different tables, you can share the same DB

  The database of the update manager that you use can be identical to the vCenter Server database. You can also use a
  separate database, or you can use existing database clusters. For best results in a large scale environment, you
  must use a dedicated Update Manager database that is located on one computer other than the
  the vCenter Server system database.

  http://pubs.VMware.com/vSphere-50/topic/com.VMware.ICbase/PDF/vSphere-Update-Manager-50-install-Administration-Guide.PDF

• LOG_ARCHIVE_DEST_2 parameter error and cannot start the primary database

  Hello
  I was getting errors in my RMAN backup script. I took a glance on the database settings. Looks like I made a mistake when I was in the LOG_ARCHIVE_DEST_2 setting in the standby database. Instead of putting on the eve I put it in the name of the primary instance. I also noticed that the LOG_ARCHIVE_DEST_2 setting has been changed in the primary database where I put it first. I guess he's changed when I changed the sleep setting. I have two questions:
  
  (1) can the parameter LOG_ARCHIVE_DEST_2 be changes for the correct setting now that I set it wrong. The reason why I ask is because when I tried to change by using the following ALTER SYSTEM command I got an error saying something about conflicting attributes. I guess it's because the name of the primary instance has been upgraded with the DB_UNIQUE_NAME instead of the name of the standby instance. If I could change the LOG_ARCHIVE_DEST_2 setting to sleep first then maybe I can change the primary to the correct setting? Please provide markets.
  
  ALTER SYSTEM SET LOG_ARCHIVE_DEST_2 ='SERVICE = < DB PRIMARY > ASYNC VALID_FOR =(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME = < PRIMARY_INSTANCE > '
  
  (2) the second question is you can start a database using a spfile? (I use ASM and Data Guard) I ask because while I was connected to the primary database I executed the following command:
  
  ALTER SYSTEM SET LOG_ARCHIVE_DEST_2 = 'SERVICE = < PRIMARY_INSTANCE > ASYNC VALID_FOR =(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME = < PRIMARY_INSTANCE >' scope = spfile;
  
  I then stop the database and try to start but it won't start because it says to conflicting attributes. I don't create a pfile from spfile file before you shut down the database. (I'm bad). How can I change the setting for the primary database to start over. (The PFILE file is different in ASM. There are sub + DATA but has only a single line indicating where is the location of the SPFILE) I need to run the following RMAN RESTORE CONTROLFILE FROM backup AUTOMATIC;
  
  Please help as it is a production environment that was supposed to be delivered only yesterday.
  
  Any help will be greatly appreciated!
  
  Thanks in advance.
  
  J

  I always use it. So my answer is Yes.

  Please consider several of the responses of CKPT marking "useful".

  He works very hard in the forum and didn't work great!

  I call it "SuperStar."

  Best regards

  mseberg

• Script of free space for the physics of the standby database

  I need to determine how much free space I have in my physical storage spaces of the standby database. Is there a query for this? Remember that dba_ views are not available in a mounted single standby database so I'm pretty well limited to using the views v$. Thank you

  Why do you think you have to check the free space into a storage ensures physical ?
  You cannot create all segments anyway.

  Kind regards
  Uwe Hesse

  http://uhesse.WordPress.com

• RMAN and repositories on the same database grid control

  What are the disadvantages of having the RMAN Repository and repository on the same database grid control?
  
  What effect does this have
  
  1. daily maintenance
  
  2. after disaster or high availability... or the recovery scenarios.
  
  3 is server performance with respect to the use of the CPU and memory - not desirable to have two repositories on the same database?
  
  Currently we have not a RMAN or a repository of GC. We intend to implement both. Angle of savings, it would be good if we can just build another data base for two repositories on an existing database server with 2 production databases. The server has enough CPU and RAM face for 1 new database, but that would mean an exaggeration to have 2 new databases.
  
  If it is not advisable to have two repositories on the same database, then we would need strictly two separate databases, in this case, we will need to go to a new database server host two databases, which the org seeks to avoid, as this would mean that to buy a new license.
  
  I tried searching a few books, but don't have no clear guidance on the same. Any opionion would really help. Thank you.
  
  Concerning
  
  S diallo

  Where this instance fails, all rman needs to restore is in the database control file. How to restore a database with rman from the command line, without a catalog. (The backup and Recovery Guide has details of how do.) This will get data back so that you can use the grid again control.

  In order to insure against a default of the machine hosting the instance, verify that the database is in log mode archive and protected with scheduled backups of hot and copy the backup files to another server.

  Other options for high availability, you have a license (Data Guard, RAC) could also be deployed for this instance, if you need more recovery options.

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

• Switching from primary to the standby database

  Hi all
  
  Please can you give me some advice/comments/documents to help understand the steps that should be applied to move from a primary database to a standby database.
  I'm using Oracle 11 g 2 with Dataguard.
  
  What are the steps that must be applied from the primary to the standby database.
  
  Kind regards

  Hello again;

  My paper is a physical standby database. I have NOT tested using a logical standby database.

  The steps documented to perform the failover of the database logical Standby is located in:

  Perform the failover in a Configuration of data hold without the [ID 232240.1] Data Guard Broker

  Look under the heading "the steps to perform the logical passage with the Standby databases:

  I hope this helps.

  There is additional information here:

  http://ayyudba.blogspot.com/2007/10/performing-switchover-in-Data-Guard.html

  Best regards

  mseberg

• 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

• Data file not shipped from the primary database to the standby database

  Hello
  
  (1) create a new user
  (2) created a new table space and add datafile on the primary database
  (3) the value tablespace default user
  
  But so far, this new data file is not delivered on the standby database.
  
  Version of database - 10.2.0.3
  OS - Windows
  
  Setting of primary and Standby: -.
  
  SQL > show parameter standby_file_management;
  
  VALUE OF TYPE NAME
  ------------------------------------ ----------- ------------------------------
  standby_file_management string AUTO
  
  Both have the same file system, but the difference is case sensitive.
  
  Primary data file location - D:\testdata
  
  Location of file data at rest - D:\TESTDATA
  
  Help, please.

  MRP process is running on the standby database?

  If it is then try to pass, log on the primary database and share your result.

• Switch on the physics of the standby database

  Hello
  
  I'm the primary database "DPRB" on the ip address of the server 10.0.0.7.
  and database ensures "DBST" Physics on the ip address of 10.0.0.8 Server
  
  I can spend the roles of database with integrated OEM Data Guard Broker.
  
  At some methods including ip automatic change of database pending after switch? cuase users didn't change tsnnames of files?
  
  Can I use LDAP internet directory or 2 network interfaces on private and public servers, but is located in oracle, another solution? simple like DataGuard broker

  Follow this metalink note:

  Step by step guide how to configure and test the failover of Client for the transition to the Dataguard and failover.
  DOC - ID: 740029.1

  Werner

• 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

• After doing a failover and failback - store of data replicated

  So I have a question of the State of the data store where my vms are in fact a table after failover and restore.

  I did a few VMs reocvery failover, and then made a reprotect and definitely failed virtual machines to their original location... Then when I discovered the virtual machines they are running on the original cluster before testing with SRM (as expected)

  what I didn't expect is the data store using the vms system has the prefix "follow" yet.

  I really don't think that the store of data they use is a snapshot, when I did an esxcfg-volume - l, nothing came as far as snapshots.

  So has she not only removed the prefix 'snap' or did I miss something...

  Thank you!!!

  Regarding your point about retrieved data warehouses, they actually aren't all that normal.  During the recovery process, vSphere resignatures LUN and it is this will need the LUN that makes vSphere treat it like a snapshot.  The prefix '-wink', says @memadd, is just the default agreement used by SRM for resigned handling LUN, that they are all in the recovery.  The recommended option to keep the original name works well, I've used it before datacenter migrations.

  These could help.

  VMware KB: Snapshot LUN in ESX and ESXi detection

  http://SearchVMware.TechTarget.com/Tip/Resignaturing-vmfs-volumes-the-forgotten-VMware-SRM-subject

  http://SearchVMware.TechTarget.com/tip/the-mechanics-of-VMware-site-recovery-manager-Resignaturing