Switchover to Standby is it necessary to shutdown other nodes?

Hi,
I have installed oracle 11g r2 rac with asm in two nodes. OS is hp-Unix.
I have installed oracle11g Active Data Guard using Single alone Database.
Both RAc and Active Data Guard works fine.
I have not configure Data Guard Broker.
For testing purpose I need to make primary as standby and standby as primary.
In node 1: I will run commend in node 1
SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN ;
Shall I need to shutdown node 2 in RAC?
if node 2 is in shutdown then after switch over primary as standby just open the node 2 ?
Thanks
Solaiman

I have installed oracle 11g r2 rac with asm in two nodes. OS is hp-Unix.
I have installed oracle11g Active Data Guard using Single alone Database.
Both RAc and Active Data Guard works fine.
I have not configure Data Guard Broker.
For testing purpose I need to make primary as standby and standby as primary.
In node 1: I will run commend in node 1
SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN ;
Shall I need to shutdown node 2 in RAC?
if node 2 is in shutdown then after switch over primary as standby just open the node 2 ?When you are not managing with broker, primary if you have 2 node RAC. Then prior to switchover shutdown any one of the node.
Once you performed switch over, Your primary database will be non-RAC database[because not an clustered], So the redo threads active in only one node.
In such case you will be having one node primary and one node standby.

Similar Messages

Propagation after switchover to standby

Hi
My DB Version=10.2.0.4
I had a stream relation that working correctly after switchover to standby in destination now in source database i got the following error in propagation:
select status,error_message from dba_propagation
DISABLED
ORA-02068: following severe error from AQHOS
ORA-01033: ORACLE initialization or shutdown in progress
ORA-06512: at "SYS.DBMS_AQADM_SYS", line 1087
ORA-06512: at "SYS.DBMS_AQADM_SYS", line 7616
ORA-06512: at "SYS.DBMS_AQADM", line 631
ORA-06512: at line 1
i corrected all tnsnames and dblink is working correctly but still i have this error.
WHAT I MUST TO DO?

Refer to metalink document _STREAMS propagation to Primary of physical Standby configuation errors with Ora-01033, Ora-02068 *[ID 359971.1]*_
You need to set SERVICE_NAMES. Hope this helps resolve your issue.
Thanks

One node RAC pause/hang/block on other node shutdown

Hi,
We have a Java application running on Linux servers connecting to a 10.2.0.1 RAC cluster, also Linux. When the application starts it opens up a pool of connections to the databsae, and these are used throughout the life time of the application. One server connects to one RAC node.
AppA - DBA
AppB - DBB
When we shutdown one node, the application connecting to that node stops, which is what we would expect in this configuration.
What is strange is that the other application blocks for 63 seconds and then continues. So it is like the database is blocking, or the database connections are blocking.
We are not using TAF, FAN, FCN, LB, VIPs or any special features, just simple lightweight JDBC from one server to one database. In fact I do not thing we are unwittingly using any of these features, we have them switched off.
john

user1788323 wrote:
What is strange is that the other application blocks for 63 seconds and then continues. So it is like the database is blocking, or the database connections are blocking.How have you determined/diagnosed the 63s blocking? (more details in this regard may shed some light on the problem)
Assuming that the block is server side, then two basic reasons comes to mind.
Networking issue - the CRS on the surviving node has to perform certain functions, like switching the VIP of the node that left the cluster to a surviving cluster node. The listener may need to re-register services. A local firewall may need to be dynamically reconfigured for supporting the new failed-over VIP. Etc.
Thus these could result in some kind of delay or issue in the network layer that you are seeing from the client side.
Infrastructure issue. If the actual client request via JDBC reaches the server process, and it is slow in responding, then that is not a network issue - instead some underlying service or s/w layer that the server process needs to use to perform the client request is busy for those 63s.
This could be related to the Interconnect, the shared I/O storage layer or something along those lines. For example, how does the Interconnect and/or SAN switch re-act when a server node is powered down or rebooted?
There's not really sufficient information to make anything but a guesses.. You will need to isolate the problem with further testing.
I have seen similar problems with 10.1.0.3 CRS and RAC when a node is evicted from the cluster. In this case the "hung" period was in excess of 15 minutes and only for new connections (Listener unable to hand off to dedicated servers or dispatchers). Existing connections worked fine however and were unaware of any problems. But part of the issue in this case was a poor (outdated) driver layer - and also the last time we used proprietary binary drivers (kernel modules) from 3rd party vendors that results in a tainted (and very fixed and rigid) Linux kernel. Today we're sticking with an OpenSource driver layer only for Linux.

After switchover to standby as primary, now how to switch back

Hello DG experts:
I'm running Oracle 11.2 on Linux 5.8.
I am in the process of (trying) to mimic our existing production DG environment for testing purposes.
So far...
I've managed to set up a primary and standby database and ensured all logs apply properly.
My database name is DGTEST (on both primary and standby).
My db_unique_name is DGTEST_DG1 on primary, and DGTEST_DG2 on standby.
I performed a switchover from primary to standby, and opened the standby database as primary.
But, first thing is that when I check the switchover_status from v$database, it says: NOT ALLOWED.
Okay, so now what? Do I need to have another pfile to set specifically for when I am in primary or standby modes?
Here are relevant commands I have checked already:
on new Primary (db_unique_name = DGTEST_DG2)
SQL> select switchover_status from v$database;
SWITCHOVER_STATUS
NOT ALLOWED
SQL> select sequence#, applied from v$archived_log order by 1;
      SEQUENCE# APPLIED
            291 YES
            292 YES
            293 YES
            398 YES
            399 NO
            400 NO
            401 NO
            402 NO
112 rows selected.
SQL> select destination, status, error from v$archive_dest;
DESTINATION                    STATUS    ERROR
/arch/DGTEST/archivelogs       VALID
/arch/DGTEST_STBY              VALID
                               INACTIVE
                               INACTIVE
                               INACTIVE
31 rows selected.
on new Standby (db_unique_name = DGTEST_DG1)
SQL> select switchover_status from v$database;
SWITCHOVER_STATUS
TO PRIMARY
1 row selected.
SQL> select sequence#, applied from v$archived_log order by 1;
      SEQUENCE# APPLIED
            276 YES
            277 YES
            278 YES
            397 NO
            397 YES
            398 YES
            398 NO
231 rows selected.
SQL> select destination, status, error from v$archive_dest;
DESTINATION                    STATUS    ERROR
/arch/DGTEST                   VALID
DGTEST_DG2                     VALID
/arch/DGTEST_STBY              DEFERRED
                               INACTIVE
                               INACTIVE
                                 . . .Please keep in mind that I have made this test environment as close as possible (I think) to our production environment.
One of the objectives is to confirm we can switchover and back in our production environment.
So if there is something seriously wrong with this environment and it is the same in our production environment, that would be one of my primary objectives to find out about.
Only significant difference is that we are also using DGBroker in production and I did create configuration yet until I got the switchover working manually first.

Hi,
Follow This Steps:
How to Switchover from Primary to Standby Database?
MY Configuration:
RAC is configured on dcpdb1(node1) and dcpdb2(node2).
DB Name: dcpdb
db_unique_name: dcpdb
Instance Name: dcpdb1 on node1
Instance Name: dcpdb2 on node2
Active Data Guard is configured on drpdb1
DB Name: dcpdb
db_unique_name: drpdb
Instance Name: drpdb
Process:
On the primary server, check the latest archived redo log and force a log switch.
*########### Login dcpdb1 as Oracle user #########*
SQL> SELECT sequence#, first_time, next_time
FROM v$archived_log
ORDER BY next_time;
SQL> ALTER SYSTEM SWITCH LOGFILE;
Check the new archived redo log has arrived at the standby server and been applied.
*########### Login drpdb1 as Oracle user #########*
SQL> SELECT sequence#, first_time, next_time, applied
FROM v$archived_log
ORDER BY next_time ;
*########### Login dcpdb2 as Oracle user #########*
SQL> SELECT sequence#, first_time, next_time
FROM v$archived_log
ORDER BY next_time ;
SQL> ALTER SYSTEM SWITCH LOGFILE;
Check the new archived redo log has arrived at the standby server and been applied.
*########### Login drpdb1 as Oracle user #########*
SQL> SELECT sequence#, first_time, next_time, applied
FROM v$archived_log
ORDER BY next_time ;
*########### Login dcpdb1 as Oracle user #########*
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
TO STANDBY
*########### Login dcpdb2 as Oracle user #########*
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
TO STANDBY
*########### Login drpdb1 as Oracle user #########*
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
NOT ALLOWED
*########### Login dcpdb2 as Oracle user #########*
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL>
*########### Login dcpdb1 as Oracle user #########*
SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN;
Database altered.
SQL>
SQL> shutdown immediate
ORA-01507: database not mounted
ORACLE instance shut down.
SQL>
SQL> startup mount
ORACLE instance started.
Total System Global Area 1.5400E+10 bytes
Fixed Size 2184872 bytes
Variable Size 7751076184 bytes
Database Buffers 7616856064 bytes
Redo Buffers 29409280 bytes
Database mounted.
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
TO PRIMARY
SQL>
*########### Login drpdb1 as Oracle user #########*
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
SESSIONS ACTIVE
SQL> alter database commit to switchover to primary with session shutdown;
Database altered.
SQL> shutdown immediate
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL>
SQL> startup
ORACLE instance started.
Total System Global Area 1.5400E+10 bytes
Fixed Size 2184872 bytes
Variable Size 7717521752 bytes
Database Buffers 7650410496 bytes
Redo Buffers 29409280 bytes
Database mounted.
Database opened.
*########### Login dcpdb1 as Oracle user #########*
SQL> alter database open read only;
Database altered.
SQL> alter database recover managed standby database using current logfile disconnect;
Database altered.
*########### Login dcpdb2 as Oracle user #########*
SQL> startup mount
ORACLE instance started.
Total System Global Area 1.5400E+10 bytes
Fixed Size 2184872 bytes
Variable Size 7751076184 bytes
Database Buffers 7616856064 bytes
Redo Buffers 29409280 bytes
Database mounted.
SQL> alter database open read only;
Database altered.
SQL> alter database recover managed standby database using current logfile disconnect ;
Database altered.
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
NOT ALLOWED
SQL>
*########### Login drpdb1 as Oracle user #########*
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
TO STANDBY
*########### Login dcpdb1 as Oracle user #########*
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
NOT ALLOWED
SQL>
*########### Login dcpdb2 as Oracle user #########*
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
NOT ALLOWED
SQL>
*############### End of Switchover from Primary to Standby Database ##########*
How to Switchback from New Primary(drpdb) to old Standby(drdb) Database and New Standby(dcpdb to Old Primary(dcpdb)?
Process:
On the New primary server, check the latest archived redo log and force a log switch.
*########### Login drpdb1 as Oracle user #########*
SQL> SELECT sequence#, first_time, next_time
FROM v$archived_log
ORDER BY next_time ;
SQL>ALTER SYSTEM SWITCH LOGFILE;
Check the new archived redo log has arrived at the standby server and been applied.
*########### Login dcpdb1 as Oracle user #########*
SQL> SELECT sequence#, first_time, next_time, applied
FROM v$archived_log
ORDER BY next_time ;
*########### Login dcpdb2 as Oracle user #########*
SQL> SELECT sequence#, first_time, next_time, applied
FROM v$archived_log
ORDER BY next_time ;
*########### Login drpdb1 as Oracle user #########*
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
TO STANDBY
*########### Login dcpdb1 as Oracle user #########*
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
NOT ALLOWED
*########### Login dcpdb2 as Oracle user #########*
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
NOT ALLOWED
*########### Login drpdb1 as Oracle user #########*
SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN;
Database altered.
SQL> shutdown immediate
ORA-01507: database not mounted
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.
Total System Global Area 1.5400E+10 bytes
Fixed Size 2184872 bytes
Variable Size 7717521752 bytes
Database Buffers 7650410496 bytes
Redo Buffers 29409280 bytes
Database mounted.
SQL>
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
TO PRIMARY
SQL>
*########### Login dcpdb2 as Oracle user #########*
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL>
*########### Login dcpdb1 as Oracle user #########*
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
SESSIONS ACTIVE
OR
SWITCHOVER_STATUS
SWITCHOVER PENDING
SQL> alter database commit to switchover to primary with session shutdown;
Database altered.
SQL>
SQL> shutdown immediate
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
Total System Global Area 1.5400E+10 bytes
Fixed Size 2184872 bytes
Variable Size 7751076184 bytes
Database Buffers 7616856064 bytes
Redo Buffers 29409280 bytes
Database mounted.
Database opened.
SQL>
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
TO STANDBY
SQL>
*########### Login dcpdb2 as Oracle user #########*
SQL> startup
ORACLE instance started.
Total System Global Area 1.5400E+10 bytes
Fixed Size 2184872 bytes
Variable Size 7751076184 bytes
Database Buffers 7616856064 bytes
Redo Buffers 29409280 bytes
Database mounted.
Database opened.
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
SWITCHOVER_STATUS
TO STANDBY
SQL>
*########### Login drpdb1 as Oracle user #########*
SQL> alter database open read only;
Database altered.
SQL> alter database recover managed standby database using current logfile disconnect;
Database altered.
SQL>
*####### End of Switchback from New Primary(drpdb) to old Standby(drdb) Database and New Standby(dcpdb to Old Primary(dcpdb) #########*
Thanks
Solaiman
Edited by: 876149 on Apr 1, 2013 11:56 AM

Switchover in Standby database.

Hi All,
DB:11g
OS:AIX
If I am performing a switchover for a Physical standby database, and I have successfully converted my Primary database to new Standby database and when I am trying to convert my Old Standby database to a new Primary database and let us say due to some error (the error is not the important here) I am not able to switch my Old standby database to a new primary database.
What should be my possible steps to undo the switchover or to get me out of this hole?
Regards,
Sphinx

Hi Mohamed,
Thanks!
Well, I was asked this question in an interview and I cross questioned him "What is the error?". He said that the error is irrelevant and you have to give me back a Primary database in minimum time.
Since the original primary is now converted to a standby database and the old standby database is not getting converted to Primary database, so what steps I will have to do to get a Primary database in minimum time, at this moment even if I do not have a standby database that will do as per the interviewer.
This is my concern, finding the error is secondary which I can dig once my Primary is back.
In a nutshell, I just want to know if in the middle of a switchover that I have to perform in a time constrain, if my switchover fails as I have explained above. What approach or steps that I have to take to undo the swicthover or at least get my Primary back.
Hope it calirifes.
Regards,
Sphinx

Steps to switchover a standby to production

Hi All,
How can I perform a switchover from a standby database to production and vice versa.
Thanks in advanced
Bhupinder

Metalink has few good notes on this subject. In case, if you dont have any access to metalink, here is a good PDF.
www.oracle.com/technology/deploy/availability/pdf/MAA_WP_9iSwitchoveFailoverBestPractices.pdf
Jaffar

Necessary to shutdown an embedded derby?

is it necessary to manually shutdown a running embedded derby server?

No. Simply add a shutdown hook (see the API docs for Runtime) to your code and open another connection with the shutdown=true parameter.

Is it necessary to shutdown when dis/connecting the S-video cable?

Well, the title says it all- do I need to shut down to connect (or disconnect) an S-video cable? The manual says nothing about shutting the machine down, which makes me think it's NOT necessary. Thanks in advance for the help!
CW

No, you don't need to shut down. Putting the PB to sleep before making or breaking the connection is a sensible precaution, but I don't think that's essential either. I've never used an S-Video connection with my PB, but I've connected and disconnected external monitors and projectors via the DVI port on my PB without shutting down or sleeping it first, with no ill effects.

Switchover logical standby dataguard

hi
we are using oracle9i on enterprise linux 3 . our primary and logical database are not located remotely but are two different servers.
now i need to know the steps that i need to perform in order to switch my primary database to standby database and vice versa . i tried few things but was unsuccessful.
according to my concept what we need to do is
Make sure no data is arriving and the applied and newest_scn are equal.
change the database role of the respective database .
make changes in initialization parameter file to change the primary dest as standby and vice versa .
and then start logical standby apply .
Is thier something that i am missing i tried few things from net but was not able to understand the logic and was unsuccessful .
THANKS

OEM>Tools>Database Applications>Dataguard Manager.
Select primary>Disable
Select secondary>Enable

"WARNING! Closed connections to peer [standby IP] database! Please restart peer node to bring databases in sync!!"

i have a two appliances of NAC Manager, i want to make a failover, but i only connect them with a crossover cable on eth1,
is it neccesary conect a serial cable?, because when i try to verify a failover they appear this:
“WARNING! Closed connections to peer [192.168.0.254] database! Please restart peer node to bring databases in sync!!” in each one

Hi. I had a lot of those messages. In my scenario the failover bundle works OK during certain time but ocassionally the hearbeat fails (never knew why) and the warning messages appeared. Since there's no sync anymore the config in both manager will be different, so the very first thing to do is to backup the configuration. Please notice if the current active NAM is the primary or the secondary NAM (it's necessary to know this information for the later steps).
Then you will have to stop both NAM (service perfigo stop)
Now there's an extra step only if the last active NAM was the secondary : you will have to restore the backup into the primary NAM (since this NAM will have an outdated configuration).
Now back to the regular steps. You must start both NAM . The primary NAM will be the new active , synchronization will take some minutes, after that the "warning" will be cleared.
Please rate if it helps.

