In a message dated 99-02-15 10:31:47 EST, you write:
I’m having a problem with sending documents to the repository. I’m
receiving ORA-01631 max # extents reached in table obj_x_documents. I’ve
searched the archives and done all the cleaning/scanning/repairing that was
recommended. I’ve also purged the da history. Still no luck. I don’t
want
to simply allocate more space, if that’s what this error suggests. I’d
like
to understand more about the table and how/when things are written there.
This is actually a sizing issue for your Oracle DBA.
Data in an Oracle database is stored in Tables. Tables, however, are allocated
in Extents. When a table grows, the Oracle database tries to allocate a new
extent for more space.
For control purposes, there is a maximum number of times that this can occur.
It is generally set by the Database Administrator.
To resolve this problem, you have to either:
- Allow a higher number of extents
- Configure bigger extents
Each of these steps is outside of the responsibility of BusinessObjects.
There is, however, one option that you can do. You didn’t say if you were
sending documents to Document Agent or simply to the Repository. If you are
trying to store documents for users in the repository, you can Purge the
documents prior to saving them. This will result in the report being stored
“empty”, which should significantly reduce the amount of space required in the
repository.
To calculate the space needed in the repository is fairly simple: look at the
file size of the file on your hard drive. Storing the document is simply a
matter of breaking the report file up into chunks and storing each chunk as
is. No compression is done. So, if a file is 2 megabytes on your hard drive,
it will occupy 2 megabytes of repository space. More or less.
Your DBA may want to know this information prior to resizing your document
domain.
The bad news is that the Purge trick does not work for Document Agent, since
the entire purpose of DAS is to refresh the report and send the data back to
the user. In that case, the data must be stored in the repository on its way
back to the users.
Hope this helps!
Regards,
Dave Rathbun
Integra Solutions
www.islink.com
Listserv Archives (BOB member since 2002-06-25)