Status of Logical Standby In case of Failover to Physical Standby

I am using oracle 9.2.0.8 database . I have one logical and one physical standby database in place. If I perform failover to my physical standby, will my logical standby still continue to work with new primary database?

Thank you for your kind reply.
I performed failover to my physical standby and now archives are going on my logical standby from new primary but changes are not getting applied on my logical standby database.
when i tried to register the logical logfile from new primary on my logical standby i am getting following error.
SQL> ALTER DATABASE REGISTER LOGICAL LOGFILE 'E:\orcl1\stdb\archives\TESTDBT001S00001.ARC';
ALTER DATABASE REGISTER LOGICAL LOGFILE 'E:\orcl1\stdb\archives\TESTDBT001S00001.ARC'
ERROR at line 1:
ORA-01287: file is from a different database incarnation

Similar Messages

Logical Standby Issue

Hi Friends,
I have 4 doubts. Please help me to clear my confusion.
Doubt 1:-
I have one primary and one logical standby database. When i restart the primary database or logical standby database or whenever data is not transffering to standby database, I execute the package "EXECUTE DBMS_LOGSTDBY.BUILD;". Then it starts to transfer the data to standby. My question is executing this package many times will affect the primary database? or my configuration is wrong?
Doubt 2:-
I configured DGMGRL for both database and i can switch over and switch back to logical standby database. It automatically start to apply the data to new logical standby database. But when i switch back to old primary database, It didnt transfer the data automatically. So i execute the package "EXECUTE DBMS_LOGSTDBY.BUILD;" in primary. Then it starts to transfer the data. My question is my switchback is wrong? or it happens like that only?
Note:- I check the verbose of both database before switchback. It show success.
Doubt 3:-
When i check the switchover status in logical standby database, It show "NOT ALLOWED". Even though i can switch over by using dgmgrl. Why logical standby database showing "NOT ALLOWED"?
Doubt 4:-
Is it any possible to view that what commands executing by dgmgrl process in background while it switchovering to logical standby database.?
Because when i try to switchover manually it didnt work. Many times i tried. But in dgmgrl, I simply give "switchover to logdb;", It works.
Please help to me to understand clearly.
Thank you in advance.