Should i shutdown other DBs while applying patchsets?

I have a 10.2.0.1.0 and an 11g DB running on a machine. I need a third database which should be of version 10.2.0.4.0 .
For that, i've installed 10.2.0.1.0 on a separate ORACLE_HOME(a software only installation) and i am going to apply the 10.2.0.4.0 patchset. But in the patchset documentation's pre-requisite bit it says
+8.6 Shut Down Oracle Databases+
Shut down any existing Oracle Database instances with normal or immediate priority. On Oracle RAC systems, shut down all instances on each node.
If Automatic Storage Management (ASM) is running, shut down all databases that use ASM, then shut down the ASM instance on each node of the cluster.
Does this mean i have to shutdown all other databases in this machine due to the patchset installation?

I just noticed that two threads were created by me for the same issue. This was mistake because of intermittent internet connection problem here. Sorry for the duplicate thread.

I have shot the same photo at different angles and would like to get them side by side to correct the color so the match. The balance between the photos is different and applying a mask to correct one photo does not necessary fix the other one being out o

I would like to align them too.

Topic or subject titles should be clear, pertinent and concise so that individual users can tell at a glance if they can help or not.
That field is not for attempting to fit your entire question in there.
Please keep this in mind next time you post. Thank you.

Shutdown inactive node cause reboot active node

