CLUSTER_DATABASE parameter

Hi
By setting CLUSTER_DATABASE=TRUE is my instance not part of the cluser database.
Why are using " srvctl add database -d proddb" and srvctl add asm -n node1 -i +ASM1 -o $ORACLE_HOME
Could someone please explain
Thanks,
Silver

What is your 4 digts Oracle version ?
If your database is single instance database you must set CLUSTER_DATABASE to FALSE.
About SRVCTL usage for single instance database in 11.2 http://docs.oracle.com/cd/E11882_01/install.112/e24321/whatsnew.htm#BGGHBEJG says:
>
SRVCTL was enhanced to support single-instance databases with Oracle Restart on standalone servers and on clusters with Oracle Clusterware. SRVCTL is a command-line interface used to manage Oracle processes (database instance, listener, Oracle ASM instance) when using Oracle Restart. With SRVCTL, you can manage the Oracle Restart configuration, see the status of processes managed by Oracle Restart, and start or stop processes such as the Oracle Database.

Similar Messages

Cluster_Database parameter in init file

Hi All,
I have received one cluster environment backup so when I start with restore operation, I have created pfile and provide list of required parameters. There is one parameter called cluster_database which I set to TRUE. When I want to start database in nomount mode with created pfile it failed with ORA-03113. If I removed cluster_database parameter from pfile then there is no error and DB started in nomout mode.
Does it mean that given backup is from non-cluster environment? Please guide..
Thanks in advance.

Hi,
During restore of database yes, I prefer to opt for working on single node instead of cluster. Coming to issue of startup (during the non-recovery operation), if you are facing then that could be different (needs to check across/verify the parameters)
- Thanks
Pavan Kumar N

Question on alter system set cluster_database = true

11.2.0.2.0 windows 2008
doing a restore to a development RAC I noticed the following. I took the database out of cluster mode on one instance
alter system set cluster_database=false scope=spfile sid='PRD1';
shutdown, start up, do the restore, all good, I go to set cluster_Database=true but had issue instance would only start on one node, I reviewed my notes and found problem was when I set cluster_Database back to true I had typed
alter system set cluster_database=true scope=spfile sid='*';
instead of
alter system set cluster_database=true scope=spfile sid='PRD1';
So issue fixed.
I retested and confirmed '*' wont take. Ive seen many examples of '*' working online and I am sure I have used '*' many times so had just typed it off my head. Anyone explain? probably quotes or something.

Any chance there are multiple lines for cluster_database in the spfile ?I had thought maybe this, but confirmed no, it was a fresh build anyway that I was restoring to.
>
- Dump the spfile to a pfile ... edit ... recreate the spfile on all nodes.
>
Im not sure what this will achieve? the spfile is shared on the ASM.
>
As the cluster_database=true is a parameter to enable the RAC configuration. As you typed sid='*' it will try to enable the cluster_database parameter in all the instances(nodes) as it is RAC.
In your case as you did on a single node by specifiying the sid name it will work as it will look only for that sid and enable that particular node.
>
I find this hard to read but I think this misinterprets as well.
Thanks for the contribution. I think Ive found the solution
the asterisk doesnt apparently mean actually "all instances", from here
http://www.comp.dit.ie/btierney/oracle11gdoc/rac.111/b28254/admin.htm#BCEFICEE
and
"Setting SPFILE Parameter Values for Oracle Real Application Clusters"
-- this is a good example of what happened to me
>
*.OPEN_CURSORS=500
prod1.OPEN_CURSORS=1000
Note:
The value before the dot in an SPFILE entry identifies the instance to which the particular parameter value belongs. When an asterisk precedes the dot, the value is applied to all instances that do not have a subsequent, individual value listed in the SPFILE.
For the instance with the Oracle system identifier (SID) prod1, the OPEN_CURSORS parameter is set to 1000 even though it has a database-wide setting of 500. Parameter file entries that have the asterisk (*) wildcard character only affect the instances without an instance-specific entry. This gives you control over parameter settings for instance prod1. These two types of settings can appear in any order in the parameter file.
If another DBA runs the following statement, then Oracle updates the setting on all instances except the instance with SID prod1:
ALTER SYSTEM SET OPEN_CURSORS=1500 sid='*' SCOPE=MEMORY;
>
so when I was on node 1 and ran it for *, I was setting it for all the nodes except the node I was on which holds true from what Ive seen. I'll remember that one.

