Configuration of rman for dataguard environment.

Hi all

Here we have an environment dataguard with as primary db1 and db2 as Physics of the standby database. We have configured dataguard in environments of 10 g and we don't use a grid control. Can anyone provide for incremental backups rman configuration steps in this environment? We want to schedule backups to take standby db (which is also applicable in the case of swithover). In the case of swithover for db2, what should we do to rman manually resume db1 backups?

Thank you

Hello;

A database of Eve is a copy of the primary, so if you try to save it RMAN will probably tell you already recorded sound. Let me start with this:

Watch the basic backup

1 activate the automatic backup of the control file and server parameter file. CONFIGURE CONTROLFILE AUTOBACKUP ON.
2. move the backups already backup of data files. CONFIGURE BACKUP OPTIMIZATION.
3. set the deletion of archives policy. CONFIGURE THE POLICY OF DELETION VOTES AGAINST ZERO.

You need to decide on the exact RMAN script to use, but because the database is saved you can perform a backup on the primary or standby as necessary.

See "With RMAN to back up and restore files" in "the DataGuard of Concepts and Administration 10 g Release 2 (10.2)" B14239-05 ".

http://docs.Oracle.com/CD/B19306_01/server.102/b14239/RMAN.htm

Example in this post

How to manage backups of database primary and standby with rman catalog

How to use the backup of the previous day to restore primary db

http://alexzeng.WordPress.com/2008/09/13/how-to-use-standby-backup-to-restore-primary-DB/

Best regards

mseberg

Tags: Database

