Activate Standby Database

Hi,
I have a question regarding activation of an Oracle 8i Standby Database running under Manual Recovery mode.
Assuming the Primary database has crashed, are there any steps that I should take other than issue the Command 'Alter Database Activate Standby Database'.
Will the Standby controlfile automatically change status to "current" from "Standby".
Thanks
NewSolarisUser

Try this
1. Take it out of managed recovery mode.
2. Manually recover it up to the last archive
3. Execute 'clear' logfile.
4. Activate the standby datase.

Similar Messages

What is the Use of "Alter database activate standby database"

Hi ,
I appreciate your time.
I just wanted to know what is the use of "Alter database activate standby database" command when doing the failover. How different it will act in failover process. Can we use this command in SwitchOver.
Thanks in advance.

Hi Uwe Hesse,
Wonderfull... good info....
So my understanding is that the use of "ACTIVATE PHYSICAL STANDBY DATABASE" is conditional and depends on the redo log gap and the Database status(Able to mount or not).
Condition 1: If the Db is in Mount state and Redo log gap is successfully filled.
1) Flush any unsent redo from the primary database to the target standby database.
SQL> ALTER SYSTEM FLUSH REDO TO target_db_name;
Note: If the above Statement Completes successfully without any errors.
2) Stop Redo Apply.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
3) Finish applying all received redo data.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH;
4) Verify that the target standby database is ready to become a primary database.
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
5) Switch the physical standby database to the primary role.
SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY WITH SESSION SHUTDOWN;
Condition 2: If the DB is not able Mount and Redo Gap can't be filled.
Important Note: If the the above command in STEP3 gives error, some received redo data was not applied. Try to resolve the cause of the error and re-issue the statement before proceeding.
If the error condition cannot be resolved, a failover can still be performed (with some data loss) by issuing the following SQL statement on the target standby database:
SQL> ALTER DATABASE ACTIVATE PHYSICAL STANDBY DATABASE;
Thanks in advance.

Logical Standby Database with 10g+ASM on both sides??

Hi out there,
is there a known way to establish a logical standby database on 10g, if both
sides are running with an ASM setup?
I've tried to create one out of a physical standby database (which is set up
and running w/o any problems), like a book suggested me to do.
The procedure was:
1. switch on supplemental logging
2. prepare initiation parameters (for archive logging etc.) on both sides for
logical stb.
3. shut down the phyiscal standby
4. alter database create logical standby controlfile as '<path>'; on the
primary, transfer the controlfile to the standby db. Here I had to use RMAN
to copy the controlfile into the ASM System, and modify the initfile/spfile
in order to use the controlfile. No problem so far.
5. mount the standby database, alter database recover managed standby database
disconnect; -> At this point, the alert log complained about non-available
datafiles.
6. alter database activate standby database; --> fails ("needs recovery") due
to last point.
The trouble is, the controlfile created at point 4 cointains wrong paths to
the datafiles. Since I can not have the same disk group name on the standby
system, and since ASM renames the stored datafiles by its own, the complaints
of point 5 are comprehensible, but nevertheless annoying.
I tried to backup a controlfile to trace and change the paths, but at after
mounting the standby with this controlfile and proceeding at point 5, the
system says "<path> is not a standby controlfile"
Is there a different way of creating a "Logical Standby Database with 10g+ASM
on both sides"? Metalink said nothing about LogStby and ASM.
Best regards and thanks in advance,
Martin

I'm not sure if this will work but try:
1. create trace control file (you did it)
2. change paths (you did it)
3. recrate control file (you did it)
... there was error occured during mount before
so mount database (not as standby)
4. create standby control file (from recreated control file)
5. shutdown instance, replace control file with new standby control file or replace the control filename in parameter file.
6. mount as standby
What happend?
Update: Tested on my side and it has worked fine... How about you?
Message was edited by:
Ivan Kartik

Test physical standby database in dataguard

Hi all,
I had a successfull dataguard implementation for oracle 9r2.
Primary and standby databases are on different nodes, logs from primay are shipping and applying to physical standby database successfully.
As these database are for oracle 11i ebs, so for testing dataguard status i had created a table manually having columns date and remarks. Periodically i insert few records in this table in primary database and then chek this tabel in standby database (by opening in read only mode).
Now i want to test physical standby database with applications tier but don't want to disturb origional primary database.
as these are the normal switchover steps
1) at primary db
ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN;
2) at standby
ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY;
3) at primary, now this will be the stand by database
SHUTDOWN IMMEDIATE;
STARTUP MOUNT;
4) at standby, now this will be the primary database
SHUTDOWN IMMEDIATE;
STARTUP
My concern is if i skip step 1 and 3 and only execute step 2 and 4, will that be applicable for my requirement, or there is some other way to achieve this goal.
Regards,
Ken

To avoid touching the primary production DB, you may try to use the following command on your standby database side:
alter database activate standby database;
This will turn your standby database to primary database, however the log will be reset and this means you will need to rebuild your DR.
Another way is to use flash back feature on your standby database, activate it and revert back to the flashback point when the DR testing is done.

(V7.3) STANDBY DATABASE IN ORACLE 7.3

제품 : ORACLE SERVER
작성날짜 : 2004-08-13
SCOPE
Standard Edition 에서는 standby, data guard 기능은 지원하지 않으며, 이 기능을 대체하는 Oracle Fail Safe 는 Oracle 8.1.6 이상 부터 지원이 됩니다.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Standby database에 대하여
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1. 오라클 7.3 버젼에 추가된 new feature 로서 archive log mode 상태에서
online tablespace backup이 필요없는 새로운 backup/recovery 방법이다.
즉, archive log mode에서도 각 tablespace의 주기적인 online backup이
필요하였고, 이 작업에 따라 회복시간이 좌우되었다. Standby database를 잘 유지
하여줄 수 있는 환경이라면, online tablespace backup 대신 유용하게 사용될 수
있다.
2. 회복 시간은 작업량과 standby database에 archive log file이 어느 정도
반영되었느냐에 따라 다르다.
3. OPS와의 비교
instance를 두개 이상 사용하는 Oracle Parallel Server와 비교하는 것보다
위의 1번에서 소개한 환경과 비교하는 것이 더 적절하다.
4. 생성 방법
4.1 create the standby database
; standby db의 생성
1) back up the datafiles
2) startup mount;
alter database create standby controlfile as 'filename';
3) alter system archive log current;
4) transfer backup-datafile, archived log files, standby controlfile
to the safe place for standby database.
4.2 maintain the standby database
; log file을 standby db에 적용시켜 최신의 데이타로 유지함.
1) startup nomount;
2) alter database mount standby database;
3) recover standby database ;
4.3 activate the standby database
; primary database가 정상적으로 startup할 수 없을 때
1) alter database activate standby database;
!!! 일단 standby database를 기동시켰으면, 이전의 stand by database
상태로 되돌릴 수 없으니 신중하게 사용하여야 함.

I haven't done a Snapshot Standby (RAC or non-RAC). But I see no reason why it shouldn't work with a RAC Standby either.
The command is a Database level command, not an Instance level command.
Hemant K Chitale

Standby database recovery problems....

