Standby database unable to fetch missing archive sequence from primary

Hi,
My primary oracle db version is 10.2.0.5 which is n Windows 2003 server 32 bit in file system
My standby database version is 10.2.0.5 which in wondows 2008 server in ASM instance.
some of the archivelogs are not fetching by standby database from primary db.because of that recovery is not happening and it waits for missing archive logs but its not transfering on satndby database.
I tried many time by doing manuall..manuall its hapening but again sometimes its stucks and waits for next missing archivelog.
standby alert log mesage
Sun Jul 08 21:33:13 Pacific Daylight Time 2012
FAL[client]: Failed to request gap sequence
GAP - thread 1 sequence 128945-128945
DBID 4176230406 branch 617106566
FAL[client]: All defined FAL servers have been attempted.
Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
parameter is defined to a value that is sufficiently large
enough to maintain adequate log switch information to resolve
archivelog gaps.
Sun Jul 08 21:44:03 Pacific Daylight Time 2012
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.
trace file of standby
Dump file d:\oracle\admin\mks01p\bdump\mks01p_mrp0_6628.trc
Sun Jul 08 21:30:23 2012
ORACLE V10.2.0.5.0 - 64bit Production vsnsta=0
vsnsql=14 vsnxtr=3
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production
With the Oracle Label Security, OLAP, Data Mining and Real Application Testing options
Windows NT Version V6.1 Service Pack 1
CPU : 8 - type 8664, 4 Physical Cores
Process Affinity : 0x0000000000000000
Memory (Avail/Total): Ph:37019M/49108M, Ph+PgF:87277M/103214M
Instance name: mks01p
Redo thread mounted by this instance: 1
Oracle process number: 19
Windows thread id: 6628, image: ORACLE.EXE (MRP0)
*** SERVICE NAME:() 2012-07-08 21:30:23.422
*** SESSION ID:(95.1) 2012-07-08 21:30:23.422
*** 2012-07-08 21:30:23.422 64949 kcrr.c
MRP0: Background Managed Standby Recovery process started
*** 2012-07-08 21:30:28.445 1170 krsm.c
Managed Recovery: Initialization posted.
*** 2012-07-08 21:30:28.445 64949 kcrr.c
Managed Standby Recovery not using Real Time Apply
*** 2012-07-08 21:30:39.833
Recovery target incarnation = 1, activation ID = -118713082
Influx buffer limit = 10000 min(50% x 191963, 10000)
Successfully allocated 7 recovery slaves
Using 158 overflow buffers per recovery slave
Start recovery at thread 1 ckpt scn 7982577982885 logseq 128945 block 2
*** 2012-07-08 21:30:40.784
Media Recovery add redo thread 1
*** 2012-07-08 21:30:40.784 1170 krsm.c
Managed Recovery: Active posted.
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '+ORAREDO3/mks01p/mks01p_redo01b.rdo'
ORA-17503: ksfdopn:2 Failed to open file +ORAREDO3/mks01p/mks01p_redo01b.rdo
ORA-15001: diskgroup "ORAREDO3" does not exist or is not mounted
ORA-15001: diskgroup "ORAREDO3" does not exist or is not mounted
ORA-00312: online log 1 thread 1: '+ORAREDO1/mks01p/mks01p_redo01a.rdo'
ORA-17503: ksfdopn:2 Failed to open file +ORAREDO1/mks01p/mks01p_redo01a.rdo
ORA-15001: diskgroup "ORAREDO1" does not exist or is not mounted
ORA-15001: diskgroup "ORAREDO1" does not exist or is not mounted
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '+ORAREDO3/mks01p/mks01p_redo01b.rdo'
ORA-17503: ksfdopn:2 Failed to open file +ORAREDO3/mks01p/mks01p_redo01b.rdo
ORA-15001: diskgroup "ORAREDO3" does not exist or is not mounted
ORA-15001: diskgroup "ORAREDO3" does not exist or is not mounted
ORA-00312: online log 1 thread 1: '+ORAREDO1/mks01p/mks01p_redo01a.rdo'
ORA-17503: ksfdopn:2 Failed to open file +ORAREDO1/mks01p/mks01p_redo01a.rdo
ORA-15001: diskgroup "ORAREDO1" does not exist or is not mounted
ORA-15001: diskgroup "ORAREDO1" does not exist or is not mounted
*** 2012-07-08 21:30:40.940 64949 kcrr.c
Clearing online redo logfile 1 +ORAREDO1/mks01p/mks01p_redo01a.rdo
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '+ORAREDO3/mks01p/mks01p_redo01b.rdo'
ORA-17503: ksfdopn:2 Failed to open file +ORAREDO3/mks01p/mks01p_redo01b.rdo
ORA-15001: diskgroup "ORAREDO3" does not exist or is not mounted
ORA-15001: diskgroup "ORAREDO3" does not exist or is not mounted
ORA-00312: online log 1 thread 1: '+ORAREDO1/mks01p/mks01p_redo01a.rdo'
ORA-17503: ksfdopn:2 Failed to open file +ORAREDO1/mks01p/mks01p_redo01a.rdo
ORA-15001: diskgroup "ORAREDO1" does not exist or is not mounted
ORA-15001: diskgroup "ORAREDO1" does not exist or is not mounted
ORA-00349: failure obtaining block size for '+ORAREDO1/mks01p/mks01p_redo01a.rdo'
ORA-15001: diskgroup "ORAREDO1" does not exist or is not mounted
Error 349 creating/clearing online redo logfile 1
*** 2012-07-08 21:30:40.987 64949 kcrr.c
Clearing online redo logfile 1 complete
*** 2012-07-08 21:30:41.034 64949 kcrr.c
Media Recovery Waiting for thread 1 sequence 128945
*** 2012-07-08 21:30:41.050 64949 kcrr.c
Fetching gap sequence in thread 1, gap sequence 128945-128945
Redo shipping client performing standby login
OCISessionBegin failed -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
*** 2012-07-08 21:30:41.533 64949 kcrr.c
Error 1031 received logging on to the standby
*** 2012-07-08 21:30:41.533 64949 kcrr.c
FAL[client, MRP0]: Error 1031 connecting to MKS01P_PRD for fetching gap sequence
ORA-01031: insufficient privileges
*** 2012-07-08 21:31:11.610
Redo shipping client performing standby login
OCISessionBegin failed -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
*** 2012-07-08 21:31:12.094 64949 kcrr.c
Error 1031 received logging on to the standby
*** 2012-07-08 21:31:12.094 64949 kcrr.c
FAL[client, MRP0]: Error 1031 connecting to MKS01P_PRD for fetching gap sequence
ORA-01031: insufficient privileges
*** 2012-07-08 21:31:42.186
Redo shipping client performing standby login
OCISessionBegin failed -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
*** 2012-07-08 21:31:42.654 64949 kcrr.c
Error 1031 received logging on to the standby
*** 2012-07-08 21:31:42.670 64949 kcrr.c
FAL[client, MRP0]: Error 1031 connecting to MKS01P_PRD for fetching gap sequence
ORA-01031: insufficient privileges
*** 2012-07-08 21:32:12.747
Redo shipping client performing standby login
OCISessionBegin failed -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
*** 2012-07-08 21:32:13.215 64949 kcrr.c
Error 1031 received logging on to the standby
*** 2012-07-08 21:32:13.230 64949 kcrr.c
FAL[client, MRP0]: Error 1031 connecting to MKS01P_PRD for fetching gap sequence
ORA-01031: insufficient privileges
*** 2012-07-08 21:32:43.276
Redo shipping client performing standby login
OCISessionBegin failed -1
.. Detailed OCI error val is 1031 and errmsg is 'ORA-01031: insufficient privileges
*** 2012-07-08 21:32:43.759 64949 kcrr.c
Error 1031 received logging on to the standby
*** 2012-07-08 21:32:43.775 64949 kcrr.c
FAL[client, MRP0]: Error 1031 connecting to MKS01P_PRD for fetching gap sequence
ORA-01031: insufficient privileges
*** 2012-07-08 21:33:13.821
Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
parameter is defined to a value that is sufficiently large
enough to maintain adequate log switch information to resolve
archivelog gaps.
i created new password fle on bith primary and standby database also.
Please help me to resolve this issue.

