Re: DCI Log Interpretation (721 Views)
Reply
Honored Contributor
TRIMGuru
Posts: 605
Registered: ‎05-24-2010
Message 1 of 11 (726 Views)
Accepted Solution

DCI Log Interpretation

Ok, I've never seen this before.  Client is using 6.2.5 and recently had a document content indexing problem (which was resolved by doing a total reindex), but take a look at some of the entries from the DCI log.  Question for you guru's out there (in red)  follows each type of log entry (in blue) listed below:

 

Log opened on xxx.ms.xxxxxxxxx.xxx S/W version: 6.2.5.1297 Friday, August 20, 2010 at 12:10:24 AM (GMT) (Thursday, August 19, 2010 at 5:10:24 PM (GMT-07:00))

00:10:24         16    BP    ***** Could not open Content Index dataset. ERROR:  I/O Error: File version mismatch Check 'Document Content Search' Options.

 

What or where is this "Document Content Search' Options it is referring to?

 


01:26:17          0    BP    ***** Content index needs configuration update. No chain indexes defined.

 

We believe they are, is there some other place we need to define this?

 

 

01:27:01          0    BP    ***** The document 7618 is not recognized by the ISYS indexing engine.

 

We understand the message, however, how do we identify WHICH document it's referring to?

 


01:30:17          0    BP    ***** Error indexing document: 8/19/2010 6:30:17 PM     OPEN ERROR  Excel          TRIMDB_BP_8158.

 

We understand the message, however, how do we identify WHICH document it's referring to?

 

 

01:30:17          0    BP    ***** Record 8158 failed to index correctly () and has been automatically quarantined.

 

We understand the message, however, how do we identify WHICH document it's referring to? And it's not listed in the quarantined section of the TES.

 

01:31:18          0    BP    ***** Error indexing document: 8/19/2010 6:31:18 PM    TRIMDB_BP_8286 - exceeds 65,535 paragraph per document limit..

 

We understand the message, however, how do we identify WHICH document it's referring to?

 

 

01:50:36          0    BP    ***** Error indexing document: 8/19/2010 6:50:36 PM     OPEN EXCEPTION Exception EAccessViolation in module ISYS9core.dll at 00131FD4..

 

Ut oh, either this means the document was open when it was trying to be indexed or ?  Also, how to identify which document?

 


02:17:09          0    BP    ***** The document 5407 is not recognized by the ISYS indexing engine.

 

We understand the message, however, how do we identify WHICH document it's referring to?

 

 

Any help appreciated and thanks in advanced!  I've just not seen these before (guess I've been lucky).

 

 

Honored Contributor
EWillsey
Posts: 1,930
Registered: ‎04-20-2010
Message 2 of 11 (726 Views)

Re: DCI Log Interpretation

Responses in gray.

 

00:10:24         16    BP    ***** Could not open Content Index dataset. ERROR:  I/O Error: File version mismatch Check 'Document Content Search' Options.

 

What or where is this "Document Content Search' Options it is referring to?

 

This is stored in the DCI definition file.

 


01:26:17          0    BP    ***** Content index needs configuration update. No chain indexes defined.

 

We believe they are, is there some other place we need to define this?

 

This error occurs when using a networked DCI path and the path becomes unavailable.  The Event Server will continue to show this error until it is restarted (even if the path becomes available again). 

 

 

01:27:01          0    BP    ***** The document 7618 is not recognized by the ISYS indexing engine.

 

We understand the message, however, how do we identify WHICH document it's referring to?

 

Isn't 7618 the URI?  Search the database tables directly or use a search based on the time frame (or use the quarantine search/tab).


01:30:17          0    BP    ***** Error indexing document: 8/19/2010 6:30:17 PM     OPEN ERROR  Excel          TRIMDB_BP_8158.

 

We understand the message, however, how do we identify WHICH document it's referring to?

 

See previous.

 

01:30:17          0    BP    ***** Record 8158 failed to index correctly () and has been automatically quarantined.

 

We understand the message, however, how do we identify WHICH document it's referring to? And it's not listed in the quarantined section of the TES.

 

See previous.

 

01:31:18          0    BP    ***** Error indexing document: 8/19/2010 6:31:18 PM    TRIMDB_BP_8286 - exceeds 65,535 paragraph per document limit..

 

