|
Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code
2011-04-17 04:47:06
Nancy
Not a fix for your problem, but I'd strongly urge you to reduce your log
from the 13GB max to maybe 12GB - reason being is that if you do hit the
situation where the log gets to 100% and the instance stops, the only way
to get it back is to do an emegency log growth. If your already at the
maximum, you will be stuck.
Steven
On Apr 17, 2011 4:41am, Nancy L Leugemors <Leugemors.Nancy AT healthnow DOT org>
wrote:
fit? Our recovery log has always been set to 13GB so I can't expand it>
anymore. Running a database backup doesn't free any space while the
|
|
|
