Data guard - missed archive log

Hi:
I am on 10.2.0.3, using physical standby. One of my check-up sqls shows missed (not applied) arch log:
SELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG
where applied='NO'
THREAD# SEQUENCE# APP
1 16595 NO
It's relatively old one, my max is 18211i and the log application is going fine.
How can I apply this missed one? Do I have to stop managed recovery and do manual recovery for it?
TIA.

GregX,
Please check if this file actually needs to be applied.
You can find out the when the archived log file was created – FIRST_TIME/NEXT_TIME columns in V$ARCHIVED_LOG.
If the archived log file was created before you created the stand-by DB, you do not need ( nor you can) to apply that file.
Please note that the physical standby would stop applying archivelog if you fail to provide the next required archive log file. Since this has not happened (as per your statement) there is a good chance that you archive redo in question is not needed.
Hope that helps,
Edited by: IordanIotzov on Jan 30, 2009 1:34 PM

Similar Messages

RMAN,Data Guard and Archive log deletion

Our DG environment is running Oracle 11g R2
we have a 3 node DG environment with
A being the Primary
B and C being Active Data Guard Standbys
Backups are taken off of B and go directly to tape.
Standby Redo Logs and Fast Recovery Area are being used
Taking recommendation from "Using Recovery Manager with Oracle Data Guard in Oracle Database 10g"
RMAN Setting on Primary ("A")
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY
RMAN Setting on Standby ("B") where Backup is done
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE
RMAN Setting on other Standby ("C")
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY
How can we know what archive logs are eligible to be deleted from "A" and "C" ?
When does the delete take place?
How can we tell when the archive logs are being deleted from "A" and "C" ?

Dear user10260925,
The documentation that you have read is reliable but insufficient.
The Oracle can manage the archivelog directory and knows which one is eligible for the deletion. Those stuff you have posted in here has been taken from the online documentation and is supported and can be used when the Oracle knows and manages the archivelogs. That is simply called the flash recovery area. Please read about the FRA in this very moment.
Under normal circumstances people in the industry uses some scripts to achive the archivelog deletion on the standby system.
Here is a useful example to you;
# Remove old archivelogs
00,30 * * * * /home/oracle/scripts/delete_applied_redo_logs_OPTSTBY.sh
vals3:/home/oracle#cat /home/oracle/scripts/delete_applied_redo_logs_OPTSTBY.sh
export ORACLE_SID=optstby
export ORACLE_HOME=/oracle/product/10.2.0/db_1
cd /db/optima/archive/OPTPROD/archivelog
/oracle/product/10.2.0/db_1/bin/sqlplus "/ as sysdba" @delete_applied_redo_logs.sql
grep arc delete_applied_redo_logs.lst > delete_applied_redo_logs_1.sh
chmod 755 delete_applied_redo_logs_1.sh
sh delete_applied_redo_logs_1.sh
rm delete_applied_redo_logs_1.sh
rm delete_applied_redo_logs.lst
vals3:/home/oracle#cd /db/optima/archive/OPTPROD/archivelog
vals3:/db/optima/archive/OPTPROD/archivelog#cat delete_applied_redo_logs.sql
set echo off
set heading off
spool /db/optima/archive/OPTPROD/archivelog/delete_applied_redo_logs.lst
select 'rm -f ' || name from v$archived_log where applied = 'YES';
spool off
exit
vals3:/db/optima/archive/OPTPROD/archivelog#Hope That Helps.
Ogan

Missing archived logs in v$archived_log

I want to monitor if system accounts such as system, sys or other DBA accounts
did any DML in my application schema. What are the minimal audit statements?
needed to accomplish this. I know using Oracle Database Vault one can set realm to restrict this but I do
not have Data Vault, just looking to audit this using Oracle’s database auditing.
My organization also has Oracle Audi Vault, but Database Auditing Events have to be set in database
first for collection agent to pass this information to Oracle Audit Vault server.
Thanks a lot.

Duplicate post
Please ignore
Missing archived logs in v$archived_log
Handle:      user632098
Status Level:      Newbie
Registered:      Apr 20, 2008
Total Posts:      115
Total Questions:      29 (28 unresolved)
Edited by: sb92075 on Dec 19, 2009 4:49 PM

Problems Recovering Sysaux table space with missing archive log

Dear All
We have a 10G r2 database running on RHEL 4.2.
Today when updating certain records in one of the databases. whe have started getting the following error:
error occurred at recursive SQL level 2 ORA-00376: file 3 cannot be read at this time ORA-01110: data file 3: '/u02/oradata/EDM/datafile/o1_mf_sysaux_1wwwhpg5_.dbf'
This appears to have occurred as a result of one ofthe users adding a large amount of data to a table in one of the other tablespaces. Checking the V$datafile view shows this file to have a status of RECOVER. However on trying to do a
recover datafile 3;
I'm told that a change number generated back in April 2006 is required, this being in an archive log we no longer have.
My question is how do I recover the datafile to the point in time shown without causing all the other tablespaces to revert to that date.
It seems the SYSAUX tablespace has been in RECOVER status for some time now with no effect on the operation of the database. As such I'm loathe to return all of the database back to 04/2006 and lose 18 months work. Is it possible to just fix the SYSAUX tablespace? If so what is the process? If I recover the TS to the point in time that the missing archive log occurs and then do a reset logs will that truncate all the other tablespaces.
Many Thanks
Paul

Thanks for the reply
WE have a table named mlm_papertrail which, having added about 2000 rows to it, now causes the error shown whenever someone tries to insert a new row into it. Ihave created a new table and pointed the application to it and the problem no longer occurs.
However the SYSAUX tablespace is marked recover as is the datafile that forms it. I can only assume that adding the rows to the table has in turn caused sysaux to expand until it has hit a part of the disk that is damaged or corrupt.
I've tried recovering both the tablespace and the datafile getting the request for the archivelog back in 04/06. Again I can only assume the sysaux file has been damaged at this point, but till now hasn't caused any problems.
I don't want to roll the whole database back to 04/06 since in the main it works fine. But obviously the SYSAUX tablespace needs recovering.
My question is how do I do that with as little pain as possible :-)
Anyway, thanks for the advice. I'll try what you suggest.
regards
paul

