Standby sync

Hello
Recenlty i rebuild physical standby based on scn..Mine is a 2 node rac 10g database(primary) with a physical standby .There are 2 therads (thread 1 and thread 2) for some reason only from thread 1 its coming into physical stanby and it stopped after applying 2 logs .I missed the below steps as per document
--On the standby database, clear all standby redo log groups (there may be more than 3):
SQL> ALTER DATABASE CLEAR LOGFILE GROUP 1;
SQL> ALTER DATABASE CLEAR LOGFILE GROUP 2;
SQL> ALTER DATABASE CLEAR LOGFILE GROUP 3;
then i started the MRP:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT;
Can you please advice the next steps

Similar Messages

Standby sync problem.

Hi,
DB Version:10g R2
OS:LINUX
We have configured the physical standby database and it was running as expected, but due to some un know reasons one of the archivelog at primary side has been deleted and it is no longer available to be transferred and applied at standby side and hence now standby is not sysnc with primary DB. In this case how i can make the standby in sync with primary DB.
No backup of delete archivelog is avaliable.
I really appreciate the help.

Hi
THIS WORKS TRY THIS
In 10g you can use an incremental backup and recover the standby using the same to compensate for the missing archivelogs as shown below
In the case below archivelogs with sequence numbers 137 and 138 which are required on the standby are deleted to simulate this problem.
Step 1: On the standby database check the current scn.
STDBY>>select current_scn from v$database;
CURRENT_SCN
4793543
Step 2: On the primary database create the needed incremental backup from the above SCN
C:\Documents and Settings\frego>rman target /
Recovery Manager: Release 10.2.0.2.0 - Production on Wed Oct 25 13:39:04 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: USYD (DBID=768471617)
RMAN> BACKUP DEVICE TYPE DISK INCREMENTAL FROM SCN 4793543 DATABASE
FORMAT 'C:\temp\bkup_%U';
Starting backup at 25/OCT/06
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE\PRODUCT\10.2.0\ORADATA\USYD\SYSTEM01.DBF
input datafile fno=00002 name=C:\ORACLE\PRODUCT\10.2.0\ORADATA\USYD\UNDOTBS01.DBF
input datafile fno=00003 name=C:\ORACLE\PRODUCT\10.2.0\ORADATA\USYD\SYSAUX01.DBF
input datafile fno=00004 name=C:\ORACLE\PRODUCT\10.2.0\ORADATA\USYD\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 25/OCT/06
channel ORA_DISK_1: finished piece 1 at 25/OCT/06
piece handle=C:\TEMP\BKUP_02I0NSNE_1_1 tag=TAG20061025T134102 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:35
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current control file in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 25/OCT/06
channel ORA_DISK_1: finished piece 1 at 25/OCT/06
piece handle=C:\TEMP\BKUP_03I0NSOI_1_1 tag=TAG20061025T134102 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
Finished backup at 25/OCT/06
Step 3: Cancel managed recovery at the standby database
STDBY>>recover managed standby database cancel;
Media recovery complete.
Move the backup files to a new folder called INCR_BACKUP so that they are the only files in that folder.
Step 4: Catalog the Incremental Backup Files at the Standby Database
C:\oracle\product\10.2.0\db_1\database>rman target /
Recovery Manager: Release 10.2.0.2.0 - Production on Wed Oct 25 14:54:27 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: USYD (DBID=768471617, not open)
RMAN> CATALOG START WITH 'C:\temp\INCR_BACKUP';
searching for all files that match the pattern C:\temp\INCR_BACKUP
List of Files Unknown to the Database
=====================================
File Name: C:\TEMP\INCR_BACKUP\BKUP_02I0NSNE_1_1
File Name: C:\TEMP\INCR_BACKUP\BKUP_03I0NSOI_1_1
Do you really want to catalog the above files (enter YES or NO)? YES
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: C:\TEMP\INCR_BACKUP\BKUP_02I0NSNE_1_1
File Name: C:\TEMP\INCR_BACKUP\BKUP_03I0NSOI_1_1
Step 5: Apply the Incremental Backup to the Standby Database
RMAN> RECOVER DATABASE NOREDO;
Starting recover at 25/OCT/06
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=151 devtype=DISK
channel ORA_DISK_1: starting incremental datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
destination for restore of datafile 00001: C:\ORACLE\PRODUCT\10.2.0\ORADATA\STDB
Y\SYSTEM01.DBF
destination for restore of datafile 00002: C:\ORACLE\PRODUCT\10.2.0\ORADATA\STDB
Y\UNDOTBS01.DBF
destination for restore of datafile 00003: C:\ORACLE\PRODUCT\10.2.0\ORADATA\STDB
Y\SYSAUX01.DBF
destination for restore of datafile 00004: C:\ORACLE\PRODUCT\10.2.0\ORADATA\STDB
Y\USERS01.DBF
channel ORA_DISK_1: reading from backup piece C:\TEMP\INCR_BACKUP\BKUP_02I0NSNE_
1_1
channel ORA_DISK_1: restored backup piece 1
piece handle=C:\TEMP\INCR_BACKUP\BKUP_02I0NSNE_1_1 tag=TAG20061025T134102
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
Finished recover at 25/OCT/06
Step 6: Put the standby database back to managed recovery mode.
STDBY>> recover managed standby database nodelay disconnect;
Media recovery complete.
From the alert.log you will notice that the standby database is still looking for the old log files
FAL[client]: Failed to request gap sequence
GAP - thread 1 sequence 137-137
DBID 768471617 branch 600609988
This is because the controlfile has not been updated.
Hence the standby controlfile has to be recreated
On the primary
PRIM>>alter database create standby controlfile as 'C:\temp\standby01.ctl';
System altered.
Copy the standby control file to the standby site and restart the standby database in managed recovery mode...
Managed Standby Recovery not using Real Time Apply
parallel recovery started with 2 processes
Media Recovery Waiting for thread 1 sequence 139
As you can see from the above output the standby is now looking for the next archivelog.
If you have the luxury of time at your disposal you can do an export of the standby database in read only mode.
Cheers
Kanchana.

Standby sync check - Manual syncing

