Logical standby db help

hi
can anyone tell differnece between the two code
==================================================
1)
SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY;
Database altered.
SQL> EXECUTE DBMS_LOGSTDBY.SKIP(stmt => 'SCHEMA_DDL',-
schema_name => 'HR', -
object_name => 'TESTEMP%');
PL/SQL procedure successfully completed.
SQL> EXECUTE DBMS_LOGSTDBY.SKIP('DML','HR','TESTEMP%');
PL/SQL procedure successfully completed.
SQL> ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;
Database altered.
============================================================
2)
Stop SQL Apply:
SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY;
Register the SKIP rules:
SQL> EXECUTE DBMS_LOGSTDBY.SKIP (stmt => 'DML', schema_name => 'HR', -
object_name => 'EMPLOYEES', proc_name => null);
SQL> EXECUTE DBMS_LOGSTDBY.SKIP (stmt => 'SCHEMA_DDL', schema_name => 'HR', -
object_name => 'EMPLOYEES', proc_name => null);
Start SQL Apply:
SQL> ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;

skipping a DML is absolutely different than skipping a schema_DDL. if all you did is block any DDL operations, then on existing tables a row change will still occur. if it is a new table, it will never happen and you could halt SQL apply with a DML operation on a table that is not created due to you skipping the DDL statement for it
HTH
Victoria DeVore

