Rebuilding a database for version 10
This section describes how to unload the database and load it into a new version 10 database. To upgrade your Windows CE database, refer to the documentation.
Attention:
Unloading and loading large databases can take considerable time and disk space. The entire process takes approximately twice times the size of the database disk space to hold the unload data and the new database files.
The following are the limitations of using the tools provided by version 10 to upgrade a version 9.0.2 or an earlier version of a database:
• The earlier version of the database server must be disconnected from the database and the number of earlier versions running is closed
According to the library server. You must also close the version 10 database server. If the dbunload detects the above situation, it may cause an error or failure.
• Do not include Eng, START, or links connection parameters in the Dbunload connection string (-C option). If you specify the above parameters, they are ignored and a warning message is generated. In the Sybase Central Connection dialog box, do not enter values in the server name and start line two text boxes.
• You must run Dbunload on the computer where the legacy database resides (Dbunload must use shared memory to connect to the database).
• You cannot start a database server named Dbunload_support_engine on a computer that is about to occur on the rebuild.
• If you are using NetWare, you must rebuild the database on Windows, Unix platforms. You can use the version 10 database server on NetWare to connect to the upgraded database.
Special matters:
• Password is sensitive to case sensitivity. In the newly created SQL Anywhere 10 database, all passwords are case-sensitive, regardless of the case sensitivity settings for the database. The new default password for the DBA is SQL.
When you rebuild an existing database, SQL Anywhere determines the case sensitivity of the password according to the following rules:
o packages passwords are created in a case-sensitive database, the passwords are case sensitive.
o packages passwords are created in a case sensitive database, uppercase and lowercase passwords will remain case-sensitive. However, if the original password is all lowercase, the password becomes case sensitive.
o Modifying existing and new passwords are case sensitive.
• Page size. SQL Anywhere 10 has adjusted the default page size from 2048 bytes to 4096 bytes. In version 10, 2048 bytes, 4096 bytes, 8192 bytes, 16384 bytes, and 32768 bytes are supported. If the older database uses an unsupported page size, the new database uses the default 4096 bytes as the page size. Use the Dbinit command with the-P option to specify a different page size.
• character sorting. Unless you specify a new or different character sort for the rebuilt database, the character ordering in the old database is followed.
If you use custom character sorting to rebuild a database, character sorting is saved in the case of a single-step rebuild. If you choose to unload the database and then load the schema and data into the newly created database, you must use one of the provided character sorts.
• External unload loading and character set conversion. When you use the external unload, load, and the database character set and run
Dbunload the host system does not match the character set, the conversion of the character set can cause data corruption because the data is converted from the database character set to the host system's character set. To avoid this problem, specify the database character set in the database connection string (the-AC option of the-C option or dbunload), or fill in the value at the appropriate location of the Database Uninstall Wizard. For example, the database character set is UTF-8, you must include "Charset=utf-8" in the connection string:
dbunload -c UID=user-ID;PWD=password;
CHARSET=utf-8;DBF=filename -ac UID=user-ID;
PWD=password;CHARSET=utf-8;ENG=server-name -xx