HP-UX 11.23
oracle 10.2.0.2
I know that this has been discussed quite a bit. I've spent a number of hours on this forum alone today just reading through the search hits. I've tried some of the 'tricks' that have been described in the threads. But I'm still getting the same error....
My standby database lost connectivity with my primary, and stopped receiving logs. I got no notification, because my scripts were not set up to catch this event...
The retention policy on my primary is 30 days of archive logs. After that, they are deleted. (I don't agree with it, but not my call)
The standby got more than 30 days out of sync, so I decided to just refresh the whole standby.
Since cold backups are not an option, I did an alter system checkpoint to flush all archive logs. Then I issued a complete hot backup.
Once completed, I went ahead and created a fresh standby control file, as well as a fresh backup control file. In that exact order.
I transferred all db files, archive logs, and control files over to the standby.
I ran the commands:
startup nomount;
(SUCCESSFUL)
alter database mount standby database;
(SUCCESSFUL)
recover standby database;
I let it run through all the archive log files until it errored saying it couldn't find "X" file being the next sequence that wasn't in the directory. Which to my understanding, is normal...time to quit recovery.
When I entered cancel, I get the following error.
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 7313561157126 generated at 12/17/2008 19:01:02 needed for
thread 1
ORA-00289: suggestion : /oraarch/swesc/1_13729_640853326.arc
ORA-00280: change 7313561157126 for thread 1 is in sequence #13729
ORA-00278: log file '/oraarch/swesc/1_13728_640853326.arc' no longer needed for
this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/ora1/oradata/peregrine/system01.dbf'
So my understanding of this is that it means that you still need to apply logs.
So I grabbed the logs that had been auto created during the time that I was rebuilding everything and applied them.
Same errors.
I'm at a loss here. How can it still be out of sync? Is there a way to force it to a specific sequence so that I can successfully open it and then shut it down to complete the sequence?
Thanks.

Thanks OrionNet. Great info!!
Here is the response.
OrionNet wrote:
select * from v$archive_gap
NO ROWS SELECTED.
and all the logs got applied
select applied , count(*) from v$archived_log;
-- This should return 1 rows with "YES", number of logs applied.
I had to change change this as it complained about "not a single-group group function
I changed it by adding group by applied to the end...
NO ROWS SELECTED
Then you should try activating standby database
SQL> alter database force nomount pfile='....'; -- or without the pfile
SQL> alter database mount standby database;
-- If all the archived logs have been applied to your standby then stop recovery
SQL> alter database recover manated standby cancel;
-- Note if it fails on activating the database ;shutdown and mount it again and activate (skip stopping recovery step).
SQL> alter database activate standby database;
IF successfull, then perform followin
SQL> alter database open;Regards
OrionNet;
I thought that in a primary/standby scenario, thiat this action would automatically shut down the primary. I can't have that.
HOLDING OFF ON REST FOR RESPONSE...
Edited by: WillyB on Dec 17, 2008 9:40 PM

How to re-synch primary and standby database?

Hello everyone,
Working on 10g R2/windows server 2003, I have configured a physical standby database but, I have an issue, and don't know how to resolve it.
We were making an update that made some DDL and DML on our application, and for security reason we
1. we ensure that primary and standby are in sync
2. We made a cold backup of the primary database
3. We Deferred the redo shipping between primary and standby
4. We applied changes on primary database
But the big issue is that, for any reason my colleague did the following.
a) made above steps 1,2,3,4
b) after the update he kept the resulted archived log files generated during to another location
c) He restore the cold backup before the update(step 2 above)
c) he applied again the update.
Now the issue is
At the first update step(2), the sequence# 553 was applied to the stand by before the update
At the second update step(c) above another sequence# 553 was created but stored localy in the primary database, because the both servers were deverged (step 3 above).
Technically both servers cannot be in sync again,because sequence# 553 at the first update has next_change# 80307804 and sequenc# 553 at the second update has next_change# 80461356.
Question:
How Can I do to rollback the the first sequence# 553 ( before the first update) on the standby database? in order to apply the sequence#553 generated at the second update and then re-sync both servers to roll forward subsequent sequence#? 554,etc...
Thank you for your help