Similar Messages

  • Dataguard - logical standby - need help - not updating data at commit

    Hi
    Need help ?
    We have logical standby setup where data is not updated at standby when committed at Primary. It only updates when alter system swith logfile.
    On Primary:
    log_archive_dest_2='service=xxStandby LGWR ASYNC valid_for=(online_logfiles,primary_role) db_unique_name=xxStandby'
    On Standby:
    we have already created standby redo logs ( 1+ # redo logs)
    we used ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE NODELAY;
    The data only ships when we do the ALTER SYSTEM SWITCH LOGFILE whereas it should so when data is commited on the primary.
    Is there anything we are missing or need attention.
    Please help
    Thanks you so much

    Yes, I have standby redo logs = ( 1 + # redo logs on the primary) and are of same size.
    I also changed the log_archive_dest_2 setting for valid_for to ALL_LOGFILES, but the performance is still very slow... we are now overr 9 hrs behind the primary.
    log_archive_dest_2='service=xxStandby LGWR ASYNC valid_for=(ALL_LOGFILES,primary_role) db_unique_name=xxStandby'
    The Logical standby performance reallly not good at all. trying to increase sga/pga more ... hoping this will speed up some
    Paul

  • 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

  • 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.

  • Help! 10g logical standby not replicating "create table" on standby

    Hi,
    I'm setting up a logical standby environment and everything works, except when I tried to create a simple table on the primary, the table doesn't show up on the standby. I tried creating a new tablespace on the primary and it shows up right away on the standby. I checked the error logs on both primary and standby and no errors.
    create table test1 (id number(10) primary key, col1 varchar(20), col2 varchar(20));
    The table is created successfully on primary and I also inserted couple of rows and all committed.
    I even tried the following query on the standby to check any failed events and the "create table" DDL doesn't show up , even if it failed:
    select event_time, status, event from dba_logstdby_events order by event_timestamp, commit_scn
    So I'm now confused. The logical standby is active and applying. What would be the issue? How do I find out ?
    Thanks

    had you started apply using this syntax
    real time apply
    alter database start logical standby apply immediate;
    check lag:
    alter session set nls_date_format='dd/mm hh24:mi';
    select newest_time || chr(22)|| newest_scn||chr(10)||applied_time||chr(22)||applied_scn||chr(13)||chr(16)||(newest_scn-applied_scn) lag from dba_logstdby_progress
    /

  • Creating a new schema in a Logical Standby Database

    Hi All,
    I am experimenting with logical standby databases for the purpose of reporting, and have not been able to create a new schema in the logical standby database - one of the key features of logical standbys.
    I have setup primary and logical standby databases, and they seem to be running just fine - changes are moved from the primary to the standby and queries on the standby seem to run ok.
    However, If I try to create a new schema on the logical standby, that does not exist on the primary, I get "ORA-01031: insufficient privileges" errors when I try to create new objects.
    Show below are the steps I have taken to create the new schema on the logical standby. Any help would be greatly appreciated.
    SYS@UATDR> connect / as sysdba
    Connected.
    SYS@UATDR>
    SYS@UATDR> select name, log_mode, database_role, guard_status, force_logging, flashback_on, db_unique_name
    2 from v$database
    3 /
    NAME LOG_MODE DATABASE_ROLE GUARD_S FOR FLASHBACK_ON DB_UNIQUE_NAME
    UATDR ARCHIVELOG LOGICAL STANDBY ALL YES YES UATDR
    SYS@UATDR>
    SYS@UATDR> create tablespace ts_new
    2 /
    Tablespace created.
    SYS@UATDR>
    SYS@UATDR> create user new
    2 identified by new
    3 default tablespace ts_new
    4 temporary tablespace temp
    5 quota unlimited on ts_new
    6 /
    User created.
    SYS@UATDR>
    SYS@UATDR> grant connect, resource to new
    2 /
    Grant succeeded.
    SYS@UATDR> grant unlimited tablespace, create table, create any table to new
    2 /
    Grant succeeded.
    SYS@UATDR>
    SYS@UATDR> -- show privs given to new
    SYS@UATDR> select * from dba_sys_privs where grantee='NEW'
    2 /
    GRANTEE PRIVILEGE ADM
    NEW CREATE ANY TABLE NO
    NEW CREATE TABLE NO
    NEW UNLIMITED TABLESPACE NO
    SYS@UATDR>
    SYS@UATDR> -- create objects in schema
    SYS@UATDR> connect new/new
    Connected.
    NEW@UATDR>
    NEW@UATDR> -- prove ability to create tables
    NEW@UATDR> create table new
    2 (col1 number not null)
    3 tablespace ts_new
    4 /
    create table new
    ERROR at line 1:
    ORA-01031: insufficient privileges
    NEW@UATDR>
    NEW@UATDR>

    HI Daniel,
    I appreciate your quick response.
    My choice of name may not have been ideal, however changing new to another name - like gav - does not solve the problem.
    SYS@UATDR> connect / as sysdba
    Connected.
    SYS@UATDR>
    SYS@UATDR> select name, log_mode, database_role, guard_status, force_logging, flashback_on, db_unique_name
    2 from v$database
    3 /
    NAME LOG_MODE DATABASE_ROLE GUARD_S FOR FLASHBACK_ON DB_UNIQUE_NAME
    UATDR ARCHIVELOG LOGICAL STANDBY ALL YES YES UATDR
    SYS@UATDR>
    SYS@UATDR> create tablespace ts_gav
    2 /
    Tablespace created.
    SYS@UATDR>
    SYS@UATDR> create user gav
    2 identified by gav
    3 default tablespace ts_gav
    4 temporary tablespace temp
    5 quota unlimited on ts_gav
    6 /
    User created.
    SYS@UATDR>
    SYS@UATDR> grant connect, resource to gav
    2 /
    Grant succeeded.
    SYS@UATDR> grant unlimited tablespace, create table, create any table to gav
    2 /
    Grant succeeded.
    SYS@UATDR>
    SYS@UATDR> -- show privs given to gav
    SYS@UATDR> select * from dba_sys_privs where grantee='GAV'
    2 /
    GRANTEE PRIVILEGE ADM
    GAV CREATE TABLE NO
    GAV CREATE ANY TABLE NO
    GAV UNLIMITED TABLESPACE NO
    SYS@UATDR>
    SYS@UATDR> -- create objects in schema
    SYS@UATDR> connect gav/gav
    Connected.
    GAV@UATDR>
    GAV@UATDR> -- prove ability to create tables
    GAV@UATDR> create table gav
    2 (col1 number not null)
    3 tablespace ts_gav
    4 /
    create table gav
    ERROR at line 1:
    ORA-01031: insufficient privileges
    GAV@UATDR>

  • Best practice on using Flashback and Logical Standby

    Hello,
    I'm testing a fail-back scenario where I first need to activate a logical standby, then do some dummy transactions before I flashback this db and resme the redo apply. Here is what the steps look like:
    1)     Ensure logical standby is in-sync with primary
    2)     Enable flashback on standby
    3)     Create a flashback guaranteed restore point
    4)     Defer log shipping from primary
    5)     Activate the logical standby so it’s fully open to read-write
    6)     Dummy activities against the standby (which is now fully open)
    7)     Flashback the database to the guaranteed checkpoint
    8)     Resume log shipping on primary
    9)     Resume redo apply on secondary
    In the end, i can see the log shipping is happening but the logical standby does not apply any of these..and there is no error in the alert log on Standby side. But the following query could explains why the standby is idle:
    SELECT TYPE, HIGH_SCN, STATUS FROM V$LOGSTDBY;
    TYPE HIGH_SCN STATUS
    COORDINATOR ORA-16240: Waiting for log file (thread# 2, sequence# 0)
    ORA-16240: Waiting for log file (thread# string, sequence# string)
    Cause: Process is idle waiting for additional log file to be available.
    Action: No action necessary. This informational statement is provided to record the event for diagnostic purposes.
    I dont understand why it's looking for sequence #0 after the flashback.
    Thanks for the help.

    Hello;
    I hesitate to answer your question because you are not doing a good job of keeping the forum clean :
    Total Questions: 13 (13 unresolved)
    Please consider closing some of you old answered questions and rewarding those who helped you.
    No action necessary.
    Do you really have a thread 2? ( Redo thread number )
    Quick check
    select applied_scn,latest_scn from v$logstdby_progress;Use the DBA_LOGSTDBY_LOG View if you don't have a thread 2 then the sequence# is meaningless.
    COLUMN DICT_BEGIN FORMAT A10;
    SELECT FILE_NAME, SEQUENCE#, FIRST_CHANGE#, NEXT_CHANGE#,
    TIMESTAMP, DICT_BEGIN, DICT_END, THREAD# AS THR# FROM DBA_LOGSTDBY_LOG
    ORDER BY SEQUENCE#;Logical Standby questions are difficult, not a lot of them out there I'm thinking.
    Check
    http://docs.oracle.com/cd/E14072_01/server.112/e10700/manage_ls.htm
    "Waiting On Gap State" ( However I still believe you don't have a 2nd thread# )
    OR
    http://psilt.wordpress.com/2009/04/29/simple-logical-standby/
    Best Regards
    mseberg
    Edited by: mseberg on Apr 26, 2012 5:13 PM

  • ORA-01403 - Logical Standby Apply ends on delete/update statement

    - This thread is relocated to this forum; advice from Daniel Roy -
    After implementing 2 logical standby databases and running pretty smooth for a while 'strange' errors occur which puzzle me. Sometimes I skip a transaction or exclude a schema from replication and hold my breath for what next roars its ugly head.
    Despite fulfilling all logical standby prerequisites and maintaining primary keys on tables I now run into ORA-01403 errors. The updated table only contains 1 row and has a foreign key to another small table.
    I could instantiate these tables, but I want to understand why these errors occur and prevent them form happing or learn how to resolve them best.
    Anyone around who dealt with these matters and won?
    I'm running this implementation with Oracle 9.2.0.7 on Tru64 51.b
    I'm able to create the logical standby databases manually and with aid of the Data Guard Creation Wizard (EM10g 10.1).
    Can anyone also help me out with refining the faulty transaction from e.g. V$LOGMNR_CONTENTS? (Without disrupting the data guard setup).
    I've already retrieved redo info from archivelogs, but there must be an easy way.
    Regards,
    Erik

    Any way for you to turn tracing on for the DB where you see this ORA-01403 error? We could then probably find out exactly what goes wrong. It's very hard for us to know exactly what might be wrong, since we don't know your exact setup (except for this table). Let me know if that's not possible, and I could construct a logical DB setup to test (even tho it would be on Windows, I don't have Tru64).
    Daniel

  • Logical standby database

    Guys,
    Is it possible to create a logical standby database without installing Oracle Data Guard.And if yes how sync. is performed.
    Thanks

    Hi,
    Is it possible to create a logical standby database without installing Oracle Data Guard.In a sense Oracle Streams and Quest Shareplex created a logical standby, but you can have them open too . . . Madhu Tumma explains this in his Oracle Streams book, but it's only conceptually similar to logical standby in Data Guard:
    http://www.rampant-books.com/book_2004_2_streams.htm
    Hope this helps. . .
    Don Burleson
    Oracle Press author
    Author of “Oracle Tuning: The Definitive Reference”
    http://www.dba-oracle.com/bp/s_oracle_tuning_book.htm

  • Logical standby is in Normal State but it dosent apply any changes.

    I had a Rac  active data guard 11.2.0.3   and i converted it to logical standby database.
    My soluition was same as this link :  http://docs.oracle.com/cd/E11882_01/server.112/e41134/create_ls.htm#SBYDB4734
    After that configuration was complete,
    When i change for example 1 row in a table in primary server, it does'nt Apply in standby server .I have checked alert log file and i have not seen any error in alert logfile.
    Primary parameter file:
    *.db_name='KS'
    *.db_unique_name='KS'
    *.dg_broker_start=true
    *.fal_client='KS'
    *.fal_server='KSSTBY_standby'
    *.log_archive_config='DG_CONFIG=(KS,ksstby)'
    *.log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=KS'
    *.log_archive_dest_2='SERVICE=KSSTBY_standby LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=ksstby'
    *.log_archive_dest_3='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=KS'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='ENABLE'
    *.log_archive_dest_state_3='ENABLE'
    *.log_archive_format='archive_%s_%t_%r'
    *.log_file_name_convert='+DATA/KSSTBY','+DATA/KS','+fra/KSSTBY','+fra/KS'
    *.db_file_name_convert='+DATA/KSSTBY','+DATA/KS'
    *.standby_file_management='auto'
    Logical standby parameter file:
    *.db_name='KS'
    *.db_unique_name='ksstby'
    *.fal_client='ksstby'
    *.fal_server='KS_primary'
    *.log_archive_config='DG_CONFIG=(KS,ksstby)'
    *.log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=ksstby'
    *.log_archive_dest_2='SERVICE=KS_primary LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=KS'
    *.log_archive_dest_3='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=ksstby'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='ENABLE'
    *.log_archive_dest_state_3='ENABLE'
    *.log_archive_format='archive_%s_%t_%r'
    *.log_file_name_convert='+DATA/KS','+DATA/KSSTBY','+fra/KS','+fra/KSSTBY'
    *.db_file_name_convert='+DATA/KS','+DATA/KSSTBY'
    *.standby_file_management='auto'
    The Status of Standby server :
    select sequence#,applied from dba_logstdby_log;
        SEQUENCE# APPLIED
    1 5486 CURRENT
    2 5487 CURRENT
    3 5488 CURRENT
    4 5489 NO
    5 5490 NO
    6 5491 NO
    7 5492 NO
    8 5493 NO
    9 5494 NO
    select * from v$logstdby_stats;
        NAME VALUE
    1 logminer session id 1
    2 number of preparers 1
    3 number of appliers 5
    4 server processes in use 9
    5 maximum SGA for LCR cache (MB) 30
    6 preserve commit order TRUE
    7 transaction consistency FULL
    8 coordinator state INITIALIZING
    9 coordinator startup time 28-APR-15
    select * from v$logstdby_state;
        PRIMARY_DBID SESSION_ID REALTIME_APPLY STATE
    1 3130490787 1 Y APPLYING
    Please help to me.

    Start Firefox in <u>[[Safe Mode]]</u> to check if one of the extensions is causing the problem (switch to the DEFAULT theme: Tools > Add-ons > Appearance/Themes).
    * Don't make any changes on the Safe mode start window.
    * https://support.mozilla.com/kb/Safe+Mode
    * [[Troubleshooting extensions and themes]]
    In Firefox 4 [http://kb.mozillazine.org/Safe_mode Safe mode] disables extensions and disables hardware acceleration.
    Check if there is an update available for your graphics display card driver.
    * Tools > Options > Advanced > General > Browsing: "Use hardware acceleration when available"
    In Firefox 4 you can use one of these to start in <u>[[Safe mode]]</u>:
    * Help > Restart with Add-ons Disabled
    * Hold down the Shift key while double clicking the Firefox desktop shortcut (Windows)

  • Logical Standby Problem

    My environment is Primary database is 11.1.0.7 64bit on Windows 2003 Enterprise 64bit. Logical is on the same platform and oracle version but a different server. I created a physical standby first and it applied the logs quickly without any issues. I received no errors when I changed it over to a Logical standby database. The problem that is happening is as soon as I issue the command "alter database start logical standby apply;" the CPU usage goes to 100% and the SQL apply takes a long time to apply a log. When I was doing this on 10G I never ran into this, as soon as the log was received, it was applied within a couple of minutes. I don't think it could be a memory issue since there is plenty on the Logical standby server. I just can't figure out why the SQL apply is so slow and the CPU usage skyrockets. I went through all of the steps in the guide "Managing a Logical Standby Database" from Oracle and I don't see anything wrong. The only difference between the two databases is that on the Primary I have Large Page support enabled, I don't on the Logical. Any help would be greatly appreciated, I need to use this Logical to report off of.

    Thanks for the responses. I have found what is causing the problem. I kept noticing that the statements it was slowing down on were the ones where data was being written to the SYS.AUD$ table in the System tablespace on the Logical Standby database. A quick count of the records showed that I had almost 6 million records in that table. After I decided to truncate SYS.AUD$ on the Logical, the archive logs started to apply normally. I wonder why the Logical has a problem with this table and the Primary doesn't. I didn't even know auditing was turned on on the Primary database, it must be enabled by default. Now I know why my System table space has grown from 1gb to 2gb since November.
    Now that I fixed it for now, I am unsure what to do to keep this from happening. Can I turn off Auditing on the Logical and keep it on for the Primary? Would this stop data from being written to the SYS.AUD$ table on the Logical? It doesn't appear that there is any kind of cleanup on this table that is offered by Oracle, I guess I can just clean out this table occasionally but that is just another thing to add to the list of maintenance tasks. I notice that you can also write this audit data to a file on the OS. Has anyone here done that?

  • Logical standby Slow after starting auditing

    Hi:
    I have logical standby, which was keeping with the primary database, then we started auditing on the primary database(Database auditing.) , After starting auditing my Logical standby not keeping with primary, after doing reasearch we found out that there are so many sql statement from sys schema on AUD$ table, and they are doing full tablescan on it, which is of 3GB as off now. Also This table is own by sys and by default all sys objects should be excluded from logical standby apply. But this is not, when I tryed to skip it by my self, then apply process gives ora-600 and stops.
    I think it is a bug or what ???
    Any help on this will be appriciated.
    Regards
    Bhushan

    Hi Guys:
    After taking my time we decided to truncate the sys.AUD$ on the LOGICAL STANDBY and that solved our problem.Now LS is catching up fast as I can see the progree is verry fast.
    Still if anybody from "ORACLE CORP" is reading this thread they should give us the reason why the sys.aud$ table is beging replicated on the LOGICAL STANDBY site. is this a BUG in oracle?
    Regards
    Bhushan

  • Logical standby server stopped applying changes

    Hi
    I set up a logical standby database with database guard and it worked fine for some time. But recently I had to use it again and discovered that applying changes from primary database to secondary database just stopped working. I see in V$ARCHIVED_LOG one entry per day. If I restart the logical standby then the changes from primary server are also applied. But if I just make a change on primary server and even call 'alter system switch logfile' then I see an entry in V$ARCHIVED_LOG on primary server but not on standby server (BTW in general there are much more entries in this view on the primary server). I checked pairs of log files indicated by the parameter *.log_file_name_convert in standby server's spfile: their last changed date is always the same.
    I will paste spfile of my standby server (dh5). Primary server name is dh2.
    dh2.__db_cache_size=79691776
    dh5.__db_cache_size=96468992
    dh2.__java_pool_size=4194304
    dh5.__java_pool_size=4194304
    dh2.__large_pool_size=4194304
    dh5.__large_pool_size=4194304
    dh2.__shared_pool_size=71303168
    dh5.__shared_pool_size=54525952
    dh2.__streams_pool_size=0
    dh5.__streams_pool_size=0
    *.audit_file_dest='/var/lib/oracle/oracle/product/10.2.0/db_1/admin/dh5/adump'
    *.background_dump_dest='/var/lib/oracle/oracle/product/10.2.0/db_1/admin/dh5/bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='/var/lib/oracle/oracle/product/10.2.0/db_1/oradata/dh5/control01.ctl'
    *.core_dump_dest='/var/lib/oracle/oracle/product/10.2.0/db_1/admin/dh5/cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_file_name_convert='dh2','dh5'
    *.db_name='dh7'
    *.db_recovery_file_dest='/var/lib/oracle/oracle/product/10.2.0/db_1/flash_recovery_area'
    *.db_recovery_file_dest_size=2147483648
    *.db_unique_name='dh5'
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=dh2XDB)'
    *.fal_client='dh5'
    *.fal_server='dh2'
    *.job_queue_processes=10
    *.log_archive_config='DG_CONFIG=(dh2,dh5)'
    *.log_archive_dest_1='LOCATION=/var/lib/oracle/oracle/product/10.2.0/db_1/oradata/dh5_local
    VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES)
    DB_UNIQUE_NAME=dh5'
    *.log_archive_dest_2='SERVICE=dh2 LGWR ASYNC
    VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
    DB_UNIQUE_NAME=dh2'
    *.log_archive_dest_3='LOCATION=/var/lib/oracle/oracle/product/10.2.0/db_1/oradata/dh5
    VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLES)
    DB_UNIQUE_NAME=dh5'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='ENABLE'
    *.log_archive_dest_state_3='ENABLE'
    *.log_archive_format='%t_%s_%r.arc'
    *.log_archive_max_processes=30
    *.log_file_name_convert='oradata/dh2/redo01.log','flash_recovery_area/DH5/onlinelog/o1_mf_4_5x0o5grc_.log','oradata/dh2/r
    edo02.log','flash_recovery_area/DH5/onlinelog/o1_mf_5_5x0o61mw_.log','oradata/dh2/redo03.log','flash_recovery_area/DH5/on
    linelog/o1_mf_6_5x0o63gj_.log'
    *.nls_language='AMERICAN'
    *.open_cursors=300
    *.pga_aggregate_target=311427072
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=167772160
    *.undo_management='AUTO'
    *.undo_retention=3600
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='/var/lib/oracle/oracle/product/10.2.0/db_1/admin/dh5/udump'
    Thanks in advance for any help.
    JM

    Hi,
    Nice to hear you issue got resolved.
    It is good practice to keep monitoring the progress of SQL apply on the logical standby on a regular basis.
    You can mark my response as helpful if it has helped you.
    Regards
    Anudeep

  • 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

  • Logical standby stopped lastnight

    Subject: Logical standby stopped lastnight
    Author: raghavendra rao yella, United States
    Date: Nov 14, 2007, 0 minutes ago
    Os info: solaris 5.9
    Oracle info: 10.2.0.3
    Error info: ORA-16120: dependencies being computed for transaction at SC
    N 0x0002.c8f6f182
    Message: Our logical standby stopped last night. we tried to stop and start the standby but no help.
    Below are some of the queries to get the status:
    APPLIED_SCN LATEST_SCN MINING_SCN RESTART_SCN
    11962328446 11981014649 11961580453 11961536228
    APPLIED_TIME LATEST_TIME MINING_TIME RESTART_TIME
    07-11-13 09:09:41 07-11-14 10:26:26 07-11-13 08:57:53 07-11-13 08:56:36
    sys@RP06>SELECT TYPE, HIGH_SCN, STATUS FROM V$LOGSTDBY;
    TYPE HIGH_SCN STATUS
    COORDINATOR 1.1962E+10 ORA-16116: no work available
    READER 1.1962E+10 ORA-16127: stalled waiting for additional transact
    ions to be applied
    BUILDER 1.1962E+10 ORA-16127: stalled waiting for additional transact
    ions to be applied
    PREPARER 1.1962E+10 ORA-16127: stalled waiting for additional transact
    ions to be applied
    ANALYZER 1.1962E+10 ORA-16120: dependencies being computed for transac
    tion at SCN 0x0002.c8f6c002
    APPLIER ORA-16116: no work available
    APPLIER ORA-16116: no work available
    APPLIER ORA-16116: no work available
    APPLIER ORA-16116: no work available
    APPLIER ORA-16116: no work available
    10 rows selected.
    Select PID,
    TYPE,
    STATUS
    From
    V$LOGSTDBY
    Order by
    HIGH_SCN; 2 3 4 5 6 7 8
    PID TYPE STATUS
    17896 ANALYZER ORA-16120: dependencies being computed for transaction at SC
    N 0x0002.c8f6f182
    17892 PREPARER ORA-16127: stalled waiting for additional transactions to be
    applied
    17890 BUILDER ORA-16243: paging out 8144 bytes of memory to disk
    17888 READER ORA-16127: stalled waiting for additional transactions to be
    applied
    28523 COORDINATOR ORA-16116: no work available
    17904 APPLIER ORA-16116: no work available
    17906 APPLIER ORA-16116: no work available
    17898 APPLIER ORA-16116: no work available
    17900 APPLIER ORA-16116: no work available
    17902 APPLIER ORA-16116: no work available
    10 rows selected.
    How can i get this transaction information, which log miner is looking for dependencies?
    Let me know if you have any questions.
    Thanks in advance.
    Message was edited by:
    raghu559

    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.

