Starting Physically Standby Database in Mount Mode

Hi All
I have configured Data Guard using Oracle 10g 10.2.0.4.0 (64 bits) on Windows 2008 Server (64 bits) Release 2 Enterprise.
Data guard configuration was OK as the message from "Enable Configuration DG1" was "SUCCESS" for both
Primary and Standby Database. I have also set both Databases and TNS to start Automatically whenever Windows Starts.
The Problem is as long as the Standby Server is running, there is No issue.
But when we Restarts the Backup Server, Physically Standby Database is Started and TNS is also Started,
but Archives  are not received until I physically do the following steps so that it can received the Archives.
SQL> startup nomount;                                                                                                                
SQL> alter database mount standby database;                                                                 
SQL> alter database recover managed standby database disconnect from session;
Is there a way to start Physically Standby Database in Mount mode when windows started.
Regards
Thunder2777

Hi Mihael
I have created 2 files. 1 Bat file 2nd sql file which contains all commands as written above.
When I execute start.bat file
1. set ORACLE_HOME=C:\oracle\product\10.2.0\db_1
2. set ORACLE_SID=UMISBK
3. sqlplus / [email protected]
1 & 2 executed properly. At 3 it just display SQL help for login as shown below.
SQL*Plus: Release 10.2.0.4.0 - Production
Copyright (c) 1982, 2007, Oracle.  All Rights Reserved.
Usage 1: sqlplus -H | -V
    -H             Displays the SQL*Plus version and the usage help.
    -V             Displays the SQL*Plus version.
Usage 2: sqlplus [ [<option>] [<logon>] [<start>] ]
  <option> is: [-C <version>] [-L] [-M "<options>"] [-R <level>] [-S]
It Did Not execute start.sql file to excute sql commands.
Regards
Thunder2777

