IO10709: TDS server may not sort national language characters properly

Direct links to fixes

APAR status

Closed as program error.

Error description

When requesting sorted results from the TDS server, the sort
order depends on the code page and collation options of the
underlying DB2 database.

If the database was created in the local code page (default for
TDS 5.x and earlier, or "-x" option for TDS 6.x), then the data
will be collated according to the system defaults (and should be
correct).

If the database was created with UTF-8 code page (default for
TDS 6.x, or "-c" option for TDS 5.x), then the data will be
collated in strict byte-order, equivalent to the DB2 option
"COLLATE USING IDENTITY". This will generally not produce
expected results for extended character sets beyond portable
ASCII (US).

Local fix

Once the database has been created, the code set and collation
order cannot be changed. So the only way to fix this on an
existing server is to:

  1) backup the data to an LDIF file,
  2) create a new database with the desired code set / collation
       order,
  3) configure the server to use the new database
       (or crate a different server instance altogether),
  4) reload the data from LDIF back into the new database.

If all your data can be represented in a single (non-unicode)
code page, then using the "idscfgdb -x" option to create the
database in a local system code page should work fine.

However; if you need to store unicode data, it is also possible
to configure the database in the UTF-8 code set using the
standard Unicode Collation Algorithm (UCA). Unfortunately, this
is not supported directly by the TDS configuration commands. To
use this option, step (2) would require you to configure the
database manually instead of using idscfgdb, using a command
like:

  db2 "CREATE DATABASE <dbname> USING CODESET UTF-8
       TERRITORY US COLLATE USING UCA400_NO"

Problem summary

This APAR adds a new option to the idscfgdb command: "-collate".
Adding the "-collate" option to idscfgdb when creating the
database will cause UTF-8 data to be sorted using the UCA
(Unicode Collation Algorithm) collation sequence that is based
on the Unicode Standard version 4.00 with normalization
implicitly set to on. Details of the UCA can be found in the
Unicode Technical Standard #10, which is available at the
Unicode Consortium Web site (www.unicode.org).

Problem conclusion

The fix for this APAR will be contained in the following
maintenance packages:
| interim fix | 6.2.0.1-TIV-ITDS-IF0001 |

Temporary fix

Comments

APAR Information

APAR number
IO10709
Reported component name
IBM TIV DIR SER
Reported component ID
5724J3960
Reported release
620
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2009-06-02
Closed date
2009-06-02
Last modified date
2023-03-15

APAR is sysrouted FROM one or more of the following:

IO10650
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
IBM TIV DIR SER
Fixed component ID
5724J3960

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVJJU","label":"IBM Security Directory Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"620","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

Modified date:
15 February 2024

Tips

IO10709: TDS server may not sort national language characters properly

Direct links to fixes

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

Document Information

Share your feedback

Need support?