TDP for Oracle error – SBT error = 7011, errno = 106, sbtopen: system error

Today, for the first time,  I configured TDP (Tivoli Data Protect) for Oracle on Linux .  I had already have done this many times before on AIX.  The Linux version requires less operating system configuration then AIX.

My Linux admin installed the TDP client version 6.3.  After he was done, I verified his handy work, and found that he followed the instructions from IBM to the letter.  He is usually very through.

Then I finished by configuring RMAN to use TDP.  Next in RMAN, I attempted a backup. It failed with a similar error I get when I run TDP for Oracle on AIX for the first time.  So out came my AIX notes on TDP installation.  I found that the error for Linux is almost identical to the error I used to get when I run TDP on AIX for the first time.

Oracle TDP error

SBT error = 7011 error for TDP for Oracle

RMAN> backup database;

Starting backup at 17-DEC-12

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

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

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

RMAN-03002: failure of backup command at 12/17/2012 15:04:20

ORA-19554: error allocating device, device type: SBT_TAPE, device name:

ORA-27000: skgfqsbi: failed to initialize storage subsystem (SBT) layer

Linux-x86_64 Error: 106: Transport endpoint is already connected

Additional information: 7011

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

SBT error = 7011, errno = 106, sbtopen: system error



The problem for both AIX & Linux is that the TDP client can not write to the tdpoerror.log file.  When TDP is install, the person doing this is usually logged in as root or a super user, and the directory the log is stored is under the installer’s account name.


Change the permission on the file tdpoerror.log or its directory to allow the user ‘oracle’ to write to the error log.


  1. In the TDP for Oracle configuration file: ‘tdpo.opt’, find the parameter DSMI_LOG for the log file location.

Default location for tdpo.opt:


In the tdpo.opt file find the parameter: DSMI_LOG

Example:  DSMI_LOG           /var/logs/oracle/tdp

2.  Check the permissions of the DSMI_LOG location:

Example: in folder in /var/logs/oracle I found that it looked like below
drwxr-xr-x 2 root   root      4096 Nov 30 10:33 tdp

Note:  the owner of the folder is root without write permission to the directory

3.  In the tdp folder, check the permissions tdpoerror.log

I found that it looked like below:
-rw-r–r– 1 root root 2012 Nov 30 10:46 tdpoerror.log

Again the log file was owned by root, and could not be written to.

4.  Fixing the permissions:

As either root or some super user on the operating system, run the two commands below:

chown oracle:dba /var/logs/oracle/tdp

chown oracle:dba /var/logs/oracle/tdp/tdpoerror.log

Then I was able to run a successful backup in RMAN.



The only difference from Linux above was the default location of the tdpo.opt file.


Now back to testing my backups & restores in Oracle on Linux.


Leave a Comment