How Auto starting Physical Standby Database ( when Server Restart)

Dear All(s)
I have configure oracle (10.2.0) dataguard on production database, some time server restart due to power disconnectivity, i want to restard dataguard when server restart. i am using Server 2003 32bit. Guide me how i can run following commands when server restart.
SQL> connect/as sysdba
SQL> Startup mount;
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
Thanks in Advance

i want to run these command each time when server restart.Yes, I did understand that... but what's the problem ? can't you schedule a task when the server starts ?

Similar Messages

Starting Physically Standby Database in Mount Mode

Hi All
I have configured Data Guard using Oracle 10g 10.2.0.4.0 (64 bits) on Windows 2008 Server (64 bits) Release 2 Enterprise.
Data guard configuration was OK as the message from "Enable Configuration DG1" was "SUCCESS" for both
Primary and Standby Database. I have also set both Databases and TNS to start Automatically whenever Windows Starts.
The Problem is as long as the Standby Server is running, there is No issue.
But when we Restarts the Backup Server, Physically Standby Database is Started and TNS is also Started,
but Archives are not received until I physically do the following steps so that it can received the Archives.
SQL> startup nomount;
SQL> alter database mount standby database;
SQL> alter database recover managed standby database disconnect from session;
Is there a way to start Physically Standby Database in Mount mode when windows started.
Regards
Thunder2777

Hi Mihael
I have created 2 files. 1 Bat file 2nd sql file which contains all commands as written above.
When I execute start.bat file
1. set ORACLE_HOME=C:\oracle\product\10.2.0\db_1
2. set ORACLE_SID=UMISBK
3. sqlplus / [email protected]
1 & 2 executed properly. At 3 it just display SQL help for login as shown below.
SQL*Plus: Release 10.2.0.4.0 - Production
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Usage 1: sqlplus -H | -V
    -H             Displays the SQL*Plus version and the usage help.
    -V             Displays the SQL*Plus version.
Usage 2: sqlplus [ [<option>] [<logon>] [<start>] ]
<option> is: [-C <version>] [-L] [-M "<options>"] [-R <level>] [-S]
It Did Not execute start.sql file to excute sql commands.
Regards
Thunder2777

How to create physical standby database without dataguard

Hi,
Can anyone please help me how to create Physical Standby Database without dataguard. As i am using Oracle 10.2.0.1 Standard Edition for production databases.
Please find the specifications of my server :
Database : Oracle 10.2.0.1(Standard Edition)
Server : Linux 4.0(32 bit machine)
As we know that Dataguard cannot be created in Standard Edition as we dont have that option in this edition. So please help me how to create the physical standby database.
Thanks in advance.
Regards,
Farooq

Hello,
I hope this link helps you out...
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rcmbackp.htm
http://www.dbasupport.com/oracle/ora10g/manual_standby.shtml
Thanks & Regards
Pratik Lakhpatwala
Jr Oracle DBA
Edited by: Pratik.L on Dec 31, 2009 12:03 PM

Ora-38500 physical standby database not started

hiiii,
When i executed the command at physical standby database server.
it give error:
To start real-time apply:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
2> USING CURRENT LOGFILE;
Error at line 1:
ORA: 38500 using current logfile option not available without stand.
please help me how could i start physical standby database
Regards
Vaibhav Dixit

Hi Vaibhav,
What exactly do you want to do?
Alter database recover managed standby database; --->it will be in Manged Recovery mode.
Alter database mount standby database; ----> it will be mounted, but no log files applies.
Alter database open read only; ----> it will be open with read only option, but archeive logs will NOT be applied
If you want to apply the Archive logs which are trasfered from Primary, then you need to fire the below commands
Alter database recover managed standby database;
Alter database recover managed standby database using current logfile;
Alter database recover managed standby database using current logfile disconnect from session;
To stop applying archives then,
Alter database recover managed standby database cancel;
Thanks and Regards.
tnaresh1982

How to apply Oracle patch when physical standby database in place

Dear All,
I want to apply Oracle patchset 8 on 10.2.0.5 when physical standby database in place. What are the steps for Primary site and for standby site.
Thanks in advance
Kamran Laeeq

Hi Kamran,
You will not upgrade or patch the standby database by importing offline redologs. On the contrary, there is a procedure to do this. Please note that you will not transitiate the role from standby to primary or startup the database. You will just startup the database by executing "startup mount" and "startup upgrade", during the upgrade. It means that you will not change database role standby to primary and you will be able to continue to the log shipment after the respective upgrade.
But, it is very important that you should stop the log shipment and apply all the offline redologs, before the upgrade. Technically, you can import offline redologs after the upgrade, by changing "compatibility" parameter in oracle, but regarding to my experiences it may cause some problems after you transitiate the role from standby to primary.
In short;
In order to stop log shipment, at the primary site;
alter system set log_archive_dest_state_2=defer;
In order to import all the offline redologs without a delay, at the standby site;
alter database recover managed standby database cancel;
alter database recover managed standby database nodelay disconnect from session;
I hope that I clarified the issue,
Best regards,
Orkun Gedik

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 convert logical standby database to Physical Standby Database

Hi,
Does anyone know how to convert logical standby database(10.2.0.3) to Physical Standby Database(10.2.0.3)? Is this possible? If so,please give me steps for it.
Thanks.
Regards,
RJ.

I don't believe this to be possible. One of the steps invloved in the creation of a logical standby is the following:
ALTER DATABASE OPEN RESETLOGS;
This makes the logical standby a different incarnation of the db from the primary.
A physical standby is a binary copy of a primary db, a logical standby is a completely seperate db that just happens to get sql statements applied to it that are generated from a primary db, but is open read/write.
One avenue, though would be if you had flashback database enabled and you flashed back all the way to when the db was a physical standby and then rolled forward with the archived redo logs.
It's somewhat unlikely you are in that situation, but that is a possibility.
Indeed the 11g snapshot standby does this sort of thing:
http://download.oracle.com/docs/cd/B28359_01/server.111/b28294/manage_ps.htm#sthref740
jason.
http://jarneil.wordpress.com

How to create 11.2.0.2 physical standby database from 2 node RAC (11.2.0.2)

Hi,
Can any one please help me How to manually create 11.2.0.2 standalone physical standby database from 2 node RAC (11.2.0.2) database which is running in RHEL5 and ASM plugged in.
DB : 11.2.0.2
OS : RHEL5
RMAN duplicate is causing problem with network and we decided to go for manual creation of the same.
Thanks in Advance..

Hi;
Can any one please help me How to manually create 11.2.0.2 standalone physical standby database from 2 node RAC (11.2.0.2) database which is running in RHEL5 and ASM plugged in.
DB : 11.2.0.2
OS : RHEL5I had similar issue, what i did
1. Used source oracle_home on standby server
2. Created new asm instance and use same naming
3. I took RMAN full backup on source and move it to target
4. I edit initora file remove RAC setting and restore db(also edited listener file)
Regard
Helios

How to make a physical standby database in the read_only state in 11g?

In 10g, we can make a physical standby database in the read_only state. But in 11g, no a read_only state for a physical standby database. How to make a physical standby database in the read_only state in 11g?

Hi
read-only mode (for 11g physical standby)
A mode in which a database can be opened that allows queries, but disallows modifications.
A physical standby database can be opened read-only so that queries may be performed. If a license for the Oracle Active Data Guard option has been purchased, a physical satndby database can be open while redo apply is active. This capability is known as Real-time Query.
For more details have a look at:
http://download.oracle.com/docs/cd/B28359_01/server.111/b28294/manage_ps.htm#SBYDB00706
Hipe this Helps
Regards

Got RMAN error when running RMAN backup of archivelogs on physical standby database

Got below error when running RMAN backup of datafiles and archivelogs on physical standby database.
RMAN-06820: WARNING: failed to archive current log at primary database
ORACLE error from target database:
ORA-17629: Cannot connect to the remote database server
ORA-17627: ORA-00942: table or view does not exist
Could anyone help me? Thanks,

Hello;
When you connect RMAN to the source database as TARGET you must specify a password even if RMAN uses operating system authentication.
So the errors ORA-17627 and ORA-00942 appear to be cause and effect.
What version of Oracle? ( 11.2.0.4 according to the tag )
Can you post your backup script?
Best Regards
mseberg
Update
According to :
Database Error Messages 11g Release 2 (11.2) E17766-03
RMAN-06820: WARNING: failed to archive current log at primary database
Cause: An attempt to switch the archived log at the primary database failed.
So I would check my Primary alert log for an issue.
Message was edited by: mseberg

How to open a "manual" Physical standby database in read/write mode

Hi,
I am running Oracle Database 10g Release 10.2.0.3.0 - 64bit Production Standard Edition on Linux version 2.6.9-42.0.8.ELsmp ([email protected]) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-3))
I've created a physical standby database, but since I am running Standard Edition, I am not using the DataGuard features. I use the rsync utility to copy over the archivelogs to the standby database, and I apply them periodically to the standby database.
The standby database is started this way :
startup nomount pfile='/u01/oradata/orcl/initorcl.stdby';
alter database mount standby database;
Everything runs perfectly fine, I can do "alter database open read only" and then I can do selects into tables to confirm that everything is up to date.
The thing is, if I shutdown immediate the database, then do just startup :
shutdown immediate;
startup;
The database opens with no error messages, but is still in read-only mode...
I read that the default behavior for a standby database is to open read-only, like I am experiencing, but I would like to know what is the right way to open it correctly in read-write mode (I understand that after that, my standby will not be standby anymore and that I will have to recreate my standby database).
Thanks,
Mat

Hello,
There're features which allows you to open a Standby database in Read/Write mode but for all I know
it needs Entreprise Edition.
In Enterprise Edition you can use Logical Standby database. More over, for Physical standby there's
a way by using flashback database so as to rolling backward the database and avoiding to recreate
the Standby.
In Standard Edition I'm afraid that you'll have to recreate your Standby database.
Best regards,
Jean-Valentin

How to change the database character set on physical standby database?

Hi,
We have a database with character set WE8ISO8859P1 and migrated the character set to WE8MSWIN1252 using csscan/csalter scripts. This database has a physical standby database setup also and after the migration, the physical standby database is still showing the character set as WE8ISO8859P1. How can I change the characterset on the physical standby? I raised a Service Request with Oracle, and they said that recreating the standby database is the only supported way of changing the char set on the standby database. Is this true?
Thanks,
Sreekanth

Thank you, Robert, for your reply.
The standby is in sync with the primary.
see below
SYS@sisprod>select * from v$dataguard_stats;
NAME VALUE UNIT TIME_COMPUTED
apply finish time +00 00:00:00.0 day(2) to second(1) interval 12-NOV-2009 14:02:46
apply lag +00 00:00:00 day(2) to second(0) interval 12-NOV-2009 14:02:46
estimated startup time 11 second 12-NOV-2009 14:02:46
standby has been open N 12-NOV-2009 14:02:46
transport lag +00 00:00:00 day(2) to second(0) interval 12-NOV-2009 14:02:46
SYS@sisprod>
I am selecting from v$nls_parameters;
I don't know how to restore the controlfile from primary. Could you please tell me how to do it?
Thanks,
Sreekanth

How to check data in physical standby database?

Hi!
I'm maintaining physical standby database system. everyday, i must check tranfer and apply progress. I known, it operate very good. No archive gap is found.
But i want to check data in physical standby database that there is consistant with primary database, there isn't? What method do I use? How to do?
thankS

