Bulk site deletion and Oracle's ORA-01654 exception

[nenad982]

Hi all,

I wrote the script that will delete batches of Share Sites with certain description (the batch is specified as query parameter in the request). So because we had approximately 3000 sites to delete, I executed script using batches of 200 sites. In the beginning everything was fine, I called this service few times and sites were deleted from the repo. But later on I started to receive following SQL exception (Oracle is used as db):

14:59:03,926 INFO  [org.aag.alfresco.webscript.DeleteSitesWebScript] START - DeleteSitesWebScript
14:59:04,088 INFO  [org.aag.alfresco.webscript.DeleteSitesWebScript] SITE INFO = NodeRef: workspace://SpacesStore/a89ff4f4-78af-446d-b19b-1a08e1d5ff60
14:59:04,091 INFO  [org.aag.alfresco.service.impl.AagSiteServiceImpl] START DELETION - Site is going to be deleted. Site's nodeRef: workspace://SpacesStore/a89ff4f4-78af-446d-b19b-1a08e1d5ff60
14:59:06,057 ERROR [org.aag.alfresco.webscript.DeleteSitesWebScript] DELETE FAILURE: NodeRef: workspace://SpacesStore/a89ff4f4-78af-446d-b19b-1a08e1d5ff60. MESSAGE:
### Error updating database.  Cause: java.sql.SQLException: ORA-01654: Index ALFRESCO.FK_ALF_PROPLN_KEY kann nicht um 128 in Tablespace USER_INDEX erweitert werden

### The error may involve alfresco.propval.insert_PropertyLink-Inline
### The error occurred while setting parameters
### Cause: java.sql.SQLException: ORA-01654: Index ALFRESCO.FK_ALF_PROPLN_KEY kann nicht um 128 in Tablespace USER_INDEX erweitert werden
‍‍‍‍‍‍‍‍‍‍‍

And now I am not able to delete this site at all using Java API. I did full rebuilt of Lucene indexes but without success to solve this problem. FYI I am using Alfresco Enterprise v4.1.2.

Did somebody have the same problem and maybe knows how to fix it?

Thanks…

[afaust]

Hello,

this error does not have anything to do with Lucene indexes. It seems your database has reached some kind of size limit and can not increase the storage space for an index on a table that is usually used for Auditing and the AttributeService. It does not have to be a limit on the hard drive - it can also be a limit set via configuration. Check back with your DBA to analyze your database.

Regards
Axel