On Jun 18, 2010, at 10:47 AM, zia4u2 wrote:
> Hi Brenda,
> I am facing the same issue of yours for db2 online restore.
The posting referred to a February 2009 discussion where no resolution was
posted, and no feedback regarding a suggestion to review the DB2 logs.
A classic cause of a large res
Hi Brenda,
I am facing the same issue of yours for db2 online restore.
Can you please give me the solution to this problem on how did you resolve it ?
Thanks in advance
Cheers,
Zia
bcollins wrote:
> Hi everyone!
>
> I have a client that can not resore a DB2 database. It does backup fine but
>
>> On Mon, 2 Feb 2009 21:21:36 -0500, Richard Sims said:
> The symptoms seem like something in the network layer, as though the
> faucet were shut because something thought that was enough data
> already through that single session (service throttling). You might
> try an artificial FTP of an eq
Brenda -
Thanks for the helpful extra info.
The TSM server messages indicate that it was attempting to send data
to the client - corroborated by the SendW condition you reported.
The DB2 log indicates that app trying to get data, and "problem
reading from vendor device", which resolves to the TS
What does DB2 logs show during the restore
--Original Message--
From: Collins, Brenda
Sender: ADSM: Dist Stor Manager
To: ADSM-L@VM.MARIST.EDU
ReplyTo: ADSM: Dist Stor Manager
Subject: [ADSM-L] Client in SENDW state
Sent: Feb 2, 2009 15:57
Hi everyone!
I have a client that can not resore
Hi everyone!
I have a client that can not resore a DB2 database. It does backup fine but
when restoring, it restores a certain amount of data and then goes into a
'sendw' state. After about 9 - 10 min., the client terminates the session with
TSM.
TSM Server - 5.5.1.1
Client 5.4.0.0
DB2 B
