Hello,
your db2diag.log shows a return code of 106.
This is a permission denied which may have to do
with the error log file permissions.
See this solution here for details on this :
http://www-1.ibm.com/support/docview.wss?uid=swg21385178
Hello,
yes, this is a defect described by apar IC33455.
This apar is fixed in the 4.2.2.5 level of the TSM server
which is already available on our ftp site.
This apar will also be fixed in the TSM 5.1 level
in a patch to be made available shortly also on ftp site.
Hello Ken,
I believe you are suffering from a known defect identified by IC32636.
This apar describes a problem with the client having problems
backing system files if the root drive is other than C:.
Per your note below, it appears the boot drive is M:. This is why
the client works fine if you
Hello Matt,
remove the -TAB and use -DISPLAY=LIST instead.
I believe this is what you are looking for.
-
Rejean Larivee
IBM TSM/ADSM Level 2 Support
MC Matt Cooper
(2838)
Hello Rene,
with your level of server client, you should be fine.
However, the syntax of the include statement needs to
be corrected. You are missing the all keyword, i.e,
INCLUDE.SYSTEMOBJECTS ALL class_name
That should work.
Regards,
Hello,
this is a known problem with the 3.7.3.0 server.
This is known as apar IC27060. You should at the
very least upgrade your server to 3.7.5.0.
This is available here :
ftp://service.boulder.ibm.com/storage/tivoli-storage-management/maintenance/server/v3r7/AIX/LATEST/
That should fix it.
Hello,
there is an open apar that addresses your situation.
This is apar PQ55669. The problem is that there may be
orphan entries in a TSM table in the db that prevents
the volume from being acessed again until the server
is restarted. There is no fix for this yet.
Regards,
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
On Thu, 3 May 2001, Rejean Larivee/Quebec/IBM wrote:
Hello John,
I have worked with one customer getting the same
behaviour on restore, even with the 0C1 microcode
applied. Small bursts of files being restored at a time.
We have captured TSM and Atape traces
information.
Regards,
-
Rejean Larivee / IBM
TSM/ADSM Level 2 Support
- Forwarded by Rejean Larivee/Quebec/IBM on 05/08/01 06:24 PM -
Rejean
Larivee/Quebec To: [EMAIL
Hello John,
I have worked with one customer getting the same
behaviour on restore, even with the 0C1 microcode
applied. Small bursts of files being restored at a time.
We have captured TSM and Atape traces and found
TSM to be waiting for LOCATE commands to complete.
We found this to be an LTO
Hello,
your adapter needs to be configured as "fcs0" device
for it to work with the TSM smit menus.
Since your adapter is defined as an lpfc0 device, this tells
me that you have loaded the "emulex" device driver.
The Emulex device driver corresponds to the following filesets :
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Rejean Larivee/Quebec/IBM
Sent: Thursday, November 16, 2000 7:42 AM
To: [EMAIL PROTECTED]
Subject: Re: Partition a 3494
Hello,
indeed, with TSM 4.1, you can share a 3494 library
with the 3494SHARED se
Hello,
indeed, with TSM 4.1, you can share a 3494 library
with the 3494SHARED server option. However, you
still need to "logically" partition the 3494 by making sure
to use separate categories for scratch and private
volume between the different servers.
Have a great day !
13 matches
Mail list logo
