Closed (outdated)
Project:
Oracle Driver
Version:
7.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Dec 2012 at 10:39 UTC
Updated:
20 Oct 2025 at 09:35 UTC
Jump to comment: Most recent
Comments
Comment #1
ron_ron commentedThank you for advice.
Kind regards
Ron
Comment #2
ron_ron commentedHi find the line where the error occures
include\database\oracle\query.inc line 60
at: $this->connection....
if (count($this->insertValues)==0) // all default query
$last_insert_id = $this->connection->query($stmt, array(), $this->queryOptions);
Kind regards,
Ron
Comment #3
Unitoch commentedI ran into this error as well. I can shed some more light on this.
Steps to reproduce:
1. Install and use the Oracle driver.
2. Install and configure a Solr server and use the Solr module to connect it to your Drupal site.
3. Go to admin/config/search/apachesolr/settings/apache_solr/index and try to reindex your content. You'll get the error.
This is happening because of a query that the Apache Solr module is issuing. It's trying to issue the following query:
What's happening is that the arguments are not correctly bound to the PDOStatement object when it's ultimately getting run. The arguments are there correctly in query.inc, and they're getting bound to the $stmt object on line 53:
But, the bound values aren't correctly being reflected in the final query. I got around it by doing some dirty hacking, passing the arguments to the query function just after that.
And then also hacking database.inc to use that array instead of bound variables.
This kind of hacking is, of course, horrible in many ways and will kill kittens.
I'm guessing this is an edge case, using a select inside an insert and binding the variables to the select. Maybe that's why the error is happening?
Comment #4
bohartD7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7. All D7-related issues are marked as outdated in a bunch.
Everyone can apply the patches/suggestions above (not tested by the maintainers, tested by the community) to their D7 projects.
If the issue remains relevant for D10+ versions, merge requests with proposed solutions for a new module version (D10+) are welcome in a new follow-up issue.
Thanks!