Standby Database Archives

I have created a standby database in 10g using Data Guard. I ran a query to check that the logs are being applied and I get a perplexing result. It looks as if my logs are getting sent to the DB twice. Any ideas as to what may be causing this?
The result from the query is below.
Jim
SEQUENCE#     FIRST_TIME     NEXT_TIME     APPLIED
3206     9/18/2006 9:38:33 AM     9/18/2006 9:53:35 AM     NO
3206     9/18/2006 9:38:33 AM     9/18/2006 9:53:35 AM     YES
3205     9/18/2006 9:23:28 AM     9/18/2006 9:38:33 AM     NO
3205     9/18/2006 9:23:28 AM     9/18/2006 9:38:33 AM     YES
3204     9/18/2006 9:08:23 AM     9/18/2006 9:23:28 AM     NO
3204     9/18/2006 9:08:23 AM     9/18/2006 9:23:28 AM     YES
3203     9/18/2006 8:53:18 AM     9/18/2006 9:08:23 AM     NO
3203     9/18/2006 8:53:18 AM     9/18/2006 9:08:23 AM     YES
3202     9/18/2006 8:38:13 AM     9/18/2006 8:53:18 AM     NO
3202     9/18/2006 8:38:13 AM     9/18/2006 8:53:18 AM     YES
3201     9/18/2006 8:23:08 AM     9/18/2006 8:38:13 AM     NO
3201     9/18/2006 8:23:08 AM     9/18/2006 8:38:13 AM     YES
3200     9/18/2006 8:08:03 AM     9/18/2006 8:23:08 AM     NO
3200     9/18/2006 8:08:03 AM     9/18/2006 8:23:08 AM     YES

Nevermind please. I was running the query on the Primary DB and I was seeing the createion and transmittal of the logs from the Primary to the Standby. My mistake.
Jim

Similar Messages

Standby database archive log apply in production server.

Dear All,
How I apply standby database archive log apply in production server.
Please help me.
Thanks,
Manas

How can i use standby database as primary for that 48 hour ?Perform a switchover (role transitions).
First check if the standby is in sync with the primary database.
Primary database:
sql>select max(sequence#) from v$archived_log; ---> Value AStandby database:
sql>select max(sequence#) from v$archived_log where applied='YES'; -----> Value BCheck if Value B is same as Value A.
If the standby is in sycn with the primary database, then perform the switchover operation (refer the below link)
http://www.articles.freemegazone.com/oracle-switchover-physical-standby-database.php
http://docs.oracle.com/cd/B19306_01/server.102/b14230/sofo.htm
http://www.oracle-base.com/articles/9i/DataGuard.php#DatabaseSwitchover
manas
Handle: manas
Email: [email protected]
Status Level: Newbie
Registered: Jan 24, 2012
Total Posts: 10
Total Questions: 3 (3 unresolved)
Name Manas
Location kolkata Mark your questions as answered if you feel that you have got better answers rather than building up a heap of unanswered questions.

Standby Database (Archive Log Mode)

I'm going to be setting up a standby database.
I understand that the primary database must be in archive log mode.
Is there any reason for the standby database to be in archivelog mode?

Since your primary Db is in archive log mode, so will be your standby, when it is made primary.But. you can use STANDBY REDO LOGS from 9i version, where these Standby Redo Logs then store the information received from the Primary Database.
As per metalink:-
>
Standby Redo Logs are only supported for the Physical Standby Database in Oracle 9i and as well for Logical Standby Databases in 10g. Standby Redo Logs are only used if you have the LGWR activated for archival to the Remote Standby Database.If you have Standby Redo Logs, the RFS process will write into the Standby RedoLog as mentioned above and when a log switch occurs, the Archiver Process of the Standby Database will archive this Standby Redo Log to an Archived Redo Log, while the MRP process applies the information to the Standby Database. In a Failover situation, you will also have access to the information already written in the Standby Redo Logs, so the information will not be lost.
>
Check metalink Doc ID: Note:219344.1
Regards,
Anand

Standby database Archive log destination confusion

Hi All,
I need your help here..
This is the first time that this situation is arising. We had sync issues in the oracle 10g standby database prior to this archive log destination confusion.So we rebuilt the standby to overcome this sync issue. But ever since then the archive logs in the standby database are moving to two different locations.
The spfile entries are provided below:
*.log_archive_dest_1='LOCATION=/m99/oradata/MARDB/archive/'
*.standby_archive_dest='/m99/oradata/MARDB/standby'
Prior to rebuilding the standby databases the archive logs were moving to /m99/oradata/MARDB/archive/ location which is the correct location. But now the archive logs are moving to both /m99/oradata/MARDB/archive/ and /m99/oradata/MARDB/standby location, with the majority of them moving to /m99/oradata/MARDB/standby location. This is pretty unusual.
The archives in the production are moving to /m99/oradata/MARDB/archive/ location itself.
Could you kindly help me overcome this issue.
Regards,
Dan

Hi Anurag,
Thank you for update.
Prior to rebuilding the standby database the standby_archive_dest was set as it is. No modifications were made to the archive destination locations.
The primary and standby databases are on different servers and dataguard is used to transfer the files.
I wanted to highlight one more point here, The archive locations are similar to the ones i mentioned for the other stndby databases. But the archive logs are moving only to /archive location and not to the /standby location.

(V7.3) STANDBY DATABASE IN ORACLE 7.3

제품 : ORACLE SERVER
작성날짜 : 2004-08-13
SCOPE
Standard Edition 에서는 standby, data guard 기능은 지원하지 않으며, 이 기능을 대체하는 Oracle Fail Safe 는 Oracle 8.1.6 이상 부터 지원이 됩니다.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Standby database에 대하여
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1. 오라클 7.3 버젼에 추가된 new feature 로서 archive log mode 상태에서
online tablespace backup이 필요없는 새로운 backup/recovery 방법이다.
즉, archive log mode에서도 각 tablespace의 주기적인 online backup이
필요하였고, 이 작업에 따라 회복시간이 좌우되었다. Standby database를 잘 유지
하여줄 수 있는 환경이라면, online tablespace backup 대신 유용하게 사용될 수
있다.
2. 회복 시간은 작업량과 standby database에 archive log file이 어느 정도
반영되었느냐에 따라 다르다.
3. OPS와의 비교
instance를 두개 이상 사용하는 Oracle Parallel Server와 비교하는 것보다
위의 1번에서 소개한 환경과 비교하는 것이 더 적절하다.
4. 생성 방법
4.1 create the standby database
; standby db의 생성
1) back up the datafiles
2) startup mount;
alter database create standby controlfile as 'filename';
3) alter system archive log current;
4) transfer backup-datafile, archived log files, standby controlfile
to the safe place for standby database.
4.2 maintain the standby database
; log file을 standby db에 적용시켜 최신의 데이타로 유지함.
1) startup nomount;
2) alter database mount standby database;
3) recover standby database ;
4.3 activate the standby database
; primary database가 정상적으로 startup할 수 없을 때
1) alter database activate standby database;
!!! 일단 standby database를 기동시켰으면, 이전의 stand by database
상태로 되돌릴 수 없으니 신중하게 사용하여야 함.

I haven't done a Snapshot Standby (RAC or non-RAC). But I see no reason why it shouldn't work with a RAC Standby either.
The command is a Database level command, not an Instance level command.
Hemant K Chitale

How to check data in physical standby database?

Hi!
I'm maintaining physical standby database system. everyday, i must check tranfer and apply progress. I known, it operate very good. No archive gap is found.
But i want to check data in physical standby database that there is consistant with primary database, there isn't? What method do I use? How to do?
thankS

