|
Home > Archive > SQL Anywhere Mobile > March 2005 > There is a new progress about unix odbc driver's error.
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
There is a new progress about unix odbc driver's error.
|
|
| tanxs@263.net 2005-03-30, 9:43 am |
| There is a new progress about unix odbc driver's error.
When i configure MobiLink Add user automatic with parm(-zu
+), there is say:ORA-01400: cannot insert NULL into
("UNICOM_RESOURCE"."ML_USER"."NAME").And there is say:Unable
to insert user name 'pda1' into the ml_user table.I'm
perplexed about this.
But in same setting on windows,MobiLink can add user
automatic.
---------------------------------------
....
W. 03/23 16:25:32. <Main>: Warning: [10050] ODBC:
[DataDirect][ODBC Oracle Wire Protocol driver]Optional
feature not implemented. (ODBC State = HYC00, Native error
code = 0)
W. 03/23 16:25:32. <Main>: Warning: [10050] ODBC:
[DataDirect][ODBC Oracle Wire Protocol driver]Driver's
SQLSetConnectAttr failed. (ODBC State = IM006, Native error
code = 0)
....
I. 03/23 18:54:41. <1.5> [pda1]: User name 'pda1' not found
in the ml_user table, inserting a new entry
I. 03/23 18:54:41. <1.5> [pda1]: Cached ODBC statement:
SELECT hashed_password FROM ml_user WHERE
name = ?
I. 03/23 18:54:41. <1.5> [pda1]: Translated SQL:
SELECT MAX( user_id ) + 1 FROM ml_user
I. 03/23 18:54:41. <1.5> [pda1]: Translated SQL:
INSERT INTO ml_user
(user_id,name,commit
_state,hashed_passwo
rd) VALUES(?,?,?,?)
E. 03/23 18:54:41. <1.5> [pda1]: Error: [-10002] ODBC:
[DataDirect][ODBC Oracle Wire Protocol
driver][Oracle]ORA-01400: cannot insert NULL into
("UNICOM_RESOURCE"."ML_USER"."NAME") (ODBC State = 23000,
Native error code = 1400)
E. 03/23 18:54:41. <1.5> [pda1]: Error: [-10054] Unable to
insert user name 'pda1' into the ml_user table
---------------------------------------
ODBC State = HYC00 is a Unknown Data Type error.
I find the type of field hashed_password of table ml_user is
raw(20).
Maybe is Odbc driver can not map raw to SQL_VARBINARY
But the error remain as before,where i force change the type
or hashed_password to varchar2(20).
| |
| Greg Fenton 2005-03-30, 9:43 am |
| tanxs@263.net wrote:
>
> ---------------------------------------
> E. 03/23 18:54:41. <1.5> [pda1]: Error: [-10002] ODBC:
> [DataDirect][ODBC Oracle Wire Protocol
> driver][Oracle]ORA-01400: cannot insert NULL into
> ("UNICOM_RESOURCE"."ML_USER"."NAME") (ODBC State = 23000,
> Native error code = 1400)
> ---------------------------------------
> I find the type of field hashed_password of table ml_user is
> raw(20).
> Maybe is Odbc driver can not map raw to SQL_VARBINARY
> But the error remain as before,where i force change the type
> or hashed_password to varchar2(20).
Why do you suspect the password column when the error explicitly says
that the issue is with the NAME column?
Can you do an ODBC trace (or unixODBC's equivalent) to find out which
values are being passed to that INSERT statement?
greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/
|
|
|
|
|