ADSM-L

Re: SQL TDP - Server out of data storage space - Solved

2003-05-08 00:43:44
Subject: Re: SQL TDP - Server out of data storage space - Solved
From: Alexander Verkooijen <alexander AT SARA DOT NL>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 8 May 2003 06:42:03 +0200
Thanks to everybody who responded.
Setting DIFFESTIMATE to 100 solved
our problem.

Thanks again,

Alexander

> -----Original Message-----
> From: Del Hoobler [mailto:hoobler AT US.IBM DOT COM] 
> Sent: vrijdag 2 mei 2003 15:09
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: SQL TDP - Server out of data storage space
> 
> 
> Alexander,
> 
> Take a look at the following options:
> 
>    /LOGESTimate=numpercent
> 
>    /DIFFESTimate=numpercent
> 
> They are in the User's Guide.
> In some sitautions, the intial size estimate that the
> SQL server tells DP for SQL is too low.
> The User's Guide discusses those details.
> 
> Thanks,
> 
> Del
> 
> ----------------------------------------------------
> 
> > (Server 5.1.6.4 on AIX 4.3.3, SQL TDP 2.2 (not completely sure) on
> > WinNT, 5.1.5.0 TSM client)
> >
> > I have a TDP for MS SQL that can't complete it's backup:
> > Full: 0   Read: 411059712  Written: 411059712  Rate: 5,901.75 Kb/Sec
> > Full: 0   Read: 411059712  Written: 411059712  Rate: 5,816.24 Kb/Sec
> > Full: 0   Read: 411059712  Written: 411059712  Rate: 5,733.18 Kb/Sec
> > Full: 0   Read: 411059712  Written: 411059712  Rate: 5,652.45 Kb/Sec
> > Full: 0   Read: 411059712  Written: 411059712  Rate: 5,652.37 Kb/Sec
> > Backup of AwareUtrechttest failed.
> > ANS1311E (RC11)   Server out of data storage space
> >
> > The activity log on the server agrees with the client:
> > 04/29/03   04:18:50  ANR0534W Transaction failed for 
> session 9796 for
> > node
> >                       IF_SQL1 (TDP MSSQL) - size estimate 
> exceeded and
> > server
> >                       is unable to obtain additional space 
> in storage
> > pool
> >                       IFDISKPOOL.
> > My first thought was that the client was trying to send 
> data that grew
> > during compression because that usually produces this error message.
> 

<Prev in Thread] Current Thread [Next in Thread>