Steps for data guard RAC primary RAC standby

Hi,
I have some doubt in configuring data guard for rac DR to rac primary.
1) In RAC DR, physical standby will be in RAC before starting data guard for RAC Primary , right?.
2) While configuring RAC DR , should one node be down in standby?.
3) After creating the auxiliary database in standby, i mean restoring the rman backup from staging directory in DR,
Shall we have to register the services(database,instance,asm,etc..) to CRS(OCR)?. If yes ,Why?.
4) After DR configure over , Shall i shut/down one node?. Should all the nodes in DR be in up , while applying logs to
standby ?.
If anybody have made the setup and have the prepared document , requesting you to share with me.
Thank you very much,
Sunand

Hi Sunand,
Please follow the following My Oracle Support (MOS) Document ID:
MAA - Creating a RAC Physical Standby for a RAC Primary [ID 380449.1]
For further details, see the referred documents in previous post. Try practicing on VMWare because it will give you the flexibility for creating snapshots to save your work. Please see the answers for your question below:
Q1. In RAC DR, physical standby will be in RAC before starting data guard for RAC Primary , right?.
Answer: Yes, this is recommend but not mandatory. You can add a second node later on.
Q2. While configuring RAC DR , should one node be down in standby?
Answer: Yes, there are some database configuration commands that should be run in exclusive mode. You can start the remaining instance(s) after DB creation. Do not forget to set CLUSTER_DATABASE parameter to TRUE. Also, all instances except one should be close while performing switchover/failover.
Q3. After creating the auxiliary database in standby, i mean restoring the rman backup from staging directory in DR, Shall we have to register the services(database,instance,asm,etc..) to CRS(OCR)?. If yes ,Why?
Answer: Yes, this is recommended for RAC configuration to take advantage of high availability services.
Q4. After DR configure over , Shall i shut/down one node?. Should all the nodes in DR be in up , while applying logs to
standby ?
Answer: You can start up all the instances after DR creation. In this case if your one node goes down log apply services will continue to apply changes in DR.
Hope, this helps to clear your questions.
Regards,
Shahid

Only one instance in a RAC will start at a time

All:
I have a 4 node Oracle RAC running on RHEL AS 4 64 bit. 10.2.0.1 64 Bit
This DB was running just fine last week.
Now all of a sudden only one instance will start.
In the alert log I get an ORA-1102
crsctl shows everything good
srvctl show all node apps running
srvctl shows all ASM instances running
When the second instance starts the alert log shows the reconfiguration taking place.
Then the second instance will die after getting an ORA-1102.
I have tried deleting and re-adding all the instances with DBCA.
ocrcheck comes back fine on all nodes.
I have another RAC on the same set of HP Blades that is still hunky dorey so I don't know what is going on.
Please help.

Hi,
check the value of cluster_database parameter
it should be TRUE on all instances, also post ur alert log and trace file.
Thanks
Kuljeet

RAC DB failover from one Datacenter to Standby site

