Purge old data from OBJ_X_DOCUMENTS table

security Supervisor (4.x - 6.x)
1

Hi,

I am getting this error when I am trying to send a query to Doc Agent… [ORA-01652: unable to extend temp segment by 128 in tablespace TEMP :-1652]

Can anyone help me with this ?

I just realized that the table OBJ_X_DOCUMENTS has grown to a size of 1768 MB due to which I am running out of Temp space whenever I query against the database. Is there an easy method to get rid od the old documents ?
Can I know what exactly is the data contained in this table ? Is it the documents sent to repository via Doc Agent or is it the documents residing in the repository or what is it ? I do not want to delete the data from backend with the fear of distrbuing the links. So please tell me a way of deleting them from OBJ_X_DOCUMENTS ( 1768 MB). And what info does OBJ_M_DOCUMENTS ( 0.27 MB) contain ?

Thanks
Ashish

Listserv Archives (BOB member since 2002-06-25)

2

Ashish:

If you have access to the Supervisor module, you can click on Tools, delete docs and remove your old docs if you know which ones are old. Else if you’ve aleady done so, you can run a scan, repair and compact on your document domain.
Either this or increase the database extents. Cheers,
Ketan

Listserv Archives (BOB member since 2002-06-25)

3

Ketan,

I do have access to Supervisor… but all I find in that window is…3 fields, Name, Domain and Type. There isnt any Date field by which I can know the latest document. The Type field shows …
Document (user)
Document (repository) or
Processed Document( user)

What do these mean ?

Thanks

Ashish

Listserv Archives (BOB member since 2002-06-25)

4

Ashish:
These are the only 3 fields under ‘delete/documents’. Therefore, you need to know which docs are no longer in use and delete those. As for the Type fields, see below:
Document (user)- a document sent from a user to another user (ie. inbox) Document (repository)- document exported to the repository by a user Processed Document( user) - a document processed by DAS or BCA (v5) WebIntelligence Document(repository) - A corporate document created in WebIntelligence

Cheers,
Ketan

Listserv Archives (BOB member since 2002-06-25)

5

In a message dated 00-01-06 17:11:27 EST, you write:

I just realized that the table OBJ_X_DOCUMENTS has grown to a size of 1768 MB due to which I am
running out of Temp space whenever I query against the database. Is there
an
easy method to get rid
od the old documents ?
Can I know what exactly is the data contained in this table ? Is it the documents sent to repository
via Doc Agent or is it the documents residing in the repository or what is it ? I do not want to
delete the data from backend with the fear of distrbuing the links. So please tell me a way of deleting them from OBJ_X_DOCUMENTS ( 1768 MB). And what info does OBJ_M_DOCUMENTS ( 0.27 MB) contain ?

OBJ_X_DOCUMENTS contains binary data made up of your documents, their data providers, and all of the data. These can be documents set to DAS, documents sent to the Repository, or documents sent to Users that were never retrieved. (Once a document sent to “user” is retrieved it is supposed to leave the repository.)

OBJ_M_DOCUMENTS is where the document name, owner, and other supporting information is stored. It will be much smaller since there is no actual data involved.

You should never delete items from the repository directly!

You can try to “Compact” your repository. That will ensure that any documents marked to be deleted actually go away. Documents (users, universes, etc.) that are “deleted” do not actually leave until a Compact is done. At least that is my understanding.

Another possibility is to retrieve each document from the repository, Purge it, and store it once again. If a document is stored in the repository to be a “template” or starting point for a user report, there is not much need to distribute a file with data in it.

Find out which documents have been sent to a user. Perhaps a user that no longer uses BusObj or works at the company. Someone should log as that user and delete any documents stored by that user.

All of these options are temporary. Ultimately your DBA needs to understand the purpose of the repository, the needs of the users, and size the table accordingly. If you are running out of TEMP space, it looks like there are some sizing issues that need to be resolved.

Regards,
Dave Rathbun
Integra Solutions
www.islink.com

Listserv Archives (BOB member since 2002-06-25)

6

Ketan, i think the question still remains, how about dates?
For example i have a document refresh daily in DAS, with a large user distribution. Let’s say a user does not always retrieve his/her copy of the document. The repository will hold a number of copies of the same document. When i look at the repository that document shows up a number of times, which ones should i delete if i want to keep just the latest?(no date identifaction available in supervisor).
I could use managerO to view associated info, dates etc. but to follow the joins thread to do a delete seems too complicated. any suggestions?
thanks. daniel
__________________________________________________ Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com

Listserv Archives (BOB member since 2002-06-25)