Trace in Physical Standby Database

I'm getting the following messages in the trace file for a Physical Standby database:
Background Managed Standby Recovery process started
Start recovery at thread 1 ckpt scn 8253476346531 logseq 4391 block 2
*** 2008-02-13 09:09:44.366
Managed Recovery: Active posted.
*** 2008-02-13 09:09:44.367
Acquiring global enqueue on thread 1 sequence 4391
*** 2008-02-13 09:09:44.367
Failed to acquire global enqueue on thread 1 sequence 4391
Has anyone encountered this before?

found this...
http://ora-00569.ora-code.com/
ORA-00569:     Failed to acquire global enqueue.
Cause:     A prior error occurred on one of the instances in the cluster. Typically errors are caused by shared pool resource contention.
Action:     Check for and resolve prior errors on all instances in the cluster. If there is shared pool resource contention, increase the SHARED_POOL_SIZE, DML_LOCKS, PROCESSES, TRANSACTIONS, CLUSTER_DATABASE_INSTANCES and PARALLEL_MAX_SERVERS initialization parameters.

Similar Messages

  • 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

  • Create ONLINE logfile in physical standby database

    We have created a physical standby database with rman duplicate command on a remote server
    "duplicate target database for standby dorecover nofilenamecheck"
    When I see the standby server...Online logfiles are not created however its relevant entries are there in V$LOG and V$LOGFILE views.
    I guess it is the default behaviour of duplicate command in RMAN and we can not specify LOGFILE clause when we create standby database.
    Now the problem is we could not drop the online logfile on standby database since it's status is "CURRENT", "ACTIVE".
    Since the ONLINE LOGFILE are not actually created , "ALTER DATABASE CLEAR LOGFILE GROUP " command returns with error as it could not find the file in the server.
    So How we can drop the current/active online logfile and add new ones in standby db?

    I'm assuming you have physical standby. Here are step I did in the past.
    1) create a backup control file
    2) bring the database back using the "recreate control file" it the trace file BUT you need to remove or comment out the line that has the corrupt or missing redo log file. And don't forget to add the tempfile after you recreate the controlfile
    example:
    alter database backup controlfile to trace;
    STARTUP NOMOUNT
    CREATE CONTROLFILE REUSE DATABASE "ORCL" NORESETLOGS FORCE LOGGING ARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 100
    MAXINSTANCES 8
    MAXLOGHISTORY 292
    LOGFILE
    GROUP 1 '/oracledata/orcl/redo01.log' SIZE 200M,
    GROUP 2 '/oracledata/orcl/redo02.log' SIZE 200M,
    GROUP 3 '/oracledata/orcl/redo03.log' SIZE 200M,
    # GROUP 3 '/oracledata/orcl/redo03.log' SIZE 200M
    -- STANDBY LOGFILE
    -- GROUP 10 '/oracledata/orcl/redostdby04.log' SIZE 200M,
    -- GROUP 11 '/oracledata/orcl/redostdby05.log' SIZE 200M
    DATAFILE
    '/oracledata/orcl/system01.dbf',
    '/oracledata/orcl/undotbs01.dbf',
    '/oracledata/orcl/sysaux01.dbf',
    '/oracledata/orcl/users01.dbf'
    CHARACTER SET WE8ISO8859P1
    If you just want to add the standby redo log then using this command.
    alter database add standby logfile
    '/<your_path>/redostdby01.log' size 200M reuse,

  • 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

  • Error while creating physical standby database using Oracle Grid 10.2.0.5

    Hi All,
    I am setting up data guard using oracle grid.
    Primary database version: - 10.2.0.4
    Standby database version: - 10.2.0.4
    Primary OS Red Hat Enterprise Linux AS release 4 (Nahant Update 8)2.6.9
    Standby OS Red Hat Enterprise Linux AS release 4 (Nahant Update 8)2.6.9
    I am creating physical standby database using EM. But it is getting failed with error message in sqlnet.ora file
    Fatal NI connect error 12533, connecting to:
    (DESCRIPTION=(ADDRESS_LIST=)(CONNECT_DATA=(SERVICE_NAME=INPRDSB_XPT)(SERVER=dedicated)(CID=(PROGRAM=oracle)(HOST=indb50.oii.com)(USER=oracle))))
      VERSION INFORMATION:
            TNS for Linux: Version 10.2.0.4.0 - Production
            TCP/IP NT Protocol Adapter for Linux: Version 10.2.0.4.0 - Production
      Time: 17-AUG-2010 02:40:07
      Tracing not turned on.
      Tns error struct:
        ns main err code: 12533
        TNS-12533: TNS:illegal ADDRESS parameters
        ns secondary err code: 0
        nt main err code: 0
        nt secondary err code: 0As we can see, address_list is empty.
    Can anyone suggest what could be the reason behind this?

    Dear user13295317,
    Here is the error explanation;
    Oracle Error :: TNS-12533
    TNS:illegal ADDRESS parameters
    Cause
    An illegal set of protocol adapter parameters was specified.
    In some cases, this error is returned when a connection cannot be made to the protocol transport.
    Action
    Verify that the destination can be reached using the specified protocol.
    Check the parameters within the ADDRESS section of TNSNAMES.ORA.
    Legal ADDRESS parameter formats may be found in the Oracle operating system specific documentation for your platform.
    Protocols that resolve names at the transport layer (such as DECnet object names) are vulnerable to this error if not properly configured or names are misspelled.Hope That Helps.
    Ogan

  • SQL exception during creation of a physical standby database with EM

    Version: EM Oracle 10.2.5 (agents running, repository running, primary db running, all targets visible and reachable with EM)
    I try to create a physical standby database with the enterprise manager and each time the process is aborted with a SQL exception during the preparation of the job by the EM. I have added a part of the OMs log containing the error at the end of the excerpt.
    =============
    2010-04-29 16:00:39,856 [EMUI_16_00_39_/console/targets] WARN pref.SubtabPref getFolders.710 - Unknown folder id: VirtualServers retrieved from repository
    2010-04-29 16:01:04,765 [EMUI_16_01_04_/console/database/dataguard/create] ERROR em.dataguard validate.1329 - CreateBean: ClassNotFoundException: null
    2010-04-29 16:02:05,476 [EMUI_16_02_05_/console/database/dataguard/create] ERROR jobs.dbclone checkSetFileError.79 - DatabaseFileAttributes.checkSetFileError(): Null database file!
    2010-04-29 16:02:05,476 [EMUI_16_02_05_/console/database/dataguard/create] ERROR jobs.dbclone setControlfiles.160 - DatabaseFileAttributes.setDatafiles(): Invalid control file!
    2010-04-29 16:02:05,492 [EMUI_16_02_05_/console/database/dataguard/create] ERROR jobs.dbclone getControlFileNames.616 - DatabaseFileAttributes.getDatafileNames(): null datafile names!
    2010-04-29 16:02:32,823 [Thread-28] ERROR em.jobs remoteOp.2389 - DBVerify.remoteOp(): Error: max_stamp# 6071384
    2010-04-29 16:02:32,823 [Thread-28] ERROR jobs.dbclone submitJobPreparation.3297 - DBCloneObject.submitJobPreparation(): getMaxLogSequenceNum: Während der Vorbereitung des Jobs ist eine SQL Exception aufgetreten. Um das Problem zu diagnostizieren, legen Sie das Agent Perl-Skript-Tracing auf DEBUG fest und wiederholen den Vorgang
    2010-04-29 16:02:32,823 [Thread-28] ERROR jobs.dbclone submitJobPreparation.3501 - DBCloneObject.submitJobPreparation(): Exception: java.lang.Exception: Während der Vorbereitung des Jobs ist eine SQL Exception aufgetreten. Um das Problem zu diagnostizieren, legen Sie das Agent Perl-Skript-Tracing auf DEBUG fest und wiederholen den Vorgang
    2010-04-29 16:02:32,823 [Thread-28] ERROR jobs.dbclone submitDBCloneJob.3716 - DBCloneObject.submitDBCloneJob(): Exception: Während der Vorbereitung des Jobs ist eine SQL Exception aufgetreten. Um das Problem zu diagnostizieren, legen Sie das Agent Perl-Skript-Tracing auf DEBUG fest und wiederholen den Vorgang
    2010-04-29 16:02:37,496 [EMUI_16_02_37_/console/database/dataguard/create] ERROR em.dataguard onEvent.1243 - CreateConfigController: Exception: oracle.sysman.db.dg.util.VxxStandbyException: Während der Vorbereitung des Jobs ist eine SQL Exception aufgetreten. Um das Problem zu diagnostizieren, legen Sie das Agent Perl-Skript-Tracing auf DEBUG fest und wiederholen den Vorgang
    =========
    I have set the agent perl script tracing to DEBUG, but can't find any reason, why the job preparation failed.
    Has anyone an idea why the job cannot be prepared? Thanks in advance for investigation :-)

    Can you please tell me how can i see data gaurd on EM..
    I have oracle 11gR1..i have implemmented primary as well standby database..
    I have already started EM but i have no idea where to find datagaurd option..or how to create standdby db using EM..
    You got error that means u did it using EM..how can i do it on EM

  • Problem in recover physical standby database(Data Guard) by rman

    Hello to all
    I have created a physical standby database ,I want make backup of it by rman and when I lose it's datafile I can restore it ,making backup and restore is fine but in recovery I encounter some problem
    scenarios is follow
    1- In rman I create a backup of standby database by this command:
    backup database plus archivelog delete all input;
    2- I run this comman in rman for recover standby database
    run{
    2> set until scn 1392701;
    3> restore database;
    4> recover database;
    5> }
    (1392701 is extracted from this query "SELECT MAX(NEXT_CHANGE#)+1 UNTIL_SCN FROM V$LOG_HISTORY LH,
    V$DATABASE DB WHERE LH.RESETLOGS_CHANGE#=DB.RESETLOGS_CHANGE# AND LH.RESETLOGS_TIME =
    DB.RESETLOGS_TIME;" "http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rman.htm")
    but RMAN result is like this:
    executing command: SET until clause
    Starting restore at 13-DEC-08
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backupset restore
    channel ORA_DISK_1: specifying datafile(s) to restore from
    backup set
    restoring datafile 00001 to /u01/app/oracle/oradata/sari/system01.dbf
    restoring datafile 00002 to /u01/app/oracle/oradata/sari/undotbs01.dbf
    restoring datafile 00003 to /u01/app/oracle/oradata/sari/sysaux01.dbf
    restoring datafile 00004 to /u01/app/oracle/oradata/sari/users01.dbf
    restoring datafile 00005 to /u01/app/oracle/oradata/sari/example01.dbf
    restoring datafile 00006 to /u01/app/oracle/oradata/sari/users02.dbf
    channel ORA_DISK_1: reading from backup piece /home/oracle/backup/0ek24dt4_1_1
    channel ORA_DISK_1: restored backup piece 1
    piece handle=/home/oracle/backup/0ek24dt4_1_1
    tag=TAG20081213T042506
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:07
    Finished restore at 13-DEC-08
    Starting recover at 13-DEC-08
    using channel ORA_DISK_1
    starting media recovery
    archive log thread 1 sequence 116 is already on disk as file /u01/app/oracle/oradata/archive/1_116_666786084.arc
    archive log thread 1 sequence 117 is already on disk as file /u01/app/oracle/oradata/archive/1_117_666786084.arc
    archive log filename=/u01/app/oracle/oradata/archive/1_116_666786084.arc thread=1 sequence=116
    archive log filename=/u01/app/oracle/oradata/archive/1_117_666786084.arc thread=1 sequence=117
    unable to find archive log
    archive log thread=1 sequence=118
    RMAN-03002: failure of recover command at 12/13/2008 05:14:13
    RMAN-06054: media recovery requesting unknown log: thread 1
    seq 118 lowscn 1392700
    3- then I decline 1392701 to 1392700 and i run this command
    run{
    2> set until scn 1392700;
    3> restore database ;
    4> recover database;
    5> }
    executing command: SET until clause
    Starting restore at 13-DEC-08
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backupset restore
    channel ORA_DISK_1: specifying datafile(s) to restore from
    backup set
    restoring datafile 00001 to /u01/app/oracle/oradata/sari/system01.dbf
    restoring datafile 00002 to /u01/app/oracle/oradata/sari/undotbs01.dbf
    restoring datafile 00003 to /u01/app/oracle/oradata/sari/sysaux01.dbf
    restoring datafile 00004 to /u01/app/oracle/oradata/sari/users01.dbf
    restoring datafile 00005 to /u01/app/oracle/oradata/sari/example01.dbf
    restoring datafile 00006 to /u01/app/oracle/oradata/sari/users02.dbf
    channel ORA_DISK_1: reading from backup piece /home/oracle/backup/0ek24dt4_1_1
    channel ORA_DISK_1: restored backup piece 1
    piece handle=/home/oracle/backup/0ek24dt4_1_1 tag=TAG20081213T042506
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:08
    Finished restore at 13-DEC-08
    Starting recover at 13-DEC-08
    using channel ORA_DISK_1
    starting media recovery
    archive log thread 1 sequence 116 is already on disk as
    file /u01/app/oracle/oradata/archive/1_116_666786084.arc
    archive log thread 1 sequence 117 is already on disk as
    file /u01/app/oracle/oradata/archive/1_117_666786084.arc
    archive log filename=/u01/app/oracle/oradata/archive/1_116_666786084.arc thread=1
    sequence=116archive log
    filename=/u01/app/oracle/oradata/archive/1_117_666786084.arc
    thread=1 sequence=117Oracle Error:
    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: '/u01/app/oracle/oradata/sari/system01.dbf'
    media recovery complete, elapsed time: 00:00:10
    Finished recover at 13-DEC-08
    4- if I run
    run{
    restore database;
    recover database;
    I will recieve that error of step 2 (RMAN-06054: media recovery requesting unknown log: thread 1
    seq 118 lowscn 1392700)
    5- if I just restore the database and I don't perform recovery by rman and I restart redo apply all thing seem fine
    but in opening database I'll recieve ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '/u01/app/oracle/oradata/sari/system01.dbf' error)
    do you know what is problem
    thanks
    Edited by: ARKH on Dec 12, 2008 11:06 PM

    hi
    I myself have found the solution , when I recover the standby database
    it do recovery but at the end of recovery it raise the error(RMAN-06054: media recovery requesting unknown log: thread 1
    seq 118 lowscn 1392700) but if I begain redo apply before open the database
    and I wait till all redo apply process start and communication between the
    standby database and the primary database start, then I can
    open the standby database and no error will raise
    but if befor restarting redo apply I open the database I'll recieve the
    ORA-01152: file 1 was not restored from a sufficiently old backup
    ORA-01110: data file 1: '/u01/app/oracle/oradata/sari/system01.dbf' error
    thanks

  • How to create 11.2.0.2 physical standby database from 2 node RAC (11.2.0.2)

    Hi,
    Can any one please help me How to manually create 11.2.0.2 standalone physical standby database from 2 node RAC (11.2.0.2) database which is running in RHEL5 and ASM plugged in.
    DB : 11.2.0.2
    OS : RHEL5
    RMAN duplicate is causing problem with network and we decided to go for manual creation of the same.
    Thanks in Advance..

    Hi;
    Can any one please help me How to manually create 11.2.0.2 standalone physical standby database from 2 node RAC (11.2.0.2) database which is running in RHEL5 and ASM plugged in.
    DB : 11.2.0.2
    OS : RHEL5I had similar issue, what i did
    1. Used source oracle_home on standby server
    2. Created new asm instance and use same naming
    3. I took RMAN full backup on source and move it to target
    4. I edit initora file remove RAC setting and restore db(also edited listener file)
    Regard
    Helios

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

  • Logical standby database to physical standby database

    I already start my logical standby database and I want to return it again to physical standby database. So what should I do?

    >
    The "may be" is because I have tested flashback of a physical standby to before resetlogs, but not a logical standby.
    >
    A physical standby keeps the DBID of the primary - a logical standby does not. That is exactly the problem that restricts the reconversion into physical from logical, and you did not encounter that problem.
    >
    I haven't used "keep identity" but from what I read it relates to "convert to physical" not "flashback database".
    >
    Exactly. And that is what the OP wants to do: convert to physical (from logical).
    You mentioned that this might be possible with flashback.
    Problem: During the conversion from physical to logical, the DBID gets changed unless you specify (in 11g) KEEP IDENTITY. This would make it possible to reconvert into phyiscal from logical.
    In short: If there is no solution for the changed DBID of the logical standby in order to flashback it into physical as you suggested, then it is not possible .
    When I saw your first answer, I thought that you might have a solution in mind in order to solve that obvious problem. Sorry for having bothered you.
    Kind regards
    Uwe
    http://uhesse.wordpress.com

  • 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

  • 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

  • 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

  • Physical standby database in RAC system

    Hi EXperts,
    We have a 4 nodes 11.2 cluster system. i will set a data guard as a disaster recovery mothods.
    As a physical standby database set, does we need to configure same nodes (4 nodes) in other city as primary database cluster system?
    Can we set physical standby database is in 2 nodes cluster system and primary database is in 4 nodes cluster system?
    Thanks explaining!
    Jin

    Can we set physical standby database is in 2 nodes cluster system and primary database is in 4 nodes cluster system?Yes. You can setup 2 node RAC as physical standby and also with different memory parameters. But, the only issue is when DB failover from primary to standby, the applications connect to 2 node RAC in place of 4 node RAC and may be overloaded.

Maybe you are looking for