ArchiveLog deletion using RMAN
Hi,
My backup failed for some time due to disk space issue which I was able to fix using setting db_recovery_file_dest_size but after the completion of backup script it didn't delete all the archivelog files. I still have log files from 05 Jan 2011 - 20 Feb 2011, but log files from 21 Feb 2011 - 18 Apr 2011 were deleted, When I run "crosscheck archivelog all;" it didn't show me archivelogs between 05 Jan 2011 - 20 Feb 2011 in the results but physically they are present in the archive folder.
1 How to delete these archive files to free up disk space?
2 Can I restore my database from last backup which was successful?
3 Why the RMAN was unable to delete my archivelog files?
My retention policy is set to Redundancy 1.
Thanks,
Prashanth
The older archivelogs are no longer in the control file if they are not being reported by CROSSCHECK.
Normally, when the FRA is close to 100% usage, Oracle can automatically purge known obsolete files. However, if you resized the FRA before the files were auto-purged and, subsequently, they became older than the keep time, Oracle became "unaware" of them.
You could re-CATALOG them with a CATALOG command and then DELETE them, with a DELETE command.
Hemant K Chitale
Similar Messages
-
RMAN show archivelog deletion policy;
RMAN> show archivelog deletion policy;
RMAN configuration parameters are:
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
What choices i have for its deletion policy? I want to carry only 30 days archivelogs , How i can chnage that?Hello,
These are the options.
When backups of archived redo log files are taken on the standby database:
1)Issue the following command on the primary database:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
2) Issue the following command on the standby database:
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
When backups of archived redo log files are taken on the primary database:
1) Issue the following command on the standby database:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
2) Issue the following command on the primary database:
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
Check this url for more info
https://dpt-info.u-strasbg.fr/doc/oracle/server.102/b14239/rman.htm
-Sri -
Using RMAN to delete unwanted archivelog files..??
Hi All,
How can i remove the unwanted archivelog files from the disk, to manage the disk space usage, using RMAN?
My 10g database is in ARCHIVELOG mode and the OS is RHEL ES Release 3
when i tried with 'delete expired archivelog all;', i got the result as follows:
RMAN> delete expired archivelog all;
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=363 devtype=DISK
specification does not match any archive log in the recovery catalog
Please update...
Many Thanks in advance.....!!!with the delete all input, can i assume that the archivelog files has been got deleted...Don't you trust Oracle ? :-)
You should see two series of messages, like below
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=73 recid=1 stamp=599697994
input archive log thread=1 sequence=74 recid=2 stamp=599698064
input archive log thread=1 sequence=75 recid=3 stamp=599698103
input archive log thread=1 sequence=76 recid=4 stamp=599698138
input archive log thread=1 sequence=116 recid=44 stamp=600271740
input archive log thread=1 sequence=117 recid=45 stamp=600271859
input archive log thread=1 sequence=118 recid=46 stamp=600277637
channel ORA_DISK_1: starting piece 1 at 04-SEP-06
channel ORA_DISK_1: finished piece 1 at 04-SEP-06
piece handle=/home/ora102/flash_recovery_area/DB102/backupset/2006_09_04/o1_mf_annnn_TAG20060904T154722_2hrcmh13_.bkp tag=TAG20060904T154722 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:37
channel ORA_DISK_1: deleting archive log(s)
archive log filename=/home/ora102/flash_recovery_area/DB102/archivelog/2006_08_28/o1_mf_1_73_2h6ok83j_.arc recid=1 stamp=599697994
archive log filename=/home/ora102/flash_recovery_area/DB102/archivelog/2006_08_28/o1_mf_1_74_2h6omjb9_.arc recid=2 stamp=599698064
archive log filename=/home/ora102/flash_recovery_area/DB102/archivelog/2006_08_28/o1_mf_1_75_2h6onq39_.arc recid=3 stamp=599698103
archive log filename=/home/ora102/flash_recovery_area/DB102/archivelog/2006_08_28/o1_mf_1_76_2h6oosvn_.arc recid=4 stamp=599698138
archive log filename=/home/ora102/flash_recovery_area/DB102/archivelog/2006_09_04/o1_mf_1_116_2hr5tw8c_.arc recid=44 stamp=600271740
archive log filename=/home/ora102/flash_recovery_area/DB102/archivelog/2006_09_04/o1_mf_1_117_2hr5ym80_.arc recid=45 stamp=600271859
archive log filename=/home/ora102/flash_recovery_area/DB102/archivelog/2006_09_04/o1_mf_1_118_2hrcm58z_.arc recid=46 stamp=600277637
Finished backup at 04-SEP-06 -
Deletion of archive log using RMAN Target in Oracle 10g
Hi All,
I recently have noticed that the archive logs have occupied 102 GBs out of the drive and I need to free up some space. When I tried to connect RMAN Catalog using
connect catalog user@dbI got error message as
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-06445: cannot connect to recovery catalog after NOCATALOG has been usedBut I was able to get through using
connect target user@dbMy Query is can I use
RMAN> delete noprompt expired archivelog all;as given in [how to delete archive log file |https://forums.oracle.com/forums/thread.jspa?threadID=2321257&start=0&tstart=0]
Or shall I take any other approach to delete the obsolete archive logs?
Regards,
*009*Hello;
I recently have noticed that the archive logs have occupied 102 GBs out of the drive and I need to free up some space. When I tried to connect RMAN Catalog using
connect catalog user@dbI got error message as
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-06445: cannot connect to recovery catalog after NOCATALOG has been usedBut I was able to get through using
connect target user@db
Are you trying to connect it through Grid control ? If connecting through a script, then please post its contents.
Make sure you are not connecting to the target database using "nocatalog".
rman target sys/<pwd_of_target>@<target_db> catalog <catalog_schema>/<catalog_schema_pwd>@<catalog_db>
My Query is can I use
RMAN> delete noprompt expired archivelog all;
as given in [how to delete archive log file |https://forums.oracle.com/forums/thread.jspa?threadID=2321257&start=0&tstart=0]
Or shall I take any other approach to delete the obsolete archive logs?
Regards,
*009*Are these archives backed up ? The above command only updates the RMAN repository if in case the archives were delete manually at OS level.
I would recommend you to backup these archives and then delete them.
RMAN>backup archivelog all not backedup 1 times delete input;If these archives are already backed up and have not been deleted from the disk, then you can use the below command
RMAN>delete force noprompt archivelog all completed before 'SYSDATE-n';where "n" is the number of days behind the current date. Make sure to verify if these archives have been backed up before deleting.
Regards,
Shivananda -
When to delete archive logs- using rman 10.1.0.5
Hello,
I am using rman to backup my database(10.1.0.5) along with backing up the archivelogs delete input. The retention of the backup is set to 1. I am backing the datafiles and archivelogs to disk /backupdata. I noticed that the /backupdata is filling up with a lot of backup archivelogs. Since the retention of the database is set to 1, does that mean that rman will also clean the archivelogs in /backupdata too? What I am asking is, since the retention is set to 1, does rman automatically determine witch archivelogs in the /backupdata to delete if rman determines that the archivelogs is not needed to satisfied the retention 1 condition??? Thank you in advance.rman won't automatically purge your backups. Retention policy can be defined to be 1 (what?) redundancy copies or recovery window?
You may have defined, let's say 1 redundant copy, which means you must have at least one backup to consider the other obsolete, and you will keep one redundant copy. The other backups are not automatically deleted, they are just marked obsolete, and you can delete them.
I suggest you to manually purge your backups, as they will fill up your storage. issue, from a recovery manager session:
rman> report obsolete;
rman > delete noprompt obsolete;
rman> report obsolete;
The delete noprompt obsolete will physically purge all backups reported as obsolete by the first command. You can confirm actions from the last command.
I suggest you to perform a periodic task to purge obsolete backups, schedule last command, it can be done once your regular backup ends.
If you have Enterprise manager DB Control console enabled, it can be scheduled using the internal scheduler, and it can be monitored from within EM.
~ Madrid. -
Deleting all backed up archives using RMAN
Hi,
I used 'delete input' to delete all the archives backed up.
I am storing archives in dest1 and dest2...i.e, in two locatiions in production.
Although archive in dest1 is getting deleted I am unable to delete those in dest2.Please help to delete archives in dest2 too.Ed,
Probably there is missing one "all" in your command :
C:\>rman target /
Recovery Manager: Release 11.2.0.1.0 - Production on Thu Jul 5 17:37:57 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID=1308204436)
RMAN> backup archivelog delete ALL input;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "delete": expecting one of: "all, from, high, like, low, scn, sequence, time, until"
RMAN-01007: at line 1 column 19 file: standard input
RMAN> BACKUP ARCHIVELOG ALL DELETE ALL INPUT;
Starting backup at 05-JUL-12
current log archived
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=70 device type=DISK
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=325 RECID=300 STAMP=786108184
input archived log thread=1 sequence=326 RECID=301 STAMP=786108634
Finished backup at 05-JUL-12
RMAN>Regards
Girish Sharma -
Do we need archivelog is we are using rman?
Hi,
I am confused about rnan and archivelog. If we have our database registered with rman with a recovery catalog database, then surely we do not need to have archivelog on, do we?
Thanks.A quick high-level overview:
When you change some piece of information in a table (i.e. you change the salary of an employee from 100 to 200), that change is written to the redo logs.
The redo logs are then archived by the archiver process. At that point, they are known as archive [redo] logs. These logs are necessary in order to recover a
database to a particular point in time.
When you back up your database (whether you use RMAN or something else), the archive redo logs need to be backed up.
When RMAN does your database backup, it needs to record things like which files were backed up at what point in time and the name of the corresponding backup piece. It can either do that by writing that information to the control file or, preferrably, by writing that information to the recovery catalog.
The recovery catalog, therefore, has no idea that the salary of an employee changed from 100 to 200 at a particular SCN. Instead, it knows that the archived redo log X was backed up at time Y into backup piece Z. If you needed to recover that change in the future, RMAN would read backup piece Z, extract redo log X, and apply the log to the database. The archived redo log would store the information that the salary changed from 100 to 200.
Justin -
Move large database to other server using RMAN in less downtime
Hi,
We have large database around 20TB. We want to migrate (move) the database from one server to other server. We do not want to use standby option.
1) How can we move database using RMAN in less downtime
2) Other than RMAN is there any option is available to move the database to new server
For option 1 (restore using RMAN),
Whether below options are valid?
If this option is valid, how to implement this?
1) How can we move database using RMAN in less downtime
a) Take the full backup from source (source db is up)
b) Restore the full backup in target (source db is up)
c) Take the incremental backup from source (source db is up)
d) Restore incremental backup in target (source db is up)
e) Do steps c and d, before taking downtime (source db is up)
f) Shutdown and mount the source db, and take the incremental backup (source db is down)
g) Restore last incremental backup and start the target database (target is up and application is accessing this new db
database version: 10.2.0.4
OS: SUN solaris 10
Edited by: Rajak on Jan 18, 2012 4:56 AMSimple:
I do this all the time to relocate file system files... But the principle is the same. You can do this in iterations so you do not need to do it all at once:
Starting 8AM move less-used files and more active files in the afternoon using the following backup method.
SCRIPT-1
RMAN> BACKUP AS COPY
DATAFILE 4 ####"/some/orcl/datafile/usersdbf"
FORMAT "+USERDATA";
Do as many files as you think you can handle during your downtime window.
During your downtime window: stop all applications so there is no contention in the database
SCRIPT-2
ALTER DATABASE DATAFILE 4 offline;
SWITCH DATAFILE 4 TO COPY;
RECOVER DATAFILE 4;
ALTER DATABASE DATAFILE 4 online;
I then execute the delete of the original file at somepoint later - after we make sure everything has recovered and successfully brought back online.
SCRIPT-3
DELETE DATAFILECOPY "/some/orcl/datafile/usersdbf"
For datafiles/tablespaces that are really busy, I typically copy them later in the afternoon as there are fewer archivelogs that it has to go through in order to make them consistent. The ones in the morning have more to go through, but less likelihood of there being anything to do.
Using this method, we have moved upwards 600G at a time and the actual downtime to do the switchover is < 2hrs. YMMV. As I said, this can be done is stages to minimize overall downtime.
If you need some documentation support see:
http://docs.oracle.com/cd/E11882_01/server.112/e18951/asm_rman.htm#CHDBDJJG
And before you do ANYTHING... TEST TEST TEST TEST TEST. Create a dummy tablespace on QFS and use this procedure to move it to ASM to ensure you understand how it works.
Good luck! (hint: scripts to generate these scripts can be your friend.) -
Retention policy vs. Archivelog deletion policy
Environment:
Oracle EE 11.2.0.3 on Solaris 10.5
Which policy takes precedence?
My Retention Policy is set to 'Recovery window of 8 days' and my Archivelog deletion policy is set to 'backed up 2 times to disk'.
My DAILY full backup happens at 03:00am and uses the following commands:
backup incremental level 0 cumulative database tag 'full_daily' plus archivelog tag 'full_daily';
DELETE NOPROMPT OBSOLETE;I also have an archivelog backup that runs every 4 hours at 02:00, 06:00, 10:00, 14:00, 18:00 and 22:00 and looks like this:
backup archivelog all tag '&1';
delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-8';With the archivelog backup running every 4 hours the logs are getting backed up to disk the required 2 times very quickly. Much sooner than 8 days! :-)
I have a problem where the archivelog backup that runs immediately AFTER the full database backup fails due to not being able to find some older archivelog files.
In looking at V$ARCHIVED_LOG the files were dated (COMPLETION_DATE) just outside the 8 day retention window but they had a status of 'A' (Archived) instead of the 'D' (Deleted) I was expecting. When I ran a 'Crosscheck archivelog all' it changed the statuses to 'D' and the next archivelog backup ran successfully.
What am I missing?
Should I change the archivelog deletion policy to something else? If so, what and why (just trying to understand!) ?
I am not using an FRA and have controlfile autobackup turned on.
Please let me know if you need more information. I have been scouring the docs and the 11g RMAN Oracle Press book but haven't found the trick yet!
Thanks for any assistance!
-garyHemant K Chitale wrote:
The Retention Policy applies to Backups. It does not apply to ArchiveLogs.
The ArchiveLog Deletion Policy applies to ArchiveLogs. It does not apply to Backups.
Since you have 2 copies of ArchiveLogs in the backups and these are retained for 8 days, a "delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-8';" is overkill. Why retain 8 days of archivelogs on disk if there are 2 copies already backed up ?
Does your full backup that begins at 3am complete before 6am ? If it goes beyond 6am, it will be deleting some files after 6am but the "backup archivelog all" at 6am will expect some archivelogs (8 days old) to be present.
Hemant K Chitale
RMAN> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/oracle/oracle/.Autobackup_CTRL/%F.ctl_bkp';
Starting backup at 22-MAY-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile copy
input datafile file number=00001 name=/oracle/oracle/oradata/orcl/system01.dbf
output file name=/oracle/oracle/flash_recovery_area/ORCL/datafile/o1_mf_system_7vpg432v_.dbf tag=TAG20120522T122602 RECID=1 STAMP=783951999
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:46
channel ORA_DISK_1: starting datafile copy
input datafile file number=00002 name=/oracle/oracle/oradata/orcl/sysaux01.dbf
output file name=/oracle/oracle/flash_recovery_area/ORCL/datafile/o1_mf_sysaux_7vpg5l1n_.dbf tag=TAG20120522T122602 RECID=2 STAMP=783952038
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:35
channel ORA_DISK_1: starting datafile copy
input datafile file number=00003 name=/oracle/oracle/oradata/orcl/undotbs01.dbf
output file name=/oracle/oracle/flash_recovery_area/ORCL/datafile/o1_mf_undotbs1_7vpg6ms0_.dbf tag=TAG20120522T122602 RECID=3 STAMP=783952046
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:03
channel ORA_DISK_1: starting datafile copy
input datafile file number=00004 name=/oracle/oracle/oradata/orcl/users01.dbf
output file name=/oracle/oracle/flash_recovery_area/ORCL/datafile/o1_mf_users_7vpg6ptn_.dbf tag=TAG20120522T122602 RECID=4 STAMP=783952047
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:03
Finished backup at 22-MAY-12
Starting Control File and SPFILE Autobackup at 22-MAY-12
piece handle=/oracle/oracle/product/11.2.0/dbhome_1/dbs/controlfile_c-1309370544-20120522-02 comment=NONE
Finished Control File and SPFILE Autobackup at 22-MAY-12
ORA-00604: error occurred at recursive SQL level 1
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
RMAN-08132: WARNING: cannot update recovery area reclaimable file list
old RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
new RMAN configuration parameters:
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/oracle/oracle/.Autobackup_CTRL/%F.ctl_bkp';
new RMAN configuration parameters are successfully stored
RMAN> delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-8';
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=196 device type=DISK
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=/oracle/oracle/flash_recovery_area/ORCL/archivelog/2012_04_28/o1_mf_1_2_7sq8tf5p_.arc thread=1 sequence=2
RMAN-08138: WARNING: archived log not deleted - must create more backups
archived log file name=/oracle/oracle/flash_recovery_area/ORCL/archivelog/2012_05_22/o1_mf_1_3_7vpdcjjm_.arc thread=1 sequence=3
ORA-00604: error occurred at recursive SQL level 1
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
RMAN-08132: WARNING: cannot update recovery area reclaimable file list
RMAN> having problem with Archivelog backup. -
Create Standby Database using RMAN changing backuppiece location ID753902.1
[https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWTO&id=753902.1] I am trying to create standby using above document however when I do recover database I get below error
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 07/06/2011 13:50:40
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 1899 and starting SCN of 25926696
logsequence 1899 is very very old sequence and doesnt exist on primary.this sequence is not needed because backu pwas taken after this sequence so I dont undrestand why rman is asking for a sequence that doesnt exists?
my db is 11.2 and in archivelog mode , i have all the archivelogs from the date backup was taken until now...
thanks
Edited by: user9198889 on Jul 6, 2011 8:29 AMCKPT wrote:
user9198889 wrote:
[https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWTO&id=753902.1] I am trying to create standby using above document however when I do recover database I get below error
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 07/06/2011 13:50:40
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 1899 and starting SCN of 25926696
logsequence 1899 is very very old sequence and doesnt exist on primary.this sequence is not needed because backu pwas taken after this sequence so I dont undrestand why rman is asking for a sequence that doesnt exists?
my db is 11.2 and in archivelog mode , i have all the archivelogs from the date backup was taken until now...
thanks
Edited by: user9198889 on Jul 6, 2011 8:29 AMHave you restored from the recent backup?
validate the backup compeltion_time and then retry the operation, Are you restoring from tapes?yes its recent backup(last and only backup infact ) , the backup took couple of days to run..
the backup was executing using this command BACKUP INCREMENTAL LEVEL 1 AS COMPRESSED BACKUPSET DATABASE TAG 'LEV1_BCKP_2011-06-27_11_54' PLUS ARCHIVELOG DELETE INPUT
there was no full backup so oracle must have taken full one and not incremental correct?
first logseq that was back's up is : 35818
primary uses local disk for its db and backup
standby that i am trying to create is on asm. i have copied backup to FRA and restored to +data its recovery that is failing now -
Unable to restore TABLESPACE using RMAN backups
Hi,
I am not able to restore tablespace using RMAN (TSPITR).
I have full backup of database,
While try to restore it's failed.
RMAN> recover tablespace TEST1 until logseq 706 auxiliary destination '/tmp';
Starting recover at 16-OCT-13
using channel ORA_DISK_1
RMAN-05026: WARNING: presuming following set of tablespaces applies to specified point-in-time
List of tablespaces expected to have UNDO segments
Tablespace SYSTEM
Tablespace UNDOTBS2
Creating automatic instance, with SID='CsFz'
initialization parameters used for automatic instance:
db_name=TRAINEE
db_unique_name=CsFz_tspitr_TRAINEE
compatible=11.2.0.0.0
db_block_size=8192
db_files=200
sga_target=280M
processes=50
db_create_file_dest=/tmp
log_archive_dest_1='location=/tmp'
#No auxiliary parameter file used
starting up automatic instance TRAINEE
Oracle instance started
Total System Global Area 292933632 bytes
Fixed Size 1336092 bytes
Variable Size 100666596 bytes
Database Buffers 184549376 bytes
Redo Buffers 6381568 bytes
Automatic instance created
List of tablespaces that have been dropped from the target database:
Tablespace TEST1
contents of Memory Script:
# set requested point in time
set until logseq 706 thread 1;
# restore the controlfile
restore clone controlfile;
# mount the controlfile
sql clone 'alter database mount clone database';
# archive current online log
sql 'alter system archive log current';
# avoid unnecessary autobackups for structural changes during TSPITR
sql 'begin dbms_backup_restore.AutoBackupFlag(FALSE); end;';
executing Memory Script
executing command: SET until clause
Starting restore at 16-OCT-13
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=81 device type=DISK
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /oracle/product/11.2.0/dbhome_1/dbs/c-332232391-20131016-09
channel ORA_AUX_DISK_1: piece handle=/oracle/product/11.2.0/dbhome_1/dbs/c-332232391-20131016-09 tag=TAG20131016T144951
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
output file name=/tmp/TRAINEE/controlfile/o1_mf_95wbkpvj_.ctl
Finished restore at 16-OCT-13
sql statement: alter database mount clone database
sql statement: alter system archive log current
sql statement: begin dbms_backup_restore.AutoBackupFlag(FALSE); end;
contents of Memory Script:
# set requested point in time
set until logseq 706 thread 1;
# set destinations for recovery set and auxiliary set datafiles
set newname for clone datafile 1 to new;
set newname for clone datafile 7 to new;
set newname for clone datafile 2 to new;
set newname for clone tempfile 1 to new;
set newname for datafile 6 to
"/oracle/oradata/TRAINEE/datafile/o1_mf_test1_95w9fln9_.dbf";
# switch all tempfiles
switch clone tempfile all;
# restore the tablespaces in the recovery set and the auxiliary set
restore clone datafile 1, 7, 2, 6;
switch clone datafile all;
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
renamed tempfile 1 to /tmp/TRAINEE/datafile/o1_mf_temp_%u_.tmp in control file
Starting restore at 16-OCT-13
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00001 to /tmp/TRAINEE/datafile/o1_mf_system_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00007 to /tmp/TRAINEE/datafile/o1_mf_undotbs2_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00002 to /tmp/TRAINEE/datafile/o1_mf_sysaux_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00006 to /oracle/oradata/TRAINEE/datafile/o1_mf_test1_95w9fln9_.dbf
channel ORA_AUX_DISK_1: reading from backup piece /tmp/1iomi9rv_1_1
channel ORA_AUX_DISK_1: piece handle=/tmp/1iomi9rv_1_1 tag=TAG20131016T144935
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:15
Finished restore at 16-OCT-13
datafile 1 switched to datafile copy
input datafile copy RECID=11 STAMP=828975325 file name=/tmp/TRAINEE/datafile/o1_mf_system_95wbkybb_.dbf
datafile 7 switched to datafile copy
input datafile copy RECID=12 STAMP=828975325 file name=/tmp/TRAINEE/datafile/o1_mf_undotbs2_95wbkycy_.dbf
datafile 2 switched to datafile copy
input datafile copy RECID=13 STAMP=828975325 file name=/tmp/TRAINEE/datafile/o1_mf_sysaux_95wbkybz_.dbf
contents of Memory Script:
# set requested point in time
set until logseq 706 thread 1;
# online the datafiles restored or switched
sql clone "alter database datafile 1 online";
sql clone "alter database datafile 7 online";
sql clone "alter database datafile 2 online";
sql clone "alter database datafile 6 online";
# recover and open resetlogs
recover clone database tablespace "TEST1", "SYSTEM", "UNDOTBS2", "SYSAUX" delete archivelog;
alter clone database open resetlogs;
executing Memory Script
executing command: SET until clause
sql statement: alter database datafile 1 online
sql statement: alter database datafile 7 online
sql statement: alter database datafile 2 online
sql statement: alter database datafile 6 online
Starting recover at 16-OCT-13
using channel ORA_AUX_DISK_1
starting media recovery
archived log for thread 1 with sequence 702 is already on disk as file /oracle/product/11.2.0/dbhome_1/dbs/arch1_702_807275402.dbf
archived log for thread 1 with sequence 703 is already on disk as file /oracle/product/11.2.0/dbhome_1/dbs/arch1_703_807275402.dbf
archived log for thread 1 with sequence 704 is already on disk as file /oracle/product/11.2.0/dbhome_1/dbs/arch1_704_807275402.dbf
archived log for thread 1 with sequence 705 is already on disk as file /oracle/product/11.2.0/dbhome_1/dbs/arch1_705_807275402.dbf
archived log file name=/oracle/product/11.2.0/dbhome_1/dbs/arch1_702_807275402.dbf thread=1 sequence=702
archived log file name=/oracle/product/11.2.0/dbhome_1/dbs/arch1_703_807275402.dbf thread=1 sequence=703
archived log file name=/oracle/product/11.2.0/dbhome_1/dbs/arch1_704_807275402.dbf thread=1 sequence=704
archived log file name=/oracle/product/11.2.0/dbhome_1/dbs/arch1_705_807275402.dbf thread=1 sequence=705
media recovery complete, elapsed time: 00:00:01
Finished recover at 16-OCT-13
database opened
contents of Memory Script:
# make read only the tablespace that will be exported
sql clone 'alter tablespace TEST1 read only';
# create directory for datapump import
sql "create or replace directory TSPITR_DIROBJ_DPDIR as ''
/tmp''";
# create directory for datapump export
sql clone "create or replace directory TSPITR_DIROBJ_DPDIR as ''
/tmp''";
executing Memory Script
sql statement: alter tablespace TEST1 read only
sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/tmp''
sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/tmp''
Performing export of metadata...
EXPDP> Starting "SYS"."TSPITR_EXP_CsFz":
EXPDP> Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
EXPDP> Processing object type TRANSPORTABLE_EXPORT/TABLE
EXPDP> Processing object type TRANSPORTABLE_EXPORT/POST_INSTANCE/PLUGTS_BLK
EXPDP> Master table "SYS"."TSPITR_EXP_CsFz" successfully loaded/unloaded
EXPDP> ******************************************************************************
EXPDP> Dump file set for SYS.TSPITR_EXP_CsFz is:
EXPDP> /tmp/tspitr_CsFz_17454.dmp
EXPDP> ******************************************************************************
EXPDP> Datafiles required for transportable tablespace TEST1:
EXPDP> /tmp/TRAINEE/datafile/o1_mf_test1_95wbkyck_.dbf
EXPDP> Job "SYS"."TSPITR_EXP_CsFz" successfully completed at 14:56:02
Export completed
contents of Memory Script:
# shutdown clone before import
shutdown clone immediate
executing Memory Script
database closed
database dismounted
Oracle instance shut down
Performing import of metadata...
IMPDP> Master table "SYS"."TSPITR_IMP_CsFz" successfully loaded/unloaded
IMPDP> Starting "SYS"."TSPITR_IMP_CsFz":
IMPDP> Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
Removing automatic instance
Automatic instance removed
auxiliary instance file /tmp/TRAINEE/datafile/o1_mf_temp_95wblk08_.tmp deleted
auxiliary instance file /tmp/TRAINEE/onlinelog/o1_mf_3_95wblj14_.log deleted
auxiliary instance file /tmp/TRAINEE/onlinelog/o1_mf_2_95wblhn8_.log deleted
auxiliary instance file /tmp/TRAINEE/onlinelog/o1_mf_1_95wblh8q_.log deleted
auxiliary instance file /tmp/TRAINEE/datafile/o1_mf_sysaux_95wbkybz_.dbf deleted
auxiliary instance file /tmp/TRAINEE/datafile/o1_mf_undotbs2_95wbkycy_.dbf deleted
auxiliary instance file /tmp/TRAINEE/datafile/o1_mf_system_95wbkybb_.dbf deleted
auxiliary instance file /tmp/TRAINEE/controlfile/o1_mf_95wbkpvj_.ctl deleted
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 10/16/2013 14:56:16
RMAN-06963: Error received during import of metadata
RMAN-06961: IMPDP> ORA-39123: Data Pump transportable tablespace job aborted
ORA-01565: error in identifying file '/oracle/oradata/TRAINEE/datafile/o1_mf_test1_95w9fln9_.dbf'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3Hi,
Cloud you please cheek below link:
ORACLE Cookies: TSPITR to recover a dropped tablespace
Thank you -
Script for cold backup using RMAN
Dear all,
db_version:-10.2.0.4
os_version:- Windows 2003 server
I wish to schedule a script that will take cold backup of my database using RMAN.
Any help is appreciated ..
Edited by: user12000301 on May 18, 2011 5:02 AMDear All,
Thanks a lot for your valuable time :
However i have managed to do it as follows :
1. First i have configure the parameter of RMAN ( Since it is my UAT in Noarchive log mode), I have never tried RMAN cold backup on the same.
Following is the out put of SHOW ALL;
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'D:\DB\RMAN_BKP\BACKUPS%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'D:\DB\RMAN_BKP\BACKUPS\DB_%U.%r';
CONFIGURE MAXSETSIZE TO UNLIMITED;
CONFIGURE ENCRYPTION FOR DATABASE OFF;
CONFIGURE ENCRYPTION ALGORITHM 'AES128';
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\DB\RMAN_BKP\BACKUPS\SNCFDB.ORA';
2. I have created a rman_cold_bkp.bat file which has following entry :
cd c:\oracle10g\bin
set oracle_sid=DB
rman target system/*** @D:\DB\RMAN_BKP\SCRIPT\rman_cold_bkp.rcv log=D:\DB\RMAN_BKP\SCRIPT\rman_cold_bkp.log
exit
3. Whereas rman_cold_bkp.rcv file contains following contents:
run
allocate channel C1 device type disk;
shutdown immediate;
startup mount;
backup database;
alter database open;
release channel C1;
exit
I did checked it and it;s working fine for me :-)
Regards,
Girish -
How to backup Oracle Database Single Instance using RMAN
Folks,
Hello. I am using Oracle Database Server 11gR1 with Operating System Oracle Linux 5.10.
I understand how to backup database instance in SQL Server with Windows. But don't really understand how to backup database instance in Oracle with Linux.
I have done Cold backup and Hot backup for the database instance HRCS90 but both get the same error message.
Cold backup is below:
SQL> startup
ORACLE instance started.
Total System Global Area 538677248 bytes
Fixed Size 2146024 bytes
Variable Size 528482584 bytes
Database Buffers 4194304 bytes
Redo Buffers 3854336 bytes
Database mounted.
Database opened.
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
RMAN> backup database;
Starting backup at 25-NOV-13
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 11/25/2013 14:26:52
RMAN-06171: not connected to target database
RMAN> backup HRCS90
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: "archivelog, auxiliary, as, backup, backupset, blocks, channel, check, copy, copies, controlfilecopy, cumulative, current, database, datafile, datafilecopy, device, diskratio, db_recovery_file_dest, db_file_name_convert, duration, filesperset, for, format, from, full, force, file, incremental, keep, (, maxsetsize, nochecksum, noexclude, nokeep, not, proxy, pool, reuse, recovery, section, skip, spfile, skip readonly, setsize, tablespace, tag, to, validate"
RMAN-01008: the bad identifier was: HRCS90
RMAN-01007: at line 1 column 8 file: standard input
RMAN> backup database HRCS90
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: "archivelog, auxiliary, backup, backupset, channel, copy, controlfilecopy, current, database, datafile, datafilecopy, delete, diskratio, db_recovery_file_dest, filesperset, format, from, force, file, include, keep, (, maxsetsize, noexclude, nokeep, not, pool, plus, reuse, recovery, section, ;, skip, spfile, skip readonly, setsize, tablespace, tag, to"
RMAN-01008: the bad identifier was: HRCS90
RMAN-01007: at line 1 column 17 file: standard input
While the database instance HRCS90 is startup, I do hot backup using the same commands and get the same error message with above cold backup.
My question is:
Can any folk tell me the specific steps (command by command) to backup a single database instance in Oracle using RMAN ?
Thanks.Folks,
Hello. Thanks a lot for replying. My database instance named HRCS90 is going to be backed up. My backup directory is /backup_Database_Instance_HRCS90.
If database in open state, we must back up in archive log. If database in mount state but not open, we can back up in noarchive log.
I have tried to back up HRCS90 in archive and noarchive log when database in mount state but not open as below:
SQL>startup mount;
SQL>exit
[user@linux bin]$./rman
RMAN>connect target;
RMAN> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backup_Database_Instance_HRCS90/full_%u_%s_%p';
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backup_Database_Instance_HRCS90/full_%u_%s_%p';
new RMAN configuration parameters are successfully stored
released channel: ORA_DISK_1
RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 360 DAYS;
new RMAN configuration parameters:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 360 DAYS;
new RMAN configuration parameters are successfully stored
RMAN> backup as backupset database plus archivelog;
Starting backup at 01-DEC-13
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=44 device type=DISK
specification does not match any archived log in the recovery catalog
backup cancelled because all files were skipped
Finished backup at 01-DEC-13
Starting backup at 01-DEC-13
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/oradata/HRCS90/system01.dbf
input datafile file number=00090 name=/u01/oradata/HRCS90/psimage.dbf
input datafile file number=00060 name=/u01/oradata/HRCS90/gpapp.dbf
input datafile file number=00119 name=/u01/oradata/HRCS90/tlwork.dbf
input datafile file number=00102 name=/u01/oradata/HRCS90/pttlrg.dbf
input datafile file number=00054 name=/u01/oradata/HRCS90/faapp.dbf
input datafile file number=00110 name=/u01/oradata/HRCS90/saapp.dbf
input datafile file number=00101 name=/u01/oradata/HRCS90/pttbl.dbf
input datafile file number=00002 name=/u01/oradata/HRCS90/sysaux01.dbf
input datafile file number=00106 name=/u01/oradata/HRCS90/py0lrg.dbf
input datafile file number=00004 name=/u01/oradata/HRCS90/psdefault.dbf
input datafile file number=00117 name=/u01/oradata/HRCS90/tlapp.dbf
input datafile file number=00007 name=/u01/oradata/HRCS90/adapp.dbf
input datafile file number=00082 name=/u01/oradata/HRCS90/paapp.dbf
input datafile file number=00074 name=/u01/oradata/HRCS90/hrsapp.dbf
input datafile file number=00092 name=/u01/oradata/HRCS90/ptamsg.dbf
input datafile file number=00056 name=/u01/oradata/HRCS90/fgapp.dbf
input datafile file number=00114 name=/u01/oradata/HRCS90/stapp.dbf
input datafile file number=00005 name=/u01/oradata/HRCS90/aaapp.dbf
input datafile file number=00118 name=/u01/oradata/HRCS90/tllarge.dbf
input datafile file number=00009 name=/u01/oradata/HRCS90/avapp.dbf
input datafile file number=00065 name=/u01/oradata/HRCS90/hrapp2.dbf
input datafile file number=00078 name=/u01/oradata/HRCS90/hrwork.dbf
input datafile file number=00116 name=/u01/oradata/HRCS90/stwork.dbf
input datafile file number=00077 name=/u01/oradata/HRCS90/hrswork.dbf
input datafile file number=00115 name=/u01/oradata/HRCS90/stlarge.dbf
input datafile file number=00049 name=/u01/oradata/HRCS90/epapp.dbf
input datafile file number=00098 name=/u01/oradata/HRCS90/ptprc.dbf
input datafile file number=00037 name=/u01/oradata/HRCS90/eoewapp.dbf
input datafile file number=00032 name=/u01/oradata/HRCS90/eoecapp.dbf
input datafile file number=00086 name=/u01/oradata/HRCS90/piapp.dbf
input datafile file number=00099 name=/u01/oradata/HRCS90/ptprjwk.dbf
input datafile file number=00019 name=/u01/oradata/HRCS90/cularge.dbf
input datafile file number=00035 name=/u01/oradata/HRCS90/eoeiapp.dbf
input datafile file number=00045 name=/u01/oradata/HRCS90/eoppapp.dbf
input datafile file number=00076 name=/u01/oradata/HRCS90/hrslarge.dbf
input datafile file number=00044 name=/u01/oradata/HRCS90/eoltapp.dbf
input datafile file number=00094 name=/u01/oradata/HRCS90/ptappe.dbf
input datafile file number=00050 name=/u01/oradata/HRCS90/eplarge.dbf
input datafile file number=00084 name=/u01/oradata/HRCS90/pcapp.dbf
input datafile file number=00111 name=/u01/oradata/HRCS90/sacapp.dbf
input datafile file number=00100 name=/u01/oradata/HRCS90/ptrpts.dbf
input datafile file number=00023 name=/u01/oradata/HRCS90/eobfapp.dbf
input datafile file number=00096 name=/u01/oradata/HRCS90/ptcmstar.dbf
input datafile file number=00108 name=/u01/oradata/HRCS90/pylarge.dbf
input datafile file number=00016 name=/u01/oradata/HRCS90/cularg1.dbf
input datafile file number=00018 name=/u01/oradata/HRCS90/cularg3.dbf
input datafile file number=00025 name=/u01/oradata/HRCS90/eocmapp.dbf
input datafile file number=00027 name=/u01/oradata/HRCS90/eocmwrk.dbf
input datafile file number=00029 name=/u01/oradata/HRCS90/eoculrg.dbf
input datafile file number=00033 name=/u01/oradata/HRCS90/eoeclrg.dbf
input datafile file number=00036 name=/u01/oradata/HRCS90/eoeilrg.dbf
input datafile file number=00039 name=/u01/oradata/HRCS90/eoewwrk.dbf
input datafile file number=00041 name=/u01/oradata/HRCS90/eoiulrg.dbf
input datafile file number=00046 name=/u01/oradata/HRCS90/eopplrg.dbf
input datafile file number=00048 name=/u01/oradata/HRCS90/eotplrg.dbf
input datafile file number=00053 name=/u01/oradata/HRCS90/erwork.dbf
input datafile file number=00061 name=/u01/oradata/HRCS90/gpdeapp.dbf
input datafile file number=00072 name=/u01/oradata/HRCS90/hrlarg1.dbf
input datafile file number=00079 name=/u01/oradata/HRCS90/htapp.dbf
input datafile file number=00087 name=/u01/oradata/HRCS90/pilarge.dbf
input datafile file number=00120 name=/u01/oradata/HRCS90/waapp.dbf
channel ORA_DISK_1: starting piece 1 at 01-DEC-13
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 12/01/2013 17:52:45
ORA-19504: failed to create file "/backup_Database_Instance_HRCS90/full_0boqei2c_11_1"
ORA-27040: file create error, unable to create file
Linux-x86_64 Error: 13: Permission denied
RMAN>
RMAN>
RMAN>
RMAN>
RMAN> backup as backupset database;
Starting backup at 01-DEC-13
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00001 name=/u01/oradata/HRCS90/system01.dbf
input datafile file number=00090 name=/u01/oradata/HRCS90/psimage.dbf
input datafile file number=00060 name=/u01/oradata/HRCS90/gpapp.dbf
input datafile file number=00119 name=/u01/oradata/HRCS90/tlwork.dbf
input datafile file number=00102 name=/u01/oradata/HRCS90/pttlrg.dbf
input datafile file number=00054 name=/u01/oradata/HRCS90/faapp.dbf
input datafile file number=00110 name=/u01/oradata/HRCS90/saapp.dbf
input datafile file number=00101 name=/u01/oradata/HRCS90/pttbl.dbf
input datafile file number=00002 name=/u01/oradata/HRCS90/sysaux01.dbf
input datafile file number=00106 name=/u01/oradata/HRCS90/py0lrg.dbf
input datafile file number=00004 name=/u01/oradata/HRCS90/psdefault.dbf
input datafile file number=00117 name=/u01/oradata/HRCS90/tlapp.dbf
input datafile file number=00007 name=/u01/oradata/HRCS90/adapp.dbf
input datafile file number=00082 name=/u01/oradata/HRCS90/paapp.dbf
input datafile file number=00074 name=/u01/oradata/HRCS90/hrsapp.dbf
input datafile file number=00092 name=/u01/oradata/HRCS90/ptamsg.dbf
input datafile file number=00056 name=/u01/oradata/HRCS90/fgapp.dbf
input datafile file number=00114 name=/u01/oradata/HRCS90/stapp.dbf
input datafile file number=00005 name=/u01/oradata/HRCS90/aaapp.dbf
input datafile file number=00118 name=/u01/oradata/HRCS90/tllarge.dbf
input datafile file number=00009 name=/u01/oradata/HRCS90/avapp.dbf
input datafile file number=00065 name=/u01/oradata/HRCS90/hrapp2.dbf
input datafile file number=00078 name=/u01/oradata/HRCS90/hrwork.dbf
input datafile file number=00116 name=/u01/oradata/HRCS90/stwork.dbf
input datafile file number=00077 name=/u01/oradata/HRCS90/hrswork.dbf
input datafile file number=00115 name=/u01/oradata/HRCS90/stlarge.dbf
input datafile file number=00049 name=/u01/oradata/HRCS90/epapp.dbf
input datafile file number=00098 name=/u01/oradata/HRCS90/ptprc.dbf
input datafile file number=00037 name=/u01/oradata/HRCS90/eoewapp.dbf
input datafile file number=00032 name=/u01/oradata/HRCS90/eoecapp.dbf
input datafile file number=00086 name=/u01/oradata/HRCS90/piapp.dbf
input datafile file number=00099 name=/u01/oradata/HRCS90/ptprjwk.dbf
input datafile file number=00019 name=/u01/oradata/HRCS90/cularge.dbf
input datafile file number=00035 name=/u01/oradata/HRCS90/eoeiapp.dbf
input datafile file number=00045 name=/u01/oradata/HRCS90/eoppapp.dbf
input datafile file number=00076 name=/u01/oradata/HRCS90/hrslarge.dbf
input datafile file number=00044 name=/u01/oradata/HRCS90/eoltapp.dbf
input datafile file number=00094 name=/u01/oradata/HRCS90/ptappe.dbf
input datafile file number=00050 name=/u01/oradata/HRCS90/eplarge.dbf
input datafile file number=00084 name=/u01/oradata/HRCS90/pcapp.dbf
input datafile file number=00111 name=/u01/oradata/HRCS90/sacapp.dbf
input datafile file number=00100 name=/u01/oradata/HRCS90/ptrpts.dbf
input datafile file number=00023 name=/u01/oradata/HRCS90/eobfapp.dbf
input datafile file number=00096 name=/u01/oradata/HRCS90/ptcmstar.dbf
input datafile file number=00108 name=/u01/oradata/HRCS90/pylarge.dbf
input datafile file number=00016 name=/u01/oradata/HRCS90/cularg1.dbf
input datafile file number=00018 name=/u01/oradata/HRCS90/cularg3.dbf
input datafile file number=00025 name=/u01/oradata/HRCS90/eocmapp.dbf
input datafile file number=00027 name=/u01/oradata/HRCS90/eocmwrk.dbf
input datafile file number=00029 name=/u01/oradata/HRCS90/eoculrg.dbf
input datafile file number=00033 name=/u01/oradata/HRCS90/eoeclrg.dbf
input datafile file number=00036 name=/u01/oradata/HRCS90/eoeilrg.dbf
input datafile file number=00039 name=/u01/oradata/HRCS90/eoewwrk.dbf
input datafile file number=00041 name=/u01/oradata/HRCS90/eoiulrg.dbf
input datafile file number=00046 name=/u01/oradata/HRCS90/eopplrg.dbf
input datafile file number=00048 name=/u01/oradata/HRCS90/eotplrg.dbf
input datafile file number=00053 name=/u01/oradata/HRCS90/erwork.dbf
input datafile file number=00061 name=/u01/oradata/HRCS90/gpdeapp.dbf
input datafile file number=00072 name=/u01/oradata/HRCS90/hrlarg1.dbf
input datafile file number=00079 name=/u01/oradata/HRCS90/htapp.dbf
input datafile file number=00087 name=/u01/oradata/HRCS90/pilarge.dbf
input datafile file number=00120 name=/u01/oradata/HRCS90/waapp.dbf
channel ORA_DISK_1: starting piece 1 at 01-DEC-13
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 12/01/2013 17:56:51
ORA-19504: failed to create file "/backup_Database_Instance_HRCS90/full_0coqeia5_12_1"
ORA-27040: file create error, unable to create file
Linux-x86_64 Error: 13: Permission denied
As we see the above last 2 commands, either archive or noarchive, I get the same error:
Archive: ORA-19504: "failed to create file /backup_Database_Instance_HRCS90/full_0boqei2c_11_1"
Noarchive: ORA-19504: "failed to create file /backup_Database_Instance_HRCS90/full_0coqeia5_12_1"
My question is:
What is the file "full_0boqei2c_11_1" or "full_0coqeia5_12_1" ? How to solve the above error ?
Thanks. -
Backup archive logs problem using RMAN
Hi guys
I got failure when using RMAN to backup archive log files:
Starting backup at 20-APR-06
current log archived
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 04/20/2006 21:53:57
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file /opt/oracle/flash_recovery_area/DB10G/archivelog/2006_03_17/o1_mf_1_1_21p5c251_.arc
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
RMAN> **end-of-file**
My archive log files location:
SQL> show parameter log_archive_dest
NAME TYPE VALUE
log_archive_dest_1 string LOCATION=/opt/oracle/oradata/DB10G/arch/
Current archive log files:
$ ls /opt/oracle/oradata/DB10G/arch
1_17_586191737.dbf 1_21_586191737.dbf 1_25_586191737.dbf 1_29_586191737.dbf 1_33_586191737.dbf
1_18_586191737.dbf 1_22_586191737.dbf 1_26_586191737.dbf 1_30_586191737.dbf 1_34_586191737.dbf
1_19_586191737.dbf 1_23_586191737.dbf 1_27_586191737.dbf 1_31_586191737.dbf 1_35_586191737.dbf
1_20_586191737.dbf 1_24_586191737.dbf 1_28_586191737.dbf 1_32_586191737.dbf afiedt.buf
$
But when I check v$archived_log:
SQL> select name,status,deleted from v$archived_log;
NAME S DEL
D YES
D YES
D YES
D YES
D YES
D YES
D YES
D YES
D YES
D YES
D YES
/opt/oracle/flash_recovery_area/DB10G/archivelog/2006_03_17/ A NO
/opt/oracle/flash_recovery_area/DB10G/archivelog/2006_03_18/ A NO
/opt/oracle/flash_recovery_area/DB10G/archivelog/2006_03_19/ A NO
/opt/oracle/oradata/DB10G/redo01.log A NO
/opt/oracle/oradata/DB10G/redo02.log A NO
/opt/oracle/oradata/DB10G/redo03.log A NO
/opt/oracle/oradata/DB10G/arch/1_5_585926175.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_6_585926175.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_7_585926175.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_1_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_2_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_3_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_4_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_5_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_6_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_7_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_8_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_9_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_10_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_11_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_12_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_13_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_14_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_15_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_16_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_17_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_18_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_19_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_20_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_21_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_22_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_23_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_24_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_25_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_26_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_27_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_28_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_29_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_30_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_31_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_32_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_33_586191737.dbf A NO
/opt/oracle/oradata/DB10G/arch/1_34_586191737.dbf A NO
More records than actual archived logs. How could it happen? How to solve?
THanks in advance.
SharonHi,
Use
RMAN>crosscheck archivelog all; cmd -
BACKUP AND RECOVERY USING RMAN
제품 : ORACLE SERVER
작성날짜 : 2003-08-04
BACKUP AND RECOVERY USING RMAN
==============================
1. Backup Method
1.1 backing up in noarchivelog mode
SVRMGR> shutdown;
SVRMGR> startup mount
rman을 가동시킨 후 다음을 수행
run {
# backup the database to disk
allocate channel dev1 type disk;
backup (database format '/oracle/backups/bp_%s_%p'); }
1.2 Backing up databases and tablespaces in archivelog mode >
- database 단위 backup script
run {
allocate channel dev1 type 'sbt_tape';
backup skip offline (database format '/oracle/backups/%d_%u');
release channel dev1;
- tablespace 단위 backup script
run {
allocate channel dev1 type disk;
backup
(tablespace system,tbs_1,tbs_2,tbs_3,tbs_4,tbs_5
format '/oracle/backups/bp_%s_%p');
- datafile 단위 backup script
run {
allocate channel dev1 type disk;
backup
(datafile '?/dbs/t_dbs1.f'
format '/oracle/backups/%d_%u');
- control file backup script
control file은 system datafile의 첫번째 화일을 백업받을 때 백업되며 다음과
같은 방법으로도 백업받을 수 있다.
run {
allocate channel dev1 type 'sbt_tape';
backup
(tablespace tbs_5 include current controlfile
format '%d_%u');
- archived logs backup script
NLS_LANG=american
NLS_DATE_FORMAT='Mon DD YYYY HH24:MI:SS'
run {
allocate channel dev1 type 'sbt_tape';
backup
(archivelog from time 'Nov 13 1996 20:57:13'
until time 'Nov 13 1996 21:06:05'
all
format '%d_%u');
run {
allocate channel dev1 type 'sbt_tape';
backup
(archivelog low logseq 288 high logseq 301 thread 1
all delete input
format '%d_%u');
- copying datafiles
run {
allocate channel dev1 type disk;
copy datafile '?/dbs/tbs_01.f/dbs/tbs_01.f' to '?/copy/temp3.f';
- incremental backups
새로운 데이타화일이 추가되거나 테이블스페이스가 추가된다면 level 0의 backup을
반드시 수행한다.
run {
allocate channel dev1 type 'sbt_tape';
backup incremental level 0
(database
format '%d_%u');
run {
allocate channel dev1 type 'sbt_tape';
backup incremental level 1
(database
format '&d_%u');
2. Recovery Method
- tablespace recovery
run {
allocate channel dev1 type disk;
allocate channel dev2 type 'sbt_tape';
sql "alter tablespace tbs_1 offline immediate" ;
set newname for datafile 'disk7/oracle/tbs11.f'
to 'disk9/oracle/tbs11.f' ;
restore (tablespace tbs_1) ;
switch datafile all ;
recover tablespace tbs_1 ;
sql "alter tablespace tbs_1 online" ;
release channel dev1;
release channel dev2;
- point-in-time recovery
TBS_1 테이블스페이스는 두 개의 데이타 화일 소유. TEMP1은 백업이 없으나 user
data는 없는 temporary segemnt만 가지고 있음.
NLS_LANG=american
NLS_DATE_FORMAT='Mon DD YYYY HH24:MI:SS'
SVRMGR> shutdown abort;
SVRMGR> startup nomount;
run {
# recover database until 3pm after restoring tbs_1 to a new location
allocate channel dev1 type disk;
allocate channel dev2 type 'sbt_tape';
set until time 'Nov 15 1996 15:00:00'
set newname for datafile '/vobs/oracle/dbs/tbs_11.f'
to '?/dbs/temp1.f' ;
set newname for datafile '?/dbs/tbs_12.f'
to '?/dbs/temp2.f' ;
restore controlfile to '/vobs/oracle/dbs/cf1.f' ;
replicate controlfile from '/vobs/oracle/dbs/cf1.f';
sql "alter database mount" ;
restore database skip tablespace temp1;
switch datafile all;
recover database skip tablespace temp1;
sql "alter database open resetlogs";
sql "drop tablespace temp1";
sql "create tablespace temp1 datafile '/vobs/oracle/dbs/temp1.f' size 10M";
release channel dev1;
release channel dev2;
- 전체 데이타베이스를 복구하려 할때
current redologfile이 존재할때 다음과 같은 작업으로 전체 데이타베이스를 복구할
수 있다.
replace script restore_recover_db_cf {
execute script restore_cf;
sql 'alter database mount';
execute script restore_db;
execute script recover_db;
sql 'alter database open resetlogs';
replace script alloc_1_disk {
allocate channel d1 type disk;
setlimit channel d1 kbytes 2097150 maxopenfiles 32 readrate 200;
replace script rel_1_disk {
release channel d1;
replace script restore_cf {
execute script alloc_1_disk;
restore
controlfile to '/private/db_files/twih/dbf/ctrl_twih_1.ctl';
replicate
controlfile from '/private/db_files/twih/dbf/ctrl_twih_1.ctl';
execute script rel_1_disk;
replace script restore_db {
execute script alloc_1_disk;
restore
(database);
execute script rel_1_disk;
replace script recover_db {
execute script alloc_1_disk;
recover
database;
execute script rel_1_disk;
Reference Documents
<Note:104796.1>Hi Alok,
why there is a need for standby here? you mean to say standby db?
what i exactly need is , whether i will be making use of archivelogs which are all archived during that backup period (in mount stage) after some days, if i face any problem with the PRODUCTION Database..
Maybe you are looking for
-
How do i transfer pictures from ipad 2 to pc
how do i transfer pictures from my ipad 2 to my pc
-
Insert Edit and Overwrite Edit Crashes This One Premiere Project
Hi All, I'm working off of many premiere projects, and one crashes when I use the insert edit and override edit button. At first it was only if I used the keyboard command, but now it happens when using the mouse. I'm afraid the project file is corru
-
Hi, I have created a custom field in the FI invoice (FB01) that it is not created in the MM invoice (Miro). When I post the MM Invoice I need to know a user exit or BADI that can help me to retrieve the value required for the FI invoice from a custom
-
Why can't I access Scrabble through Facebook on my IPOD Touch?
Why can't I access Scrabble through Facebook on my IPOD Touch?
-
Where can I buy the mSATA adapter for GT70?
I have a GT70 0NC-494 which came with only a 750GB hard drive. I bought a SATA 3 SSD and i'm having lots of issues with it (like underspeed and unstability), so I want to install a super-raid adapter instead of a single SSD. thanks a lot