Mulitplexing redo log no use

SQL> alter database add logfile
  2  group 4 ( 'C:\oracle\oradata\orcl\logfilebackup\redo01.log') size 10m
  3  /
Database altered.
SQL> shutdown
Database closed.
Database dismounted.
ORACLE instance shut down.from dos prompt i delete the redo01.log
C:\del C:\oracle\oradata\orcl\redo01.log
C:\>
SQL> startup
ORACLE instance started.
Total System Global Area  171966464 bytes
Fixed Size                   787988 bytes
Variable Size             145488364 bytes
Database Buffers           25165824 bytes
Redo Buffers                 524288 bytes
Database mounted.
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: 'C:\ORACLE\ORADATA\ORCL\REDO01.LOG'redo01.log is deleted and i multiplexed the redo log in my first step so i can recover it by coping from there
SQL> shutdown
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
C:\copy c:\oracle\oradata\orcl\controlfilebackup\redo01.log  c:\oracle\oradata\
       1 file(s) copied.
SQL> startup
ORACLE instance started.
Total System Global Area  171966464 bytes
Fixed Size                   787988 bytes
Variable Size             145488364 bytes
Database Buffers           25165824 bytes
Redo Buffers                 524288 bytes
Database mounted.
ORA-00341: log 1 of thread 1, wrong log #  in header
ORA-00312: online log 1 thread 1: 'C:\ORACLE\ORADATA\ORCL\REDO01.LOG'why wrong log # then why we multiplexed the log file there is no advantage of multiplexed log files after moving back it from it mulitplexed location to its original location.

i will read it paul laters,but database is not going to up i tested the experiment again in new freshed database but no use
SQL> alter database add logfile member 'C:\oracle\oradata\orcl1\orcl1\logfilebackup\redo01.log' TO GROUP 1;
Database altered.
SQL> shutdown
Database closed.
Database dismounted.
ORACLE instance shut down.
deleted the log file redo01.log from "C:\oracle\oradata\orcl1\orcl1"
SQL> startup
ORACLE instance started.
Total System Global Area  171966464 bytes
Fixed Size                   787988 bytes
Variable Size             145488364 bytes
Database Buffers           25165824 bytes
Redo Buffers                 524288 bytes
Database mounted.
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: 'C:\ORACLE\ORADATA\ORCL1\ORCL1\REDO01.LOG'
ORA-00312: online log 1 thread 1:
'C:\ORACLE\ORADATA\ORCL1\ORCL1\LOGFILEBACKUP\REDO01.LOG'
SQL> shutdown
ORA-01109: database not open
Database dismounted.
ORACLE instance shut down.
copy the multiplexed log file redo01.log from "C:\oracle\oradata\orcl1\orcl1\logfilebackup"
to "C:\oracle\oradata\orcl1\orcl1"
SQL> startup
ORACLE instance started.
Total System Global Area  171966464 bytes
Fixed Size                   787988 bytes
Variable Size             145488364 bytes
Database Buffers           25165824 bytes
Redo Buffers                 524288 bytes
Database mounted.
ORA-00322: log 1 of thread 1 is not current copy
ORA-00312: online log 1 thread 1: 'C:\ORACLE\ORADATA\ORCL1\ORCL1\REDO01.LOG'
ORA-00312: online log 1 thread 1:
'C:\ORACLE\ORADATA\ORCL1\ORCL1\LOGFILEBACKUP\REDO01.LOG'what i did wrong?

