EBS database backup

Hi all

EBS R12.2

11 GR 2

Rhel6.5

We have set up a physical standby for our EBS R12.2 db.

To save the resources of the PRIMARY, we do RMAN backup on the standby only and not in primary SCHOOL. Is this a good practice?

Thank you very much

JC

Jenna_C wrote:

Thanks hussein,.

Yes we should do if we apply patches.

My question is, given that the RMAN backup will take place only in the STANDBY mode, and this RMAN also supports the removal of the obsolete.

How can I empty the archivelogs generated in the PRIMARY? Do I need to use the script to do this?

Kind regards

How will I know when it is safe to purge an Oracle archive log? (Doc ID 966843.1)

Configure RMAN to purge the archivelogs after application pending (Doc ID 728053.1)

Thank you

Hussein

Tags: Oracle Applications

Similar Questions

  • Help blackBerry Smartphones! Database backup error

    I can't back up my BB, I get the error code "Unable to save databases".  I've identified the problem as the "browser cache" database backup of databases individually in the advanced options.

    I deleted my browser cache and clean up the memory, but whenever I try to save my camera it gets so far and stops with the error message "cannot save data bases.

    Help please.

    Got a better solution that I found myself!

    If you CAN identify the problem database, and then follow the instructions in the first step of this link.  When you get to the part 4 of this, you must select the problem database and click clear.

    http://www.BlackBerry.com/BTSC/microsites/search.do?cmd=displayKC&docType=kc&externalId=KB10167&SLIC...

    Hey Presto!

    This way you don't have to wipe your entire device!

  • Can not find the trace file after "alter database backup controlfile to trace;" on the RDBMS 11.2.0.3

    Hello

    I use a database on RDBMS 11.2.0.3. Connected as sys and run

    SQL > alter database backup controlfile to trace;

    Database altered.

    view the USER_DUMP_DEST parameter.

    VALUE OF TYPE NAME

    ------------------------------------ ----------- ------------------------------

    user_dump_dest string D:\app\oracle\diag\rdbms\pears

    dev\pearsdev\trace

    Looking at the track record, there is no trace file? What am I missing?

    Thank you

    Mathias

    Confirm with:

    SQL > dir D:\APP\ORACLE\CONTROLFILE the host. TXT

  • EBS database statistics

    Hi Xperts

    I'm new to EBS and I have a doubt: what is the right way to keep statistics on the database of my EBS environment?.

    I found that many tables have updated statistics on my EBS environment and also a reading I got can´t take the statistics with DBMS_STATS

    I read a white paper from Oracle:

    New white paper: best practices for the collection of statistics of EBS database

    https://blogs.Oracle.com/stevenChan/entry/new_white_paper_guidelines_for

    In this white paper, I read that I have to use: FND_STATS , I just want to be sure with your advice

    Thank you for your help

    Concerning

    Hi J, a,

    Just use request competing to collect statistics of schema. Although it uses internally the fnd_stats, but its simple and standard way to gather statistics for all schemas.

    You can find a simple and nice explanation here: http://www.appsdba.info/docs/oracle_apps/performance/GatherSchemaStatistics.pdf

    Thank you

    Shakti

  • cannot run script change controlfile database backup

    Hai all,

    can u help me about this error,

    I can't run alter database backup controlfile script:

    SQL > alter database backup controlfile to trace;

    ALTER database backup controlfile to trace

    *

    ERROR on line 1:

    ORA-01187: cannot read the file 514 because she has no verification tests

    ORA-01110: data file 514: ' / u01/TESTDEV/testdevdata/tmp1.dbf'

    SQL >

    Thank you

    Hello

    If the above statement is blocked, try acting below.

    SQL> alter tablespace temp drop tempfile '/u01/TESTDEV/testdevdata/tmp1.dbf';

    Please make sure that you have created a tempfile more before performing this command as tablespace temp needs at a minimum a file.

    Otherwise, you can try as suggested by BalazsBerki.

    Thank you!!

  • Database backups fail

    Hello Experts,

    Database backups fail due to compatibility issues, is the target database version 10.2.0.1, so RMAN version is running on 10.2.0.4.0, I have no idea how it happened and who did it before, now I have to take this issue... could you please give me suggestions on how to make RMANback 10.2.0.1 version.

    Make sure that you run the rman binary the same $ORACLE_HOME/bin as the database.

    If you run rman from a remote server, make a new 10.2.0.1 ORACLE_HOME install and run this House of Oracle rman.

    Hemant K Collette

  • How to take database backup ASM/Instance?

    Hello

    I'm new with ASM. We take ASM/instance of database backup.

    can we have the idea to backup ASM?

    1. what components should be saved as database/Instance ASM / ASM all files?


    Please do the needful.

    Thank you
    Nitin

    Hello Nitin,

    First of all, you must understand that the RDBMS & ASM instance is different but yes, both are running on the same computer.

    ASM includes essentially two things: ASM instance (1) and the storage of the DSO (2).

    (1) ASM instance
    ------------------------

    That's just an instance when we do not backup but Yes if you want to keep the ASM instance configuration file then just follow these steps:

    [grid@host01 ~] $. oraenv
    ORACLE_SID = [+ ASM1]? + ASM1
    The basic Oracle for ORACLE_HOME=/u01/app/11.2.0/grid is/u01/app/grid

    SQL > create pfile='/home/grid/init+ASM1.ora' of spfile;

    Created file.

    (2) ASM STORAGE
    -------------------------

    -Storage ASM includes essentially ASM starts, namely new set of disks.

    -Whenever we do not create ASM diskgroup diskgroup contains still three things:

    (a) disc ASM
    (b) models and metadata
    (c) the ASM files (essentially datafile or all database files)

    -We take backup of two things on three things in ASM diskgroup:

    (1) ASM files - with RMAN because these are files of database.
    (2) ASM diskgroup models & metadata - with the MD_BACKUP of ASMCMD command.

    Now, MD_BACKUP will create a backup as your specified location file and this file will includes all models and metadata of the diskgroup. Benefits of taking diskgroup metadata are, if we lost the diskgroup, so we do not worry some details configuration command MD_RESTORE use to recreate the diskgroup with the same configuration. But remember that it does not restore the data file or any other file that was there on the diskgroup going to use RMAN to restore the missing files.

    See the example:

    ASMCMD > lsdg

    State Type sector Rebal to Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files name of the block
    EXTERN MOUNTED N 512 4096 1048576 11742 11643 0 11643 0 N ABC /.
    NORMAL CLIMB N 512 4096 1048576 15656 10661 1259 4701 0 N DATA.
    EXTERN MOUNTED N 512 4096 1048576 15656 13874 0 13874 0 N FRA.
    ASMCMD >
    >

    ASMCMD >/home/grid/data_backup_file - G DATA md_backup
    Group of disk to save metadata: DATA
    Path to current directory alias: cluster01
    Path to current directory alias: ORCL
    Path to current directory alias: ORCL/fichier_parametres
    Path to current directory alias: ORCL/DATA file
    Current directory alias path: cluster01/OCRFILE
    Path to current directory alias: ORCL/CONTROLFILE
    Path to current directory alias: ORCL/TEMPFILE
    Path to current directory alias: ORCL/ONLINELOG
    Current directory alias path: cluster01/ASMPARAMETERFILE
    ASMCMD >

    * vim # / home/grid/data_backup_file *.

    @diskgroup_set =)
    {
    "ATTRINFO"-ONLINE {}
    "MODEL. OCRBACKUP. REDUNDANCY '-ONLINE 18',
    "MODEL. FICHIER_PARAMETRES. MIRROR_REGION '-ONLINE '0',
    "MODEL. TEMPORARY FILE. REDUNDANCY '-ONLINE 18',
    "MODEL. TEMPORARY FILE. MIRROR_REGION '-ONLINE '0',
    "MODEL. FICHIER_PARAMETRES. REDUNDANCY '-ONLINE 18',
    "SECTOR_SIZE"-ONLINE '512',
    "MODEL. DATAGUARDCONFIG. REDUNDANCY '-ONLINE 18',
    ' ACCESS_CONTROL. UMASK '-ONLINE '066'.
    "MODEL. ASM_STALE. STRIPE '-ONLINE '0',
    "MODEL. ARCHIVELOG. STRIPE '-ONLINE '0',
    "MODEL. DATAGUARDCONFIG. PRIMARY_REGION '-ONLINE '0',
    "MODEL. OCRBACKUP. STRIPE '-ONLINE '0',
    "MODEL. DATA FILE. STRIPE '-ONLINE '0',
    "AU_SIZE"-ONLINE '1048576',
    "MODEL. ASMPARAMETERFILE. STRIPE '-ONLINE '0',
    "MODEL. TRACK CHANGES. PRIMARY_REGION '-ONLINE '0',
    "MODEL. CONTROLFILE. REDUNDANCY '-ONLINE 19',
    "MODEL. FLASHFILE. STRIPE '-ONLINE '0',
    "MODEL. BACKUPSET. PRIMARY_REGION '-ONLINE '0',
    "MODEL. ARCHIVELOG. PRIMARY_REGION '-ONLINE '0',
    "MODEL. TRACK CHANGES. STRIPE '-ONLINE '0',
    "MODEL. ONLINELOG. PRIMARY_REGION '-ONLINE '0',
    "MODEL. TRACK CHANGES. REDUNDANCY '-ONLINE 18',
    "MODEL. BACKUPSET. STRIPE '-ONLINE '0',
    "MODEL. OCRFILE. MIRROR_REGION '-ONLINE '0',
    "DISK_REPAIR_TIME' => '3.6 h."
    "MODEL. AUTOBACKUP. REDUNDANCY '-ONLINE 18',
    "MODEL. DUMPSET. REDUNDANCY '-ONLINE 18',
    "MODEL. RETURN OF FLAME. MIRROR_REGION '-ONLINE '0',
    "MODEL. DUMPSET. MIRROR_REGION '-ONLINE '0',
    "MODEL. DUMPSET. PRIMARY_REGION '-ONLINE '0',
    "MODEL. ASM_STALE. REDUNDANCY '-ONLINE 19',
    "MODEL. RETURN OF FLAME. PRIMARY_REGION '-ONLINE '0',
    "MODEL. CONTROLFILE. STRIPE '-ONLINE 1',
    "MODEL. DATA FILE. REDUNDANCY '-ONLINE 18',
    "MODEL. XTRANSPORT. REDUNDANCY '-ONLINE 18',
    "MODEL. AUTOBACKUP. PRIMARY_REGION '-ONLINE '0',
    "MODEL. CONTROLFILE. MIRROR_REGION '-ONLINE '0',
    "MODEL. DATA FILE. PRIMARY_REGION '-ONLINE '0',
    "MODEL. ASMPARAMETERFILE. REDUNDANCY '-ONLINE 18',
    "MODEL. FLASHFILE. MIRROR_REGION '-ONLINE '0',
    "MODEL. ASM_STALE. MIRROR_REGION '-ONLINE '0',
    "MODEL. RETURN OF FLAME. REDUNDANCY '-ONLINE 18',
    "MODEL. DATAGUARDCONFIG. STRIPE '-ONLINE '0',
    "CELL. SMART_SCAN_CAPABLE'-ONLINE 'FALSE. '
    "TEMPLATE_VERSION"-ONLINE '186646528',
    "MODEL. FICHIER_PARAMETRES. STRIPE '-ONLINE '0',
    "MODEL. DATA FILE. MIRROR_REGION '-ONLINE '0',
    "MODEL. FICHIER_PARAMETRES. PRIMARY_REGION '-ONLINE '0',
    "MODEL. BACKUPSET. MIRROR_REGION '-ONLINE '0',
    "MODEL. OCRBACKUP. MIRROR_REGION '-ONLINE '0',
    "MODEL. ONLINELOG. REDUNDANCY '-ONLINE 18',
    "MODEL. ASMPARAMETERBAKFILE. STRIPE '-ONLINE '0',
    ' ACCESS_CONTROL. PERMIT TO '-ONLINE 'FALSE. '
    "MODEL. DATAGUARDCONFIG. MIRROR_REGION '-ONLINE '0',
    "MODEL. TEMPORARY FILE. PRIMARY_REGION '-ONLINE '0',
    "COMPATIBLE. RDBMS '-ONLINE '10.1.0.0.0'.
    "MODEL. FLASHFILE. PRIMARY_REGION '-ONLINE '0',
    "MODEL. ONLINELOG. MIRROR_REGION '-ONLINE '0',
    "MODEL. FLASHFILE. REDUNDANCY '-ONLINE 18',
    "MODEL. OCRBACKUP. PRIMARY_REGION '-ONLINE '0',
    "MODEL. OCRFILE. STRIPE '-ONLINE '0',
    "MODEL. AUTOBACKUP. MIRROR_REGION '-ONLINE '0',
    "MODEL. ASM_STALE. PRIMARY_REGION '-ONLINE '0',
    "MODEL. ASMPARAMETERBAKFILE. PRIMARY_REGION '-ONLINE '0',
    "MODEL. XTRANSPORT. PRIMARY_REGION '-ONLINE '0',
    "MODEL. DUMPSET. STRIPE '-ONLINE '0',
    "MODEL. TEMPORARY FILE. STRIPE '-ONLINE '0',
    "MODEL. OCRFILE. PRIMARY_REGION '-ONLINE '0',
    "MODEL. ONLINELOG. STRIPE '-ONLINE '0',
    "MODEL. ARCHIVELOG. REDUNDANCY '-ONLINE 18',
    "MODEL. OCRFILE. REDUNDANCY '-ONLINE 18',
    "MODEL. ARCHIVELOG. MIRROR_REGION '-ONLINE '0',
    "MODEL. ASMPARAMETERFILE. MIRROR_REGION '-ONLINE '0',
    "MODEL. RETURN OF FLAME. STRIPE '-ONLINE '0',
    "MODEL. CONTROLFILE. PRIMARY_REGION '-ONLINE '0',
    "MODEL. XTRANSPORT. MIRROR_REGION '-ONLINE '0',
    "MODEL. BACKUPSET. REDUNDANCY '-ONLINE 18',
    "MODEL. ASMPARAMETERBAKFILE. REDUNDANCY '-ONLINE 18',
    "MODEL. XTRANSPORT. STRIPE '-ONLINE '0',
    "MODEL. TRACK CHANGES. MIRROR_REGION '-ONLINE '0',
    "COMPATIBLE. ASM '-ONLINE '11.2.0.0.0'.
    "MODEL. ASMPARAMETERBAKFILE. MIRROR_REGION '-ONLINE '0',
    "MODEL. ASMPARAMETERFILE. PRIMARY_REGION '-ONLINE '0',
    "MODEL. AUTOBACKUP. STRIPE'-'0' ONLINE
    },
    "DISKSINFO"-ONLINE {}
    "ASMDISK02"-ONLINE {}
    "ASMDISK02"-ONLINE {}
    "TOTAL_MB"-ONLINE '3914',
    "FAILGROUP" => "ASMDISK02."
    "NAME" => "ASMDISK02."
    "DGNAME"-ONLINE "DATA."
    'PATH' => 'ORCL:ASMDISK02 '.
    }
    },
    "ASMDISK01"-ONLINE {}
    "ASMDISK01"-ONLINE {}
    "TOTAL_MB"-ONLINE '3914',
    "FAILGROUP" => "ASMDISK01."
    "NAME" => "ASMDISK01."
    "DGNAME"-ONLINE "DATA."
    'PATH' => 'ORCL:ASMDISK01 '.
    }
    },
    "ASMDISK04"-ONLINE {}
    "ASMDISK04"-ONLINE {}
    "TOTAL_MB"-ONLINE '3914',
    "FAILGROUP" => "ASMDISK04."
    "NAME" => "ASMDISK04."
    "DGNAME"-ONLINE "DATA."
    'PATH' => 'ORCL:ASMDISK04 '.
    }
    },
    "ASMDISK03"-ONLINE {}
    "ASMDISK03"-ONLINE {}
    "TOTAL_MB"-ONLINE '3914',
    "FAILGROUP" => "ASMDISK03."
    "NAME" => "ASMDISK03."
    "DGNAME"-ONLINE "DATA."
    'PATH' => 'ORCL:ASMDISK03 '.
    }
    }
    },
    "DGINFO"-ONLINE {}
    "DGTORESTORE"-ONLINE 0
    "DGCOMPAT"-ONLINE ' 11.2.0.0.0. "
    "DGNAME"-ONLINE "DATA."
    "DGDBCOMPAT"-ONLINE ' 10.1.0.0.0. "
    "DGTYPE"-ONLINE "NORMAL."
    "DGAUSZ"-ONLINE '1048576'
    },
    "ALIASINFO"-ONLINE {}
    '6' => {
    "DGNAME"-ONLINE "DATA."
    'LEVEL'-ONLINE 1
    "ALIASNAME"-online "cluster01/ASMPARAMETERFILE"
    'REFERENCE_INDEX'-'16777322' ONLINE
    },
    '3' => {
    "DGNAME"-ONLINE "DATA."
    'LEVEL'-ONLINE 1
    "ALIASNAME" => "ORCL/CONTROLFILE.
    'REFERENCE_INDEX'-'16777534' ONLINE
    },
    '7' => {
    "DGNAME"-ONLINE "DATA."
    'LEVEL'-ONLINE 1
    "ALIASNAME" => "ORCL/FICHIER_PARAMETRES,"
    'REFERENCE_INDEX'-'16777693' ONLINE
    },
    '2' => {
    "DGNAME"-ONLINE "DATA."
    'LEVEL'-ONLINE 1
    "ALIASNAME" => "ORCL/ONLINELOG,"
    'REFERENCE_INDEX'-'16777587' ONLINE
    },
    '8' => {
    "DGNAME"-ONLINE "DATA."
    'LEVEL'-ONLINE 1
    "ALIASNAME"-online "cluster01/OCRFILE"
    'REFERENCE_INDEX'-'16777375' ONLINE
    },
    '1' => {
    "DGNAME"-ONLINE "DATA."
    'LEVEL'-ONLINE 0
    "ALIASNAME"-online "cluster01."
    'REFERENCE_INDEX'-'16777269' ONLINE
    },
    '4' => {
    "DGNAME"-ONLINE "DATA."
    'LEVEL'-ONLINE 1
    "ALIASNAME" => ORCL/DATA FILE"."
    'REFERENCE_INDEX'-'16777481' ONLINE
    },
    '0' => {
    "DGNAME"-ONLINE "DATA."
    'LEVEL'-ONLINE 0
    "ALIASNAME" => "ORCL".
    'REFERENCE_INDEX'-'16777428' ONLINE
    },
    '5' => {
    "DGNAME"-ONLINE "DATA."
    'LEVEL'-ONLINE 1
    "ALIASNAME" => "ORCL/TEMPFILE"
    'REFERENCE_INDEX'-'16777640' ONLINE
    }
    },
    'TEMPLATEINFO'-ONLINE {}
    '11' => {}
    "DGNAME"-ONLINE "DATA."
    "STRIPE"-ONLINE 'ROUGH. "
    'TEMPNAME' => 'AUTOBACKUP.
    "REDUNDANCY"-ONLINE "MIRROR."
    'SYSTEM' => 'Y '.
    },
    '7' => {
    "DGNAME"-ONLINE "DATA."
    "STRIPE"-ONLINE 'ROUGH. "
    "TEMPNAME' => 'ASMPARAMETERFILE."
    "REDUNDANCY"-ONLINE "MIRROR."
    'SYSTEM' => 'Y '.
    },
    '2' => {
    "DGNAME"-ONLINE "DATA."
    "STRIPE"-ONLINE 'ROUGH. "
    "TEMPNAME' => 'ARCHIVELOG."
    "REDUNDANCY"-ONLINE "MIRROR."
    'SYSTEM' => 'Y '.
    },
    '17' => {}
    "DGNAME"-ONLINE "DATA."
    "STRIPE"-ONLINE 'ROUGH. "
    "TEMPNAME' => 'OCRBACKUP."
    "REDUNDANCY"-ONLINE "MIRROR."
    'SYSTEM' => 'Y '.
    },
    '1' => {
    "DGNAME"-ONLINE "DATA."
    "STRIPE"-ONLINE 'ROUGH. "
    "TEMPNAME' => 'ASM_STALE."
    "REDUNDANCY"-ONLINE "HIGH."
    'SYSTEM' => 'Y '.
    },
    '18' => {}
    "DGNAME"-ONLINE "DATA."
    "STRIPE"-ONLINE 'ROUGH. "
    "TEMPNAME' => 'ONLINELOG."
    "REDUNDANCY"-ONLINE "MIRROR."
    'SYSTEM' => 'Y '.
    },
    '0' => {
    "DGNAME"-ONLINE "DATA."
    "STRIPE"-ONLINE 'ROUGH. "
    'TEMPNAME' => 'DATAFILE ',.
    "REDUNDANCY"-ONLINE "MIRROR."
    'SYSTEM' => 'Y '.
    },
    '16' => {}
    "DGNAME"-ONLINE "DATA."
    "STRIPE"-ONLINE 'ROUGH. "
    "TEMPNAME' => 'OCRFILE."
    "REDUNDANCY"-ONLINE "MIRROR."
    'SYSTEM' => 'Y '.
    },
    '13' => {}
    "DGNAME"-ONLINE "DATA."
    "STRIPE"-ONLINE 'ROUGH. "
    "TEMPNAME'-ONLINE"TRACK CHANGES. "
    "REDUNDANCY"-ONLINE "MIRROR."
    'SYSTEM' => 'Y '.
    },
    '6' => {
    "DGNAME"-ONLINE "DATA."
    "STRIPE"-ONLINE 'ROUGH. "
    "TEMPNAME' => 'ASMPARAMETERBAKFILE."
    "REDUNDANCY"-ONLINE "MIRROR."
    'SYSTEM' => 'Y '.
    },
    '3' => {
    "DGNAME"-ONLINE "DATA."
    "STRIPE"-ONLINE 'ROUGH. "
    "TEMPNAME' => 'FLASHFILE."
    "REDUNDANCY"-ONLINE "MIRROR."
    'SYSTEM' => 'Y '.
    },
    '9' => {
    "DGNAME"-ONLINE "DATA."
    "STRIPE"-ONLINE 'ROUGH. "
    "TEMPNAME" => "TEMPFILE"
    "REDUNDANCY"-ONLINE "MIRROR."
    'SYSTEM' => 'Y '.
    },
    '12' => {}
    "DGNAME"-ONLINE "DATA."
    "STRIPE"-ONLINE 'ROUGH. "
    "TEMPNAME' => 'XTRANSPORT."
    "REDUNDANCY"-ONLINE "MIRROR."
    'SYSTEM' => 'Y '.
    },
    '14' => {}
    "DGNAME"-ONLINE "DATA."
    "STRIPE"-ONLINE 'ROUGH. "
    "TEMPNAME'-ONLINE"FLASHBACK. "
    "REDUNDANCY"-ONLINE "MIRROR."
    'SYSTEM' => 'Y '.
    },
    '15' => {}
    "DGNAME"-ONLINE "DATA."
    "STRIPE"-ONLINE 'ROUGH. "
    "TEMPNAME' => 'DATAGUARDCONFIG."
    "REDUNDANCY"-ONLINE "MIRROR."
    'SYSTEM' => 'Y '.
    },
    '8' => {
    "DGNAME"-ONLINE "DATA."
    "STRIPE"-ONLINE 'ROUGH. "
    "TEMPNAME' => 'FICHIER_PARAMETRES."
    "REDUNDANCY"-ONLINE "MIRROR."
    'SYSTEM' => 'Y '.
    },
    '4' => {
    "DGNAME"-ONLINE "DATA."
    "STRIPE"-ONLINE "FINE."
    'TEMPNAME' => 'CONTROLFILE.
    "REDUNDANCY"-ONLINE "HIGH."
    'SYSTEM' => 'Y '.
    },
    '10' => {}
    "DGNAME"-ONLINE "DATA."
    "STRIPE"-ONLINE 'ROUGH. "
    "TEMPNAME' => 'BACKUPSET."
    "REDUNDANCY"-ONLINE "MIRROR."
    'SYSTEM' => 'Y '.
    },
    '5' => {
    "DGNAME"-ONLINE "DATA."
    "STRIPE"-ONLINE 'ROUGH. "
    "TEMPNAME' => 'DUMPSET."
    "REDUNDANCY"-ONLINE "MIRROR."
    'SYSTEM' => 'Y '.
    }
    }
    }
    );

    NOTE:

    To re-create the diskgroup dropped with the same restoration of the configuration of the diskgroup even with the aid of diskgroup as:

    asmcmd >/home/grid/data_backup_file - full - G DATA md_restore

    Hope its clear now.

    Thank you

    Ashish Shukla

  • Oracle database backup basics

    May I ask, from a point of view, low tech a little question on the backup/restore of Oracle databases. Are there tools commonly used for backup of Oracle database? And have you ever encounter the snowman DBA / other places you have worked to make bad backups? I'd like to hear horror stories about what can and will hurt in oracle database backups? It is a simple process, or wrong - this easy ens at the end and things / featuring data etc.?
    And the second part of the question is if you're looking for auditing oracle backup processes, that you are looking 'good evidence' that this is done in line with the policy /strategy?

    >

    Are there specific reasons why backups become unnecessary, i.e. what goes wrong, when it comes to restoration, it is not restore.

    There may be two reasons. One, for example, backups are accidentally deleted, partially or completely. Another way may be the backup is marked as obsolete due to the retention or some operations strategy as resetlogs who could not leave the backups in use.

    I was also wondering how easy it is perhaps "missing data" when planning a backup DB with RMAN? Is this possible? Have you ever seen do, and if so is there any 'specific' part of a database that is often overlooked during examination of what to plan for in the backup task?

    What do you mean by "missing data"? It would be possible if you don't take care of backups that you plan.

    Aman...

  • Database backup RMAN with Veritas NetBackup catalog

    Hello

    How can I use Veritas NetBackup to backup my database of catalog RMAN? I need to stop this catalog DB in order to save it. How can I plan with NetBackup?

    Thanks in advance.

    qtpham

    Hello

    Normally, the catalog database backup is currently off cause is very small database and may remain unavailable for a few minutes. In my company, we use netbackup.
    Try to schedule an offline backup of the database via the Netbackup graphical interface, it will generate RMAN scripts bpstart_notify. YOUR_POLICY_NAME and bpend_notify. YOUR_POLICY_NAME under/usr/openv/netbackup/bin/if you use SOLARIS.

    Kind regards

    Rodrigo Mufalani
    http://mufalani.blogspot.com

  • Smartphones blackBerry unable to backup (Options memory cleaner): database backup error

    Hi all!

    I need help.  I'm trying to make a backup of my "BOLD", but when the procedure happens to Options cleaner memory, the process stops and I get the error "Error backup database".

    All the ideas from the pros?

    Thank you!
    Dan

    Hi and welcome to the forums!

    Cleaner memory in my opinion is misnamed and abusively.

    The cleaner memory formats a Government on the memory wipe. He won't

    improve or move memory back and more quickly to the BB. Therefore, I completely

    stopped using it and it was not in my last update.

    Try to turn the option off, battery pull, then run a backup.

    IF it doesn't go away, I'll be back with right clear procedure of database.

    Thank you

    Bifocals

    No data will be lost when you do the following: remove the battery while the device is activated.
    Remplacer replace after one minute, let the device reboot 1-3 min, see if the problem is corrected.

  • Oracle 12 c with RMAN database backup

    Hi All-

    I started back to the top of one of my PDB using utility RMAN following the instructions on the link below.

    http://www.Oracle.com/WebFolder/technetwork/tutorials/OBE/DB/12C/R1/PDB/pdb_pitr/pdb_pitr.html

    --Connect to Oracle RMAN.
rman> Connect target /
--Set the Oracle RMAN backup device type and backup file location.
rman> configure channel device type disk format '/stage/db_backup_files/cdb1/%U';
--Turn on automatic backup of control files.
rman> configure controlfile autobackup on;
--Back up the database and archive logs.
rman>backup database plus archivelog;
rman> exit

    Back to the top has been done successfully, but when I started with the recovery process he gave me error reporting collection.

    Run {set until what SNA = 2263440; restore database connectable to pdb2; retrieve auxiliary destination of the pluggable database pdb2 = "/ stage/db_backup_files/cdb1 '; alter connectable database to pdb2 ;} open resetlogs}

    This is the track to RMAN

    Recovery Manager: release 12.1.0.2.0 - Production on sat 22 Aug 12:22:44 2015

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

    RMAN > Connect target /.

    connected to target database: RELIABLE (DBID = 1028507357)

    RMAN > run {}

    2 > ALTER DATABASE connectable to MultiPlay NARROW;

    3 > set up what SNA = 14899894;

    4 > restore database pluggable MultiPlay;

    5 > restore database pluggable MultiPlay;

    6 > alter database connectable to MultiPlay open resetlogs;

    {7 >}

    using the control file of the target instead of recovery catalog database

    Statement processed

    executing command: SET until clause

    From restoration to 22 August 15

    allocated channel: ORA_DISK_1

    channel ORA_DISK_1: SID = 22 type of device = DISK

    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 00035 to E:\APP\ORADATA\RELIABLE\MULTIPLAY\SYSTEM01. DBF

    channel ORA_DISK_1: restore datafile 00036 to E:\APP\ORADATA\RELIABLE\MULTIPLAY\SYSAUX01. DBF

    channel ORA_DISK_1: restore datafile 00037 to E:\APP\ORADATA\RELIABLE\MULTIPLAY\MULTIPLAY_USERS01. DBF

    channel ORA_DISK_1: backup E:\APP\RECOVERY_AREA\RELIABLE\40A433F530464F3BBF2E7C0B1553ECE8\BACKUPSET\2015_08_22\O1_MF_NNNDF_TAG20150 piece reading

    822T115328_BXJ5C182_. BKP

    channel ORA_DISK_1: piece handle = E:\APP\RECOVERY_AREA\RELIABLE\40A433F530464F3BBF2E7C0B1553ECE8\BACKUPSET\2015_08_22\O1_MF_NNNDF_TAG20150822T115328_BX

    J5C182_. Tag BKP = TAG20150822T115328

    channel ORA_DISK_1: restored the backup part 1

    channel ORA_DISK_1: restore complete, duration: 00:01:05

    Restoration finished in 22 August 15

    From pick up to August 22, 15

    using channel ORA_DISK_1

    RMAN-05026: WARNING: following tablespaces set applies to the Point in time specified assuming

    List of tablespaces should have UNDO segments

    SYSTEM tablespace

    Tablespace UNDOTBS1

    Creation of automatic instance with SID = "zbnt."

    RMAN-00571: ===========================================================

    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

    RMAN-00571: ===========================================================

    RMAN-03002: failure of the command recover at 22/08/2015 12:24:56

    ORA-19852: error creating services for the instance auxiliary zbnt (error 0)

    ORA-27302: failure occurred:

    ORA-27303: additional information: could not start the instance

    Thank you

    Siradji

    Just a wild guess

    You do not use this script in a command as Administrator window

    Therefore, you won't be able to create any service.

    I also have a question: your only troubleshooting activity consisted of hitting CTRL + C and CTRL-V, is not it?

    It's so boring to most of the people here do not even TRY to solve their own problems.

    -------------

    Sybrand Bakker

    Senior Oracle DBA

  • RMAN takes longer than usual to the database backup cars.

    Hi all

    I have a database of CARS 2 nodes (11.2.0.3) using ASM on OUL5x64 (DB1/DB2) the backup script was running on DB2 for the past 3 years without problem.

    backup with compress is 80 GB Sunday.

    level Inc 1 day = 20 to 30 GB)

    I just added 2 other nodes to this CAR, now there DB1, DB2, DB3, DB4

    moved the backup to DB4 script and set up all of the environments for this work.

    The first 2 days, it did increase normal level 1 backup around time (20-30 GB) between (1 h 30 min)

    but on Thursday which is always increase of LEVEL 1, it took 8 hours to do the job.  and when checking the size

    the backup, the size was 255 GB level 1 (s/n 20/30 GB) and today it did the same.

    Please give suggestions as why backup is so huge.

    Thank you.

    Here's the script.

    RMAN target / < < EOF

    echo setting

    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT for DEVICE TYPE DISK TO ' / u02/%F';

    Run {}

    allocate channels d1 type disk maxpiecesize 5 g;

    allocate channels d2 type disk maxpiecesize 5 g;

    Compressed backupset backup

    format ' / d01/pr1/pr1_%s_%t_%p.dbf'

    extra strength 1 cumulative

    Skip inaccessible

    tag hot_db_bk_level1

    filesperset 4

    (data include current controlfile);

    # sql 'alter system archive log current';

    #Backup all archive logs

    Compressed backupset backup

    format ' / d01/pr1/pr0_%s_%t_%p.arc'

    Ark of the tag

    filesperset 4

    (archivelog all delete all entries).

    }

    Hi all

    After you resolve the problem, the support of Oracle pointed out that

    I hit the limit in this note:

    How many incremental backups can be taken when the OWA is enabled? ( Doc ID 452455.1 )

    the default value

    _bct_bitmaps_per_file = 8

    in my case, I ran more than 8 times in the week. sous-séquence then run don't use BTC (block_change_tracking)

    After running a backup full again, backup works like it suppose to.

    Thanks for the replies.

    Kind regards

  • Cloning of database backup items

    Dear administrators,

    I'm about to clone a production DB a DB test with the prod DB Backup items that are already copied to test DB destination.

    the backup items are stored in the DB in the location test - / apollo/exports/apptest/PROD

    Is the correct script duplicate DB below?

    Start DB pfile nomount mode changed with all necessary conversion settings and...

    Auxiliary RMAN / target sys/sysdb@PROD catalog rman11g/rman11g@catdb

    Catalogue start with "/ apollo/exports/apptest/PROD."

    Run {}

    allocate channels ch01 type disk maxpiecesize 7000 M;

    allocate channels ch02 type disk maxpiecesize 7000 M;

    duplicate target database to test;

    output channel ch01.

    output channel ch02;

    }

    You've done a STARTUP NOMOUNT.  Oracle does not have the DBID of the files that must be "appropriate" in the location of the catalog.  You still must SET DBID.

    Hemant K Collette

  • Need help with Oracle Database Backup &amp; Restore Cold

    Environment:

    Oracle Version: 11.2.0.4

    Platform: AIX

    A few weeks ago, I had updated my Oracle 10.2.0.1 to 11.2.0.4 database. The customer changed his mind and now I downgrade to 10.2.0.1. Unfortunately, the compatibility setting is set to 11.2.0.4. So I can't use the lower upgrade scripts.

    I had taken a cold backup of the database before the upgrade. Unfortunately, I missed save logs for recovery.

    Is there a way I can always downgrade / recovery 10.2.0.1 with cold back? or is it simply not possible without the backup of redo logs.

    Thanks in advance.

    rogers42

    I had taken a cold backup of the database before the upgrade. Unfortunately, I missed save logs for recovery.

    And what do YOU mean by "had taken a cold backup"?

    Because in addition to what John said, you also need the correct initialization file.

    Do you have a return of this init file which was taken at the same time as the backup?

    I had updated my Oracle 10.2.0.1 to 11.2.0.4 database.

    I suggest that you first reinstall the 10.2.0.1 version or Oracle before recovering your cold backup.

    You must use the EXACT name of the folder structure and file that have been used originally.

    See my response in this thread a few years ago:

    Re: Restore incompatible cold backup

    You will be able to simplify this process, some given that your backup is consistent, but the steps should help you to understand what to do.

    One of my answers in THIS thread has real details for each of the steps in the other thread

    https://community.oracle.com/message/10132328?

  • backup database - backup multiple sets of 1 piece 1 statement each

    Hi all!

    I have an ORACLE database 11 GR 1 material running on RHEL X86_64 5.7. The size of the database is approximately 800 GB.

    This is the current configuration of RMAN:

    CONFIGURE REDUNDANCY 2 RETENTION STRATEGY;

    CONFIGURE BACKUP OPTIMIZATION

    SET UP DEFAULT DISK DEVICE TYPE;

    CONFIGURE CONTROLFILE AUTOBACKUP ON;

    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT for DEVICE TYPE DISK TO ' / d02/rman_backups/%T_%F';

    SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP TO COMPRESSED BACKUPSET TYPE;

    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 ' / d02/rman_backups/%T_%U' MAXPIECESIZE 60 G;

    CONFIGURE MAXSETSIZE TO UNLIMITED; # by default

    CONFIGURE ENCRYPTION OF DATABASE # by default

    CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default

    CONFIGURE THE "ZLIB" COMPRESSION ALGORITHM

    CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default

    CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / d01/dev/db/tech_st/11.1.0/dbs/snapcf_DEV.f'; # by default

    It's my 'RUN' block to create a single full backup:

    RUN

    {

    SHUTDOWN IMMEDIATE;

    BOOTABLE MEDIA;

    BACKUP DATABASE;

    OBSOLETE REPORT;

    REMOVE OBSOLETE;

    ALTER DATABASE OPEN;

    }

    Backup of days RMAN created 1 backup set made up of 5 pieces: 4 pieces of 60GB and 1 piece of 42 GB as well as saving the file spfile and control... for me this is the expected behavior.

    But today, RMAN created 34 games backup of 1 piece of each... parts are no more than 7 GB.

    It is the output for control of BACKUP of LIST SUMMARY:

    Backup list

    ===============

    S LV TY Device Type delay #Pieces compressed #Copies Tag key

    ------- -- -- - ----------- --------------- ------- ------- ---------- ---

    39. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    40. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    41. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    42. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    43. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    44. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    45. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    46. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    47. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    48. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    49. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    50. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    51. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    52. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    53. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    54. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    55. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    56. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    57. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    58. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    59. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    60. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    61. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    62. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    63. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    64. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    65. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    66. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    67. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    68. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    69. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    70. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    71. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    72. A DISC APRIL 18, 14 1 1 YES TAG20140418T015553

    73. A DISC 18 APRIL 14 1 1 no TAG20140418T065039

    Please help me to reconfigure RMAN to create the backup set 1, composed by the "n" backup items.

    I appreciate your time and your help nicely.

    MAXSETSIZEsizeSpec Specifies a maximum size for a backup (as shown in example 2-17). RMAN limit all backup sets to this size.

    It is possible for a game span multiple tapes, sort of blocks from each data file is written to multiple backup tapes. If a tape of a multivolume backup set fails, then you lose the data on all bands, rather than a single one. Because a backup set always includes an entire file rather than the part of a file, you can use MAXSETSIZE to specify that each backup set should fit on a single tape.

    Specify the size in bytes (default), kilobytes ( K ), Mo ( M ), or gigabytes ( G ). For example, to limit a game to 3 MB of backup, specify MAXSETSIZE 3M . The default size is expressed in bytes, rounded to kilobytes. For example, MAXSETSIZE 3000 is rounded to 2 k (2048 bytes). The minimum value must be greater than or equal to the database block size.

    The number of files in each default backup set is determined by FILESPERSET , which by default is 64. When you specify MAXSETSIZE , RMAN attempts to limit the size in bytes of the backup sets according to the MAXSETSIZE parameter. The limit on the number of files in a backup set applies even if the total size of the backup set that results is lower to MAXSETSIZE .

    Note: This option will result in an error if used with BACKUP AS COPY . If you run BACKUP AS COPY on a channel that has MAXSETSIZE value, then MAXSETSIZE is ignored in silent mode.

Maybe you are looking for