Skip to main content
D
dgrobe1-Visitor
1-Visitor
November 18, 2015
Question

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

  • November 18, 2015
  • 3 replies
  • 7113 views

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.

    3 replies

    B
    23-Emerald III
    BenLoosli23-Emerald III
    23-Emerald III
    November 18, 2015

    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.

    B
    BineshKumar11-Visitor
    1-Visitor
    November 19, 2015

    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

      D
      dgrobe1-VisitorAuthor
      1-Visitor
      November 19, 2015

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

      B
      BineshKumar11-Visitor
      1-Visitor
      November 19, 2015

      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

      M
      mfischer-41-Visitor
      1-Visitor
      January 14, 2016

      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

      Terms & ConditionsAccessibility statement