You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.
Assignee: Tommi
Status: Resolved (closed on 2011-08-02 09:15:58 +00:00)
Target Version: (none)
Last Update: 2014-12-08 14:35:50 +00:00 (in Redmine)
Icinga Version: 1.10.0
OS Version: any
there is a strange error while using ido2db_get_object_id with insert in upcomming idoutils V1.5.
Binding the first value will raise an OCILIB-Error claiming statement is not prepared. But preparing finished successfully and a getsql on the statement handle just before will print the right statement. I already spend days on this issue without a finding the reason. Maybe its a threading isue or some memory segments are overwritten- i have no glue.
Well, im checkin this, but we are using "returning" in several places and the "needs prepared" problem occures only with objects.
Expectation from oracle side with prepares are if we generate the same sql the hash with every reparsing in the same session will be equal and then only one cursor should be generated. But looks like its implemented in a different way.
Patch is already written, but needs to be tested before commit.
for 1.5 i want to stay with the workaround expecting majoriti of users are not upgrading ocilib to safer version 3.9.2. Maybe it can be removed in a later release
This issue has been migrated from Redmine: https://dev.icinga.com/issues/1638
Created by Tommi on 2011-06-12 10:37:14 +00:00
Assignee: Tommi
Status: Resolved (closed on 2011-08-02 09:15:58 +00:00)
Target Version: (none)
Last Update: 2014-12-08 14:35:50 +00:00 (in Redmine)
there is a strange error while using ido2db_get_object_id with insert in upcomming idoutils V1.5.
Binding the first value will raise an OCILIB-Error claiming statement is not prepared. But preparing finished successfully and a getsql on the statement handle just before will print the right statement. I already spend days on this issue without a finding the reason. Maybe its a threading isue or some memory segments are overwritten- i have no glue.
Changesets
2011-06-12 10:23:44 +00:00 by Tommi db74189
2011-06-12 18:40:39 +00:00 by Tommi 934d920
2011-07-13 17:19:38 +00:00 by Tommi 5ed6a8a
Relations:
The text was updated successfully, but these errors were encountered: