http://www-1.ibm.com/support/docview.wss?rs=663&context=SSGSG7&q1=insert
ing+row+in+table+%22Object.Ids%22&uid=swg1IC47516&loc=en_US&cs=utf-8&lan
g=en
//Henrik
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Nielsen, Bo
Sent: den 22 januari 2006 23
Hi,
Paul Zarnowski schrieb:
TSM does not do round-robin allocation
of DB pages across it's volumes. It fills up one, then works on the
next.
Are you shure? I think this only applies to log volumes.
--
Viele Gruesse,
Dirk Kastens
Universitaet Osnabrueck, Rechenzentrum (Computer Center)
Albre
Same applies for "Enter your user id:" prompt, backspace behaves
differently than command line entering.
On 1/22/06, Jurjen Oskam <[EMAIL PROTECTED]> wrote:
> On Sat, Jan 21, 2006 at 02:16:07PM -0600, Mike wrote:
>
> > Have you tried changing your terminal emulation and the TERM variable?
>
> Yes,
Server: TSM 5.1.10.0 on AIX 5.2; client: TSM 5.1.7.0 on Windows 2003
I'm trying to understand what the client is reporting in the session
summary when it reports:
"01/23/2006 08:20:23 ANE4958I (Session: 47866, Node: ILOX-FS1) Total
number of objects updated:673,012"
I've checked the produ
Always first have a look at Richards fabulous TSM site:
http://people.bu.edu/rbs/ADSM.funcdir
Objects Updated "Total number of objects updated"
element in a backup statistics summary.
The Object
Tab,
They tell the following in the technote
http://www-1.ibm.com/support/docview.wss?rs=663&context=SSGSG7&q1=Total+number+objects+updated&uid=swg21154305&loc=en_US&cs=utf-8&lang=en
Updating-->. Indicates that only the file meta data is sent, if file attributes
change and not the data itself
Thomas,
Thanks very much. That is what I would expect given our work this
weekend.
And although I've checked Richard's site before, I simply forgot to check
it today. Monday morning and all that...
Tab
Thomas Rupp <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager"
01/23/2006 10:01
Tab - That's documented in the client manuals, under topic
"Displaying backup processing status ".
Richard Sims
Richard,
Thanks. I was searching for the message number because I was worring that
searching for "updating" would be like searching Google for "Windows".
In reality, when I searched the V 5.1 Windows client manual for "updating"
I got exactly 8 hits. The first hit was the reference cited by the
We are experiencing more and more logpin issue. we are running db=160GB & log
size=12GB. i t is not a particular client which will hung up the sessions. It
is at random we are on tsm 5.3.0.0 aix 5.3. ml 02
IS anybody out there experience similar issue ? What can be done to can a hung
sessio
Hi Everybody,
I have two instances of TSM 5.1.6 running on my AIX server . I added 1Gb of
physical memory and increased the bufpoolsize in both instances by 512Mb .
After the reboot, one instance came up fine and the other one complained about
not enough memory available . Why would it complain
Rich,
A bit of a wild guess, but is there enough swap space to host the increased
buffpoolsize.
I know that the buffpoolsize should remain in the physical memory. But if the
second instance starts up after adding some additional swap space, you know
that it was the bottleneck.
Will TSM its
Ashok -
Topic "Recovery Log pinning/pinned" in http://people.bu.edu/rbs/
ADSM.QuickFacts summarizes the issue and quotes IBM Technotes which
address remediation. The TSM Problem Determination Guide also has
notes on pinning/pinned.
Richard Sims
On Jan 23, 2006, at 3:30 PM, Vats.Ashok wrote:
Hi ,
Here is the error I saw when trying to start up my second instance :
Tivoli Storage Manager for AIX-RS/6000
Version 5, Release 1, Level 1.6
Licensed Materials - Property of IBM
5698-ISE (C) Copyright IBM Corporation 1999,
Rich -
Thanks for the actual error messages.
Whereas you are running AIX: The ANR0358E may be a consequence of
your static /etc/security/limits values for root (or whatever user
the instance is running under), and/or the shell Unix Resource Limits
in effect for that session when the server was s
At 06:56 AM 1/23/2006, Dirk Kastens wrote:
Paul Zarnowski schrieb:
TSM does not do round-robin allocation
of DB pages across it's volumes. It fills up one, then works on the
next.
Are you shure? I think this only applies to log volumes.
That's the way it was explained to me years ago. Easy
16 matches
Mail list logo
