Archive destination on Logical Standby

Dear colleagues,
A physical standby database writes archivelogs in '/oradata3/iclgstdb/archivelog' destination because a parameter standby_archive_dest set in '/oradata3/iclgstdb/archivelog':
SQL> sho parameter standby
NAME                                 TYPE        VALUE
standby_archive_dest                 string      /oradata3/iclgstdb/archivelog
standby_file_management              string      AUTO
When I switch the physical to a logical standby then archivelogs are written in '$ORACLE_HOME/dbs/arch' destination:
SQL> ARCHIVE LOG LIST
Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            /ora/OraHome11203/dbs/arch
Oldest online log sequence     1
Next log sequence to archive   2
Current log sequence           2
But I don't see this destination in v$parameter view.
How can I change "Archive destination /ora/OraHome11203/dbs/arch" to '/oradata3/iclgstdb/archivelog'?

Hi,
Above answered given by one of our DBA friend is correct...just want to add few things,
We need to update both the parameters related to log_archive_dest_1 and log_archive_dest_2 on primary and standby location,
on primary,
log_archive_dest_1 would be local directory or would be ASM...
log_archive_dest_2 would be standby database service name and archive will generated on standby location location...
Correct ans:-
"If your version of Oracle is 11 then STANDBY_ARCHIVE_DEST parameter is deprecated.
set LOG_ARCHIVE_DEST_1 to '/oradata3/iclgstdb/archivelog on the standby"
Regards,
GRB

Similar Messages

Skip archive log on logical standby

hi ,
I want to skip archive log from nmber 1150 to 1161 on logical standby dtbs.
I knw , we can skip ddl , dml on logical standby .
How can archive this ??
(oracle 10g entreprise edition )

Hello;
I do not believe this is an option. The closest to this would be "applying modifications to specific tables"
See :
9.4.3 Using DBMS_LOGSTDBY.SKIP to Prevent Changes to Specific Schema Objects
Data Guard Concepts and Administration 10g Release 2 (10.2) B14239-05
While this is not the answer you want the skip Archive would create a Gap and cause many other issues you don't want.
Best Regards
mseberg

Determining the last archive applied on Logical Standby

Hi,
I am trying to determine the last log received and applied on my Logical Standby
SQL> select thread#, max(sequence#) "Last Standby Seq Received"
from v$archived_log val, v$database vdb
where val.resetlogs_change# = vdb.resetlogs_change#
group by thread# order by 1;
THREAD# Last Standby Seq Received
1 14
SQL> select thread#, max(sequence#) "Last Standby Seq Applied"
from v$archived_log val, v$database vdb
where val.resetlogs_change# = vdb.resetlogs_change#
and applied='YES'
group by thread# order by 1;
Does not return anything
These statements work ok on a physical standby.
I know Sql Apply is enabled on my logical standby - my broker configuration is enabled and for the logical standby database, it is showing the Intended State as APPLY-ON with no Transport or Apply Lag on any of the databases
Q. How do I determine the last seq applied on my logical standby ?
thanks,
Jim