Hi,
when I try to shutddown a inactive node of Oracle clusterware (two nodes) the active node reboot (s.o Oracle Linux 5.6 and ocfs2).
Fire it acquires vip of second node, then reboot and work correctly.
Anyone can help me?
Have a nice day

user2907588 wrote:
Here the log of active node:
Jan 31 15:35:23 esse3-db1 avahi-daemon[7041]: Registering new address record for 192.168.101.222 on eth0. *> Jan 31 15:56:30 esse3-db1 kernel: bnx2: eth2 NIC Copper Link is Down*
Jan 31 15:56:32 esse3-db1 kernel: bnx2: eth2 NIC Copper Link is Up, 100 Mbps full duplex, receive & transmit flow control ON
Jan 31 15:56:59 esse3-db1 kernel: o2net: connection to node esse3-db2.unisalento.it (num 0) at 192.168.101.202:7777 has been idle for 30.0 seconds, shutting it down.
Jan 31 15:56:59 esse3-db1 kernel: (0,17):o2net_idle_timer:1503 here are some times that might help debug the situation: (tmr 1359644189.432221 now 1359644219.431047 dr 1359644189.432200 adv 1359644189.432221:1359644189.432221 func (1f70fe7a:504) 1359644047.329097:1359644047.329102)
Jan 31 15:56:59 esse3-db1 kernel: o2net: no longer connected to node esse3-db2.unisalento.it (num 0) at 192.168.101.202:7777 *> Jan 31 15:57:29 esse3-db1 kernel: (6377,17):o2net_connect_expired:1664 ERROR: no connection established with node 0 after 30.0 seconds, giving up and returning errors.*
*> Jan 31 16:01:40 esse3-db1 syslogd 1.4.1: restart.*
>
Edited by: user2907588 on 1-feb-2013 7.39Hello,
One of the nodes in cluster seemed to have been evicted previously due to eth2 NIC outage between nodes so as removing the failed node(could be what u r referring to "INACTIVE")
Please check I have highlighted in provided log information... Check If you are able to ping to the specified IP, and do password-less ssh to other node (101), and ask your system/network administrator to look into it...
Regards,
Naga

Oracle Grid general questions

