Jump to content

Recommended Posts

Posted (edited)

Hi All

Tried to apply the summer 24 update but it keeps failing due to the SQL sims.ldf growing way beyond it limits. Original set to Growth +10% and unlimited Max, it is now set 45GB growth and unlimited Max size and still fails. Iv never seen a log file grow so much. I am now expanding the log file to 90GB growth.

Due to it being weekend my sims support provider is not available

 

This is part of the agent log before it failed and rolled back

 

/***********************************sims.att_covid19_mapping_codes_history*****************************************************************/

#REDACTED# SQL CODE

/*******************************************************************************************************************************************/

-- reset the recovery mode back as it was

#REDACTED#

/*******************************************************************************************************************************************/

- Package: 33e70998-3196-407e-b370-6dd981e26b6d

#REDACTED#|13/07/2024 21:02:31|PackageRunner: Install failed. Exception: Sims.Solus3.Agent.PackageDeployer.TaskException: Execution of task c11c3391-4ecb-4951-b56e-ba8afa8289c6 failed. ---> System.Data.SqlClient.SqlException: Could not allocate a new page for database 'SIMS' because of insufficient disk space in filegroup 'PRIMARY'. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.

DBCC execution completed. If DBCC printed error messages, contact your system administrator.

Anyone with any advice if there is a better way of doing what i am doing by stepping up log file growth size. Surely given enough eventually it will complete

Thanks

Paul

Edited by dapaulio
Posted

What version of SQL are you running. I was advised that there would be an issue if I wasn't on at least (I think 2016 SP2). Support are upgrading the SQL server before I run the update next week.

I wonder if this is the issue they were referring to...

Posted (edited)

I've just looked up the technical bulletin LCC posted out to us...

 

 

"Only Microsoft SQL Server 2016 (Service Pack 3 – version 13.0.6300.2) and Microsoft SQL Server 2019 (RTM-CU19 – version 15.0.4223.1) will be supported by ESS after the Summer 2024 SIMS upgrade."

 

As you're 2016 SP2, this may be the problem, it may not be the direct cause, but worth looking in to...

Edited by smithson83
Posted

Bad news im afraid it doesnt seem to have resolved my issue however there were references to shrinking the log file in the script following updating to SP3. so you could be on to something.

I have given up. Database rollback successfully and sims is still accessible however a note that the SQL database gets stuck in restricted mode after the rollback which in experience locks out all non power users.

 

if this happens tro you check

refresh sql management studio and expand the databases. if it has written restricted Mode next to the database SIMS, then

Right click SIMS Database

Properties

Options

Scroll down to the bottom

change restricted mode to multi user.

 

This will allow everyone back in to sims

 

I have a support call open with my sims support provider now, so i will update this thread when its fixed

Thanks for your help

  • Thanks 2
Posted

Always used to have issues with file sizes, and particularly the log file. What are you based mdf and ldf file sizes before you start? You might need to truncate the log file to begin with. Is there enough spare room to have a +90GB growth?

 

There are commands that can truncate the log file, I believe some LA backup programs would also do this routinely, or you can switch the backup mode to simple, and then back to full. Of course, make sure the whole server is fully backed up / snapshotted before making any changes. If in doubt wait for your support team to confirm. Getting stuck in restricted mode, sounds like it's not even exitting properly, which is a worry.

Posted (edited)

So summarising this was due to sims being installed on sql express. The database reached its 10gb limit and crashed out.

 

The configuration was inherited by the last people who supported the school. Personally I’d never consider putting a secondary school on sql express. It barely coped in a primary environment

 

Upgraded sql, upgrade sims no problems after that.

Edited by dapaulio
  • Thanks 2
  • 2 weeks later...
Posted

I had a similar issue. The ldf was so big during the upgrade it filled the drive and it ran out of space during the upgrade. I rolled the VM back and upped the drive size but again it failed. Not knowing why I looked in the log and by luck saw it was taking over 30 minutes to deploy and SOLUS was the rolling back the install.

 

In the end after changing the timeout in SOLUS the database update took 32 mins so I got very unlucky.

 

Hoping this helps someone out.

 

Cheers

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...