Hello;
I have this from my notes:
SELECT
L.SEQUENCE#,
L.FIRST_TIME,
(CASE WHEN L.NEXT_CHANGE# < P.READ_SCN THEN 'YES'WHEN L.FIRST_CHANGE# < P.APPLIED_SCN THEN 'CURRENT' ELSE 'NO' END) APPLIED
FROM
DBA_LOGSTDBY_LOG L, DBA_LOGSTDBY_PROGRESS P
ORDER BY SEQUENCE#;
Best Regards
mseberg

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.

Logical Standby Database Down

I am new to the Data Guard process and i wanted to know the following:
I have a 9i Primary DB that ships to a Logical Standby Database, however if the logical standby database goes down for whatever reason, (hardware failure) it is unreachable, what can I configure to alert me that the has occurred?
Is it something on the Primary DB that alerts me that the redo logs are perhaps not being processed? Does one use the Dead Connection Detection parameter SQLNET.EXPIRE? How do I identify the Primary to Standby connection is down amongst so many user connections?
Many Thanks
AM

You will have an error for the archive log destiantion that is for your standby
For like 10g or 11g using a SYNC or ASYC the logwr reports the issue the archiver process will report same as well.
LGWR: Error 1041 disconnecting from destination LOG_ARCHIVE_DEST_2 standby host 'testsb'
so for your archive destination for you standby look for errors to the destination and then alert.

Logical standby | archive log deleted | how to remove gap ???

hi gurus...
i have problem on logical standby
by mistake standby log coming to logical standby has been deleted , now how to fill up the gap ???
ON STANDBY
SEQUENCE# FIRST_CHANGE# NEXT_CHANGE# APPLIED
228 674847 674872 YES
229 674872 674973 CURRENT
230 674973 674997 NO
231 674997 675023 NO
232 675023 675048 NO
233 675048 675109 NO
234 675109 675135 NO
235 675135 675160 NO
236 675160 675183 NO
237 675183 675208 NO
238 675208 675232 NO
239 675232 675257 NO
240 675257 675282 NO
241 675282 675382 NO
242 675382 675383 NO
243 675383 675650 NO
244 675650 675652 NO
245 675652 675670 NO
246 675670 675688 NO
247 675688 675791 NO
248 675791 678524 NO
archive log are shipping to standby location also and getting registered
ALERT LOG OF STANDBY
Fri May 7 12:25:36 2010
Primary database is in MAXIMUM PERFORMANCE mode
RFS[21]: Successfully opened standby log 5: '/u01/app/oracle/oradata/BEST/redo05.log'
Fri May 7 12:25:37 2010
RFS LogMiner: Registered logfile [u01/app/oracle/flash_recovery_area/BEST/archivelog/archBEST_248_1_715617824.dbf] to LogMiner session id [1]
but i dont have standby log after 229 sequence ...
ON PRIMARY
SYS@TEST AS SYSDBA> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /u01/app/oracle/flash_recovery_area/TEST/standlogOldest online log sequence 247
Next log sequence to archive 249
Current log sequence 249
what to do next to apply sequences and bring both in sync.
please help me ,,,,
Edited by: user12281508 on May 7, 2010 9:45 AM

thanks for response.
no its pure logical standby
i have tried to ftp the archive logs of primary to standby and applied manually
SYS@BEST AS SYSDBA> alter database register logfile '/u01/app/oracle/flash_recovery_area/BEST/archivelog/archBEST_230_1_715617824.dbf';
alter database register logfile '/u01/app/oracle/flash_recovery_area/BEST/archivelog/archBEST_230_1_715617824.dbf'
ERROR at line 1:
ORA-01289: cannot add duplicate logfile
SYS@BEST AS SYSDBA> alter database register logfile '/u01/app/home/archTEST_230_1_715617824.dbf';
alter database register logfile '/u01/app/home/archTEST_230_1_715617824.dbf'
ERROR at line 1:
ORA-01289: cannot add duplicate logfile
any other way ????

Logical standby stops deleting archives automatically

We are ruining 11.1.0.7 on windows 2008 64 bit
The issue I am facing is we have these settings implemented
log_auto_delete = true
log_auto_delete_retention_target = 5
Logical standby works fine and deletes the archive logs coming from primary but after some day it stops working. I have to stop and start the database in order to make it work. Does anybody has this kind of situation? Please help.

Hello;
This might be worth a look:
Bug 13448652 - LOG_AUTO_DELETE setting reverts to FALSE on Logical Standby (Doc ID 13448652.8)
Best Regards
mseberg

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)

Logical Standby out of sync after archiver stuck (how to resync)

Hi,
I had an archiver stuck on my logical standby database for about 4 hours this night.
2 hours later my primary db also had an archiver stuck.
After solving the problem by repairing the backup mechanism and startup of the archivelog backup I realised
that some tables are out of sync.
How can I get back all things back in sync again?
DB: 11gR2 EE
OS: RedHat Linux 5.5
Thanks
941743

Hi,
I don't sure have or not resyncronization whole schema, but you can use with PL/SQL as
Stop SQL Apply on logical standby database
SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY;
on primary
SQL> begin
2> for t in (select table_name from db_tables where owner = '<your schema name>')
3> loop
4> DBMS_LOGSTDBY.INSTANTIATE_TABLE(shema_name => '<your schema name>', object_name => T.Table_name, dblink => '<you dblink name>');
5> end loop;
6>end;
Start SQL Apply on logical standby database
SQL> ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;If you skip DML and DDL for your schema, then you must UNSKIP DML and DDL on this tables you must add following script to PL/SQL block before INSTANTIATE_TABLEs.
DBMS_LOGSTDBY.UNSKIP(stmt => 'DML', schema_name => '<your schema name>', object_name => T.Table_Name);
DBMS_LOGSTDBY.UNSKIP(stmt => 'DDL', schema_name => '<your schema name>', object_name => T.Table_Name);Regards
Mahir M. Quluzade
Edited by: Mahir M. Quluzade on Sep 13, 2012 6:17 PM

Data guard - logical standby in no archive log

We are creating a logical standby for reporting purpose only. I see no reason why it should be in archivelog mode. Would this hamper our current situation?

the solution is already approved , the only thing i could do is wonder if backup is necessary for the logical.
Its not going to be used for any purpose other than reporting.
From what i understand, no archivemode should not affect it. Is this undertanding true

Logical standby stuck at initializing SQL apply only coordinator process up

Hi
OS: solaris 5.10
Hardware: sun sparc
Oracle database: 11.2.0.1.0
Primary database name: asadmin
Standby database name: test
I had been trying to convert a physical standby to logical standby database. Both the primary and standby reside on the same machine.
The physical standby was created with a hot backup of primary.
I had been following document id 278371.1 to convert the physical to logical standby and used the following steps:
Relevant init parameters on primary:
*.db_name='asadmin'
*.db_unique_name='asadmin'
*.log_archive_config='dg_config=(asadmin,test)'
*.log_archive_dest_1='location=/u01/asadmin/archive valid_for=(all_logfiles,all_roles) db_unique_name=asadmin'
*.log_archive_dest_2='SERVICE=test async valid_for=(online_logfiles,primary_role) db_unique_name=test'
*.log_archive_dest_state_1='enable'
*.log_archive_dest_state_2='enable'
*.fal_client='asadmin'
*.fal_server='test'
*.remote_login_passwordfile='EXCLUSIVE'
Relevant init parameters on standby database:
*.db_name='test' -- Was asadmin before I renamed the DB during conversion to logical standby
*.db_unique_name='test'
*.log_archive_dest_1='location=/u01/test/archive valid_for=(all_logfiles,all_roles) db_unique_name=test'
*.log_archive_dest_2='service=asadmin async valid_for=(online_logfiles,primary_role) db_unique_name=asadmin'
*.log_archive_dest_state_1=enable
*.log_archive_dest_state_2=defer
*.remote_login_passwordfile='EXCLUSIVE'*.fal_server=test
*.fal_client=asadmin
Steps on primary:
1) alter system set log_archive_dest_state_2=defer;
2) shutdown immediate;
3) Made sure that the physical standby has applied all of the redo sent to it following the shutdown.
4) startup mount;
5) ALTER DATABASE BACKUP CONTROLFILE to '/home/oracle/control01.ctl';
6) ALTER SYSTEM ENABLE RESTRICTED SESSION;
7) ALTER DATABASE OPEN;
8) Verified that the supplemental logging is on.
9) ALTER SYSTEM ARCHIVE LOG CURRENT;
10) Checked for the checkpoint change no. at this point which is 72403818 and is present in archive log file 1_62_775102253.dbf
11) EXECUTE DBMS_LOGSTDBY.BUILD;
12) ALTER SYSTEM ARCHIVE LOG CURRENT;
13) Checked for the archive log containing dictionary build which is 1_64_775102253.dbf
14) ALTER SYSTEM DISABLE RESTRICTED SESSION;
Details of archive logs and related checkpoint change nos:
NAME FIRST_CHANGE# NEXT_CHANGE#
/u01/asadmin/archive/1_61_775102253.dbf 72402901 72403817
/u01/asadmin/archive/1_62_775102253.dbf 72403817 72404069
/u01/asadmin/archive/1_63_775102253.dbf 72404069 72404211
/u01/asadmin/archive/1_64_775102253.dbf 72404211 72405700
Steps on standby:
1) shutdown immediate;
2) Copy the archivelog file 61(was created at primary after apply stopped at standby), 62(contains checkpoint no. 72403818), 63 and 64(contains dictionary build). Copy the backup controlfile from step 5 above to the controlfile location in standby init.
3) startup mount;
4) Rename all datafiles and redo log files (including standby redo log files) to the correct path on standby.
5) alter database recover automatic from '/u01/test/archive' until change 72405700 using backup controlfile; -- This completed error-free
6) alter database guard all; -- this completed error free
7) alter database open resetlogs; -- this completed error free.
8) nid target=sys/oracle12 dbname=test
9) Changed the db_name in init file to new name test.
10) Added a tempfile to temp tablespaces.
11) ALTER DATABASE REGISTER LOGICAL LOGFILE '/u01/test/archive/1_61_775102253.dbf'; -- ORA-16225: Missing LogMiner session name for Streams
12) ALTER DATABASE START LOGICAL STANDBY APPLY INITIAL 72405700; -- This completed error free.
Also enabled the log_archive_dest_state_2 on primary.
After this output from some views:
SQL> SELECT SESSION_ID, STATE FROM V$LOGSTDBY_STATE;
SESSION_ID STATE
1 INITIALIZING
SQL> SELECT SID, SERIAL#, SPID, TYPE FROM V$LOGSTDBY_PROCESS;
SID SERIAL# SPID TYPE
587 22 15476 COORDINATOR
SELECT PERCENT_DONE, COMMAND
FROM V$LOGMNR_DICTIONARY_LOAD
WHERE SESSION_ID = (SELECT SESSION_ID FROM V$LOGSTDBY_STATE);
PERCENT_DONE
COMMAND
0
SQL> SELECT TYPE, HIGH_SCN, STATUS FROM V$LOGSTDBY;
TYPE HIGH_SCN STATUS
COORDINATOR ORA-16111: log mining and apply setting up
SQL> SELECT APPLIED_SCN, NEWEST_SCN FROM DBA_LOGSTDBY_PROGRESS;
APPLIED_SCN NEWEST_SCN
72405700 72411501
SELECT THREAD#, SEQUENCE#, FILE_NAME FROM DBA_LOGSTDBY_LOG L
WHERE NEXT_CHANGE# NOT IN
(SELECT FIRST_CHANGE# FROM DBA_LOGSTDBY_LOG WHERE L.THREAD# = THREAD#)
ORDER BY THREAD#,SEQUENCE#;
no rows selected
SQL> SELECT EVENT_TIME, STATUS, EVENT
FROM DBA_LOGSTDBY_EVENTS
ORDER BY EVENT_TIMESTAMP, COMMIT_SCN; 2 3
EVENT_TIME STATUS EVENT
14-FEB-12 02:00:50 ORA-16111: log mining and apply setting up
14-FEB-12 02:00:50 Apply LWM 72405699, HWM 72405699, SCN 72405699
14-FEB-12 02:20:11 ORA-16128: User initiated stop apply successfully
completed
14-FEB-12 02:20:39 ORA-16111: log mining and apply setting up
14-FEB-12 02:20:39 Apply LWM 72405699, HWM 72405699, SCN 72405699
14-FEB-12 02:54:15 ORA-16128: User initiated stop apply successfully
completed
14-FEB-12 02:57:38 ORA-16111: log mining and apply setting up
EVENT_TIME STATUS EVENT
14-FEB-12 02:57:38 Apply LWM 72405699, HWM 72405699, SCN 72405699
14-FEB-12 03:01:36 ORA-16128: User initiated stop apply successfully
completed
14-FEB-12 03:13:44 ORA-16111: log mining and apply setting up
14-FEB-12 03:13:44 Apply LWM 72405699, HWM 72405699, SCN 72405699
14-FEB-12 04:32:23 ORA-16128: User initiated stop apply successfully
completed
14-FEB-12 04:34:17 ORA-16111: log mining and apply setting up
14-FEB-12 04:34:17 Apply LWM 72405699, HWM 72405699, SCN 72405699
EVENT_TIME STATUS EVENT
14-FEB-12 04:36:16 ORA-16128: User initiated stop apply successfully
completed
14-FEB-12 04:36:21 ORA-16111: log mining and apply setting up
14-FEB-12 04:36:21 Apply LWM 72405699, HWM 72405699, SCN 72405699
14-FEB-12 05:15:22 ORA-16128: User initiated stop apply successfully
completed
14-FEB-12 05:15:29 ORA-16111: log mining and apply setting up
14-FEB-12 05:15:29 Apply LWM 72405699, HWM 72405699, SCN 72405699
I also greped for lsp and lcr processes and found that lsp is up but do not see any lcr.
The logs are getting transported to the archive destination on standby whenever they are archived on primary but are not getting applied to standby.
Also in case the standby is down while a log is generated on primary it is not automatically transported to standby once the standby is up, means gap resolution is also not working.
I see the following in alert log every time I try to restart the log apply, everything seems to be stuck at initialization.
ALTER DATABASE START LOGICAL STANDBY APPLY (test)
with optional part
IMMEDIATE
Attempt to start background Logical Standby process
Tue Feb 14 05:15:28 2012
LSP0 started with pid=28, OS id=23391
Completed: alter database start logical standby apply immediate
LOGMINER: Parameters summary for session# = 1
LOGMINER: Number of processes = 3, Transaction Chunk Size = 201
LOGMINER: Memory Size = 30M, Checkpoint interval = 150M
LOGMINER: SpillScn 0, ResetLogScn 0
-- NOTHING AFTER THIS

Hello;
I noticed some of your parameters seem to be wrong.
fal_client - This is Obsolete in 11.2
You have db_name='test' on the Standby, it should be 'asadmin'
fal_server=test is set like this on the standby, it should be 'asadmin'
I might consider changing VALID_FOR to this :
VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES)Would review 4.2 Step-by-Step Instructions for Creating a Logical Standby Database of Oracle Document E10700-02
Document 278371.1 is showing its age in my humble opinion.
-----Wait on this until you fix your parameters----------------------
Try restarting the SQL Apply
ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATEI don't see the parameter MAX_SERVERS, try setting it to 8 times the number of cores.
Use these statements to trouble shoot :
SELECT NAME, VALUE, UNIT FROM V$DATAGUARD_STATS;
SELECT NAME, VALUE FROM V$LOGSTDBY_STATS WHERE NAME LIKE ;TRANSACTIONS%';
SELECT COUNT(1) AS IDLE_PREPARERS FROM V$LOGSTDBY_PROCESS WHERE
TYPE = 'PREPERER' AND STATUS_CODE = 16166;Best Regards
mseberg
Edited by: mseberg on Feb 14, 2012 7:37 AM

