Re: Data not importing correctly

From: Andrew Lowe <agl_at_wht.KILLSPAM.com.au>
Date: 04 Oct 2004 21:50:32 GMT
Message-ID: <Xns95794FCAF6D30aglwhtcomau@211.29.133.50>

Hans Forbrich <news.hans_at_telus.net> wrote in news:7zb8d.20310$223.5959_at_edtnps89:

> Andrew Lowe wrote:
>

>> 
>>             As I said I'm new to the Oracle world. I hav TOAD on both
>>             the 

>
> No worries. There are reasons for using exp and there may be some for
> avoiding it. Wanted to verify first.
>

>>             clients
>> machine and my own and it makes life a lot easier for me, eg SQL Plus
>> Vs TOAD. When I was at my clients office, my concern was that their
>> setup of Oracle 9i running on Solaris, ie 64 bit on a SPARC CPU,
>> would cause binary problems when trying to load data into my setup,
>> 9i on Win2000, ie 32bit on Intel, hence the "text way".

>
> Assuming you want ALL the table data, Oracle provides a pair of
> utilities to export data from a database and import that same data.
> There are preconditions (version, char set), but in general these
> utilities will help you ensure you get the data across properly
> regardless of OS.
>
> You want to run exp for a table using the table owner on the solaris
> box. Then imp on windows. (Command line utilities)
>
> Both commands respond to parameter 'help=Y' to provide syntax - should
> be enough to help. Both are very flexible and are fully described in
> the Utilities manual at http://tahiti.oracle.com
>
> HTH
> /Hans
>

Hans,

            Thanks for the reply but the blame as to why this was not working lays directly at the feet of TOAD. As I said I had to import a series of rows that contained as one of its columns a column that consisted of the lower, non displayable, ASCII characters, the characters such as '^C', the value 3 or ETX and '^K', the value 11 or VT. When I viewed the columns in question in a text editor, it appeared as a square box inside quotes, something I've seen before for non-displayable characters, so I loaded this file as a script into TOAD and executed it. TOAD displayed the column in question as '.' which I assumed to be its way of displaying the lower value ASCII characters. IT'S NOT!!!! After loading the data several times I eventually worked out that TOAD can't handle the lower value ASCII characters when it reads in scripts to its SQL editor. I have hunted around and found DBOne from Fox Software which HAS been able to handle lower ASCII values and has successfully loaded my data.

            So after all that, thanks for your time and ideas but it was my $%% &&^$%$^$$^$%&^%**$%##$% copy of TOAD.

    	Regards,
    	    	Andrew Lowe

Received on Mon Oct 04 2004 - 16:50:32 CDT