3 node RAC database need to build standby database

Respected DBA's
I have create 3 node rac architecture now i want create a single instance standby database is anyone tell me the steps or any documentation to consult.
thanks

See the [ MAA Home page|http://www.oracle.com/technology/deploy/availability/htdocs/maa.htm#Database] for " [MAA 10g Setup Guide: Creating a Single Instance Physical Standby Database for a RAC Primary Database|http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10g_RACPrimarySingleInstancePhysicalStandby.pdf] "

Similar Messages

Running an external job at the specific node out of a 2 Node RAC database.

Hi. all.
I created a job , which runs an external script, by using dbms_scheduler.
Our database is 2 node RAC database(10.2.0.2.0).
The external script exists at a only one Node(Node 1).
select status,instance_id, additional_info
from dba_scheduler_job_run_details
where job_name='TEST_EXPORT_JOB'
shows that jobs which run on Node 2 failed.
Of course, the external script does not exist on Node 2.
I would like to force the job to ALWAYS run on Node 1.
How can I do that? Is there any ideas?
Locating the script on Node 2 is not the option.
Best and Regards.

Hi,
In the upcoming 11g release there is an easy solution for this - a new attribute instance_id for a job.
For 10g there is a workaround. Basically you create a service with just the one instance you want the job to run on. Then create a job class pointing to that service. Finally have your job be in the job class you just created.
If you create a service and job class per instance you can get jobs to run under whichever instance you want.
Hope this helps,
Ravi.

No response from EM on 2 node RAC database 10.2.0.3

Hi
I have configured 2 node RAC database , version 10.2.0.3 using ASM and CRS. The database and all services are running fine . And successfully completed the EM configuration on the default ports .
But when I am trying to login into the EM grid control , login page doesnt go to the Welcome page instead the username and password fields get blank . I checked the status for EM and its running fine on both nodes .
See the output from the EMCA tool :
INFO:
**************** Current Configuration ****************
INSTANCE NODE DBCONTROL_UPLOAD_HOST
SITB1 ccman_rac1 ccman_rac2
SITB2 ccman_rac2 ccman_rac2
Getting these messages in emoms.log:
2007-10-25 14:51:57,597 [JobWorker 87:Thread-14] ERROR jobs.pingCfmEMDDown pingHost.439 - TimeoutException caught pinging the
host for EMD URL http://ccman_rac1:3938/emd/main
2007-10-25 14:55:44,081 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.272 - Integration Class not found: o
racle.sysman.ias.ias.IASIntegration
2007-10-25 14:55:44,422 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.272 - Integration Class not found: o
racle.sysman.eml.target.slb.common.SLBIntegration
2007-10-25 14:55:44,531 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.272 - Integration Class not found: o
racle.sysman.eml.ssl.intg.SSLIntegration
2007-10-25 14:55:44,682 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.272 - Integration Class not found: o
racle.tip.oem.central.domain.ProcessConnectDomainIntg
2007-10-25 14:55:44,685 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.272 - Integration Class not found: o
racle.tip.oem.central.instance.ProcessConnectInstanceIntg
2007-10-25 14:55:44,688 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.272 - Integration Class not found: o
racle.webdb.admin.em.PortalIntegration
2007-10-25 14:55:44,691 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.272 - Integration Class not found: o
racle.webdb.admin.em.SSOIntegration
2007-10-25 14:55:44,694 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.272 - Integration Class not found: o
racle.reports.em.RepIntg
2007-10-25 14:55:44,717 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.272 - Integration Class not found: o
racle.sysman.ocs.mntr.target.OcsEmailIntegration
2007-10-25 14:55:44,720 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.272 - Integration Class not found: o
racle.sysman.ocs.mntr.target.OcsOidIntegration
2007-10-25 14:55:44,724 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.272 - Integration Class not found: o
racle.sysman.ocs.mntr.target.OcsOvfIntegration
2007-10-25 14:55:44,727 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.272 - Integration Class not found: o
racle.sysman.ocs.mntr.target.OcsWebconfIntegration
2007-10-25 14:55:44,729 [Orion Launcher] ERROR app.ContextInitializer contextInitialized.272 - Integration Class not found: o
racle.sysman.ocs.mntr.target.OcsWirelessIntg
Please suggest how to go ahead to resolve this issue.
Thanks in advance.
Ankur

Is this something to do with fully qualified host names ? I've been caught with EM by that before.

Modifying a service in a 3-node RAC database

Hello,
I have a 3-node rac 10.2.0.4 here under Windows 2003 x64.
I created, months ago, a service that have 1 preferred instance, and 1 available instance.
Now I have to change it, so it does not have an available instance anymore, just 1 preferred instance, because the client wants it to run only on this node.
After looking up in the 10.2 manual, I could not find the exact command to accomplish the job. Have you done this and can you shed a light ?
Thanks.

Hi, thanks for your answer, but no, each node has 2 instances only, ASM and Database.
But they changed their minds, instead of keeping togheter the service SRV3 on NODE3, now we need that, when NODE3 restart or something, and come back, the service be relocated to NODE3.
This does not happen automatically, Oracle says we have to code the "srvctl relocation" command using some callback mechanism to automate fallback. Is there an url or paper or so that explains how to do it ?
Thanks.

For 4 node RAC database on Exadata x3-2, how many scan IP I should assign?

We want to build a 4 node RAC 11gr23 on exadata x3-2. Oracle only recommend 3 ip for scan listener. by previous observation of non-exadata RAC, seems each node will spread randomly one Scan Ip address. So if we assign 3 ip to one scan listener, how that will work on a 4-node RAC?
Thanks

You're welcome
by Load balancing
Oracle RAC databases increase load balancing by using the single client access name (SCAN) for the cluster to balance connections among all instances in a cluster database. SCAN also adds location independence for the databases, so that client configuration does not have to depend on which nodes are running a particular database or database instance.
http://docs.oracle.com/cd/E11882_01/install.112/e48195/undrstnd.htm#RIWIN607
Based on the environment, the following actions occur when you use SCAN to connect to an Oracle RAC database using a service name. The numbered actions correspond to the arrows shown in Figure 7-1.
http://docs.oracle.com/cd/E11882_01/install.112/e48195/undrstnd.htm#CIHIBEIH
Regards

Enable Archivelog Mode On 2 Node RAC DATABASE

hi,
We are having 2 Node Rac 10g Database Installed on Windows.
Currently the Database is in Non Archivelog Mode.
I want to convert it to Archivelog Mode.
I come to know the steps to convert cluster database to Archivelog mode.
i.e.
set archive parameters like Disk Location and Archivelog File format.
then Convert the database in Exclusive Mode
ALTER SYSTEM SET cluster_database=FALSE SCOPE=spfile;
then
C:\> srvctl stop database -d <Global_DB_SID>
then enable Archivelog Mode.
SQL> STARTUP MOUNT;
SQL> ARCHIVE LOG START;
SQL> ALTER DATABASE ARCHIVELOG;
SQL> ALTER DATABASE SET cluster_database=TRUE SCOPE=spfile;
SQL> SHUTDOWN IMMEDIATE
C:\> srvctl start database -d <Global_DB_SID>
But I am confuse with Do i need to RUN this commands in both the nodes seperatly or only on any one node.
Please Reply,

comments embeddedf
Node 1: OSERP1
Log on to OSERP1 Server
C:\> sqlplus sys/oracle@racdb2 as sysdba
SQL> ALTER SYSTEM SET log_archive_format='arch_%t_%s.arc' SCOPE=spfile ; -- this needs to be database wide
SQL > ALTER SYSTEM SET log_archive_dest_1='location=\\OSERP1\archive$\ERP1 ' SCOPE=spfile sid ='ERP1'; -- required quotes added
-- not required
SQL> ALTER SYSTEM SET cluster_database=FALSE SCOPE=spfile;
not required to connect to other node
-- not required
SQL> ALTER SYSTEM SET log_archive_format='arch_%t_%s.arc' SCOPE=spfile sid =ERP2;
SQL > ALTER SYSTEM SET log_archive_dest_1='location=\\OSERP2\archive$\ERP2 ' SCOPE=spfile sid ='ERP2'; -- quotes added
-- not required, and database wide setting
SQL> ALTER SYSTEM SET cluster_database=FALSE SCOPE=spfile;
Then following commands will be run connecting any of the instance
-- database has to be stopped first, if you stick to switching it to a non-cluster database
C:\> set ORACLE_SID=<local_instance_id>
C:\> sqlplus / as sysdba
SQL> STARTUP MOUNT;
-- wrong sequence of commands
SQL> ARCHIVE LOG START;
SQL> ALTER DATABASE ARCHIVELOG;
-- not required (see previous steps)
SQL> ALTER DATABASE SET cluster_database=TRUE SCOPE=spfile;
SQL> SHUTDOWN IMMEDIATE;
6. Start the cluster database.
C:\> srvctl start database -d <Global_DB_SID>
-- There is no such thing as a <Global_DB_SID>. There is a database name.
Please note your tnsnames.ora, in a standard install, needs to have the following service names.
ERP
ERP1
ERP2
I'm not sure why you have the non-standard service_name racdb2.
Somehow it looks like you both don't understand the RAC concept, and didn't understand my answer. I had to correct several things I already corrected in my previous response. I'm not sure why I'm not getting through.
Sybrand Bakker
Senior Oracle DBA

Single-instance manual standby for a three-node RAC database

Hi all,
I am wondering how it is possible to create a manual standby database for a rac primary database.
Oracle versione is standard edition 11.1.
I have experience creating and managing manual standby for single-instance database; I am wondering if and how I can instruct the single-instance standby database to discover and apply the three redo threads that I will copy from the primary site to the standby site.
Should I use rman to catalog all the archived log on the standby site ?
Should I configure many LOG_ARCHIVE_DEST_n parameters to point to many different path, one for each primary instance (i.e. one for each redo thread), and let rman automagically discover all the archived logs ?
Should I configure only LOG_ARCHIVE_DEST_1 , put archivelogs from all threads in the same folder, and let rman automagically discover all the archived logs ?
Thanks for every answer!
Andrea

Hi,
indeed i catalog all transfered archive logs in front of the recover process.
During the tests i believe (iirc) i was unable to recover from transfered archivelogs without catalog them first. But this statement is out of my mind, i am not 100% sure for this, sorry.
Some more details.
Because it is a standard edition, i have to use on the RAC side ASM. So our normal scripts to transfer archivelogs from primary to standby are obsolete.
So i decided to put the whole standby thing into the database. Now the primary database uses external scheduler jobs to do the work. The standby side is not using ASM, so there is no need to handle the logs in any special way.
The steps are:
1. Get SCN from primary and standby
2. Transfer the logs for the gap from ASM to "normal" filesystem.
3. Transfer (and compress, if not in LAN) to standby archive dest
4. Catalog on standby side
5. Recover on standby side
6. Delete on normal filesystem (on both sides, but on standby with a delay of 2 days just to be sure)
The steps on the standby side are both using the primary scn from step 1 as a parameter to avoid error messages during the catalog or recover call.
Hth
Joerg

Archive log mode in 3 node rac database

Sir I am using oracle 10.2.0.1 and created 3 node cluster setup on.OS i am using linux 4
I am too much confuse in setting up this cluster in archive log mode bec why we need to false cluater_database parameter to setup cluster in archive log mode.
I have search lot of documents but all are saying we not need setting this parameter flase perior to 10.2.But what is the actual concept behind setting this parameter to false in early release and why we need not to set it false.Please help me.
I know how to set up in archive log mode but this parameter create confusion.
Thanks sir in advance

I also dont't know all the details about this but I'll try to explain what I know. Setting cluster_database to false in a rac environment is usually done when you need to mount the database from one instance exclusively. This is still needed when you upgrade the catalog, for example during release update (from 10.2.0.1 to 10.2.0.4 for example). Now with switching archivelog mode someone at oracle must have discovered that it is sufficient when the database is mounted by only one instance and you can actually save one step.
As I (and propably most of you) don't switch archiving on or off on a daily basis, I don't worry about this a lot, simply turn this on when I create a new database and then leave it on forever.
Bjoern

Error in creating control file for 2 node RAC database

SQL> CREATE CONTROLFILE set DATABASE "SBLS" RESETLOGS NOARCHIVELOG
2 MAXLOGFILES 192
3 MAXLOGMEMBERS 3
4 MAXDATAFILES 1024
5 MAXINSTANCES 32
6 MAXLOGHISTORY 292
7 DATAFILE
8 '+SBLDATA/SBLTST/DATAFILE/system.dbf'
9 '+SBLDATA/SBLTST/DATAFILE/sysaux.dbf'
10 '+SBLDATA/SBLTST/DATAFILE/undotbs1.dbf'
11 '+SBLDATA/SBLTST/DATAFILE/undotbs2.dbf'
12 '+SBLDATA/SBLTST/DATAFILE/users.dbf'
13 '+SBLDATA/SBLTST/DATAFILE/sbl_data.dbf'
14 '+SBLDATA/SBLTST/DATAFILE/sbl_idx.dbf';
'+SBLDATA/SBLTST/DATAFILE/sysaux.dbf'
ERROR at line 9:
ORA-01967: invalid option for CREATE CONTROLFILE
Please advice.

ASMCMD> pwd
+sblDATA/SBLTST/DATAFILE
ASMCMD> ls -l
Type Redund Striped Time Sys Name
DATAFILE UNPROT COARSE MAY 29 14:00:00 Y SBL_DATA.258.815440497
DATAFILE UNPROT COARSE MAY 29 14:00:00 Y SBL_IDX.259.815441389
DATAFILE UNPROT COARSE DEC 26 11:00:00 Y SYSAUX.272.802440861
DATAFILE UNPROT COARSE MAY 29 14:00:00 Y SYSAUX.282.804173239
DATAFILE UNPROT COARSE MAY 29 13:00:00 Y SYSTEM.262.804173239
DATAFILE UNPROT COARSE DEC 26 11:00:00 Y SYSTEM.271.802440859
DATAFILE UNPROT COARSE MAY 29 14:00:00 Y UNDOTBS1.270.804173239
DATAFILE UNPROT COARSE DEC 26 11:00:00 Y UNDOTBS1.273.802440861
DATAFILE UNPROT COARSE MAY 29 14:00:00 Y UNDOTBS2.265.804173409
DATAFILE UNPROT COARSE DEC 26 11:00:00 Y UNDOTBS2.279.802441035
DATAFILE UNPROT COARSE MAY 29 14:00:00 Y USERS.264.804173239
DATAFILE UNPROT COARSE DEC 26 11:00:00 Y USERS.274.802440861
N sbl_data.dbf => +SBLDATA/SBLTST/DATAFILE/SBL_DATA.258.815440497
N sbl_idx.dbf => +SBLDATA/SBLTST/DATAFILE/SBL_IDX.259.815441389

Single instance standby for 2-node RAC

Hi,
Oracle Version:11.2.0.1
Operating system:Linux
Here i am planing to create single instance standby for my 2-node RAC database.Here i am creating my single instance standby database on 1-node of my 2-node RAC DB.
1.) Do i need to configure any separate listener for my single instance standby in $ORACLE_HOME/network/admin in ORACLE user or need to change in Grid user login.
2.) Below is the error when i am duplicating my primary 2-Node RAC to single instance DB. And it is shutting down my auxiliary instance.
[oracle@rac1 ~]$ rman target / auxiliary sys/racdba123@stand
Recovery Manager: Release 11.2.0.1.0 - Production on Sun Aug 28 13:32:29 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: RACDB (DBID=755897741)
connected to auxiliary database: RACDB (not mounted)
RMAN> duplicate database racdba to stand
2> ;
Starting Duplicate Db at 28-AUG-11
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=6 device type=DISK
contents of Memory Script:
   sql clone "create spfile from memory";
executing Memory Script
sql statement: create spfile from memory
contents of Memory Script:
   shutdown clone immediate;
   startup clone nomount;
executing Memory Script
Oracle instance shut down
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 08/28/2011 13:33:55
RMAN-03015: error occurred in stored script Memory Script
RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptorAlso find my listener services.
[oracle@rac1 ~]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 29-AUG-2011 10:56:24
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date                18-AUG-2011 10:35:07
Uptime                    11 days 0 hr. 21 min. 17 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /u01/11.2.0/grid/network/admin/listener.ora
Listener Log File         /u01/app/oracle/diag/tnslsnr/rac1/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.8.123)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.8.127)(PORT=1521)))
Services Summary...
Service "+ASM" has 1 instance(s).
Instance "+ASM1", status READY, has 1 handler(s) for this service...
Service "RACDB" has 1 instance(s).
Instance "RACDB1", status READY, has 1 handler(s) for this service...
Service "RACDBXDB" has 1 instance(s).
Instance "RACDB1", status READY, has 1 handler(s) for this service...
Service "stand" has 2 instance(s).
Instance "stand", status UNKNOWN, has 1 handler(s) for this service...
Instance "stand", status BLOCKED, has 1 handler(s) for this service...
Service "testdb" has 1 instance(s).
Instance "RACDB1", status READY, has 1 handler(s) for this service...
Service "testdb1" has 1 instance(s).
Instance "RACDB1", status READY, has 1 handler(s) for this service...
The command completed successfully
[oracle@rac1 ~]$ lsnrctl services
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 29-AUG-2011 10:56:35
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
Services Summary...
Service "+ASM" has 1 instance(s).
Instance "+ASM1", status READY, has 1 handler(s) for this service...
    Handler(s):
      "DEDICATED" established:0 refused:0 state:ready
         LOCAL SERVER
