Has anyone encountered this problem? If so, how did you resolve it?

After upgrading the AIX level on which the TSM server runs from AIX 5.2.0
ML01 to ML02, a TDP for Oracle (TDO) version 2.2.1.0 client is now unable to
do a full backup.  After running for 4 or 5 hours the full backup fails on
varing datasets.  The TDO client is running on system with AIX 5.1.0 ML03
and TSM BA client 5.1.0.0.  The error in the sbtio.log file is of the form
that follows. However since some of the failed full backups did not generate
this error in the sbtio.log file, this error may be caused by some other
activity (like tdposync).

SBT-108412 11/07/2003 02:23:57 remove2.cpp(237): sbtremove2(): Exit - wrong
state, dsmHandle = 1, state = 2

The error reported by RMAN and Oracle's interpretation of the error is:

> RMAN-00571: ===========================================================
> RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
> RMAN-00571: ===========================================================
> RMAN-03007: retryable error occurred during execution of command: backup
> RMAN-07004: unhandled exception during command execution on channel c1
> RMAN-10035: exception raised in RPC: ORA-19506: failed to create
>          sequential file, name="prod_backup_4578_f2f538v0_9_1", parms=""
> ORA-27028: skgfqcre: sbtbackup returned error
> ORA-19511: ANU0004E An unknown error has been detected.
> RMAN-10031: ORA-19624 occurred during call to
> DBMS_BACKUP_RESTORE.BACKUPPIECECREATE

And this is Oracle's interpretation of that error:

prod1 $ oerr ora 27028
27028, 00000, "skgfqcre: sbtbackup returned error"
// *Cause:  sbtbackup returned an error.  This happens when creating a backup
//          file during a backup operation.
// *Action: This error is returned from the media management software which is
//          linked with Oracle.  There should be additional messages which
//          explain the cause of the error.  This error usually requires
//          contacting the media management vendor.