ORA-15001: diskgroup "ORAREDO3" does not exist or is not mounted
ORA-15001: diskgroup "ORAREDO3" does not exist or is not mountedhave you mentioned parameter LOG_FILE_NAME_CONVERT in standby when online redo log locations are different?
post from standby:-
SQL> select name, state From v$asm_diskgroup;
FAL[client, MRP0]: Error 1031 connecting to MKS01P_PRD for fetching gap sequence
ORA-01031: insufficient privilegesPost from primary & standby
SQL> select * from v$pwfile_users;
User Profile for 919131
919131
Handle:     919131
Status Level:     Newbie
Registered:     Mar 6, 2012
Total Posts:     16
Total Questions:     8 (8 unresolved)
OTN failed 100% to help you, then why you posted another question?
First close all your old answered threads and then better continue your updates in your thread.
Edited by: CKPT on Jul 9, 2012 11:45 AM

Similar Messages

Creating Standby Database / Steps might be missing..

I have created standby database..
The archives are copied except one archived log and those copied archived are not applied at Standby database.
Besides this issue, I just checked the alert log file and pasting its contents here.
Do check it and let me know If I m missing any paramter[s].
Dump file c:\oracle\product\10.2.0\admin\rockstd\bdump\alert_rockstd.log
Mon May 12 15:23:42 2008
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows XP Version V5.1 Service Pack 2
CPU : 2 - type 586
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:1194M/2038M, Ph+PgF:1368M/2641M, VA:1940M/2047M
Mon May 12 15:23:42 2008
Starting ORACLE instance (normal)
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 = 167772160
control_files = C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\ROCKSTD.CTL
db_block_size = 8192
compatible = 10.2.0.1.0
log_archive_dest_1 = location=C:\oracle\product\10.2.0\oradata\rockstd\Archive_rock
log_archive_dest_state_1 = ENABLE
log_archive_format = arc_%s_%t_%r.arc
fal_client = ROCKSTD
fal_server = ROCK
db_file_multiblock_read_count= 16
db_recovery_file_dest = C:\oracle\product\10.2.0\flash_recovery_area\rockstd
db_recovery_file_dest_size= 2147483648
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=rockXDB)
job_queue_processes = 10
audit_file_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ROCKSTD\ADUMP
background_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ROCKSTD\BDUMP
user_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ROCKSTD\UDUMP
core_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ROCKSTD\CDUMP
db_name = rock
db_unique_name = rockstd
open_cursors = 300
pga_aggregate_target = 16777216
PMON started with pid=2, OS id=3656
PSP0 started with pid=3, OS id=504
MMAN started with pid=4, OS id=2544
DBW0 started with pid=5, OS id=3652
LGWR started with pid=6, OS id=552
CKPT started with pid=7, OS id=2688
SMON started with pid=8, OS id=3436
RECO started with pid=9, OS id=3696
CJQ0 started with pid=10, OS id=1636
MMON started with pid=11, OS id=2072
MMNL started with pid=12, OS id=3812
Mon May 12 15:23:43 2008
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
Mon May 12 15:24:06 2008
alter database mount standby database
Mon May 12 15:24:11 2008
Setting recovery target incarnation to 14
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=16, OS id=3536
Mon May 12 15:24:11 2008
ARC0: Archival started
ARC1 started with pid=17, OS id=4084
Mon May 12 15:24:12 2008
ARC1: Archival started
ARCH: STARTING ARCH PROCESSES COMPLETE
Mon May 12 15:24:12 2008
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
ARC1: Thread not mounted
Mon May 12 15:24:12 2008
Successful mount of redo thread 1, with mount id 3275426006
Mon May 12 15:24:12 2008
Physical Standby Database mounted.
Mon May 12 15:24:13 2008
ARC0: Becoming the heartbeat ARCH
Completed: alter database mount standby database
Mon May 12 15:25:02 2008
Using STANDBY_ARCHIVE_DEST parameter default value as C:\oracle\product\10.2.0\oradata\rockstd\Archive_rock
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[1]: Assigned to RFS process 3444
RFS[1]: Identified database type as 'physical standby'
Mon May 12 15:25:02 2008
RFS LogMiner: Client disabled from further notification
Mon May 12 15:25:21 2008
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 May 12 15:26:19 2008
alter database add standby logfile 'C:\oracle\product\10.2.0\oradata\rockstd\redo04.log' size 50m
Mon May 12 15:26:20 2008
Completed: alter database add standby logfile 'C:\oracle\product\10.2.0\oradata\rockstd\redo04.log' size 50m
Mon May 12 15:26:27 2008
alter database add standby logfile 'C:\oracle\product\10.2.0\oradata\rockstd\redo05.log' size 50m
Completed: alter database add standby logfile 'C:\oracle\product\10.2.0\oradata\rockstd\redo05.log' size 50m
Mon May 12 15:26:33 2008
alter database add standby logfile 'C:\oracle\product\10.2.0\oradata\rockstd\redo06.log' size 50m
Mon May 12 15:26:34 2008
Completed: alter database add standby logfile 'C:\oracle\product\10.2.0\oradata\rockstd\redo06.log' size 50m
Mon May 12 15:27:20 2008
alter database recover managed standby database disconnect from session
MRP0 started with pid=19, OS id=596
Managed Standby Recovery not using Real Time Apply
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_dbw0_3652.trc:
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_dbw0_3652.trc:
ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
ORA-01110: data file 2: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\UNDOTBS01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_dbw0_3652.trc:
ORA-01157: cannot identify/lock data file 3 - see DBWR trace file
ORA-01110: data file 3: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSAUX01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_dbw0_3652.trc:
ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
ORA-01110: data file 4: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\TESTING1.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_dbw0_3652.trc:
ORA-01157: cannot identify/lock data file 5 - see DBWR trace file
ORA-01110: data file 5: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM03.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_dbw0_3652.trc:
ORA-01157: cannot identify/lock data file 6 - see DBWR trace file
ORA-01110: data file 6: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\ABAMCO_TEST01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
MRP0: Background Media Recovery terminated with error 1110
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_mrp0_596.trc:
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM01.DBF'
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM01.DBF'
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_mrp0_596.trc:
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM01.DBF'
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM01.DBF'
Mon May 12 15:27:27 2008
Completed: alter database recover managed standby database disconnect from session
Mon May 12 15:30:18 2008
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[2]: Assigned to RFS process 2456
RFS[2]: Identified database type as 'physical standby'
Primary database is in MAXIMUM PERFORMANCE mode
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Mon May 12 15:30:22 2008
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[3]: Assigned to RFS process 3124
RFS[3]: Identified database type as 'physical standby'
RFS[3]: Successfully opened standby log 5: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO05.LOG'
Mon May 12 15:53:45 2008
RFS[3]: Successfully opened standby log 5: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO05.LOG'
Mon May 12 15:53:46 2008
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Mon May 12 15:53:58 2008
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Mon May 12 16:00:06 2008
RFS[3]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Mon May 12 16:00:09 2008
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Mon May 12 16:00:14 2008
RFS[3]: Successfully opened standby log 5: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO05.LOG'
Mon May 12 16:00:18 2008
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Regards,
Rakesh Soni.

