cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

The transaction log for database 'WindchillDB' is full due to 'LOG_BACKUP'

Regular Member

The transaction log for database 'WindchillDB' is full due to 'LOG_BACKUP'

we just started everyone in our company with creo this monday.  its only mid day wednesday, and this is the error we are all getting.

The transaction log for database 'WindchillDB' is full due to 'LOG_BACKUP'.

what is the deal with this.  is there something we can do to prevent this from happening?  not sure what these log files are, and why they take up so much space.

7 REPLIES 7

Re: The transaction log for database 'WindchillDB' is full due to 'LOG_BACKUP'

What is your database engine, Oracle or SQL Server?

Check the log folder under the Windchill installation point on your server for excessively large files. Are you doing verbose logging?

Check the free space on the server drive that Windchill is installed on.

Check the free space of the cache folder drive on your local machines. Cache files need to be local and each user must have their own.

Re: The transaction log for database 'WindchillDB' is full due to 'LOG_BACKUP'

This is a common issue with Windchill with SQL Server. SQL Server database for Windchill is configured to be in full recovery mode to have a point in time recovery. This requires every transaction to be logged. Over the time the transaction log grows full and leaves Windchill system  in non-writable state.

To fix this what you can do is

  1. Take a full db backup followed by transaction log backup. I have attached a document which will guide you in this. You can also google to get some more guidance on this.
  2. A backup of the transaction log ships out logs from ldf.

Long term solution is to setup a backup of transaction log along with  database backup. This can be either through scripts or through SQL Sever Management Jobs. See the blog - http://solutioncenter.apexsql.com/how-to-create-a-sql-server-scheduled-backup/

Thank you,

Binesh Kumar

Barry Wehmiller

Re: The transaction log for database 'WindchillDB' is full due to 'LOG_BACKUP'

what is a good size for the server.  i think ours is 500g.  does it need to be bigger?

Re: The transaction log for database 'WindchillDB' is full due to 'LOG_BACKUP'

There is no straight answer for the sizing. It totally depends on how many users do you have and how much data you have/ you are planning to have.

Increasing the size of the server is not going to resolve the transaction log filling up, it is just going to delay it. The best fix is to create a backup script which periodically backs up the SQL Server along with transaction which will clear the transaction log off from the data files.

Thank you

Binesh Kumar

Barry Wehmiller

Re: The transaction log for database 'WindchillDB' is full due to 'LOG_BACKUP'

ahh.. thank you.  we just started our use of creo.  we have everything transfered over from Intralink,  is there a way to actually see how much data we have on the server? 

just the last 2 days, we had all our parts go from inwork state to release state.  thats multiple thousands of files.  wondering if each release, is a transaction, and, thats what filled it up so quick.

i will talk to our IT department, see if they can write a script as you say.

do you have any recommedations, on how often the backup runs, and clears the log files?  once a week?  once a day?

also, how often should i go delete the actual backups?  or, should those backups be placed on a different server? 

Re: The transaction log for database 'WindchillDB' is full due to 'LOG_BACKUP'

If you are talking about the number of CAD files in  Windchill, you can run database queries against epmdocument/epmdocumentmaster tables. You can create a  QML report to get this information - similar to the one here - https://www.ptcusercommunity.com/servlet/JiveServlet/download/2034-39509-197193-47739/EPM_DrawingRef...

Sure, a massive update on the database could be the reason for the issue which you have faced.

Daily Windchill Backup is always good, so even the worst case scenario you will be able to recover to a point within the last 24 hours. For transaction log, you can start with a monthly and if you spot transaction log issue,  you can increase the frequency.  The retention of backup depends on your business requirement and company's IT policy. It is always preferred to store the backups on different server / network share. You can directly give this location in your scripts.

Thank you

Binesh Kumar

Barry Wehmiller

Re: The transaction log for database 'WindchillDB' is full due to 'LOG_BACKUP'

We've recently migrated from Oracle to SQL Server.

The default Windchill database that gets created has a limit to the size of the log file, can you tell me why this is and why it is not set to unlimited.

Melissa Fischer