Hello,
I have just tried the FLASHBACK DATABASE TO SCN XXXXXXXX;
but it doesn't work.
Here are steps used from my local dev envirronnment
From the stand by I retrieved the following information.
SEQUENCE# FIRST_CHANGE# NEXT_CHANGE# FIRST_TIM NEXT_TIME
95 707168 707906 15-AUG-08 15-AUG-08
96 707906 708653 15-AUG-08 15-AUG-08
97 708653 709359 15-AUG-08 15-AUG-08
100 710951 711794 15-AUG-08 15-AUG-08
98 709359 710179 15-AUG-08 15-AUG-08
99 710179 710951 15-AUG-08 15-AUG-08
101 711794 712762 15-AUG-08 15-AUG-08
102 712762 713720 15-AUG-08 15-AUG-08
103 713720 714748 15-AUG-08 15-AUG-08
104 714748 715920 15-AUG-08 15-AUG-08
105 715920 739430 15-AUG-08 15-AUG-08
106 739430 800525 15-AUG-08 16-AUG-08
107 800525 875810 16-AUG-08 17-AUG-08
108 875810 916527 17-AUG-08 18-AUG-08
SQL> alter database recover managed standby database cancel;
Database altered.
SQL> alter database activate standby database; --> prepare to open stby in R/W mode
Database altered.
SQL> startup mount force;
ORACLE instance started.
Total System Global Area 612368384 bytes
Fixed Size 1250428 bytes
Variable Size 180358020 bytes
Database Buffers 423624704 bytes
Redo Buffers 7135232 bytes
Database mounted.
SQL> alter database set standby database to maximize performance;
Database altered.
SQL> alter database open;
Database altered.
SQL> startup mount force;
ORACLE instance started.
Total System Global Area 612368384 bytes
Fixed Size 1250428 bytes
Variable Size 180358020 bytes
Database Buffers 423624704 bytes
Redo Buffers 7135232 bytes
Database mounted.
Now I tried to mimic the flashback database as in the production, to bring it back to sequence# 105 above
SQL> flashback database to scn 739430;
flashback database to scn 739430
ERROR at line 1:
ORA-38754: FLASHBACK DATABASE not started; required redo log is not available
ORA-38761: redo log sequence 75 in thread 1, incarnation 2 could not be
accessed
I'm reverted back the physical standby to its function
SQL> alter database convert to physical standby;
Database altered.
SQL> startup mount force;
ORACLE instance started.
Total System Global Area 612368384 bytes
Fixed Size 1250428 bytes
Variable Size 180358020 bytes
Database Buffers 423624704 bytes
Redo Buffers 7135232 bytes
Database mounted.
SQL> alter database recover managed standby database using current logfile disconne
Database altered.
Verifying if the MRP is up and running: YES see below
SQL> select message from v$dataguard_status;
MESSAGE
ARC0: Archival started
ARC1: Archival started
ARC2: Archival started
ARC3: Archival started
ARC3: Becoming the 'no FAL' ARCH
ARC3: Becoming the 'no SRL' ARCH
ARC1: Becoming the heartbeat ARCH
Attempt to start background Managed Standby Recovery process
MRP0: Background Managed Standby Recovery process started
Managed Standby Recovery starting Real Time Apply
Clearing online redo logfile 1 C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO11.LOG
11 rows selected.
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination C:\local_destination1_orcl
Oldest online log sequence 110
Next log sequence to archive 0
Current log sequence 110
So, how can I reslove this issue? without creating the standby from scratch?
Thanks Again for your help

Failover from standby database to primary database

Hi,
Can anyone suggest me, How to do " Standby DataGuard database to primary database (dataguard)".
Kindly Give me steps.
Thanks,
Shweta

