Database FileGroup Size is increasing exponentially

Which IIQ version are you inquiring about?

Sailpoint IIQ 8.3P3

Please share any images or screenshots, if relevant.

Please share any other relevant files that may be required (for example, logs).

Failure occured during job recovery. [See nested exception: org.quartz.JobPersistenceException: Couldn’t store trigger ‘DEFAULT.Perform maintenance 0’ for ‘DEFAULT.Perform maintenance’ job:Could not allocate a new page for database ‘identityiq’ because the ‘PRIMARY’ filegroup is full due to lack of storage space or database files reaching the maximum allowed size. Note that UNLIMITED files are still limited to 16TB. 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. [See nested exception: com.microsoft.sqlserver.jdbc.SQLServerException: Could not allocate a new page for database ‘identityiq’ because the ‘PRIMARY’ filegroup is full due to lack of storage space or database files reaching the maximum allowed size. Note that UNLIMITED files are still limited to 16TB. 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.quartz.impl.jdbcjobstore.JobStoreSupport.schedulerStarted(JobStoreSupport.java:697)
at org.quartz.core.QuartzScheduler.start(QuartzScheduler.java:539)
at org.quartz.impl.StdScheduler.start(StdScheduler.java:142)
at sailpoint.scheduler.QuartzSchedulerStarter.startScheduler(QuartzSchedulerStarter.java:96)
… 68 more

Share all details about your problem, including any error messages you may have received.

The Primary FileGroup Size is full and is increasing every day. What could be the possible cause for the increase in filegroup.

Hi @Nitish92,

growing in size is the normal behavior of a DB. In IIQ there are some options which can significantly increase the size of the DB and every IIQ creates some objects like TaskResult, ProvisioningTransaction, SysLog and IdentitySnapshot.

You can configure an expiration time for this objects on Global Configuration → IdentityIQ Configuration and those objects will be delete with Perform Maintenance task:

This help you to reduce the size of db. Another tools is the Shrink of DB, is an operation on DB side that compact the db. ALso, you can reduce the size of extended column until the effective util size; on this page you can find some recommendations.

I suggest you implement those operation incluse a maintance plan on DB but to resolve the problem you must increse the Autogrowth, the Maxsize(if it is configurated with a limit), the avaible space for the db on the server, ecc…

1 Like

Thank you @enistri_devo for the suggestions. We will work on them to tune our DB.

2 Likes

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.