We understand the message, however, how do we identify WHICH document it's referring to?

 

See previous.

 

01:50:36          0    BP    ***** Error indexing document: 8/19/2010 6:50:36 PM     OPEN EXCEPTION Exception EAccessViolation in module ISYS9core.dll at 00131FD4..

 

Ut oh, either this means the document was open when it was trying to be indexed or ?  Also, how to identify which document?

 

This is an ISYS error.  Must submit a ticket to the helpdesk.  See previous.

 


02:17:09          0    BP    ***** The document 5407 is not recognized by the ISYS indexing engine.

 

We understand the message, however, how do we identify WHICH document it's referring to?

 

See previous.

 


I hope this helps!


Cheers,

Erik

Honored Contributor
TRIMGuru
Posts: 605
Registered: ‎05-24-2010
Message 3 of 11 (726 Views)

Re: DCI Log Interpretation

Eric,

 

It DOES help a LOT!  Really appreciate it.  We'll submit a help desk ticket on that one.

 

By the way, where does one go to find out the answers, like you provided?  Is there a reference document somewhere?

 

 

Honored Contributor
EWillsey
Posts: 1,930
Registered: ‎04-20-2010
Message 4 of 11 (726 Views)

Re: DCI Log Interpretation

It's not provided anywhere public.  Just comes with years of experience!

Frequent Advisor
TRIM 6.1.3.6768
Posts: 39
Registered: ‎05-05-2009
Message 5 of 11 (726 Views)

Re: DCI Log Interpretation

[28735] An error occurred during event processing.
Process Type: Content Indexing
Current Action: processOneEvent-ep_contentIndex
The primary content index in folder \\XXXXX\XXXXXXXXXXX\DCI\BD\SDB_20110205 has a pending transaction file (\\XXXXX\XXXXXXXXXXX\DCI\BD\SDB_20110205\TRIMpending.bin).  This indicates that a previous call to update the index using these transactions has failed.  All content indexing will cease for this database until the problem has been rectified.

Can someone explain this one and how to rectify it?

Honored Contributor
TRIMGuru
Posts: 605
Registered: ‎05-24-2010
Message 6 of 11 (726 Views)

Re: DCI Log Interpretation

The attached document should give you some insight into this and what you can do.

 

Hope it helps :smileyhappy:

Frequent Advisor
TRIM 6.1.3.6768
Posts: 39
Registered: ‎05-05-2009
Message 7 of 11 (726 Views)

Re: DCI Log Interpretation

Thanks TRIMguru

 

I tried these steps of renaming TRIMPending to TRIMTrans but then a error comes up saying

 

08:07:30          0    BD    ***** Could not open Content Index dataset. ERROR:  I/O Error: File version mismatch Check 'Document Content Search' Options.

 

Any ideas from here - We have a logged a case with HP as there are currently 356 content indexes in queue

Honored Contributor
TRIMGuru
Posts: 605
Registered: ‎05-24-2010
Message 8 of 11 (726 Views)

Re: DCI Log Interpretation

Hmm, are you on 6.2.5 ?

 

It appears there was an ISYS patch that came out awhile ago.  (Ref:  http://h30501.www3.hp.com/t5/Client-Support/DCI-Failing-6-2-5/m-p/20561/highlight/true#M1087 ). 

 

And if on 6.2.5, do you know if you got the patch?

 

Frequent Advisor
TRIM 6.1.3.6768
Posts: 39
Registered: ‎05-05-2009
Message 9 of 11 (726 Views)

Re: DCI Log Interpretation

Thanks again for the help.  We currently using ISYS 9 but I don't believe we have the patch as the prvious support call was not related to the patch.  yes using 6.2.5

 

Are you thinking this is the one that does relate to the patch.

Honored Contributor
TRIMGuru
Posts: 605
Registered: ‎05-24-2010
Message 10 of 11 (726 Views)

Re: DCI Log Interpretation

Yep, sent you a PM... 

Honored Contributor
Grundy
Posts: 2,853
Registered: ‎02-16-2009
Message 11 of 11 (721 Views)

Re: DCI Log Interpretation

The latest 6.2.5 1332 has the patch included.

If you are on an earlier build, you can obtain the patch by contacting support.

 

Just ask for the DCI Hotfix for the I/O Mismatch error.

 

 



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

Kapish.com.au
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.