Done, I've given the same path in Standby Database [datafiles, controlfiles] as it has been given in the Primary Database.
MoreOver, I m manually switching logfiles at primary database [alter system switch logfile] they are copied and applied sucessfully at standby database. But the archived files that I have copied with cold backup are not applied yet. Infact they are not retrieved executing the below query.
select name, applied from v$archived_log;
How can I apply those archived logs? [archives that copied with cold backup]
Regards.

Archiving Error. from Primary & Standby Server. pls help.

Hi all.
Im currently getting error messages from both of my Primary and Standby Database. can anyone help me identify what error message would it be?
Primary Database:
Tue Apr 21 09:40:13 2009
Creating archive destination LOG_ARCHIVE_DEST_2: 'Standby'
ARC0: FAL archive, error 20 creating remote archivelog file 'Standby'
Tue Apr 21 09:40:14 2009
Errors in file /export/oradata/log/bdump/arc0_20901.trc:
ORA-00020: maximum number of processes () exceeded
ARC0: FAL archive failed, see trace file.
ARCH: FAL archive failed. Archiver continuing
Tue Apr 21 09:40:14 2009
ORACLE Instance - Archival Error. Archiver continuing.
ARCH: Connecting to console port...
Tue Apr 21 09:40:14 2009
ORA-16055: FAL request rejected
ARCH: Connecting to console port...
Tue Apr 21 09:40:14 2009
Errors in file /export/oradata/log/bdump/arc0_20901.trc:
ORA-16055: FAL request rejected
Tue Apr 21 09:40:40 2009
Thread 1 advanced to log sequence 41971
Current log# 1 seq# 41971 mem# 0: /export/oradata/logfile/redoMIBS01a.log
Current log# 1 seq# 41971 mem# 1: /export/oradata/logfile/redoMIBS01b.log
Tue Apr 21 09:40:40 2009
ARC1: Evaluating archive log 4 thread 1 sequence 41970
ARC1: Beginning to archive log 4 thread 1 sequence 41970
Creating archive destination LOG_ARCHIVE_DEST_1: '/export/oradata/MIBS/archive/log00010001S0000041970.ARC'
ARC1: Completed archiving log 4 thread 1 sequence 41970
Tue Apr 21 09:41:40 2009
Errors in file /export/oradata/log/bdump/arc0_20901.trc:
ORA-00020: maximum number of processes () exceeded
Standby Database:
Tue Apr 21 09:36:10 2009
RFS: Possible network disconnect with primary database
Closing latent archivelog for thread 1 sequence 41687
EOF located at block 40958 low SCN 0:123821645 next SCN 0:123821645
Latent archivelog '/opt/app/oracle/product/9.2.0/dbs/archlog00010001S0000041687.ARC'
If you wish to failover to this standby database, you should use the
following command to manually register the archivelog for recovery:
ALTER DATABASE REGISTER LOGFILE '/opt/app/oracle/product/9.2.0/dbs/archlog00010001S0000041687.ARC';
Tue Apr 21 09:36:10 2009
Errors in file /export/oradata/log/udump/mibs_rfs_3802.trc:
ORA-00367: checksum error in log file header
ORA-00311: cannot read header from archived log
ORA-00334: archived log: '/opt/app/oracle/product/9.2.0/dbs/archlog00010001S0000041687.ARC'
ORA-27091: skgfqio: unable to queue I/O
ORA-27072: skgfdisp: I/O error
SVR4 Error: 22: Invalid argument
Additional information: 1
Tue Apr 21 09:36:19 2009
RFS: Possible network disconnect with primary database
Closing latent archivelog for thread 1 sequence 41688
EOF located at block 2677 low SCN 0:123821835 next SCN 0:123821835
Latent archivelog '/opt/app/oracle/product/9.2.0/dbs/archlog00010001S0000041688.ARC'
If you wish to failover to this standby database, you should use the
following command to manually register the archivelog for recovery:
ALTER DATABASE REGISTER LOGFILE '/opt/app/oracle/product/9.2.0/dbs/archlog00010001S0000041688.ARC';
Tue Apr 21 09:36:19 2009
Errors in file /export/oradata/MIBS/log/udump/mibs_rfs_3807.trc:
ORA-00367: checksum error in log file header
ORA-00311: cannot read header from archived log
ORA-00334: archived log: '/opt/app/oracle/product/9.2.0/dbs/archlog00010001S0000041688.ARC'
ORA-27091: skgfqio: unable to queue I/O
ORA-27072: skgfdisp: I/O error
SVR4 Error: 2: No such file or directory
Additional information: 1
Really2 needing anyone's help at this point.

Hi..
Errors in file /export/oradata/log/bdump/arc0_20901.trc:ORA-00020: maximum number of processes () exceeded>
What is the value of the parameter PROCESSES.You need to increase the value which would require bouncing the database.Increaing the Processes parameter requires increase in session parameter too.
Sessions = (1.1 * PROCESSES) + 5
[http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams169.htm]
[http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams191.htm]
HTH
Anand

Data Guard archive deleted from Primary datbase before transfaring Standby

Dear all
I have a physical standby database. And Primary database on RAC node 1 and node 2.
Accidently archive log deleted from Primary db before shipped standby db .
I saw this error which is showing the GAP.
FAL[client]: Failed to request gap sequence
GAP - thread 1 sequence 1_7090 1_7090
ir
Edited by: user8244545 on Jun 7, 2010 11:33 AM
Edited by: user8244545 on Jun 7, 2010 6:47 PM

Well, I feel sorry for you after all these guys gave you such a hard time :^)
You should be using at least an RMAN Archive Log deletion policy to manage your archive log files.
See "Deletion Policy for Archived Redo Log Files In Flash Recovery Areas" at http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rman.htm#SBYDB00750 and http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rman.htm#i1031870 for 10gR2. 10g does require you use a Flash Recovery Area (FRA, renamed to Fast Recovery Area) . Read the paper at http://www.oracle.com/technology/deploy/availability/pdf/RMAN_DataGuard_10g_wp.pdf to sort out not having to use MANDATORY (which we do not recommend).
Now, if you are at 11g (R1 or R2) you don't even have to be using the FRA nor mandatory to have it work. See http://www.oracle.com/pls/db111/to_URL?remark=ranked&urlname=http:%2F%2Fdownload.oracle.com%2Fdocs%2Fcd%2FB28359_01%2Fbackup.111%2Fb28270%2Frcmconfb.htm%23BRADV89439.
If you do not use RMAN to backup the archive logs at least these deletion policy will prevent this from happening again since you will no longer be deleting archive logs manually.
Now, it may be too late for this, I am behind in my mail, but you could get the standby past this gap by using an incremental backup of the primary from the last SCN that was applied at the standby. See the manual at http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/scenarios.htm#CIHIAADC for more information.
Larry

Unable to fetch 50,000 records from SQL using Orchestrator

Hi Team,
I have a table in MS SQL which is having more than 50,000 records. I am trying to fetch 50,000 records using orchestrator, but unable to fetch the records..
There is no problem with the SQL query because I can able to get 40,000 records..
I am using SCORCH DEV - SQL Integration Pack.
Regards,
Soundarajan.

Hi,
Thanks for your query.
I have also used timeout parameter but it is not working.. As you said I also tried with Query database Activity which is out of the box...
Now i can able to fetch more than 80,000 records but the output what i am getting is not in the format which we are looking for..
Attached the output...
How to edit this..?
I tried to write the output in excel but all the data sits in the first column itself..
Regards,
Soundarajan.

Archive Deleted from primary database

Dear Experts
I have configured physical standby database on oracle 9.2.0.1
an archive has been deleted from primary database. and it is not applied on standby database.
How can I synch my standby database with primary database?
please help me out
thanks

Do not need configure rman. Try this.This mean is you will get all changes from primary database without logs(archivelogs becuse you loss these) then apply these to stand by.This is a best way.First change SCN from Standby database then do these.
You can get SCN from standby as
select min (checkpoint_change#) from v$datafile_header

Standby database not working after reinstallation of oracle in primary DB

Hello All,
Initially I had setup primary database (DB1) and Standby database (DB2), for test environment.
In DB1 I had got ORA-600 error. So, after I researched, I came to know that I need to apply some patches. But I reinstalled oracle in DB1. And the problem was solved in DB1.
After that, I issued the following commands in DB2, but I got error
SQL>SHUTDOWN IMMEDIATE;
ORA-01034: Oracle not available
ORA-27101: shared memory realm does not exist
SQL>STARTUP MOUNT;
ORA-27102: out of memoryNow, I mean to say, both DB1 and DB2 are independent.
Also, DB2 is not active since 2 months
DB1 is working fine.
Please guide me with procedure, how to configure DB2 for the current DB1

Hello;
After two months I would rebuild.
If you are on Oracle 11 you can use RMAN to do this quickly.
Here's a few short notes :
http://www.visi.com/~mseberg/duprman2.html
http://www.visi.com/~mseberg/standby_creation_from_active_database_using_rman.html
Can you post your full oracle version and Primary database size?
If you rebuild I would remove all the data files from the Standby, recopy the password file from the Primary to the Standby and double my tnsnames.ora and listener.ora on both servers.
Best Regards
mseberg

Mail deleted a current inbox and restored an old deleted inbox. It won't restore from Time Machine, and I'm missing archived emails from the old account. I'm pretty sure there is other stuff missing, but it's hard to tell. Any ideas why it would do this?

Our Mac was working fine last Monday, then Tuesday morning one of our current inboxes was gone, and an old, archived inbox was restored--twice. Other than some trouble-shooting on Tuesday, we've pretty much left things alone as we were busy doing other stuff.
I tried restoring the files from Time Machine, but it didn't work. I followed plisk restore instructions--nothing. It's a mess. We have no idea what would have caused this. We're above average users--we weren't mucking about with anything. It was just so strange.
I went back into Time Machine, and it just makes no sense that I can't restore anything. We're now missing important emails--nothing too tragic, but still a pain in the butt. Thankfully the current inbox that was somehow deleted had a back-up on our email server, but the archived/deleted inbox file that was magically restored had all the archived emails that we kept deleted.
Any ideas would be wonderful.
Thanks!

Hello,
Could be many things, we should start with this...
"Try Disk Utility
1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu at top of the screen. (In Mac OS X 10.4 or later, you must select your language first.)
*Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
3. Click the First Aid tab.
4. Select your Mac OS X volume.
5. Click Repair Disk, (not Repair Permissions). Disk Utility checks and repairs the disk."
http://docs.info.apple.com/article.html?artnum=106214
Then try a Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
(Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.)
If perchance you can't find your install Disc, at least try it from the Safe Boot part onward.
If 10.7.0 or later...
Bootup holding CMD+r, or the Option/alt key to boot from the Restore partition & use Disk Utility from there to Repair the Disk.

Unable to delete archive logs from primary

Dear DBAs,
I made the necessary configuration in RMAN at both site (primary and physical standby) as below:
on primary:
configure archivelog deletion policy to applied on standby;
alter system set "_log_deletion_policy"=ALL scope=spfile;
log_archive_dest_10=LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=ora10cs1
log_archive-dest_1=service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)
(HOST=LBLX-ORA10-SCS1)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=ora10scs1_XPT)(INSTANCE_NAME=ora10cs1)(SERVER=dedicated)))",
ARCH SYNC NOAFFIRM delay=0 OPTIONAL max_failure=0 max_connections=1 reopen=300 db_unique_name="ora10scs1" register net_timeout=180 valid_for=
(online_logfile,primary_role)
at standby:
configure archivelog deletion policy to none;
By the way i'm using Oracle 10gR2 patch4 on RHEL 5
and till now the database won't delete the archivelogs automaticaly, since the current available size in the flash folder is only 2MB.
Please waiting your advice
Thx in advance

Hi,
I have a different issue, I am not sure i can combine on the same thread.
From the DOC, this command is appeared to be useful. I am not sure if it can be applied to my environment.
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY
We have some databases with DG configuration on Sun. We take the backups only primary using RMAN online & archivelog alternate days. But, the archivelogs on standby are to be deleted every day manually (i mean we have a script scheduled for it).
Note: We use "delete input" on primary backup every day after they are backedup by RMAN. Anyway, the logs that are not applied on standby will not be deleted as RMAN is intelligent to keep them safe.
In the past we attempted to delete using rman script with the command shown below.
delete archivelog all completed before 'sysdate-2/24';
This causes a problem every time for us with regard to the primary database Backup as it expects the archivelogs on primay which were deleted by RMAN on standby. We had to crosscheck archivelog all every time to resolve the issue. There seems to be a mismatch of the archlog status both on primary and standby.
Please let me know if the above configuration command "CONFIGURE ARCHIVELOG DELETION POLICY " on both primary and standby or give an idea/steps what way i can use this.
Regards,
Vasu.
Edited by: vasu77 on Aug 31, 2009 4:02 PM
Edited by: vasu77 on Aug 31, 2009 4:05 PM
Edited by: vasu77 on Aug 31, 2009 4:10 PM

Unable to open TestStand 2 sequence from TestStand 3

I have a sequence file built in TestStand 2 that I am unable to open from TestStand 3. I first receive some type conflict prompts, then the following error.
Invalid adapter name: 'Labview'.
The sequence file 'filename' cannot be loaded.
Error code -17336, Invalid adapter name.
Source 'TSAPI'.
Does anyone have any ideas as to what may be causing this or how work around it?

Kevin -
The adapter name in TestStand 2.x for LabVIEW is "G Std Prototype Adapter". If you look in most TestStand 2.x files you should see lines like this:
Adapter = "G Std Prototype Adapter"
Based on your error I assume that if you look in your TS 2.x file you will see:
Adapter = "Labview"
I am not sure how the adapter name was set like this. If the text is "Labview", then you should be able to backup your current TS 2.x file, edit in NOTEPAD the value of the text in quotes for the Adapter setting.
If the text is not "Labview", can you please post the sequence file?
Note that TestStand 3.0 files no longer store this adapter setting in the same way, so you no longer see this line in TestStand 3.0 files.
Scott Richardson
Scott Richardson
National Instruments

Unable to fetch requisition lines data from package POR_CUSTOM_PKG.CUSTOM_VALIDATE_REQ_DIST

Problem Description
We need to validate the Distribution data and based on that we will throw Error with respective Line Number. But the line number is not in the parameter list of this procedure POR_CUSTOM_PKG.CUSTOM_VALIDATE_REQ_DIST. So we thought of deriving the Line Number by querying the table po_requisition_lines_all by passing the parent_req_line_id. But unfortunately the query is throwing no data found exception though the related line records are seen from the backend.
Request your help to fetch the requisition line number from this procedure POR_CUSTOM_PKG.CUSTOM_VALIDATE_REQ_DIST
Thanks & Regards,
Munish Mittal

Hi,
This is just for the information that the issue is resolved for me by using the below code.
begin
select parent_req_line_id into l_line_id_1 from dual;
select requisition_line_id, line_num into l_line_id, l_line_num
from po_requisition_lines_all
where requisition_line_id = l_line_id_1;
exception when others then
null;
end;

Recover standby database

Our primary linux 10g db is in standard edition and we would like to manually create a standby database
After copying the control and datafiles from primary to standby database, started the standby instance ..
SQL> startup nomount pfile=/path/to/pfile/initSID.standby
SQL> alter database mount standby database;
SQL> recover standby database;
ORA-00279: change 2342934 generated at 8/27/2009 21:10:35 needed for thread 1
ORA-00289: suggestion : /opt/oracle/arch/SID/1_833_682861383.arc
ORA-00280: change 2342934 for thread 1 is in sequence #833
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
AUTO
ORA-00308: cannot open archived log
'/opt/oracle/arch/SID/1_833_682861383.arc'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01195: online backup of file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/opt/oracle/oradata/SID/system01.dbf'
How do I resolve this problem? Log sequence 833 is the current log on the primary db, archive log haven't been written yet. When I try to "alter database open read only" on the standby db, I get an error "ORA-01156: recovery in progress may need access to file".
I then went back to my primary database, which already had another log switch to 834, log 833 is now available, I then moved that archive log file to the standby db. Try to recover standby database again, but still got errors..
SQL> startup nomount pfile=/path/to/pfile/initSID.standby
SQL> alter database mount standby database;
SQL> recover standby database;
ORA-00279: change 2342934 generated at 8/27/2009 21:10:35 needed for thread 1
ORA-00289: suggestion : /opt/oracle/arch/SID/1_833_682861383.arc
ORA-00280: change 2342934 for thread 1 is in sequence #833
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
AUTO
ORA-00317: file type 0 in header is not log file
ORA-00334: archived log: '/opt/oracle/arch/SID/1_833_682861383.arc'
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01195: online backup of file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/opt/oracle/oradata/SID/system01.dbf'
SQL> alter database open read only;
ERROR at line 1:
ORA-16004: backup database requires recovery
ORA-01195: online backup of file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/opt/oracle/oradata/SID/system01.dbf'
Would something please explain this to me? What am I doing wrong? Thanks in advance.

I copied the missing archive log over to standby db, still got the same error.
1) SQL> recover standby database;
ORA-00279: change 2342934 generated at 8/27/2009 21:10:35 needed for thread 1
ORA-00289: suggestion : /opt/oracle/arch/SID/1_833_682861383.arc
ORA-00280: change 2342934 for thread 1 is in sequence #833
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
AUTO
ORA-00317: file type 0 in header is not log file
ORA-00334: archived log: '/opt/oracle/arch/SID/1_833_682861383.arc'
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01195: online backup of file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/opt/oracle/oradata/SID/system01.dbf'
I also tried..
2) SQL> recover standby database using backup controlfile until cancel;
ORA-00279: change 2342934 generated at 8/27/2009 21:10:35 needed for thread 1
ORA-00289: suggestion : /opt/oracle/arch/SID/1_833_682861383.arc
ORA-00280: change 2342934 for thread 1 is in sequence #833
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
AUTO
ORA-00317: file type 0 in header is not log file
ORA-00334: archived log: '/opt/oracle/arch/SID/1_833_682861383.arc'
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01195: online backup of file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/opt/oracle/oradata/SID/system01.dbf'
Edited by: user10427867 on Aug 28, 2009 5:56 AM

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;
}

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

Archives are not transorting to standby database

Hi Experts,
DB version: 10.2.0.4
OS Version: Windows 2003
Here i have one issue, unable to transfer the archives from Primary to standby database.
I have no errors found in primary and also in standby database, I can able to ping both primary & standby database from both locations, I unable to trace the issue,
Take as high importance.Can any one help. Appriciated for your help.
Completed: alter database recover managed standby database cancel
Fri Jan 28 22:36:49 2011
alter database recover managed standby database disconnect from session
MRP0 started with pid=24, OS id=2164
Managed Standby Recovery not using Real Time ApplyMedia Recovery Waiting for thread 1 sequence 84857
Fri Jan 28 22:36:55 2011
Completed: alter database recover managed standby database disconnect from session

Post the values of the following parameters from your standby database: fal_client and fal_server, SQL> show parameter falNAME TYPE VALUE
fal_client string STBY
fal_server string SYS
also post the last 100 lines from the alert log of your production database.
Thread 1 advanced to log sequence 84895
Current log# 1 seq# 84895 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYS\REDO01.LOG
Current log# 1 seq# 84895 mem# 1: F:\ORA_DATA\REDO01A.LOG
Fri Jan 28 22:00:10 2011
Thread 1 advanced to log sequence 84896
Current log# 3 seq# 84896 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYS\REDO03.LOG
Current log# 3 seq# 84896 mem# 1: F:\ORA_DATA\REDO03A.LOG
Thread 1 advanced to log sequence 84897
Current log# 2 seq# 84897 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYS\REDO02.LOG
Current log# 2 seq# 84897 mem# 1: F:\ORA_DATA\REDO02A.LOG
Fri Jan 28 22:00:34 2011
Thread 1 advanced to log sequence 84898
Current log# 1 seq# 84898 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYS\REDO01.LOG
Current log# 1 seq# 84898 mem# 1: F:\ORA_DATA\REDO01A.LOG
Fri Jan 28 22:02:13 2011
Thread 1 advanced to log sequence 84899
Current log# 3 seq# 84899 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYS\REDO03.LOG
Current log# 3 seq# 84899 mem# 1: F:\ORA_DATA\REDO03A.LOG
Fri Jan 28 23:37:21 2011
ALTER SYSTEM SET log_archive_dest_state_2='enable' SCOPE=BOTH;
Fri Jan 28 23:46:36 2011
ALTER SYSTEM SET log_archive_max_processes=12 SCOPE=BOTH;
Sat Jan 29 00:01:32 2011
alter database add standby logfile thread 1
group 4 size 50m,
group 5 size 50m
Sat Jan 29 00:01:35 2011
Starting control autobackup
Sat Jan 29 00:01:39 2011
Errors in file e:\oracle\product\10.2.0\admin\sys\udump\sys_ora_5056.trc:
Sat Jan 29 00:01:39 2011
Errors in file e:\oracle\product\10.2.0\admin\sys\udump\sys_ora_5056.trc:
Sat Jan 29 00:01:39 2011
Errors in file e:\oracle\product\10.2.0\admin\sys\udump\sys_ora_5056.trc:
Control autobackup written to DISK device
handle 'J:\ORACLE\RECO\SYS\AUTOBACKUP\2011_01_29\O1_MF_S_741657695_6N77SKJM_.BKP'
Sat Jan 29 00:09:32 2011
Thread 1 advanced to log sequence 84900
Current log# 2 seq# 84900 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYS\REDO02.LOG
Current log# 2 seq# 84900 mem# 1: F:\ORA_DATA\REDO02A.LOG
Sat Jan 29 00:10:04 2011
Thread 1 advanced to log sequence 84901
Current log# 1 seq# 84901 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYS\REDO01.LOG
Current log# 1 seq# 84901 mem# 1: F:\ORA_DATA\REDO01A.LOG
Thread 1 cannot allocate new log, sequence 84902
Checkpoint not complete
Current log# 1 seq# 84901 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYS\REDO01.LOG
Current log# 1 seq# 84901 mem# 1: F:\ORA_DATA\REDO01A.LOG
Thread 1 advanced to log sequence 84902
Current log# 3 seq# 84902 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYS\REDO03.LOG
Current log# 3 seq# 84902 mem# 1: F:\ORA_DATA\REDO03A.LOG
Thread 1 cannot allocate new log, sequence 84903
Checkpoint not complete
Current log# 3 seq# 84902 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYS\REDO03.LOG
Current log# 3 seq# 84902 mem# 1: F:\ORA_DATA\REDO03A.LOG
Sat Jan 29 00:10:18 2011
Thread 1 advanced to log sequence 84903
Current log# 2 seq# 84903 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYS\REDO02.LOG
Current log# 2 seq# 84903 mem# 1: F:\ORA_DATA\REDO02A.LOG
Thread 1 advanced to log sequence 84904
Current log# 1 seq# 84904 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYS\REDO01.LOG
Current log# 1 seq# 84904 mem# 1: F:\ORA_DATA\REDO01A.LOG
Thread 1 cannot allocate new log, sequence 84905
Checkpoint not complete
Current log# 1 seq# 84904 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYS\REDO01.LOG
Current log# 1 seq# 84904 mem# 1: F:\ORA_DATA\REDO01A.LOG
Thread 1 advanced to log sequence 84905
Current log# 3 seq# 84905 mem# 0: E:\ORACLE\PRODUCT\10.2.0\ORADATA\SYS\REDO03.LOG
Current log# 3 seq# 84905 mem# 1: F:\ORA_DATA\REDO03A.LOG

Standby database unable to fetch missing archive sequence from primary

Similar Messages

Maybe you are looking for