Hi All,
Many a times when taking the rman backup you can face the following error reported in the rman log as shown below
allocated channel: ch00
channel ch00: sid=110 devtype=SBT_TAPE
channel ch00: VERITAS NetBackup for Oracle – Release 5.0GA (2003103006)
allocated channel: ch01
channel ch01: sid=106 devtype=SBT_TAPE
channel ch01: VERITAS NetBackup for Oracle – Release 5.0GA (2003103006)
Starting backup at 19-SEP-07
current log archived
released channel: ch00
released channel: ch01
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 09/19/2007 21:32:32
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file /ExtSD11/oracle/oradata/TMMBFMPR/arch_1_4323.arc
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
RMAN>
Recovery Manager complete.
The above error is mainly due to the specified archivelog could not be found by the rman at the desired location. It can be due to archive log backed up at the OS level and deleted from the location to reclaim some free space Or it may be due accidential deleteion of archive logs.
Hence the ramn backup archive log command will give the above error unless you remove the reference of that archive logs which were deleted at the OS level from the catalog repository of RMAN.
So the solution for above error is make sure the archivelog is avaliable at the desired location. Or try to copy the archive log to that location.
However if the archive log is already backed up you can use the crosscheck command at RMAN prompt so that the missing archive logs will be marked as EXPIRED and then you can delete EXPIRED archivelog reference from the catalog as shown
RMAN> crosscheck archivelog all;
RMAN> delete expired;
Now you can rerun the backup script and the problem must get solved
—————-Script to Collect Data Guard Primary Site Diagnostic Information.txt———-
set echo off
set feedback off
column timecol new_value timestamp
column spool_extension new_value suffix
select to_char(sysdate,’Mondd_hhmi’) timecol,
‘.out’ spool_extension from sys.dual;
column output new_value dbname
select value || ‘_’ output
from v$parameter where name = ‘db_name’;
spool dg_prim_diag_&&dbname&×tamp&&suffix
set linesize 79
set pagesize 35
set trim on
set trims on
alter session set nls_date_format = ‘MON-DD-YYYY HH24:MI:SS’;
set feedback on
select to_char(sysdate) time from dual;
set echo on
– In the following the database_role should be primary as that is what
– this script is intended to be run on. If protection_level is different
– than protection_mode then for some reason the mode listed in
– protection_mode experienced a need to downgrade. Once the error
– condition has been corrected the protection_level should match the
– protection_mode after the next log switch.
column role format a7 tru
column name format a10 wrap
select name,database_role role,log_mode,
protection_mode,protection_level
from v$database;
– ARCHIVER can be (STOPPED | STARTED | FAILED). FAILED means that the
– archiver failed to archive a log last time, but will try again within 5
– minutes. LOG_SWITCH_WAIT The ARCHIVE LOG/CLEAR LOG/CHECKPOINT event log
– switching is waiting for. Note that if ALTER SYSTEM SWITCH LOGFILE is
– hung, but there is room in the current online redo log, then value is
– NULL
column host_name format a20 tru
column version format a9 tru
select instance_name,host_name,version,archiver,log_switch_wait
from v$instance;
– The following query give us information about catpatch.
– This way we can tell if the procedure doesn’t match the image.
select version, modified, status from dba_registry
where comp_id = ‘CATPROC’;
– Force logging is not mandatory but is recommended. Supplemental
– logging must be enabled if the standby associated with this primary is
– a logical standby. During normal operations it is acceptable for
– SWITCHOVER_STATUS to be SESSIONS ACTIVE or TO STANDBY.
column force_logging format a13 tru
column remote_archive format a14 tru
column dataguard_broker format a16 tru
select force_logging,remote_archive,
supplemental_log_data_pk,supplemental_log_data_ui,
switchover_status,dataguard_broker
from v$database;
– This query produces a list of all archive destinations. It shows if
– they are enabled, what process is servicing that destination, if the
– destination is local or remote, and if remote what the current mount ID
– is.
column destination format a35 wrap
column process format a7
column archiver format a8
column ID format 99
column mid format 99
select dest_id “ID”,destination,status,target,
schedule,process,mountid mid
from v$archive_dest order by dest_id;
– This select will give further detail on the destinations as to what
– options have been set. Register indicates whether or not the archived
– redo log is registered in the remote destination control file.
set numwidth 8
column ID format 99
select dest_id “ID”,archiver,transmit_mode,affirm,async_blocks async,
net_timeout net_time,delay_mins delay,reopen_secs reopen,
register,binding
from v$archive_dest order by dest_id;
– The following select will show any errors that occured the last time
– an attempt to archive to the destination was attempted. If ERROR is
– blank and status is VALID then the archive completed correctly.
column error format a55 wrap
select dest_id,status,error from v$archive_dest;
– The query below will determine if any error conditions have been
– reached by querying the v$dataguard_status view (view only available in
– 9.2.0 and above):
column message format a80
select message, timestamp
from v$dataguard_status
where severity in (‘Error’,'Fatal’)
order by timestamp;
– The following query will determine the current sequence number
– and the last sequence archived. If you are remotely archiving
– using the LGWR process then the archived sequence should be one
– higher than the current sequence. If remotely archiving using the
– ARCH process then the archived sequence should be equal to the
– current sequence. The applied sequence information is updated at
– log switch time.
select ads.dest_id,max(sequence#) “Current Sequence”,
max(log_sequence) “Last Archived”
from v$archived_log al, v$archive_dest ad, v$archive_dest_status ads
where ad.dest_id=al.dest_id
and al.dest_id=ads.dest_id
group by ads.dest_id;
– The following select will attempt to gather as much information as
– possible from the standby. SRLs are not supported with Logical Standby
– until Version 10.1.
set numwidth 8
column ID format 99
column “SRLs” format 99
column Active format 99
select dest_id id,database_mode db_mode,recovery_mode,
protection_mode,standby_logfile_count “SRLs”,
standby_logfile_active ACTIVE,
archived_seq#
from v$archive_dest_status;
– Query v$managed_standby to see the status of processes involved in
– the shipping redo on this system. Does not include processes needed to
– apply redo.
select process,status,client_process,sequence#
from v$managed_standby;
– The following query is run on the primary to see if SRL’s have been
– created in preparation for switchover.
select group#,sequence#,bytes from v$standby_log;
– The above SRL’s should match in number and in size with the ORL’s
– returned below:
select group#,thread#,sequence#,bytes,archived,status from v$log;
– Non-default init parameters.
set numwidth 5
column name format a30 tru
column value format a48 wra
select name, value
from v$parameter
where isdefault = ‘FALSE’;
spool off
– - – - – - – - – - – - – - – - Script ends here – - – - – - – - – - – - – - – -
————-Script_to_Collect_Data_Guard_Primary_Site_Diagnostic_Information.txt———
set echo off
set feedback off
column timecol new_value timestamp
column spool_extension new_value suffix
select to_char(sysdate,’Mondd_hhmi’) timecol,
‘.out’ spool_extension from sys.dual;
column output new_value dbname
select value || ‘_’ output
from v$parameter where name = ‘db_name’;
spool dg_prim_diag_&&dbname&×tamp&&suffix
set linesize 79
set pagesize 35
set trim on
set trims on
alter session set nls_date_format = ‘MON-DD-YYYY HH24:MI:SS’;
set feedback on
select to_char(sysdate) time from dual;
set echo on
– In the following the database_role should be primary as that is what
– this script is intended to be run on. If protection_level is different
– than protection_mode then for some reason the mode listed in
– protection_mode experienced a need to downgrade. Once the error
– condition has been corrected the protection_level should match the
– protection_mode after the next log switch.
column role format a7 tru
column name format a10 wrap
select name,database_role role,log_mode,
protection_mode,protection_level
from v$database;
– ARCHIVER can be (STOPPED | STARTED | FAILED). FAILED means that the
– archiver failed to archive a log last time, but will try again within 5
– minutes. LOG_SWITCH_WAIT The ARCHIVE LOG/CLEAR LOG/CHECKPOINT event log
– switching is waiting for. Note that if ALTER SYSTEM SWITCH LOGFILE is
– hung, but there is room in the current online redo log, then value is
– NULL
column host_name format a20 tru
column version format a9 tru
select instance_name,host_name,version,archiver,log_switch_wait
from v$instance;
– The following query give us information about catpatch.
– This way we can tell if the procedure doesn’t match the image.
select version, modified, status from dba_registry
where comp_id = ‘CATPROC’;
– Force logging is not mandatory but is recommended. Supplemental
– logging must be enabled if the standby associated with this primary is
– a logical standby. During normal operations it is acceptable for
– SWITCHOVER_STATUS to be SESSIONS ACTIVE or TO STANDBY.
column force_logging format a13 tru
column remote_archive format a14 tru
column dataguard_broker format a16 tru
select force_logging,remote_archive,
supplemental_log_data_pk,supplemental_log_data_ui,
switchover_status,dataguard_broker
from v$database;
– This query produces a list of all archive destinations. It shows if
– they are enabled, what process is servicing that destination, if the
– destination is local or remote, and if remote what the current mount ID
– is.
column destination format a35 wrap
column process format a7
column archiver format a8
column ID format 99
column mid format 99
select dest_id “ID”,destination,status,target,
schedule,process,mountid mid
from v$archive_dest order by dest_id;
– This select will give further detail on the destinations as to what
– options have been set. Register indicates whether or not the archived
– redo log is registered in the remote destination control file.
set numwidth 8
column ID format 99
select dest_id “ID”,archiver,transmit_mode,affirm,async_blocks async,
net_timeout net_time,delay_mins delay,reopen_secs reopen,
register,binding
from v$archive_dest order by dest_id;
– The following select will show any errors that occured the last time
– an attempt to archive to the destination was attempted. If ERROR is
– blank and status is VALID then the archive completed correctly.
column error format a55 wrap
select dest_id,status,error from v$archive_dest;
– The query below will determine if any error conditions have been
– reached by querying the v$dataguard_status view (view only available in
– 9.2.0 and above):
column message format a80
select message, timestamp
from v$dataguard_status
where severity in (‘Error’,'Fatal’)
order by timestamp;
– The following query will determine the current sequence number
– and the last sequence archived. If you are remotely archiving
– using the LGWR process then the archived sequence should be one
– higher than the current sequence. If remotely archiving using the
– ARCH process then the archived sequence should be equal to the
– current sequence. The applied sequence information is updated at
– log switch time.
select ads.dest_id,max(sequence#) “Current Sequence”,
max(log_sequence) “Last Archived”
from v$archived_log al, v$archive_dest ad, v$archive_dest_status ads
where ad.dest_id=al.dest_id
and al.dest_id=ads.dest_id
group by ads.dest_id;
– The following select will attempt to gather as much information as
– possible from the standby. SRLs are not supported with Logical Standby
– until Version 10.1.
set numwidth 8
column ID format 99
column “SRLs” format 99
column Active format 99
select dest_id id,database_mode db_mode,recovery_mode,
protection_mode,standby_logfile_count “SRLs”,
standby_logfile_active ACTIVE,
archived_seq#
from v$archive_dest_status;
– Query v$managed_standby to see the status of processes involved in
– the shipping redo on this system. Does not include processes needed to
– apply redo.
select process,status,client_process,sequence#
from v$managed_standby;
– The following query is run on the primary to see if SRL’s have been
– created in preparation for switchover.
select group#,sequence#,bytes from v$standby_log;
– The above SRL’s should match in number and in size with the ORL’s
– returned below:
select group#,thread#,sequence#,bytes,archived,status from v$log;
– Non-default init parameters.
set numwidth 5
column name format a30 tru
column value format a48 wra
select name, value
from v$parameter
where isdefault = ‘FALSE’;
spool off
—————————————Script Ends here———————————–
———-Script_to_Collect_Data_Guard_Primary_Site_Diagnostic_Information.txt—–
set echo off
set feedback off
column timecol new_value timestamp
column spool_extension new_value suffix
select to_char(sysdate,’Mondd_hhmi’) timecol,
‘.out’ spool_extension from sys.dual;
column output new_value dbname
select value || ‘_’ output
from v$parameter where name = ‘db_name’;
spool dgdiag_phystby_&&dbname&×tamp&&suffix
set lines 200
set pagesize 35
set trim on
set trims on
alter session set nls_date_format = ‘MON-DD-YYYY HH24:MI:SS’;
set feedback on
select to_char(sysdate) time from dual;
set echo on
–
– ARCHIVER can be (STOPPED | STARTED | FAILED) FAILED means that the archiver failed
– to archive a — log last time, but will try again within 5 minutes. LOG_SWITCH_WAIT
– The ARCHIVE LOG/CLEAR LOG/CHECKPOINT event log switching is waiting for. Note that
– if ALTER SYSTEM SWITCH LOGFILE is hung, but there is room in the current online
– redo log, then value is NULL
column host_name format a20 tru
column version format a9 tru
select instance_name,host_name,version,archiver,log_switch_wait from v$instance;
– The following select will give us the generic information about how this standby is
– setup. The database_role should be standby as that is what this script is intended
– to be ran on. If protection_level is different than protection_mode then for some
– reason the mode listed in protection_mode experienced a need to downgrade. Once the
– error condition has been corrected the protection_level should match the protection_mode
– after the next log switch.
column ROLE format a7 tru
select name,database_role,log_mode,controlfile_type,protection_mode,protection_level
from v$database;
– Force logging is not mandatory but is recommended. Supplemental logging should be enabled
– on the standby if a logical standby is in the configuration. During normal
– operations it is acceptable for SWITCHOVER_STATUS to be SESSIONS ACTIVE or NOT ALLOWED.
column force_logging format a13 tru
column remote_archive format a14 tru
column dataguard_broker format a16 tru
select force_logging,remote_archive,supplemental_log_data_pk,supplemental_log_data_ui,
switchover_status,dataguard_broker from v$database;
– This query produces a list of all archive destinations and shows if they are enabled,
– what process is servicing that destination, if the destination is local or remote,
– and if remote what the current mount ID is. For a physical standby we should have at
– least one remote destination that points the primary set but it should be deferred.
COLUMN destination FORMAT A35 WRAP
column process format a7
column archiver format a8
column ID format 99
select dest_id “ID”,destination,status,target,
archiver,schedule,process,mountid
from v$archive_dest;
– If the protection mode of the standby is set to anything higher than max performance
– then we need to make sure the remote destination that points to the primary is set
– with the correct options else we will have issues during switchover.
select dest_id,process,transmit_mode,async_blocks,
net_timeout,delay_mins,reopen_secs,register,binding
from v$archive_dest;
– The following select will show any errors that occured the last time an attempt to
– archive to the destination was attempted. If ERROR is blank and status is VALID then
– the archive completed correctly.
column error format a55 tru
select dest_id,status,error from v$archive_dest;
– Determine if any error conditions have been reached by querying thev$dataguard_status
– view (view only available in 9.2.0 and above):
column message format a80
select message, timestamp
from v$dataguard_status
where severity in (‘Error’,'Fatal’)
order by timestamp;
– The following query is ran to get the status of the SRL’s on the standby. If the
– primary is archiving with the LGWR process and SRL’s are present (in the correct
– number and size) then we should see a group# active.
select group#,sequence#,bytes,used,archived,status from v$standby_log;
– The above SRL’s should match in number and in size with the ORL’s returned below:
select group#,thread#,sequence#,bytes,archived,status from v$log;
– Query v$managed_standby to see the status of processes involved in the
– configuration.
select process,status,client_process,sequence#,block#,active_agents,known_agents
from v$managed_standby;
– Verify that the last sequence# received and the last sequence# applied to standby
– database.
select max(al.sequence#) “Last Seq Recieved”, max(lh.sequence#) “Last Seq Applied”
from v$archived_log al, v$log_history lh;
– The V$ARCHIVE_GAP fixed view on a physical standby database only returns the next
– gap that is currently blocking redo apply from continuing. After resolving the
– identified gap and starting redo apply, query the V$ARCHIVE_GAP fixed view again
– on the physical standby database to determine the next gap sequence, if there is
– one.
select * from v$archive_gap;
– Non-default init parameters.
set numwidth 5
column name format a30 tru
column value format a50 wra
select name, value
from v$parameter
where isdefault = ‘FALSE’;
spool off
————————————-Script Ends Here————————————