Hi
Follow these steps
Oracle switchover operation:
1.     Check and verify the role parameter on the v$parameters both primary and standby
On Primary
Log_archive_dest_1=”this is the local archive destination”
+Log_archive_dest_2=”This is the Service [TNS ENTRY]”+
Log_archive_dest_state_1=Enable
Log_archive_dest_state_2=Enable
Fal_server=”this should have the tns entry for the standby
Fal_Client=”this should have the tns entry for the primary
Standby_archive_dest=”This should have the Location where the archive located”
Standby_File_Management=AUTO
On Standby
Log_archive_dest_1=”this is the local archive destination”
+Log_archive_dest_2=”This is the Service [TNS ENTRY]”+
Log_archive_dest_state_1=Enable
Log_archive_dest_state_2=DEfer
Fal_server=”this should have the tns entry for the primary
Fal_Client=”this should have the tns entry for the standby
Standby_archive_dest=”This should have the Location where the archive located”
Standby_File_Management=AUTO
2.     Down all the applications connects to the database
3.     Shutdown both primary and standby databases
4.     For RAC Keep Only one primary and One standby up and all other nodes should be down
5.     Check the Primary database on Open mode and the Standby database on mount stage
6.     On Primary
SQL>select switchover_status from v$database;Sessions Active or To standby will be appearing on the result
SQL> alter database commit to switchover to standby with session shutdown;
SQL> shutdown Immediate;
SQL>startup nomount;
SQL>alter database mount standby database;
SQL>Alter system set log_Archive_dest_state_2=defer;7.     On Standby
SQL>select switchover_status from v$database;it is acceptable to have Sessions Active or To Primary
SQL>alter database commit to switchover to primary with session shutdown;
SQL>shutdown immediate;
SQL>Startup;
SQL.>Alter system set log_archive_dest_state_2=enable;8.     On Primary
start the managed recovery
SQL>Alter database recover managed standby database disconnect from session;9.     Check the log shipment is working from New Primary to New Standby Using
SQL>Alter system switch logfile; ---- On New Primary.check the alert log on both Primary and Standby for the log shipment and Media recovery.
10.     If the switch over fail issue the following statement on standby (ORACLE 9i)
SQL> alter database recover managed standby database finish skip standby logfile ┘
SQL> alter database commit to switchover to primary┘
SQL> shutdown immediate;
SQL> Startup;11.     If this don’t work please issue the below statement
SQL> alter database activate standby database skip standby logfile;12.     If the switch over fail issue the following statement on standby (ORACLE 10g and above)
SQL> alter database recover managed standby database finish force;
SQL> alter database commit to switchover to primary;
SQL> alter database open;
SQL> shutdown Immediate;
SQL> startup;13. Added the temp file to your temp tablespace
If you follow the steps (10,11 & 12 ) you have to recreate the standby again. those steps are actually fail over steps. Hope this will be helpful
Cheers
Kanchana

10g dataguard - physical standby database

Hi Guys,
DB1 <Primary> - Production
DB2 <Physial Standby> - DR
I will need to startup my DB2 in DR segment for testing.
If i perform the below, will it affect my Production DB? I need it to be up and running as well.
DR:
recover managed standby database cancel;
shutdown immediate;
startup nomount;
alter database mount standby database;
recover standby database until cancel;
alter database activate standby database;
thanks

Hi,
In 10g version, you can open database database with READ ONLY mode. In that case standby database
recieve primary generated changes but not apply .
I see you steps you using ALTER DATABASE ACTIVATE STANDBY DATABASE statement for activating database
Activate the standby database using the SQL ALTER DATABASE ACTIVATE STANDBY DATABASE statement. This converts the standby database to a primary database, creates a new reset logs branch, and opens the database.*
If you are not need convert standby database to primary database then , you must use only
ALTER DATABASE OPEN READ ONLY;
Regards
Mahir M. Quluzade
www.mahir-quluzade.com

Open standby database read/write

What's the syntax to open a standby database read/write?
Any help will be appreciated.
Thanks

Technically it's not open Standy database read/write,
Activate the standby database using the SQL ALTER DATABASE ACTIVATE STANDBY DATABASE statement.
This converts the standby database to a primary database, creates a new reset logs branch, and opens the database. See Section 8.5 to learn how the standby database reacts to the new reset logs branch.
Physical Standby can only be open read/write in 11g with active standby option.

