| Author |
Message
|
| mooretis |
 Posted: Wed Jun 05, 2002 6:47 am Post subject: Database Connection Error ORA-3113 |
 |
|
Newbie
Joined: 13 Nov 2001
Posts: 9
Location: Kansas City
|
We are connecting to an Oracle database for the purpose of doing data translation. We are getting an ORA-3113 'End of Communication Channel' for the first transaction each day and our theory is that WMQI is opening a connection to our database and holding onto that connection across flow instances. Then when our database is brought down for backups each night, WMQI does not recognize that the connection is broken until it attempts to use the connection it had previously. It only happens on the first transaction of the day and then works fine for the remainder of the day.
I am looking for confimation to this and to see if anyone else has experienced similar issues and how they were able to get around this issue.
Thanks! |
|
| Back to top |
|
 |
| TorpedoSTu |
| Posted: Fri Jun 07, 2002 1:26 am Post subject: |
|
|
Acolyte
Joined: 14 Nov 2001
Posts: 73
|
Hi,
We're experiencing a similar problem here.
Your exact symptoms were allegedly fixed in SI 2.1 (APAR IY29050), Our problem (and we're using 2.1 CSD2) is similar and slightly worse in that our connection is dropping causing the same 3113 error if an execution group is left dormant for a period of time (i.e. timeout'ing).
We've raised this with IBM and will keep you posted as to it's resolution.
Regs
Stu
BTW - which version of Oracle are you using as this seems to have a bearing on the timeouts |
|
| Back to top |
|
|
| mooretis |
| Posted: Fri Jun 07, 2002 5:13 am Post subject: |
|
|
Newbie
Joined: 13 Nov 2001
Posts: 9
Location: Kansas City
|
| Thanks for the response. We are using Oracle 8.1.7, and just recently upgraded to WMQI 2.1 and applied CSD3. |
|
| Back to top |
|
|
| philip.baker |
| Posted: Fri Jun 07, 2002 9:59 am Post subject: |
|
|
Voyager
Joined: 21 Mar 2002
Posts: 77
Location: Baker Systems Consulting, Inc. - Tampa
|
WMQI V2.1 CSD02 was released on April 26,2002. I don't see a CSD03 out there. Are you sure about your CSD? There have been a lot of APARs for various MQSI versions relating to Oracle connections. Please confirm your version of MQSI/WMQI and CSD loaded. Also, which Oracle driver are you using with 8.1.7. This can sometimes make a difference; not in how the broker manages database connections, but in data retrieved from the Oracle database.
Regards,
Phil |
|
| Back to top |
|
|
| mooretis |
| Posted: Fri Jun 07, 2002 10:39 am Post subject: |
|
|
Newbie
Joined: 13 Nov 2001
Posts: 9
Location: Kansas City
|
| We are actually at CSD02. I am using the Microsoft ODBC for Oracle driver, on Windows 2000. However, I know it uses the Oracle Client (which we have 8.0.6 client installed) to talk with Oracle. |
|
| Back to top |
|
|
| TorpedoSTu |
| Posted: Wed Jun 12, 2002 6:16 am Post subject: |
|
|
Acolyte
Joined: 14 Nov 2001
Posts: 73
|
Hi,
Getting to the bottom of this having managed to talk to the chap who wrote the code !!!!...
First up, you should be using the MERANT driver with Oracle 8.1.7 client. This is because the MERANT (MQSeries MERANT 3.70 32-BIT Oracle8) driver is ODBC level 3 compliant which is pre-requisite for ALL releases of WMQI. The reason why it's only started with the implementation of 2.1 is that the level3 capabilities were only brought in at this release level (CSD2 - Create procedure support). Also, WMQI is only valid for Oracle 8.1.6 and above. The documentation that says that previous versions are ok is wrong, although you can connect to previous releases of Oracle as long as you're using the 8.1.7 client - but it's not supported.
Our problem is on AIX, and we've had to upgrade our C++ runtime libraries to 5.0.2.0 which is a pre-requisite of the MERANT driver (NOT WMQI so it's not documented)
Regs
Stu |
|
| Back to top |
|
|
|
|
