RMAN backup consistency

Hi
Does RMAN backup ensure the consistency of the database sequences when doing a hot backup? My concern is that my database uses a lot of sequence as identifier and during hot backup, the sequence will not be in sync as people are still accessing to the database. Does RMAN ensure consistency during the backup? Thanks!

You don't need to worry about sequences not being in sync with the backup. The backup will be consistent as at an SCN (as seen in the backup) and point in time so the backup will contain what the sequences look like as at that point in time. What occurs after then in the database would be contained in the archive logs for recovery.
When you may get inconsistencies with sequences is when you have a CACHE set on the sequence. When a sequence is selected the sequence value is in the shared pool but say you have an outage causing the shared pool to be wiped (from memory) and therefore lose the held value. Therefore you may get values in a table where it appears a sequence was skipped.

Similar Messages

  • How to make hot RMAN backup as consistent in 10g?

    Hi,
    While cloning database using rman hot backup it asking archivelog files. how to recover easily? How to make hot RMAN backup as consistent in 10g?
    Thanks,

    user2017273 wrote:
    Hi,
    While cloning database using rman hot backup it asking archivelog files. how to recover easily? How to make hot RMAN backup as consistent in 10g?
    Thanks,Take backup with "plus archivelog" command. This will require archived redo log files and automatically apply them

  • 10.1.0.2.0 RMAN backup- What would cause RMAN to hang?

    Oracle gurus- Fellow in trouble, need your guidance.
    I have a serious issue that has no direct error to examine or fix.
    I have a replicated offline server that has a scripted RMAN backup to run nightly, but the backup times flux from what should be only 1 hour 30 minutes. Every other day it takes up to 10 hours to complete a backup that normally takes 1 hr 30 minutes. There is no difference in data loads- the server is offline and the data has not changed to any effect. I use database control instead of grid control, and I turn off emctl every night before the rman backup- I thought maybe emctl was hogging resources. There is nothing else running on the server except replication inserting a couple of rows of data on three tables every other minute.
    Where would I look to see where the problem exists when no errors are generated?
    Does RMAN wait to backup files if they are being accessed?
    Here is my backup script (the OS is Linux AS3) I run an AT job nightly.
    at -f /path/path/rman_backup 0600 tomorrow
    rman target/
    run {
    backup database plus archivelog;
    delete noprompt obsolete;
    sql 'alter system archive log current';
    exit;
    The Administrators are running a Legato Jukebox backup? a tape backup that backs up my DB files nightly. They run the Legato backup 3 hours after my RMAN backup- the problem is that my RMAN backup may be running during the Legato backup- so I assume that contention occurs and both backups fight for the DB files. This is not an issue when RMAN plays nice and finishes in the normal 1 hour 30 minutes, but when it exceeds 3 hours- we have serious issues, both RMAN and Legato backups take 10 hours.
    Please help, I am really puzzled. This is causing me major headaches, how can I assure that RMAN has a consistent backup time to completion. Is there anyway to script it to use more resources to ensure it finishes quickly?

    Have you monitored CPU and I/O during this process? Are there any other processes running during this time? You mentioned the server is offline, but you also mentioned replication is taking place ?
    You could query V$BACKUP_ASYNC_IO and look at EFFECTIVE_BYTES_PER_SECOND, WAITS and IO_COUNT.
    During the backup, you can run the following query to monitor RMAN:
    SELECT sid, serial#, context, sofar, totalwork,
         round(sofar/totalwork*100,2) "% Complete"
         FROM v$session_longops
         WHERE opname LIKE 'RMAN%'
         AND opname NOT LIKE '%aggregate%'
         AND totalwork != 0
         AND sofar <> totalwork;If the % Complete doesn't seem to be increasing, you should run the following select to determine what waits exist:
    SELECT sid, seconds_in_wait AS sec_wait, event FROM v$session_wait
         WHERE wait_time = 0
         ORDER BY sid;

  • Oracle 9i RMAN backup filling up all disk and failing at the very end

    Hello to all and thank you in advance for any input from any of you.
    I am new in oracle and the only one in my company with a little bit of oracle knowledge, which is not a whole lot.
    I inherited a few servers (Linux and Windows based). We mostly run all our production environment on a Linux box hosting oracle 10g release 10.2.0.1 but we had a legacy application server that still runs on 9i release 9.2.0.1.0. This server is a windows 2003 box, the previous DBA or someone else with admin rights to this machine compressed the whole drive where oracle resides, when I started summarying the oracle assets, I saw this server with no backups scheduled and a compressed disk with very limited space after this compression, only 13 GB left, the database if uncompressed would definitively filled up all the disk. The machine is in used and cannot be taken down for more than a couple of hours. We tried adding another disk but the machine only accept it as a hot spare. The database is in archive mode, when I tried to run a RMAN backup, it start filling up the database drive until it's empty and it crashes the whole machine, it seems like the buffer is growing and growing until it fills up the whole drive. The only way to get the server up and running again is to reboot the machine since the server is more than 6 years old we are not please with this action because we are afraid the machine would go south in one of those reboots.
    Has anyone heard of similar issues when running RMAN on a compressed drive? Can the compressed disk have any involvement in this kind of odd behaviour? I tried running the backup in debug mode and creating a log in a different disk (the one where the backup is going to) and still the same issue. Again any help is much appreciate,
    Sincerely,
    Alex

    Sybrand,
    Thank you for your fast response, I am going to use your previous post to answer one by one your question,
    1 The Oracle binaries --- on a compressed drive > Yes
    2 The Oracle database control files redo log files and datafiles on that same compressed drive? > Yes
    3 The archived redo log ditto? > Yes
    I know for a fact (as I have been using that in 9i) you can create a RMAN backup on a compressed drive, and you can have your archived redo go to a compressed drive. No problemo! > Excellent good news!!!
    But I would never touch the data files. Please note backup sets are multiplexed files consisting of multiple datafiles, so RMAN would need to do some calculations to decompress several blocks at the same time and to calculate a new block and compress it.
    Do you have enough space to:
    a) (preferred) to make datafile copies instead of a backup >
    Not in the drive that hosts the oracle instance but yes on an external usb drive (1TB) I attached to use as a backup repository, maybe this is why I am having these issues. I only have 13 GB left on that drive where the oracle instance resides (actually as I explained in a previous reply to Mark, the server only has 3 slots for disks, two of them as configured as RAID 1 and the other is a hot spare because the RAID configuration manager cannot can only added as hot-spare. The raided disk are partitioned in two, one small partition is for the OS and the other is for the oracle instance). When you said make a copy of the datafiles, I assumed you are talking about doing manual backups, and copying the database after using using "alter tablespace tablespace_name begin backup; then copy the file; alter tablespace tablespace_name end backup;
    b) use filesperset=1 on the backup command line, so the multiplexing (and associated calculations) stop. I have not tried the option of fileperset yet but I can tryi it and see if that helps.
    Can you post the last few lines of the RMAN log where RMAN bombs out? Note: the last few lines. Not all of it, or you must send some paracetamol in conjunction! >
    When I ran the debug option, I stopped the backup at less than 20% because I didn't want to reboot the system in the middle of the production time, the backup consumed at least 3 GB during the time was running. The times I ran the RMAN backup I didn't used the debug option so I don't have a log long enough to send unless you want the last few lines of what I have.
    Thanks again for your input,
    Sincerely,
    Alex

  • RMAN / backup.  oracle 9 vs. oracle 10

    My colleague mentioned a while ago that we had to investigate RMAN &/or a backup client, "because in oracle 10, when doing an export of a live db, oracle does not switch into "single user mode" like it did in 9. So we couldn't have 100% faith in our .dmp file."
    I'd like to do some further research on this, but looking through the "Oracle 10 Complete reference" and googling - I don't see any information about it. Has anyone here dealt with this or know of a link I should see?
    Finally... Does anyone know if an RMAN backup for Oracle 10 accounts for any "in progres" transactions?
    Thanks in advance,
    Mike.

    Oracle, itself, doesn't switch to single user mode.
    Your colleague might have been talking of scripts which shutdown and restart the
    database in restricted mode to run an export of the database.
    RMAN backups as in 8.0/8i/9i/10g (or EBU in Oracle 7) and scripted (aka
    "user managed") backups are all physical backups. They take database blocks
    "as they are". Conceptually, the datafile backups aren't aware of active transactions.
    It is the redo stream in the archivelogs that is required for you to be able to restore
    and recreate a consistent database image.

  • Rman backup with  standby database

    Hi All,
    I am looking for some suggestions for rman backup with standby  database with datagaurd but no active DG. I wanted to do a rman tablespace backup. but I am stuck at  sql 'alter system archive log current' in rman  with standby as target. which gives following errors  with or without noswitch clause
    RMAN> sql 'alter system archive log current noswitch';
    sql statement: alter system archive log current noswitch
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of sql command on default channel at 10/05/2013 18:15:12
    RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current noswitch
    ORA-01109: database not open
    Recovery Manager: Release 11.2.0.1.0
    Oracle databaes  Release 11.2.0.1.0 64 bit
    OS:RHEL 6 x86-64 bit
    Secondly, do I need to cancel manged recovery while taking rman backups on standby.
    I scanned thru MOS but could find solutions for rman with active DG.
    Thanks in advance

    726d07e6-b870-431f-8c22-a499c3ec4e0c wrote:
    Hi All,
    I am looking for some suggestions for rman backup with standby  database with datagaurd but no active DG. I wanted to do a rman tablespace backup. but I am stuck at  sql 'alter system archive log current' in rman  with standby as target. which gives following errors  with or without noswitch clause
    RMAN> sql 'alter system archive log current noswitch';
    sql statement: alter system archive log current noswitch
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of sql command on default channel at 10/05/2013 18:15:12
    RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current noswitch
    ORA-01109: database not open
    Recovery Manager: Release 11.2.0.1.0
    Oracle databaes  Release 11.2.0.1.0 64 bit
    OS:RHEL 6 x86-64 bit
    Secondly, do I need to cancel manged recovery while taking rman backups on standby.
    I scanned thru MOS but could find solutions for rman with active DG.
    Thanks in advance
    "I scanned thru MOS but could find solutions for rman with active DG."
    Howto make a consistent RMAN backup in an Standby database in Active DataGuard mode (Doc ID 1419923.1)

  • RMAN Backup Failed.

    Hi Gurus,
    My RMAN backup failed with below error.Please suggest.
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of sql command on default channel at 01/26/2013 22:48:56
    RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current
    ORA-00258: manual archiving in NOARCHIVELOG mode must identify log
    RMAN>
    Recovery Manager complete.
    Thanks,

    The message indicates that your database is in NOARCHIVELOG mode. You cannot make an RMAN Backup of a database that is OPEN if it is in NOARCHIVELOG mode.
    You have two options
    1. Make consistent RMAN Backups with the database only in MOUNT mode (SHUTDOWN ; STARTUP MOUNT)
    OR
    2. Configure for ArchiveLogs (create a target filesystem or FRA), set the database to ARCHIVELOG mode, monitor the volume of ArchiveLog generation, configure both Database and ArchiveLog backups.
    Hemant K Chitale

  • Best practice for RAC RMAN backup

    I have a 10gR2 RAC db that is 3.5TB. It is a 2 node cluster on AIX. Each instance is db1 on node1, and db2 on node2, the "world" database name is db.
    Currently we are doing our backup from 1 node of the cluster, specifying that it connect to to db2, so this instance is doing all of the backup work. We allocate 14 channels to back this database up to tape (yes, we have plenty of tape resources, connecting to a tape machine with > 20 physical tape drives). Would it be better to have our rman script connect to the general database db and let the listener decide which instance to send the channel allocation to, or keep all the work on one node.

    I seem to remember that when I was reading up on RAC and RMAN a couple of years ago (maybe up to 4 years ago) that there was something about always doing backups from the same node in a RAC configuration i.e. you have logically 'db' in your network configuration and also direct names of 'db1' and 'db2', and you should always use one of 'db1' or 'db2' but never 'db'. And I also mean do not alternate between 'db1' and 'db2'. Pick one of them and always do your backups from that instance.
    I think this was to do with things like the database identifier, and the instance identifier too, which RMAN reads and puts into the backup. It also affects things like reading the archive logs, which must be cross mounted to both nodes. I have this feeling that using the same node kept a kind of consistency within the backups, and meant that Oracle was getting all of the block images from one node i.e. from one of the SGAs. If you used both nodes simultaneously you could run into issues with their SGAs being out of sync. I know this does not make much sense, given that RAC is all about keeping the SGAs consistent with each other. But at the end of the day I do remember something about always using one node all the time to do your RMAN backups.
    Not sure if these rules hold true if you are using ASM, which itself is shared in a RAC environment.
    Things may have moved on since then, but that was still 10g Release 2 documentation, so I would guess it is still true. At the end of the day, it is not the backup that is important, but the recovery. You don't want to create any kind of inconsistent backup that RMAN cannot successfully recover, even though the backup may look good when you create it.
    I'd check out the RMAN and RAC documentation further to see if this is supported.
    John

  • E-business Suite RMAN backup retention

    Hi,
    i want to retain my backup for clone for 90 days. One parameter need to set at RMAN level is CONFIGURE RETENTION POLICY TO REDUNDANCY 90;
    What other parameter need to set at DB level?
    Thanks

    i want to retain my backup for clone for 90 days. One parameter need to set at RMAN level is CONFIGURE RETENTION POLICY TO REDUNDANCY 90;
    What other parameter need to set at DB level?Rman backup retention policy [ID 462978.1]
    Oracle10g / 11g - Getting Started with Recovery Manager (RMAN) [ID 360416.1]
    RMAN : Consistent Backup, Restore and Recovery using RMAN [ID 162855.1]
    Backup and Recovery
    http://www.oracle.com/pls/db112/portal.portal_db?selected=4&frame=#backup_and_recovery
    Thanks,
    Hussein

  • Delete RMAN backup

    Oracle 11.2.0.1
    Windows
    I takes RMAN backup at D:\RMAN_BAKCUP of our test database. Now there is space problem, I have to allocate some space to other folder. I shall take cold backup of database by shutdown. How do I start to delete RMAN backup from above location. It is incremental backup. What precautions should be there while deleting RMAN backup with archive logs.
    Can I delete all archive logs too after consistent backup by shutting down the database ?
    I am facing space problem, thats why I though that I shall take cold backup of db and now no need of rman backup as well as archive logs. Am I correct ?
    Thanks.

    user12050217 wrote:
    Oracle 11.2.0.1
    Windows
    I takes RMAN backup at D:\RMAN_BAKCUP of our test database. Now there is space problem, I have to allocate some space to other folder. I shall take cold backup of database by shutdown. How do I start to delete RMAN backup from above location. It is incremental backup. What precautions should be there while deleting RMAN backup with archive logs.
    Can I delete all archive logs too after consistent backup by shutting down the database ?
    I am facing space problem, thats why I though that I shall take cold backup of db and now no need of rman backup as well as archive logs. Am I correct ?
    Thanks.Given what else I've read in this thread (test database, no need for point in time recovery, etc.) A 'cold' backup may be appropriate, but I'd still use rman to do it. I have a similar situation right now with one of my test databases. I took an rman cold backup (database is open MOUNT) with KEEP UNTIL 'SYSDATE + 60'. Once, sometimes twice, a day the developer asks for a restore to the backup. Piece of cake with rman, especially with a little script all ready to go. Would be a bit more difficult with a 'user managed' backup.

  • RMAN Backup keep forever

    Hi all,
    I want to keep Rman backup for forever.
    But i dnt want to retian archive log .
    Kindly suggest.
    Regards

    RMAN> BACKUP TAG Q107 DATABASE KEEP FOREVER;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01009: syntax error: found ";": expecting one of: "consistent, logs, nologs"
    RMAN-01007: at line 1 column 38 file: standard input

  • RMAN Backup Restore from tape

    Hello Gurus
    We have lvl0 RMAN database backup restored from tape but due to some reasons we could not apply recovery on it. On checking the information in controlfile, it identified only the system file and no other file. So, we recreated the controlfile and decided to recover using backup controlfile option (until cancel or until change or until time). However, to my surprise, when I listed the checkpointchange# and checkpoint_time columns of v$datafile_header, I found the difference in timestamps ranging 24 hrs -- which menat we had to apply 24 hrs of archiving to bring all dbfs to a consistent state (before it allowed us to open the db) -- so far so good, it worked that way.
    My question is that, while I trigger a lvl0 RMAN backup at say 4PM on 27th July and it finishes on 4PM on 28th July (as I am directly pushing around 1 TB data to tapes) -- what is the consistency timestamp of this backup. In other words, is this backup available for a restore of 4PM 27th July? Or is it available only for a restore of 4PM 28th July and later ...?
    Isn't it that RMAN works at block level and when I fire a backup it should give me all the dbf's of that timestamp..?
    Appreciate your inputs/comments.

    When taking a online backup with RMAN, the datafiles backup is always inconsistent because it needs the archived redo logs generated during the backup to be consistent: http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/intro005.htm#sthref70.
    A full online backup can only be used to restore the database to a point in time starting after backup end: if a backup starts at 4PM on 27th July and it finishes on 4PM on 28th July you can use it to restore the database to a point in time after 28-JUL 4PM.

  • RAC RMAN BACKUP Recovery FOR  Oracle APPS Application

    Hi,
    We have an Application which is similar to Oracle APPs application and We have a RAC Database at Backend.
    As I am a Oracle RAC DBA and never worked as an Oracle apps DBA.
    Each Week or month We have to deploy a patch on Our Database which are kind of sql changes to Database and before we applying we need to backup our Database.
    I am very comfortable while applying patches on Single instance Database:-
    I Usually shutdown my database and backing up My Database(Conistent\cold Backup) before applying patch.
    and I have a Flash back on both option I am having for my Database.
    Problem:-
    But in Production I have RAC Database, on which I already configured Hot Backup.
    FlashBackup Feature is there with me, but Not reliable.
    I want cold backup along with my existing hot backup, and want to restore same if something goes wrong.
    Since ASM is configured so we have only option RMAN backup.
    IF possible kindly Share your knowledge and Experience of your to handle Such Problem.

    Sir,
    RMAN is already configured for backing up database online.
    My only intention is to have cold or consistent backup before applying application patch, So that at the time of crisis I will resotre my Cold/Conistent backup.
    Because I am using 11gr2 RAC with ASM, so only option is there for me to use rman as backup tool.
    But I never tried to Have Cold backup in RAC environment in my previous jobs, and I am new to this Oracle APPS DBA technology. So Here I am looking for a Strategy that Normally oracle apps dba use while applying patch to Oracle Database and kind of backup strategy they use.
    Regards
    Gaurav

  • Rman backup with a missing archivelog.

    hello,
    I backed my database up yesterday after you guys helped me fix few problems I had on it. I used RMAN with the following command in a run block:
    *run {*
    allocate channel t1 type disk;
    backup current controlfile ;
    backup database;
    backup archivelog all delete input;
    release channel c1;
    At the end of the operation, RMAN indicates that and archivelog is missing and it couldn't find it. As a result, recover operation can be compromised. Now am confused because I do not know whether the command executed successfully or not and how to fix the missing archivelog.
    Below is the entire output of the operation along with error message:
    canal affectÚ : t1
    canal t1 : sid=131 typedev=DISK
    DÚmarrage de backup dans 16/04/09
    canal t1 : dÚmarrage de l'ensemble de sauvegarde de tous les fichiers de donnÚes
    canal t1 : insertion du fichier de donnÚes dans l'ensemble de sauvegarde
    insertion du fichier de contr¶le en cours dans l'ensemble de sauvegarde
    canal t1 : dÚmarrage de l'ÚlÚment 1 dans 16/04/09
    canal t1 : ÚlÚment 1 terminÚ dans 16/04/09
    pointeur=+ASMTEST/meta4/backupset/2009_04_16/ncnnf0_tag20090416t211049_0.334.684
    *364257 Útiquette=TAG20090416T211049 commentaire=NONE*
    canal t1 : ensemble de sauvegarde terminÚ, temps ÚcoulÚ : 00:00:14
    Fin de backup dans 16/04/09
    DÚmarrage de backup dans 16/04/09
    canal t1 : dÚmarrage de l'ensemble de sauvegarde de tous les fichiers de donnÚes
    canal t1 : insertion du fichier de donnÚes dans l'ensemble de sauvegarde
    fichier de donnÚes en entrÚe fno=00008 nom=+ASMTEST/meta4/m4prod.dbf
    fichier de donnÚes en entrÚe fno=00010 nom=H:\ORADATA\M4REC.DBF
    fichier de donnÚes en entrÚe fno=00009 nom=E:\DATAFILEMETA4\M4PROD02.DBF
    fichier de donnÚes en entrÚe fno=00001 nom=+ASMTEST/meta4/system01.dbf
    fichier de donnÚes en entrÚe fno=00003 nom=+ASMTEST/meta4/sysaux01.dbf
    fichier de donnÚes en entrÚe fno=00006 nom=C:\TEST.DBF
    fichier de donnÚes en entrÚe fno=00007 nom=+ASMTEST/meta4/meta4.dbf
    fichier de donnÚes en entrÚe fno=00005 nom=+ASMTEST/meta4/example01.dbf
    fichier de donnÚes en entrÚe fno=00002 nom=+ASMTEST/meta4/undotbs01.dbf
    fichier de donnÚes en entrÚe fno=00004 nom=+ASMTEST/meta4/users01.dbf
    canal t1 : dÚmarrage de l'ÚlÚment 1 dans 16/04/09
    canal t1 : ÚlÚment 1 terminÚ dans 16/04/09
    pointeur=+ASMTEST/meta4/backupset/2009_04_16/nnndf0_tag20090416t211107_0.333.684
    *364271 Útiquette=TAG20090416T211107 commentaire=NONE*
    canal t1 : ensemble de sauvegarde terminÚ, temps ÚcoulÚ : 00:51:10
    canal t1 : dÚmarrage de l'ensemble de sauvegarde de tous les fichiers de donnÚes
    canal t1 : insertion du fichier de donnÚes dans l'ensemble de sauvegarde
    insertion du fichier de contr¶le en cours dans l'ensemble de sauvegarde
    inclusion du SPFILE en cours dans l'ensemble de sauvegarde
    canal t1 : dÚmarrage de l'ÚlÚment 1 dans 16/04/09
    canal t1 : ÚlÚment 1 terminÚ dans 16/04/09
    pointeur=+ASMTEST/meta4/backupset/2009_04_16/ncsnf0_tag20090416t211107_0.345.684
    *367351 Útiquette=TAG20090416T211107 commentaire=NONE*
    canal t1 : ensemble de sauvegarde terminÚ, temps ÚcoulÚ : 00:00:26
    Fin de backup dans 16/04/09
    DÚmarrage de backup dans 16/04/09
    journal en cours archivÚ
    canal libÚrÚ : t1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: Úchec de la commande backup Ó 04/16/2009 22:04:03
    RMAN-06059: journal d'archivage attendu introuvable ; la perte du journal d'arch
    ivage compromet la possibilitÚ de rÚcupÚration
    ORA-19625: erreur lors de l'identification du fichier H:\ARCHIVEMETA4\ARC00001_0
    *682674928.001*
    ORA-27041: ouverture du fichier impossible
    OSD-04002: ouverture impossible du fichier
    O/S-Error: (OS 2) Le fichier spÚcifiÚ est introuvable.
    Here's my nderstanding and please correct me if am wrong:
    The first 3 instructions of the run block executed successfully, but
    the last one didn't. Is that so?
    Whatever the understanding, do I have a backup? WHat can I do to have a consistent backup?
    Thanks in advance.

    Adomi,
    It is sad to see you are still running RMAN in 8i fashion where you are on 10g.
    The script is bs, sorry
    run {
    allocate channel t1 type disk; -- not required
    backup current controlfile ; -- not required, as this is already done by backup database
    backup database;
    backup archivelog all delete input;
    release channel c1; -- not required.
    If you have controlfile autobackup on, you could just
    backup database plus archivelog
    and be done with it.
    As you didn't make a RMAN backup from the start, your backup archivelog statement should have read
    backup archivelog all skip inaccessible delete input;
    Once that succeeds Oracle shouldn't need the archivelog anymore, and you should make a second backup without the skip inaccessible clause.
    Sybrand Bakker
    Senior Oracle DBA

  • How can i do a RMAN backup of my database from the network ?

    i'm using oracle 8i.1.7.3 with win server 2003
    i want to know how can i do a RMAN backup of my database (sever machine A) from the network.
    i'd like to save the backup in another machine (the same LAN, the same OS ).
    to do that i've mapped a logical device in my comptur (z):
    when i run rman command i got this error:
    channel ORA_DISK_1: starting piece 1 at .......
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command ON ORA_DISK_1 channel at .......
    00
    ORA-19504: failed TO CREATE file "\\remote\save\"
    ORA-27040: skgfrcre: create error, unable to create file
    OSD-04002: unable to open file
    O/S-Error: (OS 123) The filename, directory name, or volume label syntax is inco
    rrect.

    Hi,
    ORA-19504: failed TO CREATE file "\\remote\save\"make sure you have created this directory and change it's ownership (chown command)to oracle.
    also make sure that oracle user has permission to write to this direcotry (chmod command)
    hope this helps
    cheers, walrus

Maybe you are looking for