Archive log fail

Hi guys
I have problem with SAP archive log backups.Sessions will fail there is no archive logs to backup.
Regards
Imrankhan

> I have problem with SAP archive log backups.Sessions will fail there is no archive logs to backup.
Please give more information, logfiles etc.
It's like I'd ask you "my PC is not working, Winword is not starting, plesae help".
Markus

Similar Messages

Archive log missing on standby: FAL[client]: Failed to request gap sequence

My current environment is Oracle 10.2.0.4 with ASM 10.2.0.4 on a 2 node RAC in production and a standby that is the same setup. I'm also running on Oracle Linux 5. Almost daily now an archivelog doesnt make it to the standby and oracle doesnt seem to resolve the gap sequence from the primary. If I stop and restart recovery it gets the logfile and continues recovery just fine. I have checked my fal_client and fal_server settings and they look good. The logs after this error do continue to get written to the standby but the standby wont continue recovery until I stop and restart recovery and it fetches this missing log.
The only thing I know thats happening is that the firewall people are disconnecting any connections that are inactive for 60 minutes and recently did an upgrade that they are claiming didnt change anything:) I dont know if this is causing this problem or not. Any thoughts on what might be happening?
Error in standby alert.log:
Tue Jun 29 23:15:35 2010
RFS[258]: Possible network disconnect with primary database
Tue Jun 29 23:15:36 2010
Fetching gap sequence in thread 2, gap sequence 9206-9206
Tue Jun 29 23:16:46 2010
FAL[client]: Failed to request gap sequence
GAP - thread 2 sequence 9206-9206
DBID 661398854 branch 714087609
FAL[client]: All defined FAL servers have been attempted.
Error on primary alert.log:
Tue Jun 29 23:00:07 2010
ARC0: Creating remote archive destination LOG_ARCHIVE_DEST_2: 'WSSPRDB' (thread 1 sequence 9265)
(WSSPRD1)
ARC0: Transmitting activation ID 0x29c37469
Tue Jun 29 23:00:07 2010
Errors in file /u01/app/oracle/admin/WSSPRD/bdump/wssprd1_arc0_14024.trc:
ORA-03135: connection lost contact
FAL[server, ARC0]: FAL archive failed, see trace file.
Tue Jun 29 23:00:07 2010
Errors in file /u01/app/oracle/admin/WSSPRD/bdump/wssprd1_arc0_14024.trc:
ORA-16055: FAL request rejected
ARCH: FAL archive failed. Archiver continuing
Tue Jun 29 23:00:07 2010
ORACLE Instance WSSPRD1 - Archival Error. Archiver continuing.
Tue Jun 29 23:00:41 2010
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
Tue Jun 29 23:00:41 2010
FAL[server, ARC2]: Begin FAL archive (dbid 0 branch 714087609 thread 2 sequence 9206 dest WSSPRDB)
FAL[server, ARC2]: FAL archive failed, see trace file.
Tue Jun 29 23:00:43 2010
Errors in file /u01/app/oracle/admin/WSSPRD/bdump/wssprd1_arc2_14028.trc:
ORA-16055: FAL request rejected
ARCH: FAL archive failed. Archiver continuing
Tue Jun 29 23:00:43 2010
ORACLE Instance WSSPRD1 - Archival Error. Archiver continuing.
Tue Jun 29 23:01:16 2010
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
Tue Jun 29 23:15:01 2010
Thread 1 advanced to log sequence 9267 (LGWR switch)
I have checked the trace files that get spit out but they arent anything meaningful to me as to whats really happening. Snipit of the trace file:
tkcrrwkx: Starting to process work request
tkcrfgli: SRL header: 0
tkcrfgli: SRL tail: 0
tkcrfgli: ORL to arch: 4
tkcrfgli: le# seq thr for bck tba flags
tkcrfgli: 1 359 1 2 0 3 0x0008 ORL active cur
tkcrfgli: 2 358 1 0 1 1 0x0000 ORL active
tkcrfgli: 3 361 2 4 0 0 0x0008 ORL active cur
tkcrfgli: 4 360 2 0 3 2 0x0000 ORL active
tkcrfgli: 5 -- entry deleted --
tkcrfgli: 6 -- entry deleted --
tkcrfgli: 7 -- entry deleted --
tkcrfgli: 8 -- entry deleted --
tkcrfgli: 9 -- entry deleted --
tkcrfgli: 191 -- entry deleted --
tkcrfgli: 192 -- entry deleted --
*** 2010-03-27 01:30:32.603 20998 kcrr.c
tkcrrwkx: Request from LGWR to perform: <startup>
tkcrrcrlc: Starting CRL ARCH check
*** 2010-03-27 01:30:32.603 66085 kcrr.c
Beginning controlfile transaction 0x0x7fffd0b53198 [kcrr.c:20395 (14011)]
*** 2010-03-27 01:30:32.645 66173 kcrr.c
Acquired controlfile transaction 0x0x7fffd0b53198 [kcrr.c:20395 (14024)]
*** 2010-03-27 01:30:32.649 66394 kcrr.c
Ending controlfile transaction 0x0x7fffd0b53198 [kcrr.c:20397]
tkcrrasgn: Checking for 'no FAL', 'no SRL', and 'HB' ARCH process
# HB NoF NoS CRL Name
29 NO NO NO NO ARC0
28 NO YES YES NO ARC1
27 NO NO NO NO ARC2
26 NO NO NO NO ARC3
25 YES NO NO NO ARC4
24 NO NO NO NO ARC5
23 NO NO NO NO ARC6
22 NO NO NO NO ARC7
21 NO NO NO NO ARC8
20 NO NO NO NO ARC9
Thanks.
Kristi

It's the network that's messing up; unlikely due to firewall timeout as it waits for 60 minutes and you are switching every 15 minutes. There may be some other network glitch that needs rectified.
In any case - arch file missing/ corrupt / halfway through - FAL setting should have refetched the problematic archive log automatically.
As many had suggested already, the best way to resolve RFS issues I believe is to use real-time apply by configuring standby redo logs. It's very easy to configure it and you can opt for real-time apply even in max-performance mode that you are using right now.
Even though you are maintaining (I guess) 1-1 between primary & standby instances, you can provide both primary instances in fal_server (like fal_server=string1,string2). See if that helps.
lastly, check if you are having simiar issue at other times as well that might be getting rectified automatically as expected.
col message for a80
col time for a20
select message, to_char(timestamp,'dd-mon-rr hh24:mi:ss') time
from v$dataguard_status
where severity in ('Error','Fatal')
order by timestamp;
Cheers.

