Manual Standby Recovery

Hi Friendz,
Oracle Db 9i
I have configured a manual standby database(I am not using Dataguard or "create standby database" command ) I only copy the cold backup to the target recovery server. I have been applying archive logs to it for a week now. I use the "recover automatic database using backup controlfile" command.
My problem is, when I try to "alter database open resetlogs" so I can test if I can open it, It is asking for the next archive log and message "that the system01.dbf needs recovery". How can I open my standby database and force it to stop recovery?
Thanks a lot
Ms Inday

ALTER DATABASE RECOVER  automatic database using backup controlfile
Media Recovery Start
Sun Dec 19 18:33:14 2010
Media Recovery Log /u02/oracle/oaproddb/9.2.0/dbs/arch/1_40621.dbf
Sun Dec 19 18:33:14 2010
Media Recovery Log /u02/oracle/oaproddb/9.2.0/dbs/arch/1_40622.dbf
Sun Dec 19 18:33:18 2010
Media Recovery Log /u02/oracle/oaproddb/9.2.0/dbs/arch/1_40623.dbf
Sun Dec 19 18:33:22 2010
Media Recovery Log /u02/oracle/oaproddb/9.2.0/dbs/arch/1_40624.dbf
Sun Dec 19 18:33:25 2010
Media Recovery Log /u02/oracle/oaproddb/9.2.0/dbs/arch/1_40625.dbf
Sun Dec 19 18:33:26 2010
Media Recovery Log /u02/oracle/oaproddb/9.2.0/dbs/arch/1_40626.dbf
Errors with log /u02/oracle/oaproddb/9.2.0/dbs/arch/1_40626.dbf
ORA-279 signalled during: ALTER DATABASE RECOVER  automatic database using b...
Sun Dec 19 18:33:26 2010
ALTER DATABASE RECOVER    CANCELThis is the alert when I try to open it using resetlogs.
ALTER DATABASE   MOUNT
Sun Dec 19 19:29:56 2010
Successful mount of redo thread 1, with mount id 4188096816
Sun Dec 19 19:29:56 2010
Database mounted in Exclusive Mode.
Completed: ALTER DATABASE   MOUNT
Sun Dec 19 19:29:56 2010
ALTER DATABASE OPEN
ORA-1589 signalled during: ALTER DATABASE OPEN...
Sun Dec 19 19:30:51 2010
alter database open noresetlogs
Sun Dec 19 19:30:51 2010
ORA-1588 signalled during: alter database open noresetlogs...
Sun Dec 19 19:31:18 2010
alter database open resetlogs
Sun Dec 19 19:31:20 2010
ORA-1113 signalled during:  alter database open resetlogs...
Sun Dec 19 19:32:00 2010
ALTER DATABASE RECOVER  database
Sun Dec 19 19:32:00 2010
Media Recovery Start
Sun Dec 19 19:32:00 2010
Media Recovery failed with error 1610
ORA-283 signalled during: ALTER DATABASE RECOVER  database  ...
Sun Dec 19 19:32:56 2010
ALTER DATABASE RECOVER  database using backup controlfile
Sun Dec 19 19:32:56 2010
Media Recovery Start
ORA-279 signalled during: ALTER DATABASE RECOVER  database using backup cont...
Sun Dec 19 19:33:12 2010
ALTER DATABASE RECOVER    CANCEL
Sun Dec 19 19:33:12 2010
Media Recovery Cancelled
Completed: ALTER DATABASE RECOVER    CANCEL
Sun Dec 19 19:33:31 2010
alter database open resetlogs
Sun Dec 19 19:33:31 2010
ORA-1113 signalled during: alter database open resetlogs...
Sun Dec 19 19:34:15 2010Thanks