Service "RACDB" has 1 instance(s).
Instance "RACDB1", status READY, has 1 handler(s) for this service...
    Handler(s):
      "DEDICATED" established:3 refused:0 state:ready
         LOCAL SERVER
Service "RACDBXDB" has 1 instance(s).
Instance "RACDB1", status READY, has 1 handler(s) for this service...
    Handler(s):
      "D000" established:0 refused:0 current:0 max:1022 state:ready
         DISPATCHER <machine: rac1.qfund.net, pid: 3975>
         (ADDRESS=(PROTOCOL=tcp)(HOST=rac1.qfund.net)(PORT=43731))
Service "stand" has 2 instance(s).
Instance "stand", status UNKNOWN, has 1 handler(s) for this service...
    Handler(s):
      "DEDICATED" established:0 refused:0
         LOCAL SERVER
Instance "stand", status BLOCKED, has 1 handler(s) for this service...
    Handler(s):
      "DEDICATED" established:669 refused:0 state:ready
         LOCAL SERVER
Service "testdb" has 1 instance(s).
Instance "RACDB1", status READY, has 1 handler(s) for this service...
    Handler(s):
      "DEDICATED" established:3 refused:0 state:ready
         LOCAL SERVER
Service "testdb1" has 1 instance(s).
Instance "RACDB1", status READY, has 1 handler(s) for this service...
    Handler(s):
      "DEDICATED" established:3 refused:0 state:ready
         LOCAL SERVER