I hope the following will help
Verifying the Physical Standby Database
==========================================
Once you create the physical standby database and set up log transport services, you may want verify that database modifications are being successfully shipped from the primary database to the standby database.
To see the new archived redo logs that were received on the standby database, you should first identify the existing archived redo logs on the standby database, archive a few logs on the primary database, and then check the standby database again. The following steps show how to perform these tasks.
Step 1 Identify the existing archived redo logs.
On the standby database, query the V$ARCHIVED_LOG view to identify existing archived redo logs. For example:
SQL> SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME
2 FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
SEQUENCE# FIRST_TIME NEXT_TIME
8 11-JUL-02 17:50:45 11-JUL-02 17:50:53
9 11-JUL-02 17:50:53 11-JUL-02 17:50:58
10 11-JUL-02 17:50:58 11-JUL-02 17:51:03
3 rows selected.
Step 2 Archiving the current log.
On the primary database, archive the current log using the following SQL statement:
SQL> ALTER SYSTEM ARCHIVE LOG CURRENT;
Step 3 Verify that the new archived redo log was received.
On the standby database, query the V$ARCHIVED_LOG view to verify the redo log was received:
SQL> SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME
2> FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
SEQUENCE# FIRST_TIME NEXT_TIME
8 11-JUL-02 17:50:45 11-JUL-02 17:50:53
9 11-JUL-02 17:50:53 11-JUL-02 17:50:58
10 11-JUL-02 17:50:58 11-JUL-02 17:51:03
11 11-JUL-02 17:51:03 11-JUL-02 18:34:11
4 rows selected.
The logs are now available for log apply services to apply redo data to the standby database.
Step 4 Verify that the new archived redo log was applied.
On the standby database, query the V$ARCHIVED_LOG view to verify the archived redo log was applied.
SQL> SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
2 ORDER BY SEQUENCE#;
SEQUENCE# APP
8 YES
9 YES
10 YES
11 YES
4 rows selected.

How to identify that my physical standby database in use real time apply?

Hi,
Can any one give me the SQL to identifiy that my physical standby database is in real time applying redo logs?
Its urgen please....
Thanks.

You could just look at the alert log. Look for "Recovery of Online Redo Log"
Or you could select from v$standby_apply_snapshot to see if the standby is up-to-date.
select thread#, to_char(snapshot_time,'dd-mon-yyyy:hh24:mi'),
to_char(applied_time,'dd-mon-yyyy:hh24:mi'),
to_char(newest_time,'dd-mon-yyyy:hh24:mi') from V$STANDBY_APPLY_SNAPSHOT;

Problem creating physical Standby database with RMAN

