Add standby database to crs?

Hi,
I have te latest Oracle version 11.2.0.3.0.
I've created a physical standby database with OEM, when I reboot the servers the primary goes down and up automaticly, but the standby doesn't... I have to start this one up manually.
How can I add this standby database to the Oracle High availability Services to auto stop and start ?
BR
Mark

Hi,
Use the srvctl add database command with the following syntax:
srvctl add database -d db_unique_name -o oracle_home [-m domain_name]
[-n db_name] [-p spfile] [-s start_options] [-t stop_options]
[-r {PRIMARY | PHYSICAL_STANDBY | LOGICAL_STANDBY | SNAPSHOT_STANDBY}]
[-y {automatic | manual}] [-a disk_group_list]HTH,
Levi Pereira

Similar Messages

Add Standby Database not finding listener

in Enterprise Manager Cloud Control 12c 12.1.0.2
go to the primary database
go to Availability and choose Add Standby Database
create a new physical standby database
online backup - use rman
enter instance name and choose host (agent is on standby host machine and is working)
enter password if prompted
Enter Database Area
Enter Flash Recovery Area
both 'Use Default Grid Infrastructure Listener' and 'use destination database home listener' fail:
The default listener in the grid infrastructure is not running
my listener is in the grid infrastructure, and the enterprise manager sees it as a target that is up.
Status Up
Availability (%) 100
(Last 24 Hours)
Alias LISTENER
Version 11.2.0.3.0
Oracle Home C:\app\product\11.2.0\grid
Net Address (ADDRESS=(PROTOCOL=TCP)(HOST=server_name)(PORT=1521))
LISTENER.ORA Location C:\app\product\11.2.0\grid\network\admin
Start Time Jan 24, 2013 4:34:36 PM
Host server_name
Oracle Restart Enabled

stopping the grid listener and creating a listener in the database home worked..
still currious why the grid listener didnt work..

"Add Standby Database" wizard licensing

there is a wizard in grid control known as "Add Standby Database" does it require licesning ?
apparently this is missing in the EM dbconsole...
http://download.oracle.com/docs/cd/B28359_01/server.111/b28295/gui.htm#i1005702
Oracle Enterprise Manager Grid Control provides access to the complete set of Data Guard 10.2 features. Limited monitoring-only Data Guard functionality is available in Enterprise Manager Database Control.

user9198889 wrote:
there is a wizard in grid control known as "Add Standby Database" does it require licesning ?
apparently this is missing in the EM dbconsole...
http://download.oracle.com/docs/cd/B28359_01/server.111/b28295/gui.htm#i1005702
Oracle Enterprise Manager Grid Control provides access to the complete set of Data Guard 10.2 features. Limited monitoring-only Data Guard functionality is available in Enterprise Manager Database Control.It's not a licensing issue, it's an inherent limitation of dbcontrol. It (dbcontrol) works with a single database. To create/manage a DG setup, you have to be able to work with multiple databases, hence the only flavor of OEM that will do it is GC.

Creating Standby database in OEM 10g

