oracle backup RMAN fails

[Former Member]

Hello All,

The backup on production system is failing with the follwing error.

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03009: failure of backup command on sbt_1 channel at 11/05/2014 22:17:43

ORA-27192: skgfcls: sbtclose2 returned error - failed to close file

ORA-19511: Error received from media manager layer, error text:

   BKI9309E: Operation terminated due to an explicit abort request.

ORA-19502: write error on file "SID_bepcxsed.1763_1", block number 23841 (block size=8

ORA-27030: skgfwrt: sbtwrite2 returned error

ORA-19511: Error received from media manager layer, error text:

   BKI5008E: Tivoli Storage Manager Error:

RMAN>

specification does not match any backup in the repository

RMAN>

Recovery Manager complete.

BR0280I BRBACKUP time stamp: 2014-11-05 22.22.24

BR0279E Return code from 'SHELL=/bin/sh /oracle/SID/112_64/bin/rman nocatalog': 1

BR0536E RMAN call for database instance SID failed.

Please let me know how should i rectify it. The file permissions and storage is all fine.

I even checked the command ps -ef|grep -i tdp and ps -ef|grep -i dsm. They are also working fine.

Is it a TSM related issue?

Regards,

Vishwanath B

[former_member207186 · Accepted solution]

Hello,

Basically this indicates a TSM related issue.

The ORA-19511 originates with the media manager. The cause of this error seems to be some issues with the media management software (TSM) which is linked with oracle server process to perform backup activites with the help of RMAN. As you can see, the error codes "BKI9309E" and "BKI5008E" came from the backup tool/TSM you are using.

In this case, I advise you to contact your TSM partner/vendor for further help.

Regards,

Bíborka

[Reagan]

ORA-19511: Error received from media manager layer, error text:
   BKI5008E: Tivoli Storage Manager Error:

This is a TSM issue. I would get a TSM specialist to check the logs in the TSM server.

Also check if the prole process is running at the OS level.