Similar Questions

  • Configuring RMAN for dataguard.

    Hi all

    Here we have an environment dataguard with db1 (db_unique_name) as primary and db2 (db_unique_name) Physics of the standby database. For primary and secondary the ORACLE_SID is "oracledb." We have configured dataguard in environments of 10 g and we don't use a grid control. And now we want to configure rman for incremental backups. We use a third database of catalog which we recorded primary DB successfully. When the primary configuration of rman is show conflicts. Even changes to the main configuration of RMAN are applied on the standby too who I think shouldn't happen in this scenario. How to solve this problem? Is what is happening because of the ORACLE_SID even for primary and secondary school? I enclose the link from the doc, we also followed the errors and configuring in rman. Can anyone help?

    http://docs.Oracle.com/CD/B28359_01/server.111/b28294/RMAN.htm#BAJFBBBB


    RMAN > CONFIGURE ARCHIVELOG DELETION POLICY APPLIED PENDING;

    new RMAN configuration settings:
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
    new RMAN configuration settings are stored successfully
    from full resynchronization of the recovery catalog
    full complete Resync
    RMAN-08591: WARNING: invalid archivelog deletion policy

    RMAN > set UP DB_UNIQUE_NAME db1 CONNECT ID "db1".

    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-00558: error occurred during parsing of order entry
    RMAN-01009: syntax error: found 'db_unique_name': expected an a: ' archivelog, auxiliary, auxname, backup, channel, controlfile, clonename, compatible, datafile, device, by default, exclude, encryption, maxsetsize, retention, instant.
    RMAN-01007: line 1 column 11 file: entry standard


    RMAN > show all.

    from full resynchronization of the recovery catalog
    full complete Resync
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY OF 2 DAYS WINDOW;
    CONFIGURE BACKUP OPTIMIZATION # by default
    SET UP DEFAULT DISK DEVICE TYPE; # by default
    CONFIGURE CONTROLFILE AUTOBACKUP # by default
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
    SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
    CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
    CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
    CONFIGURE ENCRYPTION OF DATABASE # by default
    CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
    CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / u01/app/oracle/product/10.2.0/db_1/dbs/snapcf_NIOS.f'; # by default


    Thank you.

    Hello

    You must set log_archive_dest_2 (for the standby database) mandatory
    Like this

    alter system set log_archive_dest_2= 'service=standby lgwr async valid_for=(online_logfiles,primary_role) *mandatory*';
    

    try again the configuration of the deletion of journal policy archive on RMAN.

  • We have configured replication vsphere in our environment and when replication is triggered according to the OFR start us below the questions on the virtual machines that are configured for replication

    Question: We have configured replication vsphere in our environment and when replication is triggered according to the OFR start us below the questions on the virtual machines that are configured for replication.

    Version for esxi: Patch 5.1 level 7

    Virtual center of version 5.1

    Source of storage - IBM v7000

    Destination storage - Hitachi


    Questions:
    Events of breach RPO
    Consolidation for the VM disk failure
    Delta abandoned events
    Time change events
    NTFS error and warning (event ID: 137, 57)
    RDP disconnect and ping does matter
    Standby error
    Volsnap error
    Stop the server and offline issue
    Install vmtools emits automatically

    well, in this case, we need to disable the standby of the end of the replication.

    So that everything in triggering replication does not trigger the snapshot of the suspension.

    Then test the if you get these errors.

  • With RMAN for backup, but not with the archive logs

    We run a 10.2.0.4 database and the rest 11.2.0.3. All databases are on RHEL 5.7.

    Our backups are via RMAN, with the data files, controlfiles and spfile saved to disk, then each day, it is copied off site to a backup server.

    My question is around logs archiving and RMAN.
    Our current situation is:
    -We do not save the logs to archive via RMAN. for example: backup of the list of the archivelog all; gives "specification does not match backups in the repository.
    -We set the archive_lag_target so archiving logs is produced every 30 minutes.
    -a cron job running on a remote server runs periodically to synchronize data (rsync server) the directory of archives with a remote control.
    -daily archive logs on the server host are bzip. Purge of these newspapers is scheduled for more than 3 days rman 'window of recovery '.

    I'm interested in feedback as to if our strategy around archiving logs is correct or not.

    Should we be backup logs archiving via RMAN? Are there potential problems with our approach?
    We just kept our backups in this way the DBA in the past want to see newspapers archived as opposed to it while a backupset.

    Curious to know what others are doing.

    Hello

    Welcome to OTN!

    Archivelogs with RMAN backup is a better option. When the archives are supported by RMAN, RMAN would be aware of the backup items which are required at the time of the recovery archives. You don't have to do it manually.

    On the disk space, you can delete the archives once they were saved by RMAN.

    RMAN > delete any backup archivelog entry;

    This supports the archivelogs and then remove the archives from the disk.

    If you have a dataguard configured, you can set the deletion policy 'applied on Eve', which removes the archives as and when they are applied to the database ensures there by the management of disk space again.

    RMAN > configure archivelog political of deletion to applied pending;

  • What is the command to view the Configuration of RMAN

    What is the command to view the Configuration of RMAN

    in oracle 11g R2

    Hello

    You have to look in the documentation?

    The SHOW ALL command will show you the configuration. Is that what you're looking for?

  • Problem with the archive log when you use RMAN for backup and restore (11g 2)

    Hello world
    Please help me solve this problem.
    I'm just beginner in Oracle Database (11 g 2). Today, I had a problem, I tried to back up and restore my db by RMAN. I delete all the files in /u01/app/oracle/oradata/orcl / * , then I restore them easily, but the point is I have a table, I can restore Hungarian, but cannot restore anything ranks in it (something wrong with step restore database). I'll tell the detail below.
    -First, I create a 'Day' with command table create table hr.day (varchar (20)) day. Then I backup complete by this:
    run{
    allocate channel bkp device type DISK FORMAT '/u01/backup/DB_FULL_%d_%T_s%s_p%p' ;
    backup as compressed backupset incremental level 0 tag 'DB_FULL' database include current controlfile;
    backup as compressed backupset tag 'ARCL_BKP_FULL' archivelog all delete input;
    crosscheck archivelog all;
    crosscheck backup;
    delete noprompt obsolete;
    release channel bkp;
    }


    D ' other hand, I have insert 'Monday' to table. then do an incremental backup by this:

    run{
    allocate channel bkp device type DISK FORMAT '/u01/backup/DB_INC_%d_%T_s%s_p%p' ;
    backup as compressed backupset incremental level 1 tag 'DB_INC' database include current controlfile;
    backup as compressed backupset tag 'ARCL_BKP_INC' archivelog all delete input;
    crosscheck archivelog all;
    crosscheck backup;
    delete noprompt obsolete;
    release channel bkp;
    }

    Repeat 7 times (Monday-> Saturday). And I got these files:

    [oracle@rac ~]$ ls -l /u01/backup/
    total 400280
    -rw-r----- 1 oracle oinstall  10158080 Jan 20 07:23 c-1428943247-20160120-01
    -rw-r----- 1 oracle oinstall  10158080 Jan 20 08:04 c-1428943247-20160120-02
    -rw-r----- 1 oracle oinstall  10158080 Jan 20 08:05 c-1428943247-20160120-03
    -rw-r----- 1 oracle oinstall  10158080 Jan 20 08:06 c-1428943247-20160120-04
    -rw-r----- 1 oracle oinstall  10158080 Jan 20 08:08 c-1428943247-20160120-05
    -rw-r----- 1 oracle oinstall  10158080 Jan 20 08:08 c-1428943247-20160120-06
    -rw-r----- 1 oracle oinstall  10158080 Jan 20 08:09 c-1428943247-20160120-07
    -rw-r----- 1 oracle oinstall  10158080 Jan 20 08:32 c-1428943247-20160120-08
    -rw-r----- 1 oracle oinstall 296337408 Jan 20 07:23 DB_FULL_ORCL_20160120_s89_p1
    -rw-r----- 1 oracle oinstall   1130496 Jan 20 07:23 DB_FULL_ORCL_20160120_s90_p1
    -rw-r----- 1 oracle oinstall   2266624 Jan 20 07:23 DB_FULL_ORCL_20160120_s91_p1
    -rw-r----- 1 oracle oinstall   4073984 Jan 20 07:23 DB_FULL_ORCL_20160120_s92_p1
    -rw-r----- 1 oracle oinstall  11201536 Jan 20 07:23 DB_FULL_ORCL_20160120_s93_p1
    -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:05 DB_INC_ORCL_20160120_s100_p1
    -rw-r----- 1 oracle oinstall    146944 Jan 20 08:05 DB_INC_ORCL_20160120_s101_p1
    -rw-r----- 1 oracle oinstall    884736 Jan 20 08:06 DB_INC_ORCL_20160120_s103_p1
    -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:06 DB_INC_ORCL_20160120_s104_p1
    -rw-r----- 1 oracle oinstall     82432 Jan 20 08:06 DB_INC_ORCL_20160120_s105_p1
    -rw-r----- 1 oracle oinstall    294912 Jan 20 08:07 DB_INC_ORCL_20160120_s107_p1
    -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:07 DB_INC_ORCL_20160120_s108_p1
    -rw-r----- 1 oracle oinstall     18944 Jan 20 08:08 DB_INC_ORCL_20160120_s109_p1
    -rw-r----- 1 oracle oinstall    155648 Jan 20 08:08 DB_INC_ORCL_20160120_s111_p1
    -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:08 DB_INC_ORCL_20160120_s112_p1
    -rw-r----- 1 oracle oinstall    131584 Jan 20 08:08 DB_INC_ORCL_20160120_s113_p1
    -rw-r----- 1 oracle oinstall    647168 Jan 20 08:09 DB_INC_ORCL_20160120_s115_p1
    -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:09 DB_INC_ORCL_20160120_s116_p1
    -rw-r----- 1 oracle oinstall      8704 Jan 20 08:09 DB_INC_ORCL_20160120_s117_p1
    -rw-r----- 1 oracle oinstall   2203648 Jan 20 08:04 DB_INC_ORCL_20160120_s95_p1
    -rw-r----- 1 oracle oinstall   1130496 Jan 20 08:04 DB_INC_ORCL_20160120_s96_p1
    -rw-r----- 1 oracle oinstall   1899008 Jan 20 08:04 DB_INC_ORCL_20160120_s97_p1
    -rw-r----- 1 oracle oinstall    327680 Jan 20 08:05 DB_INC_ORCL_20160120_s99_p1

    And
    RMAN> list backup summary;
    List of Backups
    ===============
    Key     TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
    ------- -- -- - ----------- --------------- ------- ------- ---------- ---
    80      B  0  A DISK        20-JAN-16       1       1       YES        DB_FULL
    81      B  0  A DISK        20-JAN-16       1       1       YES        DB_FULL
    82      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL
    83      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL
    84      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_FULL
    85      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T072332
    86      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    87      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    88      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
    89      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080440
    90      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    91      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    92      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
    93      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080545
    94      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    95      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    96      B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
    97      B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080657
    98      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    99      B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    100     B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
    101     B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080801
    102     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    103     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    104     B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC
    105     B  F  A DISK        20-JAN-16       1       1       NO         TAG20160120T080844
    106     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    107     B  1  A DISK        20-JAN-16       1       1       YES        DB_INC
    108     B  A  A DISK        20-JAN-16       1       1       YES        ARCL_BKP_INC

    My configuration of rman:
    RMAN> show all;
    RMAN configuration parameters for database with db_unique_name ORCL are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u01/backup/%F';
    CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '/u01/backup/backup_df%t_s%s_s%p';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome/dbs/snapcf_orcl.f'; # default

    - Thirdly, i removed all file in /u01/app/oracle/oradata/orcl/*. then restore control file from the newest backup control file (saturday backup) + restore database. Seem nothing's wrong here.
    RMAN> restore controlfile from '/u01/backup/c-1428943247-20160120-08';
    Starting restore at 20-JAN-16
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=18 device type=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: SID=20 device type=DISK
    channel ORA_DISK_2: skipped, AUTOBACKUP already found
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:09
    output file name=/u01/app/oracle/oradata/orcl/control01.ctl
    output file name=/u01/app/oracle/flash_recovery_area/orcl/control02.ctl
    Finished restore at 20-JAN-16

    RMAN> alter database mount;
    database mounted
    released channel: ORA_DISK_1
    released channel: ORA_DISK_2

    RMAN> restore database;
    Starting restore at 20-JAN-16
    Starting implicit crosscheck backup at 20-JAN-16
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=20 device type=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: SID=18 device type=DISK
    Crosschecked 29 objects
    Finished implicit crosscheck backup at 20-JAN-16

    Starting implicit crosscheck copy at 20-JAN-16
    using channel ORA_DISK_1
    using channel ORA_DISK_2
    Finished implicit crosscheck copy at 20-JAN-16

    searching for all files in the recovery area
    cataloging files...
    no files cataloged

    using channel ORA_DISK_1
    using channel ORA_DISK_2

    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00001 to /u01/app/oracle/oradata/orcl/system01.dbf
    channel ORA_DISK_1: restoring datafile 00002 to /u01/app/oracle/oradata/orcl/sysaux01.dbf
    channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/orcl/undotbs01.dbf
    channel ORA_DISK_1: restoring datafile 00004 to /u01/app/oracle/oradata/orcl/users01.dbf
    channel ORA_DISK_1: restoring datafile 00005 to /u01/app/oracle/oradata/orcl/example01.dbf
    channel ORA_DISK_1: reading from backup piece /u01/backup/DB_FULL_ORCL_20160120_s89_p1
    channel ORA_DISK_1: piece handle=/u01/backup/DB_FULL_ORCL_20160120_s89_p1 tag=DB_FULL
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:15
    Finished restore at 20-JAN-16

    -Fourth, the problem here, I got the database;
    .. .every oky until this line...
    starting media recovery

    channel ORA_DISK_1: starting archived log restore to default destination
    channel ORA_DISK_1: restoring archived log
    archived log thread=1 sequence=15
    channel ORA_DISK_1: reading from backup piece /u01/backup/DB_INC_ORCL_20160120_s117_p1
    channel ORA_DISK_1: piece handle=/u01/backup/DB_INC_ORCL_20160120_s117_p1 tag=ARCL_BKP_INC
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
    archived log file name=/u01/app/oracle/flash_recovery_area/ORCL/archivelog/2016_01_20/o1_mf_1_15_c9xsyx9k_.arc thread=1 sequence=15
    unable to find archived log
    archived log thread=1 sequence=1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 01/20/2016 08:50:22
    RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 1 and starting SCN of 1205841

    The error said that it is impossible to find the archived log thread = 1 sequence = 1. Then I check it with this command always there (oh, I'm wrong?)
    RMAN> list backup of archivelog all;
    List of Backup Sets
    ===================
    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    82      2.16M      DISK        00:00:00     20-JAN-16     
            BP Key: 82   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_FULL
            Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s91_p1

      List of Archived Logs in backup set 82
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
    1    1       1154833    20-JAN-16 1177422    20-JAN-16

    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    83      3.88M      DISK        00:00:00     20-JAN-16     
            BP Key: 83   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_FULL
            Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s92_p1

      List of Archived Logs in backup set 83
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
    1    1       1162729    20-JAN-16 1188784    20-JAN-16

    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    84      10.68M     DISK        00:00:01     20-JAN-16     
            BP Key: 84   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_FULL
            Piece Name: /u01/backup/DB_FULL_ORCL_20160120_s93_p1

      List of Archived Logs in backup set 84
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    2       1177422    20-JAN-16 1201833    20-JAN-16

    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    88      1.81M      DISK        00:00:01     20-JAN-16     
            BP Key: 88   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
            Piece Name: /u01/backup/DB_INC_ORCL_20160120_s97_p1

      List of Archived Logs in backup set 88
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    3       1201833    20-JAN-16 1204844    20-JAN-16
      1    4       1204844    20-JAN-16 1204893    20-JAN-16
      1    5       1204893    20-JAN-16 1204958    20-JAN-16

    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    92      143.00K    DISK        00:00:00     20-JAN-16     
            BP Key: 92   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
            Piece Name: /u01/backup/DB_INC_ORCL_20160120_s101_p1

      List of Archived Logs in backup set 92
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    6       1204958    20-JAN-16 1205034    20-JAN-16
      1    7       1205034    20-JAN-16 1205253    20-JAN-16

    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    96      80.00K     DISK        00:00:00     20-JAN-16     
            BP Key: 96   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
            Piece Name: /u01/backup/DB_INC_ORCL_20160120_s105_p1

      List of Archived Logs in backup set 96
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    8       1205253    20-JAN-16 1205354    20-JAN-16
      1    9       1205354    20-JAN-16 1205433    20-JAN-16

    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    100     18.00K     DISK        00:00:00     20-JAN-16     
            BP Key: 100   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
            Piece Name: /u01/backup/DB_INC_ORCL_20160120_s109_p1

      List of Archived Logs in backup set 100
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    10      1205433    20-JAN-16 1205519    20-JAN-16
      1    11      1205519    20-JAN-16 1205559    20-JAN-16

    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    104     128.00K    DISK        00:00:00     20-JAN-16     
            BP Key: 104   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
            Piece Name: /u01/backup/DB_INC_ORCL_20160120_s113_p1

      List of Archived Logs in backup set 104
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    12      1205559    20-JAN-16 1205624    20-JAN-16
      1    13      1205624    20-JAN-16 1205739    20-JAN-16

    BS Key  Size       Device Type Elapsed Time Completion Time
    ------- ---------- ----------- ------------ ---------------
    108     8.00K      DISK        00:00:00     20-JAN-16     
            BP Key: 108   Status: AVAILABLE  Compressed: YES  Tag: ARCL_BKP_INC
            Piece Name: /u01/backup/DB_INC_ORCL_20160120_s117_p1

      List of Archived Logs in backup set 108
      Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
      ---- ------- ---------- --------- ---------- ---------
      1    14      1205739    20-JAN-16 1205796    20-JAN-16
      1    15      1205796    20-JAN-16 1205840    20-JAN-16


    If i ignore it and open the database, just my table in full backup come back but rows was not restored. I'm sure the problem is my archive log backup but i don't know how to solve it. Plz help me.

    Sorry for a long post.

    > 1 and from the 1205841 SNA sequence

    The SCN that indicates Oracle is above the range of SNA that you have in the ArchiveLog backups for sequence 1 to 15 (15 sequence ends at 1205840).

    The message

    channel ORA_DISK_1: restoring archives Journal

    Archives journal thread = 1 sequence = 15

    channel ORA_DISK_1: backup/u01/backup/DB_INC_ORCL_20160120_s117_p1 piece reading

    channel ORA_DISK_1: piece handle = / u01/backup/DB_INC_ORCL_20160120_s117_p1 tag = ARCL_BKP_INC

    indicates that he has restored the sequence up to 15

    You can check the log file alert database instance for messages on the fact of recovery.

    He is now asking sequence #1 it seems you did a RESETLOGS after sequence #15.

    Note: If you have NOT issued a COMMIT after the line is INSERTED in the table 'Day', the recovery of the database will have no * transactions * to retrieve.  An uncomitted transaction is cancelled.

    Hemant K Collette

  • Configure Alerts email for hardware failures

    Our ESXi 5.5 environment goes live today and now it will be in production I was wondering if there was a way to configure alerts email for hardware failures. For example, if a disk goes wrong in our RAID array, I want to be emailed on this subject. Is this possible, and is there a link to find out how to implement that?

    Go to the Administration menu-> vCenter Server Settings-> E-mail and enter SMTP server and the account of the sender.

  • Configure SNMP source for the events of HW for IPMI sensors

    Us run Dell hardware and tested OMSA installed on ESXi5 hosts pointing to OpenManage (OME) Essentials for any interruptions SNMP. As indicated in the following Dell FAQ for OME the 9.5 troubleshooting section, to avoid massive amounts of alerts unknown on the server of the OME from our hosts ESXi5 we define the SNMP CIM for IPMI event source.

    http://en.community.Dell.com/TechCenter/systems-management/w/wiki/3265.OpenManage-Essentials-FAQ.aspx

    This article as well as VMware material and KB, any reference to the need to use the vSphere CLI to make this change, which of course works such as documented. Does anyone know if it is possible to make this change via PowerCLI? We do not want to use the vSphere CLI unless it's the only possible way as all the other configuration items that we have implemented kickstart or PowerCLI scripting.

    http://KB.VMware.com/kb/1008065

    http://pubs.VMware.com/vSphere-50/topic/com.VMware.vSphere.monitoring.doc_50/GUID-01D333E8-0A34-4F04-BB6C-D80A5FDA8CC5.html

    I was able to find the key value pair in PowerCLI where EnvEventSource/directions options, but I don't know if those who may be changed.

    If someone knows a way to do this, I would like to know how it is possible.

    Thank you.

    I think I knew that.  It seems that you have to connect directly to the ESXi host nothing to do with SNMP still, but if someone knows a way to avoid this, I'd love to hear it.  But this seems to work at the same time, but would need to change to more than one host at a time.

    ## Script function: Modify SNMP source for hardware events
    ## Usage: Connect to vCenter where host(s) reside, populate constants below and run
    
    ## Host to make changes to
    $strVMHost = "your_ESXi_5_host"
    
    ## Credentials for ESXi host(s)
    $strUser = "root"
    $strPassword = "your_password"
    
    ## Key to change value on (in case there are different key/value pairs you need to change in the future)
    $keySnmpEventSource = "EnvEventSource"
    
    ## New value for above key
    $valueSnmpEventSource = "sensors"
    
    ## Connect directly to VMHost in order to see the HostSnmpSystem object (http://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.apiref.doc_50/vim.host.SnmpSystem.html)
    Connect-VIServer -Server $strVMHost -User $strUser -Password $strPassword
    
    ## Get the VMHost .NET View object and select only the HostSnmpSystem object
    $viewHost = Get-VMHost -Server $strVMHost -Name $strVMHost | Get-View -Property ConfigManager.SnmpSystem
    
    ## Get the HostSnmpSystem object
    $viewHostSnmpSystem = Get-View -Id $viewHost.ConfigManager.SnmpSystem
    
    ## Create new empty HostSnmpConfigSpec (http://pubs.vmware.com/vsphere-50/topic/com.vmware.wssdk.apiref.doc_50/vim.host.SnmpSystem.SnmpConfigSpec.html)
    $specHostSnmpConfigSpec = New-Object VMware.Vim.HostSnmpConfigSpec
    
    ## Populate newly created HostSnmpConfigSpec object with current values
    $specHostSnmpConfigSpec = $viewHostSnmpSystem.Configuration
    
    ## Modify desired value for the matching key
    ($specHostSnmpConfigSpec.Option | ?{$_.Key -eq $keySnmpEventSource}).Value = $valueSnmpEventSource
    
    ## Reconfigure the SNMP agent to take the new value
    $viewHostSnmpSystem.ReconfigureSnmpAgent($specHostSnmpConfigSpec)
    
    ## Disconnect from VMHost
    Disconnect-VIServer -Server $strVMHost -Confirm:$false
    

    Let me know if it works for your environment that we not use SNMP in ours, so I didn't do extensive testing.

  • How to test the failover of dataguard environment?

    I would like to test failover (no pass) in dataguard environment.
    How to get there?

    Thank you.

    Hello;

    Happy to share my test notes:

    http://www.Visi.com/~mseberg/Data_Guard_Failover_Test_using_SQL.PDF

    These oracle notes can also help:

    Can I use manual SQL * PLUS measures for (passage, failover, etc...), if DataGuard broker has already activated and GridControl is also used? [744396.1 ID]

    Oracle10g: Passage to the custody of data and failover best practices [ID 387266.1]

    Step by step guide on how to restore doesn't have a primary database standby physics [ID 738642.1]

    Best regards

    mseberg

  • Doubt RMAN for recovey

    Hello

    I'm learing RMAN and beginner in this area. I have a doubt for recovey db.
    I took hotbackup full db using controlfile deposit of GR 11, 2 db. Then I restored it on the same host, directory structure has also been even during the restoration restore n as it was during the backup.

    Safeguard measures:
    RMAN > configure redundancy 2 retention policy;
    RMAN > set the parallelism of peripheral disc type 2;
    RMAN > configure channel device type disk format ' / home/oracle/rman_backup/ora_df%t_b%s_p%p';
    RMAN > configure controlfile autobackup on;
    RMAN > configure CONTROLFILE AUTOBACKUP peripheral type disc format in ' / home/oracle/rman_backup/ora_cf%F';
    RMAN > set up optimization backup;
    RMAN > show all.
    RMAN > backup the database archivelog;

    Restore and refresh as follows:

    *. On SQLPLUS, stop immediately
    *. Remove all the data files, redo logs, control files, newspapers archived (of the oradata and flashback area)
    *. On the RMAN command prompt:
    1 RMAN > startup nomount;
    2 RMAN > restore controlfile to ' / home/oracle/rman_backup/ora_cfc-4124714611-20110510-00';
    3 RMAN > change the editing of the database;
    4 RMAN > restore database;
    5 RMAN > backup from the list of the archivelog all;
    6 RMAN > recover database until sequence 6.
    7 RMAN > alter database open resetlogs;


    On the SQL command prompt:

    8. SQL > select group # first_change #, status, sequence #, archived log v$. (this step was performed before you recover the database, that is to say prior to step 6)

    GROUP # FIRST_CHANGE # STATUS # ARC SEQUENCE

    1 962626 YES 4 INACTIVE
    3 979898 6 CURRENT NO.
    *2        979836                      ACTIVE                     5               YES*



    Since up to SEQ 5 only, archives were present at the start, I got db up to seq 5, but RMAN showed following error:*.

    RMAN > recover database until the sequence 5.

    From pick up to 22 May 11
    using channel ORA_DISK_1
    using the ORA_DISK_2 channel
    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03002: failure of the command recover at 22/05/2011 22:36:21
    RMAN-06556: datafile 1 must be restored from a backup that is older than SNA 979836

    Then I cleaned new system and gave 6 SEQ next time during recovery as it is the highest seq, but since archivelog to seq 6 is not present or redo logs are present (as far as my backup rman understanding isn't back ups redo logs and I had deleted previous recovery of host newspapers before starting the recovery and restoration) , then how is the recovery completed successfully? +


    Here are the steps of restoration and recovery with o/p for your reference:

    target [oracle@purnima 112_db] $ rman.

    Recovery Manager: release 11.2.0.1.0 - Production Wednesday, may 25, 22:19:49 2011

    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.

    connected to the database target (not started)

    1 RMAN > startup nomount;

    Oracle instance started

    Total System Global Area 619360256 bytes

    Bytes of size 1338280 fixed
    427820120 variable size bytes
    184549376 of database buffers bytes
    Redo buffers 5652480 bytes

    2 RMAN > restore controlfile to ' / home/oracle/rman_backup/ora_cfc-4124714611-20110510-00';

    From restoration to 25 May 11
    using the control file of the target instead of recovery catalog database
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID = 19 type of device = DISK

    channel ORA_DISK_1: restore the control file
    channel ORA_DISK_1: restore complete, duration: 00:00:04
    output file name=/home/oracle/112_db/oradata/honey/control01.ctl
    output file name=/home/oracle/112_db/flash_recovery_area/honey/control02.ctl
    Finished restoring to May 25, 11

    3 RMAN > change the editing of the database;

    mounted database
    output channel: ORA_DISK_1

    RMAN > show all.

    Database with db_unique_name HONEY RMAN configuration parameters are:
    CONFIGURE REDUNDANCY 2 RETENTION STRATEGY;
    CONFIGURE BACKUP OPTIMIZATION
    SET UP DEFAULT DISK DEVICE TYPE; # by default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT for DEVICE TYPE DISK TO ' / home/oracle/rman_backup/ora_cf%F';
    SET UP THE DEVICE TYPE DISK PARALLELISM 2 TYPE OF BACKUP BACKUPSET.
    CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
    CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ' / home/oracle/rman_backup/ora_df%t_b%s_p%p';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
    CONFIGURE ENCRYPTION OF DATABASE # by default
    CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
    CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD; # by default
    CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / home/oracle/112_db/product/11.2.0/dbhome/dbs/snapcf_honey.f'; # by default

    4 RMAN > restore database;

    From restoration to 25 May 11
    From implicit overlapping backup 25 May 11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID = 20 type of device = DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: SID = 21 type of device = DISK
    Intersected 4 objects
    Cut 3 objects
    Finished the backup implicit intersection to 25 May 11

    Starting copy of implicit intersection to 25 May 11
    using channel ORA_DISK_1
    using the ORA_DISK_2 channel
    Copy of implicit overlap finished on 25 May 11

    the search for all files in the recovery area
    cataloging files...
    not cataloged files

    using channel ORA_DISK_1
    using the ORA_DISK_2 channel

    channel ORA_DISK_1: from the restore backup set data file
    channel ORA_DISK_1: specifying datafile (s) to restore from backup set
    channel ORA_DISK_1: restore datafile 00002 to /home/oracle/112_db/oradata/honey/sysaux01.dbf
    channel ORA_DISK_1: restore datafile 00003 to /home/oracle/112_db/oradata/honey/undotbs01.dbf
    channel ORA_DISK_1: restore datafile 00005 to /home/oracle/112_db/oradata/honey/example01.dbf
    channel ORA_DISK_1: reading of the backup/home/oracle/rman_backup/ora_df750773827_b15_p1 element
    channel ORA_DISK_2: from the restore backup set data file
    channel ORA_DISK_2: specifying datafile (s) to restore from backup set
    channel ORA_DISK_2: restore datafile 00001 to /home/oracle/112_db/oradata/honey/system01.dbf
    channel ORA_DISK_2: restore datafile 00004 in /home/oracle/112_db/oradata/honey/users01.dbf
    channel ORA_DISK_2: reading of the backup/home/oracle/rman_backup/ora_df750773827_b14_p1 element
    channel ORA_DISK_1: piece handle = / home/oracle/rman_backup/ora_df750773827_b15_p1 tag = TAG20110510T121707
    channel ORA_DISK_1: restored the backup part 1
    channel ORA_DISK_1: restore complete, duration: 00:01:17
    channel ORA_DISK_2: piece handle = / home/oracle/rman_backup/ora_df750773827_b14_p1 tag = TAG20110510T121707
    channel ORA_DISK_2: restored the backup part 1
    channel ORA_DISK_2: restoration complete, duration: 00:01:18
    Finished restoring to May 25, 11

    5 RMAN > backup from the list of the archivelog all;


    List of backup sets
    ===================


    Time of accomplishment time BS key size Device Type
    ------- ---------- ----------- ------------ ---------------
    16,29 6 M DISK 00:00:01 MAY 10, 11
    BP key: 6 location: AVAILABLE Tablet: NO Tag: TAG20110510T121703
    Item name: / home/oracle/rman_backup/ora_df750773823_b13_p1

    List of newspapers archived on backup the value 6
    The next time that THRD Seq YVERT low low time next YVERT
    ---- ------- ---------- --------- ---------- ---------
    1 4 962626 10 MAY 11 979836 10 MAY 11

    Time of accomplishment time BS key size Device Type
    ------- ---------- ----------- ------------ ---------------
    22.50 9 K DISK 00:00:00 10 MAY 11
    BP key: 9 situation: AVAILABLE Tablet: NO Tag: TAG20110510T121834
    Item name: / home/oracle/rman_backup/ora_df750773914_b16_p1

    List of newspapers archived on backup value 9
    The next time that THRD Seq YVERT low low time next YVERT
    ---- ------- ---------- --------- ---------- ---------
    1 5 979836 10 MAY 11 979898 10 MAY 11

    6 RMAN > recover database until sequence 6.

    Starting recover at 25 May 11
    using channel ORA_DISK_1
    using the ORA_DISK_2 channel

    starting media recovery

    channel ORA_DISK_1: starting archived log restore to default destination
    channel ORA_DISK_1: restoring archives Journal
    Archives journal thread = 1 = 5 sequence
    channel ORA_DISK_1: reading of the backup/home/oracle/rman_backup/ora_df750773914_b16_p1 element
    channel ORA_DISK_1: piece handle = / home/oracle/rman_backup/ora_df750773914_b16_p1 tag = TAG20110510T121834
    channel ORA_DISK_1: restored the backup part 1
    channel ORA_DISK_1: restore complete, duration: 00:00:01
    Archive log file name=/home/oracle/112_db/flash_recovery_area/HONEY/archivelog/2011_05_25/o1_mf_1_5_6xtfgqc6_.arc thread = 1 = 5 sequence
    default channel: archived deletion or newspapers
    RECID = STAMP 16 = 752106671 name=/home/oracle/112_db/flash_recovery_area/HONEY/archivelog/2011_05_25/o1_mf_1_5_6xtfgqc6_.arc archived log file
    media recovery complete, duration: 00:00:01
    Finished recover at 25 May 11

    7 RMAN > alter database open resetlogs;

    open database

    8 RMAN > exit


    Kind regards
    Purnima Johari

    I have no onlinelogs on the host. I deleted all the log files from the flash and oradata recovery area before you begin the process of restoration and recovery on the host (.dbf, .log, .ctl). When I tried with "database recovery command", he gave following error (it's just the excerpt from o/p):

    Ah - yes: If you remove the onlinelogs then you receive the above error because a newspaper archive does not yet exist and the onlinelog with sequence 6 is missing too.

    >

    So you mean if we use up to clause with database recovery command, it always runs recovery up to n - 1. So imagine a scenario where all newspapers of recovery have been archived, if highest till SEQ that checked is generated is N, then to until I give SEQ N + 1 as up to execute it 'N' no time. Right?

    It's just too. It goes same for the RCS. If you want to recover to the last SNA in a specific archivelog, you can query the column NEXT_CHANGE # of v$ archived_log , then you will run 'restore database until the SNA... "and give the RCS of NEXT_CHANGE #-because it will recover to NEXT_CHANGE #-1.

    See you soon
    Jörg

  • RMAN & Configuration of RMAN script

    Dear all,

    This is the first time I'm with RMAN. I just wanted to run the RMAN script depending on the configuration of RMAN in order to test, for what is, I need to do before running this script below:
    RMAN > run {}
    stop immediately;
    bootable media;
    backup database;
    ALTER database open;
    }
    This is my current configuration of RMAN
    RMAN > show all.
    Database with db_unique_name DP RMAN configuration parameters are:
    CONFIGURE REDUNDANCY 1 RETENTION STRATEGY; # by default
    CONFIGURE BACKUP OPTIMIZATION # by default
    SET UP DEFAULT DISK DEVICE TYPE; # by default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
    SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
    CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
    CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
    CONFIGURE THE FORMAT OF DISC TYPE CHANNEL DEVICE "E:\RMAN\";
    CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
    CONFIGURE ENCRYPTION OF DATABASE # by default
    CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
    CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD; # by default
    CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' E:\APP\10004\PRODUCT\11.2.0\DBHOME_1\DATABASE\SNCFDP. ORA'; by default #
    kindly advice me and give me a very clear study for this above settings

    Concerning
    HAMEED


    Once I execute this script I got this following error message:

    + RMAN > run {+
    + 2 > shutdown immediate; +
    + 3 > mountain boot; +
    + 4 > backup database; +
    + 5 > alter database open; +
    {+ 6 >}; +

    database closed
    dismounted database
    Instance Oracle to close

    connected to the database target (not started)
    Oracle instance started
    mounted database

    Total System Global Area 770019328 bytes

    Bytes of size 1374780 fixed
    301991364 variable size bytes
    461373440 of database buffers bytes
    Redo buffers 5279744 bytes

    From backup may 18, 11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID = 134 type device = DISK
    channel ORA_DISK_1: starting full datafile from backup set
    channel ORA_DISK_1: specifying datafile (s) in the backup set
    Enter a file name 00006 = E:\APP\10004\ORADATA\DP\HAMEED01 = datafile number. DBF
    Enter a file name 00007 = E:\APP\10004\ORADATA\DP\ABDUL01 = datafile number. DBF
    Enter a number of file datafile = 00008 name = E:\APP\10004\ORADATA\DP\TEST01. DBF
    Enter a number of file datafile = 00001 name = E:\APP\10004\ORADATA\DP\SYSTEM01. DBF
    Enter a file name 00002 = E:\APP\10004\ORADATA\DP\SYSAUX01 = datafile number. DBF
    Enter a file 00005 name = E:\APP\10004\ORADATA\DP\EXAMPLE01 = datafile number. DBF
    Enter a number of file datafile = 00003 name = E:\APP\10004\ORADATA\DP\UNDOTBS01. DBF
    Enter a number of file datafile = 00004 name = E:\APP\10004\ORADATA\DP\USERS01. DBF
    channel ORA_DISK_1: starting piece 1 to 18 May 11
    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03009: failure of the backup command on the channel ORA_DISK_1 to 2011-05-18 17:22:30
    ORA-19504: cannot create the file 'E:\RMAN\ '.
    ORA-27038: created file already exists
    OSD-04010: < create > option specified, the file already exists

    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-00558: error occurred during parsing of order entry

    Published by: hamza on May 18, 2011 04:59

    CONFIGURE THE FORMAT OF DISC TYPE CHANNEL DEVICE "E:\RMAN\";

    Let's not setting up your chain. You must therefore run as

    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'E:\RMAN\full_%U.bk';
    

    Then try again.

  • Catalog RMAN and dataguard wout?

    Hello

    We have used RMAN backups and recently put in place a dataguard environment in 10g r2 (physical standby). All through the upgrade to 11g that I came across instructions say you must use a recovery catalog in an environment of dataguard. Backups are running on the primary just using the control file and everything seems to work. I fact a 'Validate restore database' and he succeeded. The recovery catalog is necessary if I chose to do the backups on the eve-, or is a catalog that is required in my scenario?

    Thank you

    Mark

    Published by: user6061469 on April 20, 2011 11:43

    It is an improvement. But not an obligation so you don't need where a plan to save the two sites and use a common catalogue.

    Hemant K Collette

  • How to remove a configuration of rman line!

    Dear friends,

    RMAN has a default configuration settings, i.e.:
    RMAN > show all.

    RMAN configuration parameters are:
    CONFIGURE REDUNDANCY 1 RETENTION STRATEGY; # by default
    CONFIGURE BACKUP OPTIMIZATION # by default
    SET UP DEFAULT DISK DEVICE TYPE;
    CONFIGURE CONTROLFILE AUTOBACKUP # by default
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO "%F" # by default
    SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
    SET UP THE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
    CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
    CONFIGURE BACKUP COPIES OF DATA FILE FOR DEVICE TYPE SBT_TAPE TO 1; # by default
    CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
    CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE SBT_TAPE TO 1; # by default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
    CONFIGURE ENCRYPTION OF DATABASE # by default
    CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
    CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / orafs/app/oracle/10.2.0/db_1/dbs/snapcf_ababil.f'; # default
    end of test, I must add the below two lines:

    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ' / dev/rmt1/ababil_%s_%t';
    CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' FORMAT ' / dev/rmt1/ababil_%s_%t';


    And now the configuration of shows like below:
    RMAN > show all.

    RMAN configuration parameters are:
    CONFIGURE REDUNDANCY 1 RETENTION STRATEGY; # by default
    CONFIGURE BACKUP OPTIMIZATION # by default
    SET UP DEFAULT DISK DEVICE TYPE;
    CONFIGURE CONTROLFILE AUTOBACKUP # by default
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO "%F" # by default
    SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
    SET UP THE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
    CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
    CONFIGURE BACKUP COPIES OF DATA FILE FOR DEVICE TYPE SBT_TAPE TO 1; # by default
    CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
    CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE SBT_TAPE TO 1; # by default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
    CONFIGURE ENCRYPTION OF DATABASE # by default
    CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
    CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / orafs/app/oracle/10.2.0/db_1/dbs/snapcf_ababil.f'; # default
    now would someone please tell me, on top of the RMAN configuration, how do I remove the lines below:

    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ' / dev/rmt1/ababil_%s_%t';
    CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' FORMAT ' / dev/rmt1/ababil_%s_%t';


    Waiting for kind response...

    NO, you can clear the settings only. You can't delete lines.

    Concerning
    Asif Kabir

  • Configuration of RMAN and REDUNDANCY

    Hello
    in 10g R2,.
    with the configuration of RMAN follwing:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 8;
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
    CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
    CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    How many backup files (before when, date on which) RMAN will remove physically from the disk?

    Thank you.

    'CONFIGURE RETENTION POLICY to REDUNDANCY 8;' means, RMAN will keep 8 independent backups of any window of time. Use 'CONFIGURE RETENTION POLICY to RECOVERY WINDOW of N days;', if you want to have a time-based retention policy.

    Werner

  • I installed the captain and my mac has been freezing on step "Configure your mac" for 24 hours. How do I please you?

    I installed the captain and my mac has been freezing on step "Configure your mac" for 24 hours. How do I please you? It is just to show the "set up your mac" and the turning circle Rainbow

    Reset the SMC. Choose the method for "on Mac Laptops with non-removable battery.

    https://support.Apple.com/en-us/HT201295

Maybe you are looking for