Similar Messages

  • How to Create Manual Standby for a Oracle 11g RAC with ASM to Single Instan

    Hi All,
    I have a task to configure a Single Instance Standby Database with ASM for 2-node Primary RAC+ASM database.
    Version using : 11.1.0.6 Oracle 11g --- *" STANDARD EDITION "* Please note datagaurd will not be supported in standard edition.
    Primary database - 2 -Node RAC using ASM storage (All datafiles, redologs, controfile and archive logs)
    Need to setup a single instance standby database manually and than using scripts to transfer the archive logs from primary server to standby server to do recovery time to time.
    Please let me know if there are any configuration document(s) which can help me to set the manual standby? or need your kind help to give your valuable ideas how to go in above situation.
    Thanks in advance

    Niall Litchfield wrote:
    El DBA wrote:
    Well if the archive logs are stored in ASM on the primary nodes, you almost definitely want to be using RMAN to access them. Then to transfer between primary and standby there are many options, this is essentially the step that Data Guard takes care of - so if you (and I) are running Standard Edition, this is the part to "worry" about.
    I'm not really sure what you mean by this:
    As in standard edition the archive destination will be on ASMI don't think the Edition of Oracle (Standard or Enterprise) dictates where and how you store your archive logs, but it's possible I've misunderstood what you mean...SE dictates that database storage for RAC will be ASM, including archive log files. Anything else is not officially supported. I haven't tested but it may be that you can use LOG_ARCHIVE_DUPLEX_DEST to specify a local filesystem for archive log files as well.
    If that doesn't work you'll have to script rman "backup as copy" jobs regularly and then transport the results of that.
    Niall Litchfield
    http://www.orawin.info/
    By the way, it seems Robert has been pretty helpful, it's polite to give him some points dude. And since this is your thread, not mine, give him a "helpful" from me too :p
    El DBA
    Incidentally if you are forced down the RMAN backup as copy route then this will likely throw your current backup retention strategy somewhat, you'll need to think carefully about when an archivelog can be deleted following backup, how many times it might be backed up and so on. I do understand, and have argued for, the use of SE RAC. I also understand and have argued for and implemented manually managed standby a number of times. However by the time your primary database is a RAC instance and you need a standby for DR etc then you really have to look very seriously at whether Standard Edition is still the right investment or not. You will be spending a lot of DBA time managing and troubleshooting this, and you will find that it is less reliable than the off the shelf solution. I suspect that you are very close to the point where an EE installation becomes a worthwhile investment here.
    Niall Litchfield
    http://www.orawin.info/

  • Manual Standby Database (10.2.0.2.0) on Windows 2003 R2

    Hi,
    We are setting up a standby database on a remote site for a simple oracle DB. As we already have a standby/master for another Oracle DB (from SAP) we want to stay as close as possible as what already exist.
    For the SAP Oracle standby, we are copying manualy all archive to the stand by and apply them with brarchive. All is working fine.
    For the new standby, we can not use brarchive as there is no SAP install on the standby but we stay with the "manual" copy of the archive from the master to the standby (using robocpy). It means all archive are on the standby (K:\oracle\oradata\archive).
    The creation of the standby DB seems to be OK as i can open it, but i can't manage to apply de redo logs.
    I'm quite new to oracle, so it's maybe a very basic issue, but i've already spent 3 days on it...
    To start the DB, we lauch a bat script :
    sqlplus /nolog @c:\backup\standby.sql
    pause
    the standby.sql:
    connect /@TECDB01 as sysdba
    startup nomount;
    alter database mount standby database;
    exit;
    Then i connect to sqlplus and enter:
    alter database recover managed standby database;
    In another sqlplus session :
    SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
    wich give me :
    PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
    ARCH CONNECTED 0 0 0 0
    ARCH CONNECTED 0 0 0 0
    MR(fg) WAIT_FOR_GAP 1 45400 0 0
    RFS IDLE 0 0 0 0
    The sequence 45400 seems to be ok regarding the time of the backup restored on the standby.
    The archive is well on the server, but it won't apply it.
    The Alert_TECDB01.log :
    Fri Oct 29 11:03:43 2010
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    Picked latch-free SCN scheme 3
    Autotune of undo retention is turned on.
    IMODE=BR
    ILAT =121
    LICENSE_MAX_USERS = 0
    SYS auditing is disabled
    ksdpec: called for event 13740 prior to event group initialization
    Starting up ORACLE RDBMS Version: 10.2.0.2.0.
    System parameters with non-default values:
    processes                = 999
    sga_target               = 7214202880
    control_files            = I:\ORACLE\ORADATA\CNTRL\STANDBY.CTL, J:\ORACLE\ORADATA\CNTRL\STANDBY.CTL, K:\ORACLE\ORADATA\CNTRL\STANDBY.CTL
    db_block_size            = 8192
    compatible               = 10.2.0.2.0
    log_archive_dest_1       = LOCATION=K:\oracle\oradata\archive
    log_archive_dest_2       = SERVICE=TECDB01
    log_archive_dest_state_1 = enable
    log_archive_dest_state_2 = enable
    standby_archive_dest     = K:\oracle\oradata\archive
    archive_lag_target       = 1800
    db_file_multiblock_read_count= 16
    undo_management          = AUTO
    undo_tablespace          = RBS
    undo_retention           = 10800
    recyclebin               = OFF
    remote_login_passwordfile= EXCLUSIVE
    db_domain                = WORLD
    dispatchers              = (ADDRESS=(PROTOCOL=tcp)(HOST=xxx.xxx.xxx.92))(DISPATCHERS=4)(CONNECTIONS=1000)
    shared_servers           = 100
    local_listener           = (ADDRESS=(PROTOCOL=TCP)(HOST=xxx.xxx.xxx.92)(PORT=1521))
    session_cached_cursors   = 300
    utl_file_dir             = \\srvuniway.vrithoff.srwt.tec-wl.be\hotspots
    job_queue_processes      = 10
    audit_file_dest          = I:\ORACLE\ADMIN\TECDB01\ADUMP
    background_dump_dest     = I:\ORACLE\ADMIN\TECDB01\BDUMP
    user_dump_dest           = I:\ORACLE\ADMIN\TECDB01\UDUMP
    core_dump_dest           = I:\ORACLE\ADMIN\TECDB01\CDUMP
    db_name                  = TECDB01
    open_cursors             = 3000
    pga_aggregate_target     = 1086324736
    PMON started with pid=2, OS id=4012
    PSP0 started with pid=3, OS id=3856
    MMAN started with pid=4, OS id=3580
    DBW0 started with pid=5, OS id=1084
    LGWR started with pid=6, OS id=576
    CKPT started with pid=7, OS id=3516
    SMON started with pid=8, OS id=508
    RECO started with pid=9, OS id=3068
    CJQ0 started with pid=10, OS id=2448
    MMON started with pid=11, OS id=2840
    MMNL started with pid=12, OS id=3024
    Fri Oct 29 11:03:44 2010
    starting up 4 dispatcher(s) for network address '(ADDRESS=(PROTOCOL=tcp)(HOST=xxx.xxx.xxx.92))'...
    starting up 100 shared server(s) ...
    Fri Oct 29 11:03:45 2010
    alter database mount standby database
    Fri Oct 29 11:03:51 2010
    Setting recovery target incarnation to 2
    ARCH: STARTING ARCH PROCESSES
    ARC0 started with pid=118, OS id=3584
    Fri Oct 29 11:03:51 2010
    ARC0: Archival started
    ARC1 started with pid=119, OS id=3688
    Fri Oct 29 11:03:51 2010
    ARC1: Archival started
    ARCH: STARTING ARCH PROCESSES COMPLETE
    Fri Oct 29 11:03:51 2010
    ARC0: Becoming the 'no FAL' ARCH
    Fri Oct 29 11:03:51 2010
    Successful mount of redo thread 1, with mount id 3987142355
    Fri Oct 29 11:03:51 2010
    ARC0: Becoming the 'no SRL' ARCH
    Fri Oct 29 11:03:51 2010
    ARC1: Becoming the heartbeat ARCH
    Fri Oct 29 11:03:51 2010
    Physical Standby Database mounted.
    Completed: alter database mount standby database
    Fri Oct 29 11:04:06 2010
    alter database recover managed standby database
    Fri Oct 29 11:04:06 2010
    Managed Standby Recovery not using Real Time Apply
    parallel recovery started with 7 processes
    Media Recovery Waiting for thread 1 sequence 45400
    Fetching gap sequence in thread 1, gap sequence 45400-45499
    +FAL[client]: Error fetching gap sequence, no FAL server specified+
    Fri Oct 29 11:04:37 2010
    +FAL[client]: Failed to request gap sequence+
    GAP - thread 1 sequence 45400-45499
    DBID 3776455083 branch 670241032
    +FAL[client]: All defined FAL servers have been attempted.+
    Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
    parameter is defined to a value that is sufficiently large
    enough to maintain adequate log switch information to resolve
    archivelog gaps.
    Fri Oct 29 11:04:51 2010
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[1]: Assigned to RFS process 3452
    RFS[1]: Identified database type as 'physical standby'
    Fri Oct 29 11:04:51 2010
    RFS LogMiner: Client disabled from further notification
    The tecdb01_arc1_3688.trc :
    Dump file i:\oracle\admin\tecdb01\bdump\tecdb01_arc1_3688.trc
    Fri Oct 29 11:03:51 2010
    ORACLE V10.2.0.2.0 - 64bit Production vsnsta=0
    vsnsql=14 vsnxtr=3
    Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
    With the Partitioning, OLAP and Data Mining options
    Windows NT Version V5.2 Service Pack 2
    CPU                 : 8 - type 8664, 2 Physical Cores
    Process Affinity    : 0x0000000000000000
    Memory (Avail/Total): Ph:7467M/9215M, PhPgF:2454M/10796M+
    Instance name: tecdb01
    Redo thread mounted by this instance: 1
    Oracle process number: 119
    Windows thread id: 3688, image: ORACLE.EXE (ARC1)
    *** SERVICE NAME:() 2010-10-29 11:03:51.177
    *** SESSION ID:(1088.1) 2010-10-29 11:03:51.177
    kcrrwkx: nothing to do (start)
    *** 2010-10-29 11:04:51.129
    Redo shipping client performing standby login
    *** 2010-10-29 11:04:51.176 64529 kcrr.c
    Logged on to standby successfully
    Client logon and security negotiation successful!
    kcrrwkx: nothing to do (end)
    *** 2010-10-29 11:05:51.285
    kcrrwkx: nothing to do (end)
    *** 2010-10-29 11:06:51.300
    kcrrwkx: nothing to do (end)
    The initTECDB01.ora :
    # Copyright (c) 1991, 2001, 2002 by Oracle Corporation
    # Archive
    archive_lag_target=1800
    log_archive_dest_1='LOCATION=K:\oracle\oradata\archive'
    # Cache and I/O
    db_block_size=8192
    db_file_multiblock_read_count=16
    # Cursors and Library Cache
    open_cursors=3000
    session_cached_cursors=300
    # Database Identification
    db_domain=WORLD
    db_name=TECDB01
    # Diagnostics and Statistics
    background_dump_dest=I:\oracle\admin\TECDB01\bdump
    core_dump_dest=I:\oracle\admin\TECDB01\cdump
    user_dump_dest=I:\oracle\admin\TECDB01\udump
    # File Configuration
    control_files=("I:\oracle\oradata\cntrl\standby.ctl", "J:\oracle\oradata\cntrl\standby.ctl", "K:\oracle\oradata\cntrl\standby.ctl")
    # Job Queues
    job_queue_processes=10
    # Miscellaneous
    compatible=10.2.0.2.0
    recyclebin=OFF
    # Processes and Sessions
    processes=999
    # SGA Memory
    sga_target=6880M
    # Pools
    #java_pool_size=150M
    # Security and Auditing
    audit_file_dest=I:\oracle\admin\TECDB01\adump
    remote_login_passwordfile=EXCLUSIVE
    # Shared Server
    shared_servers=100
    dispatchers="(ADDRESS=(PROTOCOL=tcp)(HOST=xxx.xxx.xxx.92))(DISPATCHERS=4)(CONNECTIONS=1000)"
    #dispatchers="(PROTOCOL=TCP) (SERVICE=TECDB01XDB)"
    # Sort, Hash Joins, Bitmap Indexes
    pga_aggregate_target=1036M
    # System Managed Undo and Rollback Segments
    undo_management=AUTO
    undo_retention=10800
    undo_tablespace=RBS
    local_listener="(ADDRESS=(PROTOCOL=TCP)(HOST=xxx.xxx.xxx.92)(PORT=1521))"
    # NIDA - 28.10.2010 - redo apply
    log_archive_dest_state_1=enable
    log_archive_dest_2 = 'SERVICE=TECDB01'
    log_archive_dest_state_2=enable
    #standby_file_management=auto
    standby_archive_dest=K:\oracle\oradata\archive
    And the TNSNAMES.ora :
    # tnsnames.ora Network Configuration File: C:\oracle\102\network\admin\tnsnames.ora
    # Generated by Oracle configuration tools.
    #this is the standby
    TECDB01.VRITHOFF.SRWT.TEC-WL.BE =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = xxx.xxx.xxx.92)(PORT = 1521))
    (CONNECT_DATA =
    (SERVICE_NAME = TECDB01)
    # This file is written by Oracle Services For MSCS
    # on Sat Nov 08 10:44:27 2008
    #this is the master
    PRIMARY.VRITHOFF.SRWT.TEC-WL.BE =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = xxx.xxx.xxx.246)(PORT = 1521))
    (CONNECT_DATA =
    (SID = TECDB01)
    EXTPROC_CONNECTION_DATA.VRITHOFF.SRWT.TEC-WL.BE =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)(KEY = TECDB01))
    (CONNECT_DATA =
    (SERVICE_NAME = TECDB01)
    Hope you have all information to bring me in the right way.
    Regards,
    Nicolas

    Hi,
    The recover automatic is working fine, but I still have problems with the recover managed
    Here is the Alert log :(the 46626 was there at 11:30)
    Mon Nov 15 11:31:13 2010
    alter database recover managed standby database using current logfile
    Managed Standby Recovery starting Real Time Apply
    parallel recovery started with 7 processes
    Media Recovery Waiting for thread 1 sequence 46626
    Mon Nov 15 16:36:01 2010
    alter database recover managed standby database cancel
    Mon Nov 15 16:36:05 2010
    Managed Standby Recovery not using Real Time Apply
    Recovery interrupted!
    Mon Nov 15 16:36:06 2010
    Media Recovery user canceled with status 16037
    ORA-16043 signalled during: alter database recover managed standby database using current logfile...
    Mon Nov 15 16:36:07 2010
    Completed: alter database recover managed standby database cancel
    Mon Nov 15 16:36:37 2010
    ALTER DATABASE RECOVER automatic standby database until time'2010-11-15:15:50:00'
    Mon Nov 15 16:36:37 2010
    Media Recovery Start
    Managed Standby Recovery not using Real Time Apply
    parallel recovery started with 7 processes
    Mon Nov 15 16:36:39 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46626_0670241032.001
    Mon Nov 15 16:36:45 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46627_0670241032.001
    Mon Nov 15 16:37:11 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46628_0670241032.001
    Mon Nov 15 16:37:30 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46629_0670241032.001
    Mon Nov 15 16:37:48 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46630_0670241032.001
    Mon Nov 15 16:37:59 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46631_0670241032.001
    Mon Nov 15 16:38:15 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46632_0670241032.001
    Mon Nov 15 16:38:28 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46633_0670241032.001
    Mon Nov 15 16:38:47 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46634_0670241032.001
    Mon Nov 15 16:39:34 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46635_0670241032.001
    Mon Nov 15 16:40:43 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46636_0670241032.001
    Mon Nov 15 16:42:03 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46637_0670241032.001
    Mon Nov 15 16:43:18 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46638_0670241032.001
    Mon Nov 15 16:44:38 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46639_0670241032.001
    Mon Nov 15 16:45:45 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46640_0670241032.001
    Mon Nov 15 16:46:37 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46641_0670241032.001
    Mon Nov 15 16:47:48 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46642_0670241032.001
    Mon Nov 15 16:49:07 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46643_0670241032.001
    Mon Nov 15 16:50:04 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46644_0670241032.001
    Mon Nov 15 16:51:13 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46645_0670241032.001
    Mon Nov 15 16:52:16 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46646_0670241032.001
    Mon Nov 15 16:53:07 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46647_0670241032.001
    Mon Nov 15 16:54:28 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46648_0670241032.001
    Mon Nov 15 16:55:47 2010
    Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46649_0670241032.001
    Mon Nov 15 16:56:35 2010
    Incomplete Recovery applied until change 4037420604
    Completed: ALTER DATABASE RECOVER automatic standby database until time'2010-11-15:15:50:00'
    I don't catch why the system wait for a sequence that is available...
    Regards,
    Nico

  • Manual Standby and Archlogs application

    Hi There,
    I need to set up a manual standby database for one of our production databases. We are using oracle 11g (11.1.0.7) 64x STANDARD EDITION on Windows 2008 server 64x.
    I shutdown the database, copied the data files and redo logs to a new server (same directories structure to the production database); I created a standby controlfile and a pfile and copied both across to the new host.
    I created the oracle windows service on the new machine and started the database as follows:
    C:\Users\oracle>
    C:\Users\oracle>SQLPLUS "/AS SYSDBA"
    SQL*Plus: Release 11.1.0.7.0 - Production on Tue Apr 13 15:04:53 2010
    Copyright (c) 1982, 2008, Oracle.  All rights reserved.
    Connected to an idle instance.
    SQL> STARTUP PFILE='C:\oracle\product\11.1.0.7\database\INITSTDBT.ORA' NOMOUNT;
    ORA-32006: STANDBY_ARCHIVE_DEST initialization parameter has been deprecated
    ORACLE instance started.
    Total System Global Area  542814208 bytes
    Fixed Size                  2131248 bytes
    Variable Size             419433168 bytes
    Database Buffers          117440512 bytes
    Redo Buffers                3809280 bytes
    SQL>
    SQL>
    SQL> SELECT STATUS FROM V$INSTANCE;
    STATUS
    STARTED
    SQL> alter database mount standby database;
    Database altered.The production database has forced logging enabled in it so that we can capture all the DDL statemtents.
    We created a dummy schema, a dummy table (with few rows); issued a commit, and then switched the logs few times to create the necessary archive logs. We then manually moved the archive logs to the new standby host, and put them under the appropriate directory (D:\oracle\flash_recovery_area\STDBT\ARCHIVELOG\2010_04_13).
    Now we tried to recover the database by applying the new shipped logs:
    SQL> recover standby database
    ORA-00279: change 606666 generated at 04/13/2010 14:37:19 needed for thread 1
    ORA-00289: suggestion :
    D:\ORACLE\FLASH_RECOVERY_AREA\STDBT\ARCHIVELOG\2010_04_13\O1_MF_1_46_%U_.ARC
    ORA-00280: change 606666 for thread 1 is in sequence #46
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    ORA-00308: cannot open archived log
    'D:\ORACLE\FLASH_RECOVERY_AREA\STDBT\ARCHIVELOG\2010_04_13\O1_MF_1_46_%U_.ARC'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: 'D:\ORACLE\ORADATA\STDBT\SYSTEM01.DBF'So we thought we'll try the recovery again by manually putting the filename in:
    SQL> recover standby database
    ORA-00279: change 606666 generated at 04/13/2010 14:37:19 needed for thread 1
    ORA-00289: suggestion :
    D:\ORACLE\FLASH_RECOVERY_AREA\STDBT\ARCHIVELOG\2010_04_13\O1_MF_1_46_%U_.ARC
    ORA-00280: change 606666 for thread 1 is in sequence #46
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    D:\oracle\flash_recovery_area\STDBT\ARCHIVELOG\2010_04_13\O1_MF_1_46_5W9W3LT3_.ARC
    ORA-00279: change 608376 generated at 04/13/2010 15:30:10 needed for thread 1
    ORA-00289: suggestion :
    D:\ORACLE\FLASH_RECOVERY_AREA\STDBT\ARCHIVELOG\2010_04_13\O1_MF_1_47_%U_.ARC
    ORA-00280: change 608376 for thread 1 is in sequence #47
    ORA-00278: log file
    'D:\oracle\flash_recovery_area\STDBT\ARCHIVELOG\2010_04_13\O1_MF_1_46_5W9W3LT3_.
    ARC' no longer needed for this recovery
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    D:\oracle\flash_recovery_area\STDBT\ARCHIVELOG\2010_04_13\O1_MF_1_47_5W9W7P6D_.ARC
    ORA-00279: change 608426 generated at 04/13/2010 15:32:20 needed for thread 1
    ORA-00289: suggestion :
    D:\ORACLE\FLASH_RECOVERY_AREA\STDBT\ARCHIVELOG\2010_04_13\O1_MF_1_48_%U_.ARC
    ORA-00280: change 608426 for thread 1 is in sequence #48
    ORA-00278: log file
    'D:\oracle\flash_recovery_area\STDBT\ARCHIVELOG\2010_04_13\O1_MF_1_47_5W9W7P6D_.
    ARC' no longer needed for this recovery
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    CANCEL
    Media recovery cancelled.So, the issue here is that even though the archive logs did exist in the correct directory, when we hit enter to accept the default, oracle didn't find the logs and it was looking for a file with the format "O1_MF_1_46_%U_.ARC" instead of "O1_MF_1_46_5W9W3LT3_.ARC" and so the recovery failed.. How can we fix this so that oracle will detect the correct archlog name so that when we automate the applying of the logs it will work (and we don't have to do enter them manually one by one)?
    SQL> ALTER DATABASE ACTIVATE STANDBY DATABASE;
    Database altered.
    SQL> select status from v$instance;
    STATUS
    MOUNTED
    SQL>
    SQL>
    SQL>
    SQL> alter database open read only;
    alter database open read only
    ERROR at line 1:
    ORA-16433: The database has not been opened in read-write modeAnother question, once we activated the standby database, we tried to open it but it failed with above error; do we have to shut it down 1st and then do a normal STARTUP command? or do we have to open it with resetlogs??
    If someone can shed some light here that will be great.
    Thanks
    Edited by: rsar001 on Apr 13, 2010 4:27 PM

    SQL> show parameter log_archive_dest
    NAME                                 TYPE        VALUE
    log_archive_dest                     string
    log_archive_dest_1                   string
    log_archive_dest_10                  string
    log_archive_dest_2                   string
    log_archive_dest_3                   string
    log_archive_dest_4                   string
    log_archive_dest_5                   string
    log_archive_dest_6                   string
    log_archive_dest_7                   string
    log_archive_dest_8                   string
    log_archive_dest_9                   string
    log_archive_dest_state_1             string      enable
    log_archive_dest_state_10            string      enable
    log_archive_dest_state_2             string      enable
    log_archive_dest_state_3             string      enable
    log_archive_dest_state_4             string      enable
    log_archive_dest_state_5             string      enable
    log_archive_dest_state_6             string      enable
    log_archive_dest_state_7             string      enable
    log_archive_dest_state_8             string      enable
    log_archive_dest_state_9             string      enable
    SQL> show parameter recover
    NAME                                 TYPE        VALUE
    db_recovery_file_dest                string      D:\oracle\flash_recovery_area
    db_recovery_file_dest_size           big integer 2G
    recovery_parallelism                 integer     0
    SQL>

  • Managed Standby Recovery not active

    Dear All,
    My database version is:
    SQL> select banner from v$version;
    BANNER
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
    PL/SQL Release 10.2.0.1.0 - Production
    CORE 10.2.0.1.0 Production
    TNS for Linux: Version 10.2.0.1.0 - Production
    NLSRTL Version 10.2.0.1.0 - Production
    OS:RedHat 5.5
    My current configuration is:
    We have two node RAC primary database and a local standby database.
    And TWO NODE RAC DR (REMOTE)STANDBY DATABASE
    while checking (REMOTE WHICH IS TWO NODE RAC)dr synchronization we found archive since yesterday has not been applied.
    But local dr is fully sinc with the primary database.
    When i have executed 'ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL' it says
    SQL> alter database recover managed standby database cancel;
    alter database recover managed standby database cancel
    ERROR at line 1:
    ORA-16136: Managed Standby Recovery not active
    I manually copied the archive log which where missing in the remote standby database and then register those archive log.
    after that when i manually tried to recover the standby database it has given me following error.
    sql>recover automatic standby database;
    ORA-00283: recovery session canceled due to errors
    ORA-01124: cannot recover data file 1 - file is in use or recovery
    ORA-01110:data file 1: '/database/ctmis/system01.dbf'
    please please help me to resolve the issue.
    Thanks and Regards
    Monoj Das

    according to my understand
    Node1,Node2 is having node1-standby node2-standby in RAC environment right?
    on which node logs ur trying to apply on which node standby? (node1 ==>node1-standby or node2 ==>node2-standby)
    check it...hope it will work or not sure :)
    standby side...
    rman target /
    RMAN>crosscheck archivelog all
    then try to recover..will see ..
    if not
    check with support.oracle.com through SR.

  • Manual Standby Database not in sync with missing archivelogs

    Hello,
    OS: Solaris
    DB: Oracle 11.2.0.1 EE
    Not Using ASM or RAC
    I have a Production database that is in archivelog mode and a Standby DR server.
    Both servers (Prod, Standby) have exact same structure and db name/version.
    We manually scp archive logs and recover them to a manual standby database via SQL Scripts "cron". (I.E. set autorecovery on; recover standby database;)
    We recently got out of sync with our log files and have not been applying them to the standby. As part of Prod Maintenance, these log files were deleted and are not available anymore.
    I've tried several ways to "rebuild" our standby database. I have tried to Shutdown prod, backup all the db files and scp them to standby, re-create standby controlfile and startup mount and recover standby.
    Every time I try to apply a new archive log via recover standby, these are the errors:
    ORA-00279: change 211077622 generated at 1/27/2012 12:18:42 needed for thread 1
    ORA-00289: suggestion : /oradump/arch/PROD/PROD_arch_1_69486_736618850.arc
    ORA-00280: change 211077622 for thread 1 is in sequence #69486
    ORA-00308: cannot open archived log '/oradump/arch/PROD/PROD_arch_1_69486_736618850.arc'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    ORA-10879: error signaled in parallel recovery slave
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '/oradevices/PROD/oraPRODsystem1.dbf'
    When I check v$log_history, the new logs have not been applied.
    I've also tried the "Restore from incremental backup via SCN" method with same results.
    Is there a way to re-create the standby clean and ensure that the log chain that is currently broken gets fixed or reset?
    I would eventually like to get DataGuard in here, but that's not the case at the moment.
    Thanks for your suggestions.
    -Dav

    if you are using the cold backup to create the standby database, Check that have you followed the following steps or not.
    1. remove
    all the datafiles and controlfiles from the standby database.
    2. Create a new standby controlfile of the production for standby using the following cmd
    'alter database create standby controlfile as 'Location';'
    3. move the new controlfile to standby database server location as specified in initialization parameter file.
    4. Restore all the datafiles to its appropriate loaction which was taken through cold backup.
    5. startup nomount
    6. alter database mount standby database;
    7. recover standby database.
    scp the archive log sequence that is asked by the database, from production.
    You can try this steps.

  • Physica standby recovery problem

    Hi,
    I am trying to recover physical standby database manually
    I am getting below error:
    alter database recover standby database parallel (degree 32);
    alter database recover standby database parallel (degree 32)
    ERROR at line 1:
    ORA-01153: an incompatible media recovery is active
    I have tried to cancel managed recovery, but no managed recovery is active.
    alter database recover managed standby database cancel;
    alter database recover managed standby database cancel
    ERROR at line 1:
    ORA-16136: Managed Standby Recovery not active
    select distinct recovery_mode from v$archive_dest_status;
    RECOVER
    IDLE
    Please help me to resolve this. Thanks in advance.
    regards,
    Narendra

    Apparently this is bug 5084496, related to parallel recovery on 10.1 and below (ML note 361883.1). You may avoid this bug if you don't use parallel recovery. It looks like there are no one-off patches available, so you are stuck with either serial recovery or upgrade to 10.2 or higher :-(
    Regards,
    Jeremiah Wilton
    ORA-600 Consulting
    http://www.ora-600.net

  • Query on Oracle Manual Standby management

    Hi All,
    There is requirement for upgrade of Oracle 10g Standard Edition to Oracle 11g Standard Edition. The environment has a manual standby database configured for production.
    The standby management is currently being done via scripts for archive log shipping and recovery of standby.
    As part of our recommendations we are looking out for tools to automate the standby management. Data Guard is not an options since that needs an Enterprise Edition license plus extra cost for Data Guard option.
    We would like to know of any such tools. Could you please share the details in terms of features and cost of licensing, etc.
    Thanks for your time!
    Best Regards,
    Udit

    http://www.oracle-base.com/articles/misc/dbvisit-standby.php
    http://www.dbvisit.com/
    never tried it though, and it seems it does exactly the same than the custom archivelog shipping scripts, with some GUI on top of it

  • Manual Standby on Standard Edition

    Hey, I try to setup a manual standby on standard edition 10gR2.
    Source is a RAC database (standard edition on sles10 sp3)
    I created a node and created a oracle instance on this node. This node is using the filesystem for the oracle files.
    I did a hotbackup of the source database and copied all files over to the other host.
    Which parameters needs to be change in the init.ora and how can I recover my database ?
    Articles like
    http://www.databasejournal.com/features/oracle/article.php/3682421/Manual-Standby-Database-under-Oracle-Standard-Edition.htm
    or
    Alternative for standby database in standard edition [ID 333749.1]
    does not really help me.
    Thanks for your patience... :-)

    ./rman target / cmdfile=/opt/oracle/rman.sh
    rman.sh
    run{
    change archivelog all crosscheck;
    allocate channel ch1 type disk;
    backup incremental level 0 database format
    '/opt/oracle/backup/backupnew/bk_inc0_%s_%p' include current
    controlfile for standby ;
    sql "alter system archive log current";
    backup archivelog all format '/opt/oracle/backup/backupnew/al_%s_%p';
    release channel ch1;
    copy files from '/opt/oracle/backup/backupnew' to standbyhost:'/opt/oracle/backup/backupnew'
    ./rman cmdfile=/opt/oracle/duplicate.rman
    duplicate.rman
    connect auxiliary sys/oracle@standby
    connect target /
    run {
    allocate auxiliary channel ch1 type disk;
    duplicate target database for standby dorecover nofilenamecheck;
    release channel ch1;
    Now I get this:
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 09/15/2010 15:20:35
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06026: some targets not found - aborting restore
    RMAN-06024: no backup or copy of the control file found to restore
    When do have I to issue the
    ALTER DATABASE CREATE STANDBY CONTROLFILE AS '/opt//oracle/stbycf.ctl';
    command. And where to copy ?

  • Single-instance manual standby for a three-node RAC database

    Hi all,
    I am wondering how it is possible to create a manual standby database for a rac primary database.
    Oracle versione is standard edition 11.1.
    I have experience creating and managing manual standby for single-instance database; I am wondering if and how I can instruct the single-instance standby database to discover and apply the three redo threads that I will copy from the primary site to the standby site.
    Should I use rman to catalog all the archived log on the standby site ?
    Should I configure many LOG_ARCHIVE_DEST_n parameters to point to many different path, one for each primary instance (i.e. one for each redo thread), and let rman automagically discover all the archived logs ?
    Should I configure only LOG_ARCHIVE_DEST_1 , put archivelogs from all threads in the same folder, and let rman automagically discover all the archived logs ?
    Thanks for every answer!
    Andrea

    Hi,
    indeed i catalog all transfered archive logs in front of the recover process.
    During the tests i believe (iirc) i was unable to recover from transfered archivelogs without catalog them first. But this statement is out of my mind, i am not 100% sure for this, sorry.
    Some more details.
    Because it is a standard edition, i have to use on the RAC side ASM. So our normal scripts to transfer archivelogs from primary to standby are obsolete.
    So i decided to put the whole standby thing into the database. Now the primary database uses external scheduler jobs to do the work. The standby side is not using ASM, so there is no need to handle the logs in any special way.
    The steps are:
    1. Get SCN from primary and standby
    2. Transfer the logs for the gap from ASM to "normal" filesystem.
    3. Transfer (and compress, if not in LAN) to standby archive dest
    4. Catalog on standby side
    5. Recover on standby side
    6. Delete on normal filesystem (on both sides, but on standby with a delay of 2 days just to be sure)
    The steps on the standby side are both using the primary scn from step 1 as a parameter to avoid error messages during the catalog or recover call.
    Hth
    Joerg

  • Switchover of a manual standby database (no data guard)

    Hi all,
    I have a standby database .
    I am using Oracle Standard Edition 10.2.0.4 / 10.2.0.5 so I have build a manual standby .
    I am able to do a failover in the case something goes wrong; I was thinking if it is possible to do a manual switchover . and failback.
    Do you thick that mounting the primary database and applying ALL archivelogs and online redolog to the standby database is enough ?
    Do you think this is a supported operation?
    How can I check the current scn of a mounted database? (v$database.current_scn shows 0 until the database is opened )
    thnk you for every answer
    Andrea

    helter_skelter wrote:
    hi,
    You can see current_scn of standby database in v$database.current_scn. It is null only on primary database if it's in mount state.that's the problem: I am unable to mount both database and to check they have the same current_scn
    not all changes are written to ARL so you can't recover standby database to exact the same SCN as primaryI thinks this is because the last changes are only recorder in online redolog, so I was thinking that a possible way to simulate a clean switchover could be as follow:
    1 - shutdown immediate the primary database on server prod1
    2 - shutdown abort the (manual) standby database on server dr2
    3 - copy archivelog, controlfiles, tempfiles, onlinelogs from primary to the standby database
    3 - copy controlfiles from standby database to primary database
    4 - open the database on server dr2. It should open "read write" cleanly (mount + recover from archivelog + recover from onlinelog + open noresetlogs )
    5 - mount the database on server prod1. It should mount as a physical standby database.
    What do you think about it?
    thanks,
    andrea

  • Oracle manually standby database with standard edition

    Hi, I want to have a plan for disaster. I'm triying with two virtual machines with oracle database 10g on suse linux. I follow these URLs
    http://www.dbasupport.com/oracle/ora10g/manual_standby.shtml
    http://oramdq.blogspot.com/2009/05/como-configurar-un-sistema-de-alta.html
    and it look that work all right.
    I know that with manually standby database we applied archived logs, and so, we don't propagate any physical changes to secondary database (standby), for example, if I create a new tablespace, or adding a new datafile to an existing tablespace, it don't work in the secondary database.
    Anyone does know how is the better way to apply the physical changes??
    Anyone have any scripts to do that?
    Thanks in advance.

    HI,
    Add the STANDBY_FILE_MANAGEMENT = AUTO to the primary parameter file, it will solve it.
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams209.htm]
    Reagds,
    Vijayaraghavan K
    Edited by: Vijayaraghavan Krishnan on Feb 24, 2010 7:19 PM

  • Manual Standby Database

    Hi,
    I have ORACLE 10.2.0.3.0 64 bit SE1 running on a RHEL4 server. I have a backup server on which I need to create a manual standby database for a (poor man's) high availability environment. We have explored RAC, Dataguard etc and given them up for cost considerations. We understand the potential of up to 15 minutes data loss. I know the general steps necessary to set up the manual standby server. For example, I know I need a cold (or hot) backup of the primary to reset my standby database. Then I need to create the standby control file. I need to write deamon processes to ship the archive logs to the standby server and apply those logs to the database. I am new to ORACLE and would appreciate some specific advice.
    (1) Should I use DBCA to create the database on the standby server first? My impression is that using DBCA will set up the enterprise manager, isqlplus and the relevevant entries in oratab etc on the standby server. If I simply install ORACLE 10g on the standby and copy the backup files from the primary server, I will not have access to the database tools that come with ORACLE 10g.
    (2) Can someone please share the scripts you may have written? or point me to some skeleton scripts?
    (3) What are the failure points for manual standby databases? What do I need to pro-actively monitor? For example, if the logs are not being applied properly to the standby database for a prolonged period, I would like to know about it.
    (4) What are the procedures for recovering from a failed master database?
    (5) Where can I learn more about the subject? I will need specific commands to setup the standby. Are these procedures documented somewhere?
    Thanks!
    - Rajesh

    Try this one Manual Standby Database under Oracle Standard Edition
    Or search the subject on google, many results.
    No, you will not create "standby" using DBCA, you need to use primary's backup to restore on standby server and constantly recover.

  • Manual Standby Database from EE to SE1

    Can I do a Manual Standby Database from Oracle Enterprise edition (EE) to Oracle Standard Edition One (SE1)?

    Hi,
    You can created a manual standby for EE, But you need to purchase a seperate licence for standby database also.
    See oracle licencing manul in oracle documentation.
    Thanks and Regards,
    Satish.G.S

  • ORA-16136: Managed Standby Recovery not active

    Hi
    I am trying implement the dataguard in the windows platform. And this is my first time. Right now iam trying on physical standby. i have done everything as per the document. But iam getting some error. After giving the
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
    SQL> ALTER SYSTEM SWITCH LOGFILE;
    SQL> recover managed standby database cancel;
    // I am getting error
    ORA-16136: Managed Standby Recovery not active
    When just like that i tried to open the standby database in read only mode, i am getting error
    SQL> alter database open read only;
    alter database open read only
    ERROR at line 1:
    ORA-16004: backup database requires recovery
    ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
    ORA-01110: data file 1: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\DB1\SYSTEM01.DBF'
    When i checked the alert log file of Primary Database, it shows:
    PING[ARCo]: Heartbeat failed to connect to standby 'db2sby'. Error is 1031.
    Wed Sep 01 14:10:27 2010
    Thread 1 advanced to log sequence 337 (LGWR switch)
    Current log# 2 seq# 337 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\DB1\REDO02.LOG
    Wed Sep 01 14:10:28 2010
    Deleted Oracle managed file C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\DB1\ARCHIVELOG\2010_02_25\O1_MF_1_224_5RD10Z5V_.ARC
    Wed Sep 01 14:14:53 2010
    Error 1031 received logging on to the standby
    Wed Sep 01 14:14:53 2010
    Errors in file c:\oracle\product\10.2.0\admin\db1\bdump\db1_arco_2156.trc:
    ORA-01031: insufficient privileges
    PING[ARCo]: Heartbeat failed to connect to standby 'db2sby'. Error is 1031.
    Wed Sep 01 14:19:53 2010
    Error 1031 received logging on to the standby
    Wed Sep 01 14:19:53 2010
    Errors in file c:\oracle\product\10.2.0\admin\db1\bdump\db1_arco_2156.trc:
    ORA-01031: insufficient privileges
    And when i checked alert log file of stand by database:
    Wed Sep 01 14:13:19 2010
    Errors in file c:\oracle\product\10.2.0\standbyy\admin\db2\bdump\db2sby_dbw0_3060.trc:
    ORA-01157: cannot identify/lock data file 9 - see DBWR trace file
    ORA-01110: data file 9: 'C:\TSUNDO12.DBF'
    ORA-27086: unable to lock file - already in use
    OSD-00001: additional error information
    O/S-Error: (OS 101) The exclusive semaphore is owned by another process
    --> The above error of Standby was coming for each datafile such as system, users etc.
    Kindly Help me.
    Shiyas M

    here is the pfile of Primary Database:
    db1.__db_cache_size=188743680
    db1.__java_pool_size=4194304
    db1.__large_pool_size=4194304
    db1.__shared_pool_size=83886080
    db1.__streams_pool_size=0
    *.audit_file_dest='C:\oracle\product\10.2.0/admin/db1/adump'
    *.background_dump_dest='C:\oracle\product\10.2.0/admin/db1/bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='C:\oracle\product\10.2.0\oradata\db1\control01.ctl','C:\oracle\product\10.2.0\oradata\db1\control02.ctl','C:\oracle\product\10.2.0\oradata\db1\control03.ctl'
    *.core_dump_dest='C:\oracle\product\10.2.0/admin/db1/cdump'
    *.db_16k_cache_size=4194304
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_name='db1'
    *.DB_UNIQUE_NAME='db1prim'
    *.LOG_ARCHIVE_CONFIG='DG_CONFIG=(db1,db2sby)'
    *.LOG_ARCHIVE_DEST_1='LOCATION=C:\oracle\product\10.2.0\ARCHIVELOG VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=db1prim'
    *.LOG_ARCHIVE_DEST_2='SERVICE=db2sby LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=db2sby'
    *.LOG_ARCHIVE_DEST_STATE_1=ENABLE
    *.LOG_ARCHIVE_DEST_STATE_2=ENABLE
    *.LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
    *.LOG_ARCHIVE_MAX_PROCESSES=30
    *.FAL_SERVER=db2sby
    *.FAL_CLIENT=db1
    *.DB_FILE_NAME_CONVERT='C:\oracle\product\10.2.0\Standbyy\oradata\DB2','C:\oracle\product\10.2.0\oradata\db1'
    *.LOG_FILE_NAME_CONVERT='C:\oracle\product\10.2.0\Standbyy\oradata\DB2','C:\oracle\product\10.2.0\oradata\db1'
    *.STANDBY_FILE_MANAGEMENT=AUTO
    *.db_recovery_file_dest='C:\oracle\product\10.2.0/flash_recovery_area'
    *.db_recovery_file_dest_size=2147483648
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=db1XDB)'
    *.job_queue_processes=10
    *.open_cursors=300
    *.pga_aggregate_target=95420416
    *.processes=150
    *.recyclebin='OFF'
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=287309824
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='C:\oracle\product\10.2.0/admin/db1/udump'
    *.utl_file_dir='OCM_CONFIG_HOME/state'
    Here is the Pfile of standby database:
    db1.__db_cache_size=188743680
    db1.__java_pool_size=4194304
    db1.__large_pool_size=4194304
    db1.__shared_pool_size=83886080
    db1.__streams_pool_size=0
    *.audit_file_dest='C:\oracle\product\10.2.0\Standbyy\admin\db2\adump'
    *.background_dump_dest='C:\oracle\product\10.2.0\Standbyy\admin\db2\bdump'
    *.compatible='10.2.0.1.0'
    *.control_files='C:\oracle\product\10.2.0\Standbyy\oradata\db2\control001.ctl','C:\oracle\product\10.2.0\Standbyy\oradata\db2\control002.ctl','C:\oracle\product\10.2.0\Standbyy\oradata\db2\control003.ctl'
    *.core_dump_dest='C:\oracle\product\10.2.0\Standbyy\admin\db2'
    *.db_16k_cache_size=4194304
    *.db_block_size=8192
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_name='db1'
    *.DB_UNIQUE_NAME='db2sby'
    *.LOG_ARCHIVE_CONFIG='DG_CONFIG=(db1,db2sby)'
    *.LOG_ARCHIVE_DEST_1='LOCATION=C:\oracle\product\10.2.0\ARCHIVELOG VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=db2sby'
    *.LOG_ARCHIVE_DEST_2='SERVICE=db1 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=db1'
    *.LOG_ARCHIVE_DEST_STATE_1=ENABLE
    *.LOG_ARCHIVE_DEST_STATE_2=ENABLE
    *.LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
    *.LOG_ARCHIVE_MAX_PROCESSES=30
    *.FAL_SERVER=db1
    *.FAL_CLIENT=db2sby
    *.DB_FILE_NAME_CONVERT='C:\oracle\product\10.2.0\Standbyy\oradata\DB2','C:\oracle\product\10.2.0\oradata\db1'
    *.LOG_FILE_NAME_CONVERT='C:\oracle\product\10.2.0\Standbyy\oradata\DB2','C:\oracle\product\10.2.0\oradata\db1'
    *.STANDBY_FILE_MANAGEMENT=AUTO
    *.db_recovery_file_dest='C:\oracle\product\10.2.0\flash_recovery_area\DB2SBY'
    *.db_recovery_file_dest_size=2147483648
    *.dispatchers='(PROTOCOL=TCP) (SERVICE=db1XDB)'
    *.job_queue_processes=10
    *.open_cursors=300
    *.pga_aggregate_target=95420416
    *.processes=150
    *.recyclebin='OFF'
    *.remote_login_passwordfile='EXCLUSIVE'
    *.sga_target=287309824
    *.undo_management='AUTO'
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='C:\oracle\product\10.2.0\Standbyy\admin\db2\udump'
    *.utl_file_dir='OCM_CONFIG_HOME/state'

Maybe you are looking for