Highlighted
Respected Contributor.
Respected Contributor.
637 views

HPSM Text Search not working cm3r. Error while reading file 'scirexpert:ir.cm3r'

Hi,

We are experimenting problems with the TEXT SEARCH functionality (as known as IR search).

The problem is with the cm3r table.
We have regenerated the cm3r table indexes a lot of times (from table definition by using option Regenerate IR indexes).

The last time I regenerate indexes was some days ago and steps was the following:

1. Open cm3r table in the windows client.
2. Select the option Table > Regenerate IR indexes.
3. The operation is completed and i can see a message in the log like:

RTE I IR Regen has completed.
RTE I IR Regen has completed. (redo.table,regen.table)
RTE I IR regen took: 1482703

4. At this point i can see that:

- SCIEXPERT table has NOT ir.cm3r records.
- IRQUEUE table has a lot of cm3r records.
- Progressively, IRQUEUE table has less  cm3r records and the number of ir.cm3r records in SCIEXPERT increase.
- At this point searches are working but, obviously, not all coincidences are returned because indexes doesn't exist.

(I think that this is the correct behavior)

5. The total regeneration of cm3r indexes takes a lot of time (3-4 days).
6. At 01/08/2017 10:00:00 (4 days after the process), i made a cm3r text search, from web, and i received the following error message:

Error while reading file 'scirexpert:ir.cm3r'

I saw the following messages in the log file:

4588(  4708) 01/08/2017 09:02:35  RTE I SQL scan for IR regen completed successfully. 226633 records processed.
4588(  4708) 01/08/2017 09:02:35  RTE I SQL scan for IR regen completed successfully. 226633 records processed. (redo.table,regen.table)
4588(  4708) 01/08/2017 09:02:35  RTE I IR Regen is starting to apply changes to IR index from shared memory
4588(  4708) 01/08/2017 09:02:52  RTE D 26691384: sqociExecCount - EXECUTE:DELETE FROM SCIREXPERTM1 WHERE ("FILENAME"=:Y)
4588(  4708) 01/08/2017 09:02:52  RTE I IR Regen has completed.
4588(  4708) 01/08/2017 09:02:52  RTE I IR Regen has completed. (redo.table,regen.table)
4588(  4708) 01/08/2017 09:02:52  RTE I IR regen took: 1482703
3792(  6396) 01/08/2017 09:02:52  RTE E read_ir_cache: Failure reading 512 bytes at offset scirexpert:ir.cm3r(0), errno=0 (No error)
3792(  6396) 01/08/2017 09:02:52  RTE E Error while reading file 'scirexpert:ir.cm3r'

Nobody has regenerated cm3r indexes. I don't know why there is a message at 01/08/2017 09:02:35 that says: "SQL scan for IR regen completed successfully. 226633 records processed.".

At this point:

- SCIEXPERT table has NOT ir.cm3r records.
- IRQUEUE table has a lot of cm3r records.

7. We are not able to finish the ir regeneration of cm3r indexes.

IR configurations is the following:

shared_memory:268435456
ir_disable:0
ir_asynchronous:1
ir_autostop:1
ir_max_relevant_answers:40
ir_max_shared:80530636
ir_timelimit:30

We have regenerated cm3r indexes a lot of times and the result is always the same.


Our software versions are the following:

BACKEND CONFIGURATION
SM Server RTE version: 9.34.2003-P2.
SM Application version: 9.34.2003-P2.
Server OS version: OS version Windows Server 2008 R2 Standard SP1 Intel 2,90 GHZ with 4 CPUs. 8Gb RAM.
Java version: 1.7.0_75 64-bit.
Oracle database version:  11.2.0.3.15 in Case Sensitive Mode


FRONTEND CONFIGURATION
OS version Windows Server 2008 R2 Standard SP1 Intel 2,90 GHZ with 4 CPUs. 8Gb RAM.
Tomcat 7.0.55
Apache 2.2
HP Service Manager Web-tier 9.34.2003-P2.
JRE 1.7.0_75 64-bit.
Thank you.

Tags (4)
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.