Maybe you are looking for

  • SSRS dataset throws error when another stored procedure is called inside dataset stored procedure

    Hello; I am using Report Build 3.0, I have a simple report which gets data using dataset which is created from a Stored Procedure. I have another stored procedure which updates the data in the table which is used for the report. I want to get the liv

  • Apple TV - No Sound on Recent TV Series Purchases

    I am experiencing a weird problem. I have sound problem only on the recent TV Series purchases. The video plays but there is no sound. Previous purchases work perfectly, music plays without a problem. There is no problem with the connections. The sam

  • CS4 Illustrator wont save to PDF, programe just stops

    Upgraded from CS2 to CS4 and everything is woking fine. But when I try and save a file from Illustrator CS4 to a PDF the programe just stops working.  The mouse pointer moves fine and I can use other applications on the machine. The machine is a P3 w

  • How to get crispy fonts using icewm

    Icewm doesn't produce the same crispy Verdana fonts in thunderbird and firefox, xfce shows (in Arch). I'm very glad with the quality in xfce (I selected antialias off, autohinter on and rgb full). This is my ~/.fonts.conf according to the gentoo-wiki

  • Query Performance Issue (First_rows hint)

    Dear friends, I am running a query on default optimizer mode (all_rows) but its not picking the right execution plan nor the right index but if changing optimizer mode into first_rows, its running insteadly. Tables statistics for concern tables are u