I hope the following will help
Verifying the Physical Standby Database
==========================================
Once you create the physical standby database and set up log transport services, you may want verify that database modifications are being successfully shipped from the primary database to the standby database.
To see the new archived redo logs that were received on the standby database, you should first identify the existing archived redo logs on the standby database, archive a few logs on the primary database, and then check the standby database again. The following steps show how to perform these tasks.
Step 1 Identify the existing archived redo logs.
On the standby database, query the V$ARCHIVED_LOG view to identify existing archived redo logs. For example:
SQL> SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME
2 FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
SEQUENCE# FIRST_TIME NEXT_TIME
8 11-JUL-02 17:50:45 11-JUL-02 17:50:53
9 11-JUL-02 17:50:53 11-JUL-02 17:50:58
10 11-JUL-02 17:50:58 11-JUL-02 17:51:03
3 rows selected.
Step 2 Archiving the current log.
On the primary database, archive the current log using the following SQL statement:
SQL> ALTER SYSTEM ARCHIVE LOG CURRENT;
Step 3 Verify that the new archived redo log was received.
On the standby database, query the V$ARCHIVED_LOG view to verify the redo log was received:
SQL> SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME
2> FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
SEQUENCE# FIRST_TIME NEXT_TIME
8 11-JUL-02 17:50:45 11-JUL-02 17:50:53
9 11-JUL-02 17:50:53 11-JUL-02 17:50:58
10 11-JUL-02 17:50:58 11-JUL-02 17:51:03
11 11-JUL-02 17:51:03 11-JUL-02 18:34:11
4 rows selected.
The logs are now available for log apply services to apply redo data to the standby database.
Step 4 Verify that the new archived redo log was applied.
On the standby database, query the V$ARCHIVED_LOG view to verify the archived redo log was applied.
SQL> SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
2 ORDER BY SEQUENCE#;
SEQUENCE# APP
8 YES
9 YES
10 YES
11 YES
4 rows selected.

GG on Physical Standby database

Hi All,
Could anyone please let me know whether we can create extract of physical standby database Archive logs? This is oracle 9i physical standby database and I want to configure the primary extracts on standby database instead of primary production database. Also please consider that this standby database is always in recovery mode in mount stage. Is this possible?
Thanks in Advance.
Raghav

Run a test by creating an extract that creates an ASCII file. It's simple, you don't need to have a replicat or data pump. If you can read the ORLs of the standby, you'll pick up the statements from the redo apply. The problem, though, is that the physical standby is mounted, so any connections/queries requiring access to fixed tables is going to fail. Also, what DBLOGIN can be used to add trandata for a table?

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

Changing the archive destination in standby database?

My DB is running on Oracle 9.2.0.6.0. I have data guard for my primary database.
Now i wanted to change the archive destination only standby database. What is the process? Any response or any link is appreicated. Thanks

The standby database wouldn't generate archivelogs until and unless it is opened (eg in a failover). So, although there is a definition for the log archive destination in the standby's init.ora / spfile, it is used only to read archivelogs shipped from the primary.
If you are talking of the destination that the primary's archivelogs are shipped to on the standby, technically once the archivelogs are applied on the standby, they are not required and can be deleted. You would be able to configure this.

How to monitor the successful archive log shipment to the standby database

Hello,
From the primary database, which data dictionary do I view to get information whether the standby database has received and processed the archive logs from the primary database. Both databases are 11202 on linux. Another question, which views on the primary database contain a flag sent by the standby database to the primary database to let the primary database knows that the standby database is up and functional? My purpose is to query the primary database for infomation that tell me the standby database is alive and functioning. I want to only query the primary database for these information about the standby database. Thank you in advance.

watson2011 wrote:
Hello,
From the primary database, which data dictionary do I view to get information whether the standby database has received and processed the archive logs from the primary database. Both databases are 11202 on linux. Another question, which views on the primary database contain a flag sent by the standby database to the primary database to let the primary database knows that the standby database is up and functional? My purpose is to query the primary database for infomation that tell me the standby database is alive and functioning. I want to only query the primary database for these information about the standby database. Thank you in advance.You can troubleshoot standby by views as
v$managed_standby (standby)
v$dataguard_status
v$dataguard_stats
Some of the new views are introduced from 11g, check below link too
http://docs.oracle.com/cd/B28359_01/server.111/b28294/views.htm#i79129

Online Redolog Archiving on Logical Standby Databases!!

Hi,
Can I safely stop archiving on logical standby database? It has been inherited from primary database at the time of creation, but I don't see any reason why to keep it enabled while it's consuming unnecessary disk space on our server!!
Any body can give a valid reason to keep it enabled??
Thanks

hi
u dont need archiving on standby database as standby database reads archive files that come from primary database.its simply wastage of resource.stand by database was created from primary by taking a full backup.and to apply the archive files in case of failure u need atleast 1 backup of stand by database .and i assume u wont go for taking backup of standby database.
just worry about the archives of primary database.
kanchan
OCP ( 9i,10g)

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

Archive apply issue for standby database in Standard Edition.

