Respaldando con RMAN 11gR2 y Netbackup sucede el error RMAN-10038 database session for channel CH1 terminated unexpectedly

Ahora que ando migrando bases de datos de un Nodo a un ambiente RAC, me volvi a topar con este error cuando corro un respaldo a Netbackup

connected to target database: TESTDB (DBID=1193295160)

RMAN> run
2> {
3> ALLOCATE CHANNEL CH1 DEVICE TYPE SBT PARMS 'BLKSIZE=262144';
4> BACKUP FORMAT '%d_%M_%D_%Y_%t.ctl' CURRENT CONTROLFILE;
5> }

using target database control file instead of recovery catalog
allocated channel: CH1
channel CH1: SID=548 instance=TESTDB1 device type=SBT_TAPE
channel CH1: Veritas NetBackup for Oracle - Release 6.5 (2007072323)

Starting backup at 29-JAN-12
channel CH1: starting full datafile backup set
channel CH1: specifying datafile(s) in backup set
including current control file in backup set
channel CH1: starting piece 1 at 29-JAN-12
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on CH1 channel at 01/29/2012 20:21:16
RMAN-10038: database session for channel CH1 terminated unexpectedly

Lo que me di cuenta es que la instalacion del cliente que tenia era una version no compatible con 11gR2

oracle $ cat /usr/openv/netbackup/bin/version
NetBackup-RedHat2.6 6.5.1

Una vez que actualize a la version 6.5.6, todo funciono como deberia

oracle $ cat /usr/openv/netbackup/bin/version
NetBackup-RedHat2.6 6.5.6

RMAN> run
2> {
3> ALLOCATE CHANNEL CH1 DEVICE TYPE SBT PARMS 'BLKSIZE=262144';
4> BACKUP FORMAT '%d_%M_%D_%Y_%t.ctl' CURRENT CONTROLFILE;
5> }

using target database control file instead of recovery catalog
allocated channel: CH1
channel CH1: SID=814 device type=SBT_TAPE
channel CH1: Veritas NetBackup for Oracle - Release 6.5 (2007072323)

Starting backup at 30-JAN-12
channel CH1: starting full datafile backup set
channel CH1: specifying datafile(s) in backup set
including current control file in backup set
channel CH1: starting piece 1 at 30-JAN-12
channel CH1: finished piece 1 at 30-JAN-12
piece handle=TESTDB_01_30_2012_773976339.ctl tag=TAG20120130T012539 comment=API Version 2.0,MMS Version 5.0.0.0
channel CH1: backup set complete, elapsed time: 00:01:05
Finished backup at 30-JAN-12

Starting Control File and SPFILE Autobackup at 30-JAN-12
piece handle=c-2326906767-20120131-00 comment=API Version 2.0,MMS Version 5.0.0.0
Finished Control File and SPFILE Autobackup at 30-JAN-12
released channel: CH1

Puedes encontrar la informacion mas reciente en la pagina de Symantec (INGLES) en:
RMAN-10038 error when