on 2011 Apr 12 1:12 PM
The Help says this...
Collations In version 9 and earlier, SQL Anywhere supported one collation used with CHAR data types. This collation used the SQL Anywhere Collation Algorithm (SACA). In version 10 and later, SQL Anywhere supports two collation algorithms, SACA and UCA (Unicode Collation Algorithm). Unless you specify a new or different collation for the rebuilt database, the SACA collation from the old database is unloaded and reused in the rebuilt database. http://dcx.sybase.com/index.html#1201/en/sachanges/unloading-reloading-upgrading-newjasper.html
Is it possible to specify UCA for the new database when using dbunload in a single step (internal unload)?
As Volker noted, you need to create the database first and then use dbunload -ac. On Windows, it will use an OS named piped to transfer table data between the V9 engine and the V12 engine.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I guess you would have to create a new database with the according collation first and then use dbunload -ac to do an one-step unload into the newly created database.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
67 | |
10 | |
10 | |
10 | |
10 | |
8 | |
8 | |
7 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.