The Transaction log for our OnBase SQL DB is full. ERROR[42000]. log_reuse_wait = 2, log_reuse_wait_desc = LOG_BACKUP.

[George_Cicarlan]

The Transaction log for our OnBase SQL DB is full. Every time my users try to log in they receive an ERROR[42000]. I ran a SQL query for the db and found out that the value for log_reuse_wait is 2, also for log_reuse_wait_desc the string is LOG_BACKUP. Cannot log into config or Unity with manager. My users can't do anything, we're stuck. How do I fix this problem? Thank you very much!

[Brad_Phillips · Accepted solution]

Dear George,

Do you know if your database is running in Simple recovery model or Full recovery model?  You can find this out by opening management studio and right clicking on the database itself, and look at it's options under properties.  If it's in a Full recovery model, it probably hasn't taken a transaction log backup in a while.  If it's in Simple recovery model, you may have run out of space on the disk or you hit the maximum size set for the transaction log file.

A situation like this would be best handled by your DBA.  However, if you don't have one, and all the above sounds obscure to you, it would be best to open a support issue with your first line of support and they should get you the help you need.  Our Tech Support team can respond to you faster than the forums.

Hope this helps!
Brad

[George_Cicarlan]

Brad,
Thank you very much for your response. I have already contacted our OnBase solution technicians(no response yet) and our DBA(no response).
As per your question, recovery_model = 1; recovery_model_desc = FULL
based on this it looks like it is running in Full Recovery.

I will take your advice and have our DBA look at it, it is just inconvenient because my users are just stuck on doing nothing. 😕
Thank you again! I really appreciate it!

[George_Cicarlan]

Our Solution Technician called, the problem was on the SQL server, we ran out of space, so all we had to do is increase the storrage. I will get back after I do this,

[George_Cicarlan]

Increasing the size on the SQL db drive solved the problem. I hope this will help others in the same situation.

Thank you!