11gr2 bug on Linux with standby database

It looks like there is an oracle 11gr2 bug on linux with standby database. The following shows while activating standby database on Solairs, the standby database on Solaris will clear the standby logfile and recreate it. But, on Linux plateform it generated an exception instead. I don't beleive there is a bug open in metalink yet for this problem.
On Solaris SPARC 10 MU8
===============
ALTER DATABASE ACTIVATE STANDBY DATABASE
ALTER DATABASE ACTIVATE [PHYSICAL] STANDBY DATABASE (sdb1)
Begin: Standby Redo Logfile archival
End: Standby Redo Logfile archival
RESETLOGS after incomplete recovery UNTIL CHANGE 8469476
Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Errors in file /u01/app/oracle/product/11.2.0/db_1/log/diag/rdbms/sdb/sdb1/trace/sdb1_ora_3964.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/redo/redo_group1'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
Clearing online redo logfile 1 /redo/redo_group1
Clearing online log 1 of thread 1 sequence number 23
Errors in file /u01/app/oracle/product/11.2.0/db_1/log/diag/rdbms/sdb/sdb1/trace/sdb1_ora_3964.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/redo/redo_group1'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/product/11.2.0/db_1/log/diag/rdbms/sdb/sdb1/trace/sdb1_ora_3964.trc:
ORA-00367: checksum error in log file header
Deleted Oracle managed file /data/SDB/onlinelog/o1_mf_1_6hc48ykr_.log
Deleted Oracle managed file /arch/SDB/onlinelog/o1_mf_1_6hc48zoq_.log
Clearing online redo logfile 1 complete
Clearing online redo logfile 3 /redo/redo_group3_3.dbf
Clearing online log 3 of thread 2 sequence number 0
Clearing online redo logfile 3 complete
Resetting resetlogs activation ID 3157008110 (0xbc2c1eee)
On Redhat 5.5 x64
============
ALTER DATABASE ACTIVATE STANDBY DATABASE
ALTER DATABASE ACTIVATE [PHYSICAL] STANDBY DATABASE (sdby1)
Begin: Standby Redo Logfile archival
Errors in file /u01/app/oracle/product/11.2.0/db_1/log/diag/rdbms/sdby/sdby1/trace/sdby1_ora_10932.trc:
ORA-00314: log 7 of thread 2, expected sequence# 16 doesn't match 0
ORA-00312: online log 7 thread 2: '/redo/SDBY/onlinelog/sb_redo3'
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0xD9] [PC:0x22A55A5, ksfdcls()+45] [flags: 0x0, count: 1]
Errors in file /u01/app/oracle/product/11.2.0/db_1/log/diag/rdbms/sdby/sdby1/trace/sdby1_ora_10932.trc (incident=43361):
ORA-07445: exception encountered: core dump [ksfdcls()+45] [SIGSEGV] [ADDR:0xD9] [PC:0x22A55A5] [Address not mapped to object] []
ORA-00314: log 7 of thread 2, expected sequence# 16 doesn't match 0
ORA-00312: online log 7 thread 2: '/redo/SDBY/onlinelog/sb_redo3'

Then why did you post it here? No one from support reads these forums looking for things that belong in an SR: Open one and let us know how it is resolved.

Creating logical standby database

Hi all,
10.2.0.1
Following this link
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ls.htm
Where do i need to issue these statements:
SQL> EXECUTE DBMS_LOGSTDBY.BUILD;
SQL> ALTER DATABASE RECOVER TO LOGICAL STANDBY db_name;
on physical standby or primary database.
I issued the first stament on primary and second on physical standby .
IN the alert log of standby,i have the following entries.
Wed Jan 20 15:34:28 2010
Converting standby mount to primary mount.
Wed Jan 20 15:34:28 2010
ACTIVATE STANDBY: Complete - Database mounted as primary (treasury)
*** DBNEWID utility started ***
DBID will be changed from 306589979 to new DBID of 330710340 for database
.........................I am trying to create a logical standby database after creating a physical standby database.
It seems standby changed to primary which was not desired.
Thanks

Not tried myself, but you might want to have a look at this URL.
It appears to suggest that you need to change names of datafiles as well as value db_name explcitly on standby.

Creating triggers in a logical standby database

Does anyone know if its possible to create and enable a trigger in a logical standby database on a 'guarded' table? I've been able to create the trigger (as an after insert trigger) and it appears to be valid but it never seems to fire, despite inserts taking place. Are there any other steps involved to activate this, or is it just plain not possible in a logical standby? My primary and logical standby databases are 10.2.0.3

HI Daniel,
I appreciate your quick response.
My choice of name may not have been ideal, however changing new to another name - like gav - does not solve the problem.
SYS@UATDR> connect / as sysdba
Connected.
SYS@UATDR>
SYS@UATDR> select name, log_mode, database_role, guard_status, force_logging, flashback_on, db_unique_name
2 from v$database
3 /
NAME LOG_MODE DATABASE_ROLE GUARD_S FOR FLASHBACK_ON DB_UNIQUE_NAME
UATDR ARCHIVELOG LOGICAL STANDBY ALL YES YES UATDR
SYS@UATDR>
SYS@UATDR> create tablespace ts_gav
2 /
Tablespace created.
SYS@UATDR>
SYS@UATDR> create user gav
2 identified by gav
3 default tablespace ts_gav
4 temporary tablespace temp
5 quota unlimited on ts_gav
6 /
User created.
SYS@UATDR>
SYS@UATDR> grant connect, resource to gav
2 /
Grant succeeded.
SYS@UATDR> grant unlimited tablespace, create table, create any table to gav
2 /
Grant succeeded.
SYS@UATDR>
SYS@UATDR> -- show privs given to gav
SYS@UATDR> select * from dba_sys_privs where grantee='GAV'
2 /
GRANTEE PRIVILEGE ADM
GAV CREATE TABLE NO
GAV CREATE ANY TABLE NO
GAV UNLIMITED TABLESPACE NO
SYS@UATDR>
SYS@UATDR> -- create objects in schema
SYS@UATDR> connect gav/gav
Connected.
GAV@UATDR>
GAV@UATDR> -- prove ability to create tables
GAV@UATDR> create table gav
2 (col1 number not null)
3 tablespace ts_gav
4 /
create table gav
ERROR at line 1:
ORA-01031: insufficient privileges
GAV@UATDR>

How to open a standby database for use?

