 RMAN - BACKUP ARCHIVELOG ALL DELETE INPUT - when arch_dest is full [message #190878] |
Fri, 01 September 2006 16:34  |
krouelle
Messages: 1
Registered: September 2006
|
Junior Member |
|
|
Is it possible to perform a "backup archivelog all delete input" if the arch_dest directory is full and the database is locked? The directory hit 100% when the latest archive file was being written. We have an automated procedure that backs up the arch_dest when it reaches 50%, but due to tape device problems the devices could not allocate before the arch_dest reached 100%. Our backup command template as shown below attempts; SQL 'alter system archive log current'; but fails due to arch_dest being 100% full. If we remove this and the SQL 'alter system switch logfile' command, will the backup archivelog all delete input; work? I'm thinking it will not, because the current file is locked and has not completely written to disk. When this happens I have removed the oldest files which frees up oracle to continue writing, then I run "change archivelog all crosscheck;", followed by a full incr 0 backup.
Please advise on the best procedure for dealing with this problem.
Thanks,
Kevin
RMAN archive backup command template:
run {
allocate channel 'dev_0' type 'sbt_tape'
parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=application,OB2BARLIST=host_sid_arch)';
allocate channel 'dev_1' type 'sbt_tape'
parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=application,OB2BARLIST=host_sid_arch)';
SQL 'alter system archive log current'
;
SQL 'alter system switch logfile'
;
backup
format 'host_sid_arch<application_%s:%t:%p>.dbf'
archivelog all delete input
;
resync catalog
;
}
|
|
|
|
|
|
|
|
| Re: RMAN - BACKUP ARCHIVELOG ALL DELETE INPUT - when arch_dest is full [message #227835 is a reply to message #192013] |
Thu, 29 March 2007 13:05  |
tobyc
Messages: 9
Registered: March 2007
|
Junior Member |
|
|
Kim,
The problem with the arch_dest being 100% full happened to me today. I moved some archive logs to a different directory and ran the rman archlog backup. The job ran okay and backed up the archive logs and deleted them from the OS. I then moved the other archive logs back to the orginal arch_dest and re-ran the rman archlog backup job. I got errors. Header errors- said make sure the files are associated with the database.
In your last post on this subject you said "Move a (bunch of) archive log to another location on the server.
And if You tell rman about this, You can even get it to backup and delete those too."
How would you do that? I'm new to rman and would appreicate any help. Thanks,
Toby
|
|
|
|
|
|
| Re: RMAN - BACKUP ARCHIVELOG ALL DELETE INPUT - when arch_dest is full [message #227895 is a reply to message #227835] |
Fri, 30 March 2007 01:37 |
 |
ebrian
Messages: 2794
Registered: April 2006
|
Senior Member |
|
|
Are you sure the archivelogs you moved weren't backed up already? Otherwise, you should have encountered an error when you tried to backup your archive logs.
RMAN> list archivelog all;
using target database control file instead of recovery catalog
List of Archived Log Copies
Key Thrd Seq S Low Time Name
------- ---- ------- - --------- ----
25 1 29 A 03-MAR-07 E:\ORACLE\FLASH_RECOVERY_AREA\WIN10G\ARCHIVELOG\2007_03_08\O1_MF_1_29_2Z1MFX9R_.ARC
26 1 30 A 08-MAR-07 E:\ORACLE\FLASH_RECOVERY_AREA\WIN10G\ARCHIVELOG\2007_03_17\O1_MF_1_30_2ZS09BJ3_.ARC
27 1 31 A 17-MAR-07 E:\ORACLE\FLASH_RECOVERY_AREA\WIN10G\ARCHIVELOG\2007_03_30\O1_MF_1_31_30SCFTRF_.ARC
RMAN> host;
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
E:\>move E:\ORACLE\FLASH_RECOVERY_AREA\WIN10G\ARCHIVELOG\2007_03_08\O1_MF_1_29_2Z1MFX9R_.ARC E:\ORAC
LE\FLASH_RECOVERY_AREA\WIN10G\ARCHIVELOG2
E:\>exit
host command complete
RMAN> backup archivelog all;
Starting backup at 30-MAR-07
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=143 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 03/30/2007 02:32:29
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file E:\ORACLE\FLASH_RECOVERY_AREA\WIN10G\ARCHIVELOG\2007_03_08\O1_MF_1_29_2Z1MFX9R_.ARC
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
RMAN>
By the way...what version of the database are you using?
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
