M2M Database Transaction Log Full

[bar...@wilsonindustries.com]

Hi,
I am getting the following red box error:
***
Error 1526:
Connectivity error:[Microsoft} [ODBC SQL Server Driver] The log file for 'm2mdata03'is full. Back up the transaction log for the database to free up some log space.
***
We are unable to add any new data to M2M. The file: m2mdata03_LOG.LDF has 22,180,096 KB.

We backed up our system on Friday and could not add any new data yesterday. We have never gotten this error before. How do I back this up? Do I just create a "copy" of the above file and call it m2mdata03_LOG.old.LDF and then delete all of the data on the current file? How do I access it?

Thanks for any help because we are at a standstill and are near emergency situation!

Barbara Case
Wilson Industries

[RajW]

Hi Barara. Hopefully you're in contact with M2M on this. But I guess
I would try to remove the file from that directory, reboot the server,
and see what happens.

Let us know how it goes.

Good luck!
Raj

[bar...@wilsonindustries.com]

Wilson no longer has M2M Support.

------Original Mail------
From: "RajW" <raj...@gmail.com>
To: "Los Angeles Area Made2Manage User Group" <lam2m...@googlegroups.com>
Sent: Tue, 16 Oct 2007 17:56:00 -0000
Subject: [lam2musers] Re: M2M Database Transaction Log Full

[Julie]

Hi Barbara,

 

Not sure if this will help, but this is what was on the M2M ASK EXPERT Web site regarding Transaction Logging.

 

 

Article Id:	021571 (Last Modified 1/3/2007 5:22:25 PM)
Issue:	When should I use transaction logging?
Applicable Version(s)*:	3.2 VFP, 3.5 VFP, 3.6 VFP
Applicable Screen Id(s):

 

Using transaction logging Simply stated, transaction logging means that you have instructed Made2Manage to make a separate copy of all modifications to your Made2Manage data, in a journal that can be maintained on separate media. This journal can be used to reconstruct your data in the event that your primary database becomes unusable for any reason. Since transaction logging includes any modifications to your Made2Manage data, it can also be used as a log to monitor user activity. This can help Made2Manage Support track down unexplained changes to your data, or help them understand what activities might have been performed which could be contributing to a recurring error condition. In order to enable transaction logging for your company: 1. Go to the Company Information ( COMP ) window (path: Utilities | Company Setup | Company Information)and on the Preferences tab, check the box that is titled transaction logging. 2. Below the check box, you will see a text box where you can the path to your transaction log file. It is recommended that you put in a location for the transaction log which is on a different disk drive than your primary Made2Manage data. This will ensure that if you suffer from a disk drive crash, the transaction log will still be available and can be used along with your most recent back-up to restore your data. 3. Click Save. Once you have checked this box and identified the location of your log data, Made2Manage will begin to record all database changes to a second redundant location. (the one you specified as the location for your log files). Should you encounter a disk drive crash or other major interruption you can restore your back-up file from your most recent back-up and then tell Made2Manage to re-apply all of the transaction that have been recorded in the transaction log. This will ensure that you do not encounter any lost transactions other than perhaps the last transaction that was underway at the time of the crash. As you can imagine this can result in substantial timesaving and eliminate the need to try to reconstruct lost data in the event of a crash. Because of this usage, it is important that each night when you make a back up that you reset the log file so that you do not redundantly store information in the log file that you have already backed up onto your main Made2Manage backup. In the Made2Manage backup window there is a check box which can be checked to tell Made2Manage to reset the log file at the time of these backups. If you are not using the Made2Manage backup utility, you can reset the log file by simply deleting all files in the log directory you specified on the COMP window.. Many companies choose to back-up the log file along with the data that they are backing up so that they can reconstruct logs back several days. It is important to note that because Made2Manage is now writing a transaction both to its original location database and also to the log file, there is some additional performance burden that is placed upon the system. Most users who have tried transaction logging have reported that the additional performance burden is not noticeable to users, however, we recommend that you evaluate this within your site to determine its impact. Should the need arise to recover a database and reapply the transaction log you can do so from the Recover Database ( RECOV ) window. When you go to this window you can view all of the transactions in the log file along with the transaction ID, table affected, date, time, user who performed the change, type of change, and more. You will need to hit the button entitled "gather" on the recovery window in order for Made2Manage to collect the information in the form suitable for viewing. Should you have any additional questions regarding the uses of transaction logging within Made2Manage please contact your support representative. In summary, you should use transaction logging if any of the following apply to you: Your network is new or unstable and you wish to minimize the chance for data disruption. 2. You wish to monitor user activity. 3. You want extra protection against business disruption.     Julie A. Gomez W.A. Benjamin Electric Co.