First, let me state that I am not a DBA nor am I a systems guy; I'm a software developer.
At work, we recently built a new virtualized db server by cloning our disaster recovery (DR) database server. The DR database was kept in 'standby' mode (I think that's the correct term) and was synched with production daily via archive logs.
So now, we have this new virtualized server that has a clone of that 'standby' database on it, and I need to 'open' that database so that it's usable (ie, no longer a standby db). How do I do that?? We recently lost our DBA so this has fallen into my lap.
From searching the web, I've found all sorts of instructions. It seems that I need to issue some commands via SQL*Plus? But as what user? From where do I issue these commands (I assume from the virtualized server)? And what are the commands?
This is Oracle 10g v10.2.0.3.0 running on Solaris 10 for x86.
Thanks!
Dave

Hi Dave, I do this each time we do a DR test. I have 10.2.0.3 in physical standby mode.
First, I make sure I have flashback turned on (here is what I've done):
connect / as sysdba
startup nomount
alter database mount standby database;
alter database flashback on;
alter database recover managed standby database through all switchover disconnect using current logfile;
exit;Activate the physical standby:
alter database recover managed standby database cancel;
alter database activate physical standby database;
alter database open;
exit;When completed with DR test we return the database back to physical standby mode:
Find the SCN when the physical standby was activated (this is so we can flashback to that point in time)
select standby_became_primary_scn from v$database;connect / as sysdba
flashback database to scn <this is the value returned from above>;
alter database convert to physical standby;
shutdown immediate
startup mount
alter database recover managed standby database disconnect from session;
exit;I hope that helps,
Michael Cunningham
Edited by: Michael C on Nov 10, 2011 8:59 AM
Edited by: Michael C on Nov 10, 2011 9:00 AM

Physical standby database fail-over

Hi,
I am working on Oracle 10.2.0.3 on Solaris SPARC 64-bit.
I have a Dataguard configuration with a single Physical standby database that uses real time application. We had a major application upgrade yesterday and before the start of upgrade, we cancelled the media recovery and disabled the log_archive_dest_n so that it doesn't ship the archive logs to standby site. We left the dataguard configuration in this mode incase of a rollback.
Primary:
alter system set log_archive_dest_state_2='DEFER';
alter system switch logfile;
Standby:
alter database recover managed standby database cancel;Due to application upgrade induced problems we had to failover to the physical standby, which was not in sync with primary from yesterday. I used the following method to fail-over since i do not want to apply any redo from yesterday.
Standby:
alter database activate physical standby database;
alter database open;
shutdown immediate;
startupSo, after this step, the database was a stand alone database, which doesn't have any standby databases yet (but it still has log_archive_config parameter set and log_archive_dest_n parameters set but i have 'DEFER' the log_archive_dest_n pointing to the old primary). I have even changed the "archive log deletion policy to NONE"
RMAN> configure archivelog deletion policy to none;After the fail-over was completed, the log sequence started from Sequence 1. We cleared the FRA to make space for the new archive logs and started off a FULL database backup (backup incremental level 0 database plus archivelog delete input). The backup succeded but we got these alerts in the backup log that RMAN cannot delete the archivelogs.
RMAN-08137: WARNING: archive log not deleted as it is still neededMy question here is
1) Even though i have disabled the log_archive_dest_n parameters, why is RMAN not able to delete the archivelogs after backup when there is no standby database for this failed-over database?
2) Are all the old backups marked unusable after a fail-over is performed?
FYI... flashback database was not used in this case as it did not server our purpose.
Any information or documentation links would be greatly appreciated.
Thanks,
Harris.

Thanks for the reply.
The FINISH FORCE works in some cases but if there is an archive gap (though it didn't report in our case), it might not work some times (DOCID: 846087.1). So, we followed the Switch-over & Fail-Over best practices where it mentioned about this "ACTIVE PHYSICAL STANDBY" for a fail-over if you intend not to apply any archivelogs. The process we followed is the Right one.
Anyhow, we got the issue resolved. Below is the resolution path.
1) Even though if you DEFER the LOG_ARCHIVE_DEST_STATE_N parameter's on the primary, there are some situations where the Primary database in a dataguard configuration where it will not delete the archive logs due to some SCN issues. This issue may or may not arise in all fail-over scenarios. If it does, then do the following checks
Follow DOCID: 803635.1, which talks about a PLSQL procedure to check for problematic SCN's in a dataguard configuration even though the physical standby databases are no available (i.e., if the dataguard parameters are set, log_archive_config, log_archive_dest_n='SERVICE=..." still set and even though corresponding LOG_ARCHIVE_DEST_STATE_N parameters are DEFERRED).
If this procedure returns any rows, then the primary database is not able to delete the archivelogs because it is still thinking there is a standby database and trying to save the archive logs because of the SCN conflict.
So, the best thing to do is, remove the DG related parameters from the spfile (log_archive_config, log_archive_dest_n parameters).
After i made these changes, i ran a test backup using "backup archivelog all delete input", the archive logs got deleted after backup without any issues.
Thanks,
Harris.
Edited by: user11971589 on Nov 18, 2010 2:55 PM

Activate Standby Database

Similar Messages

Maybe you are looking for