September 25, 2008 at 1:07 am
Hi all,
I got the following error message while running an application that uses SQLdb.
DBSPI-3266.1: # of transaction log expansions for NIManagementDB (6.00) too high (>=4.00) for
I tried to understand what it is, but I would appreciate if anyone can give me a better explanation.
Thanks indeed for your help
Niyala
September 25, 2008 at 1:52 am
I would start by checking the status of transaction log for NIManagementDB database.
Is it set for autogrowth?... in the affirmative case, in the growth % or size something reasonable or is it set to a ridiculous low value like 1% or 1 Meg?
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.September 25, 2008 at 5:01 am
Is seems that NIManagementDB is watching your transactionlogfile and registers when this file needs to expand. If this file expands > 4 times in an hour(?), it's complaining (This is not a SQL error). As mentioned by Paul, change the loggrowth.
Also make sure autoshrink is disabled for that specific database (although autoshrink is not recommended at all), otherwise you'll get the situation of shrinking and growing which is causing a lot of CPU and IO overhead and fragmentation
Wilfred
The best things in life are the simple things
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply