|
Problem IT04391
|
Status: Closed |
SUPPORT SPECIAL CHARACTERS IN TEXT SEARCH INDEX NAMES |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
Include support for all characters that DB2 objects support in
Text Search as well. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
****************************************************************
* PROBLEM DESCRIPTION: *
* Include support for all characters that DB2 objects support *
* for Text Search indexes as well. *
****************************************************************
* RECOMMENDATION: *
**************************************************************** |
| Local Fix: |
|
| Solution |
The fix is in V105fp5. The customers can now use special
characters as part of their index names. |
| Workaround |
not known / see Local fix |
| Comment |
The restriction of using only aplha-numeric characters in Text
Search index names has been removed. and All characters now
supported for DB2 object names are now supported for Text Search
Index names |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 15.09.2014
15.12.2014
15.12.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.5
|
 |
