Determining Gaps in Logical Standby

DB version: 11.2
For determining the gaps for Physical Standby DB, I use the queries mentioned in the post below
StandbyDB is not in sync with primary
For checking if a Logical Standby and Primary is in Sync, Can I use the same query ? Do I have to consider any other factors for Logical standby when checking for gaps ?

Hello;
Which part of that huge post! I'm thinking No, because that is not a Logical Standby.
On a logical standby database, query the DBA_LOGSTDBY_LOG view on the logical standby database :
COLUMN FILE_NAME FORMAT a55
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#;The Data Guard Concepts and Administration Oracle document should have a "Redo Transport Services" section on this.
Another one, also run on the logical standby :
SELECT
  SUBSTR(FILE_NAME,1,100) FILE_NAME, SUBSTR(SEQUENCE#,1,10) "SEQ#",
  FIRST_CHANGE#, NEXT_CHANGE#, TO_CHAR(TIMESTAMP, 'HH:MI:SS') TIMESTAMP,
  DICT_BEGIN BEG, DICT_END END, SUBSTR(THREAD#,1,4) "THR#"
FROM
  DBA_LOGSTDBY_LOG
ORDER BY
  SEQUENCE#;
  Best Regards
mseberg

Similar Messages

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

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

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

  • Determining the last archive applied on Logical Standby

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

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

  • 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

  • Logical standby stuck at initializing SQL apply only coordinator process up

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

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

  • Logical Standby Database Not Getting Sync With Primary Database

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

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

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

  • Log mining is taking too much time in logical standby database

    dear DBAs,
    today i found a gap between the production database and the logical standby database and i found that the log mining is taking more than 1 hour to complete an archivelog (size: 500M)
    note that the MAX_SGA is 1500M and the MAX_SERVERS=45
    the databases is 10gR2 (10.2.0.5.0) running on a linux machine RHEL 4
    please your help.
    thx in advance
    Elie

    hi,
    can you check metalink id [ID 241512.1]
    thanks

  • How to apply the changes in logical standby database

    Hi,
    I am new to Dataguard. I am now using 10.2.0.3 and followed the steps from Oracle Data Guard Concepts and Administration Guide to setup a logical standby database.
    When I insert a record to a table from the primary database side, when i query the same table from the logical standby database, it doesn't show the new records.
    Did I miss something? What I want to do is when I insert a record in the primary db, then the corresponding record will be inserted in the standby db.
    Or I totally misunderstand what Oracle data guard is? Any help are appreciated.
    Denis

    Hi
    Can anyone help to answer me is my logical standby db have a archive gap?
    SQL> SELECT APPLIED_SCN, APPLIED_TIME, READ_SCN, READ_TIME, NEWEST_SCN, NEWEST_T
    IME FROM DBA_LOGSTDBY_PROGRESS;
    APPLIED_SCN APPLIED_TIME READ_SCN READ_TIME NEWEST_SCN
    NEWEST_TIME
    851821 29-JUL -08 17:58:29 851822 29-JUL -08 17:58:29 1551238
    08-AUG -08 08:43:29
    SQL> select pid, type, status, high_scn from v$logstdby;
    no rows selected
    SQL> alter database start logical standby apply;
    Database altered.
    SQL> select pid, type, status, high_scn from v$logstdby;
    PID
    TYPE
    STATUS HIGH_SCN
    2472
    COORDINATOR
    ORA-16116: no work available
    3380
    READER
    ORA-16127: stalled waiting for additiona 852063
    l transactions to be applied
    2480
    BUILDER
    ORA-16116: no work available
    2492
    ANALYZER
    ORA-16111: log mining and apply setting
    up
    2496
    APPLIER
    ORA-16116: no work available
    2500
    APPLIER
    ORA-16116: no work available
    3700
    APPLIER
    ORA-16116: no work available
    940
    APPLIER
    ORA-16116: no work available
    2504
    APPLIER
    ORA-16116: no work available
    9 rows selected.
    Thanks a lot.
    Message was edited by:
    Denis Chan

  • Refresh Schema in Primary (and Logical Standby)

    Does anyone have a recommendation for the best way to refresh a 16Gb schema in a Primary Database that has a logical standby?
    I attempted to refresh our main schema in our Primary by using IMPDP. I tried to follow the same steps as I would if I had to upgrade a Primary database with a Logical Standby in place. I defered the Log archive log dest state associated with the logical standby, stopped the SQL Apply on the standby and disabled Data Guard, then dropped the schema in the Standby, created and imported the schema. i then performed the drop, recreate and import in the Primary. After that I did a DBMS_LOGSTDBY.BUILD on the Primary. Finally I enabled DG, restarted the apply and enabled the log arch dest on the primary.
    One issue I did have was that i did not defer the archivelogs until after the import had started so it did send some archives over - of course DG was disabled and the apply was off but now the status of DG is normal but i have a big gap in Last Received Log and Last Applied Log and of the missing archives, the oldest have 'Committed Transactions Applied', newer ones have 'Not Applied' and the newest have 'Not Received'.
    I think I'm hosed but I am confused on the best approach. I did try just to perform the import on the Primary previously (last year) but I remember that the volume of data killed the replication.
    This is 10.2.0.4 on Windows 2003 Server (64bit)
    Thanks
    Graeme

    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

  • Skip the DELETE command on logical standby

    Hi All,
    I want to skip the DELETE command on logical standby.
    DB Version - 10.2
    OS - Linux
    Primary DB and logical standby DB .
    In our DB schema some transaction tables. We delete data from those tables by delete commands.
    Delete command, also delete data from logical standby DB. But we want to skip on logical standby DB .
    I use following for that and get error.
    ALTER DATABASE STOP LOGICAL STANDBY APPLY;
    EXECUTE DBMS_LOGSTDBY.SKIP (stmt =>'DELETE TABLE', schema_name =>'TEST',object_name =>'TRANS',proc_name => null);
    ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;
    But I got error
    ERROR at line 1:
    ORA-06550: line 1, column 7:
    PLS-00306: wrong number or types of arguments in call to 'SKIP'
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    When I change stmt =>'DELETE TABLE' to stmt =>'DML', no error happen
    Please help me to solve this issue . This is urgent.
    Thanks in advance.
    Regards

    Dear aditi2,
    Actually it is so simple to understand the problem. Please read the following documentation and try to understand the SKIP procedure.
    http://download.oracle.com/docs/cd/B14117_01/appdev.101/b10802/d_lsbydb.htm#997290
    *SKIP Procedure*
    Use the SKIP procedure to define filters that prevent the application of SQL statements on the logical standby database.
    By default, all SQL statements executed on a primary database are applied to a logical standby database.
    If only a subset of activity on a primary database is of interest for application to the standby database,
    you can use the SKIP procedure to define filters that prevent the application of SQL statements on the logical standby database.
    While skipping (ignoring) SQL statements is the primary goal of filters,
    it is also possible to associate a stored procedure with a DDL filter so that runtime determinations can be made whether to skip the statement,
    execute this statement, or execute a replacement statement.
    Syntax
    DBMS_LOGSTDBY.SKIP (
         stmt                      IN VARCHAR2,
         schema_name               IN VARCHAR2,
         object_name               IN VARCHAR2,
         proc_name                 IN VARCHAR2,
         use_like                  IN BOOLEAN,
         esc                       IN CHAR1);Hope That Helps.
    Ogan
    Edited by: Ogan Ozdogan on 30.Tem.2010 13:03

  • Deadlock error on logical standby

    Hi All,
    I am get an issue where every thing is working fine on Db server but when it is getting replicated to Logical standby i am getting a deadlock error. Please find error logs below
    Fri May 20 21:00:56 2011
    ORA-00060: Deadlock detected. More info in file /u01/logicalstdby_home/product/admin/XXXXX/bdump/xxlog_p004_15175.trc.
    Fri May 20 21:00:56 2011
    8
    Errors in file /u01/logicalstdby_home/product/admin/XXXXX/bdump/xxlog_lsp0_2207.trc:
    ORA-12801: error signaled in parallel query server P004
    ORA-00060: deadlock detected while waiting for resource
    9
    ORA-12801: error signaled in parallel query server P004
    ORA-00060: deadlock detected while waiting for resource
    LOGSTDBY Analyzer process P003 pid=42 OS id=15173 stopped
    Please can anyone help in investigation.
    Thanks and Regrads,
    Amol

    Hi ,
    I have the logs from deadlock file.
    There are two queries in this dump. Does this mean that the two queries in the logs (which are actually same) are runing in parellel. Because this actually ran fine on the primary database.
    DEADLOCK DETECTED ( ORA-00060 )
    [Transaction Deadlock]
    The following deadlock is not an ORACLE error. It is a
    deadlock due to user error in the design of an application
    or from issuing incorrect ad-hoc SQL. The following
    information may aid in determining the deadlock:
    Deadlock graph:
    ---------Blocker(s)-------- ---------Waiter(s)---------
    Resource Name process session holds waits process session holds waits
    TX-01350024-00098ad3 44 804 X 46 797 S
    TX-012f0006-0008ac28 46 797 X 60 874 S
    TX-01340000-000a175c 60 874 X 44 804 S
    session 804: DID 0001-002C-0003E40C     session 797: DID 0001-002E-00002364
    session 797: DID 0001-002E-00002364     session 874: DID 0001-003C-0000019C
    session 874: DID 0001-003C-0000019C     session 804: DID 0001-002C-0003E40C
    Rows waited on:
    Session 797: obj - rowid = 00000000 - D/////AAaAAHqeAAAA
    (dictionary objn - 0, file - 26, block - 2008960, slot - 0)
    Session 874: obj - rowid = 00089976 - AAC5PjAAFAAAmj+AAA
    (dictionary objn - 563574, file - 5, block - 157950, slot - 0)
    Session 804: obj - rowid = 00089976 - AAC5PjAAFAAAmi3AAA
    (dictionary objn - 563574, file - 5, block - 157879, slot - 0)
    Information on the OTHER waiting sessions:
    Session 797:
    pid=46 serial=418 audsid=0 user: 0/SYS
    O/S info: user: oracle, term: UNKNOWN, ospid: 15180, machine: db5p
    program: oracle@db5p (P006)
    Current SQL Statement:
    update /*+ streams restrict_all_ref_cons */ "BEBSS"."SUBSCRIBER_POLICY_BROKER_EVENT" p set "ACTIVITY_TYPE"=decode(:1,'N',"ACTIVITY_TYPE",:2), "ATTRIBUTE_SET"=decode(:3,'N',"ATTRIBUTE_SET",:4), "CREATED_DATE"=decode(:5,'N',"CREATED_DATE",:6), "CUSTOMER_ID"=decode(:7,'N',"CUSTOMER_ID",:8), "FILE_NAME"=decode(:9,'N',"FILE_NAME",:10), "ID"=decode(:11,'N',"ID",:12), "LAST_MODIFIED_DATE"=decode(:13,'N',"LAST_MODIFIED_DATE",:14), "PORT_NUMBER"=decode(:15,'N',"PORT_NUMBER",:16), "PROCESSED_DATE"=decode(:17,'N',"PROCESSED_DATE",:18), "SERVICE_PACKAGE_ID"=decode(:19,'N',"SERVICE_PACKAGE_ID",:20), "STATUS"=decode(:21,'N',"STATUS",:22), "TRANSACTION_TYPE"=decode(:23,'N',"TRANSACTION_TYPE",:24) where (:25='N' or(decode(:26,'N','Y',decode(:27,"ACTIVITY_TYPE",'Y'))='Y' and decode(:28,'N','Y',decode(:29,"ATTRIBUTE_SET",'Y'))='Y' and decode(:30,'N','Y',decode(:31,"CREATED_DATE",'Y'))='Y' and decode(:32,'N','Y',decode(:33,"CUSTOMER_ID",'Y'))='Y' and decode(:34,'N','Y',decode(:35,"FILE_NAME",'Y'))='Y' and 1=1 and decode(:36,'N','Y',decode(:37,"LAST_MODIFIED_DATE",'Y'))='Y' and decode(:38,'N','Y',decode(:39,"PORT_NUMBER",'Y'))='Y' and decode(:40,'N','Y',decode(:41,"PROCESSED_DATE",'Y'))='Y' and decode(:42,'N','Y',decode(:43,"SERVICE_PACKAGE_ID",'Y'))='Y' and decode(:44,'N','Y',decode(:45,"STATUS",'Y'))='Y' and decode(:46,'N','Y',decode(:47,"TRANSACTION_TYPE",'Y'))='Y')) and(:48="ID")
    Session 874:
    pid=60 serial=20958 audsid=0 user: 0/SYS
    O/S info: user: oracle, term: UNKNOWN, ospid: 15182, machine: db5p
    program: oracle@db5p (P007)
    Current SQL Statement:
    update /*+ streams restrict_all_ref_cons */ "BEBSS"."SUBSCRIBER_POLICY_BROKER_EVENT" p set "ACTIVITY_TYPE"=decode(:1,'N',"ACTIVITY_TYPE",:2), "ATTRIBUTE_SET"=decode(:3,'N',"ATTRIBUTE_SET",:4), "CREATED_DATE"=decode(:5,'N',"CREATED_DATE",:6), "CUSTOMER_ID"=decode(:7,'N',"CUSTOMER_ID",:8), "FILE_NAME"=decode(:9,'N',"FILE_NAME",:10), "ID"=decode(:11,'N',"ID",:12), "LAST_MODIFIED_DATE"=decode(:13,'N',"LAST_MODIFIED_DATE",:14), "PORT_NUMBER"=decode(:15,'N',"PORT_NUMBER",:16), "PROCESSED_DATE"=decode(:17,'N',"PROCESSED_DATE",:18), "SERVICE_PACKAGE_ID"=decode(:19,'N',"SERVICE_PACKAGE_ID",:20), "STATUS"=decode(:21,'N',"STATUS",:22), "TRANSACTION_TYPE"=decode(:23,'N',"TRANSACTION_TYPE",:24) where (:25='N' or(decode(:26,'N','Y',decode(:27,"ACTIVITY_TYPE",'Y'))='Y' and decode(:28,'N','Y',decode(:29,"ATTRIBUTE_SET",'Y'))='Y' and decode(:30,'N','Y',decode(:31,"CREATED_DATE",'Y'))='Y' and decode(:32,'N','Y',decode(:33,"CUSTOMER_ID",'Y'))='Y' and decode(:34,'N','Y',decode(:35,"FILE_NAME",'Y'))='Y' and 1=1 and decode(:36,'N','Y',decode(:37,"LAST_MODIFIED_DATE",'Y'))='Y' and decode(:38,'N','Y',decode(:39,"PORT_NUMBER",'Y'))='Y' and decode(:40,'N','Y',decode(:41,"PROCESSED_DATE",'Y'))='Y' and decode(:42,'N','Y',decode(:43,"SERVICE_PACKAGE_ID",'Y'))='Y' and decode(:44,'N','Y',decode(:45,"STATUS",'Y'))='Y' and decode(:46,'N','Y',decode(:47,"TRANSACTION_TYPE",'Y'))='Y')) and(:48="ID")
    End of information on OTHER waiting sessions.
    Current SQL statement for this session:
    update /*+ streams restrict_all_ref_cons */ "BEBSS"."SUBSCRIBER_POLICY_BROKER_EVENT" p set "ACTIVITY_TYPE"=decode(:1,'N',"ACTIVITY_TYPE",:2), "ATTRIBUTE_SET"=decode(:3,'N',"ATTRIBUTE_SET",:4), "CREATED_DATE"=decode(:5,'N',"CREATED_DATE",:6), "CUSTOMER_ID"=decode(:7,'N',"CUSTOMER_ID",:8), "FILE_NAME"=decode(:9,'N',"FILE_NAME",:10), "ID"=decode(:11,'N',"ID",:12), "LAST_MODIFIED_DATE"=decode(:13,'N',"LAST_MODIFIED_DATE",:14), "PORT_NUMBER"=decode(:15,'N',"PORT_NUMBER",:16), "PROCESSED_DATE"=decode(:17,'N',"PROCESSED_DATE",:18), "SERVICE_PACKAGE_ID"=decode(:19,'N',"SERVICE_PACKAGE_ID",:20), "STATUS"=decode(:21,'N',"STATUS",:22), "TRANSACTION_TYPE"=decode(:23,'N',"TRANSACTION_TYPE",:24) where (:25='N' or(decode(:26,'N','Y',decode(:27,"ACTIVITY_TYPE",'Y'))='Y' and decode(:28,'N','Y',decode(:29,"ATTRIBUTE_SET",'Y'))='Y' and decode(:30,'N','Y',decode(:31,"CREATED_DATE",'Y'))='Y' and decode(:32,'N','Y',decode(:33,"CUSTOMER_ID",'Y'))='Y' and decode(:34,'N','Y',decode(:35,"FILE_NAME",'Y'))='Y' and 1=1 and decode(:36,'N','Y',decode(:37,"LAST_MODIFIED_DATE",'Y'))='Y' and decode(:38,'N','Y',decode(:39,"PORT_NUMBER",'Y'))='Y' and decode(:40,'N','Y',decode(:41,"PROCESSED_DATE",'Y'))='Y' and decode(:42,'N','Y',decode(:43,"SERVICE_PACKAGE_ID",'Y'))='Y' and decode(:44,'N','Y',decode(:45,"STATUS",'Y'))='Y' and decode(:46,'N','Y',decode(:47,"TRANSACTION_TYPE",'Y'))='Y')) and(:48="ID")
    ===================================================
    PROCESS STATE
    Process global information:
    process: 0x29c53bcc8, call: 0x29567f358, xact: 0x299db2d90, curses: 0x29c811dd8, usrses: 0x29c811dd8
    SO: 0x29c53bcc8, type: 2, owner: (nil), flag: INIT/-/-/0x00
    (process) Oracle pid=44, calls cur/top: 0x29567f358/0x29567eb18, flag: (0) -
    int error: 0, call error: 0, sess error: 0, txn error 0
    (post info) last post received: 0 0 117
    last post received-location: kcbzww
    last process to post me: 29c53fc08 42 0
    last post sent: 0 0 117
    last post sent-location: kcbzww
    last process posted by me: 29c53c4b0 188 0
    (latch info) wait_event=0 bits=0
    Process Group: DEFAULT, pseudo proc: 0x29f601e88
    O/S info: user: oracle, term: UNKNOWN, ospid: 15175
    OSD pid info: Unix process pid: 15175, image: oracle@db5p (P004)
    Dump of memory from 0x000000029C500F08 to 0x000000029C501110
    29C500F00 00000002 00000000 [........]
    29C500F10 9C811DD8 00000002 00000004 0003129B [................]
    29C500F20 8F34B7A0 00000002 0000001E 0003115B [..4.........[...]
    29C500F30 9CA03A98 00000002 0000000B 000313A7 [.:..............]
    29C500F40 9EBD0510 00000002 0000003D 0003115B [........=...[...]
    29C500F50 9C803260 00000002 00000004 0003129B [`2..............]
    29C500F60 75E66848 00000001 0000001E 0003115B [Hh.u........[...]
    29C500F70 99507DB0 00000002 00000007 000313A7 [.}P.............]
    29C500F80 99507F70 00000002 00000007 000313A7 [p.P.............]
    29C500F90 995083D0 00000002 00000007 000313A7 [..P.............]
    29C500FA0 99508CA8 00000002 00000007 000313A7 [..P.............]
    29C500FB0 995093C0 00000002 00000007 000313A7 [..P.............]
    29C500FC0 99509AC0 00000002 00000007 000313A7 [..P.............]
    29C500FD0 9950AC58 00000002 00000007 000313A7 [X.P.............]
    29C500FE0 9950B290 00000002 00000007 000313A7 [..P.............]
    29C500FF0 9950D6A0 00000002 00000007 000313A7 [..P.............]
    29C501000 994FDAB0 00000002 00000007 000313A7 [..O.............]
    29C501010 99510640 00000002 00000007 000313A7 [@.Q.............]
    29C501020 99510B80 00000002 00000007 000313A7 [..Q.............]
    29C501030 99510FE0 00000002 00000007 000313A7 [..Q.............]
    29C501040 99511298 00000002 00000007 000313A7 [..Q.............]
    29C501050 99511998 00000002 00000007 000313A7 [..Q.............]
    29C501060 99511A78 00000002 00000007 000313A7 [x.Q.............]
    29C501070 99511B58 00000002 00000007 000313A7 [X.Q.............]
    29C501080 99512350 00000002 00000007 000313A7 [P#Q.............]
    29C501090 99513248 00000002 00000007 000313A7 [H2Q.............]
    29C5010A0 99513408 00000002 00000007 000313A7 [.4Q.............]
    29C5010B0 99513788 00000002 00000007 000313A7 [.7Q.............]
    29C5010C0 9CA04DE8 00000002 0000000B 000313A7 [.M..............]
    29C5010D0 995144C0 00000002 00000007 000313A7 [.DQ.............]
    29C5010E0 99515038 00000002 00000007 000313A7 [8PQ.............]
    29C5010F0 995152D8 00000002 00000007 000313A7 [.RQ.............]
    29C501100 995159F0 00000002 00000007 000313A7 [.YQ.............]
    Thanks,
    Amol

  • Logical Standby table not supported 11.2.0.1

    I have a table with CLOB in primary and runs the SQL to determine which tables are unsupported.
    They, nor I, can see why this table is unsupported. Please let me know what I am missing.
    Are there additional steps to see why?
    Please also see the DDL for the table at the end.
    SQL> SELECT COLUMN_NAME,DATA_TYPE FROM DBA_LOGSTDBY_UNSUPPORTED WHERE OWNER='P_RPMX_AUDIT_DB' AND TABLE_NAME = 'AUDIT_TAB' ;
    COLUMN_NAME DATA_TYPE
    TABLE_SCRIPT CLOB
    SQL> SELECT OWNER FROM DBA_LOGSTDBY_SKIP WHERE STATEMENT_OPT = 'INTERNAL SCHEMA';
    OWNER
    DBSNMP
    SYS
    SYSTEM
    WMSYS
    ORDDATA
    OUTLN
    DIP
    EXFSYS
    XDB
    ORDPLUGINS
    ANONYMOUS
    APPQOSSYS
    ORDSYS
    SI_INFORMTN_SCHEMA
    XS$NULL
    15 rows selected.
    SQL> SELECT DISTINCT OWNER,TABLE_NAME FROM DBA_LOGSTDBY_UNSUPPORTED ORDER BY OWNER,TABLE_NAME;
    OWNER TABLE_NAME
    APG APG_REJECT_TAB
    APG ERR$_ACCOUNT
    APG ERR$_ACCOUNT_ADDRESS
    APG ERR$_ACCOUNT_ATTRIBUTES
    APG ERR$_ACCOUNT_CYCLE_HISTORY
    APG ERR$_ACCOUNT_USERS
    APG ERR$_ACCOUNT_XREFERENCE
    APG ERR$_ACTIONABLE_ITEMS
    APG ERR$_IDENTIFICATION
    APG ERR$_LOAD_RECON_METRICS
    APG ERR$_PHONE
    APG ERR$_POOL
    APG ERR$_POOL_ACCOUNTS
    APG ERR$_POOL_ACCOUNT_ENROLL_HISTO
    APG ERR$_USERS
    P_IM_EXTRACT_MASK ERR$_REWARDS_ACTIVITY
    P_IM_EXTRACT_MASK ERR$_REWARDS_TRANSACTION
    P_IM_EXTRACT_MASK ERR$_REWARDS_TRANSACTION_ITEM
    P_IM_EXTRACT_MASK ERR$_TRANSACTION
    P_RPMX_AUDIT_DB AUDIT_TAB
    P_RPMX_JOBS ERR$_ACCOUNT
    P_RPMX_JOBS ERR$_ACCOUNT_XREFERENCE
    22 rows selected.
    CREATE TABLE P_RPMX_AUDIT_DB.AUDIT_TAB
    TABLE_SCRIPT CLOB
    LOB (TABLE_SCRIPT) STORE AS (
    TABLESPACE P_RPMX_AUD_DB_DATA
    ENABLE STORAGE IN ROW
    CHUNK 8192
    RETENTION
    NOCACHE
    LOGGING
    STORAGE (
    INITIAL 1M
    NEXT 1M
    MINEXTENTS 1
    MAXEXTENTS UNLIMITED
    PCTINCREASE 0
    BUFFER_POOL DEFAULT
    FLASH_CACHE DEFAULT
    CELL_FLASH_CACHE DEFAULT
    TABLESPACE P_RPMX_AUD_DB_DATA
    RESULT_CACHE (MODE DEFAULT)
    PCTUSED 0
    PCTFREE 10
    INITRANS 1
    MAXTRANS 255
    STORAGE (
    INITIAL 1M
    NEXT 1M
    MINEXTENTS 1
    MAXEXTENTS UNLIMITED
    PCTINCREASE 0
    BUFFER_POOL DEFAULT
    FLASH_CACHE DEFAULT
    CELL_FLASH_CACHE DEFAULT
    LOGGING
    NOCOMPRESS
    NOCACHE
    NOPARALLEL
    MONITORING;
    Thanks, Chris

    Hi I was able to find the following answer. Thanks
    "Logical standby has never supported tables that only contain LOBs. We require some scalar column that can be used for row identification during update and delete processing.
    There is some discussion of row identification issues in section 4.1.2 of Oracle Data Guard Concepts and Administration. "
    http://docs.oracle.com/cd/E11882_01/server.112/e25608/create_ls.htm#i77026
    "If there is no primary key and no nonnull unique constraint/index, then all columns of bounded size are logged as part of the UPDATE statement to identify the modified row. All columns are logged except the following: LONG, LOB, LONG RAW, object type, and collections."
    So you see with only a LOB column it cannot identify the row. You need a primary key or at least some columns that can uniquely identify the row. The one LOB column is no logged with the supplemental logging.
    So it is not supported.

  • Stop/start logical standby db

    Version 10203 on AIX
    Have to stop/start logical standby db, new to data guard, Please confirm these are the steps to do that
    on primary db
    SQL > alter system switch logfile ;
    SQL > alter system archive log current ; ( to make sure current transactions come thru)
    check tail of alert log of standby to make sure these redologs shipped & mined
    standby db
    SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY; (stop SQL Apply)
    SQL> shutdown immediate;
    Lsnrctl stop listener_corp_remrpt-haprimary db
    SQL > shutdown immediate ;
    Lsnrctl stop listener_corp_remprd-ha
    Dont shutdown abort for any case, if both dbs are going down, first stop SQL apply on standby, take primary down and then take standby down)
    Startup
    primary
    SQL>startup;
    Lsnrctl start listener_corp_remprd-ha
    Standby
    SQL > startup
    SQL > alter database start logical standby apply immediate ;
    Lsnrctl start listener_corp_remrpt-ha

    Hi
    As you posted ,you are using Real Time Sql apply,So,it is LGWR who transfer changes to standby site.It is very safe to follow these steps for new user.
    1.Stop logical standby apply(Standby Database).
    2.Shutdown Primary Database.
    3.Shutdown logical standby Database.
    At startup
    1.Start Logical Standby Database.
    2.Start Primary Database.
    3.Start logical standby apply.
    At the case when primary database is taking long time to shutdown processed ,You can also use
    shutdown abort,but before doing abort be sure you have stop logical standby apply.When your primary database started,it automatically perform instance recovery.Primary site have to resolve gap in this case.
    At the case when you must have to perform shutdown abort at primary database,you can do it.By doing it you will not loose anything.Primary database has to resolve gap and it will take time to be consistent with primary site.
    Tinku

  • Logical Standby Apply became TOO SLOW !!

    Hi,
    I recently have setup a logical standby database. Everything was fine until the apply procedure on the standby became too slow:
    SQL> alter session set nls_date_format = 'HH24:MI:SS (MM/DD)';
    Session altered.
    SQL> SELECT APPLIED_SCN, APPLIED_TIME, READ_SCN, READ_TIME, NEWEST_SCN, NEWEST_TIME FROM DBA_LOGSTDBY_PROGRESS;
    APPLIED_SCN APPLIED_TIME READ_SCN READ_TIME NEWEST_SCN
    NEWEST_TIME
    3036960310 18:33:28 (05/31) 3035938077 18:12:43 (05/31) 3060387972
    16:30:16 (06/02)
    SQL>
    The applied time changed about 20 minutes during last 46 hours. v$logstdby says:
    COORDINATOR: ORA-16116: no work available
    READER, BUILDER and PREPARER: ORA-16127: stalled waiting for additional transactions to be applied
    All APPLIERs: ORA-16116: no work available
    I really don't have any idea about this issue. Any help will be appreciated.
    regards

    One reason could be the SQL Apply engine performs too many slow full table scans, check metalink note:
    Determining if SQL Apply Engine is Performing Full Table Scans
    Doc ID: Note:255958.1
    If this is the reason for the slowness you have to tune your DML statements.
    Werner

Maybe you are looking for

  • Recording songs to a cd

    It's hard getting information about Logic when you don't know all the answers. It seems these forums are really helpful and thought I'd see if anybody can help me out. I've already recorded and completed several songs and want to burn them to a cd. I

  • How to use form-login in iPlanet?

    Hi guys: I tried to use J2EE form-based login feature to trigger user authentication, but I can only specify the login page and the login error page, so how to redirector the location after user login successful? Thanks

  • Sales document delivery block histroy report

    Hi SD Gurus, I am running a report for particular sales org. for specified date range and with SO created date. After executing the report i see a field called "No. of days", which is calculated based on "DATE BLOCK History removed" minus  "DATE BLOC

  • Help restore some network settings

    I screwed up my network (wireless) I will save you the the long story of how/why, but I ended up having to reset the router. I've gone back in and restored all the settings, but I can't seem to get the Padlock next to my network name (before I had it

  • Windows 7 sees the 3GS (like a camera), but iTunes can't!

    So i finally get to upgrade from my crappy, beat-up iPhone 2G, which worked perfectly on my Windows 7 32-bit HP Mini, and bought an iPhone 3GS 32gb v3.1.2. The problem is, when i synced it, it was only recognized as a camera/ usb and not in iTunes. I