| Author |
Message
|
| akill |
 Posted: Wed Apr 11, 2018 4:13 am Post subject: [unixODBC][IBM][ODBC 20101 driver][20101]10703 |
 |
|
Novice
Joined: 26 Jun 2017
Posts: 16
|
Hi Guys,
I am using queue based message flow(MQ--> DatabaseNode) , Basically i put message in the queue from that message will be inserted into database .
My message flow is inserting records if i send one message after one . But if do load test (50 messages in 60 secs) , once in a while i am getting the below error . For the above scenario 5 messages got failed with the below error and 45 messages are inserted successfully .
DatabaseException BIP2322E: Database error: SQL State ''21''; Native Error Code '-4'; Error Text ''[unixODBC][IBM][ODBC 20101 driver][20101]10703''
Database : Oracle 11g release 2
IIB Version : 10.0.0.7
Kindly help me with the issue .
Appreciate your response . |
|
| Back to top |
|
 |
| exerk |
| Posted: Wed Apr 11, 2018 4:19 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Have you tried Googling SQL State ''21''? I did...
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| akill |
| Posted: Wed Apr 11, 2018 5:05 am Post subject: [unixODBC][IBM][ODBC 20101 driver][20101]10703 |
|
|
Novice
Joined: 26 Jun 2017
Posts: 16
|
I found that below are the possible reasons which causes SQL State 21
1.Insert value list does not match column list
2.Degree of derived table does not match column list
But in my case some records are inserting successfully , if above are the reasons no record would be inserted .
@exerk : Please help me with what might be the issue in my case ?
Thanks in advance |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Apr 11, 2018 5:38 am Post subject: Re: [unixODBC][IBM][ODBC 20101 driver][20101]10703 |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| akill wrote: |
@exerk : Please help me with what might be the issue in my case ?
Thanks in advance |
So I searched again, using the error text [unixODBC][IBM][ODBC 20101 driver][20101]10703, which revealed a post from 5 years ago - I'll leave you to find it.
Moving this to the Broker forum...
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| abhi_thri |
| Posted: Wed Apr 11, 2018 6:34 am Post subject: |
|
|
Knight
Joined: 17 Jul 2017
Posts: 516
Location: UK
|
| Hi...have you tried replaying the failed 5 messages to see what happens, if it still fails that suggests that the issue has got something to do with the data coming in for those messages (eg:- invalid type, exceeds column length etc) |
|
| Back to top |
|
|
| akill |
| Posted: Wed Apr 11, 2018 7:11 am Post subject: [unixODBC][IBM][ODBC 20101 driver][20101]10703 |
|
|
Novice
Joined: 26 Jun 2017
Posts: 16
|
Hi abhi_thri,
Thanks for your response .
Yes i tried and those messages are inserted successfully .
ODBC Trace tells:
[ODBC][6348][1116972800][2018-04-11 19:31:29.373][SQLSetEnvAttr.c][349]
Exit:[SQL_SUCCESS]
DIAG [21] [IBM][ODBC 20101 driver][20101]10703
[ODBC][6348][1136670464][2018-04-11 19:31:29.869][SQLConnect.c][4150]
Exit:[SQL_ERROR]
[ODBC][6348][1136670464][2018-04-11 19:31:29.869][SQLError.c][430]
Entry:
Connection = 0x7f765c06d080
SQLState = 0x7f7643bf9570
Native = 0x7f7643bf956c
Message Text = 0x7f765c082cc0
Buffer Length = 1024
Text Len Ptr = 0x7f7643bf956a
I didn't check connectDatasourceBeforeFlowStarts property on the Database node . Is there any chance that connectDatasourceBeforeFlowStarts property causing the issue . ? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Apr 11, 2018 6:56 pm Post subject: Re: [unixODBC][IBM][ODBC 20101 driver][20101]10703 |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| akill wrote: |
I didn't check connectDatasourceBeforeFlowStarts property on the Database node . Is there any chance that connectDatasourceBeforeFlowStarts property causing the issue . ? |
I doubt it very much. Looks more like input text too long for column width... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| akill |
| Posted: Wed Apr 11, 2018 7:33 pm Post subject: Re: [unixODBC][IBM][ODBC 20101 driver][20101]10703 |
|
|
Novice
Joined: 26 Jun 2017
Posts: 16
|
| fjb_saper wrote: |
I doubt it very much. Looks more like input text too long for column width... |
No , because when i tried inserting the same failure records they are getting inserted successfully . |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Apr 11, 2018 8:08 pm Post subject: Re: [unixODBC][IBM][ODBC 20101 driver][20101]10703 |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| akill wrote: |
| fjb_saper wrote: |
I doubt it very much. Looks more like input text too long for column width... |
No , because when i tried inserting the same failure records they are getting inserted successfully . |
The error coming right after the connect operation suggests:
https://docs.oracle.com/cd/B10501_01/server.920/a96525/nncus.htm#1000644
| Quote: |
NNC-00430 Database not accessible
Cause: When a database is used for consistency between different name servers, any modify operation should not only modify the cache but also the database. And if the database is not accessible, this error occurs.
Action: Not normally visible to the user, except when using the name server control program. If the error occurs when using the control program, make sure database is available and then re-execute the operation. If error persists, contact Oracle Support Services.
|
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| akill |
| Posted: Thu Apr 12, 2018 2:20 am Post subject: [unixODBC][IBM][ODBC 20101 driver][20101]10703 |
|
|
Novice
Joined: 26 Jun 2017
Posts: 16
|
Hi fjb_saper ,
DB team is not terminating connections and DB is accessible all the time . They also concluded that there is no log available as the request hasn't reached DB(because it is a Error while connecting to DB)
But in the IIB trace log i could see only this,
DatabaseException BIP2322E: Database error: SQL State ''21''; Native Error Code '-4'; Error Text ''[unixODBC][IBM][ODBC 20101 driver][20101]10703''
Please help me to move forward
Thanks in advance . |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Apr 12, 2018 2:31 am Post subject: Re: [unixODBC][IBM][ODBC 20101 driver][20101]10703 |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| akill wrote: |
Hi fjb_saper ,
DB team is not terminating connections and DB is accessible all the time . They also concluded that there is no log available as the request hasn't reached DB(because it is a Error while connecting to DB)
But in the IIB trace log i could see only this,
DatabaseException BIP2322E: Database error: SQL State ''21''; Native Error Code '-4'; Error Text ''[unixODBC][IBM][ODBC 20101 driver][20101]10703''
Please help me to move forward
Thanks in advance . |
Which driver are you using for your ODBC ??
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| akill |
| Posted: Thu Apr 12, 2018 3:15 am Post subject: [unixODBC][IBM][ODBC 20101 driver][20101]10703 |
|
|
Novice
Joined: 26 Jun 2017
Posts: 16
|
Hi fjb_saper ,
Below is the driver which is being used .
<InstallationPath>/iib-10.0.0.7/server/ODBC/drivers/lib/UKora95.so
Thanks in advance . |
|
| Back to top |
|
|
| abhi_thri |
| Posted: Thu Apr 12, 2018 4:45 am Post subject: |
|
|
Knight
Joined: 17 Jul 2017
Posts: 516
Location: UK
|
hi...is there any consistent pattern that you are seeing? Eg:- is it just the first few messages that are failing? Have you customized any settings at the odbc stanza (timeout ones)? Can you print the DSN stanza here...
Also I assume BIP2322E is not the only one you are seeing at the logs, can you please send the full error.
Not sure whether this will help, but if nothing works you could try using a Compute node instead of DB one and see that makes any difference. |
|
| Back to top |
|
|
| akill |
| Posted: Thu Apr 12, 2018 5:03 am Post subject: [unixODBC][IBM][ODBC 20101 driver][20101]10703 |
|
|
Novice
Joined: 26 Jun 2017
Posts: 16
|
Hi all,
I have checked the odbc.ini file , the middleware admin team didn't add InstallDir value in the file . We added it and now we are not getting this issue (all the records are getting inserted) .
But in the ODBC trace i am getting folloing error :
[ODBC][16867][1930860288][2018-04-12 18:06:11.517][SQLGetTypeInfo.c][314]
Exit:[SQL_ERROR]
DIAG [HY004] [IBM][ODBC Oracle Wire Protocol driver]Invalid SQL data type.
Please help me |
|
| Back to top |
|
|
| abhi_thri |
| Posted: Thu Apr 12, 2018 5:26 am Post subject: |
|
|
Knight
Joined: 17 Jul 2017
Posts: 516
Location: UK
|
It doesn't sounds right...are you saying that all your transactions are successful (data is inserted to DB) but you can still see errors at odbc trace? Also always use mqsicvp to verify a DSN stanza before using it from broker.
May be the error in the trace is related to someone's messages...anyway, the error is quite clear, it is caused by some data mismatch b/w incoming data and the column type. |
|
| Back to top |
|
|
|
|