Hi All
I am trying to learn oracle dataguard and as part of the process learning creating standby database.
Platform : Sun-Fire-V250 Sparc, Solaris 10
Database Version - Oracle 11R2
I am creating standby database on same server, so directory structure is different.
Following the instructions on Oracle site I managed to create a functional physical standby database. But I am not able to create standby database using RMAN. These are the steps that I followed-
1.Set up all necessary parameters on primary database as done while creating physical standby database manually, eg setting force logging, creating standby logs etc.
2.Edited parameter file on primary database as done while creating manual pysical standby database creation. Some of the changes done are-
On Primary Database:
*.FAL_CLIENT='orcl11020' #Primary database unique name
*.FAL_SERVER='stdby_11' #Standby database unique name
db_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020'
log_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11/redo_mem','/<dir>/oradata/orcl11020/redo_mem'
standby_file_management=auto
*.log_archive_config='DG_CONFIG=(orcl11020,stdby_11)'
*.log_archive_dest_1='LOCATION=/<dir>/flash_recovery_area/ORCL11020/archivelog
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=orcl11020'
*.log_archive_dest_2='SERVICE=stdby_11 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=stdby_11'
*.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
*.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
*.LOG_ARCHIVE_FORMAT='%t_%s_%r.arc'
*.LOG_ARCHIVE_MAX_PROCESSES=30
Copied same pfile for standby database and modified following-
*.control_files='/<dir>/oradata/stdby_11/stdby_11.ctl','/<dir>/fra_stdby/stdby_11/stdby_11.ctl'
*.db_name='orcl1102'
*.db_unique_name='stdby_11'
*.FAL_CLIENT='stdby_11'
*.FAL_SERVER='orcl11020'
db_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11'
log_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020/redo_mem','/<dir>/oradata/stdby_11/redo_mem'
standby_file_management=auto
*.log_archive_dest_1='LOCATION=/<dir>/fra_stdby/STDBY_11/archivelog
VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=stdby_11'
*.log_archive_dest_2='SERVICE=orcl11020 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
db_unique_name=orcl11020'
3. Add relevant information in tnsnames.ora and listener.ora files and then restart listener.
3. Created password file with same credential as primary database.
4.Up-to-date RMAN backup of primary database available.
5.Create standby controlfile with rman
While primary database s open (I tried with primary database in mount mode as well)-
$>rman catalog rman/paswd@rman target /
RMAN> BACKUP CURRENT CONTROLFILE FOR STANDBY;
6. Open a new terminal and startup standby database in nomount mode using parameter file created -
$>ORACLE_SID=stdby_11
$>export ORACLE_SID
$>sqlplus / as sysdba
SQL>STARTUP NOMOUNT pfile='<location/initfilename.ora'
SQL>quit
$> rman AUXILIARY / target sys/passwd@orcl11020 catalog rman/passwd@rman
RMAN>DUPLICATE TARGET DATABASE FOR STANDBY DORECOVER;
RMAN finishes without error but archive logs are not being tranported. Looking at the log, following caught my eye-
Error 1017 received logging on to the standby
Check that the primary and standby are using a password file
and remote_login_passwordfile is set to SHARED or EXCLUSIVE,
and that the SYS password is same in the password files.
returning error ORA-16191
FAL[client, ARC2]: Error 16191 connecting to orcl11020 for fetching gap sequence
Errors in file /<>dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
ORA-16191: Primary log shipping client not logged on standby
Errors in file /<dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
ORA-16191: Primary log shipping client not logged on standby
So on both primary and standby I confirmed
SQL> show parameter remote_login_passwordfile
NAME TYPE VALUE
remote_login_passwordfile string EXCLUSIVE
To make double sure that password files are same, I shutdown both databases, delete password files and recreated with same credentials.
Password files are called - orapworcl11020 and orapwstdby_11
Can someone guide me where thisngs are going wrong here please.

Not sure if I understood it clearly.
SELECT * FROM V$ARCHIVE_GAP;
returns no rows so there is no gap.
But could you please explain me the result of the previous query. To catch up again, on standby when I check
SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
SEQUENCE# APPLIED
75 NO
74 NO
76 NO
77 NO
I understand that though archive files have been copied across but they are not applied yet.
On primary when I give your query -
SELECT name as STANDBY,SEQUENCE#,applied, completion_time
2 FROM v$archived_log
3 where dest_id=2
4 and sequence# BETWEEN 74 and 80;
I get -
STANDBY SEQUENCE# APPLIED COMPLETIO
stdby_11 74 YES 28-JUN-11
stdby_11 75 YES 28-JUN-11
stdby_11 76 YES 29-JUN-11
stdby_11 77 YES 29-JUN-11
stdby_11 78 YES 29-JUN-11
stdby_11 79 YES 29-JUN-11
stdby_11 80 YES 29-JUN-11
stdby_11 75 NO 07-JUL-11
stdby_11 74 NO 07-JUL-11
stdby_11 76 NO 07-JUL-11
stdby_11 77 NO 07-JUL-11
stdby_11 78 NO 07-JUL-11
I have intentionally given
sequence# BETWEEN 74 and 80
because I know in the current incarnaion of the database, max sequence is 78.
So my understanding is, the rows between 28-29 June are from previous incarnation, correct me if I am wrong
Archive files of the current incarnation, since I successfully created standby database are shipped but yet to be applied - am I right?
Then my final question is, when will these archives be applied to standby database?
I am sorry to ask too many questions but I am just trying to understand how it all works.
Thanks for your help again

How Auto starting Physical Standby Database ( when Server Restart)

Similar Messages

Maybe you are looking for