Mailing List
Home
Forum Home
MySQL General - General MySQL discussion
MaxDB - Everything about MaxDB, formerly known as SAP DB
MySQL++ - Programming with the C++ API to MySQL
MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP
ODBC - ODBC with the MySQL Connector/ODBC driver
Java Help - Mostly related to the MySQL Connector/J driver
Perl - Perl support for MySQL with DBI and DBD::mysql
GUI - MySQL GUI Tools
Announcement
Subjects
• mysql openssl Question
• mysql:it 's a db not a dbms how it 's possible?!
• Does the binary log enabling affect the MySQL performances?
• Strange behavior, Table Level Permission
• FULLTEXT query format question
• Preventing Duplicate Entries
• Comparing and writing out BLOBS
• Executing MySQL Commands From Within C Program
• Can 't access mysql after kernel upgrade
• Mysql 4 0 Oracle Stored Procedure Trigger Conversion
• Downgrade Mysql from 4 to 3 23
• MySQL Cluster Software
• mysql test 4 1 fails with the gis test
• ERROR 2002: Can 't connect to local MySQL server through socket
• Getting Identity after INSERT
• Update one field with more fields from another table
• ERROR 1045: Access denied for user: 'root@localhost ' (Using
password: NO)
• mysql have same function mthod as Oracle decode()
 
maxdb crashed and cant import data anymore, even after recrea,ting the insta

maxdb crashed and cant import data anymore, even after recrea,ting the insta

2006-08-04       - By Thomas Stegbauer

 Back
>>  
>>> i can again create my usergroups and tables and import some
>>> data, but in
>>> the moment the access-table contains a german umlaut access brings the
>>> error "[SAP AG][SQLOD32.DLL][SAP DB]General error:-8046 Pos(632)
>>> Conversation from UNICODE impossible AC20. (#-8086)
>>>    
>>
>> This is done on instance creation and can't be changed. You need to drop the
>> database and create it with UNICODE=YES.
>>  
>
>i will see, i dropped the instance and recreated with the extended parameter
>_UNICODE=YES (i left this unchanged) and set DEFAULT_CODE from ASCII to
>UNICODE.
>
>
>now the import works (even with the german umlauts). but i was 100% sure
>before that the parameter was set ASCII before.
>
>i will check the test's when everything is inserted.

ok after several trials, i figured out
DEFAULT_CODE was ASCII before.

the error above comes, when
_UNICODE=YES and DEFAULT_CODE=ASCII

so i can import with access97 and sapdb odbc 7.4 (cause 7.5 doesnt work on the
old windows nt4 for me)
when:

_UNICODE=YES
DEFAULT_CODE=UNICODE

but then our app cant read all data, cause it isn't complete unicode compatible
:(

and it works when

_UNICODE=no
DEFAULT_CODE=ASCII


>>  
>>> 2006-08-03 14:24:27  3506 ERR -11987 COMMUNIC kernel released
>>> connection!
>>>
>>> 2006-08-03 14:41:25  3609 ERR -11608 COMMUNIC sql03_request: wrong
>>> connection state, state is 'requested'
>>>    
>>
>> I remember this error but I believe it's fixed already in later versions
>> (haven't seen it yet for a long time).
>>  
>i think this was a overfilled /tmp/ where i tried to save the output.
>will also come up, on the next test, but this will take a while.

this was the full /tmp/ :/



--
# Thomas Stegbauer
# https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x9A3F1866FC68E91D
# Key fingerprint = 5A2D FEDC 8A50 F1BB 25FB  967B 9A3F 1866 FC68 E91D




--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=mysql@(protected)