DB = Oracle 10.2.0.4
OS = Solaris 10 Sparc
I am trying to create a physical standby database using the add standby database option within OEM 10g. This is something we have done numerous times before on 10g and 11g db's without a single issue, but for some reason, this time after selecting my RMAN backup location and staging area location , I am getting the following error when I click Next:
RMAN Backup Location - The specified RMAN backup is invalid. Could not identify controlfile from the backup
It is the latest backup (using RMAN catalog) from the previous evening and includes datafiles and control file.
Here is the output for List backup:
BS Key Size Device Type Elapsed Time Completion Time
1741586 7.70G DISK 00:03:26 06-DEC-12
BP Key: 1741590 Status: AVAILABLE Compressed: NO Tag: TAG20121206T220033
Piece Name: /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4811_1.bus
List of Archived Logs in backup set 1741586
Thrd Seq Low SCN Low Time Next SCN Next Time
1 20013 7974703107 04-DEC-12 7974865046 04-DEC-12
1 20014 7974865046 04-DEC-12 7975209322 05-DEC-12
1 20015 7975209322 05-DEC-12 7975792781 05-DEC-12
1 20016 7975792781 05-DEC-12 7975841363 05-DEC-12
1 20017 7975841363 05-DEC-12 7976016507 05-DEC-12
1 20018 7976016507 05-DEC-12 7976577946 06-DEC-12
1 20019 7976577946 06-DEC-12 7976685352 06-DEC-12
1 20020 7976685352 06-DEC-12 7976816259 06-DEC-12
1 20021 7976816259 06-DEC-12 7976884597 06-DEC-12
1 20022 7976884597 06-DEC-12 7977236969 06-DEC-12
1 20023 7977236969 06-DEC-12 7978009499 06-DEC-12
1 20024 7978009499 06-DEC-12 7978784609 06-DEC-12
1 20025 7978784609 06-DEC-12 7979558556 06-DEC-12
1 20026 7979558556 06-DEC-12 7980614921 06-DEC-12
1 20027 7980614921 06-DEC-12 7981238045 06-DEC-12
1 20028 7981238045 06-DEC-12 7981890156 06-DEC-12
1 20029 7981890156 06-DEC-12 7982119933 06-DEC-12
1 20030 7982119933 06-DEC-12 7982775834 06-DEC-12
1 20031 7982775834 06-DEC-12 7983388279 06-DEC-12
BS Key Type LV Size Device Type Elapsed Time Completion Time
1741587 Full 214.09G DISK 01:15:15 06-DEC-12
List of Datafiles in backup set 1741587
File LV Type Ckp SCN Ckp Time Name
1 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/system01.dbf
2 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/undotbs01.dbf
3 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/sysaux01.dbf
4 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/large_indexes01.dbf
5 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/large_indexes02.dbf
6 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/large_indexes03.dbf
7 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/large_tables01.dbf
8 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/large_tables02.dbf
9 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/large_tables03.dbf
10 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/small_tables01.dbf
11 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/small_tables02.dbf
12 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/small_tables03.dbf
13 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/small_tables04.dbf
14 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/medium_tables01.dbf
15 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/medium_tables02.dbf
16 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/medium_tables03.dbf
17 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/small_indexes01.dbf
18 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/medium_indexes01.dbf
19 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/tools01.dbf
20 Full 7983402310 06-DEC-12 /oracle/oradata/care/carelive/data/small_indexes02.dbf
Backup Set Copy #1 of backup set 1741587
Device Type Elapsed Time Completion Time Compressed Tag
DISK 01:15:15 06-DEC-12 NO TAG20121206T220415
List of Backup Pieces for backup set 1741587 Copy #1
BP Key Pc# Status Piece Name
1741591 1 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_1.bus
1741592 2 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_2.bus
1741593 3 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_3.bus
1741594 4 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_4.bus
1741595 5 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_5.bus
1741596 6 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_6.bus
1741597 7 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_7.bus
1741598 8 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_8.bus
1741599 9 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_9.bus
1741600 10 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_10.bus
1741601 11 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_11.bus
1741602 12 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_12.bus
1741603 13 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_13.bus
1741604 14 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_14.bus
1741605 15 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_15.bus
1741606 16 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_16.bus
1741607 17 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_17.bus
1741608 18 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_18.bus
1741609 19 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_19.bus
1741610 20 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_20.bus
1741611 21 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_21.bus
1741612 22 AVAILABLE /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4812_22.bus
BS Key Size Device Type Elapsed Time Completion Time
1741658 104.19M DISK 00:00:04 06-DEC-12
BP Key: 1741679 Status: AVAILABLE Compressed: NO Tag: TAG20121206T231939
Piece Name: /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4813_1.bus
List of Archived Logs in backup set 1741658
Thrd Seq Low SCN Low Time Next SCN Next Time
1 20032 7983388279 06-DEC-12 7983637536 06-DEC-12
BS Key Type LV Size Device Type Elapsed Time Completion Time
1741702 Full 7.33M DISK 00:00:02 06-DEC-12
BP Key: 1741704 Status: AVAILABLE Compressed: NO Tag: TAG20121206T231950
Piece Name: /carebackup/oradata/CARELIVE/carelive/backup/ctlc-3640364239-20121206-00
Control File Included: Ckp SCN: 7983638867 Ckp time: 06-DEC-12
SPFILE Included: Modification time: 06-DEC-12
The only difference between creating a standby for this db and others we have created is that the file system the backups are stored on is on a non-global zone shared via nfs mount.
I know that when I try and share that filesystem with other servers I get the message:
share_nfs: Cannot share filesystems in non-global zones
If the /backup filesystem is not shared with any other servers would OEM be able to read from that NGZ? The filesystem is available to connect to using ssh from other locations, but not sure how OEM handles this part of the process.
Any advice would be great.
Regards,
JP

