| Author |
Message
|
| dkeister |
 Posted: Wed Aug 01, 2007 11:33 am Post subject: Insert into Oracle failure for migrating from 5 to 6 |
 |
|
Disciple
Joined: 25 Mar 2002
Posts: 184
Location: Purchase, New York
|
A message flow in WMB 5 successfully inserts records into an Oracle 9i database. One of the insert fields in the database is 4000 characters. After migrating to WMB 6 the message flow fails with the following error:
SQL error is HY104 - [DataDirect][ODBC Oracle driver]Invalid precision value. Error in parameter 21.
If the message flow is changed to truncate parameter 21 to 1999 characters, the insert is successful, 2000 characters or more gets the SQL error.
Any thoughts?
_________________
Dean Keister |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Aug 01, 2007 11:41 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
|
| Back to top |
|
|
| dkeister |
| Posted: Wed Aug 01, 2007 2:19 pm Post subject: |
|
|
Disciple
Joined: 25 Mar 2002
Posts: 184
Location: Purchase, New York
|
Yup, we are there and beyond.
_________________
Dean Keister |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Aug 01, 2007 2:21 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
....
Are you at FP3 of Broker runtime?
Are you using ESQL Insert, or PASSTHRU, or calling a stored procedure?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Aug 01, 2007 2:58 pm Post subject: Re: Insert into Oracle failure for migrating from 5 to 6 |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| dkeister wrote: |
A message flow in WMB 5 successfully inserts records into an Oracle 9i database. One of the insert fields in the database is 4000 characters. After migrating to WMB 6 the message flow fails with the following error:
SQL error is HY104 - [DataDirect][ODBC Oracle driver]Invalid precision value. Error in parameter 21.
If the message flow is changed to truncate parameter 21 to 1999 characters, the insert is successful, 2000 characters or more gets the SQL error.
Any thoughts? |
Looks suspiciously like a CCSID problem to me.
Remember UTF-16 1999 char is just under the limit with 2 bytes per char if Oracle reserves just 1 and thinks it gets ccsid 819...
Can you be sure in which way the field data is stored? UTF-16 (broker default) or UTF-8? or 819?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| dkeister |
| Posted: Thu Aug 02, 2007 5:12 am Post subject: |
|
|
Disciple
Joined: 25 Mar 2002
Posts: 184
Location: Purchase, New York
|
Thanks for the suggestion. I will have to check this out. I've not paid much attention to CCSID in the past so have some learning to do. I'm in the middle of getting a release out so it will probably be the weekend before I get a chance to follow up.
I'll post the results.
_________________
Dean Keister |
|
| Back to top |
|
|
|
|
