Dbstart/dbstop for Primary or Physical Standby instance

We have established a Physical DataGuard instance on Oracle 9i RAC, RedHat 2.
In our environment we switchover from the Primary to Standby site about every 6 months.
DBSTART is called after a system restart - and its goal is to bring the database up automatically.
DBSTART works ok when the instance is a primary instance, and does not work when the instance is a Standby database.
As supplied by Oracle, DBSTART puts the instance into NOMOUNT status when the instance is a Standby Instance.
I would to put the database into "Managed Recovery Mode" when the instance is a Standby Instance.
I know that I can modify DBSTART to always put the instance into managed recovery - but then I would need to remember to modify DBSTART after a switchover.
Has anyone modified DBSTART so that it detects a "Standby Control File" and issues the appropriate statements?

Hi Richard,
I'd suggest you read the documentation as a starting point, to answer your questions on here would be quite lengthy,
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/toc.htm
In a nutshell you dont need downtime to maintain a standby, you can create them from a hot backup of your primary and get them recovering whilst it is open, in terms of which type of standby to use (physical or logical) that depends on your requirements for the use of the standby ... as I said read the doco (chapter 2 has a section on the benefits of each type).
HTH
Paul

Similar Messages

Dataguard 9iR2 using same SID for primary and physical standby issues

