This is a CHAR(252) character, which internally is a @SM or @SVM reserved character. I don't know why it's generating this message. You do have to deal with this as an issue, though.
Do you have NLS installed?
Write failed for Hashed File
Moderators: chulett, rschirm, roy
Another workaround is doing the lookup against a uv table. Nevertheless you would not be able to take the field in question as part of the key, because uv tables use the same hashing algorithm. But afterwards you can do the lookup using any columns. For performance reasons, you might consider to create a secondary index.
Kind Regards
Stephan
Stephan
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
I think Stephan's is the wisest course. You can create a UniVerse table with an automatic key as follows (edit the DDL in the UV stage to add the DEFAULT clause on the pkey column):
You can create the index with a regular CREATE INDEX statement:
Code: Select all
CREATE TABLE tablename (
pkey INTEGER NOT NULL DEFAULT NEXT AVAILABLE,
col1 VARCHAR,
col2 VARCHAR,
col3 INTEGER,
col4 VARCHAR,
col5 VARCHAR);
Code: Select all
CREATE INDEX COL4_IDX ON tablename(col4);
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.