Hi Manuel, I'm sorry, but you cannot simply restore a backup of a ascii database into a unicode database. But there are two possibilities to migrate to unicode.
1.) Use the loader tool to export your ascii database and import it into a unicode database instance. The loader also allows to modify the datatype of the affected columns from (VAR)CHAR ASCIII to (VAR)CHAR UNICODE. Details about the loader can you find at: http://dev.mysql.com/doc/maxdb/en/59/025741c0c28447e10000000a1550b0/content.htm 2.) First please make a backup of your database. Afterwards upgrade your database to version 7.5 using our upgrade tool sdbupd. This will automatically enables uniocode for your database and migrates your catalog to unicode. But after this the columntype of your character columns is still ascii. So you need to change the datatype for all columns that should store unicode data now. For example, you have a table like "create table t ( c char(100) ascii )" then use this command "alter table t modify ( c char (100) unicode )" to change your column type. Best regards, Marco > -----Original Message----- > From: Manuel Reiter [mailto:[EMAIL PROTECTED] > Sent: Montag, 17. Juli 2006 14:05 > To: Paskamp, Marco > Cc: [email protected] > Subject: Re: save text in differnt languages eg Slaovac / > Cyrillic SAPDB/MAXDB > > Hi Marco, > thanks for the info we will give that a try. Can we cretae > the new database with the database parameter _UNICODE true > and restore a backup of the actual database into that ? Do we > have to change something elese beside the database parameter > and the JDBC-driver eg. a datatype of a table ? > greetings from Linz to Berlin. > Manuel > > > > Paskamp, Marco schrieb: > > >Hi, > >I guess you use JDBC to access the database, right? > > > >First you need a database instance that supports unicode. > The database parameter _UNICODE must be true. Unfortunately > you can set this parameter only when you create the database. > You cannot change this parameter afterwards. > > > >If you use an old version of JDBC you need to set the > connect property unicode=yes within your connect URL when > your sql statements contains unicode characters. Otherwise > unicode characters will be replaced by question marks. You > don't need to set this parameter if you use a newer version > of MaxDB's JDBC driver (at least 7.6.0 Build 020-000-005-036). > > > >Regards, > >Marco > >------------------------- > >Marco Paskamp > >SAP Labs Berlin > > > > > > > > > >>-----Original Message----- > >>From: Manuel Reiter [mailto:[EMAIL PROTECTED] > >>Sent: Montag, 17. Juli 2006 12:22 > >>To: [email protected] > >>Subject: save text in differnt languages eg Slaovac / Cyrillic > >>SAPDB/MAXDB > >> > >>Hi we have an Java client server software that runs on SAPDB 7.3. > >>As we are now expanding into other countries (no German > speaking ones) > >>we are in the need to save text to the DB that is eg. in > Slovak. The > >>problem is that there are some special characters that seem > not to be > >>saved into the DB correctly: > >>eg. ΕΎ (Unicode \u017E ). The User can type in the character > correctly, > >>bute when the reopen the text from the DB instaed of these special > >>characters it just shows ??? How can that characters be saved > >>correctly ? > >>any ideas welcome. > >>regs Manuel > >> > >> > >> > >> > >>-- > >>MaxDB Discussion Mailing List > >>For list archives: http://lists.mysql.com/maxdb > >>To unsubscribe: > >>http://lists.mysql.com/[EMAIL PROTECTED] > >> > >> > >> > >> > 9204 > > -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