Wrong forum mate. This forum deals with SQL and PL/SQL languages and related issues - not database administration and configuration issues.
The shared memory error is not unusual though ito SQL and PL/SQL. It is often a result of not using sharable SQL - in other words, SQL statements that are not using bind variables.
This causes additional consumption and fragmentation of shared pool memory. The very worse thing to do in this case would be to increase the size of the shared pool. That is akin to moving the wall a bit further away so that one can run even faster and harder into it.
But I'm merely speculating as you may have another cause for this problem. I suggest that you:
- post this in the [url http://forums.oracle.com/forums/forum.jspa?forumID=61]Database Forum
- research this error on [url http://metalink.oracle.com]Metalink

Logical Standby Creation Problems "Create STatus Unknown"

We are using Grid Control 10.2.0.3 on Oracle 10.2..0.3 databases, Windows 2003 sp2 machines.
We have a primary and fsfo physical standby working properly. We went to create a logical standby on a separate server and had problems. it turned out that the listener on the server was not discovered on the target. we fixed that problem and finished the creation of the logical standby and it seems to be functioning properly now.
However, the status on the data guard page for the logical standby shows Create Status Unknown and we are unable to proceed on to create an additional standby database for other purposes. We have tried removing the logical standby target and re-discovering it but status still shows Create Status Unknown.
Is there any way to clear this status without having to drop the logical standby and completely recreate it.

The status on the agent shows it uploading successfully.
We resolved the issue by removing the logical standby from the configuration and selecting to retain the log apply. We then re-added the standby selecting to manage an existing standby database and the status went to normal.

Fast Start Failover has broken my Logical Standby and Flashback has not helped

I have a primary ( PRIMARYP ), a physical standby ( STANDBYP ) and a logical standby ( STANDBYL ).
I configured Fast Start Failover ( with STANDBYP as the target ) and started an Observer. I did a shutdown abort on my primary and the Fast Start Failover did make STANDBYP the primary. I was able to reinstate PRIMARYP as a physical standby.
However when I checked my broker config it gave for STANDBYL
ORA-16795: the standby database needs to be recreated
Strange I though, since I would have expected STANDBYL to survive ok given that the new primary, STANDBYP was a physical standby of PRIMARYP.
Not to worry I thought, I simply will flashback STANDBYL to the beginning of the day and SQL APPLY will reapply all the redo.
This is where the problem begins
I mount STANDBYL
RMAN> connect target /
connected to target database: STANDBYL (DBID=440422466, not open)
RMAN> flashback database to time "TO_DATE('05/12/13 09:30:00','DD-MM-YY HH24:MI:SS')";
Starting flashback at 05-DEC-13
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=11 device type=DISK
starting media recovery
archived log for thread 1 with sequence 24 is already on disk as file /home/app/oracle/fast_recovery_area/STANDBYL/archivelog/2013_12_04/o1_mf_1_24_99yqwog0_.arc
archived log for thread 1 with sequence 25 is already on disk as file /home/app/oracle/fast_recovery_area/STANDBYL/archivelog/2013_12_05/o1_mf_1_25_9b0mlyvr_.arc
media recovery complete, elapsed time: 00:00:04
Finished flashback at 05-DEC-13
RMAN> quit
Recovery Manager complete.
oraclel[STANDBYL]>dgmgrl
DGMGRL for Linux: Version 11.2.0.3.0 - Production
Copyright (c) 2000, 2009, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.
DGMGRL> connect sys/manager
Connected.
DGMGRL> shutdown;
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
DGMGRL>
DGMGRL>
DGMGRL> startup;
ORACLE instance started.
Database mounted.
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
ORA-01589 - that a nasty surprise ! I didn't think I would need to do anything with the log sequences after a flashback
Any ideas of what is going on ?
thanks,
Jim

Hello;
This pdf might meet your needs :
http://blogs.oracle.com/AlejandroVargas/resource/DATAGUARD-FSFO-IMPLEMENTATION.pdf
Additional info :
http://oracle-tech.blogspot.com/2008/08/fast-start-failover-it-is-reliable.html
http://jakub.wartak.pl/blog/?p=80
http://www.databasejournal.com/features/oracle/article.php/3849106/Fast-Start-Failover-in-Oracle-11g-Data-Guard.htm
Best Regards
mseberg

Logical standby instantiate table status

Oracle 10.2.0.4
Hello All,
I am instantiating a table in a logical standby, execute dbms_logstdby.instantiate_table ('schema','table','db_link'). The table contains 18 million records and has been running for about 1 hour. Is there any way I can check the status of this instantiation as far as how much data has been processed or time remaining.
Any help would be greatly appreciated!
Thank you,
Dave

user13129655 wrote:
Oracle 10.2.0.4
Hello All,
I am instantiating a table in a logical standby, execute dbms_logstdby.instantiate_table ('schema','table','db_link'). The table contains 18 million records and has been running for about 1 hour. Is there any way I can check the status of this instantiation as far as how much data has been processed or time remaining.
Any help would be greatly appreciated!
Thank you,
Davesince other session can not see uncommitted data, you can not do so directly.
query v$sess_io repeatedly to see that I/O is occurring.

Logical Standby: WAITING FOR DICTIONARY LOGS status.

Hi,
I have just configured a Logical Standby from Physical Standby, I followed all steps explained in section 4.2.1 from the Oracle® Data Guard Concepts and Administration 10g Release 2 (10.2) documentation, but now my logical standby stay on WAITING FOR DICTIONARY LOGS more than 3 days, all archives from primary DB have been replicated and registered, I don't understand whats
wrong.
SQL> SELECT * FROM V$LOGSTDBY_STATE;
PRIMARY_DBID SESSION_ID
REALTIME_APPLY
STATE
144528764 1
Y
WAITING FOR DICTIONARY LOGS
Fri Apr 8 18:05:47 2011
RFS LogMiner: Registered logfile [/archive/dbp/581440892_1_0000157573.arc] to LogMiner session id [1]
Fri Apr 8 18:10:55 2011
RFS LogMiner: Client enabled and ready for notification
Fri Apr 8 18:10:55 2011
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: Successfully opened standby log 4: '/redo2a/dbp/redo4a_stb.log'
Fri Apr 8 18:10:58 2011
RFS LogMiner: Registered logfile [/archive/dbp/581440892_1_0000157574.arc] to LogMiner session id [1]
Fri Apr 8 18:15:54 2011
RFS LogMiner: Client enabled and ready for notification
Fri Apr 8 18:15:54 2011
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: Successfully opened standby log 3: '/redo1a/dbp/redo3a_stb.log'
Fri Apr 8 18:15:57 2011
RFS LogMiner: Registered logfile [/archive/dbp/581440892_1_0000157575.arc] to LogMiner session id [1]Thanks in advance.
My Oracle version is: 10.2.0.4
My Platform is: AIX 6.1
Nataly.

On standby alert no error messages found.
RFS LogMiner: Client enabled and ready for notification
Mon Apr 11 18:09:58 2011
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: Successfully opened standby log 4: '/redo2a/mefsf/redo4a_stb.log'
Mon Apr 11 18:10:01 2011
RFS LogMiner: Registered logfile [/archive/mefsf/581440892_1_0000157782.arc] to LogMiner session id [1]
Mon Apr 11 18:23:16 2011
RFS LogMiner: Client enabled and ready for notification
Mon Apr 11 18:23:16 2011
Primary database is in MAXIMUM PERFORMANCE mode
RFS[3]: Successfully opened standby log 3: '/redo1a/mefsf/redo3a_stb.log'
Mon Apr 11 18:23:18 2011
RFS LogMiner: Registered logfile [/archive/mefsf/581440892_1_0000157783.arc] to LogMiner session id [1]Continues
On primary alertlog,
There is a common message:
ORACLE Instance bdprod - Archival Error. Archiver continuing.
Mon Apr 11 18:22:57 2011
Errors in file /oracle/app/oracle/admin/bdprod/bdump/bdprod_arc4_2818414.trc:
ORA-00308: cannot open archived log '/archive/bdprod/581440892_1_0000157545.arc'
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 3
Mon Apr 11 18:22:57 2011
FAL[server, ARC4]: FAL archive failed, see trace file.
Mon Apr 11 18:22:57 2011
Errors in file /oracle/app/oracle/admin/bdprod/bdump/bdprod_arc4_2818414.trc:
ORA-16055: FAL request rejected
ARCH: FAL archive failed. Archiver continuing
Mon Apr 11 18:22:57 2011
ORACLE Instance bdprod - Archival Error. Archiver continuing.
Mon Apr 11 18:22:57 2011
Errors in file /oracle/app/oracle/admin/bdprod/bdump/bdprod_arc1_7078038.trc:
ORA-00308: cannot open archived log '/archive/bdprod/581440892_1_0000157546.arc'
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 3
Mon Apr 11 18:22:57 2011
FAL[server, ARC1]: FAL archive failed, see trace file.
Mon Apr 11 18:22:57 2011
Errors in file /oracle/app/oracle/admin/bdprod/bdump/bdprod_arc1_7078038.trc:
ORA-16055: FAL request rejected
ARCH: FAL archive failed. Archiver continuing
Mon Apr 11 18:22:57 2011
ORACLE Instance bdprod - Archival Error. Archiver continuing.

Restore/recover after failover to a Logical Standby database

I have a question about how to recover or restore back to my original environment after I failover to my Logical Standby database.
My setup is as follows: Oracle version 11.2.0.3, Non-RAC.
1. A Primary database at one location.
2. A Physical Standby database at a second location.
3. A Logical Standby database at a third location.
All three databases have Flashback Database on
All three databases are configured thru the Data Guard Broker.
All three databases has a Fast Recovery Area.
Suppose I loose my primary database (1) and my Physical Standby database (3) so I Failover to my only remaining database, the Logical Standby database (2).
What type of Databases are let after the this failover?
What are my recover/restore/Instantiate options?
The Data Guard Concepts book on 13.2.2 says how to bring the old Primary in to the Data Guard Configuration as a new Logical Standby database.
How do I get back to the original configuration above, a primary, a Physical, and a Logical Standby without having to re-create some databases?
Will Flashback database thru the Broker or Cloud Control/Grid Control rewind my databases?

Suppose I loose my primary database (1) and my Physical Standby database (3) so I Failover to my only remaining database, the Logical Standby database (2).
What type of Databases are let after the this failover?
What are my recover/restore/Instantiate options? Then forget about your current primary database, its out of network.
AFAIK
Now you will have only Physical standby & logical standby. Now you will perform failover only current standby to primary database.
So now you will have only one primary database with new incarnation, so you have to recreate a new standby database again.
The Data Guard Concepts book on 13.2.2 says how to bring the old Primary in to the Data Guard Configuration as a new Logical Standby database.
How do I get back to the original configuration above, a primary, a Physical, and a Logical Standby without having to re-create some databases?
Will Flashback database thru the Broker or Cloud Control/Grid Control rewind my databases?Check this. But not much aware of Clound control and all. Sorry for that. ;-) I'm sure Uwe/Mseberg can answer this ;-)
http://www.idevelopment.info/data/Oracle/DBA_tips/Data_Guard/DG_49.shtml#Flashing%20Back%20a%20Failed%20Primary%20Database%20into%20a%20Logical%20Standby%20Database

Logical standby failed with LOGSTDBY status: ORA-01281: SCN range specified

My logical standby datbase on 11gR2 failed with the above message.
A search on the error says
Error: ORA-01281 (ORA-1281)
Text: SCN range specified is invalid
Cause: StartSCN may be greater than EndSCN, or the SCN specified may be
invalid.
Action: Specify a valid SCN range.
does any one have an idea as to how to specify a Valid SCN Range
appreciate you help.

When you got to DBMS_LOGSTDBY
http://www.morganslibrary.org/reference/pkgs/dbms_logstdby.html
What did you do when you saw the procedure MAP_PRIMARY_SCN?

Status of Outbound Delivery in case of batch split

Hi All,
I have a query regarding the status updation of outbound delivery in case of a batch split.
I have a delivery with 10 qty of batch managed material and is distributed from ERP to EWM. As per standard SAP, the following 2 options exist to carry out a batch split in EWM
1. Create batch sub items in the Outbound delivery Order
2. To adopt quantities pertaining to multiple batches during WT creation from the 'Stock can be removed' tab.
We are using the second option as per business requirement. The process is working fine if i create & confirm multiple WT's at one shot i.e in this case i created one WT for 5 qty with batch-1 & one more WT for balance 5 qty with batch-2 & confirmed both the tasks. System created 2 batch sub items automatically when WT's are confirmed & the header status of 'picking' got updated as 'completed'.
However the problem is when i create only 1 WT for partial quantity. For eg. in this case i created onle WT for 5 qty of batch-1 & confirmed the task. System created 1 batch sub item for 5 qty & also updated the 'picking' status in header to completed. My understanding is that since entire delivery quantity is yet to be picked, the picking status at header must be 'partially completed' & not 'completed'.
I have checked the status profile & have status types DER & DPI active. Does this require any config in the status profile OR Is there any other way in which i can achieve this functionality ( i.e. Header status must be 'partially completed' untill entire delivery quantity is picked.)
Would be glad if you can share your thoughts on this.
Regards,
Smitha Pai.

Thank you for your kind reply.
I performed failover to my physical standby and now archives are going on my logical standby from new primary but changes are not getting applied on my logical standby database.
when i tried to register the logical logfile from new primary on my logical standby i am getting following error.
SQL> ALTER DATABASE REGISTER LOGICAL LOGFILE 'E:\orcl1\stdb\archives\TESTDBT001S00001.ARC';
ALTER DATABASE REGISTER LOGICAL LOGFILE 'E:\orcl1\stdb\archives\TESTDBT001S00001.ARC'
ERROR at line 1:
ORA-01287: file is from a different database incarnation

Logical Standby Database in NOARCHIVE Mode

Hi,
I have configured a Logical Standby Database for Reporting purposes. A Physical Standby Database is running for MAA. i.e. in case of Role Transition (switch/Failover) the Physical Stdby Db will get the role of the Primary.
The logical standby database is creating a lot of Archive Redologs files, nearly every minute. Redolog files are 50MB and there is no work done in db during the time. I'm NOT using Standby Redolog files.
Is there a need for logical standby database to be in NOARCHIVELOG mode? The Primary is definatley in ARCHIVELOG mode.
Thanks for any responses.
regards
Sahba

hi,
well there are two things to the above:-
1. there was an archive file nearly every minute:
this is due to a db recovery. for some reason, the db was in inconsistent state, after a sudden shutdownof the OS. I was on a test environment, on windows vista, unfortunately. unimportant ... a reboot solved it.
2. Logical standby db in NOARCHIVE MODE when setup for the purpose of Reporting.
As long as the MAA configured for the primary db, such as physical standby db, and a second, the logical standby db setup purely for the purpose of reporting, which then can run with NOARCHIVELOG mode, after converting the physical standby db to logical.
logical standby db uses Streams architecture, so this method brings cost, time and performance advantages to the customer.
regards
Sahba

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

NEED HELP!!!! Logical Standby and RMAN.

Hello,
I have a Data Guard env setup on win 2000 with 9.2.0.4.
I now have primary and standby. I was wondering if I create a logical standby to achieve transparent application failover. What I am saying is if the primary node dies, then in tnsnames I want to point to the logical standby, since it is an open database, the users can still perform without knowing the db went down. Then if we indeed need a failover we can failover to the physical standby. This would ensure availability without having to implement RAC or AQ, Right? Also, I read that you should create rman schema (recovery catalog) on standby db. Any thoughts?

Were you able to figure this one out?
I have a similar configuration as you - the same motherboard and an eVga Geforce 3 6600 fanless. With the latest BIOS (3.8) and this video card, the system will not go into Standby completely. I hear the HDD head park and the video goes black, but the LEDs on the front of the PC chassis and the case/PS fans do not stop. Pressing the button to bring the PC out of Standby, rather, whatever state it is in, works.

Logical standby stopped when trying to create partitions on primary(Urgent

RDBMS Version: 10.2.0.3
Operating System and Version: Solaris 5.9
Error Number (if applicable): ORA-1119
Product (i.e. SQL*Loader, Import, etc.): Data Guard on RAC
Product Version: 10.2.0.3
logical standby stopped when trying to create partitions on primary(Urgent)
Primary is a 2node RAC ON ASM, we implemented partitions on primar.
Logical standby stopped appling logs.
Below is the alert.log for logical stdby:
Current log# 4 seq# 860 mem# 0: +RT06_DATA/rt06/onlinelog/group_4.477.635601281
Current log# 4 seq# 860 mem# 1: +RECO/rt06/onlinelog/group_4.280.635601287
Fri Oct 19 10:41:34 2007
create tablespace INVACC200740 logging datafile '+OT06_DATA' size 10M AUTOEXTEND ON NEXT 5M MAXSIZE 1000M EXTENT MANAGEMENT LOCAL
Fri Oct 19 10:41:34 2007
ORA-1119 signalled during: create tablespace INVACC200740 logging datafile '+OT06_DATA' size 10M AUTOEXTEND ON NEXT 5M MAXSIZE 1000M EXTENT MANAGEMENT LOCAL...
LOGSTDBY status: ORA-01119: error in creating database file '+OT06_DATA'
ORA-17502: ksfdcre:4 Failed to create file +OT06_DATA
ORA-15001: diskgroup "OT06_DATA" does not exist or is not mounted
ORA-15001: diskgroup "OT06_DATA" does not exist or is not mounted
LOGSTDBY Apply process P004 pid=49 OS id=16403 stopped
Fri Oct 19 10:41:34 2007
Errors in file /u01/app/oracle/admin/RT06/bdump/rt06_lsp0_16387.trc:
ORA-12801: error signaled in parallel query server P004
ORA-01119: error in creating database file '+OT06_DATA'
ORA-17502: ksfdcre:4 Failed to create file +OT06_DATA
ORA-15001: diskgroup "OT06_DATA" does not exist or is not mounted
ORA-15001: diskgroup "OT06_DATA" does not exist or
Here is the trace file info:
/u01/app/oracle/admin/RT06/bdump/rt06_lsp0_16387.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /u01/app/oracle/product/10.2.0
System name: SunOS
Node name: iscsv341.newbreed.com
Release: 5.9
Version: Generic_118558-28
Machine: sun4u
Instance name: RT06
Redo thread mounted by this instance: 1
Oracle process number: 16
Unix process pid: 16387, image: [email protected] (LSP0)
*** 2007-10-19 10:41:34.804
*** SERVICE NAME:(SYS$BACKGROUND) 2007-10-19 10:41:34.802
*** SESSION ID:(1614.205) 2007-10-19 10:41:34.802
knahcapplymain: encountered error=12801
*** 2007-10-19 10:41:34.804
ksedmp: internal or fatal error
ORA-12801: error signaled in parallel query server P004
ORA-01119: error in creating database file '+OT06_DATA'
ORA-17502: ksfdcre:4 Failed to create file +OT06_DATA
ORA-15001: diskgroup "OT06_DATA" does not exist or is not mounted
ORA-15001: diskgroup "OT06_DATA" does not exist or
KNACDMP: *******************************************************
KNACDMP: Dumping apply coordinator's context at 7fffd9e8
KNACDMP: Apply Engine # 0
KNACDMP: Apply Engine name
KNACDMP: Coordinator's Watermarks ------------------------------
KNACDMP: Apply High Watermark = 0x0000.0132b0bc
Sorry our primary database file structure is different from stdby, we used db_file_name_convert in the init.ora, it look like this:
*.db_file_multiblock_read_count=16
*.db_file_name_convert='+OT06_DATA/OT06TSG001/','+RT06_DATA/RT06/','+RECO/OT06TSG001','+RECO/RT06'
*.db_files=2000
*.db_name='OT06'
*.db_recovery_file_dest='+RECO'
Is there any thing wrong in this parameter.
I tried this parameter before for cloning using rman backup. This din't work.
What exactly must be done? for db_file_name_convert to work.
Even in this case i think this is the problem its not converting the location and the logical halts.
help me out.....
let me know if you have any questions.
Thanks Regards
Raghavendra rao Yella.

Hi reega,
Thanks for your reply, our logical stdby has '+RT06_DATA/RT06'
and primary has '+OT06_DATA/OT06TSG001'
so we are using db_file_name_convert init parameter but it doesn't work.
Is there any thing particular steps hiding to use this parameter? as i tried this parameter for rman cloning it din't work, as a workaround i used rman set new name command for clonning.
Let me know if you have any questions.
Thanks in advance.

Logical standby database keeps displaying ORA-16768

I have a logical standby database setup on a remote host to accept cascaded logs from a physical standby. Everything was working fine until yesterday when I get the above error and log apply services stopped. When I go into Grid Control to Data Guard I see the error and it displays the failed SQL statement which is a create index statement. I have the option of clicking the SKIP button. When I click SKIP it appears to have processed it as the error goes away but then a few minutes later the error comes back, log apply stops and the failed SQL statement is the same create index statement. I guess the Skip doesn't mean Skip, it means Retry... My question is how do I get past this? Logs have been piling up.

Hi,
Ok I applied :
SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY;
Database altered.
SQL> alter database start logical standby apply immediate;
Database altered.
SQL>
And now I received this :
ORA-16825: Fast-Start Failover and other errors or warnings detected for the database
Cause: The broker has detected multiple errors or warnings for the database. At least one of the detected errors or warnings may prevent a Fast-Start Failover from occurring.
Action: Check the StatusReport monitorable property of the database specified.
What does it mean to check the status report.....
I found this about monitorable status report !!
DGMGRL> show database 'M3RPT' 'StatusReport';
STATUS REPORT
INSTANCE_NAME SEVERITY ERROR_TEXT
* WARNING ORA-16821: logical standby database dictionary not yet loaded
DGMGRL>
What can I do ?
Thanks a lot
oldschool
Edited by: oldschool on Jun 4, 2009 2:37 AM

Logical Standby - Log auto delete

Hello Everybody,
We are having a logical standby database which is working fine.. But the only concern is with deletion of archive logs that are applied..
I wanted to auto delete the archives that are applied.. Till yesterday all the archives that had applied was getting deleted automatically.. But now some how its not getting deleted..
Nothing has been changed since yesterday and i even checked alert log no error has been recorded but it just simply doesn't delete the archives..
For a try i restarted SQL apply, its applying the archive logs but it doesn't delete the archives that are applied..
Please any help or suggestions would be great.
Thanks

Thanks for your response..
As per the links you provided, these links are for archive deletion policy for primary and physical standby which we configure using RMAN..
But in Logical Standby case archive logs are automatically deleted after its applied...
So when ever we start sql apply following are the alert entries and it should automatically delete archives after it gets applied..
ALTER DATABASE START LOGICAL STANDBY APPLY
Thu Aug 20 16:34:14 2009
ALTER DATABASE START LOGICAL STANDBY APPLY (oracle)
Thu Aug 20 16:34:14 2009
No optional part
Attempt to start background Logical Standby process
LSP0 started with pid=23, OS id=4715
Thu Aug 20 16:34:15 2009
LOGSTDBY Parameter: LOG_AUTO_DELETE = TRUE
Completed: ALTER DATABASE START LOGICAL STANDBY APPLY
Thu Aug 20 16:34:15 2009
LOGSTDBY status: ORA-16111: log mining and apply setting up
Thu Aug 20 16:34:15 2009
LOGMINER: Parameters summary for session# = 1
LOGMINER: Number of processes = 3, Transaction Chunk Size = 201
LOGMINER: Memory Size = 30M, Checkpoint interval = 150M
LOGMINER: session# = 1, reader process P000 started with pid=24 OS id=4717
LOGMINER: session# = 1, builder process P001 started with pid=25 OS id=4719
LOGMINER: session# = 1, preparer process P002 started with pid=26 OS id=4721
Thu Aug 20 16:34:15 2009
LOGMINER: Begin mining logfile: /u01/app/oracle/archive/oracle/ARCH_ORACL_1309_1_692680471.arc
Thu Aug 20 16:34:15 2009
LOGMINER: Turning ON Log Auto Delete
Thu Aug 20 16:34:15 2009But in my case its not deleting archives what could be the reason..
Please any help would be great

Status of Logical Standby In case of Failover to Physical Standby

Similar Messages

Maybe you are looking for