ORA-19511: Error received from media manager layer, error text:
Hello, we're using Netbackup 8.0. I'm still new in Offline Storage (3-1/2 months). Our DBAs are seeing errors in Oracle for Archive backups, but I'm not seeing these errors when I check "Detailed Status".
Here are the DBA's 2 errors:
RMAN-03009: failure of backup command on ch00 channel at
ORA-19509: failed to delete sequential file, handle="_ARCHIVE_", parms="BLKSIZE=1048576"
ORA-27027: sbtremove2 returned error
ORA-19511: Error received from media manager layer, error text:
Failed to remove,_ARCHIVE_, from image catalog.
ORA-27191: sbtinfo2 returned error
Additional information: 3282
ORA-19511: Error received from media manager layer, error text:
RMAN> RMAN>
Recovery Manager complete.
EXITERROR:
channel ch00: starting piece 1 at 03-OCT-2017 07:44:06
released channel: ch00
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ch00 channel at 10/03/2017 07:47:31
ORA-19509: failed to delete sequential file, handle="_ARCHIVE_20171003_0737.", parms="BLKSIZE=1048576"
ORA-27027: sbtremove2 returned error
ORA-19511: Error received from media manager layer, error text:
Failed to remove, _ARCHIVE_20171003_0737., from image catalog.
ORA-27191: sbtinfo2 returned error
Additional information: 3282
ORA-19511: Error received from media manager layer, error text:
RMAN> RMAN>
Recovery Manager complete.
EXITERROR:1
Another variation:
RMAN-03009: failure of backup command on ch00 channel at 09/28/2017 03:30:51
ORA-27191: sbtinfo2 returned error
Additional information: 3282
ORA-19511: Error received from media manager layer, error text:
Failed to get info on backup file, _ARCHIVE_20170928_0303.p1.s48326.955855565.
---Any ideas on what I should check or do you think it's something on the DBA/Oracle side?
Thanks
Checking this morning, I saw that the archives were completing with the ctl file. I asked the DBA if she had many any changes to her script last night. Here's her response: "The archive logs weren’t applying to the backup datacenter, so they wouldn’t clean up for this particular db. There were so many that when backup tried to run for that one database, it would bomb. All looks good now."
We weren't aware that they were supposed to be applying to the other datacenter.
Everyone, thanks for your responses; I learned a lot.