ARC4: Failed to archive log# 3 seq# 2091911 thrd# 1

Hi gurus,
Iam running my database in archivelog mode and I receive following errors in archive trace files. kindly give me a solution and the trace file is attached below
ARC4: Failed to archive log# 3 seq# 2091911 thrd# 1
*** 2006.08.08.02.52.14.656
ARC4: Begin archiving log# 4 seq# 2091912 thrd# 1
ARC4: VALIDATE
ARC4: PREPARE
ARC4: INITIALIZE
ARC4: SPOOL
ARC4: Creating archive destination 1 : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 1 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 129 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 257 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 385 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 513 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 641 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 769 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 897 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 1025 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 1153 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 1281 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 1409 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 1537 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 1665 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 1793 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 1921 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 2049 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 2177 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 2305 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 2433 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 2561 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 2689 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 2817 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 2945 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 3073 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 3201 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 3329 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 3457 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 3585 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 3713 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 3841 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 3969 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 4097 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 4225 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 4353 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 4481 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archiving block 4609 count 128 to : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: Archive destination 1 made inactive: File I/O error
ARC4: Closing archive destination 1 : E:\ORACLE\MMP\ARCHIVE\ARC91912.001
ARC4: Archive destination 1 made inactive: File close error
ARC4: FAILED, see alert log for details
ARC4: Archival failure destination 1 : 'E:\ORACLE\MMP\ARCHIVE\ARC91912.001'
ARC4: INCOMPLETE, see alert log for details
ARC4: NOTARCHIVED, see alert log for details

Hi,
Iam running on 8.1.5 where i cannt use v$recovery_file_dest command. I have checked alert <sid>.log
Mon Sep 04 14:35:08 2006
Current log# 2 seq# 2101962 mem# 0: C:\ORACLE\MMP\LOG\REDO02.LOG
Current log# 2 seq# 2101962 mem# 1: E:\ORACLE\MMP\LOG\REDO02.LOG
Mon Sep 04 14:35:09 2006
ARC3: received prod
Mon Sep 04 14:35:09 2006
ARC3: Beginning to archive log# 5 seq# 2101961
kcrrga: Warning. Log sequence in archive filename wrapped
to fix length as indicated by %S in LOG_ARCHIVE_FORMAT.
Old log archive with same name might be overwritten.
ARC3: Completed archiving log# 5 seq# 2101961
ARC3: re-scanning for new log files
ARC3: prodding the archiver
Mon Sep 04 14:35:11 2006
ARC4: received prod
Mon Sep 04 14:45:57 2006
LGWR: prodding the archiver
Thread 1 advanced to log sequence 2101963
Mon Sep 04 14:45:57 2006
Current log# 3 seq# 2101963 mem# 0: C:\ORACLE\MMP\LOG\REDO03.LOG
Current log# 3 seq# 2101963 mem# 1: E:\ORACLE\MMP\LOG\REDO03.LOG
Mon Sep 04 14:45:58 2006
ARC0: received prod
Mon Sep 04 14:45:59 2006
ARC0: Beginning to archive log# 2 seq# 2101962
kcrrga: Warning. Log sequence in archive filename wrapped
to fix length as indicated by %S in LOG_ARCHIVE_FORMAT.
Old log archive with same name might be overwritten.
ARC0: Completed archiving log# 2 seq# 2101962
ARC0: re-scanning for new log files

Incomplete Recovery Fails using Full hot backup & Archive logs !!

Hello DBA's !!
I am doing on Recovery scenario where I have taken One full hot backup of my Portal Database (EPR) and Restored it on New Test Server. Also I restored Archive logs from last full hot backup for next 6 days. Also I restored the latest Control file (binary) to their original locations. Now, I started the recovery scenario as follows....
1) Installed Oracle 10.2.0.2 compatible with restored version of oracle.
2) Configured tnsnames.ora, listener.ora, sqlnet.ora with hostname of Test server.
3) Restored all Hot backup files from Tape to Test Server.
4) Restored all archive logs from tape to Test server.
5) Restored Latest Binary Control file from Tape to Test Server.
6) Now, Started recovery using following command from SQL prompt.
SQL> recover database until cancel using backup controlfile;
7) Open database after Recovery Completion using RESETLOGS option.
Now in Above scenario I completed steps upto 5) successfully. But when I execute the step 6) the recovery completes with Warning : Recovery completed but OPEN RESETLOGS may throw error " system file needs more recovery to be consistent " . Please find the following snapshot ....
ORA-00279: change 7001816252 generated at 01/13/2008 12:53:05 needed for thread
1
ORA-00289: suggestion : /oracle/EPR/oraarch/1_9624_601570270.dbf
ORA-00280: change 7001816252 for thread 1 is in sequence #9624
ORA-00278: log file '/oracle/EPR/oraarch/1_9623_601570270.dbf' no longer needed
for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log '/oracle/EPR/oraarch/1_9624_601570270.dbf'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/EPR/sapdata1/system_1/system.data1'
SQL> SQL> SQL> SQL> SQL> SQL> SQL>
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/oracle/EPR/sapdata1/system_1/system.data1'
Let me know What should be the reason behind recovery failure !
Note : I tried to Open the database using Last Full Hot Backup only & not applying any archives. Then Database Opens successfully. It means my Database Installation & Configuration is OK !
Please Let me know why my Incomplete Recovery using Archive logs Goes Fail ?
Atul Patil.

oh you made up a new thread so here again:
there is nothing wrong.
You restored your backup, archives etc.
you started your recovery and oracle applyed all archives but the archive
'/oracle/EPR/oraarch/1_9624_601570270.dbf'
does not exist because it represents your current online redo log file and that is not present.
the recovery process cancels by itself.
the solution is:
restart your recovery process with:
recover database until cancel using backup controlfile
and when oracle suggests you '/oracle/EPR/oraarch/1_9624_601570270.dbf'
type cancel!
now you should be able to open your database with open resetlogs.

ARC0: Failed to archive log# 1 seq# 1361

Hi.
Sat Apr 26 04:00:01 2003
Current log# 2 seq# 1362 mem# 0: /redolog02/TRADEDB1/log/log02_01.ora
Current log# 2 seq# 1362 mem# 1: /redolog01/TRADEDB1/log/log02_02.ora
Sat Apr 26 04:00:01 2003
ARCH: Beginning to archive log# 1 seq# 1361
Sat Apr 26 04:00:01 2003
ARC0: Beginning to archive log# 1 seq# 1361
ARC0: Failed to archive log# 1 seq# 1361
Sat Apr 26 04:00:03 2003
ARCH: Completed archiving log# 1 seq# 1361
these are the last few lines of my DB alert log file.I have scheduled a shell script to backup all the archive log script but whenever the script is running I am getting this error.
Can any one explain me what this means.Looks like archiving is done with out any problem.
I am using "alter system archivelog current" in the script.
regards
Joe

Although this is not a serious problem, it does cause your database to stop briefly. It indicates that you do not have enough redo log groups.
Essentially, Oracle writes redo information to log group 1 until it is full, then switches to log group 2. While lgwr is writing to group 2, arc writes group 1 to the archive log destination. If arc is not finished archiving group 1 before group 2 fills, then it has nowhere to switch to (i.e. group 1 is not available for lgwr to write to yet). In normal operation, when Oracle is managing log switches, you would see an error about unable to switch logs from lgwr. However, by issuing the archivelog current, arc does all the work. Since it is unable to do the log switch required to archive the current log, it generates the failed to archive message, and waits for group 2 to finish archiving.
If this is only a problem when doing the backup, you can probably ignore it. However, if you see log switch errors in normal operation, you should add another logfile group, so there will be more time between switches into any sngle group.
TTFN
John

Failed to archive log

Hi,
I have a database A, in archive log, with standby database. After each switch, I have an error like this :
Mon Aug 9 19:55:56 2004
ARCH: Beginning to archive log# 4 seq# 19877
Mon Aug 9 19:55:56 2004
ARC2: Beginning to archive log# 4 seq# 19877
ARC2: Failed to archive log# 4 seq# 19877
Mon Aug 9 19:55:57 2004
ARCH: Completed archiving log# 4 seq# 19877
I don't understand, because all work fine in my standby database.
Thanks for your lights,
Nicolas.

No need to worry, these errors can be ignored. You have two archiver processes running, the first ARCH processed had already began the archive process, ARCH2 then tried. Not a big deal.
--Paul

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

Validation failed for archived log

Hi,
oracle database version 11.2.0.4
OS centOS 6.5
Recently i have set rman backup scripy on production Database, As we are using dbvisit for standby database for that we have set cron which run in every 10 minutes it generates archive and copy it to standby side,
but sometimes backup failed due to expected archive is not represent at location so i put "crosscheck archivelog all" in script now backup is running fine, But i have analyzed backlog file getting
"validation failed for archived log" the time stamp i have checked validation failed archive is current day and yesterday even though archives are present at the location and CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;
Guys i am worried it shouldn't be a big issue for me,
please suggest what is wrong

This forum is for Berkeley DB high availability. We do not have the expertise to help you with your Oracle database 11.2.0.4 issue. You'll need to submit this question to one of the Oracle database forums to get the help you are looking for.
Paula Bingham

Archived log application to a cold backup fails with ora-00328

I am testing backup and recovery scenario as mentioned in Metalink Doc id:69468.1 where a cold backup of one production server is restored on a separate machine. Some activity, say a table creation in some schema and insertion of rows in it is followed by a few log switches. Next I moved just the archived logs ( newly generated) to the test machine and proceed as follow to recover but log application is failing as below,any help would be appreciated!
SQL> startup mount;
ORACLE instance started.
Total System Global Area 205520896 bytes
Fixed Size 1248116 bytes
Variable Size 71304332 bytes
Database Buffers 130023424 bytes
Redo Buffers 2945024 bytes
Database mounted.
SQL> recover database until cancel using backup controlfile;
ORA-00279: change 581754 generated at 12/21/2007 02:35:04 needed for thread 1
ORA-00289: suggestion :
C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001
ORA-00280: change 581754 for thread 1 is in sequence #1
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
auto
ORA-00328: archived log ends at change 581535, need later change 581754
ORA-00334: archived log:
'C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001'
SQL> recover database until cancel;
ORA-00283: recovery session canceled due to errors
ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
SQL> recover database until cancel using backup controlfile;
ORA-00279: change 581754 generated at 12/21/2007 02:35:04 needed for thread 1
ORA-00289: suggestion :
C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001
ORA-00280: change 581754 for thread 1 is in sequence #1
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
C:\oracle\product\10.2.0\archive\ARC00001_0641874107.001
ORA-00328: archived log ends at change 581535, need later change 581754
ORA-00334: archived log:
'C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001'
SQL> recover database using backup controlfile;
ORA-00279: change 581754 generated at 12/21/2007 02:35:04 needed for thread 1
ORA-00289: suggestion :
C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001
ORA-00280: change 581754 for thread 1 is in sequence #1
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
C:\oracle\product\10.2.0\archive\ARC00001_0641874107.001
ORA-00328: archived log ends at change 581541, need later change 581754
ORA-00334: archived log:
'C:\ORACLE\PRODUCT\10.2.0\ARCHIVE\ARC00001_0641874107.001'
Please Help

The error displayed stated you are required to have an specific sequence:
ORA-00280: change 581754 for thread 1 is in sequence #1
Check the contents of the v$recover_file dynamic view and verify if you really have all required archivelog files.
~ Madrid

Archive Logs NOT APPLIED but transferred

Hi Gurus,
I have configured Primary & Standby databases in same Oracle Home. OS version is OEL 5. Database version is 10.2.0.1. I could get the archive logs in the standby site but they are not getting applied in the standby database. I don't have OLAP installed in my database version. Would this create this issue? However I attached my primary alert log details below for your reference:
Thu Aug 30 23:55:37 2012
Starting ORACLE instance (normal)
Cannot determine all dependent dynamic libraries for /proc/self/exe
Unable to find dynamic library libocr10.so in search paths
RPATH = /ade/aime1_build2101/oracle/has/lib/:/ade/aime1_build2101/oracle/lib/:/ade/aime1_build2101/oracle/has/lib/:
LD_LIBRARY_PATH is not set!
The default library directories are /lib and /usr/lib
Unable to find dynamic library libocrb10.so in search paths
Unable to find dynamic library libocrutl10.so in search paths
Unable to find dynamic library libocrutl10.so in search paths
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
processes = 150
sga_target = 289406976
control_files = /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim/control01.ctl, /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim/control02.ctl, /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim/control03.ctl
db_file_name_convert = /home/oracle/oracle/product/10.2.0/db_1/oradata/newstand, /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim
log_file_name_convert = /home/oracle/oracle/product/10.2.0/db_1/oradata/newstand, /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim, /home/oracle/oracle/product/10.2.0/db_1/flash_recovery_area/NEWSTAND/onlinelog, /home/oracle/oracle/product/10.2.0/db_1/flash_recovery_area/NEWPRIM/onlinelog
db_block_size = 8192
compatible = 10.2.0.1.0
log_archive_config = DG_CONFIG=(newprim,newstand)
log_archive_dest_1 = LOCATION=/home/oracle/oracle/product/10.2.0/db_1/oradata/newprim/arch/
VALID_FOR=(ALL_LOGFILES,ALL_ROLES)
DB_UNIQUE_NAME=newprim
log_archive_dest_2 = SERVICE=newstand LGWR ASYNC VALID_FOR=(online_logfiles,primary_role) DB_UNIQUE_NAME=newstand
log_archive_dest_state_1 = enable
log_archive_dest_state_2 = enable
log_archive_max_processes= 30
log_archive_format = %t_%s_%r.dbf
fal_client = newprim
fal_server = newstand
db_file_multiblock_read_count= 16
db_recovery_file_dest = /home/oracle/oracle/product/10.2.0/db_1/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=newprimXDB)
job_queue_processes = 10
background_dump_dest = /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/bdump
user_dump_dest = /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/udump
core_dump_dest = /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/cdump
audit_file_dest = /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/adump
db_name = newprim
db_unique_name = newprim
open_cursors = 300
pga_aggregate_target = 95420416
PMON started with pid=2, OS id=28091
PSP0 started with pid=3, OS id=28093
MMAN started with pid=4, OS id=28095
DBW0 started with pid=5, OS id=28097
LGWR started with pid=6, OS id=28100
CKPT started with pid=7, OS id=28102
SMON started with pid=8, OS id=28104
RECO started with pid=9, OS id=28106
CJQ0 started with pid=10, OS id=28108
MMON started with pid=11, OS id=28110
MMNL started with pid=12, OS id=28112
Thu Aug 30 23:55:38 2012
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
Thu Aug 30 23:55:38 2012
ALTER DATABASE MOUNT
Thu Aug 30 23:55:42 2012
Setting recovery target incarnation to 2
Thu Aug 30 23:55:43 2012
Successful mount of redo thread 1, with mount id 1090395834
Thu Aug 30 23:55:43 2012
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Thu Aug 30 23:55:43 2012
ALTER DATABASE OPEN
Thu Aug 30 23:55:43 2012
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=16, OS id=28122
ARC1 started with pid=17, OS id=28124
ARC2 started with pid=18, OS id=28126
ARC3 started with pid=19, OS id=28128
ARC4 started with pid=20, OS id=28133
ARC5 started with pid=21, OS id=28135
ARC6 started with pid=22, OS id=28137
ARC7 started with pid=23, OS id=28139
ARC8 started with pid=24, OS id=28141
ARC9 started with pid=25, OS id=28143
ARCa started with pid=26, OS id=28145
ARCb started with pid=27, OS id=28147
ARCc started with pid=28, OS id=28149
ARCd started with pid=29, OS id=28151
ARCe started with pid=30, OS id=28153
ARCf started with pid=31, OS id=28155
ARCg started with pid=32, OS id=28157
ARCh started with pid=33, OS id=28159
ARCi started with pid=34, OS id=28161
ARCj started with pid=35, OS id=28163
ARCk started with pid=36, OS id=28165
ARCl started with pid=37, OS id=28167
ARCm started with pid=38, OS id=28169
ARCn started with pid=39, OS id=28171
ARCo started with pid=40, OS id=28173
ARCp started with pid=41, OS id=28175
ARCq started with pid=42, OS id=28177
ARCr started with pid=43, OS id=28179
ARCs started with pid=44, OS id=28181
Thu Aug 30 23:55:44 2012
ARC0: Archival started
ARC1: Archival started
ARC2: Archival started
ARC3: Archival started
ARC4: Archival started
ARC5: Archival started
ARC6: Archival started
ARC7: Archival started
ARC8: Archival started
ARC9: Archival started
ARCa: Archival started
ARCb: Archival started
ARCc: Archival started
ARCd: Archival started
ARCe: Archival started
ARCf: Archival started
ARCg: Archival started
ARCh: Archival started
ARCi: Archival started
ARCj: Archival started
ARCk: Archival started
ARCl: Archival started
ARCm: Archival started
ARCn: Archival started
ARCo: Archival started
ARCp: Archival started
ARCq: Archival started
ARCr: Archival started
ARCs: Archival started
ARCt: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARCt started with pid=45, OS id=28183
LNS1 started with pid=46, OS id=28185
Thu Aug 30 23:55:48 2012
Thread 1 advanced to log sequence 68
Thu Aug 30 23:55:48 2012
ARCo: Becoming the 'no FAL' ARCH
ARCo: Becoming the 'no SRL' ARCH
Thu Aug 30 23:55:48 2012
ARCp: Becoming the heartbeat ARCH
Thu Aug 30 23:55:48 2012
Thread 1 opened at log sequence 68
Current log# 1 seq# 68 mem# 0: /home/oracle/oracle/product/10.2.0/db_1/oradata/newprim/redo01.log
Successful open of redo thread 1
Thu Aug 30 23:55:48 2012
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Thu Aug 30 23:55:48 2012
SMON: enabling cache recovery
Thu Aug 30 23:55:48 2012
Successfully onlined Undo Tablespace 1.
Thu Aug 30 23:55:48 2012
SMON: enabling tx recovery
Thu Aug 30 23:55:49 2012
Database Characterset is WE8ISO8859P1
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=47, OS id=28205
Thu Aug 30 23:55:49 2012
Error 1034 received logging on to the standby
Thu Aug 30 23:55:49 2012
Errors in file /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/bdump/newprim_arc1_28124.trc:
ORA-01034: ORACLE not available
FAL[server, ARC1]: Error 1034 creating remote archivelog file 'newstand'
FAL[server, ARC1]: FAL archive failed, see trace file.
Thu Aug 30 23:55:49 2012
Errors in file /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/bdump/newprim_arc1_28124.trc:
ORA-16055: FAL request rejected
ARCH: FAL archive failed. Archiver continuing
Thu Aug 30 23:55:49 2012
ORACLE Instance newprim - Archival Error. Archiver continuing.
Thu Aug 30 23:55:49 2012
db_recovery_file_dest_size of 2048 MB is 9.77% 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.
Thu Aug 30 23:55:50 2012
Errors in file /home/oracle/oracle/product/10.2.0/db_1/admin/newprim/udump/newprim_ora_28120.trc:
ORA-00604: error occurred at recursive SQL level 1
ORA-12663: Services required by client not available on the server
ORA-36961: Oracle OLAP is not available.
ORA-06512: at "SYS.OLAPIHISTORYRETENTION", line 1
ORA-06512: at line 15
Thu Aug 30 23:55:50 2012
Completed: ALTER DATABASE OPEN
Thu Aug 30 23:56:33 2012
FAL[server]: Fail to queue the whole FAL gap
GAP - thread 1 sequence 1-33
DBID 1090398314 branch 792689455
Kindly, guide me please..
-Vimal.

CKPT: The trace file details are added below for your reference;
/home/oracle/oracle/product/10.2.0/db_1/admin/newprim/bdump/newprim_arc1_28124.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning and Data Mining options
ORACLE_HOME = /home/oracle/oracle/product/10.2.0/db_1
System name:     Linux
Node name:     localhost.localdomain
Release:     2.6.18-8.el5PAE
Version:     #1 SMP Tue Jun 5 23:39:57 EDT 2007
Machine:     i686
Instance name: newprim
Redo thread mounted by this instance: 1
Oracle process number: 17
Unix process pid: 28124, image: [email protected] (ARC1)
*** SERVICE NAME:() 2012-08-30 23:55:48.314
*** SESSION ID:(155.1) 2012-08-30 23:55:48.314
kcrrwkx: nothing to do (start)
Redo shipping client performing standby login
OCISessionBegin failed -1
.. Detailed OCI error val is 1034 and errmsg is 'ORA-01034: ORACLE not available
*** 2012-08-30 23:55:49.723 60679 kcrr.c
Error 1034 received logging on to the standby
Error 1034 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'newstand'
Error 1034 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'newstand'
ORA-01034: ORACLE not available
*** 2012-08-30 23:55:49.723 58941 kcrr.c
kcrrfail: dest:2 err:1034 force:0 blast:1
kcrrwkx: unknown error:1034
ORA-16055: FAL request rejected
ARCH: Connecting to console port...
ARCH: Connecting to console port...
kcrrwkx: nothing to do (end)
*** 2012-08-31 00:00:43.417
kcrrwkx: nothing to do (start)
*** 2012-08-31 00:05:43.348
kcrrwkx: nothing to do (start)
*** 2012-08-31 00:10:43.280
kcrrwkx: nothing to do (start)
*** 2012-08-31 00:15:43.217
kcrrwkx: nothing to do (start)
*** 2012-08-31 00:20:43.160
kcrrwkx: nothing to do (start)
*** 2012-08-31 00:25:43.092
kcrrwkx: nothing to do (start)
*** 2012-08-31 00:30:43.031
kcrrwkx: nothing to do (start)
*** 2012-08-31 00:35:42.961
kcrrwkx: nothing to do (start)
*** 2012-08-31 00:40:42.890
kcrrwkx: nothing to do (start)
*** 2012-08-31 00:45:42.820
kcrrwkx: nothing to do (start)
*** 2012-08-31 00:50:42.755
kcrrwkx: nothing to do (start)
*** 2012-08-31 00:55:42.686
kcrrwkx: nothing to do (start)
*** 2012-08-31 01:00:42.631
kcrrwkx: nothing to do (start)
*** 2012-08-31 01:05:42.565
kcrrwkx: nothing to do (start)
*** 2012-08-31 01:10:42.496
kcrrwkx: nothing to do (start)
Mahir: Yes I have my 4 standby redo logs!
I created the standby manually without using RMAN.
Hemant: if it asks for even first thread, then obviously it shows nothing is applied on Standby. By the way so it is not called a 'GAP', I think..!
Thanks.

I have one problem with Data Guard. My archive log files are not applied.

I have one problem with Data Guard. My archive log files are not applied. However I have received all archive log files to my physical Standby db
I have created a Physical Standby database on Oracle 10gR2 (Windows XP professional). Primary database is on another computer.
In Enterprise Manager on Primary database it looks ok. I get the following message Data Guard status Normal
But as I wrote above the archive log files are not applied
After I created the Physical Standby database, I have also done:
1. I connected to the Physical Standby database instance.
CONNECT SYS/SYS@luda AS SYSDBA
2. I started the Oracle instance at the Physical Standby database without mounting the database.
STARTUP NOMOUNT PFILE=C:\oracle\product\10.2.0\db_1\database\initluda.ora
3. I mounted the Physical Standby database:
ALTER DATABASE MOUNT STANDBY DATABASE
4. I started redo apply on Physical Standby database
alter database recover managed standby database disconnect from session
5. I switched the log files on Physical Standby database
alter system switch logfile
6. I verified the redo data was received and archived on Physical Standby database
select sequence#, first_time, next_time from v$archived_log order by sequence#
SEQUENCE# FIRST_TIME NEXT_TIME
3 2006-06-27 2006-06-27
4 2006-06-27 2006-06-27
5 2006-06-27 2006-06-27
6 2006-06-27 2006-06-27
7 2006-06-27 2006-06-27
8 2006-06-27 2006-06-27
7. I verified the archived redo log files were applied on Physical Standby database
select sequence#,applied from v$archived_log;
SEQUENCE# APP
4 NO
3 NO
5 NO
6 NO
7 NO
8 NO
8. on Physical Standby database
select * from v$archive_gap;
No rows
9. on Physical Standby database
SELECT MESSAGE FROM V$DATAGUARD_STATUS;
MESSAGE
ARC0: Archival started
ARC1: Archival started
ARC2: Archival started
ARC3: Archival started
ARC4: Archival started
ARC5: Archival started
ARC6: Archival started
ARC7: Archival started
ARC8: Archival started
ARC9: Archival started
ARCa: Archival started
ARCb: Archival started
ARCc: Archival started
ARCd: Archival started
ARCe: Archival started
ARCf: Archival started
ARCg: Archival started
ARCh: Archival started
ARCi: Archival started
ARCj: Archival started
ARCk: Archival started
ARCl: Archival started
ARCm: Archival started
ARCn: Archival started
ARCo: Archival started
ARCp: Archival started
ARCq: Archival started
ARCr: Archival started
ARCs: Archival started
ARCt: Archival started
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
ARC1: Becoming the heartbeat ARCH
Attempt to start background Managed Standby Recovery process
MRP0: Background Managed Standby Recovery process started
Managed Standby Recovery not using Real Time Apply
MRP0: Background Media Recovery terminated with error 1110
MRP0: Background Media Recovery process shutdown
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[1]: Assigned to RFS process 2148
RFS[1]: Identified database type as 'physical standby'
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[2]: Assigned to RFS process 2384
RFS[2]: Identified database type as 'physical standby'
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[3]: Assigned to RFS process 3188
RFS[3]: Identified database type as 'physical standby'
Primary database is in MAXIMUM PERFORMANCE mode
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles created
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[4]: Assigned to RFS process 3168
RFS[4]: Identified database type as 'physical standby'
RFS[4]: No standby redo logfiles created
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: No standby redo logfiles created
10. on Physical Standby database
SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
RFS IDLE 0 0 0 0
RFS IDLE 0 0 0 0
RFS IDLE 1 9 13664 2
RFS IDLE 0 0 0 0
10) on Primary database:
select message from v$dataguard_status;
MESSAGE
ARC0: Archival started
ARC1: Archival started
ARC2: Archival started
ARC3: Archival started
ARC4: Archival started
ARC5: Archival started
ARC6: Archival started
ARC7: Archival started
ARC8: Archival started
ARC9: Archival started
ARCa: Archival started
ARCb: Archival started
ARCc: Archival started
ARCd: Archival started
ARCe: Archival started
ARCf: Archival started
ARCg: Archival started
ARCh: Archival started
ARCi: Archival started
ARCj: Archival started
ARCk: Archival started
ARCl: Archival started
ARCm: Archival started
ARCn: Archival started
ARCo: Archival started
ARCp: Archival started
ARCq: Archival started
ARCr: Archival started
ARCs: Archival started
ARCt: Archival started
ARCm: Becoming the 'no FAL' ARCH
ARCm: Becoming the 'no SRL' ARCH
ARCd: Becoming the heartbeat ARCH
Error 1034 received logging on to the standby
Error 1034 received logging on to the standby
LGWR: Error 1034 creating archivelog file 'luda'
LNS: Failed to archive log 3 thread 1 sequence 7 (1034)
FAL[server, ARCh]: Error 1034 creating remote archivelog file 'luda'
11)on primary db
select name,sequence#,applied from v$archived_log;
NAME SEQUENCE# APP
C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00003_0594204176.001 3 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00004_0594204176.001 4 NO
Luda 4 NO
Luda 3 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00005_0594204176.001 5 NO
Luda 5 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00006_0594204176.001 6 NO
Luda 6 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00007_0594204176.001 7 NO
Luda 7 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\IRINA\ARC00008_0594204176.001 8 NO
Luda 8 NO
12) on standby db
select name,sequence#,applied from v$archived_log;
NAME SEQUENCE# APP
C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00004_0594204176.001 4 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00003_0594204176.001 3 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00005_0594204176.001 5 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00006_0594204176.001 6 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00007_0594204176.001 7 NO
C:\ORACLE\PRODUCT\10.2.0\ORADATA\LUDA\ARC00008_0594204176.001 8 NO
13) my init.ora files
On standby db
irina.__db_cache_size=79691776
irina.__java_pool_size=4194304
irina.__large_pool_size=4194304
irina.__shared_pool_size=75497472
irina.__streams_pool_size=0
*.audit_file_dest='C:\oracle\product\10.2.0\admin\luda\adump'
*.background_dump_dest='C:\oracle\product\10.2.0\admin\luda\bdump'
*.compatible='10.2.0.1.0'
*.control_files='C:\oracle\product\10.2.0\oradata\luda\luda.ctl'
*.core_dump_dest='C:\oracle\product\10.2.0\admin\luda\cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_file_name_convert='luda','irina'
*.db_name='irina'
*.db_unique_name='luda'
*.db_recovery_file_dest='C:\oracle\product\10.2.0\flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.dispatchers='(PROTOCOL=TCP) (SERVICE=irinaXDB)'
*.fal_client='luda'
*.fal_server='irina'
*.job_queue_processes=10
*.log_archive_config='DG_CONFIG=(irina,luda)'
*.log_archive_dest_1='LOCATION=C:/oracle/product/10.2.0/oradata/luda/ VALID_FOR=(ALL_LOGFILES, ALL_ROLES) DB_UNIQUE_NAME=luda'
*.log_archive_dest_2='SERVICE=irina LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=irina'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_max_processes=30
*.log_file_name_convert='C:/oracle/product/10.2.0/oradata/irina/','C:/oracle/product/10.2.0/oradata/luda/'
*.open_cursors=300
*.pga_aggregate_target=16777216
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=167772160
*.standby_file_management='AUTO'
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='C:\oracle\product\10.2.0\admin\luda\udump'
On primary db
irina.__db_cache_size=79691776
irina.__java_pool_size=4194304
irina.__large_pool_size=4194304
irina.__shared_pool_size=75497472
irina.__streams_pool_size=0
*.audit_file_dest='C:\oracle\product\10.2.0/admin/irina/adump'
*.background_dump_dest='C:\oracle\product\10.2.0/admin/irina/bdump'
*.compatible='10.2.0.1.0'
*.control_files='C:\oracle\product\10.2.0\oradata\irina\control01.ctl','C:\oracle\product\10.2.0\oradata\irina\control02.ctl','C:\oracle\product\10.2.0\oradata\irina\control03.ctl'
*.core_dump_dest='C:\oracle\product\10.2.0/admin/irina/cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_file_name_convert='luda','irina'
*.db_name='irina'
*.db_recovery_file_dest='C:\oracle\product\10.2.0/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.dispatchers='(PROTOCOL=TCP) (SERVICE=irinaXDB)'
*.fal_client='irina'
*.fal_server='luda'
*.job_queue_processes=10
*.log_archive_config='DG_CONFIG=(irina,luda)'
*.log_archive_dest_1='LOCATION=C:/oracle/product/10.2.0/oradata/irina/ VALID_FOR=(ALL_LOGFILES, ALL_ROLES) DB_UNIQUE_NAME=irina'
*.log_archive_dest_2='SERVICE=luda LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=luda'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_max_processes=30
*.log_file_name_convert='C:/oracle/product/10.2.0/oradata/luda/','C:/oracle/product/10.2.0/oradata/irina/'
*.open_cursors=300
*.pga_aggregate_target=16777216
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=167772160
*.standby_file_management='AUTO'
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='C:\oracle\product\10.2.0/admin/irina/udump'
Please help me!!!!

