Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
SQLEXECUTOR: ORA-01024: invalid datatype in OCI call
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Thomas Becker  
View profile   Translate to Translated (View Original)
 More options Jun 29 2012, 5:10 am
From: Thomas Becker <thomas.bec...@tu-berlin.de>
Date: Fri, 29 Jun 2012 11:10:05 +0200
Local: Fri, Jun 29 2012 5:10 am
Subject: SQLEXECUTOR: ORA-01024: invalid datatype in OCI call

Hi all,

i have a problem querying a Oracle spatial database (10 & 11) regarding
some specific tables. I receive the message below if i use an SQLEXECUTOR.

---------------------------
SQL Query Error
---------------------------
<b>Failed to execute the SQL Query.</b><p><p>Could not understand type
information: type=101, size=8, scale=0, precision=0

[INFORM]: ORACLE Reader: Using Classic geometry.

[ERROR]: Could not understand type information: type=101, size=8,
scale=0, precision=0

[INFORM]: ORACLE Reader: Executing SQL Statement `Select * From
BUILDING' to obtain features for feature type `QFMEReader_SqlQuery'

[ERROR]: Unable to define column number 13: error was `ORA-01024:
invalid datatype in OCI call'. (serverType=`ORACLE8i',
serverName=`*****', userName=`******', password=`***', dbname=`')

Column 13 contains values such as 52.12356, so double values.
My assumption is, that each table containing the datatype BINARY_DOUBLE
will produce this error. Any hints how to avoid this, except of dropping
the specific column?

Kind regards

Thomas


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »