Upgrade Jira from 5.1.1 to 6.0.6 error "Could not allocate a new page for database "

After upgradeing to the newer version we get this error.

The database is set up for autogrowth and there is plenty of free space in the current file as it is.

any ideas on trying to fix this or rolling back to 5.1.1 At this point I just want our database to work since we want to migrate it back to the atlassian hosted solution.

Exception thrown during upgrade: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:ApplicationUser][id,10400][userKey,datalyzer][lowerUserName,datalyzer] (SQL Exception while executing the following:INSERT INTO jiraschema.app_user (ID, user_key, lower_user_name) VALUES (?, ?, ?) (Could not allocate a new page for database 'jiradb' 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.))
com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:ApplicationUser][id,10400][userKey,datalyzer][lowerUserName,datalyzer] (SQL Exception while executing the following:INSERT INTO jiraschema.app_user (ID, user_key, lower_user_name) VALUES (?, ?, ?) (Could not allocate a new page for database 'jiradb' 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.))
	at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.createValue(DefaultOfBizDelegator.java:379)
	at com.atlassian.jira.entity.EntityEngineImpl.createValue(EntityEngineImpl.java:28)
	at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build6040.mapUsername(UpgradeTask_Build6040.java:72)
	at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build6040.doUpgrade(UpgradeTask_Build6040.java:63)
	at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeTaskSuccess(UpgradeManagerImpl.java:673)
	at com.atlassian.jira.upgrade.UpgradeManagerImpl.runUpgradeTasks(UpgradeManagerImpl.java:526)
	at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgrade(UpgradeManagerImpl.java:456)
	at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeeded(UpgradeManagerImpl.java:399)
	at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeededAndAllowed(UpgradeManagerImpl.java:333)
	at com.atlassian.jira.upgrade.UpgradeLauncher.checkIfUpgradeNeeded(UpgradeLauncher.java:100)
	at com.atlassian.jira.upgrade.UpgradeLauncher.start(UpgradeLauncher.java:49)
	at com.atlassian.jira.startup.DefaultJiraLauncher$3.run(DefaultJiraLauncher.java:117)
	at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(DatabaseConfigurationManagerImpl.java:315)
	at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseActivated(DatabaseConfigurationManagerImpl.java:209)
	at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(DefaultJiraLauncher.java:105)
	at com.atlassian.jira.startup.DefaultJiraLauncher.access$100(DefaultJiraLauncher.java:30)
	at com.atlassian.jira.startup.DefaultJiraLauncher$1.run(DefaultJiraLauncher.java:69)
	at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:33)
	at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:64)
	at com.atlassian.jira.startup.LauncherContextListener.contextInitialized(LauncherContextListener.java:54)
	at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4791)
	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5285)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:724)
Caused by: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:ApplicationUser][id,10400][userKey,datalyzer][lowerUserName,datalyzer] (SQL Exception while executing the following:INSERT INTO jiraschema.app_user (ID, user_key, lower_user_name) VALUES (?, ?, ?) (Could not allocate a new page for database 'jiradb' 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.))
	at org.ofbiz.core.entity.GenericDAO.singleInsert(GenericDAO.java:136)
	at org.ofbiz.core.entity.GenericDAO.insert(GenericDAO.java:101)
	at org.ofbiz.core.entity.GenericHelperDAO.create(GenericHelperDAO.java:64)
	at org.ofbiz.core.entity.GenericDelegator.create(GenericDelegator.java:487)
	at org.ofbiz.core.entity.GenericDelegator.create(GenericDelegator.java:467)
	at org.ofbiz.core.entity.GenericValue.create(GenericValue.java:98)
	at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.createValue(DefaultOfBizDelegator.java:374)
	... 29 more

2 answers

1 accepted

Accepted Answer
0 votes

Upgrading to SQL Server 2008 R2 from 05 fixed the issue. I would like to add more, but I don't know what was wrong.

Good that you've fixed it :-) Always annoying when you don't really know why what you've done fixes it.

0 votes

I'm afraid the statement

>The database is set up for autogrowth and there is plenty of free space in the current file as it is

is simply not true. The error message is clear. Either:

  • Autogrowth is not enabled and you've hit the current limit.
  • You are out of disk space on the database server
  • You are using a file system that has limits on disk space usage by user and the database user has reached it (i.e. out of usable disk space)

Even if it is something else (I don't know MS-SQL that well. Well enough to diagnose the third answer when I ran into it, but not well enough to say it can only be one of those three), the problem is purely on the database side, and you need to do the diagnosis there, Jira isn't the problem.

The Database is currently 200 Mb (initial set size) and 98.75 Mb is free. Autogrowth is set at 10Mb at a time with unrestriced growth. The server has about 50GB free. There are no limitations on the server or users filesystem usage. It's standalone server thats dedicated to jira for both tomcat and Jira's sql server.

Unfortunately, there's still something wrong with that. What you've just posted might be true as far as you know, but it is clearly not what the SQL Server believes. The error you are seeing in the logs is not Jira or Java or the application server throwing any errors, they are simply reporting back what the SQL Server is telling them.

I'm afraid I can't tell you any more about that error than Google can. You need someone who knows SQL Server to help you find out why it isn't behaving in accordance with what you think you've set it up to behave like.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 25, 2018 in Jira

Atlassian Research Workshop opportunity on Sep. 28th in Austin, TX

We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...

465 views 7 5
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you