Seeing following error stack in Oracle binary log:
Information 2013/02/13 06:32:40 2169 Data Plugin HSW-KVASY-DB RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
Information 2013/02/13 06:32:40 2169 Data Plugin HSW-KVASY-DB RMAN-00571: ===========================================================
Information 2013/02/13 06:32:40 2169 Data Plugin HSW-KVASY-DB RMAN-03009: failure of allocate command on cspfile channel at 02/13/2013 07:32:42
Information 2013/02/13 06:32:40 2169 Data Plugin HSW-KVASY-DB ORA-19554: error allocating device, device type: SBT_TAPE, device name:
Information 2013/02/13 06:32:40 2169 Data Plugin HSW-KVASY-DB ORA-27000: skgfqsbi: failed to initialize storage subsystem (SBT) layer
Information 2013/02/13 06:32:40 2169 Data Plugin HSW-KVASY-DB ORA-19511: Error received from media manager layer, error text:
Information 2013/02/13 06:32:40 2169 Data Plugin HSW-KVASY-DB SBT error = 7111, errno = 0, sbtinit: system error
Information 2013/02/13 06:32:40 2169 Data Plugin HSW-KVASY-DB Recovery Manager complete.
Warning 2013/02/13 06:32:40 2169 Data Plugin HSW-KVASY-DB Failed with exit code 1
Error 2013/02/13 06:32:40 2169 Data Plugin HSW-KVASY-DB RMAN returned exit code 1
Missing or incorrect NV Server information in the 'Plugin for Oracle' configuration tab.
For RMAN backups, the NetVault Backup Server name MUST be specified in the 'Plugin for Oracle' Configuration tab.
This was found out initially by running an sbt output test to see if there was a problem with the command, however it showed the reason for the issue as well. It showed that SBT was trying to connect to the NV Server name which was using the client name.
Because the NV Server name was not put in the 'Plugin for Oracle' configuration tab, the sbttest was using the default NetVault Oracle client to run the backup. The SBT API then errored out stating it could not find the NV Backup Server name.
