disk space growth after TS 6.5 upgrade

Hello All-

I have recently upgraded one of our Windows 2000 TeamSite 6.1 SP1 servers to TeamSite 6.5 with Search installed locally. The event sub system DB is also the default install. Since the upgrade, we have noticed that the disk space is growing daily. For example, openjms.db has balooned to over 5 GB in less than 2 weeks. Has anyone seen this before and know how to control this growth?

I imagine that since we are only using the search feature, and not the optional reporting feature, that we don't need to keep the eventsubsystem DB entries for very long. Any insights, suggestions, flames, etc. much appreciated.

Regards,

-nathan
WA DIS
~~~

Find more posts tagged with

Comments

iwovGraduate

Have you searched the devnet forums ? There has been a lot of discussion on this.

This is a known issue in the default DB with TS 6.5.
You will not have this issue if you use a supported RDBMS (Oracle/SQL Svr) for reporting DB instead of the default.

Johnny

There's plenty posts here about this.. the default file implementation has a bug in which events are never removed, thus it continously grows.

If you are not going to use a rdbms, I suggest you turn the event sub system off and run a nightly incremental index instead.

Your users will only be able to search for newly created content the next day however.

John Cuiuli

NathansDIS

Thanks for your input guys! Yes, I have seen the posts on Devnet, but found the info scattered in among other issues, and wanted to try to get all the info about this issue in one place.

Does anyone know of a way to truncate or start over with the event sub system database? This would just be a temporary fix until I get back from a long weekend's vacation. Don't really want the disk filling up when I'm out of the office. Has there been any commitment from Interwoven about when this bug will be fixed? Is this going to be addressed in TeamSite 6.5 SP1 due out any time now?

I know that you should use a real RDBMS to manage the event subsystem DB, but since we don't plan to use the reporting feature, the default DB should be sufficient to feed the search/index services. The excuse that the default install should only be used for testing and not used in production is growing a bit thin, and really doesn't apply (in my mind) to someone who is only wanting to use Search with incremental updates. What think?

Thx again for your time,

-nathan
Washington State DIS

iwovGraduate

... but since we don't plan to use the reporting feature, the default DB should be sufficient to feed the search/index services ...

I think you may have misunderstood the issue here. The problem with the default DB is NOT due to who (reporting or search) uses it. In other words the growth of openjms.db is independent of whether you are using reporting feature or not.

NathansDIS

Right, my point is that I shouldn't have to use a RDBMS when all I want to do with event subsystem is support incremental updates... Is anyone from Interwoven going to jump in here, please?

iwovGraduate

Does anyone know of a way to truncate or start over with the event sub system database?

This has been discussed in the threads as well. I don't recall the exact steps (and don't have time right now to search for it, sorry), but it involves something like stopping the Events Subsystem service, deleting the .db file along with some other related files, and restarting the service. Search the forums again. Its out there.

cellmerged.jpg

sampledata.txt

NathansDIS

Thanks graduate, if I find the steps, I'll post em to this thread.

smenon

Yes.. the way to do this would be to stop the index service and then stop the event subsystem. Remove the openjms.db file and then restart the event subsystem and then the index manager. In order to ensure that your indices are up to date, you might want to refresh the index by running the iwndxrefreshbr CLT.

The problem/bug with the growth of the openjms.db file is in the OpenJMS implementation which forms the foundation of the publilshing service and not in the TeamSite code. We added support for MySQL as the RDBMS in case you don't have (and don't want to purchase) a license for Oracle or SQL Server or DB2.

--Sunil Menon
Product Manager
Interwoven, Inc.

NathansDIS

Well, this did work! Here is the revised set of steps that I created from Sunil's post and my conversation with support:

stop IW search
stop IW index
stop IW eventsubsystem
delete openjms.db
delete openjms.lg
start IW eventsubsystem
start IW index
start IW search
run iwndxrefreshbr -i on each branch shown in the output of iwndxlistbr
check the logs in iw-home\search\logs
test the search command from within content center
take the rest of the weekend off.

Thanks all you guys for your input.

-Nathan
Washington State DIS
~~~

NathansDIS

Thanks for your reply Sunil-

Is there a documented process for moving the db to MySQL that you can point me to?

Thanks,

-nathan
Washington State DIS

mgal

Hello Nathan

There is a KB article on this one
https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=53407

You might want to look at event subsystem section in the Admin manual too.

Hope this helps

Thxs,

Mohammed Gazal.

Ottawa_IWOV

Anyone know where I can obtain the drivers for MS SQL that are mentioned in the Admin Guide?

nipper

>Anyone know where I can obtain the drivers for MS SQL that are mentioned in the Admin Guide?

just a guess, Microsoft ?

Do you have a license for it ?

Ottawa_IWOV

Yes we have a license. I am just a little confused following the documentation. I though TeamSite might have shipped with these (In the case of datadeploy the inetuna drivers).

Just preplexed on how to point to the drivers correctly

No worries - found what I was looking for ...

Lucas

Edited by Ottawa_IWOV on 03/29/05 11:52 AM (server time).

ProfessorX

Thanks for the share...worked on DEV going to try it on PROD tonight.

Thanks in advance!
win2k3 TS 6.5 sp1; OD 6.0.1; DD enabled
The Professor-