Will CDC look for a missing archive log in an alternate log_archive_dest ?

Will CDC look for a missing archive log in an alternate log_archive_dest ?
If a log is deleted from the primary dest, will CDC look in all the altenate destinations before failing? Or is it unaware of the other destinations?

Duplicate post:
missing archive log in backup and restore

Data Guard Missing Redo Archive Logs

Hi All Gurus
I have setup data guard on windows 2008 server sp2 with oracle 10.2.0.4.0 (Both OS & Oracle DB are 64 bits).
The Network Admin have shutdown Backup server. Now when I checked the Archive status as follows
1. select * from v$archive_gap;            It shows a gap in archives       e.g. 891 - 920.
2. SELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG;                 e.g. 891-920 Not Applied.
Now I issue following command
1. SELECT RECOVERY_MODE FROM V$ARCHIVE_DEST_STATUS;                                e.g. MANAGED REAL TIME APPLY
2. DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
or ALTER DATABASE RECOVER managed standby database disconnect from session ;
                    e.g.      incompatible Media Recovery in Progress
3. Alert Log says Adjust CONTROL_FILE_RECORD_KEEP_TIME to sufficient limits.
I have also adjusted CONTROL_FILE_RECORD_KEEP_TIME to 90 days as follows
4. show parameter control_file          e.g. CONTROL_FILE_RECORD_KEEP_TIME=90
5. I have checked firewall and tnsping for both Primary and Standby Server e.g. tnsping CVMIS (Primary), CVMISBK (Standby)
     Both are OK. TNSPING is showing 10-30msec delay.
6. I have checked the web for gap Removal, Mostly are using RMAN method to Backup and then Restore to Standby DB.
      Is there any other way to fill this gap without using RMAN? I mean DG automatically fill it by using some commands
     are settings?
Kind Regards
Thunder2777

Hi CKPT
Thanks for the scripts which I executed today on 24 Mon 2013. Here are the Results.
Standby Database Script Output:
NAME                           DISPLAY_VALUE
db_file_name_convert
db_name                            UMIS
db_unique_name                 UMISBK
dg_broker_config_file1         C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\DR1UMISBK.DAT
dg_broker_config_file2         C:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\DR2UMISBK.DAT
dg_broker_start                TRUE
fal_client                          (DESCRIPTION=(ADDRESS_LIST=(AD
                                       DRESS=(PROTOCOL=tcp)(HOST=WIN-
                                       7VSLKL4CGU2)(PORT=1521)))(CONN
                                       ECT_DATA=(SERVICE_NAME=umisbk_
                                       XPT)(INSTANCE_NAME=umisbk)(SER
                                       VER=dedicated)))
fal_server                         (DESCRIPTION=(ADDRESS_LIST=(AD
                                       DRESS=(PROTOCOL=tcp)(HOST=CV-A
                                       JKDB)(PORT=1521)))(CONNECT_DAT
                                       A=(SERVICE_NAME=umis_XPT)(SERV
                                       ER=dedicated)))
local_listener
log_archive_config               DG_CONFIG=(UMIS,UMISBK)
log_archive_dest_2             SERVICE=UMIS LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=UMIS
log_archive_dest_state_2           ENABLE
log_archive_max_processes      10
log_file_name_convert                E:\oracle\product\10.2.0\flash_recovery_area\UMIS\, D:\ORACLE\FRA\UMISBK
remote_login_passwordfile         EXCLUSIVE
standby_archive_dest                D:\ORACLE\FRA\UMISBK\ARCHIVELOG\
standby_file_management                         AUTO
NAME       DB_UNIQUE_NAME                 PROTECTION_MODE DATABASE_R OPEN_MODE
UMIS       UMISBK      MAXIMUM PERFORMANCE PHYSICAL STANDBY MOUNTED
   THREAD# MAX(SEQUENCE#)
         1            890
PROCESS   STATUS          THREAD# SEQUENCE#
ARCH      CONNECTED             0          0
ARCH      CONNECTED             0          0
ARCH      CONNECTED             0          0
ARCH      CONNECTED             0          0
ARCH      CLOSING                   1       1062
ARCH      CONNECTED             0          0
ARCH      CONNECTED             0          0
ARCH      CONNECTED             0          0
ARCH      CONNECTED             0          0
ARCH      CONNECTED             0          0
MRP0      WAIT_FOR_GAP          1        891
RFS       IDLE                  1       1063
RFS       IDLE                  0          0
NAME                           VALUE      UNIT                           TIME_COMPUTED
apply finish time                         day(2) to second(1) interval
apply lag                                   day(2) to second(0) interval
estimated startup time                22         second
standby has been open              N
transport lag                             day(2) to second(0) interval
   THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
         1           891            948
