I got this error couple of times.
Once when i restored a backup from DB2FP5 to DB2 FP2.
Installing the appropriate fixpak fixed the issue.
Second time i received this error when i restored a backup from Windows
2000 to Win 2003. This time DB2 level was same.
I noticed the text index was not there when i restored. Recreating &
Updating the Text index helped.
And the *.ini file you specified was read only too.
Lars Haugseth wrote:
* Lars Haugseth <la***********@tn.no> wrote:
|
| * Lars Haugseth <la***********@tn.no> wrote:
| |
| | Setup: SuSE Linux 8.2 running IBM DB2 v8.1 with Net Search
Extender. | |
| | We had to hard reset our server, and did a successfull crash
recovery. | | We now have a problem with operations involving text indexes. For
| | example, when We try to update an index, we get the error message
| | "CTE0190 Executable program "cteadmsv" could not be started."
| |
| | We have tried the following:
| |
| | - db2text stop/start
| | - dbadmin stop/start
| | - db2text drop index... => just produces the above error message
| |
| | The free text indexes are not working at all, ie. all operations
| | involving free text searches are now failing with various error
| | messages.
| |
| | Any ideas on how to get the system back into a working condition
| | short of backup/reinstall/restore would be appreciated.
|
| Additional info that may or may not be of use: any select statement
| involving freetext indexes produces the following error message:
|
| SQL0443N Routine "*RCH_1K16" (specific name "") has returned an
error | SQLSTATE with diagnostic text "CTE0101 A search engine operation
failed. | Reason code: "16"". SQLSTATE=38701
For now, we managed to "fix" this by doing the following:
db2inst1:~> chmod 666 ~/sqllib/db2ext/indexes/NODE0000/IX*.ini
By using 'strace', we could see that when running text search
queries, DB2 complained about being unable to open these files. It was
obviously trying to open these files in 'write' mode, which failed since they
had permission 440.
We're still interested in any clues about how this happened and
how to fix it properly.
--
Lars Haugseth