Server: Msg 9002, Level 17, State 6, Line 1

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2000 Forums

SQL Server Administration (2000)

Server: Msg 9002, Level 17, State 6, Line 1

Author

Topic

venkath
Posting Yak Master

202 Posts

Posted - 2006-06-20 : 03:33:11

Hi all,

when i am trying to update a table in the database, i am getting the
following error
Server: Msg 9002, Level 17, State 6, Line 1
The log file for database 'A2PDD' is full. Back up the transaction log for the database to free up some log space.

could any one explain me the steps to resolve the above issue..

Help on this is greatly appreciated..

Thanks

jen
Master Smack Fu Yak Hacker

4110 Posts

Posted - 2006-06-20 : 03:47:51

like what the message says... backup the database, if this is in development environment, better change the recovery model to simple, after changing take a full backup of the database

if this is in production, take a full backup for now, then setup a routine job for daily backup, check Kristen's sticky post in the newbie forum

--------------------
keeping it simple...

venkath
Posting Yak Master

202 Posts

Posted - 2006-06-20 : 05:24:03

Hi jen.

But my log file properties were set as
Unlimiete File Growth
The drive in which the log files are stored has very littile unused
space..

Do i still need to take the backup of Log file..?

Thanks

jen
Master Smack Fu Yak Hacker

4110 Posts

Posted - 2006-06-20 : 05:39:44

to immediately resolve your problem, do the backup

to troubleshoot why this is happening, determine the following:
how many percent is the file growth?
how much space is left on your drive?
how large is your log file now?

these type of messages usually pertain to server administration, like backups are regularly created for disaster recovery, database sizes are monitored making sure they don't run out of disk space preventing growth, etc

--------------------
keeping it simple...

kjmraohyd
Starting Member

34 Posts

Posted - 2006-06-20 : 08:11:52

Also Try the following commands.

backup log [databasename] with no_log
go

backup log [databasename] with truncate_only
go

dbcc shrinkfile(LogicalLogFilename,10)
go

Jaganmohan Rao

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources