Re: [ADSM-L] TDPO RMAN problems

We ran into something similar yesterday.

The DBA tracked down and fixed the permissions on the log file, and we
were still seeing trouble.

A helpful command to issue to check is the "tdpoconf shownenv" which
sits in the bin64 directory. In our case, tdpooconf showed we were also
missing the agent.lic file. (I suspect the DBAs did a virgin install
with the upgrade fileset from the FTP site instead of getting the client
off the passport site.)

Since we had other systems configured with the same levels of code, we
ftp'd the missing agent.lic file from one of them.

[RC]

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
De Gasperis, Mike
Sent: Wednesday, February 11, 2009 6:08 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TDPO RMAN problems

Found this old posting from Richard, sounds like you just need to update
your permissions so you can write to the dsmerrorlog/schedlog

Goran - See that msg in the TSM Wiki or ADSM QuickFacts.

The 106 should be API error DSM_RC_ACCESS_DENIED, meaning denied due to
improper permission.

   Richard Sims


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Allan Mills
Sent: Wednesday, February 11, 2009 8:48 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TDPO RMAN problems

Have just installed TDPO 5.3.3 64bit  on solaris 8 64bit with oracle
9.2.0.4
This is part of a enterprise wide migration from NetBackup to TSM


everything appeared to install ok,
relinked the libobk.so as per manual

running the following test script gives the output below

cat y.y


rman nocatalog <<-ENDRMAN
        connect target /
        run {
                allocate channel d1 type 'sbt_tape' parms
'ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/netdev2.opt)';
                sql 'alter system archive log current'; } exit ENDRMAN

=============================================================

RMAN>
connected to target database: NETXXXX (DBID=2912724135) using target
database controlfile instead of recovery catalog

RMAN> 2> 3> 4>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of allocate command on d1 channel at 02/12/2009
12:11:52
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27000: skgfqsbi: failed to initialize storage subsystem (SBT) layer
SVR4 Error: 106: Error 106
Additional information: 7011
ORA-19511: Error received from media manager layer, error text:
   SBT error = 7011, errno = 106, sbtopen: system error

RMAN>

Have checked and ensured Servername,Nodename etc correct accross all
dsm.opt, dsm.sys tdpo.opt Have ensured all these files are readable by
oracle user, as well as tdpo.password file

NOTE:
as soon as we reverse the link to the netbackup libobk.so it works again
for netbackup


Regards,
Allan

Allan Mills
Technology Operations
02 8835 8035
0422 208 031
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _

The information contained in this email is intended for the named
recipient(s)
only. It may contain private, confidential, copyright or legally
privileged information.  If you are not the intended recipient or you
have received this email by mistake, please reply to the author and
delete this email immediately.
You must not copy, print, forward or distribute this email, nor place
reliance on its contents. This email and any attachment have been virus
scanned.
However,
you are requested to conduct a virus scan as well.  No liability is
accepted for any loss or damage resulting from a computer virus, or
resulting from a delay or defect in transmission of this email or any
attached file. This email does not constitute a representation by the
NSW Police Force unless the author is legally entitled to do so.


DISCLAIMER:
This message is intended for the sole use of the addressee, and may contain 
information that is privileged, confidential and exempt from disclosure under 
applicable law. If you are not the addressee you are hereby notified that you 
may not use, copy, disclose, or distribute to anyone the message or any 
information contained in the message. If you have received this message in 
error, please immediately advise the sender by reply email and delete this 
message.