Re: Some more problems with exporting Access Table in Oracle

From: Mark Bole <makbo_at_pacbell.net>
Date: Sat, 01 Jan 2005 17:17:52 GMT
Message-ID: <4XABd.5781$yV1.5694@newssvr14.news.prodigy.com>

Alan wrote:

> <premmehrotra_at_hotmail.com> wrote in message
> news:1104520927.457862.5180_at_c13g2000cwb.googlegroups.com...
>

>>I am using Access 2000 and Oracle 9.2.0.x on a Windows 2000. I have
>>setup Oracle 9.2 ODBC Driver (I have not yet figured how to set
>>Microsoft's Oracle ODBC driver).

Setting MS Oracle driver for ODBC data source is the same process as Oracle driver. The default driver that comes with, say, W2K Pro, appears to be sadly out of date (treats CLOB as TEXT(255) datatype), but there's probably an update available from MS. But then, if you have to go download something, just go get Oracle's driver.

>>
>>I am exporting a table from Access to Oracle and I get following error:
>>
>>ODBC Call Failed:
>>ORA-12571: TNS Packet Failure Error
>>

As Sybrand stated, the error is a network error, no reason to think it has anything to do with CLOBs.

>>I see table and its indexes created in Oracle. However, there are no
>>rows populated.
>>
>>I see there are CLOB columns created in Oracle Table (Memo of Access is
>>mapped to CLOB). Could CLOB be an issue?
>>How does one troubleshoot an error like this.
>>
>>Thanks.
>>
>>Prem
>>

> 
> 
> I have never seen an ODBC driver that suppports CLOBs, or any *LOB, for that
> matter.
> 
>

Need to look harder. ODBC and CLOBs work just fine, I just confirmed my recollection with a quick test. MS Access 2000, Oracle ODBC driver, Oracle 9iR2 database and client. As mentioned, the Access datatype corresponding to CLOB is MEMO. As the CLOB gets bigger, there does come a point (somewhere before 1 MB) where Access no longer be able to view or edit the entire CLOB value, but it still displays in query view.

-Mark Bole Received on Sat Jan 01 2005 - 11:17:52 CST