So your dutiful Infrastructure Team upgrades the Data Domain backup appliance with the latest DD OS code and patches, bringing you up to the latest patch level.

After this, your RMAN backups using DD Boost start failing, and checking the sbtio.log file, which is found in the user dump destination, we see entries like this:

SBT-27970 (211074992) 04/01/16 21:45:01 ERR : [6D42:C94BFB0] ddp_open_file() failed for File: dd0205_boost/XIO11WSB_df_svr1vlas_1_1.bk, Err: 5034-nfs create failed (nfs: Permission denied)
SBT-27970 (211074992) 04/01/16 21:45:01 error 7501: sbtbackup: Could not create file XIO11WSB_df_svr1vlas_1_1.bk on host rstdd0205mgmt.us.oracle.com, error 5034
SBT-27973 (227712944) 04/01/16 21:45:01 ERR : [6D45:D929FB0] ddp_open_file() failed for File: dd0205_boost/XIO11WSB_df_t0r1vlas_1_1.bk, Err: 5034-nfs create failed (nfs: Permission denied)
SBT-27973 (227712944) 04/01/16 21:45:01 error 7501: sbtbackup: Could not create file XIO11WSB_df_t0r1vlas_1_1.bk on host rstdd0205mgmt.us.oracle.com, error 5034

This is DD Boost 1.3, and the problem is that the lockbox authentication needs to be regenerated.

But the second problem is that re-executing the original lockbox script in RMAN does not resolve the problem.

In order to solve this problem, we need to delete the Boost configuration files on the database server, so that the lockbox script will completely recreate them.

To remove them, we typically find them in $ORACLE_HOME/config:

[oracle@rstemc64vm22 config]$ pwd
/u01/app/oracle/product/11.2.0/dbhome_1/config

[oracle@rstemc64vm22 config]$ ls -ltr
total 20
-rw-r--r-- 1 oracle asmadmin 2834 Apr  7  2015 ddboost.config.bak
-rw-r--r-- 1 oracle asmadmin    2 Apr  7  2015 ddboost.config.bak.FCD
-rw-r--r-- 1 oracle asmadmin 4182 Apr  1 22:30 ddboost.config
-rw-r--r-- 1 oracle asmadmin   14 Apr  1 22:30 ddboost.config.FCD

So go ahead and delete all of these files, and then re-execute the Boost lockbox script inside of RMAN:

[oracle@rstemc64vm22 lockbox]$ rman target /

Recovery Manager: Release 11.2.0.4.0 - Production on Fri Apr 1 22:36:11 2016

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

connected to target database: XIO11WSB (DBID=2386171380)

RMAN> run {
2> allocate channel dd0 type sbt PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0/dbhome_1/lib/libddobk.so,ENV=(ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1)';
3> 
4> send 'set username ddboostora password mypassword servername rstdd0205mgmt.emc.com';
5> 
6> release channel dd0;
7> }
using target database control file instead of recovery catalog
allocated channel: dd0
channel dd0: SID=367 device type=SBT_TAPE
channel dd0: Data Domain Boost API

sent command to channel: dd0

released channel: dd0

RMAN> 
RMAN> **end-of-file**

If we check the $ORACLE_HOME/config directory we should see the files have been completely regenerated.

Now try the backup again and it should complete successfully.

With thanks to Diana Yang for her assistance with this issue.