Similar Questions

• Dataguard Configuration database upgrade

  Hello
  
  I have some doubts regarding the upgrade of database in dataguard configuration. Could someone help me please.
  
  -How update occurs in the dataguard configuration?
  -Is that we must install only different OH in both? And once the catupgrade script is run on the primary, it will automatically update pending as well?
  - Or is to upgrade the two separately? That is to say, first aid and then primary or vice versa
  -Can reduce us downtime by breaking the dataguard config. Do a permutation, and do secondary as main and primary upgrade first?
  And once the upgrade is complete in the primary, raise and improve the day before. And later once the upgrade completed on standby, primary synch and sleep.
  
  Please share your ideas and your thoughts!
  
  Thank you!

  First of all, - steps may differ about the version upgrade but - my post with the following link might help clarify the concept.
  http://emrebaransel.blogspot.com/2009/02/10204-upgrade-with-DataGuard.html

  user1982050 wrote:
  Hello

  I have some doubts regarding the upgrade of database in dataguard configuration. Could someone help me please.

  -How update occurs in the dataguard configuration?

  First you patch the binary Oracle both primary and standby. Then open services dataguard and upgrade the primary, standby database will update already.

• Upgrade Dataguard 9.2.0.8 (32-bit) to 10.1.0.5(64-Bit)

  What is the best way to do this with minimal downtime. I have two (2) machines [the two 32-Bit] primary (9.2.0.8) and Eve (9.2.0.8)... I need to switch the primary and standby to 10.1.0.5 (64-bit) to new hardware, limited service disruption. I'll have the new machines built and installed with 64 - Bit. My question is: can I have a computer 32-bit archlogs sending to a 64-Bit machine to apply (Dataguard)? My thought was to have the original upgraded to 10.1.0.5 (32-bit) 32-bit machine (9.2.0.8) Firstly build a Dataguard on one of the new 64-Bit machines and ship the new machine until the changeover weekend newspapers. I read a few posts that I can have a 32-bit database running on a 64-bit computer (with just the RPM 64 - Bit and 64-Bit o/s installed), deliver the newspapers to the Machine 64 - Bit, and then failover weekend change the wordsize of 32 bit to 64 bit, but don't know how true that is. Any help would be greatly appreciated

  I agree with FZheng, you should consider Oracle 11.

  You can avoid a database bounce by putting in place all your new settings Data Guard and FRA beforehand. And you can use an alter system to change the LOG_ARCHIVE_DEST_STATE_2 of "reporter" while you use RMAN duplicate to create the day before.

  So to build the new system, but add these settings even before starting the data move from Oracle 9.

  FAL_SERVER
  FAL_CLIENT
  STANDBY_FILE_MANAGEMENT=AUTO
  DB_UNIQUE_NAME
  DB_FILE_NAME_CONVERT
  LOG_FILE_NAME_CONVERT
  log_archive_dest_1
  log_archive_dest_2
  LOG_ARCHIVE_DEST_STATE_1
  LOG_ARCHIVE_DEST_STATE_2
  LOG_ARCHIVE_MAX_PROCESSES
  

  Create your spfile on the primary with LOG_ARCHIVE_DEST_STATE_2 set to ACTIVATE and you avoid a stop and restart later. Then change to DELAY until you build the day before. You can save time more by copying the password in advance. Wait to issue the FORCE LOGGING until all the data is transferred.

  Place your tnsnames and the Auditor including _DGMGRL on both servers in advance.

  If plan you correctly, you can use RMAN two copies and never primary stop. The day before will just begin to apply again them.

  If you find this "Helpful" Please mark as well.

  Best regards

  mseberg

• Agent upgrade on the DataGuard configuration

  Hello
  
  Win x 64 server
  Oracle 10.2.0.3.0
  Agent 10.2.0.3.0 (go 10.2.0.5)
  
  Last days I've been patching all the agents out there, nothing complicated on this matter, but now I came to our configuration dataguard, for me, it seems that this will not matter, I have found no documentation contends it would be different, since the agent are separated from data bases itself.
  
  #shut to the bottom of the agent
  #patch
  
  Grateful for answers,.

  There is nothing special dataguard / agency relationship. As usual, upgrade after upgrade test, and if you find any problems you will need to remove the target, and add it again.