Similar Messages

  • Can u we take online redo log backups using RMAN......can any one guide me

    can u we take online redo log backups using RMAN.....in 1og

    'Backup' solution for online redo logs is multiplexing (members of a group on different independent drives).
    Werner

  • Sizing the redo log files using optimal_logfile_size view.

    Regards
    I have a specific question regarding logfile size. I have deployed a test database and i was exploring certain aspects with regards to selecting optimal size of redo logs for performance tuning using optimal_logfile_size view from v$instance_recovery. My main goal is to reduce the redo bytes required for instance recovery. Currently i have not been able to optimize the redo log file size. Here are the steps i followed:-
    In order to use the advisory from v$instance_recovery i had to set fast_start_mttr_target parameter which is by default not set so i did these steps:-
    1)SQL> sho parameter fast_start_mttr_target;
    NAME TYPE VALUE
    fast_start_mttr_target               integer                           0
    2) Setting the fast_start_mttr_target requires nullifying following deferred parameters :-
    SQL> show parameter log_checkpoint;
    NAME TYPE VALUE
    log_checkpoint_interval integer 0
    log_checkpoint_timeout integer 1800
    log_checkpoints_to_alert boolean FALSE
    SQL> select ISSES_MODIFIABLE,ISSYS_MODIFIABLE,ISINSTANCE_MODIFIABLE,ISMODIFIED from v$parameter where name like'log_checkpoint_timeout';
    ISSES_MODIFIABL ISSYS_MODIFIABLE ISINSTANCE_MODI ISMODIFIED
    FALSE IMMEDIATE TRUE FALSE
    SQL> alter system set log_checkpoint_timeout=0 scope=both;
    System altered.
    SQL> show parameter log_checkpoint_timeout;
    NAME TYPE VALUE
    log_checkpoint_timeout               integer                           0
    3) Now setting fast_start_mttr_target
    SQL> select ISSES_MODIFIABLE,ISSYS_MODIFIABLE,ISINSTANCE_MODIFIABLE,ISMODIFIED from v$parameter where name like'fast_start_mttr_target';
    ISSES_MODIFIABL ISSYS_MODIFIABLE ISINSTANCE_MODI ISMODIFIED
    FALSE IMMEDIATE TRUE FALSE
    Setting the fast_mttr_target to 1200 = 20 minutes of checkpoint switching according to Oracle recommendation
    Querying the v$instance_recovery view
    4) SQL> select ACTUAL_REDO_BLKS,TARGET_REDO_BLKS,TARGET_MTTR,ESTIMATED_MTTR, OPTIMAL_LOGFILE_SIZE,CKPT_BLOCK_WRITES from v$instance_recovery;
    ACTUAL_REDO_BLKS TARGET_REDO_BLKS TARGET_MTTR ESTIMATED_MTTR OPTIMAL_LOGFILE_SIZE CKPT_BLOCK_WRITES
    276 165888 *93* 59 361 16040
    Here Target Mttr was 93 so i set the fast_mttr_target to 120
    SQL> alter system set fast_start_mttr_target=120 scope=both;
    System altered.
    Now the logfile size suggested by v$instance_recovery is 290 Mb
    SQL> select ACTUAL_REDO_BLKS,TARGET_REDO_BLKS,TARGET_MTTR,ESTIMATED_MTTR, OPTIMAL_LOGFILE_SIZE,CKPT_BLOCK_WRITES from v$instance_recovery;
    ACTUAL_REDO_BLKS TARGET_REDO_BLKS TARGET_MTTR ESTIMATED_MTTR OPTIMAL_LOGFILE_SIZE CKPT_BLOCK_WRITES
    59 165888 93 59 290 16080
    After altering the logfile size to 290 as show below by v$log view :-
    SQL> select GROUP#,THREAD#,SEQUENCE#,BYTES from v$log;
    GROUP# THREAD# SEQUENCE# BYTES
    1 1 24 304087040
    2 1 0 304087040
    3 1 0 304087040
    4 1 0 304087040
    5 ) After altering the size i have observed the anomaly as redo log blocks to be applied for recovery has increased from *59 to 696* also now v$instance_recovery view is now suggesting the logfile size of *276 mb*. Have i misunderstood something
    SQL> select ACTUAL_REDO_BLKS,TARGET_REDO_BLKS,TARGET_MTTR,ESTIMATED_MTTR, OPTIMAL_LOGFILE_SIZE,CKPT_BLOCK_WRITES from v$instance_recovery;
    ACTUAL_REDO_BLKS TARGET_REDO_BLKS TARGET_MTTR ESTIMATED_MTTR OPTIMAL_LOGFILE_SIZE CKPT_BLOCK_WRITES
    *696* 646947 120 59 *276* 18474
    Please clarify the above output i am unable to optimize the logfile size and have not been able to achieve the goal of reducing the redo log blocks to be applied for recovery, any help is appreciated in this regard.

    sunny_123 wrote:
    Sir oracle says that fast_start_mttr target can be set to 3600 = 1hour. As suggested by following oracle document
    http://docs.oracle.com/cd/B10500_01/server.920/a96533/instreco.htm
    I set mine value to 1200 = 20 minutes. Later i adjusted it to 120=2 minutes as Target_mttr suggested it to be around 100 (if fast_mttr_target value is too high or too low effective value is contained in target_mttr of v$instance_recovery)Just to add, you are reading the documentation of 9.2 and a lot has changed since then. For example, in 9.2 the parameter FSMTTR was introduced and explicitly required to be set and monitored by the DBA for teh additional checkpoint writes which might get caused by it. Since 10g onwards this parameter has been made automatically maintained by Oracle. Also it's been long that 9i has been desupported followed by 10g so it's better that you start reading the latest documentation of 11g and if not that, at least of 10.2.
    Aman....

  • Why not use Redo log for consistent read

    Oracle 11.1.0.7:
    This might be a stupid question.
    As I understand if a select was issued at 7:00 AM and the data that select is going to read has changed at 7:10 AM even then Oracle will return the data that existed at 7:00 AM. And for this Oracle needs the data in Undo segments.
    My question is since redo also has past and current information why can't redo logs be used to retreive that information? Why is undo required when redo already has all that information.

    user628400 wrote:
    Thanks. I get that piece but isn't it the same problem with UNDO? It's written as it expires and there is no guranteee until we specifically ask oracle to gurantee the UNDO retention? I guess I am trying to understand that UNDO was created for effeciency purposes so that there is less performance overhead as compared to reading and writing from redo.And this also you said,
    >
    If data was changed to 100 to 200 wouldn't both the values be there in redo logs. As I understand:
    1. Insert row with value 100 at 7:00 AM and commit. 100 will be writen to redo log
    2. update row to 200 at 8:00 AM and commit. 200 will be written to redo log
    So in essence 100 and 200 both are there in the redo logs and if select was issued at 7:00 data can be read from redo log too. Please correct me if I am understanding it incorrectly.I guess you didnt understand the explaination that I did. Its not the old data that is kept. Its the changed vector of Undo that is kept which is useful to "recover" it when its gone but not useful as such for a select statement. Whereas in an Undo block, the actual value is kept. You must remember that its still a block only which can contain data just like your normal block which may contain a table like EMP. So its not 100,200 but the change vectors of these things which is useful to recover the transaction based on their SCN numbers and would be read in that order as well. And to read the data from Undo, its quite simple for oracle to do so using an Undo block as the transaction table which holds the entry for the transaction, knows where the old data is kept in the Undo Segment. You may have seen XIDSEQ, XIDUSN, XIDSLOT in the tranaction id which are nothing but the information that where the undo data is kept. And to read it, unlke redo, undo plays a good role.
    About the expiry of Undo, you must know that only INACTIVE Undo extents are marked for expiry. The Active Extents which are having an ongoing tranaction records, are never marked for it. You can come back after a lifetime and if undo is there, your old data would be kept safe by oracle since its useful for the multiversioning. Undo Retention is to keep the old data after commit, something which you need not to do if you are on 11g and using Total Recall feature!
    HTH
    Aman....

  • Why do we need standby redo log on Primary database.

    Hi Gurus,
    I was going through the document in OBE,
    http://www.oracle.com/technology/obe/11gr1_db/ha/dataguard/physstby/physstdby.htm
    I have two queries:
    1) I noticed the statement -
    "Configure the primary database to receive redo data, by adding the standby logfiles to the primary. "
    Why do we have to create standby redo log on a primary database?
    2) There is another statement --
    "It is highly recommended that you have one more standby redo log group than you have online redo log groups as the primary database. The files must be the same size or larger than the primary database’s online redo logs. "
    Why do we need one additional standby redo log group than in Primary database.
    Could anyone please explain to me in simple words.
    Thanks
    Cherrish Vaidiyan

    Hi,
    1. Standby redo logs are used only when the database_role is standby, it is recommended to be added in primary also so that they can be used on role reversal, however during normal working standby redo logs will not be used at all on primary.
    2. In case of 3 online redo log groups, it is recommended to use 4 standby redo log group this is in case if log switching is happening frequently on primary and all 3 standby redo logs are still not completely archived on the standby and 4th can be used here as there will be some delay on standby due to network or slowness of arch on standby.
    Use of the standby redo log groups depends on the redo generation rate, you can see only 2 standby redo logs are getting used while you have 4 standby redo log groups, when the redo generation rate is less.
    So it is recommended to have one more standby redo log group when redo generation rate is high and all of the existing standby redo log group are getting used.
    Regards
    Anudeep

  • Require 9i Primary and Standby redo logs files same size?

    Hi,
    We have 9.2.0.6 Oracle RAC (2 node) and configured data guard (physical standby).
    I want to increase redo log files size, but i can't this do same time primary and standby side.
    Is there a rule, primary and standby database instances have same size redo log files?
    If I increase only primary redo log files, is there any side effect? However I try this issue on test system. I increased all primary redo log files(if status='INACTIVE' drop redo log group and add redo log group, switch logfile,...)
    , but i couldn't changed standby side. So the system is work well. Is this correct solution or not? How can i increase both sides redo log files?
    Thank you for helps..

    Thank you for your helps.. I found this issue answer:
    http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14239/manage_ps.htm#i1010448
    Consequently, when you add or drop an online redo log file at the primary site, it is important that you synchronize the changes in the standby database by following these steps:
    If Redo Apply is running, you must cancel Redo Apply before you can change the log files.
    If the STANDBY_FILE_MANAGEMENT initialization parameter is set to AUTO, change the value to MANUAL.
    Add or drop an online redo log file:
    To add an online redo log file, use a SQL statement such as this:
    SQL> ALTER DATABASE ADD LOGFILE '/disk1/oracle/oradata/payroll/prmy3.log' SIZE 100M;
    To drop an online redo log file, use a SQL statement such as this:
    SQL> ALTER DATABASE DROP LOGFILE '/disk1/oracle/oradata/payroll/prmy3.log';
    Repeat the statement you used in Step 3 on each standby database.
    Restore the STANDBY_FILE_MANAGEMENT initialization parameter and the Redo Apply options to their original states.
    bye..

  • The file structure online redo log, archived redo log and standby redo log

    I have read some Oracle documentation for file structure and settings in Data Guard environment. But I still have some doubts. What is the best file structure or settings in Oracle 10.2.0.4 on UNIX for a data guard environment with 4 primary databases and 4 physical standby databases. Based on Oracle documents, there are 3 redo logs. They are: online redo logs, archived redo logs and standby redo logs. The basic settings are:
    1. Online redo logs --- This redo log must be on Primary database and logical standby database. But it is not necessary to be on physical standby database because physical standby is not open. It doesn't generate redo log. However, if don't set up online redo log on physical standby, when primary failover and switch standby as primary. How can standby perform without online redo logs? In my standby databases, online redo logs have been set up.
    2. Archived redo logs --- It is obviously that primary database, logical and physical standby database all need to have this log file being set up. Primary use it to archive log files and ship to standby. Standby use it to receive data from archived log and apply to database.
    3. Standby redo logs --- In the document, it says A standby redo log is similar to an online redo log, except that a standby redo log is used to store redo data received from another database. A standby redo log is required if you want to implement: The maximum protection and maximum availability levels of data protection and Real-time apply as well as Cascaded destinations. So it seems that this standby redo log only should be set up on standby database, not on primary database. Am my understanding correct? Because I review current redo log settings on my environment, I have found that Standby redo log directory and files have been set up on both primary and standby databases. I would like to get more information and education from experts. What is the best setting or structure on primary and standby database?

    FZheng:
    Thanks for your input. It is clear that we need 3 type of redo logs on both databases. You answer my question.
    But I have another one. In oracle ducument, it says If you have configured a standby redo log on one or more standby databases in the configuration, ensure the size of the current standby redo log file on each standby database exactly matches the size of the current online redo log file on the primary database. It says: At log switch time, if there are no available standby redo log files that match the size of the new current online redo log file on the primary database. The primary database will shut down
    My current one data gurard envirnment setting is: On primary DB, online redo log group size is 512M and standby redo log group size is 500M. On the standby DB, online redo log group size is 500M and standby redo log group size is 750M.
    This was setup by someone I don't know. Is this setting OK? or I should change Standby Redo Log on standby DB to 512M to exactly meatch with redo log size on primary?
    Edited by: 853153 on Jun 22, 2011 9:42 AM

  • Number of Standby Redo Logs on Standby Database

    Hello All:
    Per various docs i calculated and created the number of standby redo logs.
    I created 6 standby redo logs in addition to 3 online.
    However, i always see only two standby redo logs being used. Any ideas?
    Thanks
    San~

    try:
    alter system archive log current;
    and get information:
    select * from v$logfile;
    select * from v$log;
    Thanks.

  • Online Redo logs instead of Standby Redo logs

    RDBMS Version: 11.2.0.3/Platform : RHEL 6.3
    To migrate a 3TB Database to a new DB server , we are going to use RMAN DUPLICATE.
    Step1. Take full backup of DB + Standby Control file at primary site and transfer the Bkp files to Standby site
    Step2. At standy site, we will run the RMAN duplicate target database for standby
    After the above step, we don't want to create the standby redo logs because the newly restored DB in standby server is going to be the new Prod DB which application will be pointing to.
    So, Can I skip the Standby Redo log creation part and create Online redo logs instead  ?
    As mentioned earlier, Our objective is not to create a proper Dataguard Standby DB setup. We just want to clone our DB to another server using RMAN Duplicate.

    Tom wrote:
    RDBMS Version: 11.2.0.3/Platform : RHEL 6.3
    To migrate a 3TB Database to a new DB server , we are going to use RMAN DUPLICATE.
    Step1. Take full backup of DB + Standby Control file at primary site and transfer the Bkp files to Standby site
    Step2. At standy site, we will run the RMAN duplicate target database for standby
    After the above step, we don't want to create the standby redo logs because the newly restored DB in standby server is going to be the new Prod DB which application will be pointing to.
    So, Can I skip the Standby Redo log creation part and create Online redo logs instead  ?
    As mentioned earlier, Our objective is not to create a proper Dataguard Standby DB setup. We just want to clone our DB to another server using RMAN Duplicate.
    Hi,
    Take full backup of DB + Standby Control
    We just want to clone our DB to another server using RMAN Duplicate
    If you want only clone database of production, why you  are take Standby controlfile?
    If you don't want create standby  database then, why you using DUPLICATE  command with FOR STANDBY option.
    You can  use DUPLICATE command for clone database, without for standby option.
    If you  say no, we want create standby database and we will perform swithover,
    then yes, you can use online redo  logs for max performance mode.
    and you can create standby redo logs on all database, but this redo logs will use by database when database role
    is standby.
    Regards
    Mahir M. Quluzade

  • Online redo logs vs standby redo logs

    Hi All,
    Oracle version : 10.2.0.4
    OS : SunOS 5.10 Generic_118855-36 i86pc i386 i86pc
    This might be a silly question for the experts :(
    We are having 2 standby databases and 1 logical database. Everything is running fine , I have one confusion : My primary server having 3 online redo log files and 3 standby redo log files (on primary local), but as per the architecture standby redo logs should be on standby server.My question is whether standby redo logs on standby are online redo logs of standby server or standby redo logs of primary server. e.g If i perform a log switch on primary then what is the role of sync and affirm, will lgwr write parallel on online redo logs ,standby redo logs (of primary) or online redo logs (of primary) and online redo logs (which is known as standby redo logs on standby ). Please help me to understand the scenerio.
    Thanks in advance!

    RFS receives redo information from the primary database.
    RFS can write the redo into standby redo logs or directly to archived redo logs. Each LNSn and ARCn process from the primary database has its own RFS process.
    A standby redo log is used only when the database is in the standby role to store redo data received from the primary database. Standby redo logs form a separate pool of log file groups.
    Configuring standby redo log files is highly recommended on all standby databases in a Data Guard configuration, including the primary database to aid in role reversal.
    A standby redo log is required to implement:
    • The maximum protection and maximum availability levels of data protection
    • Real-time apply
    • Cascaded redo log destinations
    Standby redo logs are recommended for maximum performance data protection mode. Unless you are using the real-time apply feature, standby redo logs must be archived before the data can be applied to the standby database. The standby archival operation occurs automatically.

  • Standby redo log status

    Can anyone explain what the status of clearing means when viewing standby redo log status?
    SQL> select status from v$log;
    STATUS
    CLEARING
    CLEARING
    CURRENT
    This is a bit different to what we'd see on an open database.

    Hello;
    Log is being re-created as an empty log.
    In a Standby database the regular redo are not used ( when not in PRIMARY MODE) only the standby redo logs are used. Sometimes as buffers for the redo coming from the primary.
    You should be able to change the status by doing a ALTER SYSTEM SWITCH LOGFILE on your primary.
    This note may help:
    Online Redo Logs on Physical Standby [ID 740675.1]
    Also
    Take a look at v$standby_log too.
    http://docs.oracle.com/cd/B28359_01/server.111/b28320/dynviews_3068.htm
    Best Regards
    mseberg

  • Backup of redo log files

    Hello,
    How can I make a backup with redo log files using the following parameters?
    backup_type = online_cons
    backup_dev_type =  disk_copy
    -->archive_function = save_delete (It could be changed. Maybe it is the source of the error)
    The copy is made, but an error occurs when it tries to copy the redo log files. The log shows the following message:
    BR0291I BRARCHIVE will be started with options '-U -d disk_copy -c force -p initFDP_local.sap -cds'
    BR0002I BRARCHIVE 6.40 (43)
    BR0169I Value 'disk_copy' of parameter/option 'backup_dev_type/-d' ignored for 'brarchive' - 'disk'assumed
    BR0181E Option '-cds' not supported for 'disk'
    BR0007I End of offline redo log processing: adxexvpd.log 2008-02-06 03.41.57
    Thanks in advance,
    Ricard.
    Edited by: Oscar Barrabes on Feb 6, 2008 10:08 AM

    Hi Ricard,
    You are right, you need to change the entry
    archive_function = save_delete
    to
    archive_function = save
    in init<SID>.sap
    Nahum

  • Behaviuor in reading logs from DB13 - redo log backup for DB

      Hi all,
    I have a question ,
    We have scheduled redo log backup using HP DP Tool.
    When I am reading a backup log from DB13 , I am facing the weird behavior.
    copy, delete, save
    0000
    aeomzyok.cds
    copy, delete, save
    0001
    aeomzyoh.cds
    Where ever the RC is 000 I am able to read the log files available at OS level . But not able to read the log for other RC.
    Please help me to understand this
    Thanks,
    Gnana

    Hi Gnana.
    Use the latest BR*Tools as there were problems with permission issues while creating logfiles. In the latest BR*Tools version, the different logfiles are created with predefined permission levels that suits to SAP needs.
    Also it worth to check if the BR*Tools executables hav the correct ownership.
    113747 Owners and authorizations for BR*Tools
    Regards,
    János

  • Backup Not Starting for 'Whole database offline + redo log backup' @ DB13

    Hi Experts,
    I am not able to perform 'Whole database offline + redo log backup' by DB13.
    I have recently configured my 'init<SID>.sap'  to take 'Whole database online + redo log backup' and its working perfectly fine.
    I tried taking test backup for  'Whole database offline + redo log backup'  but it didn't even  started.
    Thus I created another profile with name init<SID>back.sap  and changed the Parameter
    from 'backup_type = online'  to 'backup_type = offline' and also tried by 'backup_type = offline_force'
    rest all parameters being same as the profile  init<SID>.sap
    Kindly Suggest as I need to take set the backup Strategy as  Mon-Fri  -> 'Whole database offline + redo log backup'  and Sat ->  'Whole database offline + redo log backup'
    One more Query : While taking the redo log backup by DB13 why is it that some times it only saves the Files and some time it
    saves and delete the files from the '/oracle/<SID>/oraarch'  location. Please throw some light over this matter also.
    Thanks,
    Jitesh

    Hi Mr Bhavik,
    Thanks for your reply..  Here are the details you have asked for.
    1.My SAP BASIS Patch Level  is :  10. ( We shall be updating it by the end of this Year)
    2. Br*tools version is :
    BRTOOLS   7.00 (11)
    kernel release    700
    patch level   11
    3. I don't have any file with name alert<dbsid>.log file (located at /oracle/<SID>/saptrace/background/) but i do have alert_<SID>.log
    I execute the command more -p G alert_JMD.log
    after my  'Whole database offline + redo log backup' again failed at DB13 but I was not able to see any specific complains while executing the above action.
    I got the Error Detailed Log in DB13 as :
    Detail log:                    beeneedv.aft
    BR0051I BRBACKUP 7.00 (20)
    BR0055I Start of database backup: beeneedv.aft 2010-11-08 13.16.43
    BR0484I BRBACKUP log file: /oracle/JMD/sapbackup/beeneedv.aft
    BR0280I BRBACKUP time stamp: 2010-11-08 13.16.43
    BR0261E BRBACKUP cancelled by signal 13
    BR0056I End of database backup: beeneedv.aft 2010-11-08 13.16.44
    BR0280I BRBACKUP time stamp: 2010-11-08 13.16.45
    BR0054I BRBACKUP terminated with errors
    4. No I have not yet Tried 'execute such Offline+REdo log backups using brback command', will Try and post it Definately
    5. Query : select grantee, granted_role from dba_role_privs;
    result :
    SQL> select grantee, granted_role from dba_role_privs;
    GRANTEE                        GRANTED_ROLE
    SYS                            SAPDBA
    SYS                            EXP_FULL_DATABASE
    SYS                            CONNECT
    IMP_FULL_DATABASE              SELECT_CATALOG_ROLE
    DBSNMP                         OEM_MONITOR
    SAPSR3                         CONNECT
    OPS$SAPSERVICEJMD              SAPDBA
    SYS                            SELECT_CATALOG_ROLE
    DBA                            DELETE_CATALOG_ROLE
    DBA                            EXECUTE_CATALOG_ROLE
    SYSTEM                         DBA
    GRANTEE                        GRANTED_ROLE
    OPS$ORAJMD                     SAPDBA
    SAPDBA                         GATHER_SYSTEM_STATISTICS
    SYS                            SCHEDULER_ADMIN
    SYS                            AQ_USER_ROLE
    SYS                            GATHER_SYSTEM_STATISTICS
    SYS                            DELETE_CATALOG_ROLE
    DBA                            GATHER_SYSTEM_STATISTICS
    DBA                            IMP_FULL_DATABASE
    EXECUTE_CATALOG_ROLE           HS_ADMIN_ROLE
    IMP_FULL_DATABASE              EXECUTE_CATALOG_ROLE
    OPS$JMDADM                     CONNECT
    GRANTEE                        GRANTED_ROLE
    SYS                            LOGSTDBY_ADMINISTRATOR
    SYS                            EXECUTE_CATALOG_ROLE
    SYS                            RESOURCE
    DBA                            SCHEDULER_ADMIN
    DBA                            SELECT_CATALOG_ROLE
    EXP_FULL_DATABASE              EXECUTE_CATALOG_ROLE
    SAPDBA                         SELECT_CATALOG_ROLE
    SYS                            SAPCONN
    SYS                            OEM_ADVISOR
    SYS                            IMP_FULL_DATABASE
    SELECT_CATALOG_ROLE            HS_ADMIN_ROLE
    GRANTEE                        GRANTED_ROLE
    OUTLN                          RESOURCE
    LOGSTDBY_ADMINISTRATOR         RESOURCE
    SAPSR3                         RESOURCE
    OPS$SAPSERVICEJMD              RESOURCE
    SYS                            RECOVERY_CATALOG_OWNER
    DBA                            EXP_FULL_DATABASE
    EXP_FULL_DATABASE              SELECT_CATALOG_ROLE
    TSMSYS                         RESOURCE
    OPS$ORAJMD                     RESOURCE
    SAPCONN                        SELECT_CATALOG_ROLE
    SYS                            OEM_MONITOR
    GRANTEE                        GRANTED_ROLE
    SYS                            AQ_ADMINISTRATOR_ROLE
    SYS                            DBA
    SYSTEM                         AQ_ADMINISTRATOR_ROLE
    OPS$ORAJMD                     CONNECT
    OPS$JMDADM                     SAPDBA
    OPS$JMDADM                     RESOURCE
    SAPSR3                         SAPCONN
    SYS                            HS_ADMIN_ROLE
    SYSTEM                         SAPDBA
    OPS$SAPSERVICEJMD              CONNECT

  • Groups and Member in Redo Log

    Hi,
    I would like to the defination and the functionality of Groups and Member in a Redo log file and also the distinction between them
    Thks

    Dear J.C.,
    The redo logs are files that the Oracle server uses to commit or rollback the transactions applied by the users.
    Redo Log files (minimum of two files) record all changes made to the database, hence ensuring that no data is lost in the event of a failure. In case of an instance failure, when the database is next started up, the Oracle server is automatically able to roll forward the transactions that were not applied when the database crashed and roll back the uncommitted transactions from the rollback segments. Hence the database recovers automatically to a consistent state that existed prior to the crash.
    A set of Redo Log files is called a Redo Log Group. Multiple copies (mirroring) of the Redo Log Files are used so as to protect the Redo Log Files from corruption / damage. Each Redo Log File in a Redo Log Group (called Redo Log Member) has essentially the same information, so if one is destroyed, another copy of that file is available for the Oracle server to use.
    Finally, the term Redo Log is used interchangeably with Redo Log Group.
    Ciao!

Maybe you are looking for