| Author |
Message
|
| srinivas.dee |
 Posted: Fri Dec 19, 2014 3:06 am Post subject: Issue while connecting to DB |
 |
|
Newbie
Joined: 19 Dec 2014
Posts: 5
|
Hi,
I am getting the below exception, when trying to execute the stored procedure in oracle database. Coudl you please let us the possible reason for this exception.
ODBC Entry:
[DSN]
Driver=/opt/IBM/mqsi/6.1/DD64/lib/UKora23.so
Description=DataDirect 5.3 64bit Oracle Wire Protocol
HostName=10.14.188.55
PortNumber=1521
SID=brmstg
CatalogOptions=0
EnableStaticCursorsForLongData=0
ApplicationUsingThreads=1
EnableDescribeParam=1
OptimizePrepare=1
WorkArounds=536870912
ProcedureRetResults=1
ColumnSizeAsCharacter=1
Exception in the trace file:
2014-12-19 06:41:50.057352 21075 UserTrace BIP2231E: Error detected whilst processing a message in node 'BALANCE'. The message broker detected an error whilst processing a message in node 'BALANCE'. The message has been augmented with an exception list and has been propagated to the node's failure terminal for further processing. See the following messages for details of the error.
2014-12-19 06:41:50.057368 21075 DatabaseException BIP2393E: Database error: ODBC return code '-1' from data source ''DSN''. The broker received an error when executing a database operation. The ODBC return code was '-1'. See the following messages for information obtained from the database about this error. Use the following messages to determine the cause of the error. Typical causes are incorrect data source or table names. Correct either the database or the broker configuration.
2014-12-19 06:41:50.057372 21075 DatabaseException BIP2322E: Database error: SQL State ''08S01''; Native Error Code '0'; Error Text ''[DataDirect][ODBC 20101 driver]7503''. The error has the following diagnostic information: SQL State ''08S01'' SQL Native Error Code '0' SQL Error Text ''[DataDirect][ODBC 20101 driver]7503'' This message may be accompanied by other messages describing the effect on the message broker itself. Use the reason identified in this message with the accompanying messages to determine the cause of the error.
2014-12-19 06:41:50.057376 21075 DatabaseException BIP2322E: Database error: SQL State ''21''; Native Error Code '-4'; Error Text ''[DataDirect][ODBC 20101 driver][20101]10703''. The error has the following diagnostic information: SQL State ''21'' SQL Native Error Code '-4' SQL Error Text ''[DataDirect][ODBC 20101 driver][20101]10703'' This message may be accompanied by other messages describing the effect on the message broker itself. Use the reason identifie
d in this message with the accompanying messages to determine the cause of the error.
Regards,
Srini |
|
| Back to top |
|
 |
| srinivas.dee |
| Posted: Fri Dec 19, 2014 3:11 am Post subject: |
|
|
Newbie
Joined: 19 Dec 2014
Posts: 5
|
Additional details for the above post..
Broker version is 6.1.0.9
Os : AIX |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Dec 19, 2014 5:27 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| srinivas.dee wrote: |
| Coudl you please let us the possible reason for this exception |
Well....
| srinivas.dee wrote: |
| Broker version is 6.1.0.9 |
This version of broker is very old (not even the latest version of v6.1), out of support, and so are it's ODBC drivers. If this used to work and has stopped (which you don't bother to metnion) then I would suggest that maintenance has been applied at the database level making the database incompatible with the drivers.
If it's never worked, I would suggest you're using a version of Oracle higher than the drivers support.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| srinivas.dee |
| Posted: Fri Dec 19, 2014 6:04 am Post subject: Migh |
|
|
Newbie
Joined: 19 Dec 2014
Posts: 5
|
| Thanks Vitor for prompt reply. This is new DSN which we are trying to configure in a new test environement, |
|
| Back to top |
|
|
| srinivas.dee |
| Posted: Fri Dec 19, 2014 6:11 am Post subject: |
|
|
Newbie
Joined: 19 Dec 2014
Posts: 5
|
| The version of broker is same in prod and new test environment. As you mentioned, I need to check the oracle version between new test env and prod. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Dec 19, 2014 7:07 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| srinivas.dee wrote: |
| I need to check the oracle version between new test env and prod. |
You also need to get off that out of support version of WMB before something worse than this happens. Like someone applies maintenance to the OS it's running on......
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| zpat |
| Posted: Fri Dec 19, 2014 7:17 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
http://www.mqseries.net/phpBB/viewtopic.php?p=261796&sid=e20d912db3d870d0f09204e60bece67f
Possible network or firewall issue.
This can result in an error if the firewall or database server terminates the
connection after a certain period of inactivity.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| srinivas.dee |
| Posted: Mon Dec 22, 2014 10:50 pm Post subject: |
|
|
Newbie
Joined: 19 Dec 2014
Posts: 5
|
Hi Jedi,
It is the first time we are trying to connect to this new database. Already broker was configured with other DSNs and we don't find any such issues with the existing DSN.
Below is the ODBC entry which we new configured and causing this issue.
[BILLINGDSN]
Driver=/opt/IBM/mqsi/6.1/ODBC64/V5.3/lib/UKora23.so
Description=DataDirect 5.3 64bit Oracle Wire Protocol
HostName=xx.xx.xxx.xx
PortNumber=1521
ServiceName=billingdb
CatalogOptions=0
EnableStaticCursorsForLongData=0
ApplicationUsingThreads=1
EnableDescribeParam=1
OptimizePrepare=1
WorkArounds=536870912
ProcedureRetResults=1
ColumnSizeAsCharacter=1
Thanks,
Srinivas |
|
| Back to top |
|
|
|
|
