Partially clearing out the log data

KB Home   |   Partially clearing out the log data

Main.PartiallyClearingLogData History

Hide minor edits - Show changes to output

Changed line 13 from:
!!! I am seeing the error shown below when trying to delete old logs. What can I do about it?
to:
Q: I am seeing the error shown below when trying to delete old logs. What can I do about it?
Changed lines 14-15 from:
@@Error occurred running db-tools, command: delete-old-logs. GC overhead limit exceeded@@
to:
[@ Error occurred running db-tools, command:
 
delete-old-logs. GC overhead limit exceeded @]
March 30, 2018, at 01:37 PM by Priyanka - Added information about a error that can appear when using db tools to delete old logs
Added lines 12-25:

!!! I am seeing the error shown below when trying to delete old logs. What can I do about it?
@@Error occurred running db-tools, command: delete-old-logs. GC overhead limit exceeded@@

We have seen this error at a few busy sites. (Sites printing couple of thousands of pages every day) By default, db-tools application uses 256M of memory which can be increased by making the following changes.

# Open db-tools file using a text editor.
# Find the line  @@[=Xmx256M=]@@
# Try adding more amount by doubling it. E.g. @@[=Xmx512M=]@@
# Save the file.
# Test it if that works and change the memory parameter accordingly to your needs.

Hopefully, this should resolve the issue. If you still see issue, please contact [[https://www.papercut.com/support/|support]]. If you can include the Application server [[https://www.papercut.com/kb/Main/HowToEnableDebugInNG|logs]], that would be super helpful. 

July 29, 2011, at 11:59 AM by 50.53.10.116 -
Changed lines 11-13 from:
In line with print management best practice, PaperCut recommends that all sites keep print log data as long as possible.  Historical print usage data allows organizations to look at printing trends and conduct audits over long periods of time.  PaperCut is designed in a way where large databases with historical log data will now slow down day-to-day use of the system.

to:
In line with print management best practice, PaperCut recommends that all sites keep print log data as long as possible.  Historical print usage data allows organizations to look at printing trends and conduct audits over long periods of time.  PaperCut is designed in a way where large databases with historical log data will not slow down day-to-day use of the system.

Changed lines 46-49 from:
''Categories:'' [[!Administration]]
to:
''Categories:'' [[!Administration]]

----
[-Keywords: clear, remove, purge, data, logs, history  -
]
Changed lines 5-6 from:
A:  PaperCut NG has unlimited log sizes and has a smart log rotation procedure for text based system and print logs.  Rotation is not usually required as disks are so large these days.  You can however configure the system to delete older data either:
to:
A:  PaperCut has unlimited log sizes and has a smart log rotation procedure for text based system and print logs.  Rotation is not usually required as disks are so large these days.  You can however configure the system to delete older data either:
Changed lines 11-13 from:
to:
In line with print management best practice, PaperCut recommends that all sites keep print log data as long as possible.  Historical print usage data allows organizations to look at printing trends and conduct audits over long periods of time.  PaperCut is designed in a way where large databases with historical log data will now slow down day-to-day use of the system.

Changed lines 19-20 from:
''NOTE:'' This information applies to PaperCut Quota only.
to:
''NOTE:'' This information applies to PaperCut Quota only (versions prior to version 6).
Changed lines 9-11 from:
* '''Manually''' using the command-line option [@db-tools delete-old-log-data@] as explained in detail in [[https://www.papercut.com/products/ng/manual/apdx-tools-db-tools.html|Appendix A]].  A value of [@0@] will delete all logs from today onwards.

to:
* '''Manually''' using the command-line option [@db-tools delete-old-logs@] as explained in detail in [[https://www.papercut.com/products/ng/manual/apdx-tools-db-tools.html|Appendix A]].  A value of [@0@] will delete all logs from today onwards.

Changed lines 17-18 from:
'''NOTE: This information applies to PaperCut Quota only.
to:
''NOTE:'' This information applies to PaperCut Quota only.
Added lines 12-13:
[-keywords: clearing logs, clear database, rotate log data-]
Changed lines 3-4 from:
'''NOTE: This article applies to PaperCut Quota.''' PaperCut NG has unlimited log sizes and has a smart log rotation procedure for text based system and print logs.
to:
Q:  We are a school who have been running PaperCut for approximately one year.  We would like to clear out the database of print jobs prior to this school year. How do I perform a partial clear?

A:  PaperCut NG has unlimited log sizes and has a smart log rotation procedure for text based system and print logs.  Rotation is not usually required as disks are so large these days.  You can however configure the system to delete older data either:

* '''Automatically''' via the options under ''Options -> Backup -> Delete old log data''

* '''Manually''' using the command-line option [@db-tools delete-old-log-data@] as explained in detail in [[https://www.papercut.com/products/ng/manual/apdx-tools-db-tools.html|Appendix A]].  A value of [@0@] will delete all logs from today onwards.


-----
!!Legacy Information for PaperCut Quota

'''NOTE: This information applies to PaperCut Quota only.

Deleted lines 2-3:
''Categories:'' [[!Administration]]
Added lines 29-30:

''Categories:'' [[!Administration]]
Added lines 1-4:
(:title Partially clearing out the log data:)

''Categories:'' [[!Administration]]

Changed line 1 from:
'''NOTE: This article applies to PaperCut Quota'''
to:
'''NOTE: This article applies to PaperCut Quota.''' PaperCut NG has unlimited log sizes and has a smart log rotation procedure for text based system and print logs.
Added lines 1-2:
'''NOTE: This article applies to PaperCut Quota'''
Changed line 11 from:
--->@@C:\Program Files\PaperCut\Logs\PrintJobLog.mdb@@
to:
--->@@C:\Program Files\PaperCut\Logs\[=PrintJobLog.mdb=]@@
Changed lines 1-24 from:
Describe PartiallyClearingLogData here.
to:
Q: We are a school who have been running PaperCut for approximately one year.  We would like to clear out the database of print jobs prior to this school year. How do I perform a partial clear?

A: This is possible via a manual procedure.  Fortunately PaperCut uses the Microsoft Access file format for logs, so it is possible to manipulate the data directly.  This process will require a copy of Microsoft Access 2000 or higher.

-->'''1)''' Ensure PaperCut is closed and the ''PaperCut Print Charging'' service listed under ''Start->Settings->Control Panel->Services'' is Stopped.

-->'''2)''' As a first step, backup the ''[=PrintJobLog.mdb=]'' file located in the PaperCut ''Logs'' by taking a copy and placing it the PaperCut backup's directory:
--->@@C:\Program Files\PaperCut\Backups@@

-->'''3)''' Copy the file:
--->@@C:\Program Files\PaperCut\Logs\PrintJobLog.mdb@@
-->located in the PaperCut "logs" directory file to a location accessible by a copy of MS Access (e.g. maybe from the print server to a desktop workstation).

-->'''4)''' Open the file within MS Access.

-->'''5)''' Navigate to the ''Tables'' section and open the ''[=JobLog=]'' table.

-->'''6)''' Use standard Windows "shift select" to select the multiple rows to be deleted.  All log entries will be listed in date order by default.  Press the delete button to remove the rows.

-->'''7)''' Confirm the delete operation and close Microsoft Access.

-->'''8)''' Copy the edited ''[=PrintJobLog.mdb=]'' back to the server replacing the existing one copied in step 3.

-->'''9)''' Restart the ''PaperCut Print Charging Service'' and test.

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on March 30, 2018, at 04:34 PM
Printable View   |   Article History   |   Edit Article