CMS Repository Database Temp Tablespace Sizing

1. While running some large reports Business Objects (XI 3.1 FP2.7) received an ORA-01652 (Unable to extend temp segment in tablespace TEMP) error for the CMS repository. The CMS database is running in an independent Oracle instance with the auditing database, so only the Business Objects engine would be using the temp tablespace. All the report information is extracted from other database instances. This tablespace was sized at 4GB when this error occurred.

2. What is Business Objects using the CMS repository temp tablespace for? What are some sizing guidelines, should this tablespace be sized based on estimated report sizes, report rows, concurrent users, etc?