NAME                                                            Size MB    Used MB
D:\ORACLE\FRA                                                      2048          0
STANDBY Alert Log:
Mon Jun 24 10:19:55 2013
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[2]: Assigned to RFS process 1868
RFS[2]: Identified database type as 'physical standby'
RFS[2]: Successfully opened standby log 5: 'D:\ORACLE\ORADATA\UMISBK\SLOG02.LOG'
Mon Jun 24 10:22:09 2013
Adjusting the default value of parameter parallel_max_servers
from 160 to 135 due to the value of parameter processes (150)
Mon Jun 24 10:22:09 2013
Starting ORACLE instance (normal)
Mon Jun 24 10:22:09 2013
alter database mount standby database
ORA-1154 signalled during: alter database mount standby database...
Mon Jun 24 10:22:09 2013
alter database recover managed standby database using current logfile disconnect from session
Mon Jun 24 10:22:40 2013
ORA-1153 signalled during: alter database recover managed standby database using current logfile disconnect from session...
Adjusting the default value of parameter parallel_max_servers
from 160 to 135 due to the value of parameter processes (150)
Mon Jun 24 10:24:40 2013
Starting ORACLE instance (normal)
Mon Jun 24 10:24:40 2013
alter database mount standby database
ORA-1154 signalled during: alter database mount standby database...
Mon Jun 24 10:24:40 2013
alter database recover managed standby database using current logfile disconnect from session
Mon Jun 24 10:25:11 2013
ORA-1153 signalled during: alter database recover managed standby database using current logfile disconnect from session...
Mon Jun 24 10:26:46 2013
Adjusting the default value of parameter parallel_max_servers
from 160 to 135 due to the value of parameter processes (150)
Mon Jun 24 10:26:46 2013
Starting ORACLE instance (normal)
Mon Jun 24 10:28:04 2013
alter database mount standby database
Mon Jun 24 10:28:04 2013
ORA-1154 signalled during: alter database mount standby database...
PRIMARY Database Script Output:
NAME                           DISPLAY_VALUE
db_file_name_convert           UMIS, UMISBK
db_name                             UMIS
db_unique_name                  UMIS
dg_broker_config_file1           E:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\DR1UMIS.DAT
dg_broker_config_file2           E:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\DR2UMIS.DAT
dg_broker_start                   TRUE
fal_client                             UMIS
fal_server                            UMISBK
local_listener
log_archive_config               DG_CONFIG=(UMIS,UMISBK)
log_archive_dest_2             service="(DESCRIPTION=(ADDRESS
                                         _LIST=(ADDRESS=(PROTOCOL=tcp)(
                                         HOST=WIN-7VSLKL4CGU2)(PORT=152
                                         1)))(CONNECT_DATA=(SERVICE_NAM
                                         E=umisbk_XPT)(INSTANCE_NAME=um
                                         isbk)(SERVER=dedicated)))",
                                         LGWR ASYNC NOAFFIRM delay=0 O
                                         PTIONAL max_failure=0 max_conn
                                         ections=1   reopen=300 db_uniq
                                         ue_name="umisbk" register net_
                                         timeout=180 valid_for=(online
                                         _logfile,primary_role)
log_archive_dest_state_2          ENABLE
log_archive_max_processes      2
log_file_name_convert               E:\oracle\product\10.2.0\flash_recOvery_area\UMIS ARCHIVELOG\, D:\ORACLE\FRA\UMISBK\ARCHIVELOG\
remote_login_passwordfile            EXCLUSIVE
standby_archive_dest
standby_file_management             AUTO
NAME       DB_UNIQUE_NAME                 PROTECTION_MODE      DATABASE_R OPEN_MODE SWITCHOVER_STATUS
UMIS       UMIS                   MAXIMUM PERFORMANCE PRIMARY    READ WRITE SESSIONS ACTIVE
   THREAD# MAX(SEQUENCE#)
         1           1062
    Thread Last Sequence Received Last Sequence Applied Difference
         1                   1062                  1062          0
         1                   1062                  1062          0
SEVERITY        ERROR_CODE timestamp            MESSAGE
Error                12514 24-JUN-2013 10:08:02 LGWR: Error 12514 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))
Error                12514 24-JUN-2013 10:08:04 LGWR: Error 12514 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))
Error                12514 24-JUN-2013 10:08:07 FAL[server, ARC1]: Error 12514 creating remote archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'
Error                12514 24-JUN-2013 10:08:31 LGWR: Error 12514 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))
Error                12514 24-JUN-2013 10:08:59 FAL[server, ARC1]: Error 12514 creating remote archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'
Error                12514 24-JUN-2013 10:14:57 PING[ARC1]: Heartbeat failed to connect to standby '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'. Error is 12514.
ID STATUS    DB_MODE         TYPE RECOVERY_MODE        PROTECTION_MODE      SRLs ACTIVE ARCHIVED_SEQ#
1 VALID     OPEN            ARCH IDLE                 MAXIMUM PERFORMANCE     0      0          1062
2 VALID     UNKNOWN         LGWR UNKNOWN              MAXIMUM PERFORMANCE     4      3          1054
NAME                                                            Size MB    Used MB
E:\oracle\product\10.2.0\flash_recovery_area                       2048          0
Primary Alert Log:
System parameters with non-default values:
processes                      = 150
__shared_pool_size        = 335544320
__large_pool_size           = 16777216
__java_pool_size            = 33554432
__streams_pool_size      = 0
sga_target                     = 1258291200
control_files            = E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\CONTROL01.CTL, E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\CONTROL02.CTL, E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\CONTROL03.CTL
db_file_name_convert     = UMIS, UMISBK
log_file_name_convert    = E:\oracle\product\10.2.0\flash_recOvery_area\UMIS ARCHIVELOG\, D:\ORACLE\FRA\UMISBK\ARCHIVELOG\
control_file_record_keep_time= 90
db_block_size                      = 8192
__db_cache_size                 = 855638016
compatible                           = 10.2.0.3.0
log_archive_config                = DG_CONFIG=(UMIS,UMISBK)
log_archive_dest_1       = location="E:\oracle\product\10.2.0\flash_recovery_area\UMIS\ARCHIVELOG", valid_for=(ONLINE_LOGFILE,ALL_ROLES)
log_archive_dest_2       = service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))",    LGWR ASYNC NOAFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1   reopen=300 db_unique_name="umisbk" register net_timeout=180 valid_for=(online_logfile,primary_role)
log_archive_dest_state_1 = ENABLE
log_archive_dest_state_2 = ENABLE
log_archive_max_processes= 2
log_archive_min_succeed_dest= 1
standby_archive_dest     =
log_archive_trace        = 0
log_archive_format       = ARC_s%S_r%R_t%T.arc
fal_client               = UMIS
fal_server               = UMISBK
archive_lag_target       = 0
db_file_multiblock_read_count= 16
db_recovery_file_dest    = E:\oracle\product\10.2.0\flash_recovery_area
db_recovery_file_dest_size= 2147483648
standby_file_management = AUTO
undo_management          = AUTO
undo_tablespace          = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain                =
dispatchers              = (PROTOCOL=TCP) (SERVICE=UMISXDB)
job_queue_processes      = 10
audit_file_dest          = E:\ORACLE\PRODUCT\10.2.0\ADMIN\UMIS\ADUMP
background_dump_dest     = E:\ORACLE\PRODUCT\10.2.0\ADMIN\UMIS\BDUMP
user_dump_dest           = E:\ORACLE\PRODUCT\10.2.0\ADMIN\UMIS\UDUMP
core_dump_dest           = E:\ORACLE\PRODUCT\10.2.0\ADMIN\UMIS\CDUMP
db_name                  = UMIS
open_cursors             = 300
pga_aggregate_target     = 417333248
dg_broker_start          = TRUE
PSP0 started with pid=3, OS id=2824
MMAN started with pid=4, OS id=2820
DBW0 started with pid=5, OS id=2396
LGWR started with pid=6, OS id=2676
CKPT started with pid=7, OS id=2692
SMON started with pid=8, OS id=2096
RECO started with pid=9, OS id=2924
CJQ0 started with pid=10, OS id=2832
MMON started with pid=11, OS id=3052
Mon Jun 24 10:07:34 2013
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Mon Jun 24 10:07:34 2013
starting up 1 shared server(s) ...
MMNL started with pid=12, OS id=2700
DMON started with pid=15, OS id=2908
PMON started with pid=2, OS id=2812
Mon Jun 24 10:07:35 2013
alter database mount exclusive
Mon Jun 24 10:07:40 2013
Setting recovery target incarnation to 2
Mon Jun 24 10:07:42 2013
Successful mount of redo thread 1, with mount id 316954407
Mon Jun 24 10:07:42 2013
Database mounted in Exclusive Mode
Completed: alter database mount exclusive
Mon Jun 24 10:07:42 2013
alter database open
Mon Jun 24 10:07:47 2013
Starting Data Guard Broker (DMON)
NSV1 started with pid=16, OS id=3552
Mon Jun 24 10:07:50 2013
Beginning crash recovery of 1 threads
parallel recovery started with 7 processes
INSV started with pid=24, OS id=3628
Mon Jun 24 10:07:52 2013
Started redo scan
Mon Jun 24 10:07:53 2013
Completed redo scan
144 redo blocks read, 60 data blocks need recovery
Mon Jun 24 10:07:53 2013
Started redo application at
Thread 1: logseq 1059, block 8380
Mon Jun 24 10:07:53 2013
Recovery of Online Redo Log: Thread 1 Group 3 Seq 1059 Reading mem 0
Mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO03.LOG
Mon Jun 24 10:07:53 2013
Completed redo application
Mon Jun 24 10:07:53 2013
Completed crash recovery at
Thread 1: logseq 1059, block 8524, scn 26461769
60 data blocks read, 60 data blocks written, 144 redo blocks read
Mon Jun 24 10:07:57 2013
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=25, OS id=3804
ARC1 started with pid=26, OS id=3808
Mon Jun 24 10:07:57 2013
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
RSM0 started with pid=27, OS id=3812
LNS1 started with pid=28, OS id=3824
Mon Jun 24 10:08:01 2013
Thread 1 advanced to log sequence 1060 (thread open)
Thread 1 opened at log sequence 1060
Current log# 1 seq# 1060 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO01.LOG
Successful open of redo thread 1
Mon Jun 24 10:08:02 2013
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Mon Jun 24 10:08:02 2013
ARC1: STARTING ARCH PROCESSES
Mon Jun 24 10:08:02 2013
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
Mon Jun 24 10:08:02 2013
ARC2: Archival started
Mon Jun 24 10:08:02 2013
ARC1: STARTING ARCH PROCESSES COMPLETE
ARC2 started with pid=29, OS id=3544
ARC1: Becoming the heartbeat ARCH
Mon Jun 24 10:08:02 2013
LGWR: Setting 'active' archival for destination LOG_ARCHIVE_DEST_2
Error 12514 received logging on to the standby
LGWR: Error 12514 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'
Mon Jun 24 10:08:02 2013
Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_lns1_3824.trc:
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Mon Jun 24 10:08:02 2013
SMON: enabling cache recovery
Mon Jun 24 10:08:03 2013
ALTER SYSTEM SET log_archive_dest_2='service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))"','   LGWR ASYNC NOAFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1   reopen=300 db_unique_name="umisbk" register net_timeout=180 valid_for=(online_logfile,primary_role)' SCOPE=BOTH;
Mon Jun 24 10:08:03 2013
LNS: Failed to archive log 1 thread 1 sequence 1060 (12514)
Mon Jun 24 10:08:03 2013
ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=BOTH;
Mon Jun 24 10:08:03 2013
ALTER DATABASE OPEN
Mon Jun 24 10:08:03 2013
ORA-1531 signalled during: ALTER DATABASE OPEN...
Mon Jun 24 10:08:04 2013
Error 12514 received logging on to the standby
LGWR: Error 12514 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'
Mon Jun 24 10:08:04 2013
Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_lns1_3824.trc:
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
LNS: Failed to archive log 1 thread 1 sequence 1060 (12514)
Mon Jun 24 10:08:04 2013
Successfully onlined Undo Tablespace 1.
Mon Jun 24 10:08:04 2013
SMON: enabling tx recovery
Mon Jun 24 10:08:05 2013
Database Characterset is WE8MSWIN1252
Opening with internal Resource Manager plan
where NUMA PG = 1, CPUs = 8
Mon Jun 24 10:08:06 2013
Error 12514 received logging on to the standby
Mon Jun 24 10:08:06 2013
Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_arc1_3808.trc:
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
FAL[server, ARC1]: Error 12514 creating remote archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'
FAL[server, ARC1]: FAL archive failed, see trace file.
Mon Jun 24 10:08:07 2013
replication_dependency_tracking turned off (no async multimaster replication found)
Mon Jun 24 10:08:07 2013
Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_arc1_3808.trc:
ORA-16055: FAL request rejected
Mon Jun 24 10:08:07 2013
ARCH: FAL archive failed. Archiver continuing
Mon Jun 24 10:08:08 2013
Starting background process QMNC
QMNC started with pid=28, OS id=3984
Mon Jun 24 10:08:15 2013
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Mon Jun 24 10:08:15 2013
Completed: alter database open
Mon Jun 24 10:08:19 2013
ALTER SYSTEM SET standby_archive_dest='' SCOPE=BOTH SID='umis';
Mon Jun 24 10:08:19 2013
ALTER SYSTEM SET log_archive_trace=0 SCOPE=BOTH SID='umis';
Mon Jun 24 10:08:19 2013
ALTER SYSTEM SET log_archive_format='ARC_s%S_r%R_t%T.arc' SCOPE=SPFILE SID='umis';
Mon Jun 24 10:08:20 2013
ALTER SYSTEM SET standby_file_management='AUTO' SCOPE=BOTH SID='*';
Mon Jun 24 10:08:20 2013
ALTER SYSTEM SET archive_lag_target=0 SCOPE=BOTH SID='*';
Mon Jun 24 10:08:20 2013
ALTER SYSTEM SET log_archive_max_processes=2 SCOPE=BOTH SID='*';
Mon Jun 24 10:08:21 2013
ALTER SYSTEM SET log_archive_min_succeed_dest=1 SCOPE=BOTH SID='*';
Mon Jun 24 10:08:21 2013
ALTER SYSTEM SET db_file_name_convert='UMIS','UMISBK' SCOPE=SPFILE;
Mon Jun 24 10:08:21 2013
ALTER SYSTEM SET log_file_name_convert='E:\oracle\product\10.2.0\flash_recOvery_area\UMIS ARCHIVELOG\','D:\ORACLE\FRA\UMISBK\ARCHIVELOG\' SCOPE=SPFILE;
Mon Jun 24 10:08:21 2013
ALTER SYSTEM ARCHIVE LOG
Mon Jun 24 10:08:21 2013
Thread 1 cannot allocate new log, sequence 1061
Private strand flush not complete
Current log# 1 seq# 1060 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO01.LOG
Mon Jun 24 10:08:22 2013
Shutting down archive processes
Mon Jun 24 10:08:22 2013
Thread 1 advanced to log sequence 1061 (LGWR switch)
Mon Jun 24 10:08:22 2013
Current log# 2 seq# 1061 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO02.LOG
Mon Jun 24 10:08:27 2013
ARCH shutting down
ARC2: Archival stopped
Mon Jun 24 10:08:27 2013
ALTER SYSTEM SET log_archive_dest_2='service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))"','   LGWR ASYNC NOAFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1   reopen=300 db_unique_name="umisbk" register net_timeout=180 valid_for=(online_logfile,primary_role)' SCOPE=BOTH;
Mon Jun 24 10:08:27 2013
ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=BOTH;
Mon Jun 24 10:08:27 2013
ALTER SYSTEM ARCHIVE LOG
Mon Jun 24 10:08:27 2013
Thread 1 cannot allocate new log, sequence 1062
Private strand flush not complete
Current log# 2 seq# 1061 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO02.LOG
LNS1 started with pid=29, OS id=4204
Mon Jun 24 10:08:31 2013
Thread 1 advanced to log sequence 1062 (LGWR switch)
Current log# 3 seq# 1062 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO03.LOG
Mon Jun 24 10:08:31 2013
Error 12514 received logging on to the standby
LGWR: Error 12514 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'
Mon Jun 24 10:08:31 2013
Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_lns1_4204.trc:
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
LNS: Failed to archive log 3 thread 1 sequence 1062 (12514)
Mon Jun 24 10:08:59 2013
Error 12514 received logging on to the standby
Mon Jun 24 10:08:59 2013
Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_arc1_3808.trc:
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
FAL[server, ARC1]: Error 12514 creating remote archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'
FAL[server, ARC1]: FAL archive failed, see trace file.
Mon Jun 24 10:08:59 2013
Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_arc1_3808.trc:
ORA-16055: FAL request rejected
ARCH: FAL archive failed. Archiver continuing
Mon Jun 24 10:14:57 2013
Error 12514 received logging on to the standby
Mon Jun 24 10:14:57 2013
Errors in file e:\oracle\product\10.2.0\admin\umis\bdump\umis_arc1_3808.trc:
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
PING[ARC1]: Heartbeat failed to connect to standby '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))'. Error is 12514.
Mon Jun 24 10:18:46 2013
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
Mon Jun 24 10:19:23 2013
ALTER SYSTEM SET log_archive_dest_2='service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=WIN-7VSLKL4CGU2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=umisbk_XPT)(INSTANCE_NAME=umisbk)(SERVER=dedicated)))"','   LGWR ASYNC NOAFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1   reopen=300 db_unique_name="umisbk" register net_timeout=180 valid_for=(online_logfile,primary_role)' SCOPE=BOTH;
Mon Jun 24 10:19:23 2013
ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=BOTH;
Mon Jun 24 10:19:23 2013
ALTER SYSTEM ARCHIVE LOG
Mon Jun 24 10:19:24 2013
Thread 1 cannot allocate new log, sequence 1063
Private strand flush not complete
Current log# 3 seq# 1062 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO03.LOG
LNS1 started with pid=18, OS id=4300
Mon Jun 24 10:19:28 2013
Thread 1 advanced to log sequence 1063 (LGWR switch)
Current log# 1 seq# 1063 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\UMIS\REDO01.LOG
Mon Jun 24 10:19:28 2013
LNS: Standby redo logfile selected for thread 1 sequence 1063 for destination LOG_ARCHIVE_DEST_2
Mon Jun 24 10:19:58 2013
ARC1: Standby redo logfile selected for thread 1 sequence 1062 for destination LOG_ARCHIVE_DEST_2
Well there seems to be some connectivity issue on Primary DB (I Guess!!!).
But when I issue tnsping from Primary Database, the result is
SQL> host tnsping umisbk (Standy DB Name) --->   Status: OK [10-30msec]
And when I issue tnsping from Standby Database, the result is
SQL> host tnsping umis (Primary DB Name)    --->   Status: OK [10-30msec]
So what your Recommendation.
Kind Regards
Thuhnder2777

Standby database is not applying redo logs due to missing archive log

We use 9.2.0.7 Oracle Database. My goal is to create a physical standby database.
I have followed all the steps necessary to fulfill this in Oracle Data Guard Concepts and Administration manual. Archived redo logs are transmitted from primary to standby database regularly. But the logs are not applied due to archive log gap.
SQL> select process, status from v$managed_standby;
PROCESS STATUS
ARCH CONNECTED
ARCH CONNECTED
MRP0 WAIT_FOR_GAP
RFS RECEIVING
RFS ATTACHED
SQL> select * from v$archive_gap;
THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
1 503 677
I have tried to find the missing archives on the primary database, but was unable to. They have been deleted (somehow) regularly by the existing backup policy on the primary database. I have looked up the backups, but these archive logs are too old to be in the backup. Backup retention policy is 1 redundant backup of each file. I didn't save older backups as I didn't really need them from up to this point.
I have cross checked (using rman crosscheck) the archive log copies on the primary database and deleted the "obsolete" copies of archive logs. But, v$archived_log view on the primary database only marked those entries as "deleted". Unfortunately, the standby database is still waiting for those logs to "close the gap" and doesn't apply the redo logs at all. I am reluctant to recreate the control file on the primary database as I'm afraid this occurred through the regular database backup operations, due to current backup retention policy and it probably might happen again.
The standby creation procedure was done by using the data files from 3 days ago. The archive logs which are "producing the gap" are older than a month, and are probably unneeded for standby recovery.
What shall I do?
Kind regards and thanks in advance,
Milivoj

On a physical standby database
To determine if there is an archive gap on your physical standby database, query the V$ARCHIVE_GAP view as shown in the following example:
SQL> SELECT * FROM V$ARCHIVE_GAP;
THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
1 7 10
The output from the previous example indicates your physical standby database is currently missing log files from sequence 7 to sequence 10 for thread 1.
After you identify the gap, issue the following SQL statement on the primary database to locate the archived redo log files on your primary
database (assuming the local archive destination on the primary database is LOG_ARCHIVE_DEST_1):
SQL> SELECT NAME FROM V$ARCHIVED_LOG WHERE THREAD#=1 AND DEST_ID=1 AND 2> SEQUENCE# BETWEEN 7 AND 10;
NAME
/primary/thread1_dest/arcr_1_7.arc /primary/thread1_dest/arcr_1_8.arc /primary/thread1_dest/arcr_1_9.arc
Copy these log files to your physical standby database and register them using the ALTER DATABASE REGISTER LOGFILE statement on your physical standby database. For example:
SQL> ALTER DATABASE REGISTER LOGFILE
'/physical_standby1/thread1_dest/arcr_1_7.arc';
SQL> ALTER DATABASE REGISTER LOGFILE
'/physical_standby1/thread1_dest/arcr_1_8.arc';
After you register these log files on the physical standby database, you can restart Redo Apply.
Note:
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 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. Repeat this process until there are no more gaps.
Restoring the archived logs from the backup set
If the archived logs are not available in the archive destination then at that time we need to restore the required archived logs from the backup step. This task is accomplished in the following way.
To restore range specified archived logs:
Run {
Set archivelog destination to '/oracle/arch/arch_restore'
Restore archivelog from logseq=<xxxxx> until logseq=<xxxxxxx>
To restore all the archived logs:
Run {
Set archivelog destination to '/oracle/arch/arch_restore';
Restore archivelog all;
}

Error after Restoring Datafiles in Archivelog but missing archive log files

Hi all,
I have taken backup yesterday monrning in Archive log mode but have lost all the archive log files. Yesterday night i have restored my DB .
I m happy to have my datafile contents till yesterday morning.
But after restoring when i try to open th DB, i m facing the following errors:
SQL>          Startup open;
Oracle instance started but in mounted stagell
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL>         alter database open resetlogs;
Error: ORA-01113: file 1 needs media recovery
          ORA-01110: data file 1: 'E:\oracle\'<SID>\sapdata1\SYSTEM_1\SYSTEM.DATA1'
SQL>         recover database using backup controlfile until cancel;
ORA-00279 : change 26627919 generated at DATE TIMEneeded for thread 1
ORA-00289 : Suggestion E:\ORACLE\<SID>\ORAARCH\<SID>ARCHARC03020_0683715008.001
ORA-00280: change 266277189 for thread 1 is in sequence #3020
ORA - 01112: media recovery not started
SQL>   recover;
ORA-00283: recovery session cancelled due to errors
ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
Alert Log File:
Starting up ORACLE RDBMS Version: 10.2.0.2.0.
System parameters with non-default values:
processes                = 80
sessions                 = 96
event                    = 10191 trace name context forever, level 1
sga_max_size             = 633339904
shared_pool_size         = 301989888
shared_pool_reserved_size= 30183260
filesystemio_options     = setall
control_files            = E:\ORACLE\IE6\ORIGLOGA\CNTRL\CNTRLIE6.DBF, E:\ORACLE\IE6\ORIGLOGB\CNTRL\CNTRLIE6.DBF, E:\ORACLE\IE6\SAPDATA1\CNTRL\CNTRLIE6.DBF
control_file_record_keep_time= 30
db_block_size            = 8192
db_cache_size            = 301989888
compatible               = 10.2.0
log_archive_dest         = E:\oracle\IE6\oraarch\IE6arch
log_buffer               = 2854912
log_checkpoint_interval = 0
db_files                 = 254
log_checkpoints_to_alert = TRUE
dml_locks                = 4000
undo_management          = AUTO
undo_tablespace          = PSAPUNDO
undo_retention           = 43200
recyclebin               = off
remote_os_authent        = TRUE
remote_login_passwordfile= EXCLUSIVE
job_queue_processes      = 1
background_dump_dest     = E:\ORACLE\IE6\SAPTRACE\BACKGROUND
user_dump_dest           = E:\ORACLE\IE6\SAPTRACE\USERTRACE
core_dump_dest           = E:\ORACLE\IE6\SAPTRACE\BACKGROUND
optimizer_features_enable= 10.2.0.1
sort_area_size           = 2097152
sort_area_retained_size = 0
db_name                  = IE6
open_cursors             = 800
optimpeek_user_binds   = FALSE
pga_aggregate_target     = 402443468
workarea_size_policy     = AUTO
statistics_level         = typical
PMON started with pid=2, OS id=804
PSP0 started with pid=3, OS id=9580
MMAN started with pid=4, OS id=5840
DBW0 started with pid=5, OS id=8136
LGWR started with pid=6, OS id=8712
CKPT started with pid=7, OS id=1620
SMON started with pid=8, OS id=7084
RECO started with pid=9, OS id=9576
CJQ0 started with pid=10, OS id=9156
MMON started with pid=11, OS id=6000
MMNL started with pid=12, OS id=2856
Sat Apr 18 04:01:29 2009
ALTER DATABASE   MOUNT
Sat Apr 18 04:01:33 2009
Setting recovery target incarnation to 1
Sat Apr 18 04:01:33 2009
Successful mount of redo thread 1, with mount id 1124466585
Sat Apr 18 04:01:33 2009
Database mounted in Exclusive Mode
Completed: ALTER DATABASE   MOUNT
Sat Apr 18 04:01:34 2009
ALTER DATABASE OPEN
ORA-1589 signalled during: ALTER DATABASE OPEN...
Sat Apr 18 04:02:13 2009
alter database open resetlogs
Sat Apr 18 04:02:13 2009
ORA-1245 signalled during: alter database open resetlogs...
Sat Apr 18 04:11:05 2009
ALTER DATABASE RECOVER DATABASE UNTIL CANCEL
Sat Apr 18 04:11:05 2009
Media Recovery Start
Sat Apr 18 04:11:06 2009
Media Recovery failed with error 1610
ORA-283 signalled during: ALTER DATABASE RECOVER DATABASE UNTIL CANCEL...
Sat Apr 18 04:11:28 2009
ALTER DATABASE RECOVER DATABASE USING BACKUP CONTROLFILE
Sat Apr 18 04:11:28 2009
Media Recovery Start
parallel recovery started with 3 processes
ORA-279 signalled during: ALTER DATABASE RECOVER DATABASE USING BACKUP CONTROLFILE...
Sat Apr 18 04:17:23 2009
ALTER DATABASE RECOVER database using backup controlfile until cancel
Sat Apr 18 04:17:23 2009
Media Recovery Start
ORA-275 signalled during: ALTER DATABASE RECOVER database using backup controlfile until cancel ...
Any suggestions pls..............
Thanks & Regards,
Subbu

Hello Subbu,
> I have taken backup yesterday monrning in Archive log mode but have lost all the archive log files.
You mean you have taken an online backup and lost all your archive log files after that online backup?
SQL> alter database open resetlogs;
Error: ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: 'E:\oracle\'<SID>\sapdata1\SYSTEM_1\SYSTEM.DATA1'
SQL> recover database using backup controlfile until cancel;
ORA-00279 : change 26627919 generated at DATE TIMEneeded for thread 1
ORA-00289 : Suggestion E:\ORACLE\<SID>\ORAARCH\<SID>ARCHARC03020_0683715008.001
ORA-00280: change 266277189 for thread 1 is in sequence #3020
To perform a recovery with an online backup you will need all archive log files until the end of the online backup. If you have lost them you are not able to recover (or open) your database in a consistent state.
So the only suggestion we can do is:
You need the archive log files that were created during the online backup to perform an incomplete recovery ... if they are gone you can not restore your database.
Regards
Stefan

Missing archived logs when recovering database

Scenario is
1-10 archived logs required to recover database.
5 Number log is missing
It means that 6,7,8,9,10 are useless for me
yes/no Please explain it to me
Thanks a Lot

Hi,
Yes all archivelog after the missing sequence of archivelog will be useless for recovery.
in ur case 6,7,8,9,10 are useless for you.
So only incomplete recovery is the solution.
Thanks
Kuljeet Pal Singh

Cleanup data guard drc SID .log

Hi,
Is it possible to automatically rotate and/or cleanup the data guard log in the bdump destination?
Do I manually have to clean/empty/delete or rename the always growing drc<SID>.log file?
thanks for any suggestions

Hi,
You may schedule a job to delete/rename the log file once every month/quarter.....

Duplicate target database - is failed due to missing archive log

Hi,
"duplicate target database to " is failed due to required archive log is not found on tape.
After mounting the right tape, how to proceed , please suggest
ERROR:-->
RMAN>
connect catalog *******
connect auxiliary /
connect target ******
Run {
set until time '16-NOV-2008 23:50';
allocate auxiliary channel t1 type 'sbt_tape' parms ....
duplicate target database to mydb;
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 11/30/2008 10:27:00
RMAN-03015: error occurred in stored script Memory Script
ORA-19501: read error on file "orcl_ARCHIVES_BACKUP_0811160110_u0jvq7vt_1
_1", blockno 1 (blocksize=512)
ORA-27190: skgfrd: sbtread2 returned error
ORA-19511: Error received from media manager layer, error text:
ANS1314E (RC14) File data currently unavailable on server
Recovery Manager complete.
Thanks In Advance,

This is basically not a RMAN problem,but a media management issue,which has to be addressed to the TSM staff:
ANS1314E
File data currently unavailable on server
Explanation:
The file data is currently unavailable on the server. A retrieve or restore operation was attempted. Possible causes are:
Data was corrupted at the server
Server found a read error
File is temporarily involved in a reclaim operation at the server
Server requested a tape volume that was marked unavailable.
System action:
Processing stopped.
User response:
Retry the operation. If the problem continues, see your system administrator to determine the problem from the server console or the activity log. Check whether any requests were made for a tape volume that was unavailable. A tape volume may be marked unavailable if prior read errors were encountered or the volume is checked out of the tape library.
Werner

CAPTURE process error - missing Archive log

Hi -
I am getting cannot open archived log 'xxxx.arc' message when I try to start a newly created capture process. The archive files have been moved by the DBAs.
Is there a way to set the capture process to start from a new archive ?
I tried
exec DBMS_CAPTURE_ADM.ALTER_CAPTURE ( capture_name => 'STRMADMIN_SCH_CAPTURE', start_scn =>9668840362577);
I got the new scn from DBMS_FLASHBACK.GET_SYSTEM_CHANGE_NUMBER();.
But I still get the same error.
Any ideas ?
Thanks,
Sadeepa

If you are on 9i, I know that trying to reset the scn that way won't work. You have to drop and recreate the capture process. You can leave all the rules and rulesets in place, but I think you have to prepare all of the tables again.

Data Guard : Standby Redo Log CONFUSION

Trying to set up test Standby db on 10.2.0
I am well confused about below step 3.1.3, how is the normal redo linked with standby redo, should standby not be members of orginal redo groups?
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#i1225703
Original redo logs:
SQL> select * from v$log;
    GROUP#    THREAD# SEQUENCE#      BYTES    MEMBERS ARC STATUS           FIRST_CHANGE# FIRST_TIME
         1          1         28   52428800          1 YES INACTIVE                375136 22-NOV-07
         2          1         29   52428800          1 YES INACTIVE                375138 22-NOV-07
         3          1         30   52428800          1 NO CURRENT                 375143 22-NOV-07I added below from notes:
ALTER DATABASE ADD STANDBY LOGFILE GROUP 10
('/u01/oracle/oradata/db01/redo01_stb.log') SIZE 50M;
ALTER DATABASE ADD STANDBY LOGFILE GROUP 11
('/u02/oracle/oradata/db01/redo02_stb.log') SIZE 50M;
ALTER DATABASE ADD STANDBY LOGFILE GROUP 12
('/u03/oracle/oradata/db01/redo03_stb.log') SIZE 50M;After few alter system switch logfile; I still have:
    GROUP#    THREAD# SEQUENCE# ARC STATUS
        10          0          0 YES UNASSIGNED
        11          0          0 YES UNASSIGNED
        12          0          0 YES UNASSIGNEDAll are UNASSIGNED, should one standby group not be ACTIVE like the above link shows.
Many think for any help

First things first:
From the Docs.:
"Minimally, the configuration should have one more standby redo log file group than the number of online redo log file groups on the primary database. However, the recommended number of standby redo log file groups is dependent on the number of threads on the primary database. Use the following equation to determine an appropriate number of standby redo log file groups:
(maximum number of logfiles for each thread + 1) * maximum number of threads
Using this equation reduces the likelihood that the primary instance's log writer (LGWR) process will be blocked because a standby redo log file cannot be allocated on the standby database. For example, if the primary database has 2 log files for each thread and 2 threads, then 6 standby redo log file groups are needed on the standby database."
You are 1 short!

Archived log missed in standby database

Hi,
OS; Windows 2003 server
Oracle: 10.2.0.4
Data Guard: Max Performance
Dataguard missed some of the archivelog files and but latest log files are applying. standby database is not in sync with primary.
SELECT LOCAL.THREAD#, LOCAL.SEQUENCE# FROM (SELECT THREAD#, SEQUENCE# FROM V$ARCHIVED_LOG WHERE DEST_ID=1) LOCAL WHERE LOCAL.SEQUENCE# NOT IN (SELECT SEQUENCE# FROM V$ARCHIVED_LOG WHERE DEST_ID=2 AND THREAD# = LOCAL.THREAD#);
I queried above command and I found some files are missed in standby.
select status, type, database_mode, recovery_mode,protection_mode, srl, synchronization_status,synchronized from V$ARCHIVE_DEST_STATUS where dest_id=2;
STATUS TYPE DATABASE_MODE RECOVERY_MODE PROTECTION_MODE SRL SYNCHRONIZATION_STATUS SYN
VALID PHYSICAL MOUNTED-STANDBY MANAGED MAXIMUM PERFORMANCE NO CHECK CONFIGURATION NO
Anyone can tell me how to apply those missed archive log files.
Thanks in advacne

Deccan Charger wrote:
I got below error.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
ERROR at line 1:
ORA-01153: an incompatible media recovery is activeYou need to essentially do the following.
1) Stop managed recovery on the standby.
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;2) Resolve the archive log gap - if you have configured FAL_SERVER and FAL_CLIENT Oracle should do this when you follow step 3 below, as you've manually copied the missed logs you should be OK
3) restart managed recovery using the command shown above.
You can monitor archive log catchup using the alert.log or your original query.
Niall Litchfield
http://www.orawin.info/
Edited by: Niall Litchfield on May 4, 2010 2:29 PM
missed tag