Hi,
I have 2 node 10gR2 RAC cluster running on Linux with ASM and E-business suite is configured with this 10gR2 RAC DB. Would like to setup standby site with single instance and not go with RAC for now until we procure additional hardware. Also no plans in setting up DG as solution. Does anyone has similar setup? During failover we have the capability to migrate the VIP's (names) to the failed DC but the IP's will change since there is no L2 extension b/w DC's to retain the same IP. Synchronous replication is setup at disk level using EMC SRDF
Question:
1) Will i be able to bring up the RAC DB in single instance node at second DC using non-rac code tree? IF so can anyone share whitepaper/docs on how to bring up RAC db as non-RAC environment. Logically i think it should work if i have right spfile with no RAC specific parameters.. Would like to hear from experts.
2) Wanted to minimize the configuration changes at the E-business suite level since we plan to bring the VIP's over to failed DC.
3) Does the crs registry manages information about VIP name to IP address? since my IP address will change when i migrate the VIP name from one DC to other DC. Will it be relevant at all since we plan to bring up the db in single instance mode at the failed over DC?
Any help is appreciated
Thanks

1) When you say you want to have it in a non-RAC mode. what do you mean, your current DR is a RAC however during disaster you want it to be in a non-RAC mode. Yes it would be possible, you can turn off the CLUSTER_DATABASE parameter to FALSE and bring the database as a single instance database. with this option you still will have the RAC features such as dictionaries etc however not used. the other option of completely turning of the RAC feature and getting it back to a single instance configuration may require additional steps.
which ever method you pick, you should consider the workload, will this single instance be able to handle the entire workload that originally existed on a RAC configuration.
2) VIPs dont failover outside the RAC cluster. the method normally followed is to have a database service configured on the primary and as part of a database startup trigger ensure that the database service is enabled on the DC site. There is a paper on OTN on how to do this.
3) Yes, the VIP information is stored in the OCR file.

RMAN-03002: failure of recover command

Hi all,
I am testing a new backup and restore mechanism of a 11.2 system in Linux. A third mirror of the disks from the database server has been split and mounted in a media server. An RMAN backup was taken then, on tape, using HP Data Protector. Then, in the media server again, I mounted all the disk groups and removed all the files from ASM via asmcmd. With everything cleared, I proceeded in doing the following:
1. Started up nomount using an old PFILE.
2. Initiated an RMAN session and SET DBID, connected to the target and the catalog. Restore the SPFILE in a PFILE.
3. Shutdow and started up nomount with PFILE the newly created file (edited it first to comment out CLUSTER_DATABASE parameter, as the media server is not configured for this).
4. Restored the contorl file. This was done successfully.
5. Restored the database. This was done successfully.
6. Mounted the database and attempted to recover it. I received the following error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 07/12/2013 09:42:24
RMAN-06094: datafile 1 must be restored
7. I attempted a recover from SQL*Plus; the error message was a little more helpful:
SQL> recover database using backup controlfile;
ORA-00283: recovery session canceled due to errors
ORA-01110: data file 1: '+BT1_A_SYSTEM/bt1_a/datafile/system.259.813148661'
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: '+BT1_A_SYSTEM/bt1_a/datafile/system.259.813148661'
8. I checked my source database and the file name is as it appears above. But in the restored system, the file has a different name:
ASMCMD> pwd
+BT1_A_SYSTEM/BT1_A/DATAFILE
ASMCMD> ls -l SYSTEM*
Type Redund Striped Time Sys Name
DATAFILE UNPROT COARSE JUL 11 16:00:00 Y SYSTEM.257.820514399
9. OK. I presume that this happened because we are using OMF. But, I was expecting RMAN to specify the full file names and thus restore them with their original names. The problem is now that the control file has the original file names, which cannot be found in the media server, where the restore took place. I am wondering if I should MOUNT the database after the control file restore and before I start the database restore, so RMAN might have the opportunity of renaming the file names in the control file.
Has anyone encountered this problem? I would appreciate some help.
Regards,
Takis.