Logical Standby Database Not Getting Sync With Primary Database

Hi All,
I am using a Primary DB and Logical Standby DB configuration in Oracle 10g:-
Version Name:-
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bi
PL/SQL Release 10.2.0.5.0 - Production
CORE 10.2.0.5.0 Production
TNS for Solaris: Version 10.2.0.5.0 - Production
NLSRTL Version 10.2.0.5.0 - Production
We have build the logical standby last week and till date the Logical DB is not sync. I have checked the init parameters and I wont see any problems with it. Also archive log destinations are also fine enough.
We have a important table named "HPD_HELPDESK" where record count is growing gradually whereas in logical standby it's not growing. There are some 19K record difference in the both the tables.
I have checked the alert log but it is also not giving any error message. Please find the last few lines of the alert log in logical Database:-
RFS LogMiner: Registered logfile [oradata_san1/oradata/remedy/arch/ars1_1703_790996778.arc] to LogMiner session id [1]
Tue Aug 28 14:56:52 GMT 2012
RFS[2853]: Successfully opened standby log 5: '/oracle_data/oradata/remedy/stbyredo01.log'
Tue Aug 28 14:56:58 GMT 2012
RFS LogMiner: Client enabled and ready for notification
Tue Aug 28 14:57:00 GMT 2012
RFS LogMiner: Registered logfile [oradata_san1/oradata/remedy/arch/ars1_1704_790996778.arc] to LogMiner session id [1]
Tue Aug 28 15:06:40 GMT 2012
RFS[2854]: Successfully opened standby log 5: '/oracle_data/oradata/remedy/stbyredo01.log'
Tue Aug 28 15:06:47 GMT 2012
RFS LogMiner: Client enabled and ready for notification
Tue Aug 28 15:06:49 GMT 2012
RFS LogMiner: Registered logfile [oradata_san1/oradata/remedy/arch/ars1_1705_790996778.arc] to LogMiner session id [1]
I am not able to trace the issue that why the records are not growing in logical DB. Please provide your inputs.
Regards,
Arijit

