| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| DatabaseException BIP2322E when inserting into Oracle9i |
« View previous topic :: View next topic » |
| Author |
Message
|
| srikanth av |
 Posted: Tue May 09, 2006 10:15 am Post subject: DatabaseException BIP2322E when inserting into Oracle9i |
 |
|
Apprentice
Joined: 30 Jun 2005
Posts: 37
|
Hi,
My environment is MB v6,Broker on AIX,Toolkit on Windows.
I have developed a message flow which extracts the data from AS/400 system(DB2) and inserts into Oracle9i DB.
Initially the flow executed successfully inserting about 700 records into Oracle DB.But when i want to insert 1000 records into Oracle it is throwing the following exception at 756th record and also at 917th record.I checked those records and to me they looked similar to previous records.
DatabaseException BIP2322E: Database error: SQL State ''32''; Native Error Code '0'; Error Text ''[DataDirect][ODBC 20101 driver]1816073''.
Can any one give some idea what the error is and where i am going wrong.
Thanks in advance.
_________________
a v srikanth |
|
| Back to top |
|
 |
| sirsi |
| Posted: Wed May 10, 2006 7:53 am Post subject: |
|
|
Disciple
Joined: 11 Mar 2005
Posts: 177
|
| search for the error in some database forums |
|
| Back to top |
|
|
| Ian |
| Posted: Wed May 10, 2006 8:27 am Post subject: |
|
|
Disciple
Joined: 22 Nov 2002
Posts: 152
Location: London, UK
|
| Quote: |
| ''[DataDirect][ODBC 20101 driver]1816073'' |
The format when database errors are logged is : [Driver Manager][Driver]"Error text"
When using WMB and Oracle on a Unix platform then we would expect to see the following : [DataDirect][ODBC Oracle driver] Error Message
The ODBC interface would typically return "20101" when it can't locate the localized (NLS) message catalog which is an environment setup and configuration problem.
This could be due to one of a number of reasons, but in summary the DataDirect message catalogs are provided in the en_US directly only and soft (symbolic) links are created in /usr/lib/locale/en_US/LC_MESSAGES.
The DataDirect message catalog is picked up through the env variable NLSPATH as per the sample profile.
The prefix of the driver, ie UKor820, is used to find the associated messages catalogs based on the LANG, NLSPATH etc.
From the information provided I can give a definitive answer as to what has not been setup and configured correctly.
I would suggest that you check your broker profile, env, locale and WMB
directory listings. Have you run the mqsi_setupdatabase command as per topic "an07130_" ?
_________________
Regards, Ian |
|
| Back to top |
|
|
| JT |
| Posted: Wed May 10, 2006 8:48 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Have you considered activating an ODBC trace ? |
|
| Back to top |
|
|
| Ian |
| Posted: Thu May 11, 2006 1:32 am Post subject: |
|
|
Disciple
Joined: 22 Nov 2002
Posts: 152
Location: London, UK
|
An ODBC trace will not give you anything with which to resolve this error. You need to check your broker configuration as suggested.
_________________
Regards, Ian |
|
| Back to top |
|
|
| fede309 |
| Posted: Wed Mar 21, 2012 8:01 am Post subject: |
|
|
Novice
Joined: 02 Mar 2012
Posts: 15
|
| Ian wrote: |
| Quote: |
| ''[DataDirect][ODBC 20101 driver]1816073'' |
The format when database errors are logged is : [Driver Manager][Driver]"Error text"
When using WMB and Oracle on a Unix platform then we would expect to see the following : [DataDirect][ODBC Oracle driver] Error Message
The ODBC interface would typically return "20101" when it can't locate the localized (NLS) message catalog which is an environment setup and configuration problem.
This could be due to one of a number of reasons, but in summary the DataDirect message catalogs are provided in the en_US directly only and soft (symbolic) links are created in /usr/lib/locale/en_US/LC_MESSAGES.
The DataDirect message catalog is picked up through the env variable NLSPATH as per the sample profile.
The prefix of the driver, ie UKor820, is used to find the associated messages catalogs based on the LANG, NLSPATH etc.
From the information provided I can give a definitive answer as to what has not been setup and configured correctly.
I would suggest that you check your broker profile, env, locale and WMB
directory listings. Have you run the mqsi_setupdatabase command as per topic "an07130_" ? |
Hi, sorry for resuming this old post, but I have the same problem with the same environment (this is a super simple flow with a FileInputNode that read one record at time), could you be more precise on which configuration should I check?
Thanks |
|
| Back to top |
|
|
| fede309 |
| Posted: Thu Mar 22, 2012 4:13 am Post subject: |
|
|
Novice
Joined: 02 Mar 2012
Posts: 15
|
| fede309 wrote: |
| Ian wrote: |
| Quote: |
| ''[DataDirect][ODBC 20101 driver]1816073'' |
The format when database errors are logged is : [Driver Manager][Driver]"Error text"
When using WMB and Oracle on a Unix platform then we would expect to see the following : [DataDirect][ODBC Oracle driver] Error Message
The ODBC interface would typically return "20101" when it can't locate the localized (NLS) message catalog which is an environment setup and configuration problem.
This could be due to one of a number of reasons, but in summary the DataDirect message catalogs are provided in the en_US directly only and soft (symbolic) links are created in /usr/lib/locale/en_US/LC_MESSAGES.
The DataDirect message catalog is picked up through the env variable NLSPATH as per the sample profile.
The prefix of the driver, ie UKor820, is used to find the associated messages catalogs based on the LANG, NLSPATH etc.
From the information provided I can give a definitive answer as to what has not been setup and configured correctly.
I would suggest that you check your broker profile, env, locale and WMB
directory listings. Have you run the mqsi_setupdatabase command as per topic "an07130_" ? |
Hi, sorry for resuming this old post, but I have the same problem with the same environment (this is a super simple flow with a FileInputNode that read one record at time), could you be more precise on which configuration should I check?
Thanks |
fixed! the problem was a string too long for the db field limit, but the ODBC driver failed to encapsulate oracle error |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
