-
RMAN-05019 Warning
I have a "Oracle recommended backup" running on disk. It backsup to the FLASH recovery area. The job runs and it completes every time with this warning:
RMAN-05019: WARNING: no channel of required type allocated to recover copy of datafile n
Where n= 1-19
I tried looking this error up but can't find much info on it. I found some info that said to use the LIST command and then allocate the proper type to stop the error. I'm a little new to Oracle. Where do I see what type needs to be allocated? And how do I change the allocation? I am using a combonation of command line and EM. Thanks for the help
Paul
-
Hi Paul
Can you please post the generated script here.
ALso at the RMAN prompt can you say
RMAN>SHOW DEVICE TYPE
and then post the contents here
RMAN>SHOW DATAFILE BACKUP COPIES
regards
Hrishy
-
RMAN Script
Here is the output log:
connected to target database: AX (DBID=2713737753)
using target database control file instead of recovery catalog
echo set on
Starting recover at 11-SEP-07
run {
allocate channel oem_disk_backup device type disk;
recover
allocated channel: oem_disk_backup
channel oem_disk_backup: sid=499 instance=ax1 devtype=DISK
RMAN-05019: WARNING: no channel of required type allocated to recover copy of datafile 1
RMAN-05019: WARNING: no channel of required type allocated to recover copy of datafile 2
RMAN-05019: WARNING: no channel of required type allocated to recover copy of datafile 3
RMAN-05019: WARNING: no channel of required type allocated to recover copy of datafile 4
RMAN-05019: WARNING: no channel of required type allocated to recover copy of datafile 5
RMAN-05019: WARNING: no channel of required type allocated to recover copy of datafile 6
RMAN-05019: WARNING: no channel of required type allocated to recover copy of datafile 7
RMAN-05019: WARNING: no channel of required type allocated to recover copy of datafile 8
RMAN-05019: WARNING: no channel of required type allocated to recover copy of datafile 9
RMAN-05019: WARNING: no channel of required type allocated to recover copy of datafile 10
RMAN-05019: WARNING: no channel of required type allocated to recover copy of datafile 11
RMAN-05019: WARNING: no channel of required type allocated to recover copy of datafile 12
RMAN-05019: WARNING: no channel of required type allocated to recover copy of datafile 13
RMAN-05019: WARNING: no channel of required type allocated to recover copy of datafile 14
RMAN-05019: WARNING: no channel of required type allocated to recover copy of datafile 15
RMAN-05019: WARNING: no channel of required type allocated to recover copy of datafile 16
RMAN-05019: WARNING: no channel of required type allocated to recover copy of datafile 17
RMAN-05019: WARNING: no channel of required type allocated to recover copy of datafile 18
RMAN-05019: WARNING: no channel of required type allocated to recover copy of datafile 19
Finished recover at 11-SEP-07
Starting backup at 11-SEP-07
channel oem_disk_backup: starting incremental level 1 datafile backupset
channel oem_disk_backup: specifying datafile(s) in backupset
input datafile fno=00009 name=+DATA/ax/datafile/phigh1.ora
input datafile fno=00010 name=+DATA/ax/datafile/pgrow1.ora
input datafile fno=00013 name=+DATA/ax/datafile/phuge1.ora
input datafile fno=00002 name=+DATA/ax/datafile/undotbs1.258.622126609
input datafile fno=00016 name=+DATA/ax/datafile/ihigh1.ora
input datafile fno=00017 name=+DATA/ax/datafile/igrow1.ora
input datafile fno=00011 name=+DATA/ax/datafile/pmedium1.ora
input datafile fno=00003 name=+DATA/ax/datafile/sysaux.257.622126609
input datafile fno=00018 name=+DATA/ax/datafile/imedium1.ora
input datafile fno=00006 name=+DATA/ax/datafile/undotbs2.265.622126955
input datafile fno=00001 name=+DATA/ax/datafile/system.256.622126607
input datafile fno=00004 name=+DATA/ax/datafile/users.259.622126609
input datafile fno=00008 name=+DATA/ax/datafile/pstatic1.ora
input datafile fno=00012 name=+DATA/ax/datafile/pdynamo1.ora
input datafile fno=00015 name=+DATA/ax/datafile/istatic1.ora
input datafile fno=00005 name=+DATA/ax/datafile/example.264.622126791
input datafile fno=00007 name=+DATA/ax/datafile/pblob1.ora
input datafile fno=00019 name=+DATA/ax/datafile/idynamo1.ora
input datafile fno=00014 name=+DATA/ax/datafile/iblob1.ora
channel oem_disk_backup: starting piece 1 at 11-SEP-07
channel oem_disk_backup: finished piece 1 at 11-SEP-07
piece handle=+FLASH/ax/backupset/2007_09_11/nnndn1_tag20070911t020015_0.2503.632973617 tag=TAG20070911T020015 comment=NONE
channel oem_disk_backup: backup set complete, elapsed time: 00:04:45
Finished backup at 11-SEP-07
Starting Control File and SPFILE Autobackup at 11-SEP-07
piece handle=+FLASH/ax/autobackup/2007_09_11/s_632973901.2504.632973903 comment=NONE
Finished Control File and SPFILE Autobackup at 11-SEP-07
released channel: oem_disk_backup
exit;
SHow device type;
RMAN configuration parameters are:
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
RMAN> show datafile backup copies;
RMAN configuration parameters are:
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
I have Symantec Backup Exec running at other times, it backs up to tape. This backup that is failing is supposed to go to Disk. Thanks for your help!
-
Hi
Whats the output of
RMAN> LIST COPY OF DATAFILE 1, 2, 3
My suspicion is that the symantic backup you ran backed up a.k.a moved the contents (datafile copies) to the tape am i right ?
regards
Hrishy
-
RMAN Output
Here is the result of that RMAN command:
RMAN> list copy of datafile 1, 2, 3;
using target database control file instead of recovery catalog
List of Datafile Copies
Key File S Completion Time Ckp SCN Ckp Time Name
------- ---- - --------------- ---------- --------------- ----
30 1 A 24-AUG-07 5011977798 23-AUG-07 +FLASH/ax/datafile/sys
tem.2130.631249999
32 2 A 24-AUG-07 5011977798 23-AUG-07 +FLASH/ax/datafile/und
otbs1.2123.631249633
23 3 A 24-AUG-07 5011977798 23-AUG-07 +FLASH/ax/datafile/sys
aux.2127.631249883
RMAN>
SYamntec BAckup Exec does backup files onto the tape unit. Thanks for your help!
-
Hi
Whats the output of the following commands
report obsolete;
crosscheck backup;
crosscheck copy;
I asked arounf about this problem to friends and
Here is what Niall Litchfeild asked me can you post answers to this questions too
Is your ASM instance up and running ?
is the FLASH disk group available within ASM
regards
Hrishy
-
1 Attachment(s)
Results:
Hi Hrishy;
I attached the files for those reports, as the outputs were long. The ASM instance is running fine and the FLASH disk group is available in ASM. Those obsolete files, is there something I have to do with those or does Oracle get rid of them. Thanks for all your help!
All 3 logs are in the zip file
Paul
-
Hi
How does your rman backup script look like is it similar to the one below.
Code:
run {
allocate channel oem_backup_disk1 type disk format 'd:\mad3_nightly_backups\%U';
backup incremental level 1 database include current controlfile;
recover copy of database;
backup as BACKUPSET tag 'mybackupset' archivelog all not backed up delete all input;
report obsolete;
crosscheck backup;
crosscheck copy;
report need backup;
report unrecoverable;
release channel oem_backup_disk1;
}
You can get rid of those obsolete copies using the following rman commands
Code:
RMAN>DELETE NOPROMPT OBSOLETE EXPIRED BACKUP
RMAN>DELETE NOPROMPT OBSOLETE EXPIRED ARCHIVELOG ALL
RMAN>DELETE NOPROMPT OBSOLETE EXPIRED COPY
the above code is going to delete expired and obsolete backups and copies of datafile and also archived logs
-
Script
This job was set up in EM. Here is the "Daily backup Script" it generated:
run {
allocate channel oem_disk_backup device type disk;
recover copy of database with tag 'ORA\$OEM_LEVEL_0';
backup incremental level 1 cumulative copies=1 for recover of copy with tag 'ORA\$OEM_LEVEL_0' database;
}
Am I better off deleting this job from EM and creating a new job in RMAN? I know RMAN gives more power/functionality than EM. Thanks again
Paul
-
Hi Paul
Well logically speaking it shouldnt matter much since under the covers those fancy GUI widgets again call RMAN.
What i would like to try is this manually and see what happens
Code:
RMAN>DELETE NOPROMPT OBSOLETE EXPIRED BACKUP
RMAN>DELETE NOPROMPT OBSOLETE EXPIRED ARCHIVELOG ALL
RMAN>DELETE NOPROMPT OBSOLETE EXPIRED COPY
run {
allocate channel oem_disk_backup device type disk;
recover copy of database with tag 'ORA\$OEM_LEVEL_0';
backup incremental level 1 cumulative copies=1 for recover of copy with tag 'ORA\$OEM_LEVEL_0' database;
}
regards
Hrishy
-
Error Message
I tried to run the delete obsolete commands, this is what Im getting:
RMAN> delete noprompt obsolete expired backup;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "expired": expecting one of: "device, high, orph
an, redundancy, recovery, ;, until"
RMAN-01007: at line 1 column 26 file: standard input
RMAN>
WHat is it looking for?
Paul
-
Hi Paul
Apologies please try
Code:
RMAN>DELETE NOPROMPT EXPIRED BACKUP ;
RMAN>DELETE NOPROMPT EXPIRED ARCHIVELOG ALL ;
RMAN>DELETE NOPROMPT EXPIRED COPY;
And please run your backupscript again and post the results if you get the error that you are getting
regards
Hrishy
-
Delete
Ok, I ran the 3 commands to delete and they ran fine. But when I run the REPORT OBSOLETE command, it still lists a whole mess of stuff. So I ran DELETE OBSOLETE, and this failed. The error said: "no channel allocated for maintenance (of an appropriate type)". Could this be because it is trying to delete some of the BackupExec jobs? I see jobs listed in the report that have "BE_" in the front of the name. The report is still showing the "+FLASH" datafile copes also. Thanks
-
Hi
Please try
Code:
allocate channel c1 for maintenance device type disk;
crosscheck backup;
delete noprompt obsolete;
and then run the
regards
Hrishy
-
Error
Tried to run that command and got an error:
RMAN> allocate channel c1 for maintenance device type disk;
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: "for"
RMAN-01008: the bad identifier was: c1
RMAN-01007: at line 1 column 18 file: standard input
I've been in meetings all day, so I havent had a chance to look it up. I'll see if I can fix it later. I would much rather be learning more Oracle!
Paul
-
Hi Paul
Apologies again as i dont have a database to test my commands at the moment
Here is what you need to do
Code:
allocate channel for maintenance device type disk ;
crosscheck backup;
delete noprompt obsolete
-
Errors
I'm still getting a failure for the Delete Obsolete command. The other 2 worked, but when I run the delete it still says no cahannel allocated for maiintenance(of an appropriate type). I don't get that, it allocates the disk ok. Any thoughts?
-
Hi
Please try
Code:
run {
allocate channel device type sbt;
delete force obsolete;
}
-
delete worked
Hey thay worked! deleated a whole bunch of obsolete archive logs. Great! Thanks! Deleted 899 objects. I noticed it deleted the stuff on the +FLASH and some of the stuff from BE. HOw come allocating the SBT worked and not the disk?
Paul
-
Hi
Did the folks before you leave some documentation behind ?
It worked because sbt channel was used earlier to make copies etc.You need to look at the earlier docs and all what those people gave you before you were there.
Can you please run the oracle reccommended backup strategy and then let us know if you are still hitting that error for which you started this thread
regards
Hrishy
-
it works!
I ran the Oracle Suggested backup last night and this morning it ran with no problems! Thanks so much for all your help, i learned alot! Thanks again
Paul
-
Hi Paul
You are most welcome
its great to know that the problem has been solved
regards
Hrishy