Thanks for the reply. I thought that is what I would need to do. However this link is very useful and could resolve the issue. I have yet to raise it with the system admin guys here yet but will do and will report back on outcome.
http://faizsulaiman.com/mount-nfs-solaris-non-global-zone/

Looking to use DG Broker to create new standby database

Hello,
I'm looking for a good document that can help me to create another standby database on a new server.
I'm running Oracle 11.2 EE on Solaris 10.
We already have one standby database, but now, I want to create another standby database on another server, which ultimately I will make primary and then replace and destroy our current primary/standby databases.
Also, just for the heck of it, I tried to look in our DB Console, and the "Add standby database" is grey'd out.
Is this because I am only using DB Console, and not Grid?
But if that were the case, why would the option even be in DB Console, or perhaps is there a lmiitation to the number of standby databases you can manage with DB Console?

1) Do not confuse Data Guard Broker and Enterprise Manager: DG Broker is mainly a background process (DMON) that can be controlled by EM or with DGMGRL on the command line
2) Only the Grid Control flavor of EM can manage Data Guard Configurations - regardless of the number of Primary or Standby Databases
3) DGMGRL cannot create a new Standby Database - Grid Control can
Kind regards
Uwe Hesse
"Don't believe it, test it!"
http://uhesse.com

Add Standby Server in OEM Grid.

Hi,
I need to add Standby Database in Oracle EM Grid.. it is 11g Emgrid.. Standby database 11.2.0.3 is one server another one server is in 10g.. i need to add both server to EM Grid... We didn't configure Dataguard Broker.. is there any way to configure without dataguard broker. i have tried in Primary server on emgrid on availability page for add standby link.. but it's not accepting sys password for standby.... Please Give me solution.. We need Sync alert between Primary and Standby through EM Grid
Regards,
Madhan

From your description I do not understand what you have (provide full version numbers not marketing labels for each one) and their operating systems. Also the full version of OEM Grid.
What edition do you have Standard or Enterprise?
Is the source database RAC or stand-alone?
Did you read any docs telling you how to configure the standby? Post a link so we know what you were trying to do.
And finally "it's not accepting" means what? That the server reboots? That it gives you an error message you didn't think important enough to post?
Here's what your post reads like to me:
I need to add a second car for my family .. it is a 2009 Honda. Standby car is a Subaru wagon. I need to have both. I didn't do anything with my insurance policy. I have tried to start the car but it doesn't start. Please give me a solution."
{code}
Which car? Is it out of gas or did you use the wrong key? How can we know if you don't tell us.
Please provide all of the information and we should be able to answer your question ... but for starters. Data Guard broker is only "required" for RAC clusters.

Diagnosing an ASM space issue for a primary and a standby database instance with external redundancy.

I've received an alert from Enterprise manager saying "Disk Group DATA_SID requires rebalance because at least one disk
is low on space". My colleague who I would go to with this question is unavailable, so this is a learning opportunity
for me. So far google and Oracle documentation have provided lots of information, but nothing that answers my questions.
I've run the following query on both the primary and standby databases ASM instances:
select name, disk_number, sector_size,os_mb, total_mb, free_mb, redundancy from v$asm_disk;
On the primary I get 4810M Free space and 18431M Total Space
on the standby I get 1248M Free space and 18431M Total Space -- this is the one that complained via OEM
When I run the following query in the database instance:
select sum(bytes)/1024/1024 MB from dba_segments;
I get 3736.75M as a result.
My questions are:
1. Will OEM's suggestion to rebalance the disk actually help in this situation since the instance is set up with external redundancy?
2. If I've got 18G of space and only 3.7G of data, why is OEM complaining?
3. How can I reclaim what I presume is allocated but unused space in my problem disk group?
4. How can I determine what extra data the standby has that the primary doesn't since both have the same total space allocation, but different amounts of free space?

Thank you for the reply. That link is very good.
We are an 11.1 version of our database. Linus is OEL 5.6.
So, looking at the portion of the link that refers to 'Add Standby database and Instances to the OCR' - If we use SRVCTL to give the STANDBY the role of ‘physical_standby’ and the start option of ‘mount’, what effect will that have if the STANDBY becomes our PRIMARY?
Would these database settings need to be modified manually with SRVCTL each time?
We understand why the instance is not starting when the node is rebooted, we are looking for a best practice of how this is implemented.
Thank you.

Creaton of Standby database and dataguard broker