[Julie]

If you are using SQL, here is the M2M Expert response as well – GOOD LUCK!

 

Julie A. Gomez

W.A. Benjamin Electric Co.

****************************************************************************

 

 

Article Id:	022246 (Last Modified 8/23/2006 5:27:15 PM)
Issue:	Shrinking the Transaction Log in SQL Server 2000 with DBCC SHRINKFILE
Applicable Version(s)*:
Applicable Screen Id(s):

 

How to shrink the Transaction Log in SQL Server 2000 with DBCC SHRINKFILE The information in this article applies to: Microsoft SQL Server 2000 (all editions) Shrinking the log in SQL Server 2000 is no longer a deferred operation. A shrink operation attempts to shrink the file immediately. However, in some circumstances it may be necessary to perform additional actions before the log file is shrunk to the desired size. When DBCC SHRINKFILE is run, SQL Server 2000 shrinks the log file by removing as many virtual log files as it can to attempt to reach the target size. If the target file size is not reached, SQL Server places dummy log entries in the last virtual log file until the virtual log is filled and moves the head of the log to the beginning of the file. The following actions are then required to complete the shrinking of the transaction log: You must run a BACKUP LOG statement to free up space by removing the inactive portion of the log. You must run DBCC SHRINKFILE again with the desired target size until the log file shrinks to the target size. The following example demonstrates this with the pubs database and attempts to shrink the pubs_log file to 2 MB: Run this code: DBCC SHRINKFILE(pubs_log, 2) NOTE: If the target size is not reached, proceed to the next step. Run this code if you want to truncate the transaction log and not keep a backup of the transaction log. Truncate_only invalidates your transaction log backup sequence. Take a full backup of your database after you perform backup log with truncate_only: BACKUP LOG pubs WITH TRUNCATE_ONLY -or- Run this code if you want to keep a backup of your transaction log and keep your transaction log backup sequence intact. See SQL Server Books Online topic "BACKUP" for more information: BACKUP LOG pubs TO pubslogbackup Run this code: DBCC SHRINKFILE(pubs_log,2) The transaction log has now been shrunk to the target size. REFERENCES For more information, see the Shrinking the Transaction Log and DBCC SHRINKFILE topics in SQL Server 2000 Books Online. Q256650 INF: How to Shrink the SQL Server Transaction Log. To locate it, search for the article number on the Microsoft.com web site. Tips to Reduce the Size of the SQL Transaction Log This taks should be performed only by a qualified SQL administrator. It is not part of the standard Made2Manage Support contract. If you would like further assistance, our network consulting group can help you for an additional charge. 1. To minimize the file you will need to clear space on the server. 2. Do a back up of the transaction log. This will reset the check point. If it does not reduce the size continue with the following. 3. Set the transaction log to simple and do a shrink db. 4. Reset the transaction log to full.

 

 

-----Original Message-----
From: lam2m...@googlegroups.com [mailto:lam2m...@googlegroups.com] On Behalf Of bar...@wilsonindustries.com
Sent: Tuesday, October 16, 2007 9:21 AM
To: lam2m...@googlegroups.com
Subject: [lam2musers] M2M Database Transaction Log Full

 

 

Hi,

[Barbara-Wilson Ind]

Thanks so much. It is working again!!!

 

Barbara Case

Founder &  President

Compassion In Action - USA

(909) 629-5746

www.compassioninaction.us