Remove/decommission standby

Hello
I have 10G RAC database and have data guard with 2 physicals standby's in place and both standby's are non RAC
I want to decommission one of the standby's meaning the primary should not know this standby exist or try sending logs
Any steps/help are appreciated
Thanks

Assuming it has it own LOG_ARCHIVE_DEST_STATE_?
You should be able to remove or alter these at the primary site.
So set this to DEFER and change in the spfile.
I would probably create a new pfile from the spfile on the primary and review these parameters for ones that need changing or are obsolete:
DB_FILE_NAME_CONVERT
LOG_FILE_NAME_CONVERT
log_archive_dest_1
log_archive_dest_2
log_archive_dest_3
FAL_CLIENT
If you are using data broker you might want to redo the configuration too.
Fairly good thread on part of this here:
Disable Data Guard

Similar Messages

How to Remove Decommissioned CA's from PKIVIEW Locations

Hello,
I recently decommissioned two of our Enterprise Issuing Certificate Authorities from our PKI environment. I have removed the decommissioned CA http references on each of our existing CA Management Console's Extensions tabs and ensured that my CA Exchange
certs do not have the decommissioned CDP locations referenced. I have restarted all CAs, but the decommissioned servers still appear in the CDP and DeltaCRL http Locations. I've also verified they don't exist in the registry and don't exist in the NTAuthCertificates
container viewed through pkiview.msc > Enterprise PKI > Manage AD Containers.
Environment consists of Windows Server 2008 Offline Root and Policy CAs with five online Issuing CAs (which consist of two 2008 and three 2012 servers)
Any other ideas of how to get rid of the decom'd locations in pkiview.msc?
Thanks! Patrick

You need to revoke the most recent CA Exchange certificate and re-run PKIView.msc.
Vadims Podāns, aka PowerShell CryptoGuy
My weblog: en-us.sysadmins.lv
PowerShell PKI Module: pspki.codeplex.com
PowerShell Cmdlet Help Editor pscmdlethelpeditor.codeplex.com
Check out new: SSL Certificate Verifier
Check out new:
PowerShell File Checksum Integrity Verifier tool.

How to remove logical standby database configuration cleanly

Hello,
We are on RHL with 11.2.0.3 DB version. Due to various unknown reasons we would like to recreate logical standby database and for that purpose I would like to cleanly remove/uninstall/drop LOGICAL STANDBY DATABASE from the DATA GUARD configuration we have.
The DG setup already has 1 PHYSICAL STANDBY DATABASE which is working fine. PRIM,PHYSICAL, and LOGICAL all are on different HOSTS. Could you please guide or suggest us exact MOS Doc id regarding this? I have found one MOS Doc id which is close enough but its steps include removing dg configuration completely which I don't want. Only Logical Standby database needs to be remove cleanly so that it can be installed again properly.
We are using GRID CONTROL and DATA GUARD BROKER.
Bundle of thanks in advance.
Best Regards

Hello;
I would review this Oracle note:
How to remove a Data Guard Configuration from Primary Database (Doc ID 733794.1)
Best Regards
mseberg

Remove decommissioned SQL database from SCOM

Hi,
In SCOM 2007 R2, we have few SQL databases which have been decommissioned & removed but, they are still in Healthy state in SCOM.
How can I remove these entries from SCOM? I want to remove only the databases.
TIA.

Try this -
1) Log in to those SQL servers
2) Stop System center management(SCOM health) service.
3) Rename Health Service State folder located at "c:\programfiles\system center operations manager\agent\Health Service State:.
4) Restart System center management(SCOM health) service.
5) Wait for few minutes so that discoveries can run again and then check in the SCOM console. Those Databases should go away now.
Please let me know if this did not help or if this is not what you are looking for.
Thanks, S K Agrawal

Can not remove standby log file, please help

Hi,
My v$logfile
GROUP# STATUS TYPE MEMBER
IS_RECOVERY_DEST_FILE
3 ONLINE /u01/app/oracle/oradata/orcl/redo03.log
NO
2 ONLINE /u01/app/oracle/oradata/orcl/redo02.log
NO
1 ONLINE /u01/app/oracle/oradata/orcl/redo01.log
NO
GROUP# STATUS TYPE MEMBER
IS_RECOVERY_DEST_FILE
4 STANDBY /u01/app/oracle/oradata/orcl/stdlog01.log
NO
5 STANDBY /u01/app/oracle/oradata/orcl/stdlog02.log
NO
And when i clear standby log 5
SQL> alter database clear logfile group 5;
alter database clear logfile group 5
ERROR at line 1:
ORA-00600: internal error code, arguments: [2130], [0], [8], [2], [], [], [],[]
Please help me :(

I hoping you can provide more information. v$log should not return information on standby, V$STANDBY_LOG will.
Are you preforming the query on the primary or standby side?
What version of Oracle are you using?
Why do you need to remove the standby log?
You should only have to clear a logfile if it has become corrupt, what make you think this is the case?
If you can provide more details if would be very helpful.
Best Regards
mseberg
Since you have posted the exact same question in the GENERAL DATABASE section and refuse to supply version information there you really have provide more details before anybody will help you.
Remove standby redo log, get ORA-00600
Edited by: mseberg on Apr 9, 2011 5:35 AM

Remove standby redo log, get ORA-00600

Hi,
My v$logfile
GROUP# STATUS TYPE MEMBER
IS_RECOVERY_DEST_FILE
3 ONLINE /u01/app/oracle/oradata/orcl/redo03.log
NO
2 ONLINE /u01/app/oracle/oradata/orcl/redo02.log
NO
1 ONLINE /u01/app/oracle/oradata/orcl/redo01.log
NO
GROUP# STATUS TYPE MEMBER
IS_RECOVERY_DEST_FILE
4 STANDBY /u01/app/oracle/oradata/orcl/stdlog01.log
NO
5 STANDBY /u01/app/oracle/oradata/orcl/stdlog02.log
NO
And when i clear standby log 5
SQL> alter database clear logfile group 5;
alter database clear logfile group 5
ERROR at line 1:
ORA-00600: internal error code, arguments: [2130], [0], [8], [2], [], [], [],[]
Please help me :(

This is the information
SQL> select * from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
PL/SQL Release 11.1.0.6.0 - Production
CORE 11.1.0.6.0 Production
TNS for Linux: Version 11.1.0.6.0 - Production
NLSRTL Version 11.1.0.6.0 - Production
- Because the standby redo log group 5 is created with smaller size than the redo log. So, i want to remove this standby log and recreate the new one with equal or larger size of the online redo log
Chuong

Best way to drop standby database

Hi
Oracle RDBMS 11.2.0.2 on RHEL 5.6.
I need to drop standby database completeley and rebuilt physical standby for the same database. We identified there are lot of inconsistencies between primary and standby. How do i need to remove the standby? And what is the best procedure?
Thanks

951368 wrote:
Hi
Oracle RDBMS 11.2.0.2 on RHEL 5.6.
I need to drop standby database completeley and rebuilt physical standby for the same database. We identified there are lot of inconsistencies between primary and standby. How do i need to remove the standby? And what is the best procedure?
ThanksFollow this *Step By Step How to Recreate Dataguard Broker Configuration [ID 808783.1]*

Removing Dataguard

A while back we looked into some Dataguard usage on 9i. We'd like to get rid of it, but I can't find anything on removing Dataguard from my instance and removing the standby. (I assume after Dataguard is off/gone I can just shutdown the instance and remove it's files to get rid of it.)
I looked through the online docs, but nothing has been helpful.

There are severall options if you configure Dataguard Broker you can delete it using Dataguard GUI (started from Enterprise Manager Console), you can of course also do it by hand.
alter system set dg_broker_start=false scope=spfile;
delete files to which this parameter are pointing:
dg_broker_config_file1 string %ORACLE_HOME%\DATABASE\DR1%ORA
CLE_SID%.DAT
dg_broker_config_file2 string %ORACLE_HOME%\DATABASE\DR2%ORA
CLE_SID%.DAT
disable log_archive_dest_x whih was pointing to dataguard database.
restart primary database
shutdown standby database
remove datafiles (standby redo logs if in plae and standby ontrolfile) from standby database.
reconfigure listeners
drop spfile for standby database
Best Regards
Krystian Zieja / mob

ASA 5520 Upgrade From 8.2 to 9.1

To All Pro's Out There,
I have 2 x ASA 5520 in Active/Standby state (Routed, Single context) running 8.2(3) image. They are working great and everybody is happy. Now it's time for us to upgrade to the latest and greatest version: 9.1 and as you know there are some architectural changes Cisco made to NAT statements and Access Lists. As one can tell, we have a monster environment in terms of NAT statements and access list that are currently configured on the appliances.
In order to make the upgrade process "less" painful, I was able to find a loaner ASA 5520 device so I can practice the upgrade process offline and if needed, I use it in production (in conjunction with existing Primary and Secondary devices) should it be helpful. I currently don't have any plans on how to move forward with these 3 devices and put together an smooth upgrade. I am asking advice from experts that perhaps have done this in the past and know some Do's and Don’ts and can provide me some options toward getting best result: Minimum downtime and Smooth upgrade.
I appreciate all the help in advance.

Hi,
My personal approach from the start has been to learn the new NAT configuration format on the ASA CLI and manually convert the configurations for the new ASA software. I am under the impression that the automatic conversion that the ASA does by rebooting straight into a new software level causes quite a lot of configurations and they arent really optimal.
In your case it seems that you have a pretty much better situation than most people that dont have the chance to use a test device to test out the setup before actually putting it in production.
What you can basically do is
Insert the 8.2 configuration to the test ASA and boot it straight to the higher software levels and see what the conversion has done to the ASA configurations.
You can use "packet-tracer" command to test if correct NAT rules are still hit after the conversion
So far I have been lucky in the sense that most of the upgrades I have done have involved new hardware which has basically let me configure everything ready and just switch devices for the customer. So far everything has went really well and there has been only a 1-2 mistakes in NAT configurations because of misstyping some IP address or interface name which basically resulted from a lot of copy/paste when building the configurations. And these couple of mistakes have been from around 150 firewall migrations (of which most from FWSM Security Context to a ASA Security Context)
If you have time to put into this then I would suggest you try to learn the new NAT format and write your NAT configurations yourself. Converting the existing configurations should essentially give you the tools to then maintain that firewall configuration easily in the future and apply that knowledge elsewhere.
If you want to read a bit about the new NAT configuration format then I would suggest having a look at the NAT 8.3+ document I made:
https://supportforums.cisco.com/docs/DOC-31116
My personal approach when starting to convert NAT configurations for the upgrade is
Collect all NAT configurations from the current ASA including any ACLs associated with the Policy type NATs and NAT0 configurations
Divide NAT configurations based on type
Dynamic NAT/PAT
Static NAT
Static PAT
NAT0
All Policy Dynamic/Static NAT/PAT
Learn the basic configuration format for each type of NAT configuration
Start by converting the easiest NAT configurations
Dynamic NAT/PAT
Static NAT/PAT
Next convert the NAT0 configurations
And finally go through the Policy NAT/PAT configurations
Finally go through the interface ACLs and change them to use the real IP address as the destination in all cases since the NAT IP address is not used anymore. In most common screnarios this basically usually only involves modifying the "outside" interfaces ACL but depending if the customer has some other links to external resourses then its highly likely that same type of ACL changes are required on those interfaces also.
The most important thing is to understand how the NAT is currently working and then configure the new NAT configuration to match that. Again, the "packet-tracer" command is a great tool to confirm that everything is working as expected.
One very important thing to notice also is that you might have a very large number of Identity NAT configurations between your local networks interfaces of the ASA.
For example
static (inside,dmz) 10.10.10.0 10.10.10.0 netmask 255.255.255.0
In the new software you can pretty much leave all of these out. If you dont need to perform NAT between your local interfaces then you simply leave out all NAT configurations.
Naturally you can also use these forums to ask help with NAT configuration conversions. Even though its a very common topic, I dont personally mind helping out with those.
So to summarize
Try out the ASAs automatic configuration conversion when simply booting to new software levels on the test ASA you have
Learn the new NAT configuration format
Ask for help here on CSC about NAT configuration formats and help with converting old to new configurations.
Personally if I was looking at a samekind of upgrade (which I will probably be looking at again soon) I would personally do the following
Convert the configurations manually
Lab/test the configurations on an test ASA
During Failover pairs upgrade I would remove the Standby device from network, erase its configurations, reboot it to new software, insert manually written configurations.
Put the upgraded ASA to the device rack and have cables ready connected to the customer devices if possible (or use existing ones)
Disconnect currently active ASA running 8.2 and connect the new ASA to the network while clearing ARP on the connected routers to avoid any problems with traffic forwarding.
Test connectivity and monitor ASAs connection and xlate tables to confirm everything is working
Will add more later if anything comes to mind as its getting quite late here
Hope this helps
- Jouni

I am looking for a way to efficiently move from HSRP to GLBP.

I want to move from using HSRP to GLBP and encountering issues with making it a smooth transition. I am testing my plans using GNS3
Our two external production routers are configured to use HSRP and the current traffic demands are taking a toll on the primary router. The primary HSRP router's CPU is running above 70% while the standby router is hovering in the 20's. The main reason is the firewalls are running High Availability Load Sharing (Sidewinders) so each firewall is able to transmit / receive data. Our routers are setup in a BGP multihome configuration with the ISP. The upstream routers are associated with the same AS. Each side has maximum-path 2 enabled within the BGP process. The two firewalls associate a multicast mac address with a vIP. Each router has a static arp entry for the firewall vIP multicast address allowing them to send traffic they receive from the world to the firewall pair. The firewalls then decide if they will accept the traffic or defer to the other. Unfortunately I cannot upgrade the NPE's on the external routers (NPE-400) so the next best thing is to try and distribute the load coming from the two firewalls. I hope to get both routers running in the mid 50’s which aren’t great but it's better than the current situation. I've been told money is coming but you know how that goes.
Here is my glbp scheme I want to implement
R1 (This will be my AVG)
track 20 interface g2/0 line-protocol (Gi2/0 is the external interface)
interface gi0/0 (Serves as the gateway interface for the Firewalls)
glbp 10 ip 10.1.1.1 (fictitious address)
glbp 10 timers 5 15
glbp 10 weighting 100 lower 90 upper 95
glbp 10 load-balancing host-dependent
glbp 10 authentication md5 key-string #######
glbp 10 weighting track 20 decrement 20
glbp 10 forwarder preempt delay minimum 5
R2
track 20 interface g2/0 line-protocol (Gi2/0 is the external interface)
interface gi0/0 (Serves as the gateway interface for the Firewalls)
glbp 10 ip 10.1.1.1 (fictitious address)
glbp 10 timers 5 15
glbp 10 priority 95 (the interface physical ip address on this router is greater than the one on R1)
glbp 10 weighting 100 lower 90 upper 95
glbp 10 load-balancing host-dependent
glbp 10 authentication md5 key-string #######
glbp 10 weighting track 20 decrement 20
glbp 10 forwarder preempt delay minimum 5
Initially I thought this would be simple to transition from HSRP to GLBP. I would remove the standby ip ip-address command from the interface and replace it with the glbp ip ip-address command. The interface would already be configured with the other glbp commands prior to making the change. I thought this method would also aid in the event I had to roll back to HSRP due to something I didn't account for in testing.
When I attempt to execute the above command sequence, the router reports the virtual IP address is being used by another application on the interface. I tried shutting down the interface and rerun the sequence with no success. To get around this obstacle, I remove all standby commands from the interface by entering either no standby 1 or no standby.
So here is what I am thinking. On the day of moving from HSRP to GLBP, I will have a console connection to both routers.
On R2
shutdown interface g0/0 since this router is designated as the HSRP standby router and paste the following commands into the router
track 20 interface g2/0 line-protocol
interface gi0/0
no standby 1
glbp 10 ip ip-address
glbp 10 timers 5 15
glbp 10 priority 95
glbp 10 weighting 100 lower 90 upper 95
glbp 10 load-balancing host-dependent
glbp 10 authentication md5 key-string #######
glbp 10 weighting track 20 decrement 20
glbp 10 forwarder preempt delay minimum 5
While this is occurring, on router #1 which is the primary hsrp router, paste the following commands in
track 20 interface GigabitEthernet2/0 line-protocol
interface GigabitEthernet0/0
no standby 1
glbp 10 ip ip-adddress
glbp 10 timers 5 15
glbp 10 weighting 100 lower 90 upper 95
glbp 10 load-balancing host-dependent
glbp 10 authentication md5 key-string ######
glbp 10 weighting track 20 decrement 20
glbp 10 forwarder preempt delay minimum 5
Once the commands are pasted into Router #1, enable the interface on Router #2 and monitor GLBP with the following debug commands enabled on both routers.
debug glbp events
debug glbp errors
My test runs using GNS seem to run well. I know I am going to interrupt traffic and I scheduled network downtime to perform the change. I am anticipating total downtime to be less than 5 minutes.
Does this approach sound logical or is there a better method to transition from HSRP to GLBP?
thanks in advanced.

p.lagatta wrote:Jon, Thanks for the reply. The Siderwinder Firewalls associate a Multicast MAC address with the vIP. That's the reason for the static ARP entry in each router. Since our Layer II switches located between the firewalls and routers do not register the MAC with a specific port, both firewalls receive the traffic. Once the traffic reaches the firewalls, they pass information across a heartbeat interface and the selection process is based on odd / even ports. Receive traffic is already working in this configuration. Both our external routers are peered with two EBGP routers located in the same AS. The GLBP implementation will allow us to load balance the traffic each firewall is sending to the GW address.
Perhaps i'm misunderstaning.
If there is one mac-address then GLBP will assign that mac-address to one of the routers and it will keep that router for forwarding the traffic with the same mac-address. So the traffic will always be forwarded by the same router. GLBP works by assigning different source mac-addresses to different routers within the same group but it sounds like the source mac-address is always the same from the firewalls.
Jon

Problem in opening of database

hi everybody
can anyone solve this
during opening of the database the error is
ora 03113 end of file comminication channel
when i check the alert log file
the expressions are in alter file :-
Database mount in Exclusive mode
complete : alter database mount
LGWR:Primary database is in CLUSTER CONSISTENT MODE
LGWR:Primary database is in MAXIMUM PROTECTION MODE
LGWR:Destination LOG_ARCHIVE_DEST_2 IS NOT SERVIVED BY LGWR
LGWR:Destination LOG_ARCHIVE_DEST_1 IS NOT SERVICED BY LGWR
Error in file /u01/oracle/bdump/k_lgwr_2703.trc:
ora -16072: Minimun of the one standby database destination is required
LGWR Terminiating instane due to error
and in trace file same error defination is ;-
LGWR:Primary database is in CLUSTER CONSISTENT MODE
LGWR:Primary database is in MAXIMUM PROTECTION MODE
LGWR:Destination LOG_ARCHIVE_DEST_2 IS NOT SERVIVED BY LGWR
LGWR:Destination LOG_ARCHIVE_DEST_1 IS NOT SERVICED BY LGWR
so i don't know what is this ,So give ur ideas to resolve this situation
thanks

Have you removed the standby database???
If yes, check whether the Primary Database has still the Protection Mode stored in the Data Dictionary. The Protection Mode requires a running connection to a Standby Database with LGWR SYNC as Log-Transportation Mode. As per metalink:--
>
Fix
~~~~
Startup the Primary Database in Mount State and set the Protection Mode back
to Maximum Performance Mode, which is the Default:
SQL> ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE;
Then shutdown the Database and restart again.
>
Check metalink Doc ID: Note:245731.1
Anand

Best practise to change new SUP on 6509

Best practise to change new SUP on 6509, currently we have dual sup. is it we need to power down the switch and install ne sup?

Hi,
Below are few methods which you can choose:
It really depends on which Sup you want to replace ( I mean the one which is currently Active or the Standby sup).
Lets go step by step:
1st-- Think you want to replace the Standby Sup in the working chasis:
Answer: You need not have to worry, just remove the Standby Sup and install the new sup , Make sure the standby sup is running the same software version which Active has.
2nd- Replacing the Active Sup:
Answer: To avoid any distruption, failover to the Standby Sup so that the STandby Sup takes over the active role and then proceed with replacing the Active Sup.
Few reference which might help you:
https://supportforums.cisco.com/discussion/11640021/replace-failed-sup-6500-sup32
http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-virtual-switching-system-1440/109334-replace-vss-sup-proc-v1.html
HTH

Clean way to De-register/De-commission the database with EBS from RAC/Cluster.

Hi,
We have a database with EBS on RAC. We are looking for Clean way to decommissioning the database from the cluster. We tried earlier, but when we again installed a fresh database on that server some how we had issues with the user oracle in cluster configuration files.
Early response is highly appreciated.
Thanks,
Rajashekar

Hi Hussein,
We have two node db and two node application server in a cluster environment.
We want to Remove/Decommission JUST DATABASE, APPLICATION related all files from the cluster. Cluster files should not be effected. After removing them we want install a fresh Db and Application on the same cluster.
Looking for any standard method for decommissioning.
Thanks,
Rajashekar

How do you separate the Servers for UCCX?

Hello, We are current on version 8.0.2 uccx servers. We are planning to separate the servers. We will keep one at our location and the other one will be in another location. Can someone tell me where I can find the procedures needed to do this? Will I also need to change anything in CUCM. Any documentation would be appreciated.
Thanks for your help

Once you remove the Standby (Second) server from the cluster, it will just be a server with software on it. You then need to redo the post install configuration and add it back to the cluster, but this time choose the HAoWAN.
The Master(First) server is all the brains in the cluster. The Standby is just a copy of the Master, in a matter of speaking.
To learn more about how they communicate, you can look at the SRND for CCX 8.0, but there is a lot of network and system level speak about it.
I would suggest opening a TAC case and having them walk you thru it.

CSCty46471 - Duplicate VIP Messages when ARP Probe for VIP received on GLBP Vlan

I have experienced this issue in NXOS 6.0(4) 7009
I resolved this issue by removing the standby IP in GLBP on the standby Core
I then readded the standby IP and no longer saw the error relating to that Vlan in the log

Hi Daniel,
Still no joy, I can ping the VIP, I can telnet to the servers on port 8081 direct. I see the VIP taking traffic and it says it is forwarding out to a server i.e in the counters however I never see the packet arrive at the server???
Strangely when I do;
sh mod csm conn vserver GAS_8081
   prot vlan source                destination           state
In TCP 895 172.30.60.41:34805    172.30.60.41:8081     ESTAB
Out TCP 895 172.30.60.41:8081     172.30.60.41:34806    ESTAB
In TCP 895 172.30.60.41:34761    172.30.60.41:8081     ESTAB
Out TCP 895 172.30.60.41:8081     172.30.60.41:34762    ESTAB
In TCP 895 172.30.60.41:34822    172.30.60.41:8081     ESTAB
Out TCP 895 172.30.60.41:8081     172.30.60.41:34823    ESTAB
I get the above, i.e I dont see the packet going to the actual servers??
However i get the following while trying to connect;
trposr02#sh mod contentSwitchingModule 13 vservers name GAS_8081 det
GAS_8081, type = SLB, state = OPERATIONAL, v_index = 45
virtual = 172.30.60.41/32:0 bidir, any, service = NONE, advertise = FALSE
idle = 3600, replicate csrp = none, vlan = 895, pending = 30, layer 4
max parse len = 2000, persist rebalance = TRUE
ssl sticky offset = 0, length = 32
conns = 2, total conns = 83991
Default policy:
    server farm = GAS_8081, backup =
    sticky: timer = 0, subnet = 0.0.0.0, group id = 0
Policy          Tot matches Client pkts Server pkts
(default)       82409        179422       20
Any ideas??
Scott

Remove/decommission standby

Similar Messages

Maybe you are looking for