Why FRA filling faster in logical standby server.

I have two standby servers one physical and one logical for my primary database. I have notice that on logical standby server the FRA is filling faster then physical standby server. Any one have some suggestions.
Thx

>
I have two standby servers one physical and one logical for my primary database. I have notice that on logical standby server the FRA is filling faster then physical standby server. Any one have some suggestions.
>
That is to be expected, because the logical standby not only creates archive logs on behalf of the transmission from the primary but also generates its own archivelogs on behalf of the filling (& archiving) of the local online logfiles. If you watch a logical standby applying, you may notice that the standby logs are getting archived and the online logs as well. That is significant for a logical standby and leads to (at least temporary) higher space consumption in the recovery area. Temporary, because the applied archive logs can get deleted (automatically, if you allow that).
Kind regards
Uwe
http://uhesse.wordpress.com

Similar Messages

  • Shutdown Logical Standby Server

    How can I gracfully shutdown logical standby server and start it ? Please write the steps
    Thanks

    Hello,
    $> sqlplus '/as sysdba'
    $> shutdown immediate ;
    or
    $> shutdown;
    $> startup force nomount
    or
    $> startup force nomount pfile='..../yourinitstandby.ora'
    $> alter database mount standby database.Verify in alert.log file that standyby server started and mounted.
    Regards

  • 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

  • Oracle 10gR2 Data guard physical or logical standby server?

    Hi
    We are planing to implement an Oracle 10gR2 data guard standby server for DR purposes, I found out that there are two type of standby server which is logical and physical standby server. I want to know which one is preferable? in term of complexity of setup and maintenance?
    regards

    Well it depends on what you mean by maintenance. I found the physical standby to be very little trouble at all ; however the logical standby has restrictions on it that the physical standby does not. In essence the physical standby merely digest archive logs; where as the logical standby uses logminer like functionality to process sql statements much like Oracle streams.
    Hope that helps,
    -JR jr.

  • Do I need ASM for logical standby server?

    I am using ASM in production, when I created physical standby for it, system asked me create ASM file system on it else it is not possible. My question is do I need ASM file system for logical standby too.?
    Thanks

    You can have the primary database on ASM and the standby on filesystem if you want.
    You just need to set db_file_name_convert and standby_file_management. I have tested this will physical, but not logical standby.

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

  • MV Logs not getting purged in a Logical Standby Database

    We are trying to replicate a few tables in a logical standby database to another database. Both the source ( The Logical Standby) and the target database are in Oracle 11g R1.
    The materialized views are refreshed using FAST REFRESH.
    The Materialized View Logs created on the source ( the Logical Standby Database) are not getting purged when the MV in the target database is refreshed.
    We checked the entries in the following Tables: SYS.SNAP$, SYS.SLOG$, SYS.MLOG$
    When a materialized view is created on the target database, a record is not inserted into the SYS.SLOG$ table and it seems like that's why the MV Logs are not getting purged.
    Why are we using a Logical Standby Database instead of the Primary ? Because, the load on the Primary Database is too much and the machine doesn't have enough resources to support MV based replication. The CPU usage is 95% all the time. The appplication owner won't allow us to go against the Primary database.
    Do we have to do anything different in terms of Configuration/Privileges etc. because we are using a Logical Standby Database as a source ?
    Thanks in Advance.

    We have a 11g RAC database in solaris OS where there is huge gap in archive log apply.
    Thread Last Sequence Received Last Sequence Applied Difference
    1 132581 129916 2665
    2 108253 106229 2024
    3 107452 104975 2477
    The MRP0 process seems not to be working also.Almost 7000+ archives lag in standby if compared with primary database.
    i suggest you to go with Incremental rollforward backups to make it SYNC, use this below link for step by step procedure.
    http://www.oracle-ckpt.com/rman-incremental-backups-to-roll-forward-a-physical-standby-database-2/
    Here questions.
    1) Whether those archives are transported & just not applied?
    2) Is in production do you have archives or backup of archives?
    3) What you have found errors in alert log file?
    post
    SQL> select severity,message,error_code,timestamp from v$dataguard_status where dest_id=2;
    4) What errors in primary database alert log file?
    Also post
    select     ds.dest_id id
    ,     ad.status
    ,     ds.database_mode db_mode
    ,     ad.archiver type
    ,     ds.recovery_mode
    ,     ds.protection_mode
    ,     ds.standby_logfile_count "SRLs"
    ,     ds.standby_logfile_active active
    ,     ds.archived_seq#
    from     v$archive_dest_status     ds
    ,     v$archive_dest          ad
    where     ds.dest_id = ad.dest_id
    and     ad.status != 'INACTIVE'
    order by
         ds.dest_id
    /Also check errors from standby database.

  • Data Guard Logical Standby DB Questions

    Hi,
    I am creating Oracle 9i Logical Standby database on AIX 5 on same server ( for
    testing only ).
    In Data Guard Manual ( PDF file page no : 86 ) it is said that
    Step 4 Create a backup copy of the control file for the standby database. On the
    primary database, create a backup copy of the control file for the standby database:
    SQL> ALTER DATABASE BACKUP CONTROLFILE TO
    2> '/disk1/oracle/oradata/payroll/standby/payroll3.ctl';
    My Questions regarding this are
    1. Does it missing "backup standby controlfile" word ? if not what is the use of
    this control file ? Because as per this manual section 4.2.2 step no 1 and 2 I
    have stopped the primary database and copied datafiles,logfiles and controlfiles
    as specified which are having consistent stage.
    2. On primary database I am mirroring 2 controlfiles at two diffrent locations.
    On Standby Database I am going to keep same policy. Then on standby database do I have to copy this controlfile to two locations and rename datafiles or I have
    to user controlfiles which I have backed up along with datafiles ?
    3. Suppose my primary database is "infod" and standby database is "standby".
    Then what should be value of log_file_format parameter of standby database ? On
    primary db I have defined "infod LOG_ARCHIVE_FORMAT=infod_log%s_%t.arc. Do I have to keep same or change it ? If on standby db I change the value do I
    require other parameters to be set ?
    regards & thanks
    pjp

    Q/A1) Its correct you dont need the standby keyword. Not sure abut the reason why but we have created logical standby running in prod using the oracle doc.
    Q/A2) Yo can specify any location and name for your controlfiles as it is instance specific and not depending on primary database.
    Q/A3) You can set any format for your archlogs on standby side. It doesnt bother the primary db or DG configuration.
    Regards,
    http://askyogesh.com

  • Configuration of the Physical & Logical standby servers on the same machine

    I've encoutered a problem to connect to one of the standby servers .
    I created a DataGuard in 10.2. Primary on 1 machine, 1 physical standby and 1 logical standby on another machine (both phy and logical in same machine)
    I first created a primary then a physical standby. I've got no problem at all.
    But when I created a logical standby server on the same machine with the physical then I could not connect to both phy and logical . I can connect to either one of them.
    According to DataGuard setup, the db_name must be the same in primary and all standby servers. This is fine when each of the primary or the standby installed in a separate machine.
    The db_name of the physical = rolex
    The db_name of the logical = rolex
    When we have more than one instance in the same machine, we just set the ORACLE_SID = db_name ( or instance), then connect to it.
    If I connect to the physical, then I try to connect to the logical, it goes to the physical or vice versus.
    Does anyone have the solution ?
    QN

    DB_UNIQUE_NAME parameter will be the seperator.
    give DB_UNIQUE_NAME parameters different names and set ORACLE_SID with DB_UNIQUE_NAME name you gave
    DB_NAME is the primary instances database name DB_UNIQUE_NAME is given for standby instances database name

  • Resynchronization in primary and logical standby db

    Hi,
    I have implemented logical standby successfully first time.for testing i had shutdown logical standby server for last 60 hours.
    when i start standby db and execute command
    "ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;"
    but it is not synchronized data for last 3 days
    Please help me
    Vaibhav Dixit

    i suppossed that you did : alter database open resetlog; right?
    In first place, try to see any error in redo transport:
    alter system switch logfile;
    select status, error from v$archive_dest where dest_id = 2;
    any error?
    for more information, please check:
    http://www.idevelopment.info/data/Oracle/DBA_tips/Data_Guard/DG_45.shtml

  • Oracle Logical Standby as data source

    Post Author: garyreit
    CA Forum: Data Connectivity and SQL
    Has anyone succesfully used an Oracle Logical Standby server as a
    data source?  When I try I get "table not found" for all the
    tables in Crystal reports, but the report runs fine.  When I run
    the same report in BOE, The report fails with the error:Error in File D:\Program Files\Business Objects\BusinessObjects
    Enterprise
    11.5\Data\procSched\biapp1.reportjobserver\~tmp1c4c50845f07b62.rpt:
    Error in formula <Record Selection>.
    '{PS_CANC_TERM_CLASS.BATCH_ID} = {?Batch ID} and
    This field name is not known.
    Details: errorKind We are using BOE XI R2 sp2 and Oracle 10g with an ODBC using the Oracle connector.
    Any Ideas?Thanks

    Post Author: udasgupta
    CA Forum: Data Connectivity and SQL
    I am getting a similar problem. Did you get a solution? If so, could you please let me know.
    Thanks in advance,
    Uma

  • 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

  • Why Would The Logical Standby Lag?

    Oracle 11.2.0.2
    Linux RedHat 5.3+
    Logical standby
    I have a logical standby that is lagging behind the primary a lot.
    The databases have the same amount of data...about 20 million rows.
    They have the same indexes.
    I am using SQL Apply.
    I know that the slow down is that the Logical Standby is doing a full table scan because the update statement contains DECODE statements.
    It takes about 19 minutes to process this statement on the Logical Standby.
    I know what the offending statement is.
    update /*+ streams restrict_all_ref_cons */ "APPLICA"."ARCH" p set "AG_ID"=decode(:1,'N',"AG_ID",:2),
    "CREATED_BY"=decode(:3,'N',"CREATED_BY",:4),
    "CREATED_ON"=decode(:5,'N',"CREATED_ON",:6),
    "DATA_CONTACT_EMAIL"=decode(:7,'N',"DATA_CONTACT_EMAIL",:8),
    "DATA_CONTACT_NAME"=decode(:9,'N',"DATA_CONTACT_NAME",:10),
    "DATA_CONTACT_PHONE"=decode(:11,'N',"DATA_CONTACT_PHONE",:12),
    "DATA_ITEM_ID"=decode(:13,'N',"DATA_ITEM_ID",:14),
    "ITEM_ACTION"=decode(:19,'N',"ITEM_ACTION",:20),
    "ITEM_DATE"=decode(:21,'N',"ITEM_DATE",:22),
    "ITEM_STATUS"=decode(:23,'N',"ITEM_STATUS",:24),
    "MESSAGE_TIME"=decode(:25,'N',"MESSAGE_TIME",:26),
    "MODIFIED_BY"=decode(:27,'N',"MODIFIED_BY",:28),
    "MODIFIED_ON"=decode(:29,'N',"MODIFIED_ON",:30)
    where
    (:31='N' or
    (1=1 and decode(:32,'N','Y',decode(:33,"CREATED_BY",'Y'))='Y'
    and decode(:34,'N','Y',decode(:35,"CREATED_ON",'Y'))='Y'
    and decode(:36,'N','Y',decode(:37,"DATA_CONTACT_EMAIL",'Y'))='Y'
    and decode(:38,'N','Y',decode(:39,"DATA_CONTACT_NAME",'Y'))='Y'
    and decode(:40,'N','Y',decode(:41,"DATA_CONTACT_PHONE",'Y'))='Y'
    and 1=1 and decode(:46,'N','Y',decode(:47,"ITEM_ACTION",'Y'))='Y'
    and decode(:48,'N','Y',decode(:49,"ITEM_DATE",'Y'))='Y'
    and decode(:50,'N','Y',decode(:51,"ITEM_STATUS",'Y'))='Y'
    and decode(:52,'N','Y',decode(:53,"MESSAGE_TIME",'Y'))='Y'
    and decode(:54,'N','Y',decode(:55,"MODIFIED_BY",'Y'))='Y'
    and decode(:56,'N','Y',decode(:57,"MODIFIED_ON",'Y'))='Y')) and
    (:58="AG_ID") and
    (:59="DATA_ITEM_ID")
    This table does have indexes but they do not cover the entire table.
    Primary Key: AG_ID,DATA_ITEM_ID
    Index1 : ITEM_STATUS,AG_ID
    I am NOT asking why the statement is doing a full table scan I know that much.
    What I am asking is if everthing with the structure, indexes and statistics is the same why is there no problem on the PRIMDB and there is a problem on the STBYDB?

    Well I found the issue...I should say a co-worker pointed me to the correct solution.
    We were talking about the indexes and primary key and still attempting to understand why to SQL Apply was rewriting my update to include DECODE statments when he said.
    "You have the same indexes and primary key but are they USABLE."
    Well I thought of course they are usable...I just built the one index and the other is the primary key.
    After looking a bit further we found that that index for the primary key was marked as unusable. Then I remembered that when we rebuilt the standby database that I had moved that table to reduce space within the tablespace. Moving a table can invalidate the primary key index. We rebuilt the index on the primary key and all is good now.
    Regards
    Tim

  • Logical standby issue after adding a new user at production db server

    Hello Experts,
    I am facing a issue related to logical standby db server where after adding a new user at production db server logical standby has stopped sql apply. Can anybody give some idea to find out the root cause and give some tips to resolve the issue.
    tried below .....
    SELECT EVENT_TIME, STATUS, EVENT FROM DBA_LOGSTDBY_EVENTS
    ORDER BY EVENT_TIMESTAMP, COMMIT_SCN, CURRENT_SCN;
    got error
    ORA-16227: DDL skipped due to missing object
    ORA-01403: no data found
    ORA-00942: table or view does not exist
    OS : RHEL 4 (IBM P5)
    DB : Oracle 10g (10.2.0.1)
    Achyot

    Please let me know if can skip the DDL at which it is failing.
    ALTER DATABASE STOP LOGICAL STANDBY APPLY;
    Use EXECUTE DBMS_LOGSTDBY.SKIP
    ALTER DATABASE START LOGICAL STANDBY APPLY;
    Thanks,
    Renu

  • Why could not Oracle replicates tables which includes Spatial Data to Logical Standby?

    Hi all,
    Nowadays, i am working on Oracle Logical Standby Databases which includes Spatial Data? But i could not achieve to transport a table with multimedia data (with spatial data types ). But Logical Standby Databases can not support this type of tables? Is this a restriction of modelling Spatial and Geometry in data blocks? And how do i achieve this because i should use this secondary for query-only?
    Kind Regards,

    Some data types are simply not supported by logical standby replication. Depending on the version, this might or might not include Spatial.
    11.2: https://docs.oracle.com/cd/E11882_01/server.112/e41134/data_support.htm#SBYDB4936
    12.1: https://docs.oracle.com/database/121/SBYDB/data_support.htm#SBYDB4936
    If you need to replicate Spatial data, you need to look at other mechanisms. E.g., physical standby, materialized views, or GoldenGate.

Maybe you are looking for