Client Support
cancel

3 Questions - Duplicate TRIM numbers, 110,000 docs in file etc.

Highlighted
PerthRM8
Outstanding Contributor.

3 Questions - Duplicate TRIM numbers, 110,000 docs in file etc.

Hi,

Win 7, MS Office 2010, SQL 2008-R2, HP TRIM 7.3.4.5645 (still)

 

Hi,

WGS are still falling down often in 7.3.3, and yesterday when that happened, we had a case of 2 same TRIM Document numbers were registered and exist in TRIM Database...How is that possible? Screenshot atatched. When we do search for the documents made by that person, only 1 trim doc number appears, but when we do search for that specific trim doc number, two matches popped up.

 

Second question is the one I maybe asked already, but: we have 2-3 specific branches that save lost of documents into one trim file/container so now we have file with 110,000 docs and 3-4 other branches are nearby, around 80,000 docs... What is the maximum number of items that could be stored like this in those containers and what could get wrong if we continue to save docs as this? What are the potential issues that we could experiencing in regards to SQL databse, Data Store and document folders there (windows fodlers) or what else is influenced by this?

 

Third question is about amalgamation of a different branches into one big organisation ( 3 cases of that to happen) :

 

Different cities and regions will be joined into one TRIM organisation in our company. All of them are part of our company and have their WGS's (servers).

These regions already have hard copy files with TRIM Home location of that city, than the owner, assignee etc.... Now all these phisycal locations are going to be united into one digital location ... The question is: Has anyone done this before, and what were the issues arised? What to pay attention to and how to do this the best way?

 

Thanks

 

4 REPLIES
Greg Fraser_1
Acclaimed Contributor.

Re: 3 Questions - Duplicate TRIM numbers, 110,000 docs in file etc.

Here are my thoughts:

 

1) potentially just a display issue, I would guess that these are the same record. But this would be better investigated with a support case. So you will need to log one up.

 

2) Huge problems can arise with event processing when you have containers with an extremely large number of records contained. The recommended is 300. It can be a tedious process to change existing containers but one that needs to be undertaken. You should have an automatic part creation rule in place, so when the container hits 290 it will auto create a new part and add the record in there.

You should consider reviewing the process about why thousands of documents are being dumped into a single container. there might be a simpler more efficient way to register these documents that falls more in line with a traditional records keeping model.

 

3) There are a lot of things to consider when merging locations and records together. In many cases it is easier to engage HP Professional Services or a business partner with some experience to assist. The main thing is you have a detailed plan and execute within a test environment first, then test and ensure that it is working as it should.

 

 

**Any opinions expressed in this forum are my own personal opinion and should not be interpreted as an official statement on behalf of Micro Focus**
PerthRM8
Outstanding Contributor.

Re: 3 Questions - Duplicate TRIM numbers, 110,000 docs in file etc.

Thanks,

Not a display isue.... :-)

Email just came from DBA Administrator that we have 28 duplicated records:

 

"The record number was recorded in the column recordId in the table TSRECORD

 There is not unique constraint on this column, there are 28 record numbers are duplicated"

 

I thought that this column is the primary key, unique number... obviously the primary key is the URI number ...

 

2.: What sort of event processing can be in danger if we have 110,000 docs? We turned of the retention triggers a year ago since 7.1 . Is there anything else on the TRIM Store side, or on the general performance of TRIM? or in SQL database... Obviously one table will be very long ...110,000 items/rows.... Updating some metadata will be tricky ?

 

3.

On this one I am asking if anyone has done this, and how they ovecome the issues such us creation of a new physical file in one city (now other city will have the same Home Location as per this city No 1) and then assignee / owner and those sort of issues .... It looks like that users will have a bit of confusion when we do the amalgamation like that.

Cheers

 

 

 

Greg Fraser_1
Acclaimed Contributor.

Re: 3 Questions - Duplicate TRIM numbers, 110,000 docs in file etc.

The constraints must have been dropped while performing some maintenance task. So you will need to change the record number so that they are inline with the current order, then turn the constraints back on.

As you mention, anytime the contents of the container need to be updated for example security it will be incredibly slow.
**Any opinions expressed in this forum are my own personal opinion and should not be interpreted as an official statement on behalf of Micro Focus**
Grundy
Acclaimed Contributor.

Re: 3 Questions - Duplicate TRIM numbers, 110,000 docs in file etc.

We have seen some cases where the TRIM upgrade did not re-apply the constraints and indexes correctly because of integrity issues.

This is why it's important to run a full schema repair after an upgrade and review the log (don't just assume it fixed anything it found wrong, most often it needs manual work.)

 

If you run a full schema repair, the very bottom of th elog has a summary of the tasks and any issues.

 

Once you resolve the issue, run the schema repair again until and repeat the fix process until the log come sback with no errors.

 

 



::::::::::::::::::::::
NOT A HP EMPLOYEE
::::::::::::::::::::::

INFORMOTION.com.au