Hi Experts,
I am using Linux with Oracle version 11gR2. We have planned to create a physical standby database and also configure dataguard broker for the standby database.
Also, I've read the documents that active dataguard is a feature on 11g. Is it not possible on 10g ?
Can someone please provide me the steps to create the standby database and configure the dataguard broker.

Hello;
A simple Data Broker setup would be :
On both Primary and Standby sites, change the initialization parameter in the spfile to enable the Data guard broker.
SQL> Alter system set dg_broker_start=True scope=both;
On the PRIMARY site, open the ‘cmd’ and start Command Line Interface (CLI) of the Dataguard Broker (DGMGRL).
/home/oracle:PRIMARY >dgmgrl
DGMGRL for Linux: Version 11.2.0.1.0 - 64bit Production
DGMGRL> connect sys/password@PRIMARY
Create broker configuration.
DGMGRL> create configuration ‘broker1’ as
primary database is 'PRIMARY'
connect identifier is primary;Configuration "?broker1?" created with primary database "PRIMARY"
DGMGRL>
(‘primary’ in Connect identifier is the service name through which the broker is connected to the PRIMARY database)
Add Standby Database to the above configuration.
DGMGRL> add database 'standby' as
connect identifier is 'STANDBY'
maintained as physical;
Database "standby" added
(‘to_standby’ in Connect identifier is the service name through which the broker is connected to the STANDBY database)
Now the configuration has been set up but it is still disabled. You can view the configuration by executing:
DGMGRL> show configuration
The next step is to ENABLE the configuration ‘broker1’.
DGMGRL> enable configuration;
Enabled.
Again view the configuration.
DGMGRL> show configuration
Configuration - ?broker1?
Protection Mode: MaxPerformance
Databases:
PRIMARY - Primary database
standby - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESSIn my humble opinion its a good idea to setup Data Guard without Broker and get the "feel" of it first.
Remember, once you setup Broker, you cannot use SQL to change your Data Guard setup.
Best Regards
mseberg

Add Datafile in Logical Standby Database

Hi,
I have add one datafile in our primary RAC DB. We had logical standby database with file management is equal to manual. Both the primary RAC and logical standby db have the different storage structure. When the archive applied on the logical standby database its throws the error " error in creating datafile 'path'";
Would appreciate if come to know the steps to add the datafile in this kind of environment. and how can i overcome from this problem now except skip transaction for that ddl.
Thanks in advance.
Dewan

When the archive applied on the logical standby database its throws the error " error in creating datafile 'path'";Can you post the error message with the number.
From Manual..
8.3.1.2 Adding a Tablespace and a Datafile When STANDBY_FILE_MANAGEMENT Is Set to MANUAL
The following example shows the steps required to add a new datafile to the primary and standby database when the STANDBY_FILE_MANAGEMENT initialization parameter is set to MANUAL. You must set the STANDBY_FILE_MANAGEMENT initialization parameter to MANUAL when the standby datafiles reside on raw devices.
Add a new tablespace to the primary database:
SQL> CREATE TABLESPACE new_ts DATAFILE '/disk1/oracle/oradata/payroll/t_db2.dbf'
2> SIZE 1m AUTOEXTEND ON MAXSIZE UNLIMITED;
Verify the new datafile was added to the primary database:
SQL> SELECT NAME FROM V$DATAFILE;
NAME
/disk1/oracle/oradata/payroll/t_db1.dbf
/disk1/oracle/oradata/payroll/t_db2.dbf
Perform the following steps to copy the tablespace to a remote standby location:
Place the new tablespace offline:
SQL> ALTER TABLESPACE new_ts OFFLINE;
Copy the new tablespace to a local temporary location using an operating system utility copy command. Copying the files to a temporary location will reduce the amount of time the tablespace must remain offline. The following example copies the tablespace using the UNIX cp command:
% cp /disk1/oracle/oradata/payroll/t_db2.dbf
/disk1/oracle/oradata/payroll/s2t_db2.dbf
Place the new tablespace back online:
SQL> ALTER TABLESPACE new_ts ONLINE;
Copy the local copy of the tablespace to a remote standby location using an operating system utility command. The following example uses the UNIX rcp command:
%rcp /disk1/oracle/oradata/payroll/s2t_db2.dbf standby_location
Archive the current online redo log file on the primary database so it will get transmitted to the standby database:
SQL> ALTER SYSTEM ARCHIVE LOG CURRENT;
Use the following query to make sure that Redo Apply is running. If the MRP or MRP0 process is returned, Redo Apply is being performed.
SQL> SELECT PROCESS, STATUS FROM V$MANAGED_STANDBY;
Verify the datafile was added to the standby database after the archived redo log file was applied to the standby database:
SQL> SELECT NAME FROM V$DATAFILE;
NAME
/disk1/oracle/oradata/payroll/s2t_db1.dbf
/disk1/oracle/oradata/payroll/s2t_db2.dbf