Hello, I have been following the Creating Physical Standby Database document from Oracle setting up a physical clone for a 9iR2 database on Solaris 9 environment between two identical workstations. I want to databases to have the same SID for relatively seemless failover however the redo logs are not pushed to the physical clone. when I switch a logfile on the primary and then query v$archive_dest on dest_id=2 I get a status of ERROR and the ERROR is the ORA-12154 TNS service name error.
Here is a summary of my setup:
Primary - SID = PROD1, located on WS001
Clone - SID = PROD1, located on WS002
SPFILE settings on Primary:
*.db_name='PROD1'
*.dg_broker_start=true
*.fal_client='PROD1_node2'
*.fal_server='PROD1_node1'
*.log_archive_dest_2='service=PROD1_node2 optional lgwr async=20480 noaffirm reopen=15 max_failure=10 delay=30 net_timeout=30'
tnsnames.ora on Primary:
PROD1_node2 =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP) (HOST = WS002) (PORT = 1521))
(CONNECT_DATA =
(SID = PROD1)
listener.ora on secondary:
PROD1_node2 =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP) (HOST = WS002) (PORT = 1521))
SID_LIST_PROD1_node2 =
(SID_LIST =
(SID_DESC =
(ORACLE_HOME = /export/oracle/oracle_9.2/PROD1)
(SID_NAME = PROD1)
Any input would be appreciated. I can provide whatever else you might need. I thought this was the most pertinent to this problem.
Thanks.
Jim

I have been looking at the sqlnet.ora files for the two databases
for WS001:
Names.Default_Domain = WS001.example.com
Names.Directory_Path = (TNSNAMES, ONAMES,HOSTNAME)
for WS002:
Names.Default_Domain = WS002.example.com
Names.Directory_Path = (TNSNAMES, ONAMES,HOSTNAME)
I cannot connect with sqlplus from WS001 to WS002 on the other machine.

Data Guard Archive Log Latency Between Primary and Physical Standby

How can I get the time it takes (latency) for the primary instance to get an archive log over to the physical standby instance and get it "archived" and "applied". I have been looking at the V$ARCHIVED_LOG view on each side but the COLUMN "COMPLETION_TIME" always shows a date "MM/DD/YY" and no timestamp. I thought the DATE datatype include data and time. Any ideas on how I can get the latency info I'm looking for?
Thanks
Steve

the COLUMN "COMPLETION_TIME" always shows a date "MM/DD/YY"
and no timestamp. Did you try using TO_CHAR ? e.g.
to_char(completion_time,'dd/mm/yyyy hh24:mi:ss')

Data guard synchronization after link down b/w primary and physical standby

Hi All,
I have configured data guard on oracle 11gr2 db. Normally switchover between my primary and physical standby happens smoothly and the Apply lag would be zero. Recently We had to test a scenario when the network link between Primary and Physical standby is completely down and Physical standby is isolated completely for more than half an hour.
When we brought up the link every thing worked smoothly but apply lag started increasing from 0 to around 3 hrs. And then it started reducing to 0. Currently Apply lag and transport lag shows 0.
But is this normal behaviour of oracle data guard that when the link between primary and physical standby is completely down, It requires 3-4 hrs for resynchronization ??? Even when during isolation, there were very few transactions happend on primary database ??
Are there any documents available for this scenario??
Thanks

Hi, after the link is up, if there were some transactions and produced archive logs it's normal to take some time for resync. To check if 3-4 hours is normal or not, you can repeat the scenario and this time check
- how many archivelogs does primary produce in this period.
- after the link is up, does archivelog transfer immediately starts from primary to standby? Is primary able to send these archivelogs parallel?
- Is there anything wrong with the apply process?
check primary & standby alert log files, and run this query on standby to check the transport and apply processes:
SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
regards

Primary and Physical Standby databases hanging on sqlplus shell command...

I am primarily a java developer that has had the task of oracle dba thrust upon me due to circumstances that are beyond my control. In the QA lab we have two oracle 10 g release 1 instances running. They set up in a dataguard configuration: one is the primary and the other is in a physical standby.
Last week I noticed that the disk space on the primary database was at 100%. After some investigation I discovered that a good deal of the files taking up space on the box were log files and the best solution that I could think of would be to delete all old archive files. So I deleted the old archive files that were at least two weeks old using RMAN.
During this week the database started to shutdown automatically. The QA associate restarted the database twice using the ‘STARTUP’ command from sqlplus. Additionally, the standby database began to have issues: when login in to sqlplus the application would just hang: no ‘SQL” prompt or anything. Finally today the primary database has also begun to hang in a similar manner.
I have looked at many of the trace files and alert logs but haven’t been able to really discern what the real problem is with the database and the proper rectification for the database. Does anyone have a clue into what is going on? If someone could even point me in the right direction it would be greatly appreciated.

Guessing that your flash recovery area is full, archiving is stopped so the instance appears to hang.
Do you see messages like so in the alert log:
You have following choices to free up space from flash recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
   then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
   BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
   reflect the new space.
4. Delete unnecessary files using RMAN DELETE command. If an operating
   system command was used to delete files, then use RMAN CROSSCHECK and
   DELETE EXPIRED commands.
************************************************************************

Backing up primary and physical standby

We have a DG setup with a single instance primary node and a physical standby db. They both use their own FRA's and their own disks. Nothing is shared. Also the datafiles use OMF on both the db's. My questions are
1. Can i register the primary with the rman catalog and still backup the standby?
2. Should i backup the archive logs on primary? If so what rman settings should i use on both for the archive logs?
3. We wanted to back up both the dbs as it will be faster to restore since we wont have to convert filenames (cause of OMF) when we have to resotore backup taken on primary to standby or vice versa.
Any advise related to this scenario is highly appreciated.
Thanks.

Hi All,
you should have same rman format setting and log_archive_format on primary and standby database >to avoide any confusion at the time of restore. if you have different log_archive_format on standby then >primary, you might have to rename your archivelogs from standby to log_archive_format on primary.It is not required to have same log_archive_format for primary and standby database.
The database can be restored and recovered successfully even if the format is different.
Primary database
============
SYS @ oraprim> show parameter log_archive_format
NAME TYPE VALUE
log_archive_format string ARC%S_%R.%T
Standby database
=============
SYS @ orastdby> show parameter log_archive_format
NAME TYPE VALUE
log_archive_format string ARC_STDBY%S_%R.%T
Standby database
=============
C:\> set ORACLE_SID=orastdby
C:\>rman target / catalog recat/recat@recat
RMAN> backup archivelog all delete input;
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=98 recid=15 stamp=631239054
input archive log thread=1 sequence=99 recid=16 stamp=631239055
input archive log thread=1 sequence=100 recid=17 stamp=631239055
input archive log thread=1 sequence=101 recid=19 stamp=631239111
input archive log thread=1 sequence=102 recid=18 stamp=631239110
channel ORA_DISK_1: starting piece 1 at 22-AUG-07
channel ORA_DISK_1: finished piece 1 at 22-AUG-07
piece handle=C:\FLASH_RECOVERY_AREA\ORASTDBY\BACKUPSET\2007_08_22\O1_MF_ANNNN_TAG20070822T001717_3DQG6HGS_.BKP
tag=TAG20070822T001717 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
channel ORA_DISK_1: deleting archive log(s)
archive log filename=C:\ORADATA\ORASTDBY\ARCH2\ARC_STDBY00098_0630878042.001 recid=15 stamp=631239054
archive log filename=C:\ORADATA\ORASTDBY\ARCH2\ARC_STDBY00099_0630878042.001 recid=16 stamp=631239055
archive log filename=C:\ORADATA\ORASTDBY\ARCH2\ARC_STDBY00100_0630878042.001 recid=17 stamp=631239055
archive log filename=C:\ORADATA\ORASTDBY\ARCH2\ARC_STDBY00101_0630878042.001 recid=19 stamp=631239111
archive log filename=C:\ORADATA\ORASTDBY\ARCH2\ARC_STDBY00102_0630878042.001 recid=18 stamp=631239110
Finished backup at 22-AUG-07
RMAN>
Primary Database
=============
-- deleted users datafile and did complete recovery
C:\>set ORACLE_SID=oraprim
C:\>rman target / catalog recat/recat@recat
RMAN> run{
2> startup mount;
3> restore database;
4> recover database;
5> }
Oracle instance started
database mounted
channel ORA_DISK_1: starting archive log restore to default destination
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=98
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=99
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=100
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=101
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=102
channel ORA_DISK_1: reading from backup piece C:\FLASH_RECOVERY_AREA\ORASTDBY\BACKUPSET\2007_08_22\O1_MF_ANNNN_TAG20070822T001717_3DQG6HGS_.BKP
channel ORA_DISK_1: restored backup piece 1
piece handle=C:\FLASH_RECOVERY_AREA\ORASTDBY\BACKUPSET\2007_08_22\O1_MF_ANNNN_TAG20070822T001717_3DQG6HGS_.BKP tag=TAG20070822T001717
channel ORA_DISK_1: restore complete, elapsed time: 00:00:04
archive log filename=C:\ORADATA\ORA10GR2DB1\ARCH2\ARC00098_0630878042.001 thread=1 sequence=98
archive log filename=C:\ORADATA\ORA10GR2DB1\ARCH2\ARC00099_0630878042.001 thread=1 sequence=99
archive log filename=C:\ORADATA\ORA10GR2DB1\ARCH2\ARC00100_0630878042.001 thread=1 sequence=100
media recovery complete, elapsed time: 00:00:07
Finished recover at 22-AUG-07
RMAN>
Regards,
Vaibhav

ARCHIVELOG deletion on primary and physical standby

Hi,
We have a primary and a physical standby database running Oracle 11.1.0.7.0 software on Red Hat Enterprise Linux x-64 bit OS. I will be using backup software
to only backup the primary database and do not have the backup software for the standby server and database.
We need to backup archived redo log files from primary site and delete the ones which are more than one month old. These archived redo log files will be applied from primary to standby database as and when the log switch occurs.
Can anybody please let me know if the following steps can be used:
Details are:
primary database name - sun (machine name is node1)
standby database name - drsun (machine name is node2)
On node1 as oracle user:
$ cat /export/home/oracle/rman/scripts/cleanup_rman_arch_sun.sh
#!/bin/sh
ORACLE_SID=sun; export ORACLE_SID
ORACLE_HOME=/u01/app/oracle/product/11.1.0/db_1; export ORACLE_HOME
PATH=$ORACLE_HOME/bin; export PATH
$ORACLE_HOME/bin/rman target sys/oracle@sun nocatalog log=/export/home/oracle/rman/log/cleanup_rman_arch_sun.log
@/export/home/oracle/rman/scripts/cleanup_rman_arch_sun.rcv
exit
$ cat /export/home/oracle/rman/scripts/cleanup_rman_arch_sun.rcv
allocate channel for delete type disk;
crosscheck archivelog all;
sql "alter system switch logfile";
delete noprompt expired archivelog all;
change archivelog until time 'SYSDATE-1' delete;
release channel;
$ crontab -l
# Delete the archived redo log files at 11:00 PM on the first day of every month
00 23 1 * * /export/home/oracle/rman/scripts/cleanup_rman_arch_sun.sh
On node2 as oracle user:
$ cat /export/home/oracle/rman/scripts/cleanup_rman_arch_drsun.sh
#!/bin/sh
ORACLE_SID=drsun; export ORACLE_SID
ORACLE_HOME=/u01/app/oracle/product/11.1.0/db_1; export ORACLE_HOME
PATH=$ORACLE_HOME/bin; export PATH
$ORACLE_HOME/bin/rman target sys/oracle@drsun nocatalog log=/export/home/oracle/rman/log/cleanup_rman_arch_drsun.log
@/export/home/oracle/rman/scripts/cleanup_rman_arch_drsun.rcv
exit
$ cat /export/home/oracle/rman/scripts/cleanup_rman_arch_drsun.rcv
allocate channel for delete type disk;
crosscheck archivelog all;
sql "alter system switch logfile";
delete noprompt expired archivelog all;
change archivelog until time 'SYSDATE-1' delete;
release channel;
$ crontab -l
# Delete the archived redo log files at 11:00 PM on the first day of every month
00 23 1 * * /export/home/oracle/rman/scripts/cleanup_rman_arch_drsun.sh
Regards

Hello;
Welcome to the forums. ( By physical Standby I assume Data Guard )
The short answer is it should work. I noticed this :
/cleanup_rman_arch_drsun.rcv
crosscheck archivelog all;
sql "alter system switch logfile";
delete noprompt expired archivelog all;
change archivelog until time 'SYSDATE-1' delete;I see no reason for the "alter system switch logfile". In fact you can do something very simple on the Standby :
$ORACLE_HOME/bin/rman target / catalog <user>/<password>@<catalog> << EOF
delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-1';
exit
EOFThis assumes you have doing a backup with RMAN on the Primary ( tested on 11.2.0.2 ) and have this set on the Primary :
CONFIGURE ARCHIVELOG DELETEION POLICY TO APPLIED ON ALL STANDBY;
If you are deleting Archive without using RMAN first then yes something like this ( But I would try to use RMAN and not delete using another method )
echo `date`
echo "Runnung RMAN archive crosscheck"
$ORACLE_HOME/bin/rman <<EOF
connect target /
crosscheck archivelog all;
delete noprompt expired archivelog all;
exit
EOF
echo `date`
Best Regards
mseberg
h2. Another Standby Option
/u01/app/oracle/dba_tool/bin/removestandbyarch.sql
SET echo off
SET feedback off
SET term off
SET pagesize 0
SET linesize 200
SET newpage 0
SET space 0
col name format a120
spool /u01/app/oracle/dba_tool/bin/rm_arch_standby.sh
select 'rm '||NAME from v$archived_log
where REGISTRAR='RFS'
and APPLIED='YES'
and DELETED='NO'
and COMPLETION_TIME < (SYSDATE-10);
SPOOL OFFMain shell script
/u01/app/oracle/dba_tool/bin/removestandbyarch.sh
#!/bin/bash
if [ "$1" ]
then DBNAME=$1
else
echo "basename $0 : Syntax error : use . removestandbyarch <DBNAME> "
exit 1
fi
# Set the Environmental variable for input instance ( ORACLE_SID, ORACLE_HOME path etc )
. /u01/app/oracle/dba_tool/env/${DBNAME}.env
$ORACLE_HOME/bin/sqlplus /nolog <<EOF
   connect / as sysdba
-- spool /u01/app/oracle/dba_tool/bin/rm_arch_${ORACLE_SID}.sh
   @/u01/app/oracle/dba_tool/bin/removestandbyarch.sql
   SPOOL OFF
EOF
echo `date`
# Now run the generated script
echo "Setting permissions and running script"
chmod 740 /u01/app/oracle/dba_tool/bin/rm_arch_standby.sh
. /u01/app/oracle/dba_tool/bin/rm_arch_standby.sh
# Use RMAN to update V$ARCHIVED_LOG.DELETED
echo `date`
echo "Runnung RMAN archive crosscheck"
$ORACLE_HOME/bin/rman <<EOF
connect target /
crosscheck archivelog all;
delete noprompt expired archivelog all;
exit
EOF
echo `date`Edited by: mseberg on Apr 30, 2012 8:40 AM

Primary and physical standby isue

hi guyes,
ia have created physical standby database on the same host as my primary database,i have switch some logs,my standby database was on mount stage. i recovered standby database by being disconnect from session. all the logs are transfered.
but when i tried to shutdown and restart my primar database it gives following errors:-
SQL> startup;
ORACLE instance started.
Total System Global Area 167772160 bytes
Fixed Size 1247876 bytes
Variable Size 83887484 bytes
Database Buffers 75497472 bytes
Redo Buffers 7139328 bytes
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> startup;
ORACLE instance started.
Total System Global Area 167772160 bytes
Fixed Size 1247876 bytes
Variable Size 83887484 bytes
Database Buffers 75497472 bytes
Redo Buffers 7139328 bytes
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> alter database open noresetlogs;
alter database open noresetlogs
ERROR at line 1:
ORA-01588: must use RESETLOGS option for database open
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF'
and on asking 'recover database until cancel using backup controlfile'
it ask for the archive log file 35 which is not at the specified place coz no log switch occured after arch log file 34.
how come this?
i have followed complete procedure according to docs....
all 34 arch logs have been applied..
is this happen after creating standby database???
thanks and regards
VD

Vikrant,
If you have applied all the logs
select applied, count(*) from v$archived_log group by applied; -- Please make sure you have all the logs applied successfully
shutdown immediate;
startup force nomount pfile='....' or startup force nomount;
alter database mount standby database;
-- this will activate your standby database and your should be able to open it without any problem; Primary database will be up and running as well.
alter database activate standby database;
alter database set standby database to maximize performance;
alter database open;

Downtime for logical or physical standby database

Hi ,
Are there any downtime required to refresh the data from the primary database to logical standby or physical standby database. What are the pros and cons of
using logical and physical standby database approach. which one is advisable to use in production environment.
Regards,
Richard

Hi Richard,
I'd suggest you read the documentation as a starting point, to answer your questions on here would be quite lengthy,
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/toc.htm
In a nutshell you dont need downtime to maintain a standby, you can create them from a hot backup of your primary and get them recovering whilst it is open, in terms of which type of standby to use (physical or logical) that depends on your requirements for the use of the standby ... as I said read the doco (chapter 2 has a section on the benefits of each type).
HTH
Paul

How to Flashback Primary with Physical Standby

We have a dataguard configuration with one physical standby (which is the FSFO). We had an application cause problems in the primary database (basically what would be considered a user error) and we would like to flashback the primary database without having to drop and re-create the physical standby.
Does anyone have a basic set of procedures for doing this?
We are running 10.2.0.3 on windows 2003 server sp2
Thanks!

We have flashback turned on in both the primary and standby. We want to flashback the primary (and subsequently the standby) to some previous point in time.
In a regular non-data guard setup we would just shutdown and startup mount and issue the flashback database to timestamp (sysdate-1). But with dataguard it's a little more complicated because if we shutdown the primary then the observer will initiate a failover which we don't want. And when we startup mount and flashback the primary, how do we flashback the standby? manually or do we re-start the broker and let data guard do it?
I think it's going to require some specific steps and I was hoping someone had gone through this and could offer some suggestions.

ASM on primary and physical standby on normal filesystem

Hi
I have seen he white paper by oracle on migrating a database to ASM with minimal downtime using ASM for a physical standby my requirement is reverse.
I need to have a ASM for a primary database but no ASM for standby database.
How do we set the parameter db_file_name_convert
regards
Hrishy

db_file_name_convert covers the folder path for the files. I don't think, there will be issue.
If we use rman, it will use the folder path per db_file_name_convert and retain the old file names. OMF naming will apply for the new files.
Ashok

Upgrading the primary and physical standby database

Solaris 9
oracle 9i (9.2.0.8)
upgrade to 10g (10.2.0.3)
Hi,
I would like to know how to upgrade database in dataguard envronment.(primary and remote physical standby database)
Is rolling upgrade possible in this case?
Or any steps or Document is appreciated.
Thanks.
Message was edited by:
user539835

Read this Metalink Note:407040.1

Time zone difference between primary and physical standby

Dear Team,
We have Primary database server (with EST Time zone) and physical standby (with PST time zone), in case of switch over/fail over to physical standby
what are the major impacts.
Is it mandatory to be in time sync?
Thanks in advance
Aj

CURRENT_TIMESTAMP
04-FEB-10 10.22.20.444692 AM +05:30
( above is same on primary and standby)
SQL> select systimestamp from dual;
SYSTIMESTAMP
03-FEB-10 08.52.46.934125 PM -08:00
(above is 3hr diff from primary and standby)It is 13hrs difference
One is around Indian subcontinent and other should be in US western region ?
Systimestamp is the timestamp of the OS of the server and hence the difference and the sysdate value will be from systimestamp and if the applications uses SYSDATE then there can be an issue...

Problem while creating Physical standby database on remote Server

Hi
I try to create a physical standby datbaase using OEM 10gr2, it is working when I create on same server. No issue but when I try to create same on remote server it is giving below warning and process failing. Please let me know what needs to be down in this senario...
It is showing redo log information in v$log and v$log_file but not creating physically on PHYSICAL Standby instance..
I appriciate your help and ur time too..
These messages are from PRIMARY database alert*.log file
There is space for up to 12 standby redo logfiles
Use the following SQL commands on the standby database to create
standby redo logfiles that match the primary database:
ALTER DATABASE ADD STANDBY LOGFILE 'srl1.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl2.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl3.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl4.f' SIZE 52428800;
ALTER DATABASE ADD STANDBY LOGFILE 'srl5.f' SIZE 52428800;
WARNING: OMF is enabled on this database. Creating a physical
standby controlfile, when OMF is enabled on the primary
database, requires manual RMAN intervention to resolve OMF
datafile pathnames.
NOTE: Please refer to the RMAN documentation for procedures
describing how to manually resolve OMF datafile pathnames.
Thanks and Regards,
RK

Well, it is simply warning that "Creating a physical
standby controlfile, when OMF is enabled on the primary
database, requires manual RMAN intervention to resolve OMF
datafile pathnames.
NOTE: Please refer to the RMAN documentation for procedures
describing how to manually resolve OMF datafile pathnames"
For instance, the path for the logfile name in "ALTER DATABASE ADD STANDBY LOGFILE 'srl5.f' SIZE 52428800" may need to be changed manually. It is advisable to check the mentioned documentation.

How to create online log in standby instance?

Oracle say that:
Step 3 Create an Online Redo Log on the Standby Database
Although this step is optional, Oracle recommends that an online redo log be created
when a standby database is created. By following this best practice, a standby database
will be ready to quickly transition to the primary database role.
The size and number of redo log groups in the online redo log of a standby database
should be chosen so that the standby database performs well if it transitions to the
primary role.
But when I execute "ALTER DATABASE ADD LOGFILE ('/opt/oracle/oradata/orcl/redo01.log') SIZE 50M;" in standby instance,I get the follow message:
ORA-01275: Operation ADD LOGFILE is not allowed if standby file management is automatic.
How could I do?

Hello xyz_hh ;
Your post is just a little vague so I'm guessing you are referring to "3.2.6 Start the Physical Standby Database" in "Data Guard Concepts and Administration"
If this is correct, this is part of "Step-by-Step Instructions for Creating a Physical Standby Database"
Assuming I right so far you are try to "Create an Online Redo Log on the Standby Database".
Can you confirm along with you OS, and Oracle version?
If you are trying to create redo on the standby after the fact you will need to make this change before you proceed.
STANDBY_FILE_MANAGEMENT=MANUALIf this is your issue check this link out:
http://kb.dbatoolz.com/tp/2692.avoid_ora-19527_set_dummy_log_file_name_convert.html
Best Regards
mseberg
Edited by: mseberg on Aug 12, 2011 5:35 AM

Dbstart/dbstop for Primary or Physical Standby instance

Similar Messages

Maybe you are looking for