cannot read from file 201 because it failed verification tests ... temp01

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Article Type: General
Product: Aleph
Product Version: 20

Description:
I ran p_manage_01. It seemed to run OK, but after, OPAC/keyword searching are not working: the user gets no response; the www_server log shows "network connection timeout".

Resolution:
I did the SQL from KB 8192-6423 to check for missing Oracle indexes:

abc01@ALEPH20> select index_name from all_indexes where owner = 'USM01' and index_name like 'Z%' minus select index_name from all_indexes where owner = 'ABC01' and index_name like 'Z%' and status = 'VALID';
**** Hit return to continue ****

INDEX_NAME
------------------------------
Z0101_ID3
Z69_ID1
Z97_ID1
Z97_ID2
Z97_ID3
Z98_ID

The Z97_ID1, Z97_ID2, Z97_ID3, and Z98_ID are all indexes on Keyword tables which should have been generated as part of p_manage_01.

Looking at the p_manage_01 logs in abc01 $data_scratch, we see that the cycles files show success and the last data load step log (p_manage_01_e.log) is also successful, but the next step (create_ora_tables_z97_id1.log
) and all of the following Oracle index build steps -- fail like this:

aleph_admin@ALEPH20> 02:40:45 aleph_admin@ALEPH20> CREATE INDEX ABC01.Z97_ID1 ON
ABC01.Z97 (Z97_WORD_R ASC)
*
ERROR at line 1:
ORA-01187: cannot read from file 201 because it failed verification tests
ORA-01110: data file 201: '/ora01/oradata/aleph20/aleph20_temp01.dbf'

I tried to build the z97_id1 using util a/17/2, but it got the same error.

util o/14/1 and o/17/2 also show the error.

This error indicates that the Oracle TEMP tablespace files are corrupted. This is a temporary tablespace and can be dropped and recreated at will; there's no data in it which Aleph needs. It should be recreated with new tablespace files.

Once this problem is resolved you should use util a/17/2 to build all 6 of these Oracle indexes.

Article last edited: 10/8/2013