Hello,
I would like to re-confirm what DB views do we need to really check and make sure whether my primary & standby are in sync in a manual standby mode.
Should it be v$log and v$log_history or v$archived_log.
My doubt arises with one of my client current setup.Logs are manually shipped,and later manually recovered i.e not manged recovered process.
Today i did a manual healthcheck and i see there is no rows populated in v$archived_log with APPLIED='YES' on standby.But v$log_history showed me the current log sequence which is the same in primary too.From standby alert log i confirmed the sequence number is same as the value shown in v$log_history.
Oracle manual says,v$archived_log & v$log_history gets the related info from controlfile.
So why didnt v$archived_log didnt populate the same data as v$log_history.Sometimes i see a value far less in v$archvied_log when compared to v$log_history.
Below is my script which does manual recovery .
The archives are just scp'ed and done a manual recover using sql's.
This is the script part.
recover_auto ()
echo "\n`date`... Recovering database $ORACLE_SID." >>$LOGFILE
sqlplus -s "/ as sysdba" <<EOF >$TMPFILE
recover standby database ;
auto
exit
EOF
Here is my output.
@primary:
SQL> select THREAD#,max(SEQUENCE#) ,ARCHIVED,APPLIED from V$ARCHIVED_LOG group by THREAD#,ARCHIVED,APPLIED
2 /
THREAD# MAX(SEQUENCE#) ARC APP
1 75883 YES NO
@standby
SQL> select count(*) from V$ARCHIVED_LOG
2 /
COUNT(*)
0
SQL> select max(SEQUENCE#) from v$log_history
2 /
MAX(SEQUENCE#)
75883
Does the view v$archived_log & v$log_hisotry behave differently after an restart of the DR(manaul shipping & applying methods) ?
Regards
Sreeraj

Hello,
As i have already mentioned the archives are manually shipped using rsync command.There is no a remote location defined on primary.We simply pull the archives from primary and put it into a location on remote. Later recovery script is run which will recover using these archives.
So your query does not provide enough data.
Even though i do a manual recovery on standby, those details on sequence should be there in the standby controlfile. Am i right.But if you check my previous note, count from v$archved_log shows zero.
This is were am stuck.
Thanks,
sreeraj

CSM-S active / standby sync

Hi All,
We have 6509 switch with FWSM (Bridged) and CSM in two different buildings, say site-A is Primary and site-B is DR. These two 6500 switch are configured with HSRP to decide primary. I can reach DR switch, FWSM and CSM but unable to reach the SSL module on DR side. Don't understand why. When I do ping, I get 1 successful reply after 10 - 15 failure ping request. I suspect it could be because of the bridged mode but not sure. Also I am doubt that is it possible to have CSM actvie / standby like this.
Would be grateful if could help me to understand on this.
Thanks

Hi
The SSL module management IP is reachable intermittently. It respond 3 ping requests out of 10. So don't know what is happening with SSL module. When I do config sync from Primary switch CSM configs are get replicated successfully so it means intercommunication between Primay and Standby CSM is fine. Only problem to reach the SSL module in standby.
Thanks

Facing issues in standby database

standby database is in sync but when we say archive log list "Current log sequence " and "Oldest online log sequence" are not geting updated
even though archives are getting applied.
Solution :- We can create new standby controlfile in order to get those archive sync .
Question :- why we are still receiving alert log errors when the standby database is running in Max performance? We have these standby files from so many days but recently we are able to see these errors
Any help regarding this is much appreciate.
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /ofa/u001/PRMAN/app/oracle/admin/arch
Oldest online log sequence 179147
Next log sequence to archive 0
Current log sequence 179149
Standby alert log error message:-
Media Recovery Log /ofa/u001/PRMAN/app/oracle/admin/arch/1_189733_608563408.dbf
Clearing online log 6 of thread 0 sequence number 0
Errors in file /ofa/u001/PRMAN/app/oracle/admin/diag/rdbms/prmangfd/PRMAN/trace/PRMAN_ora_18720.trc:
ORA-00367: checksum error in log file header
ORA-00315: log 6 of thread 0, wrong thread # 1 in header
ORA-00312: online log 6 thread 0: '/ofa/u001/PRMAN/oradata/redologs1/stbyredo03.log'
RFS[16]: Opened log for thread 1 sequence 189734 dbid 1005584078 branch 608563408
Media Recovery Waiting for thread 1 sequence 189734 (in transit)
Mon Jul 29 12:06:03 2013
Archived Log entry 13297 adde
Trace file info:-
ORA-00367: checksum error in log file header
ORA-00315: log 6 of thread 0, wrong thread # 1 in header
ORA-00312: online log 6 thread 0: '/ofa/u001/PRMAN/oradata/redologs1/stbyredo03.log'
DDE rules only execution for: ORA 312
Standby sync status:-
DB_NAME HOSTNAME LOG_ARCHIVED LOG_APPLIED APPLIED_TIME LOG_GAP
PRMAN GFDHP122 176449 189700 29-JUL/10:29 -13251
Primary:-
DB_NAME HOSTNAME LOG_ARCHIVED LOG_APPLIED APPLIED_TIME LOG_GAP
PRMAN NGMHP121 189702 189700 29-JUL/10:41 2
standby redo logs :-
select group#, dbid, thread#, blocksize,used, status, sequence# from v$standby_log
GROUP# DBID THREAD# BLOCKSIZE USED STATUS SEQUENCE#
4 UNASSIGNED 0 1024 0 UNASSIGNED 0
5 UNASSIGNED 0 1024 0 UNASSIGNED 0
6 UNASSIGNED 0 1024 0 UNASSIGNED 0
Members of standby redo log file:-
select * from v$logfile where type='STANDBY'
SQL> /
GROUP# STATUS TYPE MEMBER IS_
4 STANDBY /ofa/u001/PRMAN/oradata/redologs1/stbyredo01.log NO
5 STANDBY /ofa/u001/PRMAN/oradata/redologs1/stbyredo02.log NO
6 STAND
Thanks,
Kumar Dharamoni

Hello;
I think I would try to clear the log :
Example
ALTER DATABASE CLEAR LOGFILE GROUP 3;
Do this for any groups you are having this issue with.
Best Regards
mseberg

Replacement of primary unit failed! (ASA5510 active/standby)

Hi all,
I have an issue bringing up my RMA'd primary ASA unit.
So what happened so far:
1. primary unit failed
2. secondary took over and is now secondary - active (as per sh fail)
2. requested RMA at Cisco
3. got ASA and checked that Lic (SSL), OS (8.2.2) and ASDM are at the same level as the secondary
4. issued wr erase and reloaded
5. copied the following commands to the new (RMA) primary unit:
failover lan unit primary
failover lan interface Failover Ethernet3
failover interface ip Failover 172.x.x.9 255.255.255.248 standby 172.x.x.10
int eth3
no shut
failover
wr mem
6. installed primary unit into rack
7. plugged-in all cables (network, failover, console and power)
8. fired up the primary unit
9. expected that the unit shows:
Detected an Active mate
Beginning configuration replication from mate.
End configuration replication from mate.
10. but nothing happened on primary unit
So can anyone give me assistance on what is a valid and viable approach in replacing a failed primary unit? Is there a missing step that hinders me to successfully replicate the secondary - active config to the primary - standby unit.
I was looking for help on the net but unfortunately I was not able to find anything related to ASA55xx primary unit replacement with a clear guideline or step by step instructions.
Any comments or suggestions are appreciated, and might help others who are in the same situation.
Thanks,
Nico

Hi Varun,
Thanks for catching-up this thread.
Here you go:
sh run fail on secondary - active:
failover
failover lan unit secondary
failover lan interface Failover Ethernet0/3
failover key *****
failover link Failover Ethernet0/3
failover interface ip Failover 172.x.x.9 255.255.255.248 standby 172.x.x.10
sh fail hist on secondary - active:
asa1# sh fail hist
==========================================================================
From State                 To State                   Reason
==========================================================================
23:47:15 CEST Feb 19 2011
Not Detected               Negotiation                No Error
23:47:19 CEST Feb 19 2011
Negotiation                Cold Standby               Detected an Active mate
23:47:21 CEST Feb 19 2011
Cold Standby               Sync Config                Detected an Active mate
23:47:36 CEST Feb 19 2011
Sync Config                Sync File System           Detected an Active mate
23:47:36 CEST Feb 19 2011
Sync File System           Bulk Sync                  Detected an Active mate
23:47:50 CEST Feb 19 2011
Bulk Sync                  Standby Ready              Detected an Active mate
10:34:09 CEDT Sep 3 2011
Standby Ready              Just Active                HELLO not heard from mate
10:34:09 CEDT Sep 3 2011
Just Active                Active Drain               HELLO not heard from mate
10:34:09 CEDT Sep 3 2011
Active Drain               Active Applying Config     HELLO not heard from mate
10:34:09 CEDT Sep 3 2011
Active Applying Config     Active Config Applied      HELLO not heard from mate
10:34:09 CEDT Sep 3 2011
Active Config Applied      Active                     HELLO not heard from mate
==========================================================================
sh fail on secondary - active
asa1# show fail
Failover On
Failover unit Secondary
Failover LAN Interface: Failover Ethernet0/3 (up)
Unit Poll frequency 1 seconds, holdtime 15 seconds
Interface Poll frequency 5 seconds, holdtime 25 seconds
Interface Policy 1
Monitored Interfaces 2 of 110 maximum
Version: Ours 8.2(2), Mate 8.2(2)
Last Failover at: 10:34:09 CEDT Sep 3 2011
        This host: Secondary - Active
                Active time: 441832 (sec)
                slot 0: ASA5510 hw/sw rev (2.0/8.2(2)) status (Up Sys)
                  Interface Outside (x.x.x.14): Normal (Waiting)
                  Interface Inside (x.x.x.11): Normal (Waiting)
                slot 1: empty
        Other host: Primary - Failed
                Active time: 40497504 (sec)
                slot 0: ASA5510 hw/sw rev (2.0/8.2(2)) status (Unknown/Unknown)
                  Interface Outside (x.x.x.15): Unknown
                  Interface Inside (x.x.x.12): Unknown
                slot 1: empty
Stateful Failover Logical Update Statistics
        Link : Failover Ethernet0/3 (up)
        Stateful Obj    xmit       xerr       rcv        rerr
        General         2250212    0          64800624   309
        sys cmd         2250212    0          2249932    0
        up time         0          0          0          0
        RPC services    0          0          0          0
        TCP conn        0          0          46402635   309
        UDP conn        0          0          21248      0
        ARP tbl         0          0          15921639   0
        Xlate_Timeout   0          0          0          0
        IPv6 ND tbl     0          0          0          0
        VPN IKE upd     0          0          96977      0
        VPN IPSEC upd   0          0          108174     0
        VPN CTCP upd    0          0          19         0
        VPN SDI upd     0          0          0          0
        VPN DHCP upd    0          0          0          0
        SIP Session     0          0          0          0
        Logical Update Queue Information
                        Cur     Max     Total
        Recv Q:         0       17      203259096
        Xmit Q:         0       1       2250212
show ver on secondary - active
asa1# sh ver
Cisco Adaptive Security Appliance Software Version 8.2(2)
Device Manager Version 6.2(5)53
Compiled on Mon 11-Jan-10 14:19 by builders
System image file is "disk0:/asa822-k8.bin"
Config file at boot was "startup-config"
asa1 up 200 days 12 hours
failover cluster up 1 year 108 days
Hardware:   ASA5510, 256 MB RAM, CPU Pentium 4 Celeron 1600 MHz
Internal ATA Compact Flash, 256MB
Slot 1: ATA Compact Flash, 64MB
BIOS Flash M50FW080 @ 0xffe00000, 1024KB
Encryption hardware device : Cisco ASA-55x0 on-board accelerator (revision 0x0)
                             Boot microcode   : CN1000-MC-BOOT-2.00
                             SSL/IKE microcode: CNLite-MC-SSLm-PLUS-2.03
                             IPSec microcode : CNlite-MC-IPSECm-MAIN-2.04
0: Ext: Ethernet0/0         : address is 0022.55cf.7420, irq 9
1: Ext: Ethernet0/1         : address is 0022.55cf.7421, irq 9
2: Ext: Ethernet0/2         : address is 0022.55cf.7422, irq 9
3: Ext: Ethernet0/3         : address is 0022.55cf.7423, irq 9
4: Ext: Management0/0       : address is 0022.55cf.741f, irq 11
5: Int: Not used            : irq 11
6: Int: Not used            : irq 5
Licensed features for this platform:
Maximum Physical Interfaces    : Unlimited
Maximum VLANs                  : 100
Inside Hosts                   : Unlimited
Failover                       : Active/Active
VPN-DES                        : Enabled
VPN-3DES-AES                   : Enabled
Security Contexts              : 2
GTP/GPRS                       : Disabled
SSL VPN Peers                  : 10
Total VPN Peers                : 250
Shared License                 : Disabled
AnyConnect for Mobile          : Disabled
AnyConnect for Cisco VPN Phone : Disabled
AnyConnect Essentials          : Disabled
Advanced Endpoint Assessment   : Disabled
UC Phone Proxy Sessions        : 2
Total UC Proxy Sessions        : 2
Botnet Traffic Filter          : Disabled
This platform has an ASA 5510 Security Plus license.
Serial Number: xxx
Running Activation Key:xxxx
Configuration register is 0x1
Configuration last modified by enable_1 at 10:05:32.149 CEDT Fri Jul 15 2011

Syncing Test DB with Prod

Hi
I have a requirement to keep in sync my test DB with prod everyday. Database size is more than 2Tb (cloning everyday not possible considering the size). I know about streams but wanted to know is there any other option such as taking incremental level backups from prod and apply it in test everynight.
Is it possible as is the case in this thread
Re: standby sync problem.
OS : OEL5
Oracle : 10GR2
Thanks
Ankurk

to keep in sync my test DB with prod everydayI'm not sure to understand what's the point to have a test database up-to-date from prod db...
Anyway, you could go for a standby database which you could probably open in read-write mode, then nightly restore to point in-time (before opening in read-write) and apply the redologs generated on primary database during that day.
But again, why making a test database with daily data from prd ? A test db should be separated from prd, from my point of view, it should not be linked to prd database as a standby database.
Nicolas.

My Active dataguard is not applying archives.

Dears,
Following is my setup
=====================
Primary:
prod on RAC with 2 nodes
Database : Oracle 11.2.0.3
OS OEL 5.7
storage : ASM
+DATADG
+FLASHDG
Standby:
sync on single node
Database : Oracle 11.2.0.3
storage : ASM
+DATADG
+FLASHDG
I've configured Active dataguard successfully and was able to apply archivelogs successfully instantly.
Archive log locations are +FLASHDG/prod/ARCHIVELOG/ AND /u02/arch --- on primary
Archive log locations are +FLASHDG/stby/ARCHIVELOG/ AND /u02/arch --- on standby
On Standby
===========
SQL> select 'Using Active Data Guard' ADG from v$managed_standby m,v$database d where m.process like 'MRP%' ;
ADG
Using Active Data Guard
SQL> select open_mode,database_role,PROTECTION_MODE,PROTECTION_LEVEL from v$database;
OPEN_MODE DATABASE_ROLE PROTECTION_MODE PROTECTION_LEVEL
READ ONLY WITH APPLY PHYSICAL STANDBY MAXIMUM PERFORMANCE MAXIMUM PERFORMANCE
SQL>
Upto now everything is ok, means same data is sync on primary and standby. As my archive location was getting full, i've used this SQL query to clean them
SELECT 'alter diskgroup '||dg.name||' drop file
''+'||dg.name||''||SYS_CONNECT_BY_PATH(al.name,'/')||''';'
FROM v$asm_alias al, v$asm_file fi, v$asm_diskgroup dg
WHERE al.file_number = fi.file_number(+)
AND al.group_number = dg.group_number
AND fi.type = 'ARCHIVELOG'
START WITH alias_index = 0
CONNECT BY PRIOR al.reference_index = al.parent_index;
SELECT 'alter diskgroup '||dg.name||' drop file
''+'||dg.name||''||SYS_CONNECT_BY_PATH(al.name,'/')||''';'
FROM v$asm_alias al, v$asm_file fi, v$asm_diskgroup dg
WHERE al.file_number = fi.file_number(+)
AND al.group_number = dg.group_number
AND fi.type = 'BACKUPSET'
START WITH alias_index = 0
CONNECT BY PRIOR al.reference_index = al.parent_index;
In order to delete ARCHIVE logs which are stored in ASM FLASHDG, which will have a type of "ARCHIVELOG" and "BACKUPSET" i've used this above two queries.
After performing this steps , my Active dataguard is not applying archives.
On the primary server, check the latest archived redo log
SELECT sequence#, first_time, next_time
FROM v$archived_log
ORDER BY sequence#;
2809 16-APR-13 16-APR-13
2809 16-APR-13 16-APR-13
2809 16-APR-13 16-APR-13
2810 16-APR-13 16-APR-13
2810 16-APR-13 16-APR-13
2810 16-APR-13 16-APR-13
2811 16-APR-13 16-APR-13
2811 16-APR-13 16-APR-13
2811 16-APR-13 16-APR-13
2812 16-APR-13 16-APR-13
2812 16-APR-13 16-APR-13
2812 16-APR-13 16-APR-13
2813 16-APR-13 16-APR-13
2813 16-APR-13 16-APR-13
2814 16-APR-13 16-APR-13
2814 16-APR-13 16-APR-13
2815 16-APR-13 16-APR-13
2815 16-APR-13 16-APR-13
2816 16-APR-13 16-APR-13
2816 16-APR-13 16-APR-13
2817 16-APR-13 16-APR-13
2817 16-APR-13 16-APR-13
2818 16-APR-13 16-APR-13
2818 16-APR-13 16-APR-13
2819 16-APR-13 16-APR-13
2819 16-APR-13 16-APR-13
2820 16-APR-13 16-APR-13
2820 16-APR-13 16-APR-13
2821 16-APR-13 16-APR-13
2821 16-APR-13 16-APR-13
2822 16-APR-13 16-APR-13
2822 16-APR-13 16-APR-13
2823 16-APR-13 16-APR-13
2823 16-APR-13 16-APR-13
2824 16-APR-13 16-APR-13
2824 16-APR-13 16-APR-13
2825 16-APR-13 16-APR-13
2825 16-APR-13 16-APR-13
2826 16-APR-13 16-APR-13
2826 16-APR-13 16-APR-13
2827 16-APR-13 16-APR-13
2827 16-APR-13 16-APR-13
2828 16-APR-13 16-APR-13
2828 16-APR-13 16-APR-13
2829 16-APR-13 16-APR-13
2829 16-APR-13 16-APR-13
2830 16-APR-13 16-APR-13
2830 16-APR-13 16-APR-13
2831 16-APR-13 16-APR-13
2831 16-APR-13 16-APR-13
2832 16-APR-13 16-APR-13
2832 16-APR-13 16-APR-13
2833 16-APR-13 16-APR-13
2833 16-APR-13 16-APR-13
2834 16-APR-13 16-APR-13
2834 16-APR-13 16-APR-13
2835 16-APR-13 16-APR-13
2835 16-APR-13 16-APR-13
2836 16-APR-13 16-APR-13
2836 16-APR-13 16-APR-13
2837 16-APR-13 16-APR-13
2837 16-APR-13 16-APR-13
2838 16-APR-13 16-APR-13
2838 16-APR-13 16-APR-13
2839 16-APR-13 16-APR-13
2839 16-APR-13 16-APR-13
2840 16-APR-13 16-APR-13
2840 16-APR-13 16-APR-13
2841 16-APR-13 16-APR-13
2841 16-APR-13 16-APR-13
2842 16-APR-13 16-APR-13
2842 16-APR-13 16-APR-13
2843 16-APR-13 16-APR-13
2843 16-APR-13 16-APR-13
2844 16-APR-13 16-APR-13
2844 16-APR-13 16-APR-13
2845 16-APR-13 16-APR-13
2845 16-APR-13 16-APR-13
2846 16-APR-13 16-APR-13
2846 16-APR-13 16-APR-13
Check the new archived redo log has arrived at the standby server and been applied.
SELECT sequence#, first_time, next_time, applied
FROM v$archived_log
ORDER BY sequence#;
2801 15-APR-13 15-APR-13 YES
2801 15-APR-13 15-APR-13 YES
2802 15-APR-13 15-APR-13 YES
2802 15-APR-13 15-APR-13 YES
2803 15-APR-13 15-APR-13 YES
2803 15-APR-13 15-APR-13 YES
2804 15-APR-13 15-APR-13 YES
2804 15-APR-13 15-APR-13 YES
2805 15-APR-13 15-APR-13 YES
2805 15-APR-13 15-APR-13 YES
2806 15-APR-13 15-APR-13 YES
2806 15-APR-13 15-APR-13 YES
2807 15-APR-13 15-APR-13 YES
2807 15-APR-13 15-APR-13 YES
2808 15-APR-13 16-APR-13 YES
2808 15-APR-13 16-APR-13 YES
2809 16-APR-13 16-APR-13 YES
2809 16-APR-13 16-APR-13 YES
2810 16-APR-13 16-APR-13 YES
2810 16-APR-13 16-APR-13 YES
2811 16-APR-13 16-APR-13 YES
2811 16-APR-13 16-APR-13 YES
2812 16-APR-13 16-APR-13 IN-MEMORY
2812 16-APR-13 16-APR-13 YES
So could anyone help me to resolve this issue. Anticipating your response at the earliest.
Regards,
VIKHAR
Edited by: VIKHARAHMED on Apr 16, 2013 9:38 AM

Here is the alert log file
Media Recovery Log +FLASHDG/stby/archivelog/2013_04_16/thread_2_seq_1476.1987.812900733
Tue Apr 16 18:56:42 2013
Primary database is in MAXIMUM PERFORMANCE mode
RFS[1]: Assigned to RFS process 16803
RFS[1]: Selected log 12 for thread 2 sequence 1485 dbid 220323208 branch 808484882
Tue Apr 16 18:56:42 2013
RFS[2]: Assigned to RFS process 16807
RFS[2]: Opened log for thread 2 sequence 1484 dbid 220323208 branch 808484882
Archived Log entry 6324 added for thread 2 sequence 1484 rlc 808484882 ID 0xd21a288 dest 10:
Tue Apr 16 19:09:02 2013
RFS[1]: Selected log 11 for thread 2 sequence 1486 dbid 220323208 branch 808484882
Tue Apr 16 19:09:02 2013
Archived Log entry 6325 added for thread 2 sequence 1485 ID 0xd21a288 dest 1:
Archived Log entry 6326 added for thread 2 sequence 1485 ID 0xd21a288 dest 2:
Tue Apr 16 19:12:23 2013
RFS[1]: Selected log 12 for thread 2 sequence 1487 dbid 220323208 branch 808484882
Tue Apr 16 19:12:23 2013
Archived Log entry 6327 added for thread 2 sequence 1486 ID 0xd21a288 dest 1:
Archived Log entry 6328 added for thread 2 sequence 1486 ID 0xd21a288 dest 2:
Tue Apr 16 19:14:41 2013
"alert_stby.log" 845L, 33990C 782,1 94%
Tue Apr 16 19:17:27 2013
Archived Log entry 6331 added for thread 2 sequence 1488 ID 0xd21a288 dest 1:
Archived Log entry 6332 added for thread 2 sequence 1488 ID 0xd21a288 dest 2:
Tue Apr 16 19:25:51 2013
RFS[1]: Selected log 11 for thread 2 sequence 1490 dbid 220323208 branch 808484882
Tue Apr 16 19:25:51 2013
Archived Log entry 6333 added for thread 2 sequence 1489 ID 0xd21a288 dest 1:
Archived Log entry 6334 added for thread 2 sequence 1489 ID 0xd21a288 dest 2:
Tue Apr 16 19:51:02 2013
RFS[1]: Selected log 12 for thread 2 sequence 1491 dbid 220323208 branch 808484882
Tue Apr 16 19:51:02 2013
Archived Log entry 6335 added for thread 2 sequence 1490 ID 0xd21a288 dest 1:
Archived Log entry 6336 added for thread 2 sequence 1490 ID 0xd21a288 dest 2:
Tue Apr 16 20:37:12 2013
RFS[1]: Selected log 11 for thread 2 sequence 1492 dbid 220323208 branch 808484882
Tue Apr 16 20:37:12 2013
Archived Log entry 6337 added for thread 2 sequence 1491 ID 0xd21a288 dest 1:
Archived Log entry 6338 added for thread 2 sequence 1491 ID 0xd21a288 dest 2:
Tue Apr 16 21:08:23 2013
RFS[1]: Selected log 12 for thread 2 sequence 1493 dbid 220323208 branch 808484882
Tue Apr 16 21:08:23 2013
Archived Log entry 6339 added for thread 2 sequence 1492 ID 0xd21a288 dest 1:
Archived Log entry 6340 added for thread 2 sequence 1492 ID 0xd21a288 dest 2:
Tue Apr 16 22:16:06 2013
RFS[1]: Selected log 11 for thread 2 sequence 1494 dbid 220323208 branch 808484882
Tue Apr 16 22:16:06 2013
Archived Log entry 6341 added for thread 2 sequence 1493 ID 0xd21a288 dest 1:
Archived Log entry 6342 added for thread 2 sequence 1493 ID 0xd21a288 dest 2:
Tue Apr 16 22:31:46 2013
RFS[1]: Selected log 12 for thread 2 sequence 1495 dbid 220323208 branch 808484882
Tue Apr 16 22:31:46 2013
Archived Log entry 6343 added for thread 2 sequence 1494 ID 0xd21a288 dest 1:
Archived Log entry 6344 added for thread 2 sequence 1494 ID 0xd21a288 dest 2:
Wed Apr 17 09:31:59 2013
RFS[1]: Selected log 11 for thread 2 sequence 1496 dbid 220323208 branch 808484882
Wed Apr 17 09:32:00 2013
Archived Log entry 6345 added for thread 2 sequence 1495 ID 0xd21a288 dest 1:
Archived Log entry 6346 added for thread 2 sequence 1495 ID 0xd21a288 dest 2:

ASA failover: secondary ASA disabled failover on its own

Hi all
I have a failover pair of ASA 5520 (Software Version 8.2(4)4)
located in two different data centers.
Because of a network issue the layer 2 connection between both locations has been interrupted for a couple of seconds and the ASAs went into split-brain as one would expect them to do.
The thing is that after approx. 1 minute the secondary ASA switched off its failover configuration (i.e. "show run" gives "no failover") without anybody telling it to do so. Here is the "show failover history" of the device:
07:57:34 MESZ Aug 15 2011
Standby Ready              Just Active                HELLO not heard from mate
07:57:34 MESZ Aug 15 2011
Just Active                Active Drain               HELLO not heard from mate
07:57:34 MESZ Aug 15 2011
Active Drain               Active Applying Config     HELLO not heard from mate
07:57:34 MESZ Aug 15 2011
Active Applying Config     Active Config Applied      HELLO not heard from mate
07:57:34 MESZ Aug 15 2011
Active Config Applied      Active                     HELLO not heard from mate
07:58:03 MESZ Aug 15 2011
Active                     Cold Standby               Failover state check
07:58:18 MESZ Aug 15 2011
Cold Standby               Disabled                   HA state progression failed
At this point failover was switched off completely and the split-brain remained even after the layer-2-connection has been reestablished.
This is no good.:( I have searched for "HA state progression failed" without any useful result/explanation.
Why did the device switch off failover on its own and how can we assure that it won't do this again?
Best regards,
Grischa

Yes, only thing I needed to do was issuing "failover" on the secondary. It detected its active mate and went properly into standby:
09:16:18 MESZ Aug 15 2011
Disabled                   Negotiation                Set by the config command
09:16:19 MESZ Aug 15 2011
Negotiation                Cold Standby               Detected an Active mate
09:16:21 MESZ Aug 15 2011
Cold Standby               Sync Config                Detected an Active mate
09:16:31 MESZ Aug 15 2011
Sync Config                Sync File System           Detected an Active mate
09:16:31 MESZ Aug 15 2011
Sync File System           Bulk Sync                  Detected an Active mate
09:16:31 MESZ Aug 15 2011
Bulk Sync                  Standby Ready              Detected an Active mate
I guess we will go the TAC way if we encounter this situation a second time. This time we will be warned and know where to look at.
Is there really no documentation available of the "HA state progression failed" message? What does it mean and how is it triggered usually?
Regards,
Grischa

RMAN in active data guard with real time apply ON without a catalog DB

I would like to know whether I can take RMAN backups (both level 0 & incremental) in active data guard with real time apply ON without a catalog database. version is 11.2.0.3.2. Will it make difference in the control file of standby syncing with primary? Can I use these backups on primary to restore and recover the database(including control file backup)?

Thank you very much msberg. Could you please answer the below queries as well?
Should I cancel Real Time Apply before starting RMAN?
Will it make difference in the control file of standby syncing with primary? Is it possible to use these backups on primary to restore and recover the database(including control file backup)? If possible, how will I do that?

Waiting for Gap Email Notification

Hi all,
11.2.0.1
Aix 6.1
Is there an email system in 11g that will notify me if our standby DB is "waiting for gap"?
What other status value are needed to be watched for?
Thanks,
zxy

Hi Mse,
We have 2 database on 1 server named PROD1, PROD2.
At PROD1, I got this:
DT        MBPS_REQ_A_DAY MIN_MBPS_REQ_AN_HOUR MAX_MBPS_REQ_AN_HOUR AVG_MBPS_REQ_AN_HOUR
15-SEP-13     28.4012215           .640219932           2.57893228           2.02865868
16-SEP-13      68.943453           .147678891           20.4264564           3.44717265
17-SEP-13     69.4071543           .639978837           28.1937717           3.47035771
18-SEP-13     54.1598321           .614150599            17.484673            2.7079916
19-SEP-13     55.7515449           .370225948           15.4680441           2.78757725
20-SEP-13     25.9854426           .135556096           17.5167623           3.71220608
6 rows selected.
At PROD2, I got this:
DT        MBPS_REQ_A_DAY MIN_MBPS_REQ_AN_HOUR MAX_MBPS_REQ_AN_HOUR AVG_MBPS_REQ_AN_HOUR
15-SEP-13     28.4012215           .640219932           2.57893228           2.02865868
16-SEP-13      68.943453           .147678891           20.4264564           3.44717265
17-SEP-13     69.4071543           .639978837           28.1937717           3.47035771
18-SEP-13     54.1598321           .614150599            17.484673            2.7079916
19-SEP-13     55.7515449           .370225948           15.4680441           2.78757725
20-SEP-13     25.9854426           .135556096           17.5167623           3.71220608
6 rows selected.
So what Mbps plan do we get from network service provider to accommodate our dataguard standby sync process?
Also can you teach me how to format the display above?
Thanks a lot,
zxy

SW-6509-FWSM failover Troubleshooting First aid

Fault Description：
（1）
active FWSM and standby FWSM inside interface Between，ping fails。
on side FWSM---active： ping 172.17.1.50 -------OK，ping 172.17.1.49------ping fails；
on side FWSM---standby： ping 172.17.1.49--------OK，ping 172.17.1.50-------ping fails；
but,active FWSM and standby FWSM outside interface between，ping OK。
on side FWSM---active：ping 172.17.1.36 、 ping 172.17.1.37、ping 172.17.1.35/33/34/、ping www.baidu.com -----------All OK；
on side FWSM---standby：ping 172.17.1.36 、 ping 172.17.1.37 、ping 172.17.1.35/33/34/、ping www.baidu.com-----------All OK；
（2）
Another problem：
active FWSM and standby FWSM inside interface，ping 7706-------All fails。
Summary：May be caused fwsm。
Topology ：Attachment
FWSM :
FWSM#                       show failover state
====My State===
Primary | Active |
====Other State===
Secondary | Standby |
====Configuration State===
    Interface config Syncing - STANDBY
    Sync Done
====Communication State===
    Mac set
=========Failed Reason==============
My Fail Reason:
    Ifc Failure
Other Fail Reason:
    Comm Failure
FWSM# show failover
Failover On
Failover unit Primary
Failover LAN Interface: lan Vlan 997 (up)
Unit Poll frequency 1 seconds, holdtime 15 seconds
Interface Poll frequency 15 seconds
Interface Policy 50%
Monitored Interfaces 42 of 250 maximum
Config sync: active
Version: Ours 4.0(13), Mate 4.0(13)
Last Failover at: 19:08:24 Beijing Dec 2 2013
    This host: Primary - Active
        Active time: 358944 (sec)
    Interface outside (172.17.1.36): Normal
    Interface inside (172.17.1.49): Normal (Not-Monitored)
    Other host: Secondary - Standby Ready
        Active time: 0 (sec)
    Interface outside (172.17.1.37): Normal
    Interface inside (172.17.1.50): Normal (Not-Monitored)
(Not-Monitored) -----------------??????

That's what I thought but the again, from the 6500 config prompt I actually get echo replys(!) from the FWCTX, with capture enabled as:
     access-list CAP permit ip any any
     capture mgmt access-list CAP interface MGMT packet-length 1500 circular-buffer
But it shows blank and no hit counts. Same happens usind RTMonitor in ASDM (6.2.(2f)) some packets that are permited and routed correctly aren't actually noticed. I don't get any logging for the missing/dropped/denied echo replies from the FWCTX to the 6500 MSFC nor for the successful replies from the 6500 to the FWCTX withh ASDM Debugging logging on.

FWSM system space does not replicate part of configuration

                   Hi
I have FWSM failover pair, Active/Active configuration, admin and another 4 context, few context active on first FWSM, other on second FWSM.
I needed to add VLANs 51 and 52 to FWSM
I created VLANs on both Cat6500, created firewall vlan-group 3 a and put "firewall module1 vlan-group 3" on both cat6500
Then I log in in system space on primary FWSM and created interface VLAN.
Created VLANs automatically occured in system space on Secondary FWSM.
Then I wanted allocate VLAN 51 and 52 to context XY, so I went to part of configuration for context XY and "allocate-interface Vlan51" and "allocate-interface Vlan52".
But this part did not replicate to system space on Secondary FWSM, i do not know why.
I tried for expample shutdown inteface101 in system space on Primary FWSM. This action was replicated.
pnfkepolsa17# sh failover state
====My State===
Primary | Active |
====Other State===
Secondary | Standby |
====Configuration State===
       Interface config Syncing - STANDBY
       Sync Done - STANDBY
====Communication State===
       Mac set
=========Failed Reason==============
My Fail Reason:
Other Fail Reason:
pnfkepolsa17#
pnfkepolsa17# sh failover state
====My State===
Secondary | Standby |
====Other State===
Primary | Active |
====Configuration State===
       Interface config Syncing - STANDBY
       Sync Done
       Sync Done - STANDBY
====Communication State===
       Mac set
=========Failed Reason==============
My Fail Reason:
Other Fail Reason:
       Comm Failure
pnfkepolsa17#
I found this message in logg of Cat6500
000160: Jun 11 20:34:22.405: %SVCLC-5-SVCLCMULTI: Group 3 being tied to more than one module
Why is this problem?
Peter

I found explanation:
Error Message    %SVCLC-5-SVCLCMULTI: Group [dec] being tied to more than one module
Explanation    The specified group is tied to multiple service modules. A group should not be associated with more than one service module unless a failover configuration is being used.
Recommended Action    If a failover configuration is in use, no action is required. Otherwise enter the show svclc module command to find out which group is being tied to more than one module. Then remove multiple associations by entering the no svclc module mod vlan-group group command.
I want to use vlan-group 3 for FWSM and for ACE module too.
which kind of failover was mentioned?
Peter

FWSM Primary delay returning to active

Hi,
We have several FWSM in 2 6500 chassis and a few days ago the primary FWSM rebooted itself for unknown reasons and the secondary FWSM took over as planned.
But the primary FWSM has, after several days, switched back over to active automatically.
Question is, does anyone know why there would be such a long delay for the primary to request active mode?

Hi,
Thanks for your reply. This is May 27 14:22:41 10.10.0.18 %FWSM-1-104002: May 27 14:22:41 10.10.0.18 %FWSM-1-104001: Here is the failover history from Not Detected Negotiation Negotiation Cold Standby Cold Standby Sync Config Sync Config Sync File System Sync File System Bulk Sync Bulk Sync Standby Ready Standby Ready Just Active Just Active Active Drain Active Drain Active Applying Config Active Applying Config Active Config Applied Active Config Applied Active Active Standby Ready Standby Ready Just Active Just Active Active Drain Active Drain Active Applying Config Active Applying Config Active Config Applied Active Config Applied Active Active Standby Ready Cheers,
- Trevor the log output when the primary decided to take over as active:-
(Secondary) Switching to STNDBY - Other unit want me Standby
(Primary) Switching to ACTIVE - Set by the CI config cmd
the standby unit. It did not reboot like the primary did a few days ago.
No Error
Detected an Active mate
Detected an Active mate
Detected an Active mate
Detected an Active mate
Detected an Active mate
Other unit want me Active
Other unit want me Active
Other unit want me Active
Other unit want me Active
Other unit want me Active
Set by the CI config cmd
HELLO not heard from mate
HELLO not heard from mate
HELLO not heard from mate
HELLO not heard from mate
HELLO not heard from mate
Other unit want me Standby

Faq .......please help me...and try to answer all the questions.will hepful

guru's
These questions are asked on various.....interviews..pls help me.
1.db in archive log mode under /ARC directory....what will happen if we remove the /arc folder by using os command ? but the archive path already there on init file and db on archive lod mode...will any error raised?? or do we need to recreate the folder to start the archive log again ?
2. Database perforamce views ?
3. how can we check the following fragmentaion needed? which view will be checked for the following ?
a. index fragmentation
b.table fragmentation
c.database level fragmentation
4. my primary db log deleted before applying in to secondary then how to get my standby synced? recreate the control file ?
5.my db totally hunged, i am unable to run any query even sysadmin too..no OS issue...no OEM facility available ..then what step should be taken ? do we need to bounce the db ?
6 how to find and check the block curruption on the DB ? and rectify it ..
7. Do we have any parameter called ORA_debug ?
8. i have two db on host1 and host2 which on same database version...is it possible to invoke my host2 database export job on host1?
9. what is difference between database on upgrade mode and migrate mode ?? what is the major steps we do for upgrade like from 10.0.2 to 10.0.4
thanks
Moorthy

Hello Azar,
i checked again and found the archivelog destination folders will be recreated on every log switch if deleted by OS command.( This will occurs when the OFA used)
If the manual archive destination used which not included in OFA architechture then the logs will be placed on the next parent directory on the specified archieve path...no directory will be created on OS level.
so the final thing is no error will be raised on DB level at any point of directory removal on OFA and normal filesystems so the archivel will be continously generated according to the suituation.
standby_archive_dest string ?/dbs/arch
alter system set log_archive_dest_1='LOCATION=/u01/app/oracle/arcv' scope=both;
SQL> alter system switch logfile;
System altered.
SQL> /
System altered.
[oracle@oracledbhost arcv]$ ls -l
total 828
-rw-r----- 1 oracle oinstall 88576 Jan 24 10:02 1_22_740096672.dbf
-rw-r----- 1 oracle oinstall 1024 Jan 24 10:02 1_23_740096672.dbf
-rw-r----- 1 oracle oinstall 5632 Jan 24 10:02 1_24_740096672.dbf
-rw-r----- 1 oracle oinstall 1536 Jan 24 10:02 1_25_740096672.dbf
-rw-r----- 1 oracle oinstall 731136 Jan 24 10:05 1_26_740096672.dbf
[oracle@oracledbhost oracle]$ rm -rf arcv/
[oracle@oracledbhost oracle]$ ls
admin oraInventory product
[oracle@oracledbhost oracle]$ ls -l
total 12
drwxr-x--- 5 oracle oinstall 4096 Jan 16 10:50 admin
drwxrwx--- 6 oracle oinstall 4096 Jan 10 22:14 oraInventory
drwxr-xr-x 3 oracle oinstall 4096 Jan 10 21:15 product
[oracle@oracledbhost oracle]$
[oracle@oracledbhost oracle]$ ls
admin arcv1_27_740096672.dbf oraInventory product
[oracle@oracledbhost oracle]$
[oracle@oracledbhost oracle]$ ls -l
total 76
drwxr-x--- 5 oracle oinstall 4096 Jan 16 10:50 admin
-rw-r----- 1 oracle oinstall 61440 Jan 24 10:07 arcv1_27_740096672.dbf
drwxrwx--- 6 oracle oinstall 4096 Jan 10 22:14 oraInventory
drwxr-xr-x 3 oracle oinstall 4096 Jan 10 21:15 product
[oracle@oracledbhost oracle]$
[oracle@oracledbhost oracle]$ pwd
/u01/app/oracle
[oracle@oracledbhost oracle]$ ls
admin arcv1_27_740096672.dbf oraInventory product
[oracle@oracledbhost oracle]$ ls -l
total 76
drwxr-x--- 5 oracle oinstall 4096 Jan 16 10:50 admin
-rw-r----- 1 oracle oinstall 61440 Jan 24 10:07 arcv1_27_740096672.dbf
drwxrwx--- 6 oracle oinstall 4096 Jan 10 22:14 oraInventory
drwxr-xr-x 3 oracle oinstall 4096 Jan 10 21:15 product
[oracle@oracledbhost oracle]$ ls
admin arcv1_27_740096672.dbf arcv1_28_740096672.dbf oraInventory product
[oracle@oracledbhost oracle]$ ls -l
total 84
drwxr-x--- 5 oracle oinstall 4096 Jan 16 10:50 admin
-rw-r----- 1 oracle oinstall 61440 Jan 24 10:07 arcv1_27_740096672.dbf
-rw-r----- 1 oracle oinstall 5632 Jan 24 10:07 arcv1_28_740096672.dbf
drwxrwx--- 6 oracle oinstall 4096 Jan 10 22:14 oraInventory
drwxr-xr-x 3 oracle oinstall 4096 Jan 10 21:15 product
Thanks
Moorthy

Standby sync

Similar Messages

Maybe you are looking for