How do you know that there's such a gap between the tables?
If your standby db is a physical standby, then it is not open and you can't query your table without cancelling the recovery of the managed standby database.
What does it say if you execute this sql?
SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;The ARCH processes should be connected and MRP waiting for a file.
If you query for the archive_gaps, do you get any hits?
select * from gv$archive_gapIf you're not working in a RAC environment you need to query v$archive_gap, instead!
Did you check whether the archives generated from the primary instance are transferred and present in the file system of your standby database?
I believe your standby is not in recovery_mode anymore or has an archive_gap, which is the reason why it doesn't catch up anymore.
Hope it helps a little,
Regards,
Sebastian
PS: I'm working on 11g, so unfortunately I'm not quite sure if the views are exist in 10gR2. It's worth a try though!
Edited by: skahlert on 31.08.2012 13:46

Logical STANDBY creating problem in 9.2

Hi,
i've a Physical standby db which is runnig quite well. i just tried to convert it to LOGICAL standby db. but it was asking for recovery. actually i had provided all the logs needed .but still was giving error.
as i had synchronised physical standby i just changed its control file to normal control file from primary db( alter database backup control file to 'c:\lglstdby.ctl' ) (just created).
i just paste the steps i did.
SQL*Plus: Release 9.2.0.1.0 - Production on Sat Apr 12 08:01:09 2008
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
SQL> conn sys@standby as sysdba
Enter password: ******
Connected.
SQL> shut immediate
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
SQL> startup mount pfile=E:\oracle\oradata\pfile\init.ora
ORACLE instance started.
Total System Global Area 312024024 bytes
Fixed Size                   453592 bytes
Variable Size             159383552 bytes
Database Buffers          150994944 bytes
Redo Buffers                1191936 bytes
Database mounted.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-12571: TNS:packet writer failure
SQL> /
alter database open resetlogs
ERROR at line 1:
ORA-03114: not connected to ORACLE
SQL> conn sys@standby as sysdba
Enter password: ******
Connected.
SQL> /
alter database open resetlogs
ERROR at line 1:
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: 'E:\ORACLE\ORADATA\DATA\SYSTEM01.DBF'
SQL> recover database using backupcontrol file;
ORA-01906: BACKUP keyword expected
SQL> recover database using backup controlfile;
ORA-00279: change 567900150 generated at 04/12/2008 07:57:01 needed for thread
1
ORA-00289: suggestion : E:\ORACLE\ORA92\RDBMS\1_43090.DBF
ORA-00280: change 567900150 for thread 1 is in sequence #43090
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel;
ORA-00308: cannot open archived log 'cancel;'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
auto
ORA-00308: cannot open archived log 'E:\ORACLE\ORA92\RDBMS\1_43090.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-00308: cannot open archived log 'E:\ORACLE\ORA92\RDBMS\1_43090.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
SQL> recover database using backup controlfile;
ORA-00279: change 567900150 generated at 04/12/2008 07:57:01 needed for thread
1
ORA-00289: suggestion : E:\ORACLE\ORA92\RDBMS\1_43090.DBF
ORA-00280: change 567900150 for thread 1 is in sequence #43090
--here i gave what it needed,but it asks for more...
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
E:\oracle\oradata\Archive\1_43090.DBF
ORA-00279: change 567900630 generated at 04/12/2008 08:07:30 needed for thread
1
ORA-00289: suggestion : E:\ORACLE\ORA92\RDBMS\1_43091.DBF
ORA-00280: change 567900630 for thread 1 is in sequence #43091
ORA-00278: log file 'E:\oracle\oradata\Archive\1_43090.DBF' no longer needed
for this recovery
---- it asks for next log as it hasn't generated yet.
even if cancel recovery it says file 1 needs media recovery ('E:\ORACLE\ORADATA\DATA\SYSTEM01.DBF' )
SQL> recover database using backup controlfile;
ORA-00279: change 567900630 generated at 04/12/2008 08:07:30 needed for thread
1
ORA-00289: suggestion : E:\ORACLE\ORA92\RDBMS\1_43091.DBF
ORA-00280: change 567900630 for thread 1 is in sequence #43091
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
Media recovery cancelled.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: 'E:\ORACLE\ORADATA\DATA\SYSTEM01.DBF'Why this is happening dont know ?
any ideas?
Thanks & regards!
Oracle 9.2
Win 2K Server