Add a new datafile to the standby database

Hi,
i have a standby database in recovery managed mode.
Now i must add a new datafile on the production database and i would like
to know how i realized adding the new datafile on the stanby database.
is it right when i do the follow steps?
Before i add a datafile to the primary database,
cancel the recovery on the standby database.
-> add the new datafile on the primary database
after all archived redo logs have been applied, cancel managed recovery:
alter database recover managed standby database cancel;
startup nomount
alter database mount standby database;than
ALTER DATABASE CREATE DATAFILE '/oracle/DB1/db1_9/data9' as '/oracle/DB1/db1_9/data9';
alter database recover managed standby database disconnect;Thanks

8.4.1.1 Adding a Tablespace and a Datafile When STANDBY_FILE_MANAGEMENT Is Set to AUTO
The following example shows the steps required to add a new datafile to the primary and standby databases when the STANDBY_FILE_MANAGEMENT initialization parameter is set to AUTO.
Add a new tablespace to the primary database:
SQL> CREATE TABLESPACE new_ts DATAFILE 't_db2.dbf'
2> SIZE 1m AUTOEXTEND ON MAXSIZE UNLIMITED;
Archive the current redo log so it will get copied to the standby database:
SQL> ALTER SYSTEM ARCHIVE LOG CURRENT;
Verify that the new datafile was added to the primary database:
SQL> SELECT NAME FROM V$DATAFILE;
NAME
/disk1/oracle/dbs/t_db1.dbf
/disk1/oracle/dbs/t_db2.dbf
Verify that the new datafile was added to the standby database:
SQL> SELECT NAME FROM V$DATAFILE;
NAME
/disk1/oracle/dbs/s2t_db1.dbf
/disk1/oracle/dbs/s2t_db2.dbf
8.4.1.2 Adding a Tablespace and a Datafile When STANDBY_FILE_MANAGEMENT Is Set to MANUAL
The following example shows the steps required to add a new datafile to the primary and standby database when the STANDBY_FILE_MANAGEMENT initialization parameter is set to MANUAL. You must set the STANDBY_FILE_MANAGEMENT initialization parameter to MANUAL when the standby datafiles reside on raw devices.
Add a new tablespace to the primary database:
SQL> CREATE TABLESPACE new_ts DATAFILE 't_db2.dbf'
2> SIZE 1m AUTOEXTEND ON MAXSIZE UNLIMITED;
Verify that the new datafile was added to the primary database:
SQL> SELECT NAME FROM V$DATAFILE;
NAME
/disk1/oracle/dbs/t_db1.dbf
/disk1/oracle/dbs/t_db2.dbf
Perform the following steps to copy the tablespace to a remote standby location:
Place the new tablespace offline:
SQL> ALTER TABLESPACE new_ts OFFLINE;
Copy the new tablespace to a local temporary location using an operating system utility copy command. Copying the files to a temporary location will reduce the amount of time that the tablespace must remain offline. The following example copies the tablespace using the UNIX cp command:
% cp t_db2.dbf s2t_db2.dbf
Place the new tablespace back online:
SQL> ALTER TABLESPACE new_ts ONLINE;
Copy the local copy of the tablespace to a remote standby location using an operating system utility command. The following example uses the UNIX rcp command:
%rcp s2t_db2.dbf standby_location
Archive the current redo log on the primary database so it will get copied to the standby database:
SQL> ALTER SYSTEM ARCHIVE LOG CURRENT;
Use the following query to make sure that managed recovery is running. If the MRP or MRP0 process is returned, managed recovery is being performed.
SQL> SELECT PROCESS, STATUS FROM V$MANAGED_STANDBY;
Verify that the datafile was added to the standby database after the redo log was applied to the standby database.
SQL> SELECT NAME FROM V$DATAFILE;
NAME
/disk1/oracle/dbs/s2t_db1.dbf
/disk1/oracle/dbs/s2t_db2.dbf
From Oracle Docs...

Add new datafile to logical standby database but not in primary