• Fact Eve DataGuard between (Source site) 11.2.0.3.0 and (target site) 11.2.0.4.0 taken in charge?

  Hello gurus

  Fact Eve DataGuard between (Source site) 11.2.0.3.0 and (target site) 11.2.0.4.0 taken in charge?

  My environment:

  Site source OS: RHEL 5.6 Database: v11.2.0.3.0

  Target site OS: RHEL 7.1 Database: v11.2.0.4.0

  The database size is 100 GB

  What about

  Hitgon

  As I mentioned, again the DG transport and apply the will to work in mixed versions. But it is not supported by Oracle for longer period. When I say not supported which means lets say if you hit any bugs in mixed environment associated with DG, then you can't get a support to connect to a new bug... etc... However, mixed versions are supported bby Oralce for 30 days. This is because any time the migration/upgrade that you can keep primary and standby in different versions.

  For more details refer,

  1.

  search for lines,

  The maximum length supported for different database software house between primary and Nightlight is 31 days.

  Insurance of Patch Oracle - Data Guard standby-first Patch applied (Doc ID 1265700.1)

  2. with regard to Cloud Control Support.

  SUBJECT: Set up and manage Oracle DataGuard, using Oracle Enterprise Manager Cloud control 12 c

  search for "the obligation for the Oracle software is stricter. The Oracle software must be the same version - including the release of the patches Oracle group. »

  Set up and manage to Oracle Data Guard with Oracle Enterprise Manager Cloud control 12 c

• DataGuard and RMAN across Oracle versions

  I was curious to know what restrictions we cross versions of Oracle using RMAN and DataGuard.  That is to say, can use DataGuard to ship newspapers a 11.2 a standby 12.1 primary?  We have to restore a database 11.2 12.1?

  Support for the mixed Version, for a Data Guard physical standby is generally NOT supported.

  Physical standby need primary and standby should be in the same version

  You can restore database on 12.1 11.2 House, but must open the database with the option 'open resetlogs upgrade' as binary and db are in different version. We perform db upgrade after the opening of database

• 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

• The upgrade of database 10g to 11g with minimal downtime?

  Hi all

  We want to improve our 10.2.0.4 RAC database for 11.2.0.3 linux linux RAC. We have two different servers, where one is the production server (10.2.0.4) and another is the 11.2.0.3 Server.

  Here, we want to minimize downtime of the production database.

  Our db size is close to 1 TB. If we turn to the traditional method of upgradation as given below, then it will take nearly 15 hours:

  1. take RMAN 10 g bkp.

  2. transfer to server 11 g.

  3. restore the db.

  4. set at the database level.

  I had two methods to minimize the downtime that arise as follows, but I'm not sure that these means are feasible or not...

  1st method:

  Our server of db source here is 10.2.0.4 and target db server is 11.2.0.3.

  1. create a DR on the target server. (10.2.0.4)

  -Here we have installed the software (stand-alone) db to 10.2.0.4 on the target server, but also some 11.2.0.3 rac linux.

  -All data of Dr. files will be filesystem (not on ASM).

  Synchronize the database of production with the Dominican Republic.

  2. break the DR and turn it on.

  3 close the db and move the datafiles of the DR to ASM storage (11.2.0.3)

  4. start PB with option upgrade and update.

  It will take nearly 5 hours.

  2nd method:

  -Install the software grid 11g and 10g and 11 g db Server db software target.

  -We set up DR as first method but the grid HERE home will be 11 g and db House will be 10 g.

  -Now we will synchronize the DR with data base of production.

  -to activate the 10g database (target server)

  -will restart the database 11g House and then we will modernize it.

  Here I want to know that is it possible to create a DR with the following configuration?

  Production DB is 10.2.0.4 and DR is configured with 11g grid and g 10 db House.

  Kindly give your entries...

  Kind regards

  Andy...!

  Hi Srini,

  Thanks for the reply.

  I have the following document for the upgradation to 11g with minimal downtime, and it seems good. We make this POC...

  Upgrade to transitional assistance rolling logical Standby database: Oracle DataGuard 11g.

  Thank you all for your suggestions.

  Kind regards

  Andy...!