Hi all,
i managed to open STANDBY DB,but in a different way...
i had to recreate controlfile .
SQL> startup nomount pfile=e:\oracle\oradata\pfile\init.ora
ORACLE instance started.
Total System Global Area 312024024 bytes
Fixed Size                   453592 bytes
Variable Size             159383552 bytes
Database Buffers          150994944 bytes
Redo Buffers                1191936 bytes
SQL> ed
Wrote file afiedt.buf
1 CREATE CONTROLFILE REUSE DATABASE "IRCS" RESETLOGS ARCHIVELOG
2 -- SET STANDBY TO MAXIMIZE PERFORMANCE
3      MAXLOGFILES 6
4      MAXLOGMEMBERS 3
5      MAXDATAFILES 100
6      MAXINSTANCES 1
7      MAXLOGHISTORY 1134
8 LOGFILE
9    GROUP 1 (
10      'E:\ORACLE\ORADATA\REDO\REDO011.LOG',
11      'D:\ORACLE\ORADATA\REDO\REDO012.LOG'
12    ) SIZE 4M,
13    GROUP 2 (
14      'E:\ORACLE\ORADATA\REDO\REDO021.LOG',
15      'D:\ORACLE\ORADATA\REDO\REDO022.LOG'
16    ) SIZE 4M,
17    GROUP 3 (
18      'E:\ORACLE\ORADATA\REDO\REDO031.LOG',
19      'D:\ORACLE\ORADATA\REDO\REDO032.LOG'
20    ) SIZE 4M,
21    GROUP 4 (
22      'E:\ORACLE\ORADATA\REDO\REDO041.LOG',
23      'D:\ORACLE\ORADATA\REDO\REDO042.LOG'
24    ) SIZE 4M,
25    GROUP 5 (
26      'E:\ORACLE\ORADATA\REDO\REDO51.LOG',
27      'D:\ORACLE\ORADATA\REDO\REDO52.LOG'
28    ) SIZE 4M,
29    GROUP 6 (
30      'E:\ORACLE\ORADATA\REDO\REDO61.LOG',
31      'D:\ORACLE\ORADATA\REDO\REDO62.LOG'
32    ) SIZE 4M
33 -- STANDBY LOGFILE
34 DATAFILE
35    'E:\ORACLE\ORADATA\DATA\SYSTEM01.DBF',
36    'E:\ORACLE\ORADATA\DATA\UNDOTBS01.DBF',
37    'E:\ORACLE\ORADATA\DATA\DRSYS.DBF',
38    'E:\ORACLE\ORADATA\DATA\FIN_DATA.DBF',
39    'D:\ORACLE\ORADATA\DATA\FIN_IDX.DBF',
40    'E:\ORACLE\ORADATA\DATA\INDX01.DBF',
41    'D:\ORACLE\ORADATA\DATA\INV_DATA.DBF',
42    'E:\ORACLE\ORADATA\DATA\INV_IDX.DBF',
43    'E:\ORACLE\ORADATA\DATA2\OTHER_DATA.DBF',
44    'D:\ORACLE\ORADATA\DATA\OTHER_IDX.DBF',
45    'E:\ORACLE\ORADATA\DATA\PAY_DATA.DBF',
46    'D:\ORACLE\ORADATA\DATA\PAY_IDX.DBF',
47    'D:\ORACLE\ORADATA\DATA\SALE_DATA1.DBF',
48    'D:\ORACLE\ORADATA\DATA\SALE_DATA2.DBF',
49    'E:\ORACLE\ORADATA\DATA\SALE_IDX.DBF',
50    'E:\ORACLE\ORADATA\DATA\USER_DATA.DBF',
51    'E:\ORACLE\ORADATA\DATA\XDB01.DBF'
52* CHARACTER SET WE8MSWIN1252
SQL> /
Control file created.
SQL> alter database open resetlogs;
Database altered.actually my db was very much consistent. it was asking for not generated logs.. i tried to make incomplete recovery but was erroring with system file not consistent. so i did recreate controlfile but my purpose to create logical was not solved here as when i opened DB with newly created contrlfile database was errorring like
SCN not matching with primary database (i forgot to copy the exact error words)
in alert log it was like
RFS: Destination database mount ID mismatch [0x821cc13b:0x821e318f]
can't it then synchronise with primary as physical does with fetching previous logs?
so stopped that to further process..then again tried open my normal physical standby db with physical standby controlfile...but with physical it gave me a error of wrong pasword file and not able mount standby database.
ERROR at line 1:
ORA-01991: invalid password file 'E:\oracle\ora92\DATABASE\PWDircs.ORA'
can't understandb !!....is this die to i tried to mount a open DB? but when creating a physical standby db we do take consistent back(optinal). so that time it doesn't give such type of error of pwd files....
can't understand this behavoir?
Any ideas?
Regards!