Hi,
Is it ok to add a new datafile to the SYSAUX tablespace on the logical standby database but not on primary? We are running out of disk space on the partition where SYSAUX01.dbf resides so we want to add a new SYSAUX02.dbf in another partition which has space. but this will only be on the logical standby not on primary, there is still lots of space in primary. standby_file_management is MANUAL and this is LOGICAL STANDBY not PHYSICAL.
Is this possible or where there be any issues?
Thanks.

Logical Standby can differ from Primary, it can have extra tablespaces, datafiles, tables, indexes, users ...
HTH
Enrique

How to add datafile to standby database

Hi,
We have standby database on another site and we are using manual recovery. How to add datafile to standby database after datafile is added to primary database.
We are on Oracle 9i R2.
Please help.
Thanks in advance

Hi,
When you recover the standby database after you added a datafile to the production, you will get an error that the file that needs recovery does not exist.
At this point you can connect to the standby and issue:
alter database create datafile '<original_name>' as '<new_name>';the new name is optional if the location of the files are the same.
After that, you can continue recovering the standby database.
Liron Amitzi
Senior DBA consultant
[www.dbsnaps.com]
[www.orbiumsoftware.com]

Add temporary datafiles after creating standby database

I used data guard manager to create standby database and it went fine. Before finish, system pop up a window and says,
"The data guard configuration has been created in a disabled state. It must be enabled using the Enable option in the configuration menu. Pior to ebaling the configuration, please verify the following:
The Primary database contains temporary datafiles. The files will not be duplicated in the new standby database. You must manually recreate the temporary files on the standby node by adding them to their respective tablespaces in the standby database after creation process in complete."
The problem is, in the standby database, how do I add tempfile without open the standby database? the documentation is very unclear...

Thanks for the reply and the useful link. I had followed the instructions when creating the standby database, although under database options there is a difference between the OEM version we are using and the version shown, whereby the 'RMAN backup location' option has been replaced with 'working directory location'.
Just found the following and am guessing this is the issue.
NFS mounts established within a zone are local to that zone. The mounts cannot be accessed from other zones, including the global zone.
I suspect I will need to copy the backup pieces onto the local server in order to create the standby database using OEM. Not something I was expecting to have to do as copying will take a long time due to the size of the backup, but unless anyone else can shed any light on the reason for the initial error
RMAN Backup Location - The specified RMAN backup is invalid. Could not identify controlfile from the backup
then I guess this is the only way forward.
Regards,
JP

ALTER DATABASE ADD STANDBY LOGFILE GROUP

version 10 & 11g
creating standby logfile groups on primary db is optional or needed? what could be advantages of both?
I am reading 2 articles one is creating that other not?
http://www.orafaq.com/node/2030
& 736863.1 Notes

DBA2008 wrote:
version 10 & 11g
creating standby logfile groups on primary db is optional or needed? what could be advantages of both? at primary database it is optional ,but it would be good candidate for switchover activity , it makes ensure that if you make any planned maintenance activity at primary site and switchover within yours data guard environment from primary database to physcial standby database ,if you create standby redo log at primary database it is not in use right now but it will be used when yours primary database switch to standby database after switching to physical standby databsae as a primary database.
Khurram

Can I use data guard to create a RAC standby database for a non RAC primary

Hi,
we need to RAC our production database but the normal methods will mean a long outage. It is possible to create a standby as a single node RAC database and when ready do a graceful failover to the standby database and open it for business. The next step would be to create another RAC node from this on the original server.
servers are already cluster aware, using ASM etc
Oracle 10.2

Yes, you will be able to setup RAC stnadby for a non-RAC Primary. For primary it just needs a available destination for redo shipping it doesn't matter whether it's RAC enabled or not. And ofcourse you are using 10.2 anyway only one node will be running MRP and that is too in standby mount mode.
However since you have are using You may follow below sequence.
1. Setup a new standby as RAC enabled.
2. Perform a switchover.
3. Shutdown the Old primary (which is standby now).
4. Install CRS and RDBMS on the old primary and it's new node.
5. Modify the cluster_database=TRUE and cluster_database_instances=<required number of instances>.
With above modification mount the standby database in standby mode and start MRP.
6. Introduce the database and instances to the OCR using SRVCTL add command.
7. Once you your database is synchronized with Primary do a switchover.
9. Now you can repeat step 3 to 6 on the other site too. <- if you need your secondary site to be RAC enabled too
10. Finally both the sites should be RAC enabled.
Hope this is helpful!!!
Thanks,
Asif Haliyal

Add standby database to crs?

Similar Messages

Maybe you are looking for