Archive logs are missing in hot backup

Hi All,
We are using the following commands to take hot backup of our database. Hot backup is fired by "backup" user on Linux system.
=======================
rman target / nocatalog <<EOF
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '$backup_dir/$date/%F';
run {
allocate channel oem_backup_disk1 type disk format '$backup_dir/$date/%U';
#--Switch archive logs for all threads
sql 'alter system archive log current';
backup as COMPRESSED BACKUPSET database include current controlfile;
#--Switch archive logs for all threads
sql 'alter system archive log current';
#--Backup Archive logs and delete what we've backedup
backup as COMPRESSED BACKUPSET archivelog all not backed up delete all input;
release channel oem_backup_disk1;
allocate channel for maintenance type disk;
delete noprompt obsolete device type disk;
release channel;
exit
EOF
=======================
Due to which after command (used 2 times) "sql 'alter system archive log current';" I see the following lines in alert log 2 times. Because of this all the online logs are not getting archived (Missing 2 logs per day), the backup taken is unusable when restoring. I am worried about this. I there any to avoid this situation.
=======================
Errors in file /u01/oracle/admin/rac/udump/rac1_ora_3546.trc:
ORA-19504: failed to create file "+DATA/rac/1_32309_632680691.dbf"
ORA-17502: ksfdcre:4 Failed to create file +DATA/rac/1_32309_632680691.dbf
ORA-15055: unable to connect to ASM instance
ORA-01031: insufficient privileges
=======================
Regards,
Kunal.

All thanks you for help, pleas find additional information. I goth the following error as log sequence was missing. Everyday during hotbackup, there are 2 missing archive logs, which makes our backup inconsistent and useless.
archive log filename=/mnt/xtra-backup/ora_archivelogs/1_32531_632680691.dbf thread=1 sequence=32531
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28768_632680691.dbf thread=2 sequence=28768
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28769_632680691.dbf thread=2 sequence=28769
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28770_632680691.dbf thread=2 sequence=28770
archive log filename=/mnt/xtra-backup/ora_archivelogs/1_32532_632680691.dbf thread=1 sequence=32532
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28771_632680691.dbf thread=2 sequence=28771
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28772_632680691.dbf thread=2 sequence=28772
archive log filename=/mnt/xtra-backup/ora_archivelogs/2_28772_632680691.dbf thread=2 sequence=28773
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 12/13/2012 04:22:56
RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/mnt/xtra-backup/ora_archivelogs/2_28772_632680691.dbf'
ORA-00310: archived log contains sequence 28772; sequence 28773 required
ORA-00334: archived log: '/mnt/xtra-backup/ora_archivelogs/2_28772_632680691.dbf'
Let me try the susggestions provided above.

Data guard - missed archive log

Similar Messages

Maybe you are looking for