Logical Standby - LGWR or ARCH mode

After reading the [Setting the Data Protection Mode of a Data Guard Configuration|http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/log_transport.htm#i1183694] , I'm still confusing about it!
What is the main difference between LGWR or ARCH when implementing a logical standby database, if I want "Maximum Performance" mode?
What the advantages and disadvantages of them? In real situation, which are used mostly by business?
Thanks!

Using the LGWR process differs from ARCn processing because instead of waiting for the online redo log to switch at the primary database and then writing the entire archived redo log at the remote destination all at once, the LGWR process selects a standby redo log file at the standby site that reflects the log sequence number (and size) of the current online redo log file of the primary database. Then, as redo is generated at the primary database, it is also transmitted to the remote destination. The transmission to the remote destination will either be synchronous or asynchronous, based on whether the SYNC or the ASYNC attribute is set on the LOG_ARCHIVE_DEST_n parameter. Synchronous LGWR processing is required for the maximum protection and maximum availability modes of data protection in Data Guard configurations.
Regards,
Muzafar

Creating Logical Standby, DBMS_LOGSTDBY.BUILD; Hangs on Primary..

My two node RAC database Primary hangs upon executing SQL> exec DBMS_LOGSTDBY.BUILD; when creating a Logical Standby. I have stopped all the recovery processes on the Physical Standby. I have also taken down the instances on the RAC apart from the one I'm working on. Additionally not much info in the alert log...
Logminer Bld: Build started
Wed Jan 23 06:01:57 2013
ALTER SYSTEM SWITCH ALL LOGFILE start (UDSRED1)
Wed Jan 23 06:01:57 2013
ALTER SYSTEM SWITCH ALL LOGFILE complete (UDSRED1)
Wed Jan 23 06:01:57 2013
Thread 1 advanced to log sequence 2323 (LGWR switch)
Current log# 2 seq# 2323 mem# 0: /data03/oracle/oradata/UDSRED/redo02.rdo
Wed Jan 23 06:01:57 2013
Wed Jan 23 06:01:57 2013
Logminer Bld: Lockdown Complete. DB_TXN_SCN is 2548 1551493736
Wed Jan 23 06:01:57 2013
LNS: Standby redo logfile selected for thread 1 sequence 2323 for destination LOG_ARCHIVE_DEST_2
Wed Jan 23 06:01:57 2013
LNS: Standby redo logfile selected for thread 1 sequence 2323 for destination LOG_ARCHIVE_DEST_3
Wed Jan 23 06:01:59 2013
ALTER SYSTEM ARCHIVE LOG
Wed Jan 23 06:01:59 2013
Thread 1 advanced to log sequence 2324 (LGWR switch)
Current log# 3 seq# 2324 mem# 0: /data03/oracle/oradata/UDSRED/redo03.rdo
Wed Jan 23 06:01:59 2013
LNS: Standby redo logfile selected for thread 1 sequence 2324 for destination LOG_ARCHIVE_DEST_3
Wed Jan 23 06:01:59 2013
LNS: Standby redo logfile selected for thread 1 sequence 2324 for destination LOG_ARCHIVE_DEST_2
Wed Jan 23 06:02:00 2013
Wed Jan 23 06:02:00 2013
Logminer Bld: Done
Edited by: Imran on Jan 23, 2013 2:10 PM

Imran,
The information from alert log file is not sufficient.
Can you log switch on primary and monitor whether it is archiving in standby or not.
and you can monitor the changes in "v$managed_standby"
Also check for the errors using "v$dataguard_status"
SQL> select error_cdoe, message, timestamp from v$dataguard_status where dest_id=<n>;

Archive destination on Logical Standby

Similar Messages

Maybe you are looking for