Strange issue regarding Oracle Data Source and Mid Server
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-11-2016 05:03 AM
Hi all,
like the topic says. We have some Data Sources that use JDBC to connect via Mid Server to Oracle Databases. Sometimes the connection failes, with no particular reason. So we test loaded records manually. Sometimes the connection fails 5 times in a row, also with different Data Sources. A few minutes later after ONE connection is succesfull all other Data Sources get also an connection.
Anyone else with symptoms like this ?
Our instances: Geneva Patch 6 Hotfix 2
Mid Server Logfile entry: 08/11/16 13:12:10 (582) Worker-Standard:JDBCProbeError Worker completed: JDBCProbeError source: Did not get a response from the MID server time: 0:00:00.002
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-03-2016 03:16 PM
Same issue here, today (10/03/16) pulling a SCCM query through midserver on our dev instance. We are also Helsinki Patch 3.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-03-2016 03:20 PM
Also, to add I set three that were ready for cancelProbe to error and restarted mid server from instance, it now appears that data result sets are starting to be returned based on queue logs.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-03-2016 03:36 PM
Some additional information to my problem was that this whole process seems to have been kicked off by a timeout being exceeded. A cancel JDBC request is sent to the MID server; this creates the NULL pointer problem and until the ECC queue is cleared of the cancel request then the MID server will only accept heartbeat (expedited) requests.
This looks like a MID server bug....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-12-2016 12:07 AM
Hi Henning
Please check the midserver which you are using for JDBC Connection are in cluster?Clustered MIDservers does not support the JDBC connection. Try to use a MIDserver which is not in cluster.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-24-2016 07:59 AM
Hi Harsh,
sorry for the late response. As i mentioned earlier, sommetimes it works, sometimes not. We have no clustered MID Servers.