That is correct Hemant. I latter realised my mistake.
When I mounted the database, the control file was opened. Then I repeated the restore. RMAN, this time was able to access the control file and rename dynamically the files, as they were restored and getting their new names.
So, I think, the correct sequence of events may be:
1, Check in ASM if the disk groups are mounted (lsdg). If not, mount the disk groups (alter diskgroup <dg_name> mount;).
2. Startup nomount (if no PFILE available, create a simple one with only db_name in it).
3. From RMAN, set DBID and then connect to target and catalog.
4. restore spfile to pfile from autobackup
5. restore control file(s) from autobackup
6. alter database mount
7. restore database
8. restore archivelog all
9. recover database
10. alter database open resetlogs
In my case, this worked, by enslarge. RMAN stopped when it run out of archived redo logs.
I then attempted, via SQL*Plus:
recover database using backup controlfile until cancel
When prompted, I typed: CANCEL
That was fine, but then, when I attempted:
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 525336576 bytes disk space from 2147483648 limit
So, I needed to increase the parameter db_recovery_file_dest_size which I did (in the pfile; luckily I had available space in the disk group). I shut down and started up (mount). Then:
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-00392: log 24 of thread 2 is being cleared, operation not allowed
ORA-00312: online log 24 thread 2: '+BT1_A_RECO'
So:
SQL> alter database clear unarchived logfile group 24;
Database altered.
SQL> alter database open resetlogs;
Database altered.
SQL> select * from dual;
D
X
Happy days!
Regards,
Takis.

Unable to start all 3 instances in RAC

Hello All,
I got the following error while trying to restart a 3 node RAC database. OEM reported two out of three nodes to be down.
We also noticed that the cluster_database parameter was set to "False" and the cluster_database_instances integer was set to 1.We changed the parameters to 'True' and '3' respectively and while trying to restart the database we get the error message as shown below. Any suggestions/help to resolve this would be appreciated.
srvctl start database -d abc123
PRCR-1079 : Failed to start resource ora.abc123.db
CRS-5017: The resource action "ora.abc123.db start" encountered the following error:
ORA-01102: cannot mount database in EXCLUSIVE mode
. For details refer to "(:CLSN00107:)" in "/oradba/app/grid/11.2.0.3_a/log/abcde104/agent/crsd/oraagent_oradba/oraagent_oradba.log".
CRS-2674: Start of 'ora.abc123.db' on 'abcde104' failed
CRS-2632: There are no more servers to try to place resource 'ora.abc123.db' on that would satisfy its placement policy
CRS-5017: The resource action "ora.abc123.db start" encountered the following error:
ORA-01102: cannot mount database in EXCLUSIVE mode
. For details refer to "(:CLSN00107:)" in "/oradba/app/grid/11.2.0.3_a/log/abcde103/agent/crsd/oraagent_oradba/oraagent_oradba.log".
CRS-2674: Start of 'ora.abc123.db' on 'abcde103' failed

Hi srsatya, thanks for your reply!
I used the alter system set cluster_database=true scope=spfile SID='*' command to change my parameter from node1.After that the restart failed. The DB is now running from node 3.
My spfile is in a shared location.
SQL> show parameter spfile;
NAME TYPE VALUE
spfile string +DATA/abc123/spfileabc123.ora
1.Login to the database and run "create pfile from spfile" , that will generate pfile in dbs folder on the server where you executed the command.
2.Shutdown all cluster database instance.Can I do this using SQLPLUS individually on each node? Or Srvctl?
3.From the node where you create pfile, open the pfile and edit cluster parameters
4.startup to nomount with new modified pfile
5.Run create spfile <+DATA/abc123/spfileabc123.ora> from pfile='Give new pfile path & file name';
My current init.ora(pfile) file points to the shared location specified above.This will overwrite my spfile with the new cluster parameters. After that can I remove the new pfile that was created?
6.shutdown the database
7.run srvctl to start all database.

Recreating control file in RAC with noresetlogs

Hi all,
I need to recreate the controlfile in a 2-node RAC environment (9i)
for altering the MAXLOGHISTORY value. I will be using noresetlogs as I
have all the online logs available with me.
I referred to metalink note (Note:118931.1) for the same, and to
clarify the same, it refers to set cluster_database to false and then
to true after creating the new controlfile.
Here I have Log Groups 1,2,5,6,7 belongs to instance1 and the rest belongs to
instance2
Below is the trace of controlfile...
create controlfile reuse database "prod" noresetlogs force logging
archivelog
maxlogfiles 64
maxlogmembers 3
maxdatafiles 800
maxinstances 32
maxloghistory 15000
logfile
group 1 '/dev/rprod_redo11' size 100m,
group 2 '/dev/rprod_redo12' size 100m,
group 3 '/dev/rprod_redo21' size 100m,
group 4 '/dev/rprod_redo22' size 100m,
group 5 '/dev/rprod_redo13' size 100m,
group 6 '/dev/rprod_redo14' size 100m,
group 7 '/dev/rprod_redo15' size 100m,
group 8 '/dev/rprod_redo23' size 100m,
group 9 '/dev/rprod_redo24' size 100m,
group 10 '/dev/rprod_redo25' size 100m
-- standby logfile
datafile
Please clarify on the same, do the traced controlfile need to have some thread info for redo logs & do I need to make the cluster_database parameter to fale/true.
Thanks!
Prat

1. Create the trace file (with Create control file statements..)
2. Edit the trace file, to remove the log groups which doesn't belong to Instance 1 (in you case you would be removing groups 3,4,8,9,10).
3. Shutdown all the instances.
4. edit the init.ora file to make CLUSTER_DATABASE=FALSE:
5. startup nomount instance 1.
6. Run the edited trace file to create the control file.
7. shutdown instance 1.
8. edit the init.ora file to make CLUSTER_DATABASE=TRUE;
9. Startup instance 1;
10. Add the log groups for the instance 2 (groups 3,4,8,9,10)
11. Add tempfiles as indicated in the trace file.
12. Enable thread 2;
13. Startup instance 2.
As always, take backups.
HTH
Thanks
Chandra

Putting a Oracle RAC in to archive log mode??

Our RAC is a 10gR2 Three(3) node RAC with a SAN as the shared storage. cluster is installed on linux. at the moment the RAC is in noarchieve log mode.
SQL> archive log list;
Database log mode No Archive Mode
Automatic archival Disabled
Archive destination /u01/app/oracle/product/10.2.
0/db_1/dbs/arch
Oldest online log sequence 665
Current log sequence 666
we created raw partitions in SAN and use ASM to manage shared storage.
when running DBCA at "specify locations for the database files to be created" step we selected "use oracle managed files" and gave database area = +DATA/
then at choose the recovery options for the database" step we ticked specify flash recovery area and gave Flash Recovery AREA = +BACKUP/ and flash recovery area = 10240 MB. we didnt click "enable archiving" option. hence the RAC DB is in NOARCHIEVELOG mode.
i found some guide to put RAC in archive log mode which i have given below....
ALTER SYSTEM SET log_archive_start=TRUE SCOPE=spfile;
ALTER SYSTEM SET log_archive_dest_1='location=/u01/oradata/MYSID/archive/' SCOPE=spfile;
ALTER SYSTEM SET log_archive_format='arch_%t_%s.arc' SCOPE=spfile;
Since we need to mount the database in exclusive mode we must also alter the following parameter:
ALTER SYSTEM SET cluster_database=FALSE SCOPE=spfile;
From the command line we can stop the entire cluster using:
srvctl stop database -d MYSID
With the cluster down we can connect to a single node and issue the following commands:
STARTUP MOUNT;
ARCHIVE LOG START;
ALTER DATABASE ARCHIVELOG;
ALTER SYSTEM SET cluster_database=TRUE SCOPE=spfile;
SHUTDOWN IMMEDIATE;
Notice that the CLUSTER_DATABASE parameter has been reset to it's original value. Since the datafiles and spfile are shared between all instances this operation only has to be done from a single node.
From the command line we can now start the cluster again using:
srvctl start database -d MYSID
my main question is about the setting of
ALTER SYSTEM SET log_archive_dest_1='location= ????? ' SCOPE=spfile;
since i have set +BACKUP/ as the FRA during installation how should i define the location of log_archive_dest_1???
many thanks in advance.
regards
Dilan

many thanks for the replies
will the command you posted send the archive logs to the "+BACKUP/" location in my SAN.
if yes how does oracle know that USE_DB_RECOVERY_FILE_DEST = BACKUP/ in my SAN. or how do i set oracle to use BACKUP/ as the USE_DB_RECOVERY_FILE_DEST??
im a newbie to RAC so pls bear with me. also at the moment i get the following outputs from my database.... pls note the bold part below, is the archive destination pointing to a location in my local server?
SQL> archive log list;
Database log mode No Archive Mode
Automatic archival Disabled
Archive destination /u01/app/oracle/product/10.2.0/db_1/dbs/arch
Oldest online log sequence 665
Current log sequence 666
SQL> show parameter db_recovery;
NAME TYPE VALUE
db_recovery_file_dest string
db_recovery_file_dest_size big integer 0
SQL> show parameter archive
NAME TYPE VALUE
archive_lag_target integer 0
log_archive_config string
log_archive_dest string
log_archive_dest_1 string
log_archive_dest_10 string
log_archive_dest_2 string
log_archive_dest_3 string
log_archive_dest_4 string
log_archive_dest_5 string
log_archive_dest_6 string
log_archive_dest_7 string
NAME TYPE VALUE
log_archive_dest_8 string
log_archive_dest_9 string
log_archive_dest_state_1 string enable
log_archive_dest_state_10 string enable
log_archive_dest_state_2 string enable
log_archive_dest_state_3 string enable
log_archive_dest_state_4 string enable
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
log_archive_dest_state_7 string enable
log_archive_dest_state_8 string enable
NAME TYPE VALUE
log_archive_dest_state_9 string enable
log_archive_duplex_dest string
log_archive_format string %t_%s_%r.dbf
log_archive_local_first boolean TRUE
log_archive_max_processes integer 2
log_archive_min_succeed_dest integer 1
log_archive_start boolean FALSE
log_archive_trace integer 0
remote_archive_enable string true
standby_archive_dest string ?/dbs/arch

Restore rac with asm

Hi,
I must restore my database with rman.
My application is an rac application with asm.
My questions are:
1- Is'it necessary to remove my datafiles on my ASM instance.
2- Is'it necessary to use srvctl stop database -d basename or can i do a shutdown immediate
My restore procedure
SQL> show parameters cluster_database
NAME TYPE VALUE
cluster_database boolean TRUE
cluster_database_instances integer 2
SQL> alter system set cluster_database=false scope=spfile sid='*';
SQL> shutdown immediate
rman target / nocatalog
RMAN> set dbid=519338572
executing command: SET DBID
RMAN> startup nomount;
restore controlfile from 'PATH/file';
RMAN> mount database;
RMAN> run { set until time="to_date('01-FEB-09 16:14:28','DD-MON-YY HH24:MI:SS')";
2> restore database;
3> recover database; }
RMAN> alter database open RESETLOGS;
database opened
RMAN> exit
SQL> alter system set cluster_database=true scope=spfile sid='*';
SQL> shutdown immediate
ORACLE instance shut down.
2) Restart the database in cluster Mode:
srvctl start database -d racdbtst
srvctl start service -d racdbtst
crs_stat –t
chkcrs
Thanks

Hello,
My questions are:
+1- Is'it necessary to remove my datafiles on my ASM instance.+
No it's not necessary to remove as you are going to overwrite them with your restore.
+2- Is'it necessary to use srvctl stop database -d basename or can i do a shutdown immediate+
Why you want to shutdown? You can shutdown both RAC instances using srvctl and with shutdown immediate you will be shutting on only one instance.
You can shutdown one of the instance and bring it up later once you are done restoring, so need to modify your cluster_database parameter.
Regards

Programmatically detect if working in RAC mode?

How can I programmatically detect if database is running in RAC mode. I found solution with dbms_utility.is_cluster_database but my boss wants to know is there any other solution. So is there :)

Hi,
If it is a RAC database, you should have several instances in v$thread :SQL> select count(distinct(instance)) from gv$thread;
COUNT(DISTINCT(INSTANCE))
                        1Or check the value of the cluster_database parameter :SQL> select name, value
2 from v$parameter
3 where name ='cluster_database';
NAME                           VALUE
cluster_database               FALSEOr count the number of instances in gv$instance:SQL> select count(*) from gv$instance;
COUNT(*)
         1

Possible to start a rac database from another standard oracle kernel ?

With oracle RAC 10g R2 :
If all nodes of a ORACLE RAC platform go down, is it possible to restart the database (with existing datafiles) from another oracle standard kernel 10g R2 ?
Thanks for help : )

That is an interesting question.. it should be possible.. you will definitely need a copy of your init.ora file. As long as the database files (control files, archive logs and redo logs) are on shared storage you should be able to start the database. Off course you will not have all the clustering features. I think it would be safe to disable the cluster database mode by setting the parameter CLUSTER_DATABASE = 'FALSE'.
hmmmm... what if you are using ASM? It could be bit more tricky in this case. Depending on the O/S and other ASM components for example ASMLib used. I think it should be possible.. never tried one though.
You may need to turn off the CLUSTER_DATABASE parameter on ASM as well.
You will need to create an ASM instance! and get the diskgroups mounted manually. if you plan to try.. do post your findings for the benefit of other readers..
Message was edited by:
Murali Vallath

Only One Signature in Msg., Please!

Is there a way to configure mail to acknowledge I have already input my signature when replying? Maybe an applescript?

Hi,
check the value of cluster_database parameter
it should be TRUE on all instances, also post ur alert log and trace file.
Thanks
Kuljeet

CONVERTING TWO NODE RAC ON WINDOWS TO SINGLE INSTANCE

I got question about a two node RAC on Windows.
One of our vendors is hosting our oracle enviroment and we are planning to bring in the datacenter in house and manage it ourselves.
Current they have a two node RACon windows
The new enviroment we are building here , we want to get rid of RAC and bring it back to a single instance environment.
How do i approach this?
1. My first option was to create a new database server and do the export dp from one of the node and import to the new single instance enviroment.
My conncern is can you do export from RAC database and import it to a non RAC enviroment?
2. My second option is to delete one node on the two node RAC and then do export dump or cold backup and copy the database files and necessary config files.
let me know how i can approach this.....

Okay guys after digging aroung i found the following approach.....
Cloning Oracle 10gR2 from RAC Environment to Single Instance Environment will raise the following error
ORA-29702: Error occurred in Cluster Group Service Operation.
The new instance is looking for CRS on new single instance non RAC environment.
For UNIX platform follow the following steps:
- Shutdown the instance which is cloned to non RAC.
- Shutdown all the listeners.
- Relink Oracle executable with rac_off option.
$ make -f ins_rdbms.mk rac_off
$ make -f ins_rdbms.mk ioracle
- Remove all the parameters from init.ora which points to second instance
and it is on other node.
- Remove cluster_database parameter
- Remove undo_tablespace parameter which points to second instance
For Windows Platform follow the following steps:
- Shutdown the instance which is cloned to non RAC.
- Shutdown all the listeners.
- Rename following file in %ORACLE_HOME%/bin directory: orarac10.dll to orarac10.dll.bak
Give me your thoughts, there is nothing on Metalink....

CLUSTER_DATABASE parameter

Similar Messages

Maybe you are looking for