2 3 4 the file /tmp//tmp/drgitmpMFi4dy4qWGlj0.tmp can not be opened, check it
the file /tmp//tmp/drgitmpMFi4dyx26xnl0.tmp can not be opened, check it
the file /tmp//tmp/drgitmpMFi4dyWEEbIp0.tmp can not be opened, check it
the file /tmp//tmp/drgitmpMFi4dy5FRxnn0.tmp can not be opened, check it
the file /tmp//tmp/drgitmpMFi4dyIOMbno0.tmp can not be opened, check it
the file /tmp//tmp/drgitmpMFi4dyawgZ2s0.tmp can not be opened, check it
the file /tmp//tmp/drgitmpMFi4dyviNINz0.tmp can not be opened, check it
the file /tmp//tmp/drgitmpMFi4dySl4JIE0.tmp can not be opened, check it
the file /tmp//tmp/drgitmpMFi4dytZ6CaJ0.tmp can not be opened, check it
the file /tmp//tmp/drgitmpMFi4dybA4JNN0.tmp can not be opened, check it
the file /tmp//tmp/drgitmpMFi4dyfNuwRP0.tmp can not be opened, check it
the file /tmp//tmp/drgitmpMFi4dy20GavV0.tmp can not be opened, check it
the file /tmp//tmp/drgitmpMFi4dybEI91Z0.tmp can not be opened, check it
the file /tmp//tmp/drgitmpMFi4dya004h10.tmp can not be opened, check it
the file /tmp//tmp/drgitmpMFi4dyDXdF650.tmp can not be opened, check it
the file /tmp//tmp/drgitmpMFi4dy6o9cPb0.tmp can not be opened, check it
the file /tmp//tmp/drgitmpMFi4dyIripWg0.tmp can not be opened, check it
the file /tmp//tmp/drgitmpMFi4dyEl2Rzi0.tmp can not be opened, check it
the file /tmp//tmp/drgitmpMFi4dyZvtrGn0.tmp can not be opened, check it

Index created.

But the same test on HPUX finishes ok.

The HPUX database is 10.2.0.4 and the Linux database is 10.2.0.5. It should be ok?

Can you try creating a directory /tmp/tmp (with world write access) and see if the problem disappears? Also check for any environment variables (TEMP or TMP perhaps) which point to this directory when you start the db.

Also, after running that create index statement, can you do

select * from ctx_user_index_errors;

10.2.0.4 and 10.2.0.5 uses filters from different vendors (10.2.0.4 is Verity, 10.2.0.5 is Stellent/Oracle), so it's possible (though unlikely) that your files are in a format not handled by the newer filters.

Text filter has been changed in 10.2.0.5 thus the slow filtering issue, more details in note 1105717.1
In 10.2.0.4 filter used by Text did not support archive file formats.
The message "tmpfile can not be opened" is ignorable, mostly from filtering archive files and this is fixed in latest filter release used by Text, ie 11.2.0.2 or 11.2.0.3, where filtering performance is also improved.

When I try to index my testtable (with 20 rows) I only get the "the file /tmp/..." messages, but when running the import with the whole table (730 000 rows) it also writes a lot of files (not all) to the /tmp directory.
Most of the documents is scanned documents in jpg format. I don't now if the indexing works on these filetypes - but again, no problems on the existing hpux/10.2.0.4 database.

"Forever" is meaningless. How long does it take, and for how many documents? Text indexes do take a long time to create - can be measured in days in some situations.

The errors you're seeing in ctx_user_index_errors are probably caused by damaged documents - files that the filter thinks it recognizes, but then fails to process according to the expected layout for those documents. If there are only a few of these, then I wouldn't worry too much - if there are lots (> 1% of your total, perhaps) then it's definitely worth investigating further.

Scanned documents stored as images (jpegs, tiffs, etc) cannot be indexed. Generally the filters should recognize and skip such documents without errors.