Similar Messages

  • Running a physical standby database in noarchivelog mode

    Primary Database: 2 node rac cluster, 11.2.0.2 GI and RDBMS
    Standby Database: single instance 11.2.0.2
    OS: AIX 7.1
    Hello,
    I'm in the process of implementing a data guard standby system. To make this system simpler to admin, I want to run the standby database in NOARCHIVELOG mode. This standby is used only as a mirror of production (to be copied to a 3rd site for separate user activity) and will never be switched to active mode. Maintaining another set of archive logs seems to be redundant to me and another point of failure, so I want to disable archiving. I wanted to ask if any of the DG experts on the forums have ever had experience with this? Does anyone know if this is recommended? I've searched the Oracle Data guard documentation online... it says that the primary obviously needs to be in archive mode, but I'm not seeing anything specific about the standby. Please let me know if anyone has experience with this.
    Thanks

    Hello again;
    If this is the case, then I have nothing to worry about here. Does that sound right to you?Yes.
    For this :
    b) monthly, shutdown this system and copy it to a 3rd site to host a separate set of business activityI would consider RMAN Duplicate in which case you may avoid the shutdown.
    And for this :
    resync the "mirror" with productionAll you have to do if DEFER the primary to the standby, then ENABLE and Data Guard will catch up.
    --- Will post a detailed example here in a moment.
    Right at the first of the year they wanted to work on our Primary server room ( Power ). What I did was switchover to the Standby but I kept log_archive_dest_state_2 on the new primary set to DEFER. Then I shutdown
    all the databases at the Primary site. At the end of work two days later I started the databases at the Primary site in standby mode. Switched log_archive_dest_state_2 to ENABLE. When the databases were back in SYNC
    I did another switchover and it was done. I used TAF and none of the users even noticed.
    Best Regards
    mseberg

  • How Auto starting Physical Standby Database ( when Server Restart)

    Dear All(s)
    I have configure oracle (10.2.0) dataguard on production database, some time server restart due to power disconnectivity, i want to restard dataguard when server restart. i am using Server 2003 32bit. Guide me how i can run following commands when server restart.
    SQL> connect/as sysdba
    SQL> Startup mount;
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
    Thanks in Advance

    i want to run these command each time when server restart.Yes, I did understand that... but what's the problem ? can't you schedule a task when the server starts ?

  • Ora-38500 physical standby database not started

    hiiii,
    When i executed the command at physical standby database server.
    it give error:
    To start real-time apply:
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
    2> USING CURRENT LOGFILE;
    Error at line 1:
    ORA: 38500 using current logfile option not available without stand.
    please help me how could i start physical standby database
    Regards
    Vaibhav Dixit

    Hi Vaibhav,
    What exactly do you want to do?
    Alter database recover managed standby database; --->it will be in Manged Recovery mode.
    Alter database mount standby database; ----> it will be mounted, but no log files applies.
    Alter database open read only; ----> it will be open with read only option, but archeive logs will NOT be applied
    If you want to apply the Archive logs which are trasfered from Primary, then you need to fire the below commands
    Alter database recover managed standby database;
    Alter database recover managed standby database using current logfile;
    Alter database recover managed standby database using current logfile disconnect from session;
    To stop applying archives then,
    Alter database recover managed standby database cancel;
    Thanks and Regards.
    tnaresh1982

  • How to open a "manual" Physical standby database in read/write mode

    Hi,
    I am running Oracle Database 10g Release 10.2.0.3.0 - 64bit Production Standard Edition on Linux version 2.6.9-42.0.8.ELsmp ([email protected]) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-3))
    I've created a physical standby database, but since I am running Standard Edition, I am not using the DataGuard features. I use the rsync utility to copy over the archivelogs to the standby database, and I apply them periodically to the standby database.
    The standby database is started this way :
    startup nomount pfile='/u01/oradata/orcl/initorcl.stdby';
    alter database mount standby database;
    Everything runs perfectly fine, I can do "alter database open read only" and then I can do selects into tables to confirm that everything is up to date.
    The thing is, if I shutdown immediate the database, then do just startup :
    shutdown immediate;
    startup;
    The database opens with no error messages, but is still in read-only mode...
    I read that the default behavior for a standby database is to open read-only, like I am experiencing, but I would like to know what is the right way to open it correctly in read-write mode (I understand that after that, my standby will not be standby anymore and that I will have to recreate my standby database).
    Thanks,
    Mat

    Hello,
    There're features which allows you to open a Standby database in Read/Write mode but for all I know
    it needs Entreprise Edition.
    In Enterprise Edition you can use Logical Standby database. More over, for Physical standby there's
    a way by using flashback database so as to rolling backward the database and avoiding to recreate
    the Standby.
    In Standard Edition I'm afraid that you'll have to recreate your Standby database.
    Best regards,
    Jean-Valentin

  • Physical Standby Database (Protection Mode)?!!

    Hi,
    I have configured a physical standby database to use Real-time Apply, but i noticed that the protection mode of the database has been changed from "Maximum Performance" to ''Maximum Availability"..
    log_archive_dest_3='service=phystby OPTIONAL LGWR SYNC AFFIRM reopen=120 valid_for=(online_logfiles,primary_role) db_unique_name=phystby'
    Any body to explaine??
    Regards,

    LGWR SYNC AFFIRM
    These are the options are used in maximum protection  mode ,in which oracle will write the information in both the server(primary and standby) and this write occurs at same time.
    oracle write the information in online redo logfile of both the server simultaneously.
    and this option ensure no data loss will occurs if primary will fail.
    SYNC related with Network transmission mode.
    AFFIRM related with disk write option.
    LGWR describe Redo archival process.
    Thanks
    Kuljeet                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Physical standby database standby redo log problem

    Hello
    We have a physical standby database , I've created some standby redo log files but my problem is that they aren't used,
    their status in v$stanby_log view is UNASSIGNED
    and I see this message (ORA-16086: standby database does not contain available standby log files) in primary database alert_log file
    while when I run "alter system switch logfile" in the primary database it transfer redo logs to the physsical standby database
    and archive log file will be created in standby database
    I've even recreated the standby redo log files and I added new ones to them but the problem wasn't solved
    Do you know what is problem ?
    elect group#,THREAD#,BYTES,STATUS from V$STANDBY_LOG;
    group#     THREAD#      BYTES       STATUS
    1                   0                   524288000                   UNASSIGNED                  
    2                   0                   524288000                   UNASSIGNED                  
    3                   0                   524288000                   UNASSIGNED                  
    8                   0                   524288000                   UNASSIGNED                  
    9                   0                   524288000                   UNASSIGNED                  
    10                   0                   524288000                   UNASSIGNED                  
    select group#,THREAD#,BYTES,MEMBERS,STATUS from v$log;
    group#                    THREAD#                    BYTES                    MEMBERS                    STATUS
    4                   1                   524288000                   2                   CLEARING                  
    7                   1                   524288000                   2                   CLEARING_CURRENT                  
    6                   1                   524288000                   2                   CLEARING                  
    5                   1                   524288000                   2                   CLEARING                  
    thanks

    Hello Anurag
    Thank you for your reply
    I have found some issue in the standby database alert_log too , in the standby database alert_log it has been written:
    RFS[782]: Assigned to RFS process 3919
    RFS[782]: Identified database type as 'physical standby'
    Primary database is in MAXIMUM AVAILABILITY mode
    Standby controlfile consistent with primary
    Primary database is in MAXIMUM AVAILABILITY mode
    Standby controlfile consistent with primary
    RFS[782]: No standby redo logfiles selected (reason:6)
    Sun Jan 31 13:59:43 2010
    Errors in file /u01/app/oracle/admin/tehrep/udump/tehrep_rfs_3919.trc:
    ORA-16086: standby database does not contain available standby log files
    Sun Jan 31 13:59:48 2010
    RFS[781]: Archived Log: '/disks/sda/tehrep/archivelogs/1_6516_670414641.dbf'
    Sun Jan 31 13:59:50 2010
    and the context "/u01/app/oracle/admin/tehrep/udump/tehrep_rfs_3919.trc"  is below :
    +/u01/app/oracle/admin/tehrep/udump/tehrep_rfs_3919.trc+
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning, OLAP and Data Mining options
    ORACLE_HOME = /u01/app/oracle/product/10.2.0/db_1
    System name:    Linux
    Node name:      linserver2.com
    Release:        2.6.9-42.ELsmp
    Version:        #1 SMP Wed Jul 12 23:27:17 EDT 2006
    Machine:        i686
    Instance name: tehrep
    Redo thread mounted by this instance: 1
    Oracle process number: 58
    Unix process pid: 3919, image: [email protected]
    *** SERVICE NAME:() 2010-01-31 13:59:43.865
    *** SESSION ID:(109.1225) 2010-01-31 13:59:43.865
    KCRRFLAS
    KCRRSNPS
    No space in recovery area for active standby redo logs
    The primary database is operating in MAXIMUM PROTECTION
    or MAXIMUM AVAILABILITY mode, and the standby database
    does not contain adequate disk space in the recovery area
    to safely archive the contents of the standby redo logfiles.
    ORA-16086: standby database does not contain available standby log files
    when I saw this line "No space in recovery area for active standby redo logs" I thought that STANDBY_ARCHIVE_DEST parameter points where that there is no enough space , but when I consider I found out that points a directory on disk a "sda" that has enough space , I don't know what that means
    by the way, at below I've written a section of the primary database alert_log context and "lgwr" trace file around Sun Jan 31 13:30:34 2010
    alert_log :
    ORA-16086: standby database does not contain available standby log files
    Sun Jan 31 13:30:34 2010
    LGWR: Failed to archive log 7 thread 1 sequence 6512 (16086)
    Thread 1 advanced to log sequence 6512
    Current log# 7 seq# 6512 mem# 0: /disks/sdb/tehrep/redo71.log
    Current log# 7 seq# 6512 mem# 1: /disks/sdd/tehrep/redo72.log
    LNSc started with pid=53, OS id=11451
    Sun Jan 31 13:36:34 2010
    Errors in file /u01/app/oracle/admin/tehrep/bdump/tehrep_lgwr_3692.trc:
    ORA-16086: standby database does not contain available standby log files
    Sun Jan 31 13:36:34 2010
    LGWR: Failed to archive log 5 thread 1 sequence 6513 (16086)
    Thread 1 advanced to log sequence 6513
    Current log# 5 seq# 6513 mem# 0: /disks/sdb/tehrep/redo51.log
    Current log# 5 seq# 6513 mem# 1: /disks/sdd/tehrep/redo52.log
    */u01/app/oracle/admin/tehrep/bdump/tehrep_lgwr_3692.trc file :*
    Error 16086 creating standby archive log file at host '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com
    +)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated)))'+
    *** 2010-01-31 13:30:34.712 60679 kcrr.c
    LGWR: Attempting destination LOG_ARCHIVE_DEST_3 network reconnect (16086)
    *** 2010-01-31 13:30:34.712 60679 kcrr.c
    LGWR: Destination LOG_ARCHIVE_DEST_3 network reconnect abandoned
    ORA-16086: standby database does not contain available standby log files
    *** 2010-01-31 13:30:34.712 60679 kcrr.c
    LGWR: Error 16086 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com)(PORT=1521
    +)))(CONNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated)))'+
    *** 2010-01-31 13:30:34.712 58941 kcrr.c
    kcrrfail: dest:3 err:16086 force:0 blast:1
    Receiving message from LNSc
    *** 2010-01-31 13:30:34.718 55444 kcrr.c
    Making upidhs request to LNSc (ocis 0x0xb648db48). Begin time is <01/31/2010 13:30:30> and NET_TIMEOUT <180> seconds
    NetServer pid:11196
    *** 2010-01-31 13:30:38.718 55616 kcrr.c
    upidhs done status 0
    *** 2010-01-31 13:36:31.062
    LGWR: Archivelog for thread 1 sequence 6513 will NOT be compressed
    *** 2010-01-31 13:36:31.062 53681 kcrr.c
    +Initializing NetServer[LNSc] for dest=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com)(PORT=1521)))(CO+
    NNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated))) mode SYNC
    LNSc is not running anymore.
    New SYNC LNSc needs to be started
    Waiting for subscriber count on LGWR-LNSc channel to go to zero
    Subscriber count went to zero - time now is <01/31/2010 13:36:31>
    Starting LNSc ...
    Waiting for LNSc to initialize itself
    *** 2010-01-31 13:36:34.116 53972 kcrr.c
    +Netserver LNSc [pid 11451] for mode SYNC has been initialized+
    Performing a channel reset to ignore previous responses
    +Successfully started LNSc [pid 11451] for dest (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com)(PORT=1+
    +521)))(CONNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated))) mode SYNC ocis=0x0xb648db48+
    *** 2010-01-31 13:36:34.116 54475 kcrr.c
    +Making upiahm request to LNSc [pid 11451]: Begin Time is <01/31/2010 13:36:31>. NET_TIMEOUT = <180> seconds+
    Waiting for LNSc to respond to upiahm
    *** 2010-01-31 13:36:34.266 54639 kcrr.c
    upiahm connect done status is 0
    Receiving message from LNSc
    Receiving message from LNSc
    Destination LOG_ARCHIVE_DEST_3 is in STANDBY RESYNCHRONIZATION mode
    Receiving message from LNSc

  • Physical standby database implementation

    Hi!
    I am trying to implement a Physical standby database, I have already done it with both the primary and secondary in the same server and successfully shipped the logs and have it configured using Data Guard.
    But Now I am trying to implement the Physical standby in a separate server, but the logs are not getting shipped, I am using Oracle 9i Enterprise edition. I have checked all the steps, but not able to find the reason, why the logs are not getting shipped to the standby.
    Also I am not able to discover the Primary node from the Standby and I have Windows 2003 server in my standby and Windows XP Prof. in the Primary, Is this the reason, why my logs are not getting shipped?
    Please help. Thanks in Advance.
    Radhika

    Hi!,
    Thanks for ur response, I am posting my alert log here... can u please help me... I probably think it is the OS issue too... Your inputs are greatly appreciated...
    Thanks
    Radhika
    Fri Feb 10 18:21:19 2006
    Errors in file d:\oracle\admin\bsnl\bdump\bsnl_arc0_1668.trc:
    ORA-12535: TNS:operation timed out
    Dump file d:\oracle\admin\bsnl\bdump\alert_bsnl.log
    Mon Feb 13 11:04:59 2006
    ORACLE V9.2.0.1.0 - Production vsnsta=0
    vsnsql=12 vsnxtr=3
    Windows 2000 Version 5.2 Service Pack 1, CPU type 586
    Mon Feb 13 11:04:59 2006
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    SCN scheme 2
    Using log_archive_dest parameter default value
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    Starting up ORACLE RDBMS Version: 9.2.0.1.0.
    System parameters with non-default values:
    processes = 150
    timed_statistics = TRUE
    shared_pool_size = 50331648
    large_pool_size = 8388608
    java_pool_size = 33554432
    control_files = D:\oracle\oradata\BSNL\CONTROL01.CTL, D:\oracle\oradata\BSNL\CONTROL02.CTL, D:\oracle\oradata\BSNL\CONTROL03.CTL
    db_block_size = 8192
    db_cache_size = 25165824
    compatible = 9.2.0.0.0
    log_archive_start = TRUE
    log_archive_dest_1 = location=D:\oracle\oradata\BSNL_LOG mandatory
    log_archive_dest_2 = service=dbabsnl
    log_archive_dest_state_2 = ENABLE
    db_file_multiblock_read_count= 16
    fast_start_mttr_target = 300
    undo_management = AUTO
    undo_tablespace = UNDOTBS1
    undo_retention = 10800
    remote_login_passwordfile= EXCLUSIVE
    db_domain =
    instance_name = BSNL
    dispatchers = (PROTOCOL=TCP) (SERVICE=BSNLXDB)
    job_queue_processes = 10
    hash_join_enabled = TRUE
    background_dump_dest = D:\oracle\admin\BSNL\bdump
    user_dump_dest = D:\oracle\admin\BSNL\udump
    core_dump_dest = D:\oracle\admin\BSNL\cdump
    sort_area_size = 524288
    db_name = BSNL
    open_cursors = 300
    star_transformation_enabled= FALSE
    query_rewrite_enabled = FALSE
    pga_aggregate_target = 25165824
    aq_tm_processes = 1
    PMON started with pid=2
    DBW0 started with pid=3
    LGWR started with pid=4
    CKPT started with pid=5
    SMON started with pid=6
    RECO started with pid=7
    CJQ0 started with pid=8
    QMN0 started with pid=9
    Mon Feb 13 11:05:07 2006
    starting up 1 shared server(s) ...
    starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
    ARCH: STARTING ARCH PROCESSES
    ARC0 started with pid=12
    ARC0: Archival started
    ARC1 started with pid=13
    Mon Feb 13 11:05:08 2006
    ARC1: Archival started
    Mon Feb 13 11:05:09 2006
    ARCH: STARTING ARCH PROCESSES COMPLETE
    ARC1: Thread not mounted
    Mon Feb 13 11:05:09 2006
    ARC0: Thread not mounted
    Mon Feb 13 11:05:10 2006
    alter database mount exclusive
    Mon Feb 13 11:05:16 2006
    Successful mount of redo thread 1, with mount id 1399936614.
    Mon Feb 13 11:05:16 2006
    Database mounted in Exclusive Mode.
    Completed: alter database mount exclusive
    Mon Feb 13 11:05:16 2006
    alter database open
    Mon Feb 13 11:05:18 2006
    Beginning crash recovery of 1 threads
    Mon Feb 13 11:05:19 2006
    Started first pass scan
    Mon Feb 13 11:05:21 2006
    Completed first pass scan
    3956 redo blocks read, 68 data blocks need recovery
    Mon Feb 13 11:05:21 2006
    Started recovery at
    Thread 1: logseq 18, block 9151, scn 0.0
    Recovery of Online Redo Log: Thread 1 Group 2 Seq 18 Reading mem 0
    Mem# 0 errs 0: D:\ORACLE\ORADATA\BSNL\REDO02.LOG
    Mon Feb 13 11:05:23 2006
    Ended recovery at
    Thread 1: logseq 18, block 13107, scn 0.967486
    68 data blocks read, 68 data blocks written, 3956 redo blocks read
    Crash recovery completed successfully
    Mon Feb 13 11:05:28 2006
    LGWR: Primary database is in CLUSTER CONSISTENT mode
    Thread 1 advanced to log sequence 19
    Thread 1 opened at log sequence 19
    Current log# 3 seq# 19 mem# 0: D:\ORACLE\ORADATA\BSNL\REDO03.LOG
    Successful open of redo thread 1.
    Mon Feb 13 11:05:33 2006
    SMON: enabling cache recovery
    Mon Feb 13 11:05:33 2006
    ARC0: Evaluating archive log 2 thread 1 sequence 18
    ARC0: Beginning to archive log 2 thread 1 sequence 18
    Creating archive destination LOG_ARCHIVE_DEST_2: 'dbabsnl'
    Mon Feb 13 11:05:36 2006
    Undo Segment 1 Onlined
    Undo Segment 2 Onlined
    Undo Segment 3 Onlined
    Undo Segment 4 Onlined
    Undo Segment 5 Onlined
    Undo Segment 6 Onlined
    Undo Segment 7 Onlined
    Undo Segment 8 Onlined
    Undo Segment 9 Onlined
    Undo Segment 10 Onlined
    Successfully onlined Undo Tablespace 1.
    Mon Feb 13 11:05:36 2006
    SMON: enabling tx recovery
    Mon Feb 13 11:05:36 2006
    Database Characterset is WE8MSWIN1252
    Mon Feb 13 11:05:47 2006
    replication_dependency_tracking turned off (no async multimaster replication found)
    Completed: alter database open
    Mon Feb 13 11:05:55 2006
    ARC0: Error 12535 Creating archive log file to 'dbabsnl'
    Mon Feb 13 11:05:56 2006
    Errors in file d:\oracle\admin\bsnl\bdump\bsnl_arc0_1596.trc:
    ORA-12535: TNS:operation timed out
    Creating archive destination LOG_ARCHIVE_DEST_1: 'D:\ORACLE\ORADATA\BSNL_LOG\ARC00018.001'
    ARC0: Completed archiving log 2 thread 1 sequence 18

  • Physical standby database error

    Hi,
    I try to create physical standby in my local machine using oracle 10g
    version :10.2.0.1.0
    Os: windows xp.
    I followed steps and parameter files
    on primary :-
    sql>alter database force logging;
    orcl.__db_cache_size=155189248
    orcl.__java_pool_size=4194304
    orcl.__large_pool_size=4194304
    orcl.__shared_pool_size=75497472
    orcl.__streams_pool_size=0
    *.audit_file_dest='D:\oracle\product\10.2.0/admin/orcl/adump'
    *.background_dump_dest='D:\oracle\product\10.2.0/admin/orcl/bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='D:\oracle\product\10.2.0\oradata\orcl\control01.ctl','D:\oracl
    e\product\10.2.0\oradata\orcl\control02.ctl','D:\oracle\product\10.2.0\orad
    ata\orcl\control03.ctl'
    *.core_dump_dest='D:\oracle\product\10.2.0/admin/orcl/cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_name='orcl'
    *.db_unique_name='orcl'
    *.log_archive_config='DG_CONFIG=(orcl,stby)'
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=orclXDB)'
    *.job_queue_processes=10
    *.open_cursors=300
    *.pga_aggregate_target=80740352
    *.processes=150
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=244318208
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='D:\oracle\product\10.2.0/admin/orcl/udump'
    *.log_archive_dest_1='LOCATION=D:\oracle\archive
    VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=orcl'
    *.log_archive_dest_2='SERVICE=stby LGWR ASYNC
    VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=stby'
    *.log_archive_format=%t_%s_%r.arc
    *.log_archive_dest_state_1=ENABLE
    *.log_archive_dest_state_2=ENABLE
    On standby
    orcl.__db_cache_size=155189248
    orcl.__java_pool_size=4194304
    orcl.__large_pool_size=4194304
    orcl.__shared_pool_size=75497472
    orcl.__streams_pool_size=0
    *.audit_file_dest='D:\stby\adump'
    *.background_dump_dest='D:\stby\bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='D:\stby\ctrl.ctl'
    *.core_dump_dest='D:\stby\cdump'
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_name='orcl'
    *.db_unique_name='stby'
    *.log_archive_config='DG_CONFIG=(orcl,stby)'
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=orclXDB)'
    *.job_queue_processes=10
    *.open_cursors=300
    *.pga_aggregate_target=80740352
    *.processes=150
    *.remote_login_passwordfile='NONE'
    *.sga_target=244318208
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='D:\stby\udump'
    *.db_file_name_convert='D:\oracle\product\10.2.0\oradata\orcl','D:\stby'
    *.log_file_name_convert='D:\oracle\product\10.2.0\oradata\orcl','D:\stby'
    *.log_archive_dest_1='LOCATION=D:\oracle\archive
    VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=stby'
    *.log_archive_dest_2='SERVICE=orcl LGWR ASYNC
    VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
    DB_UNIQUE_NAME=orcl'
    *.standby_archive_dest='D:\stby\archive'
    *.log_archive_dest_state_1=ENABLE
    *.log_archive_dest_state_2=ENABLE
    *.standby_file_management='AUTO'
    *.fal_server='orcl'
    *.fal_client='stby'
    SQL> conn / as sysdba
    Connected to an idle instance.
    SQL> startup pfile=D:\stby\initstby.ora nomount;
    ORACLE instance started.
    Total System Global Area 247463936 bytes
    Fixed Size 1248332 bytes
    Variable Size 79692724 bytes
    Database Buffers 159383552 bytes
    Redo Buffers 7139328 bytes
    SQL> alter database mount standby database;
    Database altered.
    SQL> alter database recover managed standby database disconnect from session;
    Database altered.
    SQL> alter database open read only;
    alter database open read only
    ERROR at line 1:
    ORA-01154: database busy. Open, close, mount, and dismount not allowed now
    SQL> recover managed standby database cancel;
    Media recovery complete.
    SQL> alter database open read only;
    Database altered.
    SQL> select sequence#,first_time,next_time from v$archived_log order by sequence
    no rows selected
    No archive s generated in standby ..
    what i mistake.
    Reagrds
    S.Azar

    Anand... wrote:
    Firstly you can use "*select sequence#,first_time,next_time from v$archived_log order by sequence#;"* command in mount stage itself.No need to open the standby database in ready only mode.
    No rows selected in mount stage also.
    The V$ARCHIVED_LOG fixed view on the physical standby database shows all the archived redo log files received from the primary database.
    sql> select * from v$archived_log;
    no rows selected.
    and No archived logs received from primary database to physical standby . i think here i wrongly configure parameter file.
    sql> RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION; -- > start Redo Apply
    When you do log switch on the primary are the archive logs getting transferred to the standby database???Is there some error in the alert log file in the primary database.
    No..
    >
    [http://advait.wordpress.com/2007/06/12/setting-up-oracle-dataguard-for-10g/]
    Regards
    S.Azar

  • Error while trying to open physical standby database - (DATA GUARD)

    Hi Everyone,
    I have problems in opening the database of the physical standby in read- write mode/ read only mode. I have a primary server which is running on 2 node RAC and the standby on a seperate single server being used as DR. I recently got this server and my aim was to isolate the standby server from primary server and perform few test. As it has never been tested even once.
    Primary Database spec: (2 Node Rac on ASM)
    Oracle Version : 10.2.0.3.0
    O/s : HP-UX B.11.23
    Standby Database spec: (Single Node)
    Oracle Version : 10.2.0.3.0
    O/s: HP-UX db01 B.11.23
    Error:
    alter database recover managed standby database cancel;
    Database altered.
    SQL> alter database open
    2 ;
    alter database open
    ERROR at line 1:
    ORA-16004: backup database requires recovery
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '+DATA/dprod/datafile/system01.dbf'
    Parameters :
    log_archive_dest_2 string SERVICE=PROD1 LGWR ASYNC VALID
    FOR=(ONLINELOGFILES,PRIMARY_
    ROLE) DB_UNIQUE_NAME=PROD
    remote_archive_enable string true
    fal_client string DPROD
    fal_server string PROD1, PROD2
    Steps tried so far:
    Changed log_archive_dest_2 = DEFER on both the primary nodes
    Standby :
    startup nomount
    alter database mount standby database;
    alter database recover managed standby database disconnect;
    alter database recover managed standby database cancel;
    alter database open/readonly (tried both)
    Same error.
    On Primary:
    SQL> select max(sequence#) from v$log_history;
    MAX(SEQUENCE#)
    55702
    on Standby:
    MAX(SEQUENCE#)
    33289
    Primary Database:
    SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
    SEQUENCE# FIRST_TIME NEXT_TIME
    55700 13-JUN-11 13-JUN-11
    55700 13-JUN-11 13-JUN-11
    55701 13-JUN-11 13-JUN-11
    55701 13-JUN-11 13-JUN-11
    55702 13-JUN-11 13-JUN-11
    60824 rows selected.
    Standby Database:
    SEQUENCE# FIRST_TIME NEXT_TIME
    55698 13-JUN-11 13-JUN-11
    55699 13-JUN-11 13-JUN-11
    55700 13-JUN-11 13-JUN-11
    55701 13-JUN-11 13-JUN-11
    15206 rows selected.
    Additional Information :
    There is a delay of 20 minutes before the logs get applied. which has been intentional set by team.
    Any help will be highly appreciated. Thanks in advance
    Sadiq

    Hi,
    Primary Database:
    select status,checkpoint_count from v$datafile_header;
    STATUS CHECKPOINT_COUNT
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    STATUS CHECKPOINT_COUNT
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 672472065
    ONLINE 59736
    ONLINE 59736
    ONLINE 59736
    ONLINE 59736
    ONLINE 59736
    STATUS CHECKPOINT_COUNT
    ONLINE 57717
    ONLINE 57717
    57 rows selected.
    Standby Database;
    select status,checkpoint_count from v$datafile_header;
    STATUS CHECKPOINT_COUNT
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445072
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    STATUS CHECKPOINT_COUNT
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 672445071
    ONLINE 32742
    ONLINE 32742
    ONLINE 32742
    ONLINE 32742
    ONLINE 32742
    STATUS CHECKPOINT_COUNT
    ONLINE 30723
    ONLINE 30723
    57 rows selected.
    Archieve log list :
    Primary database:
    SQL> archive log list
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence 49110
    Next log sequence to archive 49111
    Current log sequence 49111
    Standby Database:
    SQL> archive log list;
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence 49110
    Next log sequence to archive 0
    Current log sequence 49111
    I tried log switch multiple times in primary database i saw that its getting highlighted in standby database.

  • Problem creating physical Standby database with RMAN

    Hi All
    I am trying to learn oracle dataguard and as part of the process learning creating standby database.
    Platform : Sun-Fire-V250 Sparc, Solaris 10
    Database Version - Oracle 11R2
    I am creating standby database on same server, so directory structure is different.
    Following the instructions on Oracle site I managed to create a functional physical standby database. But I am not able to create standby database using RMAN. These are the steps that I followed-
    1.Set up all necessary parameters on primary database as done while creating physical standby database manually, eg setting force logging, creating standby logs etc.
    2.Edited parameter file on primary database as done while creating manual pysical standby database creation. Some of the changes done are-
    On Primary Database:
    *.FAL_CLIENT='orcl11020' #Primary database unique name
    *.FAL_SERVER='stdby_11' #Standby database unique name
    db_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020'
    log_file_name_convert='/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11/redo_mem','/<dir>/oradata/orcl11020/redo_mem'
    standby_file_management=auto
    *.log_archive_config='DG_CONFIG=(orcl11020,stdby_11)'
    *.log_archive_dest_1='LOCATION=/<dir>/flash_recovery_area/ORCL11020/archivelog
    VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=orcl11020'
    *.log_archive_dest_2='SERVICE=stdby_11 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) db_unique_name=stdby_11'
    *.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
    *.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
    *.LOG_ARCHIVE_FORMAT='%t_%s_%r.arc'
    *.LOG_ARCHIVE_MAX_PROCESSES=30
    Copied same pfile for standby database and modified following-
    *.control_files='/<dir>/oradata/stdby_11/stdby_11.ctl','/<dir>/fra_stdby/stdby_11/stdby_11.ctl'
    *.db_name='orcl1102'
    *.db_unique_name='stdby_11'
    *.FAL_CLIENT='stdby_11'
    *.FAL_SERVER='orcl11020'
    db_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11'
    log_file_name_convert='/<dir>/oradata/orcl11020','/<dir>/oradata/stdby_11','/<dir>/oradata/orcl11020/redo_mem','/<dir>/oradata/stdby_11/redo_mem'
    standby_file_management=auto
    *.log_archive_dest_1='LOCATION=/<dir>/fra_stdby/STDBY_11/archivelog
    VALID_FOR=(ALL_LOGFILES,ALL_ROLES) db_unique_name=stdby_11'
    *.log_archive_dest_2='SERVICE=orcl11020 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
    db_unique_name=orcl11020'
    3. Add relevant information in tnsnames.ora and listener.ora files and then restart listener.
    3. Created password file with same credential as primary database.
    4.Up-to-date RMAN backup of primary database available.
    5.Create standby controlfile with rman
    While primary database s open (I tried with primary database in mount mode as well)-
    $>rman catalog rman/paswd@rman target /
    RMAN> BACKUP CURRENT CONTROLFILE FOR STANDBY;
    6. Open a new terminal and startup standby database in nomount mode using parameter file created -
    $>ORACLE_SID=stdby_11
    $>export ORACLE_SID
    $>sqlplus / as sysdba
    SQL>STARTUP NOMOUNT pfile='<location/initfilename.ora'
    SQL>quit
    $> rman AUXILIARY / target sys/passwd@orcl11020 catalog rman/passwd@rman
    RMAN>DUPLICATE TARGET DATABASE FOR STANDBY DORECOVER;
    RMAN finishes without error but archive logs are not being tranported. Looking at the log, following caught my eye-
    Error 1017 received logging on to the standby
    Check that the primary and standby are using a password file
    and remote_login_passwordfile is set to SHARED or EXCLUSIVE,
    and that the SYS password is same in the password files.
    returning error ORA-16191
    FAL[client, ARC2]: Error 16191 connecting to orcl11020 for fetching gap sequence
    Errors in file /<>dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
    ORA-16191: Primary log shipping client not logged on standby
    Errors in file /<dir>/diag/rdbms/stdby_11/stdby_11/trace/stdby_11_arc2_24321.trc:
    ORA-16191: Primary log shipping client not logged on standby
    So on both primary and standby I confirmed
    SQL> show parameter remote_login_passwordfile
    NAME TYPE VALUE
    remote_login_passwordfile string EXCLUSIVE
    To make double sure that password files are same, I shutdown both databases, delete password files and recreated with same credentials.
    Password files are called - orapworcl11020 and orapwstdby_11
    Can someone guide me where thisngs are going wrong here please.

    Not sure if I understood it clearly.
    SELECT * FROM V$ARCHIVE_GAP;
    returns no rows so there is no gap.
    But could you please explain me the result of the previous query. To catch up again, on standby when I check
    SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
    SEQUENCE# APPLIED
    75 NO
    74 NO
    76 NO
    77 NO
    I understand that though archive files have been copied across but they are not applied yet.
    On primary when I give your query -
    SELECT name as STANDBY,SEQUENCE#,applied, completion_time
    2 FROM v$archived_log
    3 where dest_id=2
    4 and sequence# BETWEEN 74 and 80;
    I get -
    STANDBY SEQUENCE# APPLIED COMPLETIO
    stdby_11 74 YES 28-JUN-11
    stdby_11 75 YES 28-JUN-11
    stdby_11 76 YES 29-JUN-11
    stdby_11 77 YES 29-JUN-11
    stdby_11 78 YES 29-JUN-11
    stdby_11 79 YES 29-JUN-11
    stdby_11 80 YES 29-JUN-11
    stdby_11 75 NO 07-JUL-11
    stdby_11 74 NO 07-JUL-11
    stdby_11 76 NO 07-JUL-11
    stdby_11 77 NO 07-JUL-11
    stdby_11 78 NO 07-JUL-11
    I have intentionally given
    sequence# BETWEEN 74 and 80
    because I know in the current incarnaion of the database, max sequence is 78.
    So my understanding is, the rows between 28-29 June are from previous incarnation, correct me if I am wrong
    Archive files of the current incarnation, since I successfully created standby database are shipped but yet to be applied - am I right?
    Then my final question is, when will these archives be applied to standby database?
    I am sorry to ask too many questions but I am just trying to understand how it all works.
    Thanks for your help again

  • Issue on physical standby database

    Hi
    I've a problem on standby database.
    I recently added a datafile on primary database, then I scp'ed the data file to physical standby database.On physical standby database I tried performing recovery.
    I get following message in my alert log
    WARNING! Recovering data file 88 from a fuzzy file. If not the current file
    it might be an online backup taken without entering the begin backup command.
    ORA-279 signalled during: ALTER DATABASE RECOVER standby database ...
    how can I fix this now.
    We keep physical standby database 2 day behind, and apply logs manually.
    Physical standby database is maintained manually.
    Could someone help me in getting out of this problem.
    Oracle 9.2.0.7
    solaris

    Versus keeping it in manual mode, you can specify a time "delay" for the application of the logs:
    From http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/log_apply.htm#i1022811
    6.2.2 Specifying a Time Delay for the Application of Archived Redo Log Files
    In some cases, you may want to create a time lag between the time when redo data is received from the primary site and when it is applied to the standby database. You can specify a time interval (in minutes) to protect against the application of corrupted or erroneous data to the standby database. When you set a DELAY interval, it does not delay the transport of the redo data to the standby database. Instead, the time lag you specify begins when the redo data is completely archived at the standby destination.
    Note:
    If you define a delay for a destination that has real-time apply enabled, the delay is ignored.
    Specifying a Time Delay
    You can set a time delay on primary and standby databases using the DELAY=minutes attribute of the LOG_ARCHIVE_DEST_n initialization parameter to delay applying archived redo log files to the standby database. By default, there is no time delay. If you specify the DELAY attribute without specifying a value, then the default delay interval is 30 minutes.
    Canceling a Time Delay
    You can cancel a specified delay interval as follows:
    For physical standby databases, use the NODELAY keyword of the RECOVER MANAGED STANDBY DATABASE clause:
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE NODELAY;
    For logical standby databases, specify the following SQL statement:
    SQL> ALTER DATABASE START LOGICAL STANDBY APPLY NODELAY;
    These commands result in log apply services immediately beginning to apply archived redo log files to the standby database, before the time interval expires. Also, see:
    Section 12.8, "Using a Physical Standby Database with a Time Lag"
    Oracle Database SQL Reference for the DELAY attribute of the ALTER DATABASE RECOVER MANAGED STANDBY DATABASE statement

  • Issue with physical standby database not in sync with primary

    Hi,
    I created an physical standby database couple of Hours back . I am trying to keep the standby database in Managed recovery mode to make the standby in sync with primary but it is throwing the below erros. Please share your suggestion ...
    SQL> select thread#,max(sequence#) from v$log_history group by thread#;
    THREAD# MAX(SEQUENCE#)
    1 7
    PROCESS STATUS THREAD# SEQUENCE#
    ARCH CONNECTED 0 0
    ARCH CONNECTED 0 0
    RFS OPENING 1 12
    ALERT LOG :
    Tue Mar 20 07:31:32 2012
    alter database recover managed standby database disconnect from session
    Tue Mar 20 07:31:32 2012
    Attempt to start background Managed Standby Recovery process (PRIMARY)
    MRP0 started with pid=18, OS id=16370
    Tue Mar 20 07:31:32 2012
    MRP0: Background Managed Standby Recovery process started (PRIMARY)
    Managed Standby Recovery not using Real Time Apply
    parallel recovery started with 8 processes
    Media Recovery Log /oracle/STDBY/arch/1_3_777567883.dbf
    Tue Mar 20 07:31:39 2012
    Completed: alter database recover managed standby database disconnect from session
    Tue Mar 20 07:31:54 2012
    Incomplete recovery applied all redo ever generated.
    Recovery completed through change 9677325080303
    Tue Mar 20 07:31:54 2012
    MRP0: Media Recovery Complete (PRIMARY)
    Tue Mar 20 07:31:55 2012
    MRP0: Background Media Recovery process shutdown (PRIMARY)
    Thanks,
    Rakesh

    HI CKPT,
    Thanks for the reply. All the Archives from primary are transferred to the standby by RFS. Also i tried to register the log files manually even but it says already registered. They are no errors in the primary instance alert log file. Please find the log
    SEVERITY ERROR_CODE MESSAGE TO_CHAR(TIMESTAMP,'D
    Informational 0 ARC0: Archival started 20-MAR-2012 06:51:36
    Informational 0 ARC1: Archival started 20-MAR-2012 06:51:36
    Informational 0 ARC0: Becoming the 'no FAL' ARCH 20-MAR-2012 06:51:36
    Informational 0 ARC0: Becoming the 'no SRL' ARCH 20-MAR-2012 06:51:36
    Informational 0 ARC1: Becoming the heartbeat ARCH 20-MAR-2012 06:51:36
    Informational 0 Redo Shipping Client Connected as PUBLIC 20-MAR-2012 06:52:07
    Informational 0 -- Connected User is Valid 20-MAR-2012 06:52:07
    Informational 0 RFS[1]: Assigned to RFS process 15934 20-MAR-2012 06:52:07
    Informational 0 RFS[1]: Identified database type as 'physical standby' 20-MAR-2012 06:52:07
    Warning 0 RFS[1]: No standby redo logfiles created 20-MAR-2012 06:52:07
    Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 06:52:42
    Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 06:52:42
    Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:52:47
    Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 06:52:49
    bf
    Control 0 MRP0: Media Recovery Complete 20-MAR-2012 06:53:04
    Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 06:53:06
    Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:53:24
    Control 0 Media Recovery Complete 20-MAR-2012 06:53:43
    Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 06:54:55
    Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 06:54:55
    Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:55:00
    Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 06:55:01
    bf
    Control 0 MRP0: Media Recovery Complete 20-MAR-2012 06:55:17
    Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 06:55:18
    Informational 0 Redo Shipping Client Connected as PUBLIC 20-MAR-2012 07:31:03
    Informational 0 -- Connected User is Valid 20-MAR-2012 07:31:03
    Informational 0 RFS[2]: Assigned to RFS process 16366 20-MAR-2012 07:31:03
    Informational 0 RFS[2]: Identified database type as 'physical standby' 20-MAR-2012 07:31:03
    Warning 0 RFS[2]: No standby redo logfiles created 20-MAR-2012 07:31:04
    Warning 0 RFS[2]: No standby redo logfiles created 20-MAR-2012 07:31:06
    Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 07:31:32
    Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 07:31:32
    Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 07:31:37
    Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 07:31:38
    bf
    Control 0 MRP0: Media Recovery Complete 20-MAR-2012 07:31:54
    Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 07:31:55
    36 rows selected.
    SQL> archive log list;
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination /oracle/STDBY/arch/
    Oldest online log sequence 13
    Next log sequence to archive 0
    Current log sequence 14
    SQL> ho ls -ltra /oracle/STDBY/arch/
    total 3754456
    drwxr-xr-x 4 oracle dba 4096 Feb 13 17:38 ..
    -rw-r----- 1 oracle dba 908516864 Mar 20 06:37 1_8_777567883.dbf
    -rw-r----- 1 oracle dba 770419200 Mar 20 06:40 1_3_777567883.dbf
    -rw-r----- 1 oracle dba 757698048 Mar 20 06:41 1_4_777567883.dbf
    -rw-r----- 1 oracle dba 5171712 Mar 20 06:41 1_5_777567883.dbf
    -rw-r----- 1 oracle dba 1060801024 Mar 20 06:43 1_6_777567883.dbf
    -rw-r----- 1 oracle dba 323025920 Mar 20 06:43 1_7_777567883.dbf
    -rw-r----- 1 oracle dba 1558016 Mar 20 06:43 1_9_777567883.dbf
    -rw-r----- 1 oracle dba 4608 Mar 20 06:43 1_10_777567883.dbf
    -rw-r----- 1 oracle dba 1579008 Mar 20 06:52 1_11_777567883.dbf
    -rw-r----- 1 oracle dba 11876864 Mar 20 07:31 1_12_777567883.dbf
    -rw-r----- 1 oracle dba 2560 Mar 20 07:31 1_13_777567883.dbf
    drwxr-xr-x 2 oracle dba 36864 Mar 20 07:31 .
    SQL>

  • DB link for physical standby database

    Hi All ,
    I'm facing the below error on primary while trying to create a db link pointing to the 10g standby database which is in mount stage.
    SQL> create database link synct connect to system identified by 123 using 'stdby';
    Database link created.
    SQL> select max(sequence#) from v$archived_log@synct where applied='YES';
    select max(sequence#) from v$archived_log@synct where applied='YES'
    ERROR at line 1:
    ORA-02068: following severe error from SYNCT
    ORA-01033: ORACLE initialization or shutdown in progress
    Database version is 10.2 standard edition
    My requirement is i need to get max(sequence#) of standby database from primary database using db link.
    what i was trying to do is
    on primary get max(sequence#) & get max(sequence#) of standby using db link and compare both if the gap differene is more than 10 send a mail.
    Any suggestions will be really helpful

    976422 wrote:
    Hi All ,
    I'm facing the below error on primary while trying to create a db link pointing to the 10g standby database which is in mount stage.
    SQL> create database link synct connect to system identified by 123 using 'stdby';
    Database link created.
    SQL> select max(sequence#) from v$archived_log@synct where applied='YES';
    select max(sequence#) from v$archived_log@synct where applied='YES'
    ERROR at line 1:
    ORA-02068: following severe error from SYNCT
    ORA-01033: ORACLE initialization or shutdown in progress
    Post Standby/DataGuard/ADG all questions further in Oracle Discussion Forums » High Availability » Data Guard
    If you try to connect any users other than SYS in standby the error is very much expected. Of course you can connect with other users if you open database in OPEN READ ONLY mode, from 11gRx you can connect with other users even MRP is running if you are using ADG(active Data Guard licensed) .
    I like to know, what you want to achieve by creating DB Link on physical standby database? Which is not allowed.
    Database version is 10.2 standard edition
    My requirement is i need to get max(sequence#) of standby database from primary database using db link.
    what i was trying to do is
    on primary get max(sequence#) & get max(sequence#) of standby using db link and compare both if the gap differene is more than 10 send a mail.
    Any suggestions will be really helpfulNote:- Standard edition, Data Guard not enabled.
    To use this you should use Oracle Net Service, you no need of DB Links.
    Ex:- sqlplus sys/****@standby as sysdba
    Here standby refers to Oracle net service, Where you will have entries in $ORACLE_HOME/network/admin/tnsnames.ora file.
    Edited by: CKPT on Dec 12, 2012 2:01 PM

  • Test physical standby database in dataguard

    Hi all,
    I had a successfull dataguard implementation for oracle 9r2.
    Primary and standby databases are on different nodes, logs from primay are shipping and applying to physical standby database successfully.
    As these database are for oracle 11i ebs, so for testing dataguard status i had created a table manually having columns date and remarks. Periodically i insert few records in this table in primary database and then chek this tabel in standby database (by opening in read only mode).
    Now i want to test physical standby database with applications tier  but don't want to disturb origional primary database.
    as these are the normal switchover steps
    1) at primary db
    ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN;
    2) at standby
    ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY;
    3) at primary, now this will be the stand by database
    SHUTDOWN IMMEDIATE;
    STARTUP MOUNT;
    4) at standby, now this will be the primary database
    SHUTDOWN IMMEDIATE;
    STARTUP
    My concern is if i skip step 1 and 3 and only execute step 2 and 4, will that be applicable for my requirement, or there is some other way to achieve this goal.
    Regards,
    Ken

    To avoid touching the primary production DB, you may try to use the following command on your standby database side:
    alter database activate standby database;
    This will turn your standby database to primary database, however the log will be reset and this means you will need to rebuild your DR.
    Another way is to use flash back feature on your standby database, activate it and revert back to the flashback point when the DR testing is done.

Maybe you are looking for

  • My safari is quitting because of Flash Player-10.4-10.5 plug-in

    Can you advise me about this problem of safari. It can happen twice per day. Best ragrds..

  • Mavericks 10.9.2 Internet sharing prob after updgrade from 10.6.8, any solutions?

    Hello World! Here I am going to tell you my woe story which is, I finally decided to upgrade to 10.9.2 from my a little worn 10.6.8, and was very happy with a choice until stumbled upon the complete failure with establishing the Internet sharing for

  • Bex Query getting Freezed while formatting results

    Hi Friends, I am running a BEx Query with one year data selection but it's getting freezes while formatting results. But when i deselect the 'Format after refresh' option  in the query properties..then query is running fine. Could you please let me k

  • Serving static pages from a web application

              My weblogic environment is a a front end proxy server (httpclusterservlet or apache) for           session failover and static page serving, and a weblogic server. I have built my application as a           web application creating a .WAR f

  • Motion and Final Cut render glitch

    I am having a problem with renders, The Problem seems to be in Final Cut and Motion. Usually when I bring .motn in to my Final cut sequence, though some times the glitches happen in Motion as well. When I rerender, the glitches will usually appear in