RE: Re: Oracle Typen MDSYS.ST_ANNOT_TEXTELEMENT_ARRAY
John Dorlon <[email protected]>
| Newsgroups | gmane.comp.db.oracle.toad.free |
|---|---|
| Message-ID | <4120B436C765EC43A31CC3E2A13D36A6225666D5@ALVMBXW02.prod.quest.corp> |
There is no question of whether or not he is using a 64 bit client with Toad, because it is not possible. :) He's got to be using 32 bits with Toad, or his is not connecting to the database. Those spatial datatypes are pretty complicated, and some of these complicated data types just don't work well with the Unicode-enabled procedures/functions in the OCI. I don't have a hard and fast list of what works and what doesn't, but your best bet is to always have the most recent 32 bit Oracle client for Toad. From: [email protected] [mailto:[email protected]] On Behalf Of Simoneau, Roger Sent: Monday, October 17, 2011 5:29 PM To: '[email protected]' Subject: RE: [toad] Re: Oracle Typen MDSYS.ST_ANNOT_TEXTELEMENT_ARRAY >> habe mit beiden Versionen 32/64 bit This appears to be a conflict with regards the "Oracle Spatial" datatype. Is anyone familiar with that particular datatype in relation to Toad that might be able to offer some insight? Does Toad 11 support that datatype? Earlier in the thread it was already suggested to move away from the 64 bit client and on to the 32 bit client. Whether that has occurred is anyone's guess. Roger S. ________________________________ This communication, including any attached documentation, is intended only for the person or entity to which it is addressed, and may contain confidential, personal and/or privileged information. Any unauthorized disclosure, copying, or taking action on the contents is strictly prohibited. If you have received this message in error, please contact us immediately so we may correct our records. Please then delete or destroy the original transmission and any subsequent reply.