Our applications are running on their own application and database servers. We have a mix of hardware including Sun 4800, Sun 450, Sun 280, Sunfire 280, Dell Intel, etc. The OS on Sun boxes is Solaris 8 and on Dell Intel is Windows NT and 2000. To migrate to the grid infrastructure, are we able to make use of our existing hardware or do we need to upgrade them to make them grid ready or do we need to purchase new hardware all together leaving our current hardware investment behind?
When building either database or application cluster, is it possible to have a mix of hardware in the same cluster? For instance, can we have a cluster setup with a Sun box running one instance while a NT box running another?
How is oracle version upgrade handled in a cluster? Do we need to take all of the instances down to upgrade them at the same time or can we do the upgrade one at a time? If the latter option is doable, does that mean oracle cluster can support multi-version instances?
What happens if the upgrade involves upgrading the database as well?
In Oracle 10g, is it possible to run dataguard on two oracle versions at the same time? You run into this situation during oracle upgrade where you are upgrading the standby database while the primary database is running in production. After the upgrade, the standby database will be in a newer version than primary.

Q. Our applications are running on their own application and database servers. We have a mix of hardware including Sun 4800, Sun 450, Sun 280, Sunfire 280, Dell Intel, etc. The OS on Sun boxes is Solaris 8 and on Dell Intel is Windows NT and 2000. To migrate to the grid infrastructure, are we able to make use of our existing hardware or do we need to upgrade them to make them grid ready or do we need to purchase new hardware all together leaving our current hardware investment behind?
A. Oracle Database 10g offers a variety of features for CPU provisioning and Data provisioning that you can use to utilize your resources efficiently. Of course, you get the best resource utilization if you can cluster homogeneous resources and run all your databases on the same cluster. This is not always possible � you may have heterogeneous resources or you may have geographically distributed data centers. For such cases, you can use our data provisioning features to offload processing across these resources.
Our suggestion will be that you start off with the resources you have got now. You use our features that best fit your current IT infrastructure. Later when you want to acquire more hardware resources, you have more choices � you can acquire cheaper low-cost commodity hardware and run your databases on them.
Q. When building either database or application cluster, is it possible to have a mix of hardware in the same cluster? For instance, can we have a cluster setup with a Sun box running one instance while a NT box running another?
A. While building a cluster, you need homogeneous cluster � all the nodes need to have the same OS. Do you really want to have a heterogeneous cluster to run your databases? What about the complexities of troubleshooting o/s or Oracle issues, fail-over, possible port-specific Oracle bugs, the differences in compiled PL/SQL or Java or external procedures? Does any of this make the possible benefits worth it?
Q. How is oracle version upgrade handled in a cluster? Do we need to take all of the instances down to upgrade them at the same time or can we do the upgrade one at a time? If the latter option is doable, does that mean oracle cluster can support multi-version instances?
A. The Oracle Database 10g supports the application of patches to the nodes of a Real Application Cluster system in a rolling fashion. You can apply these patches one instance at a time. You quiesce one instance, apply patch to that instance, and reactivate and rejoin the patched instance to the cluster. While you are doing these, your applications on the RAC database are still running.
You can run system in the mixed mode for an arbitrary period to ensure that the patch corrects the original problem and has not introduced some other problem.
Q. What happens if the upgrade involves upgrading the database as well? In Oracle 10g, is it possible to run dataguard on two oracle versions at the same time? You run into this situation during oracle upgrade where you are upgrading the standby database while the primary database is running in production. After the upgrade, the standby database will be in a newer version than primary.
A. The Oracle Database 10g supports the installation of database software upgrades, and the application of patchsets, in a rolling fashion � with near zero database downtime � by using Data Guard SQL Apply. You establish the standby database using Data Guard. You upgrade the standby database. You can then continue running in this configuration for an arbitrary period of time. Later you can do a database role reversal and switchover of standby to the production database.

At time of switchover do we need to shutdown database

Hi
Oracle RDBMS : 11.2.0.2 RAC 4-node on RHEL 5.6
What are the steps for perfoming switchover between primary and physical standby,Do we need to shutdown the primary and physical standby databases before perfoeming switchover?

951368 wrote:
Hi
Oracle RDBMS : 11.2.0.2 RAC 4-node on RHEL 5.6
What are the steps for perfoming switchover between primary and physical standby,Do we need to shutdown the primary and physical standby databases before perfoeming switchover?No but you need to shut down all but one primary database instance. then you can restart the shutdown instances after the switchover task is completed.
read: http://docs.oracle.com/cd/B28359_01/server.111/b28294/role_management.htm#i1026398
Tobi

Switchover to Standby is it necessary to shutdown other nodes?

Similar Messages

Maybe you are looking for