• question awaiting upgrade

  Hello
  
  I have a GR 11, 1 material with dataguard configuration database. I've successfully upgraded the primary database to GR 11, 2 using dbua.
  
  Although 11 GR 2 software is installed on the backup server, I realized archivelogs were not sent to the standby server during the upgrade of database.
  When I switch the log file in the primary, I see below errors in alertlog Eve:
  

  RFS: 'Attach' request version mismatch

  I think it's because database versions are different after upgrade (primary became 11.2, night light is still 11.1)
  
  Because of this problem, archivelogs are not transferred.
  
  Should I manually modify oratab, create new spfile and start instance ensures new oracle home (11.2)? Those things were automatically on the primary database by dbua.

  Hello;

  The story runs on is:

  See Oracle support article: how to apply a group of patches, the power supply or the CPU in a configuration of data secondary physical custody [278641.1 ID]

  My presentation is :

  Disable the primary log shipping.
  Stop waiting.
  Install 11.2.0.2 software only on standby mode.
  Start the day before in recovery mode (using the new parameters of home and approx.) (do not run DBUA on standby)
  Re-enable log shipping
  Monitor it again apply primary eve - this will improve sleep

  Your questions

  Should I manually modify oratab, create new spfile and start instance ensures new oracle home (11.2)?

  You can change the oratab then on the previous day.

  You can move (copy) the spfile and password to the Oracle of the new homepage on the eve. (It's what I do before rebooting)

  Yes, you must change the env to the Oracle of new home before you start to the top of Mount and from recovery.

  Just did four of these this week and I do four others today. Will keep my eyes open for you.

  Best regards

  mseberg

  Subsequently

  Another thing I do is copy my tnsnames.ora and listener.ora into the new House on the primary and Standby and change it in the listener.ora according to needs:

  (SID_DESC =
  
         (global_dbname = PRIMARY_DGMGRL.thanks.buddy.com)
  
         (ORACLE_HOME = /u01/app/oracle/product/11.2.0)
  
         (sid_name = PRIMARY)
  
      )
  

  So if you restart the listeners on the two and bounce the databases, you can probably avoid a mistake of "heartbeat".

  mseberg

  Published by: mseberg on December 10, 2011 06:12

• Upgrade from Siebel 8.1 Production & Data Guard

  Hello
  We will have new material available for Siebel upgrade 8.x pre-production several months in advance. This material will be the same of prodcution with regard to size. We plan to use 'DataGuard' for Siebel 77 DB (2.5 to) replication on the new Siebel 8 DB pre-production server. My requirement is to have minimal downtime!
  
  I'm thinking next steps upgrade before the deployment weekend.
  1. take cold Siebel 77 PROD DB Backup
  2 database copy 77 PROD to the new pre-production Siebel 8 DB
  3. install and gateway of Siebel server, server Siebel, Siebel utility of database server and the Siebel web server extensions
  4. install the database schema and seeds
  5 import the new repository of Siebel 8
  6 test the application
  7 stop Siebel application and get ready for deployment to production
  
  Deployment weekend production steps:
  1. stop Siebel 77 application and DB
  2. start Siebel 77 DB data replication in the new Siebel 8 DB
  3. after the replication is complete, start Siebel 8 application.
  
  Can one that the steps above from the end of week of the production deployment might work, which means "DataGuard" replication to keep my DB Upgrade from Siebel 8 intact and wipe it away? I try to avoid the installation/configuration/upgrade to level the application during the deployment weekend.
  
  I'm lost and confused on how the upgrade of production will work. I have read several messages online, upgrade guides and haven't met good information/help for upgrade of production, all the support, the items are for the modernization of development environments!
  
  Please note that the 'Golden Gate' is not an option, do not have a budget for that!
  
  I'd appreciate any help.
  
  Thank you
  PM

  Now that you have added the stages of the upgrade, it is logical but there is no doubt some additional steps are required as you progress...

  regarding the statement:

  "I think that 'install & configure the Siebel servers' can be done before weekend of deployment without a database active, can anyone confirm that for me?"

  It might indeed and this could also be done on a copy of your development DB Upgrade environment. Siebel installation is not dependent on your DB, but there are some entries in your DB, which can be Siebel specific server, look at the guide for the copy of production if you don't understand what I mean. Restoration of Production environments in the Test [477772.1 ID] environments. If you move servers during the upgrade this guide will give you some tips too to areas that you need to consider.

• Increase the SGA on the database with dataguard

  Hi all
  
  I have a (10.2.0.2.0) database configured with dataguard and we want to increase the SGA. We want to upgrade the RAM in the server (Microsoft Windows Server 2003 R2 Server 5.2 Service Pack 2 (32-bit)) with double (actually 8G) RAM memory:
  
  The steps would be next? :
  
  -SQL > alter system set sga_max_size = 16G scope = spfile;
  
  -SQL > alter system set sga_target = 16G scope = spfile;
  
  -immediate cessation;
  
  -Start;
  
  Even in the database pending?
  
  Thanks in advance.

  Yes - it will not break the day before, but you should note that failover or crossing - new primary school will have one less memory allocated.

• patching and upgrading stream

  We have implemented between two stream sites. A site is the main and the second would be secondary
  or the backup (without using DataGuard) system. When we go operational, which we do not yet have.
  I am trying to determine how we would apply patches to the system. Yet once, if we're down for patches
  the second site should be available. Can I have two sites of different patches/upgrades?
  
  I intend to make with minimal down time. I read where the streams could push through the patch,
  but have had people do not recommend what the results might be unpredictable.
  
  Are there systems out there using rivers as their backup system? How do you make the patch or
  upgrade of maintenance?
  
  Appreciate your comments.
  Thank you.

  Streams are supported patch levels as long as you do not use a function in the Group of patches below which exists in the other. If patch to ease you and not to watch the streams. I would avoid just an accumulation of between the two session rivierra dctionary, even though I'm confident he composed with that. Just a reflex of conservatism.

• Catalog RMAN and dataguard wout?

  Hello
  
  We have used RMAN backups and recently put in place a dataguard environment in 10g r2 (physical standby). All through the upgrade to 11g that I came across instructions say you must use a recovery catalog in an environment of dataguard. Backups are running on the primary just using the control file and everything seems to work. I fact a 'Validate restore database' and he succeeded. The recovery catalog is necessary if I chose to do the backups on the eve-, or is a catalog that is required in my scenario?
  
  Thank you
  
  Mark
  
  Published by: user6061469 on April 20, 2011 11:43

  It is an improvement. But not an obligation so you don't need where a plan to save the two sites and use a common catalogue.

  Hemant K Collette

• Between different versions of oracle DataGuard

  I can dataguard year 11.1.0.6 database to a backup database 11.2.0.1

  For the purposes of upgrading Yes. But only a logical standby. And you can also use the logical standby transient rolling upgrade as well if you are a user of physical intelligence.

  See the following topics:

  Joint Oracle Version supports with Data Guard redo Transport Services (Doc ID 785347.1) on the Oracle Support

  MAA Rolling Upgrade paper at http://www.oracle.com/technology/deploy/availability/maa/maa_wp_11g_upgrades_made_easy.pdf
  Logic paper ensures Rolling Upgrade transitional MAA http://www.oracle.com/technology/deploy/availability/pdf/maa_wp_11g_transientlogicalrollingupgrade.pdf

  Larry

• DataGuard and Flashback database

  Any sense to run a database (using the flashback database) when using Dataguard.
  We don't talk about uptime

  When to use database of flashback? (to decline the upgrades?)
  0 protection against human errors
  1 flashback database
  2 flashback Data Archive

  also should we run dataguard in a physical standby or a logical standby configuration
  1 physical standby
  And effect seen use "logical standby".

  Kind regards
  Taj