Follow these instructions to change the sort order or default character set for your Adaptive Server if errors occurred when you tried to use sybinit to do this.
This writeup includes the following sections:
Before deciding to use the manual process:
Read “Changing the Default Character Set, Sort Order, or Message Language” in the System Administration Guide for information about the consequences of changing the sort order and default character set.
Look at your Adaptive Server error log and in $SYBASE/init/logs (11.9.x and earlier) or $SYBASE/$SYBASE_ASE/init/logs (12.0.x and later) to determine why sybconfig failed to change the sort order or default character set.
If you find errors in the error log, correct them. See below for common causes of failure.
Try again to use sybconfig to change the sort order or default character set. If it still fails, go to “Manual Process”.
Some common causes of the failure to change the sort order or default character set using sybconfig include:
You are changing to a case-insensitive sort order and duplicates would exist in a system table (because “A” is now equal to “a”, and so on). You should be able to determine which table(s) has this problem from information in the error log. Modify the data so that duplicates will not exist under a case-insensitive sort order.
There is insufficient system segment space to re-create system indexes. Use sp_extendsegment to increase the system segment space for user databases or use alter database to increase the size of the system segment for the master database. Refer to “Extending the Scope of Segments” and “A Segment Tutorial” in the System Administration Guide for details.
There is insufficient log space. Refer to “Using the Special dump transaction Options” in the System Administration Guide for what to do in this case.
A problem exists in sybconfig.