The command completed successfully
[oracle@rac1 ~]$Tnsnames.ora file content.
RACDB =
(DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = racdb-scan.qfund.net)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = RACDB)
#QFUNDRAC =
stand =
(DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST= racdb-scan.qfund.net)(PORT = 1521))
    (CONNECT_DATA =
      (SERVICE_NAME = stand)
      (UR = A)
)Please help me how to solve this problem.
Thanks & Regards,
Poorna Prasad.S

Hi,
Please find the output from v$dataguard_status from primary and standby
Primary
SQL> select message from v$dataguard_status;
MESSAGE
ARC0: Archival started
ARCH: LGWR is scheduled to archive destination LOG_ARCHIVE_DEST_2 after log swit
ch
ARCH: Beginning to archive thread 1 sequence 214 (4604093-4604095)
Error 12514 received logging on to the standby
ARCH: Error 12514 Creating archive log file to 'stand'
ARCH: Completed archiving thread 1 sequence 214 (4604093-4604095)
ARC1: Archival started
ARC2: Archival started
ARC3: Archival started
MESSAGE
ARC4: Archival started
ARC5: Archival started
ARC6: Archival started
ARC7: Archival started
ARC8: Archival started
ARC9: Archival started
ARCa: Archival started
ARCb: Archival started
ARCc: Archival started
ARCd: Archival started
ARCe: Archival started
MESSAGE
ARCf: Archival started
ARCg: Archival started
ARCh: Archival started
ARCi: Archival started
ARCj: Archival started
ARCk: Archival started
ARCl: Archival started
ARCm: Archival started
ARCn: Archival started
ARCo: Archival started
ARCp: Archival started
MESSAGE
ARCq: Archival started
ARCr: Archival started
ARCs: Archival started
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
ARC2: Becoming the heartbeat ARCH
ARC7: Beginning to archive thread 1 sequence 215 (4604095-4604191)
ARC7: Completed archiving thread 1 sequence 215 (4604095-4604191)
ARC5: Beginning to archive thread 1 sequence 216 (4604191-4604471)
ARC5: Completed archiving thread 1 sequence 216 (4604191-4604471)
ARCt: Archival started
MESSAGE
ARC3: Beginning to archive thread 1 sequence 217 (4604471-4605358)
ARC3: Completed archiving thread 1 sequence 217 (4604471-4605358)
LNS: Standby redo logfile selected for thread 1 sequence 217 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 217
LNS: Completed archiving log 1 thread 1 sequence 217
LNS: Standby redo logfile selected for thread 1 sequence 218 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 218
MESSAGE
LNS: Completed archiving log 2 thread 1 sequence 218
ARC4: Beginning to archive thread 1 sequence 218 (4605358-4625984)
ARC4: Completed archiving thread 1 sequence 218 (4605358-4625984)
LNS: Standby redo logfile selected for thread 1 sequence 219 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 219
LNS: Completed archiving log 1 thread 1 sequence 219
ARC5: Beginning to archive thread 1 sequence 219 (4625984-4641358)
ARC5: Completed archiving thread 1 sequence 219 (4625984-4641358)
LNS: Standby redo logfile selected for thread 1 sequence 220 for destination LOG
MESSAGE
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 220
LNS: Completed archiving log 2 thread 1 sequence 220
ARC6: Beginning to archive thread 1 sequence 220 (4641358-4644757)
ARC6: Completed archiving thread 1 sequence 220 (4641358-4644757)
LNS: Standby redo logfile selected for thread 1 sequence 221 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 221
LNS: Completed archiving log 1 thread 1 sequence 221
MESSAGE
ARC7: Beginning to archive thread 1 sequence 221 (4644757-4648306)
ARC7: Completed archiving thread 1 sequence 221 (4644757-4648306)
LNS: Standby redo logfile selected for thread 1 sequence 222 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 222
LNS: Completed archiving log 2 thread 1 sequence 222
ARC8: Beginning to archive thread 1 sequence 222 (4648306-4655287)
ARC8: Completed archiving thread 1 sequence 222 (4648306-4655287)
LNS: Standby redo logfile selected for thread 1 sequence 223 for destination LOG
_ARCHIVE_DEST_2
MESSAGE
LNS: Beginning to archive log 1 thread 1 sequence 223
LNS: Completed archiving log 1 thread 1 sequence 223
ARC9: Beginning to archive thread 1 sequence 223 (4655287-4655307)
ARC9: Completed archiving thread 1 sequence 223 (4655287-4655307)
LNS: Standby redo logfile selected for thread 1 sequence 224 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 224
LNS: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3135)
LNS: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
MESSAGE
Error 3135 for archive log file 2 to 'stand'
LNS: Failed to archive log 2 thread 1 sequence 224 (3135)
ARC3: Beginning to archive thread 1 sequence 224 (4655307-4660812)
ARC3: Completed archiving thread 1 sequence 224 (4655307-4660812)
LNS: Standby redo logfile selected for thread 1 sequence 224 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 224
LNS: Completed archiving log 2 thread 1 sequence 224
LNS: Standby redo logfile selected for thread 1 sequence 225 for destination LOG
_ARCHIVE_DEST_2
MESSAGE
LNS: Beginning to archive log 1 thread 1 sequence 225
LNS: Completed archiving log 1 thread 1 sequence 225
ARC4: Beginning to archive thread 1 sequence 225 (4660812-4660959)
ARC4: Completed archiving thread 1 sequence 225 (4660812-4660959)
LNS: Standby redo logfile selected for thread 1 sequence 226 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 226
LNS: Completed archiving log 2 thread 1 sequence 226
ARC5: Beginning to archive thread 1 sequence 226 (4660959-4664925)
MESSAGE
LNS: Standby redo logfile selected for thread 1 sequence 227 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 227
ARC5: Completed archiving thread 1 sequence 226 (4660959-4664925)
LNS: Completed archiving log 1 thread 1 sequence 227
LGWR: Error 1089 closing archivelog file 'stand'
ARC6: Beginning to archive thread 1 sequence 227 (4664925-4668448)
ARC6: Completed archiving thread 1 sequence 227 (4664925-4668448)
ARC5: Beginning to archive thread 1 sequence 228 (4668448-4670392)
ARC5: Completed archiving thread 1 sequence 228 (4668448-4670392)
MESSAGE
LNS: Standby redo logfile selected for thread 1 sequence 228 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 228
LNS: Completed archiving log 2 thread 1 sequence 228
ARC4: Standby redo logfile selected for thread 1 sequence 227 for destination LO
G_ARCHIVE_DEST_2
LNS: Standby redo logfile selected for thread 1 sequence 229 for destination LOG
_ARCHIVE_DEST_2
MESSAGE
LNS: Beginning to archive log 1 thread 1 sequence 229
LNS: Completed archiving log 1 thread 1 sequence 229
ARC3: Beginning to archive thread 1 sequence 229 (4670392-4670659)
ARC3: Completed archiving thread 1 sequence 229 (4670392-4670659)
LNS: Standby redo logfile selected for thread 1 sequence 230 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 230
LNS: Completed archiving log 2 thread 1 sequence 230
ARC4: Beginning to archive thread 1 sequence 230 (4670659-4670679)
ARC4: Completed archiving thread 1 sequence 230 (4670659-4670679)
MESSAGE
LNS: Standby redo logfile selected for thread 1 sequence 231 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 231
LNS: Completed archiving log 1 thread 1 sequence 231
ARC5: Beginning to archive thread 1 sequence 231 (4670679-4690371)
ARC5: Completed archiving thread 1 sequence 231 (4670679-4690371)
LNS: Standby redo logfile selected for thread 1 sequence 232 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 232
MESSAGE
LNS: Completed archiving log 2 thread 1 sequence 232
ARC6: Beginning to archive thread 1 sequence 232 (4690371-4712566)
ARC6: Completed archiving thread 1 sequence 232 (4690371-4712566)
LNS: Standby redo logfile selected for thread 1 sequence 233 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 233
LNS: Completed archiving log 1 thread 1 sequence 233
ARC7: Beginning to archive thread 1 sequence 233 (4712566-4731626)
LNS: Standby redo logfile selected for thread 1 sequence 234 for destination LOG
_ARCHIVE_DEST_2
MESSAGE
LNS: Beginning to archive log 2 thread 1 sequence 234
ARC7: Completed archiving thread 1 sequence 233 (4712566-4731626)
LNS: Completed archiving log 2 thread 1 sequence 234
ARC8: Beginning to archive thread 1 sequence 234 (4731626-4753780)
LNS: Standby redo logfile selected for thread 1 sequence 235 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 235
ARC8: Completed archiving thread 1 sequence 234 (4731626-4753780)
LNS: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3135)
MESSAGE
LNS: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
Error 3135 for archive log file 1 to 'stand'
LNS: Failed to archive log 1 thread 1 sequence 235 (3135)
ARC9: Beginning to archive thread 1 sequence 235 (4753780-4765626)
ARC9: Completed archiving thread 1 sequence 235 (4753780-4765626)
LNS: Standby redo logfile selected for thread 1 sequence 235 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 235
LNS: Completed archiving log 1 thread 1 sequence 235
LNS: Standby redo logfile selected for thread 1 sequence 236 for destination LOG
MESSAGE
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 236
LNS: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3135)
LNS: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
Error 3135 for archive log file 2 to 'stand'
LNS: Failed to archive log 2 thread 1 sequence 236 (3135)
ARCa: Beginning to archive thread 1 sequence 236 (4765626-4768914)
ARCa: Completed archiving thread 1 sequence 236 (4765626-4768914)
LNS: Standby redo logfile selected for thread 1 sequence 236 for destination LOG
_ARCHIVE_DEST_2
MESSAGE
LNS: Beginning to archive log 2 thread 1 sequence 236
LNS: Completed archiving log 2 thread 1 sequence 236
LNS: Standby redo logfile selected for thread 1 sequence 237 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 237
LNS: Completed archiving log 1 thread 1 sequence 237
ARCb: Beginning to archive thread 1 sequence 237 (4768914-4770603)
ARCb: Completed archiving thread 1 sequence 237 (4768914-4770603)
LNS: Standby redo logfile selected for thread 1 sequence 238 for destination LOG
MESSAGE
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 238
LNS: Completed archiving log 2 thread 1 sequence 238
ARCc: Beginning to archive thread 1 sequence 238 (4770603-4770651)
ARCc: Completed archiving thread 1 sequence 238 (4770603-4770651)
LNS: Standby redo logfile selected for thread 1 sequence 239 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 239
LNS: Completed archiving log 1 thread 1 sequence 239
MESSAGE
ARCd: Beginning to archive thread 1 sequence 239 (4770651-4773918)
ARCd: Completed archiving thread 1 sequence 239 (4770651-4773918)
LNS: Standby redo logfile selected for thread 1 sequence 240 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 240
LNS: Completed archiving log 2 thread 1 sequence 240
ARCe: Beginning to archive thread 1 sequence 240 (4773918-4773976)
ARCe: Completed archiving thread 1 sequence 240 (4773918-4773976)
LNS: Standby redo logfile selected for thread 1 sequence 241 for destination LOG
_ARCHIVE_DEST_2
MESSAGE
LNS: Beginning to archive log 1 thread 1 sequence 241
LNS: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3135)
LNS: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
Error 3135 for archive log file 1 to 'stand'
LNS: Failed to archive log 1 thread 1 sequence 241 (3135)
ARC3: Beginning to archive thread 1 sequence 241 (4773976-4774673)
ARC3: Completed archiving thread 1 sequence 241 (4773976-4774673)
LNS: Standby redo logfile selected for thread 1 sequence 241 for destination LOG
_ARCHIVE_DEST_2
MESSAGE
LNS: Beginning to archive log 1 thread 1 sequence 241
LNS: Completed archiving log 1 thread 1 sequence 241
LNS: Standby redo logfile selected for thread 1 sequence 242 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 242
LNS: Completed archiving log 2 thread 1 sequence 242
ARC4: Beginning to archive thread 1 sequence 242 (4774673-4776045)
ARC4: Completed archiving thread 1 sequence 242 (4774673-4776045)
LNS: Standby redo logfile selected for thread 1 sequence 243 for destination LOG
_ARCHIVE_DEST_2
MESSAGE
LNS: Beginning to archive log 1 thread 1 sequence 243
LNS: Completed archiving log 1 thread 1 sequence 243
ARC5: Beginning to archive thread 1 sequence 243 (4776045-4776508)
ARC5: Completed archiving thread 1 sequence 243 (4776045-4776508)
LNS: Standby redo logfile selected for thread 1 sequence 244 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 244
LNS: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3135)
LNS: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
MESSAGE
Error 3135 for archive log file 2 to 'stand'
LNS: Failed to archive log 2 thread 1 sequence 244 (3135)
ARC6: Beginning to archive thread 1 sequence 244 (4776508-4778741)
ARC6: Completed archiving thread 1 sequence 244 (4776508-4778741)
ARC7: Beginning to archive thread 1 sequence 245 (4778741-4778781)
ARC7: Completed archiving thread 1 sequence 245 (4778741-4778781)
ARC8: Beginning to archive thread 1 sequence 246 (4778781-4778787)
ARC8: Completed archiving thread 1 sequence 246 (4778781-4778787)
ARC9: Standby redo logfile selected for thread 1 sequence 244 for destination LO
G_ARCHIVE_DEST_2
MESSAGE
ARC3: Beginning to archive thread 1 sequence 247 (4778787-4778934)
LNS: Standby redo logfile selected for thread 1 sequence 247 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 247
ARC3: Completed archiving thread 1 sequence 247 (4778787-4778934)
LNS: Completed archiving log 1 thread 1 sequence 247
LNS: Standby redo logfile selected for thread 1 sequence 248 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 248
MESSAGE
ARC4: Beginning to archive thread 1 sequence 248 (4778934-4781018)
LNS: Completed archiving log 2 thread 1 sequence 248
ARC4: Completed archiving thread 1 sequence 248 (4778934-4781018)
LNS: Standby redo logfile selected for thread 1 sequence 249 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 249
LNS: Completed archiving log 1 thread 1 sequence 249
ARC5: Beginning to archive thread 1 sequence 249 (4781018-4781033)
ARC5: Completed archiving thread 1 sequence 249 (4781018-4781033)
LNS: Standby redo logfile selected for thread 1 sequence 250 for destination LOG
MESSAGE
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 250
233 rows selected.
SQL>Standby
SQL> select message from v$dataguard_status;
MESSAGE
ARC0: Archival started
ARC1: Archival started
ARC2: Archival started
ARC3: Archival started
ARC4: Archival started
ARC5: Archival started
ARC6: Archival started
ARC7: Archival started
ARC8: Archival started
ARC9: Archival started
ARCa: Archival started
MESSAGE
ARCb: Archival started
ARCc: Archival started
ARCd: Archival started
ARCe: Archival started
ARCf: Archival started
ARCg: Archival started
ARCh: Archival started
ARCi: Archival started
ARCj: Archival started
ARCk: Archival started
ARCl: Archival started
MESSAGE
ARCm: Archival started
ARCn: Archival started
ARCo: Archival started
ARCp: Archival started
ARCq: Archival started
ARCr: Archival started
ARCs: Archival started
ARC1: Becoming the 'no FAL' ARCH
ARC2: Becoming the heartbeat ARCH
Error 1017 received logging on to the standby
FAL[client, ARC2]: Error 16191 connecting to RACDB for fetching gap sequence
MESSAGE
ARCt: Archival started
Attempt to start background Managed Standby Recovery process
MRP0: Background Managed Standby Recovery process started
Managed Standby Recovery starting Real Time Apply
Media Recovery Log /u02/stand/archive/1_119_758280976.arc
Media Recovery Waiting for thread 2 sequence 183
RFS[1]: Assigned to RFS process 30110
RFS[1]: Identified database type as 'physical standby': Client is ARCH pid 25980
RFS[2]: Assigned to RFS process 30118
RFS[2]: Identified database type as 'physical standby': Client is ARCH pid 26008
RFS[3]: Assigned to RFS process 30124
MESSAGE
RFS[3]: Identified database type as 'physical standby': Client is ARCH pid 26029
RFS[4]: Assigned to RFS process 30130
RFS[4]: Identified database type as 'physical standby': Client is ARCH pid 26021
ARC4: Beginning to archive thread 1 sequence 244 (4776508-4778741)
ARC4: Completed archiving thread 1 sequence 244 (0-0)
RFS[5]: Assigned to RFS process 30144
RFS[5]: Identified database type as 'physical standby': Client is LGWR ASYNC pid
26128
Primary database is in MAXIMUM PERFORMANCE mode
ARC5: Beginning to archive thread 1 sequence 247 (4778787-4778934)
MESSAGE
ARC5: Completed archiving thread 1 sequence 247 (0-0)
ARC6: Beginning to archive thread 1 sequence 248 (4778934-4781018)
ARC6: Completed archiving thread 1 sequence 248 (0-0)
ARC7: Beginning to archive thread 1 sequence 249 (4781018-4781033)
ARC7: Completed archiving thread 1 sequence 249 (0-0)
58 rows selected.
SQL>also find the output for the primary alertlog file.
Tue Aug 30 10:45:41 2011
LNS: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3135)
LNS: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
Errors in file /u01/app/oracle/diag/rdbms/racdb/RACDB1/trace/RACDB1_nsa2_26128.trc:
ORA-03135: connection lost contact
Error 3135 for archive log file 2 to 'stand'
Errors in file /u01/app/oracle/diag/rdbms/racdb/RACDB1/trace/RACDB1_nsa2_26128.trc:
ORA-03135: connection lost contact
LNS: Failed to archive log 2 thread 1 sequence 244 (3135)
Errors in file /u01/app/oracle/diag/rdbms/racdb/RACDB1/trace/RACDB1_nsa2_26128.trc:
ORA-03135: connection lost contact
Tue Aug 30 10:50:25 2011
Thread 1 advanced to log sequence 245 (LGWR switch)
Current log# 1 seq# 245 mem# 0: +ASM_DATA1/racdb/onlinelog/group_1.268.758280977
Current log# 1 seq# 245 mem# 1: +ASM_DATA2/racdb/onlinelog/group_1.265.758280979
Tue Aug 30 10:50:25 2011
Archived Log entry 612 added for thread 1 sequence 244 ID 0x2d0e0689 dest 1:
Thread 1 cannot allocate new log, sequence 246
Checkpoint not complete
Current log# 1 seq# 245 mem# 0: +ASM_DATA1/racdb/onlinelog/group_1.268.758280977
Current log# 1 seq# 245 mem# 1: +ASM_DATA2/racdb/onlinelog/group_1.265.758280979
Thread 1 advanced to log sequence 246 (LGWR switch)
Current log# 2 seq# 246 mem# 0: +ASM_DATA1/racdb/onlinelog/group_2.269.758280979
Current log# 2 seq# 246 mem# 1: +ASM_DATA2/racdb/onlinelog/group_2.266.758280981
Tue Aug 30 10:50:27 2011
Archived Log entry 613 added for thread 1 sequence 245 ID 0x2d0e0689 dest 1:
Thread 1 cannot allocate new log, sequence 247
Checkpoint not complete
Current log# 2 seq# 246 mem# 0: +ASM_DATA1/racdb/onlinelog/group_2.269.758280979
Current log# 2 seq# 246 mem# 1: +ASM_DATA2/racdb/onlinelog/group_2.266.758280981
Thread 1 advanced to log sequence 247 (LGWR switch)
Current log# 1 seq# 247 mem# 0: +ASM_DATA1/racdb/onlinelog/group_1.268.758280977
Current log# 1 seq# 247 mem# 1: +ASM_DATA2/racdb/onlinelog/group_1.265.758280979
Tue Aug 30 10:50:30 2011
Archived Log entry 614 added for thread 1 sequence 246 ID 0x2d0e0689 dest 1:
Tue Aug 30 10:51:37 2011
ARC9: Standby redo logfile selected for thread 1 sequence 244 for destination LOG_ARCHIVE_DEST_2
Tue Aug 30 10:51:39 2011
Thread 1 advanced to log sequence 248 (LGWR switch)
Current log# 2 seq# 248 mem# 0: +ASM_DATA1/racdb/onlinelog/group_2.269.758280979
Current log# 2 seq# 248 mem# 1: +ASM_DATA2/racdb/onlinelog/group_2.266.758280981
Tue Aug 30 10:51:39 2011
Archived Log entry 620 added for thread 1 sequence 247 ID 0x2d0e0689 dest 1:
Tue Aug 30 10:51:39 2011
LNS: Standby redo logfile selected for thread 1 sequence 247 for destination LOG_ARCHIVE_DEST_2
LNS: Standby redo logfile selected for thread 1 sequence 248 for destination LOG_ARCHIVE_DEST_2
Tue Aug 30 11:08:27 2011
Thread 1 advanced to log sequence 249 (LGWR switch)
Current log# 1 seq# 249 mem# 0: +ASM_DATA1/racdb/onlinelog/group_1.268.758280977
Current log# 1 seq# 249 mem# 1: +ASM_DATA2/racdb/onlinelog/group_1.265.758280979
Tue Aug 30 11:08:27 2011
Archived Log entry 622 added for thread 1 sequence 248 ID 0x2d0e0689 dest 1:
Tue Aug 30 11:08:27 2011
LNS: Standby redo logfile selected for thread 1 sequence 249 for destination LOG_ARCHIVE_DEST_2
Thread 1 cannot allocate new log, sequence 250
Checkpoint not complete
Current log# 1 seq# 249 mem# 0: +ASM_DATA1/racdb/onlinelog/group_1.268.758280977
Current log# 1 seq# 249 mem# 1: +ASM_DATA2/racdb/onlinelog/group_1.265.758280979
Thread 1 advanced to log sequence 250 (LGWR switch)
Current log# 2 seq# 250 mem# 0: +ASM_DATA1/racdb/onlinelog/group_2.269.758280979
Current log# 2 seq# 250 mem# 1: +ASM_DATA2/racdb/onlinelog/group_2.266.758280981
Tue Aug 30 11:08:31 2011
Archived Log entry 624 added for thread 1 sequence 249 ID 0x2d0e0689 dest 1:
LNS: Standby redo logfile selected for thread 1 sequence 250 for destination LOG_ARCHIVE_DEST_2Thanks & Regards,
Poorna Prasad.S

