start the database with character set translation off

[Former Member]

I'm trying to follow the instructions on this page to start the database with character set translation turned off. According to the instructions from this page:

dbeng9 -ct- c:\\oem.db

Since, I'm using version 12. I'm trying

dbeng12 -ct- c:\\oem.db

Error in command near "ct".

In the server options of dbeng12 also I can not find the option -ct. Can someone please tell me how can I start the database with character set translation turned off, for the Sybase Anywhere v 12. Thanks

[VolkerBarth]

Here is a v12 doc page "Change a database from one collation to another" that seems more suitable than the v9-specific dpo page you relate to.

Unfortunately, it doesn't have a sample but you might get the impression...

[VolkerBarth · Accepted solution]

From the 12 docs "V10 - What's new in version 10":

Character set conversion is always enabled on the database server

The -ct database server option for enabling and disabling character set conversion is no longer supported. Character set conversion is always enabled for the database server, but if the database server determines that it is not required, then it is not used. You can disable character set conversion from the client by specifying CharSet=none. See CharSet (CS) connection parameter.

So you will have to omit this option with v12.

If the reload does not work as expected, I would try using DBISQL with the CS parameter (as specified above) or with a fitting ENCODING clause of the LOAD TABLE statements in the reload.sql script.

[Former Member · Accepted solution]

Thanks. Could you tell how I can add encoding clause to the load statement? currently i'm simply doing "read reload.sql". The problem i'm having is after updating db, the non-english characters become unreadable.

[VolkerBarth · Accepted solution]

I would suggest to answer the questions on your other question, i.e. what collation you have used so far and what collation you want to use (or what locale do you use) - that may help us to give better help....

To your current question: The reload.sql script might contain LOAD TABLE statements (when the UNLOAD tool was told to use internal reload), and these can have an ENCODING <your-code-page> clause.

Alternatively, the DBISQL READ statement can use an ENCODING clause itself.