Delete standby database fails
Hello,
I setup replication on database A in server A to Server B and on the same database A i have logshipping setup as well to Server C. Now I removed logshipping
configuration on database A in server A and trying to delete the mirrored copy of database A in server C and it wont let me. It throws the below error:
Cannot drop the database 'DatabaseA' because it is being used for replication.
I tried to detach it and it wont let me. I took the database offline and tried to delete it and it wont. I stopped the sqlserver service and deleted the ldf and mdf manually and after starting it back I still
see it.
Is there a work around?
Thanks
Remove subscription at the publisher, Run the below script to remove the subscription at the publisher database.
Change the parameter as per your requirement
DECLARE @publication AS sysname;
DECLARE @subscriber AS sysname;
SET @publication = N'AdvWorksProductTran';
SET @subscriber = $(SubServer);
USE [AdventureWorks2008R2;]
EXEC sp_dropsubscription
@publication = @publication,
@article = N'all',
@subscriber = @subscriber;
GO
http://technet.microsoft.com/en-us/library/ms146944(v=sql.105).aspx
--Prashanth
Similar Messages
-
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 -
Data Guard Broker connecting to standby database fails
Hello everybody
I checked lots of pages but I'm not able to find a solution für my problem. I already set up a primary and a standby database (prim = ALPHA1 / standby = ALPHA2).
After enabling my dgmgrl configuration I got two errors:
DGM-17016: failed to retrieve status for database "alpha2"
ORA-16664: unable to receive the result from a database
The dg log from ALPHA1 says:
06/04/2013 16:06:57
Site alpha2 returned ORA-16664.
Data Guard Broker Status Summary:
Type Name Severity Status
Configuration alphadgb Warning ORA-16607
Primary Database alpha1 Success ORA-00000
Physical Standby Database alpha2 Error ORA-16664
While the dg log from ALPHA2 (standby) says:
06/04/2013 16:43:28
SPFILE is missing value for property 'LogArchiveFormat' with sid='ALPHA2'
Warning: Property 'LogArchiveFormat' has inconsistent values:METADATA='arch_ALPHA2_%S_%t_%r.arc', SPFILE='(missing)', DATABASE='arch_ALPHA2_%S_%t_%r.arc'
Failed to connect to remote database alpha1. Error is ORA-12514
Failed to send message to site alpha1. Error code is ORA-12514.
How can I solve this issue? Every type of tnsping is successfull. The sqlplus login from the primary to the standby database works, the other way round works too! Therefore the tnsnames and listener data seems to be correct.
My configuration for ALPHA1 (primary db):
Listener
LISTENER_ALPHA1 =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.12.3.13)(PORT = 1521))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
SID_LIST_LISTENER_ALPHA1 =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = ALPHA1_DGMGRL)
(ORACLE_HOME = /oracle/ALPHA1/orahome)
(SID_NAME = ALPHA1)
tnsnames.ora
ALPHA1.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.12.3.13)(PORT = 1521))
(CONNECT_DATA =
(SID = ALPHA1)
ALPHA2.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.12.3.13)(PORT = 1522))
(CONNECT_DATA =
(SID = ALPHA2)
DG_ALPHA1.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.12.3.13)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = ALPHA1_DGMGRL)
DG_ALPHA2.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.12.3.13)(PORT = 1522))
(CONNECT_DATA =
(SERVICE_NAME = ALPHA2_DGMGRL)
Parameters
archive_lag_target integer 0
log_archive_config string DG_CONFIG=(ALPHA2,ALPHA1)
log_archive_dest string
log_archive_dest_1 string LOCATION=USE_DB_RECOVERY_FILE_DEST valid_for=(all_logfiles,all_roles) DB_UNIQUE_NAME=ALPHA2
log_archive_dest_2 string SERVICE=ALPHA1 SYNC valid_for=(online_logfiles,primary_role) DB_UNIQUE_NAME=ALPHA1
log_archive_format string arch_ALPHA2_%S_%t_%r.arc
log_archive_local_first boolean TRUE
log_archive_max_processes integer 4
log_archive_min_succeed_dest integer 1
log_archive_start boolean FALSE
log_archive_trace integer 0
standby_archive_dest string ?/dbs/arch
For the DG Broker configuration
DGMGRL> connect sys/dgalpha42@DG_ALPHA1
DGMGRL> create configuration ALPHADGB
DGMGRL> primary database is ALPHA1
DGMGRL> connect identifier is DG_ALPHA1
DGMGRL> ;
DGMGRL> add database ALPHA2
DGMGRL> connect identifier is DG_ALPHA2
DGMGRL> maintained as physical
DGMGRL> ;
There were no errors.
DGMGRL> show database verbose ALPHA1
Database - alpha1
Role: PRIMARY
Intended State: TRANSPORT-ON
Instance(s):
ALPHA1
Properties:
DGConnectIdentifier = 'dg_alpha1'
ObserverConnectIdentifier = ''
LogXptMode = 'ASYNC'
DelayMins = '0'
Binding = 'optional'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '30'
RedoCompression = 'DISABLE'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '4'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = 'ALPHA2, ALPHA1'
LogFileNameConvert = 'ALPHA2, ALPHA1'
FastStartFailoverTarget = ''
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
SidName = 'ALPHA1'
StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oraprakt)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=ALPHA1_DGMGRL)(INSTANCE_NAME=ALPHA1)(SERVER=DEDICATED)))'
StandbyArchiveLocation = 'USE_DB_RECOVERY_FILE_DEST'
AlternateLocation = ''
LogArchiveTrace = '0'
LogArchiveFormat = 'arch_ALPHA1_%S_%t_%r.arc'
TopWaitEvents = '(monitor)'
Database Status:
SUCCESS
DGMGRL> show database verbose ALPHA2
Database - alpha2
Role: PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag: (unknown)
Apply Lag: (unknown)
Real Time Query: OFF
Instance(s):
ALPHA2
Properties:
DGConnectIdentifier = 'dg_alpha2'
ObserverConnectIdentifier = ''
LogXptMode = 'SYNC'
DelayMins = '0'
Binding = 'OPTIONAL'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '30'
RedoCompression = 'DISABLE'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '4'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = 'ALPHA1, ALPHA2'
LogFileNameConvert = 'ALPHA1, ALPHA2'
FastStartFailoverTarget = ''
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
SidName = 'ALPHA2'
StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oraprakt)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=ALPHA2_DGMGRL)(INSTANCE_NAME=ALPHA2)(SERVER=DEDICATED)))'
StandbyArchiveLocation = 'USE_DB_RECOVERY_FILE_DEST'
AlternateLocation = ''
LogArchiveTrace = '0'
LogArchiveFormat = 'arch_ALPHA2_%S_%t_%r.arc'
TopWaitEvents = '(monitor)'
Database Status:
DGM-17016: failed to retrieve status for database "alpha2"
ORA-16664: unable to receive the result from a database
Can anybody help me to find a solution for this?Hey
thanks for the answer. I followed you recommendations but I got the same error again. I restored/recovered the old status and looked deeper into the dgmgrl configuration before enabling. I found an interesting point. (show database verbose ALPHAx)
Database - alpha1
Role: PRIMARY
Intended State: OFFLINE
Instance(s):
ALPHA1
Properties:
DGConnectIdentifier = 'dg_alpha1'
ObserverConnectIdentifier = ''
LogXptMode = 'ASYNC'
DelayMins = '0'
Binding = 'optional'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '30'
RedoCompression = 'DISABLE'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '4'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = 'ALPHA2, ALPHA1'
LogFileNameConvert = 'ALPHA2, ALPHA1'
FastStartFailoverTarget = ''
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
SidName = 'ALPHA1'
StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oraprakt)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=ALPHA1_DGMGRL)(INSTANCE_NAME=ALPHA1)(SERVER=DEDICATED)))'
StandbyArchiveLocation = 'USE_DB_RECOVERY_FILE_DEST'
AlternateLocation = ''
LogArchiveTrace = '0'
LogArchiveFormat = 'arch_ALPHA1_%S_%t_%r.arc'
TopWaitEvents = '(monitor)'
Database Status:
DISABLED
Database - alpha2
Role: PHYSICAL STANDBY
Intended State: OFFLINE
Transport Lag: (unknown)
Apply Lag: (unknown)
Real Time Query: OFF
Instance(s):
ALPHA2
Properties:
DGConnectIdentifier = 'dg_alpha2'
ObserverConnectIdentifier = ''
LogXptMode = 'ASYNC'
DelayMins = '0'
Binding = 'OPTIONAL'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '30'
RedoCompression = 'DISABLE'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '4'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = 'ALPHA1, ALPHA2'
LogFileNameConvert = 'ALPHA1, ALPHA2'
FastStartFailoverTarget = ''
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
SidName = 'ALPHA2'
StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oraprakt)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=ALPHA2_DGMGRL)(INSTANCE_NAME=ALPHA2)(SERVER=DEDICATED)))'
StandbyArchiveLocation = 'USE_DB_RECOVERY_FILE_DEST'
AlternateLocation = ''
LogArchiveTrace = '0'
LogArchiveFormat = 'arch_ALPHA2_%S_%t_%r.arc'
TopWaitEvents = '(monitor)'
Database Status:
DISABLED
As the listener are configured ALPHA1 (prim) should be on port 1521 while ALPHA2 (stby) should work on 1522. In the configuration of DGMGRL only appears port 1521 (look at StaticConnectIdentifier). Is this maybe the reason of the networking problems with DG Broker? How can I fix this?
Regards Mirko
Edited by: 1009733 on 04.06.2013 09:22 -
Standby Database fails to read dictionary from redo log
hi,
I am attempting to create a Logical standby database on same machine as the primary database. I have executed the steps outlined in Oracle Documentation several times, but end up with the same error. Detailes of setup and error are provided below. Please help. Thanks.
==========
OS: REdhat 8 (2.4.18-14)
RDBMS: Oracle EE Server 9.2.0.3.0
primary db init details:
*.log_archive_dest_1='LOCATION=/usr3/oracle/admin/lbsp/archive/ MANDATORY'
*.log_archive_dest_2='SERVICE=STDBY'
standby db init details:
log_archive_dest_1='LOCATION=/usr3/oracle/admin/stdby/archive/'
standby_archive_dest='/usr3/oracle/admin/lbsp/archive_pdb/'
Standby alert log file (tail)
LOGSTDBY event: ORA-01332: internal Logminer Dictionary error
Sun Jul 13 11:37:20 2003
Errors in file /usr3/oracle/admin/stdby/bdump/stdby_lsp0_13691.trc:
ORA-01332: internal Logminer Dictionary error
LSP process trace file:
Instance name: stdby
Redo thread mounted by this instance: 1
Oracle process number: 18
Unix process pid: 13691, image: oracle@prabhu (LSP0)
*** 2003-07-13 11:37:19.972
*** SESSION ID:(12.165) 2003-07-13 11:37:19.970
<krvrd.c:krvrdfdm>: DDL or Dict mine error exit. 384<krvrd.c:krvrdids>: Failed to mine dictionary. flgs 180
knahcapplymain: encountered error=1332
*** 2003-07-13 11:37:20.217
ksedmp: internal or fatal error
. (memory dump)
KNACDMP: Unassigned txns = { }
KNACDMP: *******************************************************
error 1332 detected in background process
OPIRIP: Uncaught error 447. Error stack:
ORA-00447: fatal error in background process
ORA-01332: internal Logminer Dictionary error
another trace file created by error is: stdby_p001_13695.trc
Instance name: stdby
Redo thread mounted by this instance: 1
Oracle process number: 20
Unix process pid: 13695, image: oracle@prabhu (P001)
*** 2003-07-13 11:37:19.961
*** SESSION ID:(22.8) 2003-07-13 11:37:19.908
krvxmrs: Leaving by exception: 604
ORA-00604: error occurred at recursive SQL level 1
ORA-01031: insufficient privileges
ORA-06512: at "SYS.LOGMNR_KRVRDREPDICT3", line 68
ORA-06512: at line 1
there are no errors anywhere during the creation, mounting or opening of standby database. After the initial log register, any log switch on primary is communicated to standby and visible in DBA_LOGSTDBY_LOG. Also, archived logs from primary are successfuly copied by system to directory pointed by standby db's standby_archive_dest parameter.
I noticed, somehow everytime I issue "ALTER DATABASE START LOGICAL STANDBY APPLY" command the procedures and packages related to logmnr get invalid. I compile them and again after "APPLY" they become invalid.
Invalid object list:
OBJECT_TYPE OBJECT_NAME
VIEW DBA_LOGSTDBY_PROGRESS
PACKAGE BODY DBMS_INTERNAL_LOGSTDBY
PACKAGE BODY DBMS_STREAMS_ADM_UTL
VIEW LOGMNR_DICT
PACKAGE BODY LOGMNR_DICT_CACHE
PROCEDURE LOGMNR_GTLO3
PROCEDURE LOGMNR_KRVRDA_TEST_APPLY
Anybody point out what I am doing wrong. Thanks for the helpORA-15001: diskgroup "ORAREDO3" does not exist or is not mounted
ORA-15001: diskgroup "ORAREDO3" does not exist or is not mountedhave you mentioned parameter LOG_FILE_NAME_CONVERT in standby when online redo log locations are different?
post from standby:-
SQL> select name, state From v$asm_diskgroup;
FAL[client, MRP0]: Error 1031 connecting to MKS01P_PRD for fetching gap sequence
ORA-01031: insufficient privilegesPost from primary & standby
SQL> select * from v$pwfile_users;
User Profile for 919131
919131
Handle: 919131
Status Level: Newbie
Registered: Mar 6, 2012
Total Posts: 16
Total Questions: 8 (8 unresolved)
OTN failed 100% to help you, then why you posted another question?
First close all your old answered threads and then better continue your updates in your thread.
Edited by: CKPT on Jul 9, 2012 11:45 AM -
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,
MartinI'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 -
Delete standby redo log from primary database
Hi all,
I'm trying to drop standby logfiles on primary database (other database that I'm configuring the DG).
The members of the standby log groups don't exists on file system.
Somebody have deleted these files. Its old configuration where the files were in file system. Now they are in ASM.
When I try to drop the standby logfiles I got the following error:
SQL> alter database clear logfile group 7;
alter database clear logfile group 7
ERROR at line 1:
ORA-19528: redo logs being cleared may need access to files
SQL> select * from v$logfile order by 1;
GROUP# STATUS TYPE MEMBER IS_
1 ONLINE +REDO1/proj/onlinelog/group_1.256.340558657 NO
1 ONLINE +REDO2/proj/onlinelog/group_1.256.340558659 NO
2 ONLINE +REDO1/proj/onlinelog/group_2.257.340558879 NO
2 ONLINE +REDO2/proj/onlinelog/group_2.259.340558879 NO
3 ONLINE +REDO1/proj/onlinelog/group_3.258.340558707 NO
3 ONLINE +REDO2/proj/onlinelog/group_3.257.340558709 NO
4 ONLINE +REDO2/proj/onlinelog/group_4.258.340558713 NO
4 ONLINE +REDO1/proj/onlinelog/group_4.259.340558711 NO
5 ONLINE +REDO2/proj/onlinelog/group_5.260.340558965 NO
5 ONLINE +REDO1/proj/onlinelog/group_5.260.340558963 NO
6 ONLINE +REDO1/proj/onlinelog/group_6.261.340558967 NO
6 ONLINE +REDO2/proj/onlinelog/group_6.261.340558967 NO
7 STANDBY /oracle/proj/onlinelog2/redo_702.log NO
7 STANDBY /oracle/proj/onlinelog1/redo_701.log NO
8 STANDBY /oracle/proj/onlinelog2/redo_802.log NO
8 STANDBY /oracle/proj/onlinelog1/redo_801.log NO
9 STANDBY /oracle/proj/onlinelog2/redo_902.log NO
9 STANDBY /oracle/proj/onlinelog1/redo_901.log NO
10 STANDBY /oracle/proj/onlinelog1/redo_1001.log NO
10 STANDBY /oracle/proj/onlinelog2/redo_1002.log NO
20 rows selected.
SQL> select * from v$standby_log order by 1;
GROUP# DBID THREAD# SEQUENCE# BYTES USED ARC STATUS FIRST_CHANGE# FIRST_TIM LAST_CHANGE# LAST_TIME
7 UNASSIGNED 0 0 104854601 512 YES UNASSIGNED 0 0
8 UNASSIGNED 0 0 104854601 512 YES UNASSIGNED 0 0
9 UNASSIGNED 0 0 104854601 512 YES UNASSIGNED 0 0
10 UNASSIGNED 0 0 104854601 512 YES UNASSIGNED 0 0What can I do to drop these reference?
Any other solution instead of edit the controlfile and stop/start tghe database?
thank you!!!!Hello;
Well Oracle thinks the files are there, but I remember a bug on metalink where the controlfile still had them, but they were not on the file system. Can you confirm they exist?
Meanwhile I check my notes for the Oracle doc nunber.
Bug 6128242: TRYING TO DROP STANDBY LOG FAILS WITH ORA-19528
So if you are Oracle 10 this might be the issue.
workaround is to re-create the controlfile without the incorrect logfile. ( Yuk!! )
ORA-01156 When Adding Or Dropping Redo Logs [ID 452152.1]
Best Regards
mseberg
Edited by: mseberg on Oct 31, 2011 5:09 PM -
How to delete archivelog file at standby database
Hi All,
I'm running Physical Standby Database on ASM. At standby database, I can see all logs using asmcmd:
ASMCMD> ls
thread_1_seq_14.330.625772527
thread_1_seq_15.346.625772527
thread_1_seq_16.329.625772527
thread_1_seq_17.327.625772559
thread_1_seq_18.324.625772599
thread_1_seq_19.341.625772367
thread_1_seq_2.325.625772329
But when I run RMAN to delete all these archivelogs, its give me error:
oradr:/u01/app/oracle$rman rcvcat rman/rman@rman target /
Recovery Manager: Release 10.2.0.3.0 - Production on Thu Jun 28 13:50:41 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: AIXDB (DBID=2438430915, not open)
connected to recovery catalog database
RMAN> delete archivelog all;
Starting implicit crosscheck backup at 28-JUN-07:01:50:56
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 06/28/2007 13:50:56
RMAN-12010: automatic channel allocation initialization failed
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20001: target database not found in recovery catalog
RMAN> register database;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of register command at 06/28/2007 13:51:06
RMAN-08040: full resync skipped, control file is not current or backup
Even it is not registering it. So how to delete archivelog file at standby database.
Thanks in Advance
RakeshThis appears related to Bug 3298797 that was supposed to be fixed in 10.2.0.1. The workaround is to switch over to the standby, register the standby and then switch back.
-
Failed to clone DB from StandBy database
Hello,
I need to perform a clone of Data Guard physical standby database (production) to use in preproduction. we have a full RMAN backup of standby database.
My restore is failed, i use this steps:
* full RMAN backup of standby database
* backup control file of primary
* on a new database server, copy backup
* RMAN > restore control file (of brimary)
* RMAN > CATALOG START WITH ' Path of backup'
* crosscheck backup
* restore database
-> the restore is failed with errors messages :
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
I retry restore database after restoring a standby control file, it's failed with the same message.
can you help me ,please, to resolve this issue
Regards
DjThank's AbuFazalMdAbbas for your reply,
RMAN > list backup : i display only 3 Piece Name
BS Key Type LV Size Device Type Elapsed Time Completion Time
18364 Incr 1 36.56M DISK 00:22:11 29-JUL-13
BP Key: 18364 Status: AVAILABLE Compressed: YES Tag: DIGI_SEC_DB1_DAT
Piece Name: /mnt/backup/RMAN/SEC_DB1/files/rman_SEC_DB1_29_01_0fofu8j3_1_1
List of Datafiles in backup set 18364
File LV Type Ckp SCN Ckp Time Name
17 1 Incr 22020167729 29-JUL-13 +DATA/DB1/datafile/indx_fusion54_purge.277.753031091
25 1 Incr 22020167729 29-JUL-13 +DATA/SEC_DB1/datafile/data_cmsco.284.762608775
44 1 Incr 22020167729 29-JUL-13 +DATA/SEC_DB1/datafile/indx_cmsco.303.799865601
64 1 Incr 22020167729 29-JUL-13 +DATA/SEC_DB1/datafile/indx_cmsco.324.809446025
BS Key Type LV Size Device Type Elapsed Time Completion Time
18365 Incr 1 11.17M DISK 00:22:12 29-JUL-13
BP Key: 18365 Status: AVAILABLE Compressed: YES Tag: DIGI_SEC_DB1_DAT
Piece Name: /mnt/backup/RMAN/SEC_DB1/files/rman_SEC_DB1_29_01_0gofu8j3_1_1
List of Datafiles in backup set 18365
File LV Type Ckp SCN Ckp Time Name
18 1 Incr 22020167729 29-JUL-13 +DATA/DB1/datafile/indx_fusion54_purge.279.753031091
26 1 Incr 22020167729 29-JUL-13 +DATA/SEC_DB1/datafile/data_cmsco.285.762622281
45 1 Incr 22020167729 29-JUL-13 +DATA/SEC_DB1/datafile/data_cmsco.304.800028323
65 1 Incr 22020167729 29-JUL-13 +DATA/SEC_DB1/datafile/data_cmsco.325.814713695
BS Key Type LV Size Device Type Elapsed Time Completion Time
18366 Incr 1 49.25M DISK 00:11:54 29-JUL-13
BP Key: 18366 Status: AVAILABLE Compressed: YES Tag: DIGI_SEC_DB1_DAT
Piece Name: /mnt/backup/RMAN/SEC_DB1/files/rman_SEC_DB1_29_01_0hofu9sq_1_1
List of Datafiles in backup set 18366
File LV Type Ckp SCN Ckp Time Name
4 1 Incr 22021555818 29-JUL-13 +DATA/DB1/datafile/users.281.753031093
27 1 Incr 22021555818 29-JUL-13 +DATA/SEC_DB1/datafile/indx_cmsco.286.763655749
47 1 Incr 22021555818 29-JUL-13 +DATA/SEC_DB1/datafile/indx_cmsco.306.800463801
66 1 Incr 22021555818 29-JUL-13 +DATA/SEC_DB1/datafile/data_cmsco.326.817754983
# cd <location where backup files were copied>
# ls -lrt
ALL files (piece name in list backup) exist on file System, and it's owner by oracle
# show all
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name RSP are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '+RECO/ctrl_%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/db/dbs/snapcf_MNTRSP.f'; # default -
How to delete the foreign archivelogs in a Logical Standby database
How do I remove the foreign archive logs that are being sent to my logical standby database. I have files in the FRA of ASM going back weeks ago. I thought RMAN would delete them.
I am doing hot backups of the databases to FRA for both databases. Using ASM, FRA, in a Data Guard environment.
I am not backing up anything to tape yet.
The ASM FRA foreign_archivelog directory on the logical standby FRA keeps growing and nothing is get deleted when
I run the following command every day.
delete expired backup;
delete noprompt force obsolete;
Primary database RMAN settings (Not all of them)
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 9 DAYS;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE DB_UNIQUE_NAME 'WMRTPRD' CONNECT IDENTIFIER 'WMRTPRD_CWY';
CONFIGURE DB_UNIQUE_NAME 'WMRTPRD2' CONNECT IDENTIFIER 'WMRTPRD2_CWY';
CONFIGURE DB_UNIQUE_NAME 'WMRTPRD3' CONNECT IDENTIFIER 'WMRTPRD3_DG';
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
Logical standby database RMAN setting (not all of them)
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 9 DAYS;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
How do I cleanup/delete the old ASM foreign_archivelog files?OK, the default is TRUE which is what it is now
from DBA_LOGSTDBY_PARAMETERS
LOG_AUTO_DELETE TRUE SYSTEM YES
I am not talking about deleting the Archive logs files for the Logical database that it is creating, but the Standby archive log files being sent to the Logical Database after they have been applied.
They are in the alert log as follows under RFS LogMiner: Registered logfile
RFS[1]: Selected log 4 for thread 1 sequence 159 dbid -86802306 branch 763744382
Thu Jan 12 15:44:57 2012
*RFS LogMiner: Registered logfile [+FRA/wmrtprd2/foreign_archivelog/wmrtprd/2012_01_12/thread_1_seq_158.322.772386297] to LogM*
iner session id [1]
Thu Jan 12 15:44:58 2012
LOGMINER: Alternate logfile found. Transition to mining archived logfile for session 1 thread 1 sequence 158, +FRA/wmrtprd2/
foreign_archivelog/wmrtprd/2012_01_12/thread_1_seq_158.322.772386297
LOGMINER: End mining logfile for session 1 thread 1 sequence 158, +FRA/wmrtprd2/foreign_archivelog/wmrtprd/2012_01_12/threa
d_1_seq_158.322.772386297
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 159, +DG1/wmrtprd2/onlinelog/group_4.284.771760923 -
How to delete archivelog with RMAN in the Primary and Standby database?
Hello,
I am working on Oracle 10gR2.
My question is :
How could I implement a automatized and secure way of:
1) Delete archivelogs on my PRIMARY server only when these logs are successfully TRANSFERED to all my standby databases?
2) Delete archivelogs on my STANDBY server only when these logs are sucessfully APPLIED to the database?
Thanks a lot for your help!on 10G
CONFIGURE ARCHIVELOG DELETION POLICY TO [CLEAR | NONE | APPLIED ON STANDBY];
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rman.htm#CHDBEICE
Coskan Gundogar
http://coskan.wordpress.com -
Reaction at Standby Database in 10g for alter , addtion, deletion tablespac
Deal All,
I want to know that what will be reaction on standby database (10g) if i alter , add , delete tablespace or datafile at primary database.depends on the parameter STANDBY_FILE_MANAGEMENT . please check
http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14239/manage_ps.htm#i1010428 -
Steps to rollback when Logical Standby Database creation fails
Hi,
In case while creating a logical standby database it fails. What steps should be done on primary to rollback the earlier steps. Because while creating logical standby we do certain tasks on primary e.g.
1) create supplemental logging.
2) update init file.
Regards,
TusharHi,
Thanks for the mail. Should I drop the supplemental logging using
"Alter database DROP Supplemental Log data;".
or if we need to disable, how can we do so?
Rest is ok. Anyways I would not be using force logging.
Droping of additional tablespace created to keep logminer tables on primary.
Removing of log_archive_dest_2 information from primary init.
I think the above should do.
Regards,
Tushar -
Switchover_status "FAILED DESTINATION" on both primary-standby databases
Hi,
I setup primary-standby databases and try to test the switchover functionality between them using the following commands:
alter database commit to switchover to primary with session shutdown;
alter database commit to switchover to physical standby with session shutdown;
Currently, both DBs are showing
open_mode= READ WRITE for "select open_mode_from v$database;" and
switchover_status = FAILED DESTINATION for "select switchover_status from v$database"
When both databases get into these states, how can I return them back to primary and standby roles? Could you please provide me a sequence of steps that I can execute to return them back to normal primary-standby states?
Thanks in advance for your suggestion.The OS is Red hat 4.1.2-500.
Oracle version is 11g.
Here is the sequence of steps that lead to this issue:
1. switchover_status on primary = to standby, switchover_status on secondary = not allowed
So on primary, I execute
alter database commit to switchover to physical standby with session shutdown;
and could be shutdown/startup mount ( I don't remember exactly)
2. switchover_status on secondary = to primary
So on secondary, I execute
alter database commit to switchover to primary with session shutdown;
alter database open;
3. Now on secondary, the switchover_status = FAILED DESTINATION
On primary, I execute
alter database commit to switchover to primary with session shutdown;
and could be "alter database open" ( I don't remember exactly)
The switchover_status in step 1) and 2) above should indicates that the data guard is working. At the end of the above steps, I cause both databases to get into switchover_status = "FAILED DESTINATION".
I hope to get one of the DBs back into standby role.
If I execute "alter database commit to switchover to physical standby with session shutdown", I will get
"ORA-16416: No viable Physical Standby switchover targets available"
In this situation, is there any recommendation for rescue? -
Deleting archivelog files once applied to physical standby database
Hi,
Any procedure for automatically deleting the archivelog files after applied to physical standby database.also pls see DataGuard: auto delete redo logs after applied to physical standby?
-
OEM fails to create Standby database
Hi,
I have been trying to create a standby database using the wizard in the OEM. However, it hangs when trying to create the directory structure and files on the standby server. Anybody know how it does this?
Does anyone know why it isn't working on my system.
I have watched for network traffic between the two systems and there doesn't appear to be any whilst it is supposedly creating the files
ThanksThanks sorry I hadn't checked for a while....
Oracle Enterprise Manager 10g Database Control Release 10.1.0.3.0
The standby database is on a remote server, can write to the remote server
I tried both ASM and normal file allocations
Trace Errors...Hmm, I just found lots relating to
No username specified for WBEM fetchlet,
Hopefully I fixed that now. Ah, no it's not.
I also have another in emdctl.trc
2005-07-13 21:53:46 Thread-1 WARN http: snmehl_connect: connect failed to (v20z2:1830): Connection refused (error = 146)
Can't find out what this is, any idead? Could it be related?
Other errors in emagent_perl.trc are old but some appear to relate to the clone operation.
-: Fri Nov 4 10:25:08 2005: ERROR: db_clone.parseOutput(): ORA- ERROR! Exit! See output log.
-: Fri Nov 4 10:25:08 2005: ERROR: db_clone.parseOutput(): ORA- ERROR! Exit! See output log.
dgDatabases.pl: Thu Feb 9 01:18:02 2006: ERROR: dgutil.handleError()
dgDatabases.pl: Thu Feb 9 01:18:02 2006: ERROR: SQL Error: ORA-12505: TNS:listener does not currently know of
SID given in connect descriptor (DBD ERROR: OCIServerAttach)
dgDatabases.pl: Sun Feb 12 11:40:04 2006: ERROR: dgutil.handleError()
dgDatabases.pl: Sun Feb 12 11:40:04 2006: ERROR: SQL Error: ORA-12528: TNS:listener: all appropriate instances
are blocking new connections (DBD ERROR: OCIServerAttach)
dgDatabases.pl: Sun Feb 12 11:57:06 2006: ERROR: The Data Guard configuration must be enabled.
dgDatabases.pl: Sun Feb 12 11:57:06 2006: ERROR: dgutil.handleError()
dgDatabases.pl: Sun Feb 12 11:57:06 2006: ERROR: The Data Guard configuration must be enabled.
I am working through the creation process manually on a test database. I don't want to trach my production database... I needed to bring it online earlier than planned and I hadn't solved the standby database problem at that time. Many other problems had been solved though!
Thanks for the help
Maybe you are looking for
-
My 4th gen iPod Touch will not turn on
Over the last two years, I've battled with inconsistent performance from my iPod Touch 32GB 4th Gen. At some point, I think it got overheated, and I believe that's when the battery issues started. Here's an in-depth look at the various problems... 1)
-
hello , i want the GL Account no, from ska1, .... but i am not getting this one ...at the same time i need to get the data from mkpf, mseg, makt based on the valuation type(bwtar) i need to get GL account here the problem is i am not getting the rela
-
How to manage a new Set Up time
I have a Client with a particular requirement to manage Set up time as a planning function. There requirement is that they Campaign a batch of 10 orders and say after every 5 Campaigns they want to manage a new Set Up time to reflect extra cleaning f
-
DMS Content server restriction
Hi All, In the past we have tried to restrict user access to DMS data (on content server) using DOC type/status restriction. Now we are trying to explore the possibilities of restricting users from accessing export control data from a specific conten
-
Epson 635 printer won't install via wireless with Mountain Lion
I am helping a friend with the upgrade to Mountain Lion and She has a giant desktop which I think is a MacPro but I'm not sure. Anyway everything works fine except now her Epson 635 printer won't see the wireless network. To me this seems like a rout