We have setup standby database in Oracle standard edition. the archive log cannot be send by oracle automatically. So we manually send the archive over. But do not see the database apply the archive log file. What could be wrong and where should we check on it?
We also used following when finishing the standby DB after running "recover standby database;" for a few archive log file:
alter database recover managed standby database disconnect from session;
======================================================================================
This is the status:
SQL> select OPEN_MODE, SWITCHOVER# ,REMOTE_ARCHIVE ,ARCHIVELOG_CHANGE#,SWITCHOVER_STATUS, DATABASE_ROLE from v$database;
OPEN_MODE SWITCHOVER# REMOTE_A ARCHIVELOG_CHANGE# SWITCHOVER_STATUS DATABASE_ROLE
MOUNTED 495550636 ENABLED 1.2201E+13 SESSIONS ACTIVE PHYSICAL STANDBY

The DB version is 10.2.0.5
I can do this to apply at standby DB:
SQL> set autorecovery on
SQL> recover standby database;
Then I tried to run this to leave the session:
alter database recover managed standby database disconnect from session;
Do not seen any apply.
=============================
Here is the last lines of alert log:
Errors in file /oracle/admin/cntus/bdump/cntus_mrp0_12389.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u03/cntus/redolog/redo01b.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 1 thread 1: '/u02/cntus/redolog/redo01a.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
Thu Sep 06 15:08:34 EDT 2012
Errors in file /oracle/admin/cntus/bdump/cntus_mrp0_12389.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u03/cntus/redolog/redo01b.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 1 thread 1: '/u02/cntus/redolog/redo01a.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
Clearing online redo logfile 1 /u02/cntus/redolog/redo01a.log
Clearing online log 1 of thread 1 sequence number 10158
Thu Sep 06 15:08:34 EDT 2012
Errors in file /oracle/admin/cntus/bdump/cntus_mrp0_12389.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u03/cntus/redolog/redo01b.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
ORA-00312: online log 1 thread 1: '/u02/cntus/redolog/redo01a.log'
ORA-27037: unable to obtain file status
SVR4 Error: 2: No such file or directory
Additional information: 3
Thu Sep 06 15:08:34 EDT 2012
Errors in file /oracle/admin/cntus/bdump/cntus_mrp0_12389.trc:
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 1 thread 1: '/u02/cntus/redolog/redo01a.log'
Clearing online redo logfile 1 complete
Media Recovery Waiting for thread 1 sequence 10166
Thu Sep 06 15:08:35 EDT 2012
Completed: alter database recover managed standby database disconnect from session
======
We have the directory /u02/cntus/redolog and /u03/cntus/redolog. But nothing in there. Should we create redo for it? Is this a separate issue?
Thanks!

Manually apply archived log to standby database.

Hi all,
I am working on oracle 10g EE(10.2.0.4).I am having a very difficult database switchover case in my hand.
1.> There are two database .one primary(prim) and another standby(standby).
2.> Initially both of them was configured as oracle data guard, where prim was primary and standby was standby using rman .(RMAN>duplicate target database for
standby dorecover).
3.>But the rate of generation of archivelog is very high( 20 archivelog per hour with 200mb each).
4.> So automatic shipping of archivelog has been disabled from primary.(log_archive_dest_state_2=defer and nullifying the value of log_archive_dest_2).
5> Now after a period of time archived logs are shipped to dr site manually and applied manually.(alter database recover automatic standby database;)
6.> Now there is a hardware problem occured at primary..it will take 72 hours to come up.
How can i use standby database as primary for that 72 hour.As archive log apply is manually done and parameters are being changed,can i switch over these two?
Is it possible to switchover and switch back these two database with such a configuration?

How can i use standby database as primary for that 72 hour.As archive log apply is manually done and parameters are being changed,can i switch over these two?
Is it possible to switchover and switch back these two database with such a configuration?
As of now you can perform failover your standby to primary database. you should have flashaback enabled, so you have to create a restore point.
Then it can be opened in read & write mode, So once you finished again you can go back to that point.
http://docs.oracle.com/cd/B19306_01/server.102/b14239/manage_ps.htm#i1017111
The above case applicable if you ready to loose, But it doesnt make sense. But in your case this doesnt work. Because once you start use of Standby as primary, there would be live/production data, which you need very much.
So there is lot of work to do.
You have to rebuild standby database and then switchover back to same location. So its a little trip work.
Have you enabled Dataguard Broker ?
Edited by: CKPT on Mar 13, 2012 1:43 PM

Standby Database Archives

Similar Messages

Maybe you are looking for