Hi,
After several tries my redo logs are applied now. I think in my case it had to do with the tnsnames.ora. At this moment I have both database in both tnsnames.ora files using the SID and not the SERVICE_NAME.
Now I want to use DGMGRL. Adding a configuration and a stand-by database is working fine, but when I try to enable the configuration DGMGRL gives no feedback and it looks like it is hanging. The log, although says that it succeeded.
In another session 'show configuration' results in the following, confirming that the enable succeeded.
DGMGRL> show configuration
Configuration
Name: avhtest
Enabled: YES
Protection Mode: MaxPerformance
Fast-Start Failover: DISABLED
Databases:
avhtest - Primary database
avhtestls53 - Physical standby database
Current status for "avhtest":
Warning: ORA-16610: command 'ENABLE CONFIGURATION' in progress
It there anybody that experienced the same problem and/or knows the solution to this?
With kind regards,
Martin Schaap

Recovery question using archive log

HPUX 11X
Oracle 10.2.0.2
I have a standby database that the customers want to test the ability to fail over. They also want to test the data integrity of the standby once it's brought on line as the primary.
I've already told the customer that any writes that they do on the standby during the test time WILL be lost. I plan on doing a incomplete recovery back to a specific sequence number / archive log when the tests are complete.
My plan is to take note of the current sequence number just before I bring the standby live. When all is said and done, I was going to do a recover back to the sequence number one PRIOR to that one. Then when I place the db back in standby mode, it will sync back up to the primary.
What I need to know is if this is a good or a bad idea. Should I plan on doing it differently and for what reason.
Thanks! :)

Use flashback database to recover the former primary database to a new standby.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/scenarios.htm#i1049997
Therefore the changes made on standby won't be lost (unless you want to lose them).
If your databases do not have Flashback Database feature enabled, you can use incomplete recovery instead.
I think Flashback Database should be your first option.

Recover database from archive log: Time based recovery

Hi,
Could you pelase help regarding the following:
I have power outage in my machine running oracle 9i on Solaris OS 9
Oracle is mounted but failed to open
Once it is started showing the error message
SQL> startup;
ORACLE instance started.
Total System Global Area 9457089744 bytes
Fixed Size 744656 bytes
Variable Size 3154116608 bytes
Database Buffers 6291456000 bytes
Redo Buffers 10772480 bytes
Database mounted.
ORA-01113: file 4 needs media recovery
ORA-01110: data file 4: '/opt/oracle/oradata/sysdb/indx/indx01.dbf'
So I tried to recover the database
SQL> recover database;
ORA-00279: change 1652948240 generated at 12/03/2007 13:09:08 needed for thread
1
ORA-00289: suggestion : /opt/oracle/oradata/nobilldb/archive/1_183942.dbf
ORA-00280: change 1652948240 for thread 1 is in sequence #183942
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 1652948816 generated at 12/03/2007 13:09:19 needed for thread
1
ORA-00289: suggestion : /opt/oracle/oradata/nobilldb/archive/1_183943.dbf
ORA-00280: change 1652948816 for thread 1 is in sequence #183943
ORA-00278: log file '/opt/oracle/oradata/nobilldb/archive/1_183942.dbf' no
longer needed for this recovery
The power outage at 16:00pm and the recovery archive log file '/opt/oracle/oradata/nobilldb/archive/1_183942.dbf' at 11 am
Always I am applying the next sequence it is giving the same message and asking the next sequence. I have more than 900 archive log from 11am to 4pm and each of them having the size of 100mb and it take 1 minute to get back from each to provide this error message.
How I can start my recovery from say 15:45 onwards until 16:15?
I have all archive logs in the proper destination.
Still my database is not opened and it is starts applying archive log since 5 hours back, please help me regarding this
Thanks in advance

Wrong forum. Post your question in the following forum:
General Database Discussions

Problem in Archive log sync with Passive Node to Standby

Hi,
I have configured Active-Passive Oracle Database using Fail Safe between Active and Passive Node. Also successfully configured Data Guard between Active Node to Standby Node.
Versions:
1. Oracle Database Version: Oracle 11g R2
2. Oracle Fail Safe: 3.4.2
3. OS: Windows Server 2008 R2
Problem:
Now after fail over the database to Passive node, to check whether the DR is functioning or not, archive logs are not transferring to Standby node. In the Passive Node aler log file error is showing:
"ORA-01031: insufficient privileges
PING[ARC2]: heartbeat failed to connect to standby órcldr´. Error is 1031
Could anyone please let me know the possible reason for this and the resolution.

Hello;
I'm thinking password file. It needs to be the same copy on all instances.
Did you copy and rename it as needed?
And you need to restart using the correct copy of the password file too.
So a Standby for example must startup on the correct copy of the password file or you will still get the error.
Best Regards
mseberg
Edited by: mseberg on Nov 14, 2012 9:46 AM

Archive logs are not transferred to STDBY database

Hi,
I have create a STDBY database (I am running the release 9.2.0.7.0).
I see that the archivelogs are not correctly transferred into STDBY server.
From Primary alert log, I see the following error:
ARC1: Evaluating archive log 1 thread 1 sequence 16734
ARC1: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2
ARC1: Destination LOG_ARCHIVE_DEST_2 archival not expedited
ARC1: Beginning to archive log 1 thread 1 sequence 16734
Creating archive destination LOG_ARCHIVE_DEST_1: '/backup/archivelogs/log1_16734.arc'
ARC1: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2
Invoking non-expedited destination LOG_ARCHIVE_DEST_2 thread 1 sequence 16734 host STDBY_PROD
ARC1: Completed archiving log 1 thread 1 sequence 16734
Thu Nov 17 14:54:42 2011
Errors in file /mnt/orclEBS/oracle/proddb/9.2.0/admin/PROD_ebslive/bdump/prod_arc0_5277.trc:
ORA-03114: not connected to ORACLE
Thu Nov 17 14:54:42 2011
ARC0: FAL archive failed, see trace file.
ARCH: FAL archive failed. Archiver continuing
Thu Nov 17 14:54:42 2011
ORACLE Instance PROD - Archival Error. Archiver continuing.
ARCH: Connecting to console port...
Thu Nov 17 14:54:42 2011
ORA-16055: FAL request rejected
ARCH: Connecting to console port...
Thu Nov 17 14:54:42 2011
Errors in file /mnt/orclEBS/oracle/proddb/9.2.0/admin/PROD_ebslive/bdump/prod_arc0_5277.trc:
ORA-16055: FAL request rejected
ARC0: Begin FAL archive (thread 1 sequence 16483 destination STDBY_PROD)
Creating archive destination LOG_ARCHIVE_DEST_2: 'STDBY_PROD'
Thu Nov 17 15:05:44 2011
LGWR: I/O error 3114 archiving log 2 to 'STDBY_PROD'
Thu Nov 17 15:05:44 2011
Errors in file /mnt/orclEBS/oracle/proddb/9.2.0/admin/PROD_ebslive/bdump/prod_lgwr_5265.trc:
ORA-03114: not connected to ORACLE
Thu Nov 17 15:10:08 2011
Errors in file /mnt/orclEBS/oracle/proddb/9.2.0/admin/PROD_ebslive/bdump/prod_arc0_5277.trc:
ORA-03114: not connected to ORACLE
Thu Nov 17 15:10:08 2011
ARC0: FAL archive failed, see trace file.
ARCH: FAL archive failed. Archiver continuing
Thu Nov 17 15:10:08 2011
ORACLE Instance PROD - Archival Error. Archiver continuing.
ARCH: Connecting to console port...
Thu Nov 17 15:10:08 2011
ORA-16055: FAL request rejected
ARCH: Connecting to console port...
Thu Nov 17 15:10:08 2011
Errors in file /mnt/orclEBS/oracle/proddb/9.2.0/admin/PROD_ebslive/bdump/prod_arc0_5277.trc:
ORA-16055: FAL request rejected
I see that both archiving destinations are VALID:
SQL> select dest_id, dest_name, status from v$archive_dest_status where status != 'INACTIVE';
DEST_ID ---------- DEST_NAME -------------------------------------------------------------------------------- STATUS
1 LOG_ARCHIVE_DEST_1 VALID
2 LOG_ARCHIVE_DEST_2 VALID
SQL>
TNSPING works properly in both directions, e.g. from PROD -> STDBY:
$tnsping STDBY_PROD
TNS Ping Utility for Linux: Version 9.2.0.7.0 - Production on 17-NOV-2011 16:56:40
Copyright (c) 1997 Oracle Corporation. All rights reserved.
Used parameter files:
/mnt/orclEBS/oracle/proddb/9.2.0/network/admin/PROD_ebslive/sqlnet_ifile.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION= (ADDRESS=(PROTOCOL=tcp) (HOST=EBSSTDBY) (PORT=1521)) (CONNECT_DATA=(SID=PROD)))
OK (10 msec)
Please help me to solve this issue.
Thank you.

A few notes :
Troubleshooting Tips For Dataguard Switchover (9i and 10gR1) [ID 298986.1]
Although it is about Switchover, it does mandate a password file exclusive. If the switchover requires the password file, shouldn't ARCH shipping require it ?
Step By Step Guide To Create Physical Standby Database Using RMAN [ID 469493.1]
also covers 9i with specific mentions of 9i differences from 10g. Passwordfile is not mentioned as different in 9i from 10g.
Data Guard 9i - Net8 Configuration for a 2-node database environment. [ID 175122.1
has log_archive_dest_2='SERVICE=NODE2STDBY.ACME.COM' so it connects to the service
*However* the document "Introduction to Oracle 9i Data Guard Manager" from
Data Guard 9i Introduction to Data Guard Manager GUI [ID 150217.1]
page 59 has this : "The creation process will attempt to create a remote login password file for the standby database to
enable remote connections to the database. (Note: A remote login password file is not necessary for
Data Guard operation; it is only needed to allow remote connections to the database from clients,
such as other Enterprise Manager tools.)"
Similarly the section "3.2.6 Set Initialization Parameters on a Physical Standby Database"
in the 9i DataGuard manual at http://download.oracle.com/docs/cd/B10501_01/server.920/a96653/create_ps.htm#62941
only has
remote_archive_enable=TRUE
(this is an instance parameter)
Similarly the section "5.8.2.1 Primary Database Initialization Parameters"
at http://download.oracle.com/docs/cd/B10501_01/server.920/a96653/log_transport.htm#1067609
explains
The last parameter, REMOTE_ARCHIVE_ENABLE=SEND, allows the primary database to send redo data to the standby database, but prevents the primary database from receiving redo data from another system.
with REMOTE_ARCHIVE_ENABLE=RECEIVE on the Standby
to Receive and archive the incoming redo data from the primary database, but only while the database is running in the standby role
So, I guess that REMOTE_ARCHIVE_ENABLE is the important one. Not REMOTE_LOGIN_PASSWORDFILE.
In 9i : http://download.oracle.com/docs/cd/B10501_01/server.920/a96536/ch1174.htm#1023087
In 10g it is deprecated : http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams176.htm#sthref541 so that LOG_ARCHIVE_CONFIG is used.
(and no longer appears in the 11.2 Reference)
Hemant K Chitale

Archive log fail

Similar Messages

Maybe you are looking for