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.
| Author |
Topic |
|
Rivaldo
Starting Member
7 Posts |
 Posted - 2002-04-24 : 17:29:33
|
| I am having a problem with a schuduled job, the package is giving the following error:'The log file for database 'xxxxx' is full. Back up the transaction log for the database to free up some log space.'There are a couple of things that I tried already.1. I backed up the transaction log, but it gave me the following error "Cannot allow BACKUP LOG because file 'xxxx_dat' has been subjected to nonlogged updates and cannot be rolled forward."2. dump transaction xxxx with no_log. After that my transaction log had some free space, but the package was still not runnig.3. Finally I ready this from a forum article and tried it. "truncate on checkpoint" option on, shut down SQL Server, delete/rename the log file, the start SQL again. This usually does a good job in that it creates it's own new, smaller, log file. Just be sure to reset the truncate box. It created a new log file with the name xxxx_log.LDF. Package is still not running and I keep receiving the same error message.Any suggestions will be appreciated. |
|
|
YellowBug
Aged Yak Warrior
616 Posts |
Posted - 2002-04-25 : 08:13:50
|
| It sounds like your package maybe filling the transaction log.What are you doing in the package?Maybe try extending the size of the transaction log.Or running the package with/on a smaller subset of data. |
 |
|
|
rihardh
Constraint Violating Yak Guru
307 Posts |
Posted - 2002-04-25 : 10:24:05
|
| First you have to tell us what kind of job you are executing. If the package is transaction intensive it is possible that the log gets full as soon as you run the package (although I doubt it). If this is the case CHECK YOUR PACKAGE! Make sure that you allow the TL to grow and that you backup your TL frequently with truncation (use maintainance plan). Monitor the growing of your TL in a normal (application) enviroment, if everything is OK than you have a problem in your job (package). |
|
|
|
Rivaldo
Starting Member
7 Posts |
Posted - 2002-04-25 : 11:20:11
|
| Yesterday after I did all those procedures my log file had a size of 574KB, now today after trying to run the job again the size went up to 47MB.Rihardh, the job only transfers four tables from server to server, three tables are big and one small one. The TL is set to unlimited growth.The job was running smoothly, but all of sudden it started with the problems. I have a maintenance plan on both servers. I can transfer the tables manually one by one, but that defeats the purpose of the job. Thanks for your suggestions |
|
|
|
|
|
|
|
|
Transaction Log