Question about DBCA generate script o create RAC database 2 node cluster

Question about creating two node RAC database 11g after installing and configuration 11g clusterware. I've used DBCA to generate script to create a rac database. I've set
environment variable ORACLE_SID=RAC and the creating script creates instance of RAC1 and RAC2. My understanding is that each node will represent a node, however there should only be one database with a name of 'RAC'. Please advise

You are getting your terminology mixed up.
You only have one database. Take a look, there are one set of datafiles on shared storage.
You have 2 instances which are accessing one database.
Database name is RAC. Instance names are RAC1, RAC2, etc, etc.
Also, if you look at the listener configuration and if your tnsnames is setup properly then connecting to RAC will connect you to either one of the instances wheras connecting to RAC1 will connect you to that instance.

Datagurad setup from 2 Node RAC to single instance (DR site)

Dear Expert,
I have request from management to setup the DR site from current production RAC database using active dataguard. I have two node rac database 11.2.0.3 running on sun solaris machine. I need proper step or good document can refer to setup between production RAC database to DR site single instance standby database. I only experience setup single instance to single instance .Apreciate expert can provide me some link
Regard
liang

Hello;
This will provide a good start and overview :
Creating a Single Instance Physical Standby for a RAC Primary : ( please note parameter changes for Oracle 11 )
http://www.oracle.com/technetwork/database/features/availability/maa-wp-10g-racprimarysingleinstance-131970.pdf
As will this :
http://oracleinstance.blogspot.com/2012/01/create-single-instance-standby-database.html
Oracle 11
Rapid Oracle RAC Standby Deployment: Oracle Database 11g Release 2
http://www.oracle.com/technetwork/database/features/availability/maa-wp-11g-rac-standby-133152.pdf
Best Regards
mseberg

Rac thread ARCs to single standby

We're testing a new 2-node RAC with a single-instance standby server. Since we only have standard edition, we don't have Data Guard available - we FTP the archive logs for both RAC threads out of ASM into a local directory and apply them to the standby with 'RECOVER AUTOMATIC STANDBY DATABASE'.
However, when one of the RAC nodes is down, the standby can't apply logs because it's waiting for the next log from the node that is down before continuing - Even though the UP node is doing work.
Is this normal? Should I be worried?
Ultimately it should only be a problem if a single RAC node dies - and the standby's only there in case the whole RAC dies - but I'm wondering if there's any way I can do this standby recovery when a single node is down (broken or shutdown for maintenance).
Thanks in advance.

>>However, when one of the RAC nodes is down, the standby can't apply logs because it's waiting for the next log from the node that is down before continuing - Even though the UP node is doing work.
standby should work in following scenario,becauase one node is still available.
post the output when one node is not available.
select * from (select inst_id,sequence#,next_time from gv$archived_log order by 3 desc) where rownum<50;
also post standby alertlog file when this problem occurs.

Create a Rac Database

Hii
I am testing a rac upgrade scenario and scenario is Create new one node rac database upload data from single instance database to new rac database and later add second node to rac database.
I have followed these steps
1.I have installed Cluster software on Centos node1
2.Create A rac database node1 .Oracle software installed local directory.I can see database in crs resources
3.I have add node2 via addNode.sh from node1 and crs working on two nodes correctly.I can see resources these belongs node1 and node2
4.I have installed only database software on node2
5.I run dbca on node1 and select manage instance add instance and I cant see node2 in available nodes only see node1
6.I run dbca on node1 and select create database I cant see node2 in available nodes again only see node1
7.I run dbca on node2 and select create database I cant see node1 in available nodes too only see node2
Where am I making misktake ?have you any advice ?
Os Centos
Crs 11gr2
Database 11gr2
Best Regards

It appears you manually installed the DB home on the second node. You need to instead run addnode.sh from the first node's DB home to install the DB binaries on the additional nodes.

Restoration of ASM/RAC database to another clustered set of servers for DataGuard implementation

Hi all,
I've been working with single instance Oracle DBs for several years and we're now looking into RAC. I'm trying to gather as much info as possible in areas I think may be challenging if/when we implement RAC.
Can someone please help me with some info with regards to the scenarion below:
Assuming I already have a 2 node RAC database running and I want to set-up a failover RAC database, would the following steps be correct(assuming 11g):
Configure hardware, networking and O/S for 2 node RAC cluster (I know there's a lot in this single line, but let's just assume that's all done)
Configure disks for ASM
Clusterware installation
Oracle ASM software installation
Oracle11g software installation with RAC option
Database creation
***I'm not sure of the steps after database creation:
Export primary database up to a specific SCN (data pump gives the ability to specify scn)
Import into failover database
Switch on dataguard and sync failover starting from scn specified at export.
Please, help correct these steps and any useful link where this process is treated thoroughly would be highly appreciated.

This is a very high level overview of the steps, but here are some additions/amendments I can make:
Clusterware installation
Oracle ASM software installation
-- The above 2 steps are done at the same time. In 11g, the Oracle 11g Grid Infrastructure includes both the Clusterware and ASM installation and configuration.
Oracle11g software installation with RAC option
Database creation
***I'm not sure of the steps after database creation:
Export primary database up to a specific SCN (data pump gives the ability to specify scn)
Import into failover database
Switch on dataguard and sync failover starting from scn specified at export.
Will you be using Data Guard for a physical standby? If so, using RMAN would be the correct method in creating the standby database. The general steps would be:
- Oracle 11g software installation
- Backup Primary Database
- Configure Data Guard Parameters on Primary
- Duplicate Primary to Standby RAC using RMAN (can be done manually or through the RMAN DUPLICATE command)
- Enable log transport from primary, enable managed recovery on standby, and verify log transport and apply is working as intended.
Again this is a very general overview on the entire process, there are other factors that you'll have to take into consideration when planning such a project:
- Which protection mode will you be using? Maximum Performance, Availability, or Protection? The business' recovery goals and SLAs will be able to determine which mode you will choose.
- Will the standby be used for reporting purposes?
- Recommended to have your standby site have the same hardware configuration as the primary.
- Do you have an EM site already set-up? Data Guard Broker should be considered in the configuration of the Data Guard environment.
This is just a few things quickly off the top of my head. What OS do you have/plan on using? I don't have the link handy on me at the moment, but the official Oracle documentation should provide detailed guidance.
EDIT:
At a bare minimum, read the 2 Day RAC Guide. There is more detailed information in the RAC Admin and Deployment Guide, as well as the Data Guard Concepts and Admin Guide. Also here's a step-by-step guide provided by Oracle. You can also find several blogs that provide a more concise step-by-step guide, such as here, here, and here. RACSIG also has a number of very useful whitepapers, but something seems to be wrong with their search function and I can't link anything at the moment. However, I would highly recommend reading through the official documentation as this has more comprehensive information, especially if you are deploying on a production system.
Regards,
Oscar

3 node RAC database need to build standby database

Similar Messages

Maybe you are looking for